Account Funding Transactions

Home    _TEMP_    Account Funding Transactions

On this page:

Overview

An Account Funding Transaction (AFT) 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.

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

Availability

  • Visa Direct; Mastercard Send in the EU; other cards and markets to be supported in a future release.
  • AFT-enabled merchants only.
  • Domestic transactions and, in selected markets, cross-border transactions.
  • Works with Sale and Auth & Settle flows. For P2P payments, use our dedicated REST API method.
  • Cashier supports AFTs for wallet and fund transfers (see below).

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; you do not have to modify your existing integration.

DMN Parameters

Payment DMNs (Direct Merchant Notifications) include the following AFT-specific parameters:

  • isAFT=True or False
  • isAFTOverridden=True or False
  • recipientFirstName=RecFName
  • recipientLastName=RecLName
  • recipientAddress=RecAddress

REST API 1.0

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

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

  1. Perform the standard server-to-server REST API payment flow integration steps up to the Payment step.
  2. Perform the Payment step.
    1. In the relevant /payment request, include the recipientDetails class and its parameters.

      See recipientDetails fields in:

  • Select the relevant flow for the payment request:
    • Example of a Non-3DS /payment Request Showing the recipientDetails Class
    {
    "sessionToken":"<sessionToken from /getSessionToken>",
    "merchantId":"<your merchantId>",
    "merchantSiteId":"<your merchantSiteId>",
    "clientRequestId":"<unique request ID in merchant system>",
    "amount":"200",
    "currency":"USD",
    "userTokenId":"<unique customer identifier in merchant system>",
    "clientUniqueId":"<unique transaction ID in merchant system>",
    "paymentOption":{
        "card":{
            "cardNumber":"4000027891380961",
            "cardHolderName":"John Smith",
            "expirationMonth":"12",
            "expirationYear":"2030",
            "CVV":"217"
        }
    },
    "relatedTransactionId":"<transactionId returned from initPayment>", 
    "billingAddress":{
        "country":"US",
        "email":"[email protected]"
    },
    "deviceDetails":{
        "ipAddress":"<customer's IP address>"
    },
    "recipientDetails": {
      "firstName": "string",
      "middleName": "string",
      "lastName": "string",
      "address": "alphanumeric",
      "addressLine2": "string",
      "street": "string",
      "city": "string",
      "stateCode": "string",
      "ZIP": "string",
      "countryCode": "string",
      "phoneNumber": "string",
      "email": "string",
      "dateOfBirth": "string; YYYY-MM-DD"
      "accountNumber": "alphanumeric",
      "identificationTypeCode": "nvarchar",
      "identificationValue": "nvarchar"
    },
    "timeStamp":"<YYYYMMDDHHmmss>",
    "checksum":"<calculated checksum>"
}

    The /payment response contains:

    • isAFT – Indicates whether the transaction was processed as a Sale (False) or as an AFT transaction (True).

      /settleTransaction and /refundTransaction responses also contain isAFT, which indicates whether the original payment transaction was processed as a Sale or an AFT transaction.

    • isAFTOverriden
      • True – Merchant can submit Sales and AFT transactions.
      • False – Merchant can only submit AFT transactions.
    Example of a Non-3DS /payment Response
    {
  "internalRequestId":691376548,
  "status":"SUCCESS",
  "errCode":0,
  "reason":"",
  "merchantId":"479748173730597238",
  "merchantSiteId":"204388",
  "version":"1.0",
  "clientRequestId":"20230612095910",
  "sessionToken":"4bb43678-9d50-46a9-8980-73e2658117ee",
  "orderId":"370540478",
  "isAFT":"True",
  "isAFTOverridden": "True",
  "userTokenId":"asdadsw4",
  "paymentOption":{
    "userPaymentOptionId":"91315468",
    "card":{
      "ccCardNumber":"4****5032",
      "bin":"400002",
      "last4Digits":"5032",
      "ccExpMonth":"12",
      "ccExpYear":"25",
      "acquirerId":"19",
      "cvv2Reply":"",
      "avsCode":"",
      "cardType":"Credit",
      "cardBrand":"VISA",
      "issuerBankName":"River Valley Credit Union",
      "issuerCountry":"GB",
      "isPrepaid":"false",
      "threeD":{
        
      }
    }
  },
  "transactionStatus":"APPROVED",
  "gwErrorCode":0,
  "gwExtendedErrorCode":0,
  "issuerDeclineCode":"",
  "issuerDeclineReason":"",
  "transactionType":"Sale",
  "transactionId":"711000000023888533",
  "externalTransactionId":"",
  "authCode":"111407",
  "customData":"",
  "fraudDetails":{
    "finalDecision":"Accept"
  },
  "externalSchemeTransactionId":"",
  "orderTransactionId":1201801248
}

    4. Continue with the next relevant REST API integration steps, according to the payment flow you are implementing.

    Sender Data

    In sender data, the merchant includes the following parameters.

    Parameter DescriptionParameterRequirementsFormat
    Sender first namefirstName under billingAddressRequired on non-domestic and Europe intra-EEA AFTs.
    • 2–30 characters for both first and last name
    • A–Z, a–z, 0–9
    • Cannot contain special characters (?, @, #, $, &, *, etc.) and non-English letters
    • Cannot be all numeric
    Sender last namelastName under billingAddress
    Sender addressaddress under billingAddress
    • 2–35 characters
    • A–Z, a–z, 0–9
    • Cannot contain special characters (?, @, #, $, &, *, etc.) and non-English letters.
    • Cannot be all numeric
    Sender citycity under billingAddress
    • 2–25 characters
    • A–Z, a–z, 0–9
    • Cannot contain special characters (?, @, #, $, &, *, etc.) and non-English letters.
    • Cannot be all numeric
    Sender statestate under billingAddressRequired on non-domestic AFTs to/from any one of the countries on the list.
    See Country Codes.    		Country Subdivision Codes
    Sender countrycountry under billingAddressRequired on non-domestic AFTs.2-letter ISO country code
    Sender identification type code
  • Type of identification provided for the sender (e.g., Passport, National ID, Tax ID).
    • Valid values are:
    BTHD (Date of birth)
    CUID (Customer identification (unspecified))
    NTID (National identification)
    PASN (Passport number)
    DRLN (Driver license)
    TXIN (Tax identification)
    CPNY (Company registration number/EDRPOU)
    PRXY (Proxy identification)
    SSNB (Social security number)
    ARNB (Alien registration number)
    LAWE (Law enforcement identification)
    MILI (Military identification)
    TRVL (Travel identification (nonpassport))
    EMAL (Email)
    PHON (Phone number)    		identificationTypeCode under billingAddressRequired for:
  • Transactions out of and within Brazil
  • Domestic and cross-border transactions in Nicaragua.
  • Domestic transactions in Ukraine.
  • Domestic transactions in Colombia.
    		• nvarchar (variable-length string of Unicode characters) up to a maximum of 100 characters.
    Sender identification value
  • The actual value of the identification (e.g., passport number, ID number).
    		• identificationValue under billingAddressRequired for:
  • Transactions out of and within Brazil
  • Domestic and cross-border transactions in Nicaragua.
  • Domestic transactions in Ukraine.
  • Domestic transactions in Colombia.
  • nvarchar (variable-length string of Unicode characters) up to maximum of 100 characters
  • The value is based on the code that was sent. If the code is BTHD (date of birth), the value must contain a date of birth in the format
    ccyymmdd where:
    cc = century
    yy = year
    mm = month
    dd = day

    		•
    Sender date of birthdateOfBirth under userDetailsRequired on non-domestic money transfer AFTs. If you are not sure whether an AFT is a money transfer AFT, please contact your Nuvei account manager.Format is YYYY-MM-DD.

    Recipient Data

    In recipient data, the merchant includes the following parameters.

    ParameterDescriptionRequired for:
    recipientDetails.firstNameRecipient's first nameAll AFTs
    recipientDetails.middleNameRecipient's middle name1. 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.lastNameRecipient's last nameAll AFTs
    recipientDetails.accountNumberRecipient’s account numberAll funding transactions
    recipientDetails.phoneNumberRecipient’s phone number
    recipientDetails.emailRecipient’s email address
    recipientDetails.addressRecipient's address1. 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.addressLine2Recipient's addressLine21. 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.streetStreet addressAll AFTs
    recipientDetails.zipZIP/postal codeCross-border AFTs originating from or destined to Canada
    recipientDetails.cityCity1. Cross-border AFTs originating from or destined to Canada
    2. Domestic AFTs in Colombia
    3. Domestic and cross-border AFTs in Nicaragua
    recipientDetails.stateStateAll AFTs where recipient country is US or Canada
    recipientDetails.countryCountry code1. Cross border AFTs
    2. Domestic AFTs in Colombia
    3. Domestic and cross-border AFTs in Nicaragua
    recipientDetails.cardHolderEntityTypeIndicates if the recipient is an individual or a business.
    Values: b = Business, i = Individual    		All AFTs.
    recipientDetails.identificationTypeCode
  • Type of identification provided for the recipient (e.g., Passport, National ID, Tax ID).
  • Valid values are:
    BTHD (Date of birth)
    CUID (Customer identification (unspecified))
    NTID (National identification)
    PASN (Passport number)
    DRLN (Driver license)
    TXIN (Tax identification)
    CPNY (Company registration number/EDRPOU)
    PRXY (Proxy identification)
    SSNB (Social security number)
    ARNB (Alien registration number)
    LAWE (Law enforcement identification)
    MILI (Military identification)
    TRVL (Travel identification (nonpassport))
    EMAL (Email)
    PHON (Phone number)
    		• Required for:
  • Transactions out of and within Brazil
  • Domestic and cross-border transactions in Nicaragua.
  • Domestic transactions in Ukraine.
  • Domestic transactions in Colombia.
    		•
    recipientDetails.identificationValue
  • The actual value of the identification (e.g., passport number, ID number).
  • The value is based on the code that was sent. If the code is BTHD (date of birth), the value must contain a date of birth in the format
    ccyymmdd where:
    cc = century
    yy = year
    mm = month
    dd = day


    		• Required for:
  • Transactions out of and within Brazil
  • Domestic and cross-border transactions in Nicaragua.
  • Domestic transactions in Ukraine.
  • Domestic transactions in Colombia.
    		•

    Web SDK

    To integrate AFTs using Web SDK, perform the steps for the relevant Web SDK flow as described in Getting Started with Nuvei Web SDK.

    • For non-domestic AFTs – In the createPayment() request, include sender data.

      For sender data parameters, see Sender Data.

    • Include the recipientDetails class and its parameters in the server-side /openOrder API request.

      For recipient data parameters, Recipient Data.

    Sender Data

    In sender data, the merchant includes the following parameters.

    Parameter DescriptionParameterRequirementsFormat
    Sender first namefirstName under billingAddressRequired on non-domestic and Europe intra-EEA AFTs.
    • 2–30 characters for both first and last name
    • A–Z, a–z, 0–9
    • Cannot contain special characters (?, @, #, $, &, *, etc.) and non-English letters
    • Cannot be all numeric
    Sender last namelastName under billingAddress
    Sender addressaddress under billingAddress
    • 2–35 characters
    • A–Z, a–z, 0–9
    • Cannot contain special characters (?, @, #, $, &, *, etc.) and non-English letters.
    • Cannot be all numeric
    Sender citycity under billingAddress
    • 2–25 characters
    • A–Z, a–z, 0–9
    • Cannot contain special characters (?, @, #, $, &, *, etc.) and non-English letters.
    • Cannot be all numeric
    Sender statestate under billingAddressRequired on non-domestic AFTs to/from any one of the countries on the list.
    See Country Codes.    		Country Subdivision Codes
    Sender countrycountry under billingAddressRequired on non-domestic AFTs.2-letter ISO country code
    Sender identification type code
  • Type of identification provided for the sender (e.g., Passport, National ID, Tax ID).
    • Valid values are:
    BTHD (Date of birth)
    CUID (Customer identification (unspecified))
    NTID (National identification)
    PASN (Passport number)
    DRLN (Driver license)
    TXIN (Tax identification)
    CPNY (Company registration number/EDRPOU)
    PRXY (Proxy identification)
    SSNB (Social security number)
    ARNB (Alien registration number)
    LAWE (Law enforcement identification)
    MILI (Military identification)
    TRVL (Travel identification (nonpassport))
    EMAL (Email)
    PHON (Phone number)    		identificationTypeCode under billingAddressRequired for:
  • Transactions out of and within Brazil
  • Domestic and cross-border transactions in Nicaragua.
  • Domestic transactions in Ukraine.
  • Domestic transactions in Colombia.
    		• nvarchar (variable-length string of Unicode characters) up to a maximum of 100 characters.
    Sender identification value
  • The actual value of the identification (e.g., passport number, ID number).
    		• identificationValue under billingAddressRequired for:
  • Transactions out of and within Brazil
  • Domestic and cross-border transactions in Nicaragua.
  • Domestic transactions in Ukraine.
  • Domestic transactions in Colombia.
  • nvarchar (variable-length string of Unicode characters) up to maximum of 100 characters
  • The value is based on the code that was sent. If the code is BTHD (date of birth), the value must contain a date of birth in the format
    ccyymmdd where:
    cc = century
    yy = year
    mm = month
    dd = day

    		•
    Sender date of birthdateOfBirth under userDetailsRequired on non-domestic money transfer AFTs. If you are not sure whether an AFT is a money transfer AFT, please contact your Nuvei account manager.Format is YYYY-MM-DD.

    Recipient Data

    ParameterDescriptionRequired for:
    recipientDetails.firstNameRecipient's first nameAll AFTs
    recipientDetails.middleNameRecipient's middle name1. 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.lastNameRecipient's last nameAll AFTs
    recipientDetails.accountNumberRecipient’s account numberAll funding transactions
    recipientDetails.phoneNumberRecipient’s phone number
    recipientDetails.emailRecipient’s email address
    recipientDetails.addressRecipient's address1. 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.addressLine2Recipient's addressLine21. 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.streetStreet addressAll AFTs
    recipientDetails.zipZIP/postal codeCross-border AFTs originating from or destined to Canada
    recipientDetails.cityCity1. Cross-border AFTs originating from or destined to Canada
    2. Domestic AFTs in Colombia
    3. Domestic and cross-border AFTs in Nicaragua
    recipientDetails.stateStateAll AFTs where recipient country is US or Canada
    recipientDetails.countryCountry code1. Cross border AFTs
    2. Domestic AFTs in Colombia
    3. Domestic and cross-border AFTs in Nicaragua
    recipientDetails.cardHolderEntityTypeIndicates if the recipient is an individual or a business.
    Values: b = Business, i = Individual    		All AFTs.
    recipientDetails.identificationTypeCode
  • Type of identification provided for the recipient (e.g., Passport, National ID, Tax ID).
  • Valid values are:
    BTHD (Date of birth)
    CUID (Customer identification (unspecified))
    NTID (National identification)
    PASN (Passport number)
    DRLN (Driver license)
    TXIN (Tax identification)
    CPNY (Company registration number/EDRPOU)
    PRXY (Proxy identification)
    SSNB (Social security number)
    ARNB (Alien registration number)
    LAWE (Law enforcement identification)
    MILI (Military identification)
    TRVL (Travel identification (nonpassport))
    EMAL (Email)
    PHON (Phone number)
    		• Required for:
  • Transactions out of and within Brazil
  • Domestic and cross-border transactions in Nicaragua.
  • Domestic transactions in Ukraine.
  • Domestic transactions in Colombia.
    		•
    recipientDetails.identificationValue
  • The actual value of the identification (e.g., passport number, ID number).
  • The value is based on the code that was sent. If the code is BTHD (date of birth), the value must contain a date of birth in the format
    ccyymmdd where:
    cc = century
    yy = year
    mm = month
    dd = day


    		• Required for:
  • Transactions out of and within Brazil
  • Domestic and cross-border transactions in Nicaragua.
  • Domestic transactions in Ukraine.
  • Domestic transactions in Colombia.
    		•

    Payment Page (Cashier)

    The Payment Page (Cashier) supports AFTs for wallet and fund transfers.

    To integrate AFTs using Nuvei’s Cashier integration method, perform the steps for the relevant Cashier flow.

    Domestic AFTs have no additional requirements.

    For non-domestic AFTs – The merchant should include sender data.

    For sender data parameters, see Sender Data.

    Sender Data

    In sender data, the merchant includes the following parameters.

    Parameter DescriptionParameterRequirements
    Sender first namefirst_nameRequired on non-domestic and Europe intra-EEA AFTs.
    Sender last namelast_name
    Sender addressaddress1
    Sender citycity
    Sender statestateRequired on non-domestic AFTs to/from any one of the countries on the list.
    See Country Codes.
    Sender countrycountryRequired on non-domestic AFTs.
    Sender date of birthdateOfBirthRequired on non-domestic money transfer AFTs. If you are not sure whether an AFT is a money transfer AFT, please contact your Nuvei account manager.
    Last update iconLast modified April 2026