Perform an Account Funding Transaction
Last updated: January 19, 2023
An Account Funding Transaction (AFT) is a transaction in which funds are pulled from an account and used to fund a non-merchant account. For example, to load a prepaid card, top up a wallet, or fund a person-to-person (P2P) money transfer.
The Unified Payments API can be used to perform an AFT for Visa or Mastercard.
Information
To start using this feature, please contact your Customer Success Manager.
Use the details below to set up your request.
For the full API specification, see the API reference.
post
https://api.checkout.com/payments
The processing.aft field indicates whether the payment request is an AFT, and is required for both Visa and Mastercard AFTs.
| Field name | Description |
|---|---|
| The first line of the recipient’s address. |
| The second line of the recipient’s address. |
| The recipient's city. |
| The recipient's country. |
| The recipient's state. Only applicable for US addresses. |
| The recipient's zip code. |
|
The recipient's account number can be any identifier. For example, an IBAN, internal account number, phone number or part of the PAN (the first six digits and the last four digits). |
| The recipient's first name. If the recipient is an organization, this should be the organization name. |
| The recipient's last name. If the recipient is an organization, this field is not required. |
In Europe and the UK, first_name, last_name, and account_number are mandatory for domestic European AFTs and intra-EEA/UK AFTs. This means the issuer, acquirer, and merchant are all located in the European Economic Area (EEA) or the UK.
In the US, the first_name, last_name, and address fields are mandatory for domestic AFTs.
For domestic AFTs in other jurisdictions, these fields are optional.
For cross-border AFTs, first_name, last_name, and account_number are mandatory.
The first_name, last_name, account_number, and address.country fields are mandatory globally.
| Field name | Description |
|---|---|
| The first line of the sender's address. |
| The second line of the sender's address. |
| The sender's city. |
| The sender's country. |
| The sender's state. Only applicable for US addresses. |
| The sender's zip code. |
| The sender's first name. |
| The sender's last name. |
| The merchant's unique customer ID. |
| The type of sender. For example, an individual. |
In Europe and the UK, the first_name, last_name, and address fields are mandatory for intra-EEA/UK AFTs. This means the issuer, acquirer, and merchant are all located in the European Economic Area (EEA) or the UK.
In the US, first_name, last_name, and address are mandatory for domestic AFTs.
For domestic AFTs in other jurisdictions, these fields are optional.
For cross-border AFTs, first_name, last_name, and address are mandatory.
All fields are optional in the supported jurisdictions.
Use the approved field to check whether or not the authorization was successful ("approved": true). If your authorization was not successful, it's possible the payment used an invalid/expired card, or a valid card with an insufficient available balance.
If you received a 202 response, the payment requires a redirect. For example, if the payment is 3D Secure.
Tip
The following pages can help you understand the response message:
- CVV codes and descriptions
- AVS codes
- Response codes (if the authorization was unsuccessful)
The possible values for the status field include Authorized, Captured, Card Verified, Declined, and Pending. Note that Pending only applies to 3D Secure payments.
Information
Possibly fraudulent authorization requests return the message risk.flagged: true to show that the payment has been flagged.