PaaS API Docs
  • Getting Started
  • Authentication
  • Use cases
    • Remittance
      • Bonus/Discount on Remittance
    • Business Payments
    • Individual Wallet
    • Business Wallet
    • Payout
  • API References
    • Data Population
      • Spec Sheet
      • Country
      • States
      • Settlement Rates
    • User
      • User Object
        • User Verification
        • Identification Documents
        • User Verification Status
        • CIP Information Status
      • Receive User Object
      • Register a User
      • Update User
      • Business Representatives
        • Business Representatives Object
        • Add Business Representatives
        • Update Business Representatives
        • Get Business Representatives
      • Declaration
        • Declaration Object
        • Declaration
      • Initiate Verification
      • Get User by ID
      • Get Verification Status
      • Add a Receive User
      • Update a Receive User
      • Get Receive User List
    • Funds
      • User Funding Account Object
      • Funding Account Widget
        • OAuth Integration
        • Bank Verification Status
      • Wallet Object
      • Create a Wallet
      • Get Wallet Details
      • Get User Funding Account
      • Delete User Funding Account
      • Add a Receive Account
      • Update a Receive Account
      • Get Receive Accounts
    • Payout
      • Get Banks
      • Get Payers
    • Transaction (External)
      • Transaction Object
      • Create Transaction
      • Get Transaction by ID
      • Cancel Transaction
      • Transaction Delivery
      • Get Transaction Limits
    • Transaction (Wallet)
      • Wallet Transfer Object
      • Create Transfers
        • Load Wallet
        • Unload Wallet
        • Wallet to Wallet Transfer
      • Get Wallet Transfer Details
      • Get Limits
    • Transaction (Payout)
      • Payout Transaction Object
      • Create Payout Transaction
    • Webhooks
      • Subscribe
      • Integration
      • Events
    • Error Codes
  • Sandbox
    • User: Test Values
    • Funds: Test Values
    • Transaction: Test Values
  • Changelog
    • 2023
      • February 14, 2023
      • January 06, 2023
    • 2022
      • December 28, 2022
      • December 26, 2022
      • December 23, 2022
      • December 2, 2022
      • November 21, 2022
      • November 11, 2022
      • October 31, 2022
      • October 17, 2022
      • August 31, 2022
      • August 1, 2022
      • July 25, 2022
      • May 23, 2022
      • April 7, 2022
      • March 30, 2022
      • March 23, 2022
      • Feb 21, 2022
      • Feb 15, 2022
      • Jan 24, 2022
      • Jan 19, 2022
      • March 10, 2022
Powered by GitBook
On this page
  • User Verification and Transaction Limits
  • KYC/KYB Verification
  • Tier Verification

Was this helpful?

  1. API References
  2. User
  3. User Object

User Verification

The User identification and verification policies and procedures of the program are designed to:

  • Ensure adherence with the user identification and KYC policy of FI partners and various State, Federal and International regulators governing the provision of the services.

  • Ensure adherence with all compliance requirements of FI partners and State/Federal/International regulators.

  • Promote safe and secured business practices and minimize the risk of the services from being misutilized for any fraud, money laundering and other illegal activities.

  • Help monitor and report suspicious activities.

User Verification and Transaction Limits

Our verification processes are designed in line with the compliance policies of our FI partners including the requirements of the Banking Secrecy Act (BSA) and all other State, Federal and International Money Transfer Regulations. This requires collection of certain information from users during the registration based on the amount and volume of transactions. Accordingly, we have devised a Tier based verification program which governs the transaction limits and KYC/KYB requirements for each tier.

Your Specification Sheet, provided by Machnet, will include details of the Transaction limits and KYC/KYB requirements applicable for your users.

User Verification is divided into KYC/KYB verification and Tier verification. Information required for KYC/KYB and tier verification is referred to as CIP tags. Each user has a KYC/KYB verification status and each field corresponding to the required CIP tag also has its own verification status. Only when all CIP information required for KYC/KYB verification (listed below) are verified will the KYC status of the user be verified.

KYC/KYB Verification

If the user is an individual, the following basic information will be required to perform Know Your Customer (KYC) verification checks.

  • Name

  • Date of birth

  • Gender

  • Address

  • Email

  • Phone number

If the user is a business, the following basic information will be required to perform Know Your Business (KYB) verification checks.

  • Name of company

  • Type of company

  • Date of formation of the company

  • Registered address

  • Mailing address

  • Phone number

  • Email address

  • Nature of business

  • No. of employees

  • EIN Number

  • EIN Document

  • Certificate of Incorporation (if deposit_enabled: true)

  • Company Website (if deposit_enabled: true)

  • Business Representative Information (if deposit_enabled: true)

    • Full name

    • Address

    • DOB

    • Email

    • Phone

    • Gender

    • Title

    • Ownership_percentage (if beneficial owner)

    • Business representative type

    • SSN if US individual

    • Passport no. if non-US individual

    • Copy of US government issued ID (Passport, driving license or state ID) if US individual

    • Copy of foreign passport if non-US individual

The Platform requires the user to complete user verification for any transaction of the user to be processed and paid out. Any user whose verification is pending may however be allowed to perform other actions in the Platform, unless they are “Suspended”.

Tier Verification

While basic information is required for KYC/KYB verification, additional CIP information may need to be collected and verified for the user to be able to transact. The required information for each tier and their corresponding transaction limits are outlined in your Specification Sheet.

While the user may be able to create a transaction without submission and verification of the required tier information, the transaction will not be processed and paid out until the required information is submitted and verified.

PreviousUser ObjectNextIdentification Documents

Last updated 2 years ago

Was this helpful?