On this page:

Overview

An Account Funding Transaction (AFT), also known as a ‘funding transaction’ pulls funds from a card and deposits or transfers those funds into another account.

The primary use cases for AFTs are:

Funding an account owned by the same person; for example, topping up a pre-paid card or adding funds to a digital wallet account.
Funding an account owned by a different person; for example, P2P payments or pulling funds from a merchant’s card account for disbursing payroll to its employees.

The sender is the entity owning the card from which funds are pulled. The recipient is the entity receiving the funds from the AFT.

Merchants can implement AFTs using Nuvei’s server-to-server REST API, Web SDK, and Cashier integration methods.

Availability

Visa and Mastercard cards in EU, US, and Canada.
AFT-enabled merchants only.
Domestic transactions and, in selected markets, cross-border transactions (subject to approval by Visa and Mastercard per country).
Works with Sale and Auth & Settle flows.

Prerequisites

AFTs are relevant only for merchants offering funding transactions. To begin using AFTs, contact Nuvei to configure your merchant account to use this transaction type. After your account is configured, Nuvei converts your standard transactions into AFTs; however, some modifications are required to provide additional sender and recipient information.

REST API Implementation

This topic describes the steps to integrate AFTs into the standard server-to-server REST API payment flow.

Perform the Payment step.

There are two possible flows for a /payment request: 3DS or non-3DS.

As with standard transactions, AFTs fall under Strong Customer Authentication (SCA) requirements, and thus share 3DS authentication requirements.

In the relevant /payment request, the following sender and recipient details are conditionally required.

Sender Data

The merchant should include the following sender data.

Parameter	Description	Required for:
`buyerDetails.firstName`	Sender's first name	1. Cross border South Africa AFTs 2. Domestic AFTs in Colombia 3. Domestic and cross-border transactions in Nicaragua
`buyerDetails.middleName`	Sender's middle name	1. Cross-border money and non-money transfer transactions out of South Africa 2. Domestic transactions in Colombia 3. Domestic and cross-border transactions in Nicaragua
`buyerDetails.lastName`	Sender's last name	1. Cross border South Africa AFTs 2. Domestic AFTs in Colombia 3. Domestic and cross-border transactions in Nicaragua
`buyerDetails.billingAddress.address`	Street address	Cross-border and intra-EEA AFTs
`buyerDetails.billingAddress.city`	Sender’s city	Cross-border and intra-EEA AFTs
`buyerDetails.billingAddress.state`	State (required for US/Canada)	Cross border AFTs when sender country is US or Canada
`buyerDetails.billingAddress.countryCode`	Country code	Cross border AFTs
`buyerDetails.dateOfBirth`	Sender's date of birth	Cross border AFTs that fall within the below use cases: - Account-to-Account Transfers between accounts owned by the same individual (me-to-me transactions). - Adding funds to a stored value digital wallet. - P2P Money Transfers - Staged Digital Wallet [SDW] Transfers - Transactions involving Liquid Assets (like stocks, foreign currency, or cryptocurrency)

Receiver Data

The merchant should include the following receiver data.

Parameter	Description	Required for:
`recipientDetails.firstName`	Recipient's first name	All AFTs
`recipientDetails.middleName`	Recipient's middle name	1. Cross-border money and non-money transfer transactions out of South Africa 2. Domestic transactions in Colombia 3. Domestic and cross-border transactions in Nicaragua
`recipientDetails.lastName`	Recipient's last name	All AFTs
`recipientDetails.accountReference`	Reference to recipient’s account	All funding transactions
`recipientDetails.phone`	Recipient’s phone number
`recipientDetails.email`	Recipient’s email address
`recipientDetails.addressDetails.address`	Recipient's address	1. Cross-border AFTs into and out of Canada 2. Domestic AFTs in Colombia 3. Domestic and cross-border AFTs in Nicaragua 4.Cross-border AFTs sent to issuers in Australia, New Zealand and the South Pacific
`recipientDetails.addressDetails.addressLine2`	Recipient's addressLine2	1. Cross-border money and non-money transfer transactions into and out of Canada 2. Domestic transactions in Colombia 3. Domestic and cross-border transactions in Nicaragua
`recipientDetails .addressDetails.street`	Street address	All AFTs
`recipientDetails.addressDetails.zip`	ZIP/postal code	Cross-border AFTs originating from or destined to Canada
`recipientDetails .addressDetails.city`	City	1. Cross-border AFTs originating from or destined to Canada 2. Domestic AFTs in Colombia 3. Domestic and cross-border AFTs in Nicaragua
`recipientDetails.addressDetails.state`	State	All AFTs where recipient country is US or Canada
`recipientDetails.addressDetails.countryCode`	Country code	1. Cross border AFTs 2. Domestic AFTs in Colombia 3. Domestic and cross-border AFTs in Nicaragua

Sender Data (non-domestic AFTs)

For non-domestic AFTs, the merchant should include the following sender data.

Parameter Description	Parameter	Requirements
Sender first name	`firstName` under `buyerDetails`	Required on non-domestic and Europe intra-EEA AFTs.
Sender last name	`lastName` under `buyerDetails`
Sender address	`address` under `buyerdetails.billingAddress`
Sender city	`city` under `buyerdetails.billingAddress`
Sender state	`state` under `buyerdetails.billingAddress`	Required on non-domestic AFTs to/from any one of the countries on the list. See Country Codes.
Sender country	`countryCode` under `buyerdetails.billingAddress`	Required on non-domestic AFTs.
Sender date of birth	`dateOfBirth` under `buyerDetails`	Required on non-domestic money transfer AFTs. If you are not sure whether an AFT is a money transfer AFT, contact your Nuvei Account Manager.

Select the relevant flow:

3DS REST 2.0 (which contains the “first” /payment request)
Non-3DS REST 2.0 (without liability shift)

Web SDK Implementation

To integrate AFTs using Web SDK, perform the steps for the relevant Web SDK flow. See Getting Started with Web SDK 2.0 – Nuvei Documentation.

Include the recipientDetails class and its parameters in the server-side /order API request as described in the table in REST API Implementation.
For non-domestic AFTs – In the payment() request, include sender data as described in the table in REST API Implementation.

Account Funding Transactions