Account Funding Transactions (AFT)

Account Funding Transactions (AFT) are the transferring of funds from a card account to a destination that is not the standard purchase of goods or services.

These transactions can be used for things like:

• Loading funds to a mobile wallet
• Moving funds into another financial account
• Topping up a pre-paid card
• Funding money remittance

Supported Gateways

Worldpay

In order to submit Funding Transactions to Worldpay, several GSF's must be included with your General Credit transaction. A detailed look at which fields must be included is located in our Worldpay gateway guide.

Checkout V2

To perform an AFT, you send your request with the processing.aft field set to true, along with a recipient and a sender object containing information about the transaction's sender and receiver.

A link to Checkout's documentation may be found here.

Nuvei REST

To perform an AFT, you send your request with the is_aft field set to true along with aft_recipient_first_name and aft_recipient_last_name. This will populate the recipientDetails to Nuvei. Sender details will be populated with firstName, lastName and country found in the payment method. Please reference Nuvei Rest API documentation for additional insight on AFTs.

Paysafe

Performing a Paysafe AFT will first require customers perform registration with the Card schemes in advance. Customers must contact Paysafe Support in order to receive more information and begin the registration process. This is especially important considering that not all acquirers and process support all available Merchant Category Codes (MCCs). The MCC is passed through the funding_transaction field. Passing this field to Paysafe helps them identify the Purchase or Authorization request as funding transaction that might need additional information for the purpose of a transaction. Please reference Paysafe’s API documentation for additional requirements related to this field.

For Visa Direct and Mastercard Moneysend request through GeneralCredit, first and last name are two required fields and they will the populated through the payment method.

Adyen

To perform an AFT for Adyen transactions on the legacy payment endpoint, you must include the gateway specific fields fund_source and fund_destination in your request. Below is an example of the structure of these two fields:

        "gateway_specific_fields": {
            "adyen": {
                "fund_source": {
                    "first_name": "Payer",
                    "last_name": "Name",
                    "shopper_email": "john.smith@test.com",
                    "additional_data": {
                        "fundingSource": "Debit"
                    },
                    "billing_address": {
                      "address1": "address1",
                      "address2": "address2",
                      "zip": "zip",
                      "city": "city",
                      "state": "state",
                      "country": "country"
                    }
                },
                "fund_destination": {
                    "additional_data": {
                        "walletIdentifier": "12345"
                    } 
                }
            }
        }

Please pay special attention to the camel casing of fundingSource and the walletIdentifier field names.

Credorax

To perform an AFT for Credorax transactions, you must include the gateway specific fields in your request.

    "gateway_specific_fields": {
      	"credorax": {
        	"aft": "true"
        	"sender_first_name": "firstname",
        	"sender_last_name": "lastname",
        	"sender_ref_number": "12345",
        	"sender_fund_source": "01",
        	"sender_country_code": "USA",
        	"sender_street_address": "123 street address",
        	"sender_city": "new york",
        	"sender_state": "NY",
        	"recipient_first_name": "firstname",
        	"recipient_last_name": "lastname",
        	"recipient_street_address": "321 street address",
        	"recipient_postal_code": "12345",
        	"recipient_city": "boston",
        	"recipient_province_code": "312",
        	"recipient_country_code": "USA"
      	}
    }