Account Funding Transactions (AFTs)

This page is indended for technical and product teams responsible for implementing Account Funding Transaction (AFT) integrations to ensure compliance.

Important Update: New Compliance Rules for AFTs

To comply with recent regulatory changes, all transactions classified as "Funding" must now include additional information, such as sender and receiver details, the AFT type, and other relevant data.

What's changing?

As of 31.01.2025, the parameters described in Compliance Parameters for Account Funding Transactions must be used in all "Funding" transactions.

How to build an AFT Request

Please ensure that the authorization for processing Account Funding Transactions (AFTs) is handled using the SALE operation. Additionally, we strongly recommend performing the transaction with the auto-sale option.

To initiate an AFT, submit a Register request that includes all the required parameters. The snippet below represents an example.

AFT Register request

https://test.epayment.nets.eu/Netaxept/Register.aspx?
merchantId=xxxxxx
&token=xxxxxxxxxx
&orderNumber=123456

Compliance Parameters for Account Funding Transactions

These parameters must be sent in the Register call.

Parameter	Requirement level for AFTs	Description
customerFirstName	Mandatory	Sender's first name Existing parameter https://developer.nexigroup.com/netaxept/en-EU/api/rest-v1/#netaxept-registeraspx-get-parameters-customerfirstname
customerLastName	Mandatory	Sender's last name Existing parameter https://developer.nexigroup.com/netaxept/en-EU/api/rest-v1/#netaxept-registeraspx-get-parameters-customerlastname
customerTown	Mandatory	Sender's town/city Existing parameter https://developer.nexigroup.com/netaxept/en-EU/api/rest-v1/#netaxept-registeraspx-get-parameters-customertown
customerCountry	Mandatory	Sender's country Existing parameter https://developer.nexigroup.com/netaxept/en-EU/api/rest-v1/#netaxept-registeraspx-get-parameters-customercountry
customerAddress1	Mandatory	Sender's street address Existing parameter https://developer.nexigroup.com/netaxept/en-EU/api/rest-v1/#netaxept-registeraspx-get-parameters-customeraddress1
customerPostcode	Optional	Sender's postal code Existing parameter https://developer.nexigroup.com/netaxept/en-EU/api/rest-v1/#netaxept-registeraspx-get-parameters-customerpostcode
customerState	Conditional	Sender's state New parameter String (enum, length: 2) ISO 3166-2 value without the country prefix Example: For US-CA use CA Only relevant if sender country is US or Canada.
AftInfo	Mandatory	AFT specific data New parameter Object Note: Required for all types of Account funding transactions
AftInfo.Type	Mandatory	Type of the AFT New parameter String (enum) Values: P2P - Person to person transfers (transferring funds to another individual’s non-merchant account) M2M - Me to Me transfers (both accounts are owned by the same person)
AftInfo.Purpose	Conditional	Purpose of the funding transaction New parameter String (enum) Values: FAMILY - Family Support LABOR - Regular Labor Transfers (expatriates) TRAVEL - Travel & Tourism EDUCATION - Education MEDICAL - Hospitalization & Medical Treatment EMERGENCY - Emergency Need SAVINGS - Savings GIFTS - Gifts SALARY - Salary CROWDLEND - Crowd lending OTHER - Other Required for outbound transactions sent into Chile, Columbia, Mexico, India, Bangladesh, Argentina, and Egypt.
AftInfo.Receiver	Mandatory	Data about the receiver New parameter Object
AftInfo.Receiver.FirstName	Mandatory	Receiver's first name New parameter String (max length: 64)
AftInfo.Receiver.LastName	Mandatory	Receiver's last name New parameter String (max length: 64)
AftInfo.Receiver.Account	Mandatory	Receiver's account details New parameter Object
AftInfo.Receiver.Account.Reference	Mandatory	The unique reference of the account New parameter String (max length: 50)
AftInfo.Receiver.Account.Type	Mandatory	Specifies the type of the account reference New parameter String (enum) Values: RTN_BA - Routing and transit number (RTN) + Bank account IBAN - IBAN CARD_ACCOUNT - Card Account EMAIL - Email PHONE - Phone number BAN_BIC - Bank account number (BAN) + Bank identification Code (BIC) WALLET - Wallet Id SOCIAL_NETWORK_ID - Social network Id OTHER - Other
AftInfo.Receiver.Address	Optional	Receiver's address information New parameter Object
AftInfo.Receiver.Address.Country	Optional	Receiver's country New parameter String (enum, length: 2) Receiver country according to ISO 3166-1 Alpha 2 code.
AftInfo.Receiver.Address.State	Optional	Receiver's state New parameter String (enum, length: 2) ISO 3166-2 value without the country prefix Example: For US-CA use CA Only relevant if receiver country is US or Canada.
AftInfo.Receiver.Address.City	Optional	Receiver's town/city New parameter String (max length: 25)
AftInfo.Receiver.Address.Street	Optional	Receiver's street address New parameter String (max length: 50)

Testing AFT

In the Sandbox/Test environment, AFT transactions can be sent from and tested on any test merchant. As a starting point, it si recommended to use the example AFTInfo test data under "How to build an AFT request". If you are using Postman or similar tool to send the Register request, you can use the format and sample test request below as a starting point and assign it to the parameter AftInfo . The only test card that is configured to work with AFT is Mastercard 5413000000000000 .

AFT Info test example

{"Type":"P2P","Purpose":"FAMILY","Receiver":{"FirstName":"Jane","LastName":"Hansen","Address":{"City":"Ballerup","Country":"DK","Street":"Klausdalsbrovej601"},"Account":{"Reference":"DK0000000000000000","Type":"IBAN"}}}