Account Funding Transactions

account funding transactions (aft) are required for merchants operating in specific money movement and financial services categories , as defined by card schemes for these merchants, additional data must be included in payment requests to ensure transactions are processed in line with scheme and acquirer requirements failure to provide the docid 5ol ptsgbhvgkwjwd0ghg may result in transactions being declined, flagged, or subject to additional scrutiny add the aft fields into the following integrations directly via our https //docs judopay com/api reference ( version 6 25 or later) docid\ hnglljxesinhs7ptfevtn important to consider aft requirements apply only to merchants with supported mccs for more information, see docid 5ol ptsgbhvgkwjwd0ghg these requirements are defined by the card schemes and acquirers , and apply across all supported gateways missing or invalid aft data may result in transaction declines validation errors acquirer flags to submit aft data, merchants must upgrade to judopay's transaction api version 6 25 or later for more information, see https //docs judopay com/api reference/api reference applicable merchants these requirements apply only to merchants configured with one of the following merchant category codes (mccs) merchant category code description 4829 money transfer 6012 financial institutions – money orders / foreign currency 6051 financial institutions – merchandise / services / debt repayment 6211 securities brokers / dealers 6540 stored value card purchase if your account uses one of the above mccs, you must include the aft fields described below required request fields the following request fields are used to support aft transactions field description aft indicator boolean optional optional required for aft transactions must be set to true for aft transactions businessapplicationid string optional optional identifies the type / purpose of the transaction format maximum 2 characters note if businessapplicationid is provided, aftrecipientinformation must also be provided for more information, see docid 5ol ptsgbhvgkwjwd0ghg aftrecipientinformation object optional optional required for aft transactions contains recipient details note if aftrecipientinformation is provided, businessapplicationid must also be provided for more information, see docid 5ol ptsgbhvgkwjwd0ghg business application id values the businessapplicationid defines the type / purpose of the aft transaction value description constraints aa account to account transfer accounttype must be any of the following 01 02 03 06 fd funds disbursement visa only ft funds transfer accounttype can be any of the following 00 01 02 03 06 pd payroll disbursement accounttype must be 03 tu prepaid top up accounttype must be any of the following 01 02 03 06 wt wallet funding accounttype can be any of the following 00 01 02 03 06 omitted determining the values aft is not only about providing additional fields it also requires selecting the correct values based on the transaction context when constructing a request, determine the following values based on the nature of the transaction and the destination of funds what is the purpose of the transaction? select the correct businessapplicationid where are the funds going? select the correct accounttype what identifier represents that destination? provide the correct accountid information if you are unsure which businessapplicationid accounttype accountid values to use for your transaction, contact your acquirer the correct values depend on your specific business use case, how funds are being transferred, and scheme specific rules your acquirer is responsible for confirming the appropriate configuration for your transaction scenarios select the correct business application id value the businessapplicationid must reflect the purpose of the transaction select the value that best describes the business context aa (account to account) transfers between accounts belonging to the same person ft (funds transfer) general transfers where no specific category applies fd (funds disbursement) payouts such as insurance claims ( visa only ) pd (payroll disbursement) salary or wage payments tu (top up) loading funds onto a prepaid account wt (wallet funding) funding a digital wallet select the correct account type accounttype description what to provide in accountid 00 other / unspecified account type depends on use case 01 bank account using routing number + account number routing number + account number 02 iban based bank account iban 03 card account use the card number first 6 digits (bin) + last 4 digits 06 bank account number + bic / swift account number + bic / swift business application id and account type some combinations of the businessapplicationid and accounttype are restricted by the card schemes for example pd (payroll) must use accounttype = 03 (card account) aa (account to account) must use accounttype 01, 02, 03, or 06 tu (top up) must use accounttype 01, 02, 03, or 06 ft (funds transfer) most flexible option wt (wallet funding) may allow accounttype to be omitted merchants must ensure that the selected businessapplicationid is valid for the chosen accounttype the accountid format matches the selected accounttype recipient information the following recipient details must be provided in the aftrecipientinformation object when submitting aft transactions field description firstname required required recipient’s first name addressline1 required required recipient’s address line 1 state optional optional required when countrycode is us or ca (2 character code) countrycode required required iso 3166 1 alpha 2 country code accountid required required unique identifier of the recipient account accounttype required required type of recipient account sender information (visa only) mastercard does not require sender information for aft transactions for visa aft transactions, the following sender details are required these are derived from the billingdetails object in the request field description firstname required required sender’s first name lastname required required sender’s last name addressline1 required required sender’s address countrycode required required iso 3166 1 alpha 2 country code state optional optional required when countrycode is us or ca (2 character code) putting it all together example request example aft transaction request { "aft indicator" true, "businessapplicationid" "ft", "billingdetails" { "firstname" "john", "lastname" "smith", "addressline1" "1 main street", "countrycode" "gb" }, "aftrecipientinformation" { "firstname" "jane", "addressline1" "2 high street", "countrycode" "gb", "accounttype" "03", "accountid" "123456 7890" } } field description aft indicator object optional optional this is mandatory for merchants who have an mcc code of 4829 6012 6051 6211 6540 must be set to true for aft transactions properties businessapplicationid note if businessapplicationid is provided, aftrecipientinformation must also be provided format maximum 2 characters billingdetails firstname lastname addressline1 countrycode aftrecipientinformation note if aftrecipientinformation is provided, businessapplicationid must also be provided firstname recipient’s first name addressline1 recipient’s address line 1 countrycode iso 3166 1 alpha 2 country code accounttype type of recipient account accountid unique identifier of the recipient account