INTEGRATION
TRANSACTION ASSURANCE
CHARGES
DISPUTES & FRAUD
Payouts & Funding
Payouts
The Silverflow API supports payout charges, also known as push-to-card. Payout charges have a wide range of use cases, including online gaming payouts, loyalty payments, account-to-account transfers, and many others. At the moment, this endpoint can be used to perform Visa Direct and Mastercard Moneysend payments for the following use cases:
Account to account - i.e., transaction for moving money from one account to another account, both of which are owned by the sender
General funds disbursements - i.e., generic funds disbursement transaction used to push funds from a business to an individual cardholder for various purposes
Merchant disbursements - i.e., merchant payments for purchase transaction processing where the settlement payment is sent directly to a card account
Online gambling payouts - i.e., payouts of online casino winnings
Liquid assets - i.e., payouts of liquid and cryptocurrency asset proceeds, from a sale or cash out, are paid out to a card account.
Currently, other Visa Direct and Mastercard Moneysend use cases are not supported on this endpoint.
This endpoint is very similar to the standard charges endpoint, with a few additional fields required such as payoutType and sender in order to correctly process the transaction. Note that for Visa Direct payouts, there are country-specific requirements which could result in additional information being required in the payout request. Please refer to the table below for more detail on the relevant country-specific requirements.
Note that for Visa Direct payouts, there are country-specific requirements which could result in additional information being required in the payout request. Please refer to the table below for more detail on the relevant country-specific requirements.
Country | Additional data elements required | Applicable scenario |
Canada |
| Required when the cardholder or the merchant is based in Canada |
India |
| Required when the recipient is based in India |
Brazil |
| Required when the recipient is based in Brazil |
In order to create a payout transaction for both Visa and Mastercard, you are required to state the transaction use case in the authorization request message. This is indicated by the Business Application Identifier (“BAI”) for Visa Direct transactions, and Transaction Type Identifier (“TTI”) for Mastercard Send transactions. Silverflow abstracts these identifiers away from our users, and replaces them with our payoutType enums. However, it can be beneficial for our users to know exactly which transaction use cases Silverflow currently supports, as these specific BAI/TTIs have certain data input and validation requirements. Please see below table detailing Silverflow’s payoutType to BAI/TTI mappings, as well as the MCC validations in place per payoutType enum.
payoutType | Visa Direct BAI (and supported MCCs) | Mastercard Moneysend TTI (and supported MCCs) |
online-gambling | OG (7800, 7801, 7802, 7995, 9406) | C04 (7995) |
general-funds-disbursement | FD (all MCCs) | C55 (6536, 6537) |
merchant-disbursement | MD (4829, 6012) | C57 (6536, 6537) |
account-to-account | Not supported | C52 (6536, 6537) |
liquid-assets | LA (6012, 6051, 6211) | Not supported |
This endpoint requires configuration on a client basis and may be subject to additional approvals and implementation with the card schemes. Please get in touch with your Silverflow representative before integrating with this endpoint.
Funding
The Silverflow API supports funding charges. Funding charges have a wide range of use cases, including account-to-account transfers, adding funds to a digital wallet, prepaid card load or top-ups, and many others. At the moment, this endpoint can be used to perform Visa Direct funding transactions for the following use cases:
Account to account funding charges - i.e. a transaction that debits a card account for the purpose of transferring funds to an account of any type of the same consumer or organization.
General funds disbursement - i.e. a transaction used to enable a disbursement for various use cases, e.g. insurance payouts where an acquirer uses this transaction to fund the disbursement of a payout on behalf of an insurance company.
Wallet transfer funding charges - i.e. a transaction that is used for the purpose of:
adding funds to a digital wallet;
or the direct acquisition of cryptocurrency;
or the acquisition of liquid assets (for example, stocks, shares, foreign currency).
Currently, other Visa Direct and Mastercard Moneysend use cases are not supported on this endpoint.
This endpoint is very similar to the standard charges endpoint, with a few additional fields required such as fundingType and sender in order to correctly process the transaction.
Currently, this endpoint does not support other Visa Direct and Mastercard Moneysend use cases; please contact your Silverflow representative to enable additional use cases.
In order to create a funding transaction for both Visa and Mastercard, you are required to state the transaction use case in the authorization request message. This is indicated by the Business Application Identifier (“BAI”) for Visa Direct transactions, and Transaction Type Identifier (“TTI”) for Mastercard Send transactions. Silverflow abstracts these identifiers away from our users, and replaces them with our fundingType enums. However, it can be beneficial for our users to know exactly which transaction use cases Silverflow currently supports, as these specific BAI/TTIs have certain data input and validation requirements. Please see below table detailing Silverflow’s fundingType to BAI/TTI mappings, as well as the MCC validations in place per fundingType enum.
fundingType | Visa Direct BAI (and supported MCCs) | Mastercard Moneysend TTI (and supported MCCs) |
account-to-account | AA (4829, 6012, 6211) | F52 (4829, 6540) |
general-funds-disbursement | FD (all MCCs) | Not supported |
wallet-transfer | FT (4829, 6012, 6540, 6051, 6211) | Not supported |