Let’s take an example of a generic A2A payment provider to see how the Flagright API can be seamlessly used as the compliance and anti-fincrime infrastructure.
You can find the relevant case study here
Merchants
A Merchant is represented as Business entity in the Flagright API. Everytime a new merchant onboards to your system, you can create them at Flagright using the Create business API.
To make the following request, you’ll need an API Key. Please reach out if you don’t have one.
Users
A2A Payments providers typically do not perform KYC on end users of the application - consumer users and do not have any information on the identity of the end users. If that’s the case for your system, you don’t have to create consumer users.
In case you capture the details of the end users (consumers - individuals on either side of the transaction), you would make an API to the POST /consumer/users endpoint to create a new consumer, with the payload like so:
To make the following request, you’ll need an API Key. Please reach out if you don’t have one.
Transactions
For A2A payments, there are typically two out of the three types of transactions:
User to Merchant (U2M)
A user-to-merchant is when a user transfers money from external source (typically, Bank account) to the bank account of the merchant (Business).
For U2M, the origin payment method and the destination payment method is the bank account type. In this case, the originUserId typically would be empty, since the user originating the payment isn’t the customer of the A2A payment provider and the A2A provider typically does not have information on the user. If you perform KYC on the end user and have information on them, you can pass in the consumer userId as the originUserId
The destinationUserId would be the userId of the Merchant receiving the payment.
You would make an API call to the POST /transactions to verify this transaction before processing, with the payload like so:
To make the following request, you’ll need an API Key. Please reach out if you don’t have one.
You would make an API call to the POST /transactions to verify this transaction before processing, with the payload like:
Merchant to User - Refund
A merchant-to-user is most often used for the cases of refunds. For refunds, the merchant (Business) is the originator of the A2A payment.
For Refunds, the origin payment method and the destination payment method is the bank account type. In this case, the destinationUserId typically would be empty, since the user receiving the payment isn’t the customer of the A2A payment provider and the A2A provider typically does not have information on the user. If you perform KYC on the end user and have information on them, you can pass in the consumer userId as the destinationUserId
The originUserId would be the userId of the Merchant sending the payment.
You would make an API call to the POST /transactions to verify this transaction before processing, with the payload like so:
To make the following request, you’ll need an API Key. Please reach out if you don’t have one.
You would make an API call to the POST /transactions to verify this transaction before processing, with the payload like:
Merchant to Merchant (M2M)
In cases where you enable M2M transactions, both the originator and destination would be of Business type, with originUserId and destinationUserId being the userId of the merchants.
You would make an API call to the POST /transactions to verify this transaction before processing, with the payload like so: