RaaS Operational Documents
  • Operation Documents
  • Process Level Document
    • Background
    • Platform Process Flow
    • User Registration
    • Know Your Customer (KYC) Verification
    • Payment Method
    • Recipient Addition
    • Transaction Processing
    • Returns and Chargebacks
    • Refunds
    • Transaction Payout
    • Error Resolution/Process Handling
    • Support Details
    • Service Update
    • Disclaimer
    • Guidelines for User Account Data deletion
    • Annexure I: First Level Solutions
    • Annexure II: KYC Notes and Action Required
    • Change Log
  • Whitelabel Integration Guide
    • Definition
    • Overview
    • Logos and Disclaimers
    • State Disclaimers
    • Terms of Service and Privacy Policy
    • Signup with Facebook or Google
    • Contact Us Page
    • Limit on Debit Card Transaction
    • Limit on Wallet payout
    • Email Verification
    • Mobile Number Verification
    • Device Information
    • Email Notifications
    • Invoice
    • User Know-Your-Customer (KYC)
    • Transaction Requirements
    • Guidelines for User Account Data deletion
    • Recommendations to avoid chargebacks
    • Annexure
    • Changelog
Powered by GitBook
On this page
  • ACH
  • Debit Card

Was this helpful?

  1. Process Level Document

Payment Method

PreviousKnow Your Customer (KYC) VerificationNextRecipient Addition

Last updated 3 years ago

Was this helpful?

The Platform currently supports ACH and Debit card as payment instruments for initiating transactions. Details are as described below:

ACH

A user is required to link their bank accounts for debiting their accounts for transactions created in the system. The system currently supports over 10,000 financial institutions for ACH. The system conducts the following checks on the bank accounts:

Instant Bank Account Verification

The system uses an instant bank account verification mechanism which allows verification of user’s bank account using their internet banking credentials and MFA questionnaire as set up in their bank accounts.

Bank Account name and Sender name match

The system also matches the name of the user with the bank account name. A flag is raised in case there is any mismatch between the two names. The flag in such cases, are visible to SMP in the dashboard provided by MACHNET. SMP must monitor these flags in the dashboard before paying out such transactions.

A user is permitted to use only personal accounts for the purpose of creating transactions in the system. Use of corporate and third-party accounts must be tracked by SMP using the name mismatch flag.

Debit Card

A user can also add their debit card to initiate a transaction. Users will be required to enter their full card number, expiry date and CVV code to link their debit card in the system. The card networks supported by the system are listed in the API documents.

AVS Check for cards

We have a feature to match the address detail of a sender and the card they have added as a measure to check if the card added belongs to the sender. API clients can get a responses from the AVS check from the API. We suggest you to request delivery for transactions where the AVS code is given as Y and stop delivery for all the other responses. Enhanced DD should be conducted and client can request the delivery of such transactions manually from the dashboard. You can find the details of the AVS codes in the .

API Docs