Account Funding Transaction (AFT)

Processing Guide:
Visa Supplemental Requirements
Version 1.9

October 2021
Visa Confidential
Important Information on Confidentiality and Copyright

© 2015–2021 Visa. All Rights Reserved.

Notice: This information is proprietary and CONFIDENTIAL to Visa. It is distributed to Visa participants
for use exclusively in managing their Visa programs. It must not be duplicated, published, distributed
or disclosed, in whole or in part, to merchants, cardholders or any other person without prior written
permission from Visa.

The trademarks, logos, trade names and service marks, whether registered or unregistered (collectively
the “Trademarks”) are Trademarks owned by Visa. All other trademarks not attributed to Visa are the
property of their respective owners.

Disclaimer: Practice considerations and recommendations are provided for informational purposes
only and should not be relied upon for legal, regulatory or other advice. Practice considerations
should be independently evaluated in light of your specific business needs and any applicable laws
and regulations. Visa makes no representations and warranties as to the information contained herein
and Visa participant is solely responsible for any use of the information in this guide.

Changes and enhancements are made continuously and are communicated to Visa participants
through periodic Visa communications and as updates to this Account Funding Transaction (AFT):
Processing Guide and other related documents.

Note: This document is a supplement of the Visa Core Rules and Visa Product and Service Rules. In
the event of any conflict between any content in this document, any document referenced herein, any
exhibit to this document, or any communications concerning this document, and any content in the
Visa Core Rules and Visa Product and Service Rules, the Visa Core Rules and Visa Product and Service
Rules shall govern and control.
 Contents
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Contents

Tables .............................................................................................................................................................................. iii

Figures ............................................................................................................................................................................ iii
Acronyms ......................................................................................................................................................................... 1
About this Guide ........................................................................................................................................................... 3
Audience and Scope ................................................................................................................................................................ 3
Summary of Changes in this Version ................................................................................................................................ 4
Related Publications................................................................................................................................................................. 4
1 Account Funding Transaction (AFT) Overview .............................................................................................. 6
1.1 Comparison of AFTs with Purchase and Quasi Cash Transactions .............................................................. 9
2 Requirements and Considerations for AFT Origination ............................................................................ 13
2.1 AFT Program Business Requirements ................................................................................................................... 13
2.1.1 Requirements for submitting a PIF................................................................................................................. 15
2.2 AFT Processing Requirements and Considerations ......................................................................................... 15
2.2.1 AFT Processing and Message Format ........................................................................................................... 15
2.2.1.1 Business Application Identifier (BAI) ........................................................................................................ 16
2.2.1.1.1 P2P Digital Payment Platform (DPP) Framework ............................................................................. 19
2.2.1.1.2 Bank-Initiated P2P Money Transfer – Use Case ............................................................................... 22
2.2.1.1.3 Cryptocurrency – Use Case ...................................................................................................................... 23
2.2.1.2 Merchant-initiated transactions/Recurring transactions .................................................................. 23
2.2.1.3 Restrictions on Cross-Border AFTs ........................................................................................................... 24
2.2.2 Key AFT Data Elements ....................................................................................................................................... 25
2.2.2.1 Custom Payment Service (CPS) (U.S only).............................................................................................. 25
2.2.3 Acquirer, Service Provider, and Merchant Network Routing Options .............................................. 26
2.2.3.1 VisaNet Connectivity Using ISO Messaging .......................................................................................... 26
2.2.3.2 Application Programming Interfaces (APIs) .......................................................................................... 26
2.2.3.2.1 API Terms of Use .......................................................................................................................................... 27
2.2.3.3 Push Payment Gateway Service (U.S. Only) ........................................................................................... 27
2.2.3.4 AFTs for Proprietary Card Products .......................................................................................................... 28
2.2.4 Transaction Coding at Remote Channels (CEMEA) .................................................................................. 28

21 October 2021 Visa Confidential i

 Contents
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

2.3 AFT Program Customer Requirements and Considerations ........................................................................ 28

2.4 AFT Risk Requirements and Considerations....................................................................................................... 29
2.4.1 Risk Management—General Considerations .............................................................................................. 29
2.4.2 Cardholder Data Authentication Requirements ........................................................................................ 30
2.4.3 Transaction Monitoring and Screening ........................................................................................................ 30
2.4.4 Fraud Detection and Prevention ..................................................................................................................... 31
2.4.5 Push Payments Tokenization ............................................................................................................................ 32
2.4.6 Real Time Visa Account Updater (VAU) ........................................................................................................ 33
2.4.7 Data Security—PCI Compliance....................................................................................................................... 33
2.5 AFT Refund Use Case .................................................................................................................................................. 34
2.6 AFT Reporting Requirements for Originating Entities .................................................................................... 36
2.7 AFT Certification Requirements............................................................................................................................... 36
3 Issuer Requirements and Considerations ..................................................................................................... 37
3.1 Receiving and Processing AFTs ............................................................................................................................... 37
3.2 Risk and Disputes for Issuers ................................................................................................................................... 38
3.2.1 Using Visa Velocity Limit Checking to Mitigate Risk ............................................................................... 38
3.2.2 Issuers – Dispute Resolution ............................................................................................................................. 39
3.2.3 AFT Refund – Processing Considerations .................................................................................................... 40
3.3 Issuer Reporting Requirements ............................................................................................................................... 40
3.4 Issuer Certification Requirements .......................................................................................................................... 41
A AFT Data Elements and Processing Rules .................................................................................................... 42
B BAI Acronyms and Glossary ............................................................................................................................. 68
B.1 Business Application Identifier (BAI) Acronyms ................................................................................................ 68
B.2 Glossary ............................................................................................................................................................................ 69

ii Visa Confidential 28 October 2021

 Figures
Account Funding Transaction (AFT): Processing Guide

Tables

Table 1-1: Comparison of AFTs with Purchase and Quasi Cash Transactions .................................................. 9
Table 2-1: AFT Categories .................................................................................................................................................. 17
Table 2-2: BAI and MCC usage for P2P and Digital Wallet Programs ............................................................... 20
Table 2-3: Digital wallets comparison ........................................................................................................................... 21
Table 2-4: Visa Developer Platform (VDP) APIs ......................................................................................................... 27
Table 2-5: Reversal and Adjustment transactions overview.................................................................................. 34
Table 3-1: AFT Velocity Limits........................................................................................................................................... 38
Table 3-2: Examples of AFT Dispute Situations.......................................................................................................... 39
Table 3-4: Glossary................................................................................................................................................................ 69

Figures

Figure 1-1: AFT “Pull” Transaction with Subsequent “Push” Transaction ............................................................ 7
Figure 1-2: AFT “Pull” Transaction for Wallets/Account.................................................................................................. 8

21 October 2021 Visa Confidential iii

 Acronyms
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Acronyms

The table below contains a list of AFT-related acronyms.

Acronyms Meaning

AA Account-to-Account or me-to-me (Money Transfer BAI)

AFT Account Funding Transaction

API Application Programming Interface

AVS Address Verification Service

BAI Business Application Identifier

BI Bank Initiated P2P (Money Transfer BAI)

BIN Bank Identification Number

CVV2 Card Verification Value 2

DEX Direct Exchange

DPP Digital Payment Platform

EEA European Economic Area

FRS Fraud Reporting Service

FT Funds Transfer (Stored Value Digital Wallet)

IREET Issuer Requirement to Evaluate Each Transaction

MCC Merchant Category Code

MP Merchant Payment

MVV Merchant Verification Value

OCT Original Credit Transaction

PAN Primary Account Number

PCI DSS Payment Card Industry Data Security Standard

PIF Program Information Form

PP Person-to-Person or Peer-to-Peer

PPGS Push Payment Gateway Service

P2P Same as PP

2 October 2021 Visa Confidential 1

 Acronyms
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Acronyms Meaning

SDW Staged Digital Wallet

SDWO Staged Digital Wallet Operators

SMS Single Message System (part of VisaNet V.I.P.)

SVDW Stored Value Digital Wallet

TCQ Transaction Code Qualifier

TU Top Up (Prepaid Load)

VAA Visa Advanced Authorization

VAU Visa Account Updater

VCMS VisaNet Certification Management Service

VDP Visa Developer Platform

VOL Visa Online

VRM Visa Risk Manager

VSS VisaNet Settlement Service

VTA Visa Transaction Advisor

WT Wallet Transfer (Staged Digital Wallets only)

WTMO Wire Transfer Money Orders

2 Visa Confidential 28 October 2021

 About this Guide
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

About this Guide

The Account Funding Transaction (AFT) is a transaction where funds are pulled from a Visa account
and are subsequently used to fund another Visa or non-Visa account. When an AFT is used
independently to fund another Visa or non-Visa account, AFTs must only be used to fund an account
belonging to the same individual or entity holding the Visa account from which the funds have been
pulled; for example, AFTs can be used for loading or topping up prepaid card accounts, moving funds
into another financial account such as a savings deposit account, acting as a funding source for
person-to-person (P2P) Money Transfers, or loading third-party digital wallets.

This document provides:

• An overview of the AFT
• AFT requirements and guidelines for acquirers
• Program considerations for acquirers, service providers, and merchants
• Processing guidelines and best practices for issuers

Audience and Scope

The Account Funding Transaction (AFT): Processing Guide is intended for use by Visa financial
institutions and financial institution partners (such as third party agents sponsored by a Visa client
financial institution) involved with originating or receiving AFTs.

This document provides Visa acquirers, service providers, and merchants with technical requirements,
guidelines, and considerations to support the origination of AFTs, including data element
requirements.1

It provides Visa issuers with technical guidelines, Visa reporting requirements, and best practices to
support the processing and authorization of AFTs.

This document includes some information related to the use of funds transfer programs, however, full
details about implementing a funds transfer program combining AFTs and Original Credit Transactions
(OCTs) are outside the scope of this document. For more information about Visa Direct and OCT-
based programs, see the Visa Direct Original Credit Transaction: Global Implementation Guide.

1 In this document, entities originating AFTs are now referred to as acquirers, merchants, or service providers and Visa
financial institutions receiving AFTs are referred to as issuers. The term originators have been replaced by the terms acquirers,
merchants, and service providers, as applicable, throughout the guide.

2 October 2021 Visa Confidential 3

 About this Guide
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Summary of Changes in this Version

This version of the Account Funding Transaction (AFT): Processing Guide contains updates for the
following topics. Changes also include minor edits and modifications for clarity and accuracy of rules.
Principal changes are highlighted in the Guide with underscored text.
Table 1: Version 1.6 Summary of Changes

Chapter No. Section Status Description

Chapter 1 Account Funding Update • Added an effective date for AFT support
Transaction mandate in Europe region for existing
Overview merchant programs.
• Additional clarity provided to reinforce the
requirement that AFTs must only be used
independently for me-to-me money transfer
transactions.
Chapter 2 Custom Payment New • Added a new section to describe the Custom
Service (CPS) Payment Service (CPS) and the qualification
(U.S only) criteria for CPS/AFTs.
• Additional clarity provided on using a reversal,
instead of, an adjustment transaction for an
AFT Refund.
• Added clarity to the MCCs for FT BAI to align
with the Digital Payment Platform (DPP)
framework.
Chapter 3 Using Visa Update • Updated velocity limits for domestic non-
Velocity Limit money transfer AFTs and cross-border AFTs.
Checking to
Mitigate Risk
Appendix A AFT Data Update • Updated the AFT Data Elements table to add
Elements and Field 104 Sender Data fields relevant to AFTs.
Processing Rules

Related Publications
The current versions of these documents are available on Visa Online (www.visaonline.com ) or
through your Visa representative:
• Visa Direct Original Credit Transaction: Global Implementation Guide
• Push Payment Gateway Client Implementation Guide
• Visa Core Rules and Visa Product and Service Rules
• V.I.P. System BASE I Technical Specifications, Volume 2
• V.I.P. System SMS POS (VISA & VISA Electron) Technical Specifications, Volume 2
• Fraud Reporting System (FRS) User's Guide
• Global Visa Acquirer Risk Quick Reference Guide
• Global Visa Acquirer Fraud Control Manual
• April 2021 Global Technical Letter and Implementation Guide, Articles 3.2, 11.2.12

4 Visa Confidential 28 October 2021

 About this Guide
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

• April 2020 Global Technical Letter and Implementation Guide, Articles 2,3, 4.8, 8.1.2, 7.4.1, 10.1.1
• October 2019 Global Technical Letter and Implementation Guide, Article 2.11
• April 2019 Global Technical Letter and Implementation Guide, Article 3.4
• October 2018 Global Technical Letter (Business Enhancement Release (BER)), Articles 3.4, 3.14
• October 2017 Global Technical Letter and Implementation Guide, Articles 2.12, 2.15, 11.2.1

2 October 2021 Visa Confidential 5

 Account Funding Transaction (AFT) Overview
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

1 Account Funding Transaction (AFT) Overview

The Account Funding Transaction (AFT) is a transaction where funds are pulled from a Visa account
and are subsequently used to fund another Visa or non-Visa account. When used independently to
fund another Visa or non-Visa account, AFTs must only be used to fund an account belonging to the
same individual or entity holding the Visa account.

The AFT must be processed with the Account Funding Transaction indicator and the correct Business
Application Identifier (BAI) in the authorization and clearing record.

Important: An AFT is not intended for payment of goods and services, funding a merchant account,
or for debt repayment. An AFT can be used to fund the Original Credit Transaction (OCT)
in a Scan to Pay purchase.

Effective 18 April 2020 the following is a requirement:

• An AFT must be used to load or top up Prepaid card account where the funding account belongs
to the same individual or entity holding the Visa account that is being funded.

• An AFT2 is the required pull transaction to be used to fund the following scenarios in a card not
present environment:
o Disbursement of funds from Visa Corporate cards, Visa Business Debit cards, or Visa Business
Check cards (example: payroll)
o Funding a person-to-person account (P2P) Money Transfer via a subsequent transaction
(example funding an OCT, bank transfer etc.)
o Moving funds from one account to another (A2A) (example funding a checking account,
savings deposit, or retirement account) where the funding account belongs to the same
individual or entity holding the account.
o Pre-fund a consumer’s digital wallet* (except single-merchant digital wallet) to subsequently
be used for purchases or money transfers where the funding account belongs to the same
individual or entity holding the wallet account.

* When a Visa card is used to fund a registered Staged Digital Wallet3, an AFT with a BAI of Wallet
Transfer (WT) must be used. BAI = WT is used only for Staged Digital Wallets, and in the following
circumstances:

2 Effective dates in Europe –

• 23 April 2022: All merchant programs are required to comply.
• 18 October 2020: Prepaid card load/reload.
3 Contact your Visa representative for additional information and requirements on digital wallets. For further information on

the requirements that apply to digital wallet transactions, visit the Staged Digital Wallet Operators (SDWO) section at Visa
Online (VOL).

6 Visa Confidential 21 October 2021

 Account Funding Transaction (AFT) Overview
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

• In AFTs when funding a digital wallet before the cardholder makes a purchase
• To fund a purchase when initiated by the digital wallet provider and corresponding to, or
otherwise directly connected to a specific purchase (also called Back-to-Back funding purchase
or live-load/real-time). In this scenario, the transaction must be processed as a purchase
transaction, with a BAI value = WT
Note: AFT support is mandated for issuers in U.S, Canada, and CEMEA regions. Effective 15 October
2022, AFT support will be required in the Europe region.

As shown in Figure 1-1, a cardholder uses an existing access channel (ATM, mobile app, etc.) to initiate
a transaction through an acquirer, service provider, or merchant. The acquirer, service provider, or
merchant sends the AFT message to VisaNet. Once the AFT is authorized and executed, the funds are
available and can be pulled from the sender’s account and pushed to a specified receiving account,
such as another Visa card, another network payment card, other non-merchant account, a wallet, or a
prepaid card.
Figure 1-1: AFT “Pull” Transaction with Subsequent “Push” Transaction

21 October 2021 Visa Confidential 7

 Account Funding Transaction (AFT) Overview
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Figure 1-2: AFT “Pull” Transaction for Wallets/Account

In the case of a person-to-person or account-to-account Money Transfer, the AFT can be paired with
an OCT that pushes funds to an eligible Visa card account. For more information about the OCT, refer
to the Visa Direct Original Credit Transaction: Global Implementation Guide.

Appropriate processing of AFTs is critical to ensure that cardholders are able to perform the
transactions they expect with their Visa cards.

8 Visa Confidential 21 October 2021

 Account Funding Transaction (AFT) Overview
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

1.1 Comparison of AFTs with Purchase and Quasi Cash Transactions

An AFT is a type of purchase transaction. Table 1-1 summarizes the differences between an AFT, quasi
cash, and general purpose purchase transactions.
Table 1-1: Comparison of AFTs with Purchase and Quasi Cash Transactions

Purchase Quasi Cash

Account Funding Transaction
Transaction
Business Definition A transaction that pulls funds from A transaction that A transaction that
Description: any Visa account with the intent of moves funds from pulls funds for the
funding a non-merchant account. any Visa account purchase of an item
AFTs when used independently to to fund a merchant that is representative
fund another Visa or non-Visa account. of actual cash or a
account must only be used to substitution for cash.
fund an account belonging to the It can easily convert
same individual or entity holding to cash.
the Visa account.
Examples • Account-to-account Money Any purchase of Examples of Quasi
Transfer goods and services cash purchases
• Person-to-person Money from a merchant; include:
Transfer examples include: • Gambling chips
• Prepaid card top-up • Traditional • Travelers checks
• Adding value to a digital goods and • Foreign currency
wallet services • Lottery tickets
• Funding for funds • Bill payments • Money Orders
disbursements, e.g. Pulling • Debt •
from a business debit to fund repayment
payroll OCTs. • Donations
• Gift card
purchase
• Closed-loop,
merchant-
specific
accounts (e.g.,
Starbucks app)

21 October 2021 Visa Confidential 9

 Account Funding Transaction (AFT) Overview
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Purchase Quasi Cash

Account Funding Transaction
Transaction
Risk • Use existing authorization • Use existing • Use existing
Management tools; CVV2, AVS, Visa Secure, authorization authorization
etc. tools; CVV2, tools; CVV2,
• Authorize and make approval AVS, Visa AVS, Visa
decisions using standard Secure, etc. Secure, etc.
decline reason codes • Authorize and • Authorize and
• Apply new or existing make approval make approval
spending limits and decisions decisions using
monitoring using standard standard decline
• Restricted to domestic-only4 decline reason reason codes
AFTs except WT. AFTs with BAI codes • Apply new or
WT can be cross-border • Apply new or existing
• Include Velocity limits to existing purchase limits
mitigate possible fraud and purchase limits and monitoring
money laundering risk if the and
subsequent OCT is a money monitoring
transfer transaction
Pricing Existing AFT rates apply Existing purchase Existing purchase
rates apply rates apply
Data Processing 10 00 11
Elements: Code
Transaction 05 05 05
Code
Tran Code 1 0 0
Qualifier
Business • AA (account-to-account) WT is used in WT is used in
Application • BI (Financial institution- Purchase Purchase
Identifier initiated person-to-person) transactions for transactions for
(BAI) • FT (funds transfer) Staged Wallet Staged Wallet
• MP (merchant payment for transactions transactions.
scan-to-pay programs only)
• PP (person-to-person)
• TU (prepaid top-up)
• WT (wallet transfer)
• FD (funds disbursement)
• PD (payroll disbursement)

4 In Europe, AFTs in the EEA and UK (and Gibraltar, where relevant) are considered domestic.

10 Visa Confidential 21 October 2021

 Account Funding Transaction (AFT) Overview
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Purchase Quasi Cash

Account Funding Transaction
Transaction
Eligible MCCs Depends on BAI: All except MCC All except MCC 6010
• For AA, use MCC 4829, 6012, 6010 and 6011 and 6011
or 6211 (In the U.S., MCC 4829
is not applicable with BAI AA)
• For BI, use MCC 6012
• For FT, use the MCC based on
use case5
• For MP, use MCC 6012 or the
value of the MCC embedded
in the QR code
Note: This BAI is for scan-to-
pay programs only.
• For PP, use MCC 4829 or 6012
• For TU, use MCC 6012, 6540
or 6051
• For WT, use MCC 60515
• For FD, use the MCC
associated with the
appropriate merchant.
• For PD, use the MCC
associated with the
appropriate merchant.
Merchant Merchant name is required in all Merchant Merchant
Name Field6 transactions.
• For Money Transfer, the
format should be
Merchant*recipient name
i.e. ABCD*Alex Miller
• For Funds Disbursements
and Wallets, the format
should be Merchant or
Wallet name
Note: Recipient Name is not
required for wallets (WT and FT) ,
prepaid top ups (TU) and Funds
disbursement (FD and PD)
transactions but a Merchant Name
must be included.

5 If the funds will be used for a High-Brand Risk Transaction, use the applicable high-brand risk MCC.
6 Will be used by issuers on the cardholder’s statement.

21 October 2021 Visa Confidential 11

 Account Funding Transaction (AFT) Overview
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

12 Visa Confidential 21 October 2021

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

2 Requirements and Considerations for AFT Origination

The entity that offers a service utilizing an AFT may be a Visa acquirer, merchant, or service provider,
sponsored by a Visa acquirer. This chapter discusses the requirements and considerations that
acquirers, service providers, or merchants should take into account when planning an AFT program.

2.1 AFT Program Business Requirements

The following requirements apply to AFT programs.

Acquiring Relationship

All AFT origination programs require a relationship with a Visa acquirer. A Visa client with a Visa
acquiring license must act as the originating entity or must sponsor a third party agent that acts as the
originating entity. The Visa acquirer will take all liability and responsibility for AFT origination
programs operated using their Visa acquiring identifier.

Licensing and Registration

Acquirers and their agents must ensure that all necessary licenses, registrations, notifications,
authorizations, and approvals necessary to engage in acquiring services, are obtained from the
appropriate authorities in the originating entity’s local jurisdiction.

Third Party Agent Registration

Acquirers partnering with a third party for AFT origination services must register the third party as an
agent with Visa if it performs any of the following activities:
• Stores, processes or transmits cardholder information
• Manages or has access to funds related to the AFT origination services
• Solicits other entities (e.g., service provider, merchants, corporate clients, government entities, other
businesses, etc.) for AFT origination programs or services

Review the Third Party Agent Registration Program page on www.visa.com to better understand the
TPA program.

Contact your Visa representative for more information.

Note: Acquirers that contract with third party agents are fully responsible for all activities associated
with the Visa programs.

21 October 2021 Visa Confidential 13

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Transaction Usage

AFTs cannot be used for the purchase of goods or services or with the intention of transferring funds
to a merchant account.

AFTs are the required transaction to load or top up prepaid cards in all regions. An AFT is the required
pull transaction to be used for disbursing payroll funds, P2P or me-to-me transactions, and pre-
funding a consumer’s digital wallet, in a card not present environment. When used independently to
fund another Visa or non-Visa account, AFTs must only be used to fund an account belonging to the
same individual or entity holding the Visa account.

Usage Monitoring—Origination

Monitoring must be in place to ensure that AFTs are not used for the purchase of goods and services.
Acquirers, service providers, and merchants can accomplish this by monitoring a variety of factors,
including:
• Transaction size
• Transaction frequency
• Number/variety of senders to a single receiving account

Fraud Reporting

As with all purchase transactions, AFT fraud is required to be reported to the Visa Fraud Reporting
System (FRS) as specified in the Fraud Reporting System (FRS) User's Guide.

Disputes

AFTs have the same dispute rights as purchase transactions outlined in the Visa Core Rules and Visa
Product and Service Rules.

Visa Direct Program Approval

All Visa Direct AFT origination programs must be approved by Visa prior to program launch. Acquirers
must obtain approval by completing the Visa Direct—Program Information Form (PIF). A PIF is
required for all new Visa Direct programs and for any updates or changes to existing Visa Direct
programs; for example, change in acquirer, acquiring identifier, participants, or program types.

Refer to Visa Direct Program Approval Process on Visa Online for more information on the approval
process and accessing PRM.

14 Visa Confidential 21 October 2021

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

2.1.1 Requirements for submitting a PIF

A new PIF must be submitted in the following situations:

• For programs using AFT-only transactions.

• Initiating a new Visa Direct program type7 or BAIs not indicated in a prior PIF.

• Any updates or changes to existing Visa Direct programs that were previously approved,
including adding or changing acquiring identifiers, program types or use cases, addition of
cross-border countries.

• For Funds Disbursement/non-Money Transfer services, an acquirer, service provider, or

merchant offering multiple Visa Direct program types is not required to submit a separate PIF
for each new merchant on-boarded to the service, as long as all other information in the PIF is
consistent between service offerings.

Note: Online Gambling (OG) and Gambling Payouts (GP) are excluded from this category and
are not funded using an AFT.

• For Money Transfer programs such as Account-to-Account (AA), Person-to-Person (PP), Funds
Transfer (FT), and Wallet Transfer (WT), a new PIF is required for every new merchant
origination program.

• For high-risk programs, such as cryptocurrency wallet programs (FT), a new PIF is required for
every new merchant origination program.

2.2 AFT Processing Requirements and Considerations

This section outlines the transaction processing and AFT message format requirements for originators.

2.2.1 AFT Processing and Message Format

Since the AFT is a type of purchase transaction with a different processing code, the message
requirements for a purchase transaction also apply; e.g., an AFT used in an e-commerce environment
follows the requirements for an e-commerce transaction.

Key data elements for the AFT message are detailed in Appendix A: AFT Data Elements and Processing
Rules.

7A program is defined as product or service being offered by an acquirer, service provider, or merchant. Visa defined
Program Types are listed in Table 2-1.

21 October 2021 Visa Confidential 15

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Originating entities can use a unique or an existing acquiring identifier for AFTs. AFTs must be
processed as purchase transactions using the unique AFT processing code 10. They must be cleared
for the same amount approved in the authorization8. AFTs can be processed in dual or single message
formats.

Processing Changes

Issuers in the AP, CEMEA, LAC, and Europe Regions must be aware that Visa has implemented changes
to convert AFTs with the processing code 10 (Account Funding) to a purchase transaction with the
processing code 00 (Goods/Service purchase–debit) prior to sending the transaction to issuers that are
not enabled to receive/have opted not to process the AFT processing code. AFTs converted to
purchase will include a Business Application Identifier in Field 104 based on Core configuration. Refer
to Appendix A: AFT Data Elements and Processing Rules for more information on the data elements for
Field 104.

AFTs within Europe are classified as domestic by Visa provided merchant, acquirer, and issuer are all in
the European Economic Area9 (EEA) or UK (or Gibraltar, where relevant). This allows merchants with a
license in one EEA country or UK (or Gibraltar, where relevant) to initiate an AFT from another EEA
country or UK (or Gibraltar, where relevant) where the merchant has passported their license.

2.2.1.1 Business Application Identifier (BAI)

The Business Application Identifier (BAI) is a data element used to identify the category of the AFT. The
BAI helps the issuer of the sender’s Visa account understand the purpose of the funds, enabling better
risk assessment, authorization decisions, and accurate accrual of any cardholder rewards or loyalty
point. The BAI is specified in Field 104, Usage 2, Dataset Value Hex 57 (see Appendix A: AFT Data
Elements and Processing Rules).

All acquirers, service providers, and merchants in all regions are required to submit a valid BAI value in
AFTs. Refer to Table B-: Business Application Identifier (BAI) Acronyms in this guide. In addition, full AFT
specifications can be found in the V.I.P. System BASE I Technical Specifications, Volume 2 and V.I.P.
System SMS POS (VISA & VISA Electron) Technical Specifications, Volume 2.

Table 2-1 summarizes AFT categories, their BAIs, corresponding MCCs, and regional usage
requirements.

8 AFT with BAIs WT and TU can be cross-border. The authorization/clearing amount could be different due to foreign
exchange.
9 European Economic Area (EEA), which includes the member states of the European Union, and Iceland, Liechtenstein and

Norway. Member states include Austria, Belgium, Bulgaria, Croatia, Republic of Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal,
Romania, Slovakia, Slovenia, Spain, Sweden.

16 Visa Confidential 21 October 2021

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Table 2-1: AFT Categories

Merchant Category Code BAI Usage Requirements
BAI AFT Category
(MCC)
Money Transfer
AA Account-to-account • 4829 Non-Financial Institution Used in a me-to-me Money
Money Transfer Wire Transfer Money Orders Transfer transaction, both
(funding of the (Not applicable in the U.S. with accounts are owned by the same
BAI AA)
cardholder’s own account cardholder.
at the same or a different • 6012 Financial Institutions –
financial institution) Merchandise and Services
• 6211 - Brokerage
BI Financial Institution- 6012 Financial Institutions – P2P Money Transfer is initiated
offered Bank-Initiated P2P Merchandise and Services from an online banking system,
Money Transfer making it a bank-initiated
Important: BAI BI is used transaction.
for very specific scenarios Note: BAI BI should only be used
and is enabled only in in combination with MCC 6012.
limited markets. Contact
your Visa Representative
for information on the
availability of BAI BI in your
market, and applicability of
BAI BI to your program
FT Funds Transfer • 4829 Non-Financial Adding funds to or cashing out a
Institution Wire Transfer Stored Value Digital Wallet
Money Orders (WTMOs) (SVDW) account.
• 6012 Financial Institutions – Funding a Money Transfer where
Merchandise and Services the OCT is not enabled as the
push mechanism to the recipient.
• 6540 Non-Financial
Institutions – Stored Value
Card Purchase/Load
• If the funds will be used for
a High-Brand Risk
Transaction, the applicable
high-brand risk MCC must
be used.
• If the wallet is able to be
used to purchase non-fiat
currency (for example:
cryptocurrency), the
applicable special condition
indicator must be used.

21 October 2021 Visa Confidential 17

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Merchant Category Code BAI Usage Requirements

BAI AFT Category
(MCC)
PP Person-to-person (P2P) • 4829 Non-Financial This is applicable for services that
Money Transfer Institution Wire Transfer support both AFT and OCT. If
(transferring funds to Money Orders only AFT is supported, BAI FT
another individual’s non- • 6012 Financial Institutions – must be used.
merchant account) Merchandise and Services
WT Staged Digital Wallet • 6051 Non-Financial Note: When a Visa card is used
(SDW) transfer Institutions – Foreign to fund a Staged Digital Wallet
(adding value to a digital Currency, Non-Fiat Currency before the cardholder makes a
wallet with a proprietary (example, Cryptocurrency), purchase, an AFT with a BAI of
merchant acceptance Money Orders (not Money WT must be used. WT must be
network) Transfer), Account Funding used only by registered Staged
(not Stored Value Load), Digital Wallet Operators (SDWO).
Travelers Cheques, and For additional information on
Debt Repayment Staged Digital Wallet
• If the funds will be used for transactions, visit the Staged
a High-Brand Risk Digital Wallet Operators section
Transaction, the applicable at Visa Online (VOL). Contact
high-brand risk MCC must your Visa representative for
be used. additional information and
• If the wallet is able to be requirements for digital wallets.
used to purchase non-fiat
currency (for example:
cryptocurrency), the
applicable special condition
indicator must be used.
Funds Disbursement/Non-Money Transfer
FD Funds Disbursement Any MCC associated to the Insurance payouts where a third
merchant party uses an AFT to fund the
disbursement of OCT on behalf
of the insurance company.
MP Merchant Payment • Value of the MCC This is used in context of Mobile
Note: embedded in the QR code, Push Payment Transactions
Available or (Merchant Payment/Scan to Pay)
for use in • 6012 Financial Institutions – where AFT service is called for
limited Merchandise and Services the purpose of funding the OCT
markets (default code) transaction with “MP” BAI.
only. MCC value should be captured
when Consumer scans the QR
Code. If the value of MCC is not
embedded in QR Code, the
default code (6012) should be
used.

18 Visa Confidential 21 October 2021

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Merchant Category Code BAI Usage Requirements

BAI AFT Category
(MCC)
PD Payroll Disbursement 8931 Accounting, Auditing and When a payroll provider is
Bookkeeping services including disbursing payroll on behalf of
Payroll the small business who funds the
transactions.
TU Prepaid card load or top- • 6012 Financial Institutions – Note: Merchants that sell other
up Merchandise and Services goods and services in addition to
(adding value to an eligible • 6051 Non-Financial stored value cards and offer
reloadable prepaid card) Institutions – Foreign prepaid card load capability can
Currency, Non-Fiat Currency use the MCC associated with the
(example, Cryptocurrency), merchant’s primary business in
Money Orders (not Money accordance with the Visa
Transfer), Travelers Merchant Data Standards
Cheques, and Debt Manual.
Repayment
• 6540 Non-Financial
Institutions – Stored Value
Card Purchase/Load

2.2.1.1.1 P2P Digital Payment Platform (DPP) Framework

Person-to-Person Digital Payment Platforms are a digital payment solution to facilitate movement of
funds between the sender’s accounts, or from the sender to another individual’s account. This
platform also enables payments to merchants for goods/services purchased through the wallet.

To clearly distinguish types of Money Transfers in the P2P DPP Framework, accurate BAI coding is
critical. This helps ensure:
• Implementing the right economics
• Managing risks: arbitrage, fraud, money laundering, etc.
• Maintaining compliance and transparency across all parties in the payments chain
• Taking into account a variety of emerging and evolving digital payment platform business models

Note: Single merchant wallets (where stored funds cannot be used outside the single merchant’s
environment) are not included in SDW and SVDW.

The table below maps out the different P2P digital payment business models and provides guidance
to acquirers and merchants on the proper use of transaction type, MCC and BAI coding to facilitate
the movement of funds.

21 October 2021 Visa Confidential 19

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Table 2-2: BAI and MCC usage for P2P and Digital Wallet Programs

Digital Payment Platform Model

Straight- Financial Stored-value
Staged wallet
through P2P Institution wallet
MCCs • 4829 • 6012 • 4829 • 6051
• 6012 (if bank- • 6211 • 6540 • Merchant’s
offered) • 6051 • 6012 (if bank- MCC if High-
offered) Risk or
Use cases • Merchant’s otherwise
MCC if High- Back-to-Back
Risk funding

If the wallet is If the wallet is

able to be used able to be used
to purchase to purchase
non-fiat non-fiat
currency (for currency (for
example: example:
cryptocurrency), cryptocurrency),
the applicable the applicable
transaction transaction
indicator must indicator must
be used. be used.

Me-to-me funding/adding cash N/A AFT (AA) AFT (FT) AFT (WT)

Me-to-me withdrawal/ Cash out N/A OCT (AA) OCT (FT) OCT (WT)

OCT not enabled AFT (FT) AFT (FT) AFT (FT) AFT (WT)
Send funds to
someone else
OCT enabled AFT (PP or BI) AFT (PP or BI) AFT (PP or BI) AFT (PP or BI)

Receive funds
from someone OCT enabled OCT (PP or BI) OCT (PP or BI) OCT (PP or BI) OCT (PP or BI)
else

Notes:

• AFTs with BAI = WT should only be used by registered Staged Digital Wallet Operators (SDWO).

• To ensure the correct BAI is applied the acquirer should confirm with the merchant if OCT will be
enabled through another means. This information should also be included in the program
description if submitting an AFT-only PIF.

20 Visa Confidential 21 October 2021

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Table 2-3: Digital wallets comparison

Stored Value Digital Wallet Staged Digital Wallet (SDW)
(SVDW)

Definition Stored Value Digital Wallets are A Staged Digital Wallet operates a proprietary network
offered with P2P or merchant of merchants for their users to transact with. SDW is a
payment capability. The user can add wallet that uses “stages” to complete the transaction
and store funds in the digital account and does not necessarily pass along card and/or
(wallet) that will be used to send merchant information to the card brand or issuer:
funds to others or cash out to an
• Funding stage - the wallet is funded by the
unaffiliated account. Stored Value
consumer or reimbursed after a purchase
Digital Wallets must limit usage to
• Payment stage – the wallet operator pays money
the available balance in the wallet
to the merchant
and must not facilitate Back-to-Back
Payment may happen leveraging Back-to-Back
Funding.
Funding to complete a transaction10.
SVDW may have a general-purpose Staged Digital Wallets are permitted to facilitate Back-
payment network card/account at to-Back Funding transactions, but must not have a
the “front” of the wallet. It is not general-purpose payment network card/account at
primarily used to pay a merchant. the “front” of the wallet.

Add/Store Yes Yes

funds

Pull funds to No Yes (Back-to-Back Funding)

complete a
purchase

Usage of • to send funds to other users • to send to other wallet users on the platform (P2P)
funds in the • to cash out to an unaffiliated • send payments at multiple merchants under the
wallet account operator’s brand mark
• send payments at multiple • to cash out to an unaffiliated account
merchants under the operator’s
brand mark
• send payments at multiple
merchants under the general
purpose payment network’s
brand mark
• can support cryptocurrency

10 Also known as “live-load” or “real-time funding”.

21 October 2021 Visa Confidential 21

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Stored Value Digital Wallet Staged Digital Wallet (SDW)

(SVDW)

Stored Stored funds may be used to pay Payments to merchants include:

funds to pay merchants.
• Face-to-face SDW brand acceptance mark at a
merchants
Payments to merchants include: physical POS
• e-Commerce SDW brand acceptance mark
• Face-to-face SVDW-brand or
• Merchant wallets where users instruct buyers to
general-purpose payment
send money to a merchant’s digital wallet
network acceptance mark at a
• Back-to-Back Funding purchase transaction
physical POS
• eCommerce SVDW-brand or
general-purpose payment
network acceptance mark
• Merchant wallets where users
instruct buyers to send money to
a merchant’s digital wallet
Note: A wallet that is evolving to
support a Back-to-Back funding for
real-time purchases (i.e., where the
funding transaction occurs
simultaneous with the purchase) will
be classified as a Staged Digital
Wallet. The wallet may no longer
have a general-purpose payment
network card/account at the “front” of
the wallet.

Digital Stored Value Digital Wallet may be The Staged Digital Wallet may be structured as a
Wallet as a structured as a prepaid account or prepaid account but must not offer or attach a
prepaid offer a general-purpose payment general-purpose payment network card as a physical
account network prepaid card as a physical access tool to the funds in the digital wallet. This
access tool to the funds in the digital scenario does not alter the transaction or BAI coding.
wallet. This scenario does not alter
the transaction or BAI coding.

2.2.1.1.2 Bank-Initiated P2P Money Transfer – Use Case

To better service customer needs, banks are developing easy-to-use, real-time interbank P2P payment
services. To enable banks to fully leverage the benefits of the Visa Direct platform, Visa is enabling
processing and a unique pricing fee schedule for bank-initiated P2P programs. Programs defined
under this category must meet the following requirements:
• The AFT must be offered in parity with a compliant OCT
• The bank initiating the AFT must comply with the Fast Funds mandate for receiving OCTs on all
eligible Visa debit and reloadable prepaid card accounts
• AFTs must be submitted with a BAI of “BI”

22 Visa Confidential 21 October 2021

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

• AFTs with a BAI of BI may only be used for domestic P2P payments offered by banks through
bank channels. Direct-to-consumer services provided by third-party service providers
(including client-sponsored third parties) are not eligible
Important: BAI BI is used for very specific scenarios and is enabled only in limited markets.
Contact your Visa Representative for information on:
• the availability of BAI BI in your market, and
• applicability of BAI BI to your program

In addition, service providers that enable bank P2P Money Transfer platforms on behalf of banks must
ensure Fast Funds compliance of all sending banks participating in their service prior to enabling bank
P2P services on behalf of the bank and its customers. The process for ensuring participating banks are
compliant with the Fast Funds requirement as well as the status of all participating banks must be
made available to Visa upon request.
Contact your account representative for more details on bank initiated P2P programs.

2.2.1.1.3 Cryptocurrency – Use Case

Direct cryptocurrency purchases are completed using a Quasi Cash purchase. A cryptocurrency wallet
may be prefunded using an AFT and the funds are later used to purchase cryptocurrency. Only Stored
Value Digital Wallet models can support cryptocurrency wallets. The AFT must include the following
data requirements:
• BAI must be FT
• Merchant category code must be 6051
• Special Condition indicator (Field 60.4) must be 7 to identify this pull transaction is for
cryptocurrency.

2.2.1.2 Merchant-initiated transactions/Recurring transactions

Account Funding Transactions (AFTs) are permitted for use as Merchant-initiated

transactions/Recurring transactions. The transactions must be coded as described below:

For merchant-initiated transactions (MIT), the first time a card is used and being added to the
wallet/profile, an AFT must be coded with Field 22 = 01. After the card has been committed to the
database of the wallet/profile, the AFT must be coded with Field 22 = 10 (Stored credential).

Note: All MITs are not relevant for AFTs (e.g. Installments, No Show).

Examples of MITs relevant to AFTs are as follows:

• Recurring: reload $50 every week into digital wallet, or move $500 every month from bank
account # 1 to bank account # 2.

• Use card on file: when digital wallet balance hits $10, automatically reload $50.

21 October 2021 Visa Confidential 23

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

• Resubmission: In this case, the Merchant, i.e. the digital wallet operator or the bank– whoever
is debiting the card is the entity conducting the load; but if the customer has an automated
top-up using the customer’s Visa card “on file”, then it’s an MIT using a Stored Credential.

MITs with an AFT must use the following transaction coding:

Initial AFT (full 3D Secure):

• MCC 6012 (if bank led), if not bank led, MCC must represent the appropriate merchant for the
pull.

• Filed 60.8 = 05 (ECI)

• Field 22 = 0100

• Field 25 = 59

• Field 126.9 = CAVV

• Field 126.13 = C or R

o C if being captured for the first time. C is used for unscheduled payment using a card
on file.

o R if using in the first of a recurring payment and card is already on file.

Recurring AFT:

• MCC 6012

• Field 22 = 1000

• Field 25 = 59

• Field 60.8 = 07 (ECI)

• Field 126.13 = C or R

o R, if being captured for use in a recurring payment.

o C, is used for unscheduled use of a card on file if the payment is not a recurring
transaction, but initiated by the merchant based on standing instructions.

• Field 62.2 or Field 125, DS 03, Tag 03 = original transaction ID

2.2.1.3 Restrictions on Cross-Border AFTs

In most cases, AFTs are restricted to domestic only; i.e., issuer, acquirer, and merchant are in the same
country. By restricting AFTs to domestic only, Visa applies an additional control intended to ensure the

24 Visa Confidential 21 October 2021

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

merchant (service provider) is providing AFT service in countries where they are located and hold the
appropriate operating license.
V.I.P. will decline these AFTs using response code 57 if the acquirer and issuer are in different
countries. Exceptions for cross-border AFTs include:
• U.S. and Canada - Prepaid card top-up (TU): allowed between U.S. and Canada (classified as
domestic transactions)
• European Economic Area (EEA) and UK (and Gibraltar, where relevant) - TU, AA, FD, FT, PD, and PP:
AFTs are allowed if the merchant, acquirer, and issuer are all in the European Economic Area (EEA)
and UK (and Gibraltar, where relevant) (classified as domestic transactions). This allows a merchant
licensed in one EEA country or UK (or Gibraltar, where relevant) to raise funds in another EEA
country or UK (or Gibraltar, where relevant)
All Regions: Wallet transfer (WT) can be cross-border in all regions.
Effective 22 April 2022, cross-border AFTs will be made available globally, although some regions
may not enable the functionality immediately. Please contact your representative for move
information.

2.2.2 Key AFT Data Elements

AFT transaction is a type of purchase that has specific data requirements that are different from the
purchase of goods and services. Refer to Appendix A: AFT Data Elements and Processing Rules for the
data elements and message requirements that are unique to AFTs. Appendix A includes new data
fields and requirements for sender and receiver data effective 23 April 2022.

Full requirements for purchase transaction messages can be found in the technical specifications V.I.P.
System BASE I Technical Specifications, Volume 2 and V.I.P. System SMS POS (VISA & VISA Electron)
Technical Specifications, Volumes 1 & 2.

2.2.2.1 Custom Payment Service (CPS) (U.S only)

AFTs can participate in the Custom Payment Service (CPS) in the US. The objective of CPS is to
decrease member operating costs, decrease fraud losses and operating expenses associated with each
transaction, improve risk management techniques, and increase member revenues through increased
card usage.

Issuers are able to match the authorization and clearing messages allowing proper management of
the cardholder’s spending capability.

For AFTs, the CPS program is called the CPS/Account Funding Program and has specific data
requirements.

For transaction details and CPS Qualification criteria, see the CPS/Account Funding Programs section
in the U.S. Interchange Reimbursement Fee Rate Qualification Guide. The key AFT Data Elements are
included in Appendix A.

21 October 2021 Visa Confidential 25

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

2.2.3 Acquirer, Service Provider, and Merchant Network Routing Options

Acquirers, service providers, and merchants have several options for routing AFTs to VisaNet, including
traditional VisaNet connectivity using ISO messaging and by using the Visa Direct APIs. This section
outlines the available routing configurations.

2.2.3.1 VisaNet Connectivity Using ISO Messaging

Visa provides flexible, reliable, and secure access to Visa's payment systems using one of two single-
pipe connections.
• Visa Direct Exchange (DEX) is a closed, private, TCP/IP-based connection to VisaNet. DEX provides
secure access to VisaNet core processing as well as the ability to receive reports through file
exchange.
• The Extended Access Server, available outside the U.S., provides secure connectivity to VisaNet and
performs authorization routing, file staging, and delivery services. It incorporates open standards
with powerful IP technologies.

For more information, refer to the Visa Processing Services section on Visa Online or contact your Visa
representative.

2.2.3.2 Application Programming Interfaces (APIs)

Visa offers a series of application programming interfaces (APIs) that acquirers, service providers, and
merchants can use to initiate transactions and support value-added services related to AFT processing.
Some originating entities may find these web services APIs simpler to implement than traditional ISO
8583-based V.I.P. messaging.

The following APIs are applicable to AFTs. Acquirers, service providers, and merchants may choose to
use all or some of the available APIs.
• Financial Funds Transfer: The financial API used to initiate an AFT and its associated reversal
• Payment Account Validation: Allows the acquirers, service providers, and merchants to perform
address verification and/or CVV2 validation on the sender’s account
• Payment Account Attributes Inquiry: Allows the acquirers, service providers, and merchants to
determine whether the sender’s or the recipient’s non-Visa account is eligible for domestic AFTs
• Foreign Exchange Rate: Foreign exchange rate look-up and conversion
Note: Acquirers, service providers, and merchants must obtain a unique acquiring identifier if
using the Funds Transfer API. A unique acquiring identifier is not required for the Payment
Account Attributes Inquiry, Payment Account Validation, or Foreign Exchange Rate APIs.

26 Visa Confidential 21 October 2021

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Table 2-4: Visa Developer Platform (VDP) APIs

Visa Developer Platform APIs Visa API Characteristics

PullFundsTransactions POST

PullFundsTransactions GET

MultiPullFundsTransactions POST

MultiPullFundsTransactions GET
Financial Funds Transfer API’s that require VisaNet
ReverseFundsTransactions POST
connectivity
ReverseFundsTransactions GET

MultiReverseFundsTransactions POST

MultiReverseFundsTransactions GET

Adjustment ReverseFundsTransactions POST

For more information on the Visa Direct APIs and their availability in your region, contact your Visa
representative. In addition, refer to the Visa Developer Center at
https://developer.visa.com/capabilities/visa_direct. Also refer to the Original Credit Transaction (OCT) –
Global Implementation Guide for OCT-related APIs.

2.2.3.2.1 API Terms of Use

If acquirers or their VisaNet processor(s), service provider(s), third party agent(s) or any other third
parties involved in the acquirer’s program access any APIs through the Visa Developer Program
(“VDP”) in connection with the program, the Visa Developer Terms of Use
(https://developer.visa.com/terms) and the Visa Developer Security Terms
(https://developer.visa.com/pages/security-terms) apply. The acquirer must comply, and be
responsible for all third parties’ compliance with such terms in connection with its program.

2.2.3.3 Push Payment Gateway Service (U.S. Only)

The Visa Push Payment Gateway Service (PPGS) allows acquirers, service providers, and merchants to
send AFTs to Visa for routing to multiple debit networks in the U.S. The service provides authorization,
clearing, settlement, reporting, and exception processing support for the Accel, CU24, Maestro, NYCE,
Pulse, and STAR networks.

Acquirers, service providers, and merchants can use PPGS to send AFTs to VisaNet using the Funds
Transfer API or Visa's standard V.I.P. ISO message format. VisaNet translates and reformats the
messages into the correct network formats, rather than the originating entities having to develop and
maintain transaction formats for each debit network.

21 October 2021 Visa Confidential 27

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Additional information on the PPGS can be found in the Push Payment Gateway Client Implementation
Guide available on Visa Online or through your Visa account representative.

2.2.3.4 AFTs for Proprietary Card Products

As of April 2020, acquirers and issuers in Canada may optionally support AFTs for domestic processing
of eligible proprietary card products.

Acquirers on Network 0002 (Visa) can send AFTs to issuers enabled on Network 0004 (PLUS network)
for select proprietary card products.

2.2.4 Transaction Coding at Remote Channels (CEMEA)

Where the AFT service is offered to consumers over the Internet banking channel, an AFT must be
coded as an electronic commerce transaction with the following coding: Field 3 (processing code) =
10, Field 18 = 6012, Field 22 = 0100, Field 25 = 59. The AFTs must be fully authenticated with ECI Field
63.6, value 5. Any exception to the use of other ECI values must be approved prior to coding. Please
contact your regional Visa representative.

An exception allowing for the use of other ECI values was approved for the CIS SEE sub-region by the
CEMEA region. The ECI Field 63.6 will contain the ECI value that represents the result of the Visa
Secure authentication.
• 05 Fully authenticated e-commerce transaction
• 06 Merchant attempted to authenticate the cardholder
• 07 Non-authenticated e-commerce transaction

Where the AFT service is offered to consumers over the mobile banking channel, a funding AFT
transaction must be coded as card-not-present (CNP) transaction with following coding: Field 3
(processing code) = 10, Field 18 = 6012, Field 22 = 0100, Field 25 = 5.

To enhance the Money Transfer OCT service security, the merchant must include CVV2 fields F126.10
into the authorization request and must expect to receive CVV2 results in Field 44.10 (as per standard
CVV2 processing).

2.3 AFT Program Customer Requirements and Considerations

Acquirers, service providers, and merchants developing AFT programs and services must plan for all
customer-facing requirements relating to purchase transactions. In some cases, these considerations
may be mandated by Visa Rules or local regulation. Acquirers must ensure that AFT origination
programs comply with Visa Core Rules and Visa Product and Service Rules, applicable Visa regional
operating regulations, and local laws.

28 Visa Confidential 21 October 2021

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Customer considerations include the following:

• Disclosures: The program’s user interface should include all appropriate disclosures and
communications to cardholders
• Description of fees: Acquirers, service providers, and merchants must provide senders with
information related to any fees and other material terms in connection with an AFT. The sender
must be given an opportunity to agree to the fees and proceed or to cancel the transaction
• Confirmation of transaction details: Acquirers, service providers, and merchants should provide
senders with a way to review and confirm the transfer amount and other applicable details prior to
submitting the transaction
• Transaction receipt: Acquirers, service providers, and merchants must comply with the applicable
requirements for transaction receipts in the Visa Core Rules and Visa Product and Service Rules, their
applicable Visa regional operating regulations, and local law
• Transaction notifications: Acquirers, service providers, and merchants should consider providing
notifications via email and/or SMS text messages to inform senders about the status of their
submitted AFTs. This is particularly important for web and mobile channels. Acquirers, service
providers, and merchants can ask senders if they want notifications and, if so, capture the sender’s
email address or mobile phone number

2.4 AFT Risk Requirements and Considerations

This section summarizes risk requirements and considerations for AFT origination programs. For more
information about the Visa risk services available to AFT acquirers, service providers, and merchants,
contact your Visa representative.

2.4.1 Risk Management—General Considerations

Before setting up an AFT origination program, acquirers, service providers, or merchants should carry
out a comprehensive risk assessment covering their business policies and practices, fraud prevention
and detection techniques, anti-money laundering program, and other risk controls. In addition to the
recommended fraud prevention tools, acquirers and service providers should ensure adequate
practices are in place to minimize fraud losses and excessive customer service inquiries.

Acquirers, service providers, and merchants must comply with the Visa Core Rules and Visa Product
and Service Rules, local regulations, applicable sanctions, and “Know Your Customer” (KYC), anti-
money laundering, and anti-terrorist financing laws. If an acquirer uses a third party agent to support
any aspect of their AFT origination program (e.g., risk management, customer service, etc.), the
acquirer must ensure that the third party agent is in compliance with all rules and laws.

21 October 2021 Visa Confidential 29

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

2.4.2 Cardholder Data Authentication Requirements

When an AFT is used to fund a Money Transfer transaction, the acquirer, service provider, or merchant
is responsible for ensuring that data about the sender is collected, verified, and screened against
relevant watch lists in accordance with local laws and regulations for the purposes of risk
management, sanctions enforcement, and anti-money laundering and anti-terrorist financing control.

Acquirers, service providers, and merchants should develop a method to collect and verify sender
data. The sender authentication method should be appropriate to the access channel and should
follow regulatory and industry standards and best practices. Examples are the use of government-
issued photo identification, PIN, Visa Secure, internet banking identification/password, and telephone
banking PIN/password or CDCVM. The acquirer’s, service provider’s, and merchant’s risk and
compliance teams should review sender data collection and authentication methods to ensure they
follow internal requirements, applicable KYC procedures, and applicable local laws and regulations.

Acquirers, merchants and service providers are responsible for establishing processes to verify that
AFTs used on their own to fund another Visa or non-Visa account are only used to fund an account
belonging to the same individual or entity holding the Visa card account.

Note: If a prepaid cardholder’s information has not been collected and verified, an issuer must block
an AFT on prepaid cards to ensure the funds are not transferred using Visa Direct OCT to a Visa credit,
debit or reloadable prepaid card with cash access.

2.4.3 Transaction Monitoring and Screening

Acquirers and service providers of AFT programs must implement transaction monitoring and
screening procedures to flag high-risk transactions for review prior to submission. These should
include limits (such as count, amount, and rolling limits) to reduce the risk associated with such
transactions, Modulus-10 checks, and other checks to determine whether the sender is on any
applicable government or bank-specific blocked lists.

In addition, acquirers, service providers, and merchants must have processes in place to identify
transaction activity for any signs of fraud or misuse, including money laundering and terrorist
financing. Acquirers should consult their appropriate fraud, risk, and compliance teams to ensure their
programs meet their institution’s monitoring requirements.

Acquirers, service providers, and merchants that initiate AFTs are required to monitor programs and
transactions to ensure that they are not inappropriately being used for merchant payments of goods
and services (for example, by checking for a high number or variety of senders to a single receiving
account).

30 Visa Confidential 21 October 2021

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

2.4.4 Fraud Detection and Prevention

Effective fraud tools will minimize risks to the acquirer, service provider, or merchant. The acquirer,
service provider, or merchant has little recourse with the issuer if an AFT proves fraudulent. Risk
management tools should be built into processing systems to detect and prevent fraud, errors,
sanctions, violations, money laundering, and terrorist financing.

Such tools include PIN or CDCVM, internet or telephone banking identification and password, Visa
Risk Manager (VRM), Visa Advanced Authorization (VAA), CVV2 verification, Visa Secure, Address
Verification Service (AVS)11, Visa Transaction Advisor (VTA), Modulus-10 check digit verification,
negative files and screening, and systems control tools to identify processing errors and suspicious
activity.
Note: CVV2 and/or AVS checking associated with the AFT can be accomplished using the Visa Direct
APIs. Refer to Section 2.2.3.2: Application Programming Interfaces (APIs) for more information.

The following risk management reference materials can be found on Visa Online or obtained from
your Visa representative:
• Global Visa Acquirer Risk Quick Reference Guide: Provides acquirers with best practices for managing
card-absent acceptance risk
• Global Visa Acquirer Fraud Control Manual: Covers the merchant life cycle, from underwriting
through monitoring and termination, and provides information and resources for reducing and
preventing fraud losses
• Fraud and dispute risk information, including:
• Fraud Reporting Service (FRS): AFT origination entities are required to report fraudulent AFTs
to the FRS
• Address Verification Service (AVS): Verifies a cardholder’s billing statement address when
processing card-not-present or key-entered transactions
• Card Verification Value 2 (CVV2): The three-digit code printed on the signature panel of all
Visa cards

In the Europe Region, please refer to the following risk materials:

• Acquirer Risk Monitoring and Detection
• Issuer Fraud Monitoring and Detection
• Merchant and Cardholder Lifecycle Risks—Best Practice Guide
• Managing Fraud in the Card Not Present Environment
• Payment Services Directive 2 (PSD2) Strong Customer Authentication (SCA) Guide

11AVS is available in the U.S., Canada, UK, and Ireland. Check with your regional Visa representative for availability of
verification tools.

21 October 2021 Visa Confidential 31

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

These documents are available on VOL. You may also contact your Fraud Manager for a copy of the
documents. For more information on PSD2 SCA applicability to Visa Direct, refer to Payment Services
Directive 2 (PSD2) on VOL.

For additional information about the Visa risk services available to AFT acquirers, service providers,
and merchants, contact your Visa representative.

2.4.5 Push Payments Tokenization

A Payment Token is an “alternate identifier” that can be used in place of a PAN to initiate a payment
transaction. Push Payments tokenization enables Visa Direct service providers that submit account
funding transactions (AFTs) and original credit transactions (OCTs) with Personal Account Numbers
(PANs) to process with tokens.

Visa supports Visa Token Service for AFTs and OCTs for all available token types.
• AFTs and OCTs that are submitted for token processing must comply with all the existing
processing rules for AFTs and OCTs
• Token requestors or entities that act on behalf of the token requestors must adhere to the
tokenization rules for push payments token transactions. AFT and OCT token transactions only
work with tokens assigned to token requestors who are enabled for Visa Direct. Please contact
your tokenization service provider for details.
• Acquirers, service providers and merchants who integrate with the token requestors and submit
an AFT and OCT token transaction must follow the tokenization specifications. An AFT token
transaction requires an AFT-specific cryptogram. Please contact your tokenization service
provider for details.
• Acquirers, service providers and merchants that submit AFTs and OCTs for token processing
may only send these transactions to recipient issuers that support AFTs, OCTs, and Visa Token
Service
• In the U.S. region, OCTs with a token are eligible to be sent and received on Network 0002
(Visa), Network 0003 (Interlink), and Network 0004 (PLUS)

For more information on the impacted token types for AFTs and OCTs, contact your regional client
support representative.

For more information on Tokens, refer to Visa Token Service.

32 Visa Confidential 21 October 2021

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

2.4.6 Real Time Visa Account Updater (VAU) 12

Visa Account Updater (VAU) is a key service to support payment continuity in recurring billing and
credential-on-file segments. Real Time VAU is a feature that integrates the VAU updates into the
VisaNet authorization process for merchant-initiated transactions and enables real-time updates. Real
Time VAU eliminates the multi-step process to update account information.

Acquirers, merchants, and service providers that participate in Real Time VAU have the option to
request account information replacement when originating AFTs and OCTs.

Note: Acquirers, merchants and service providers that request account information replacement in
AFTs and OCTs must support Field 127—PAN File Maintenance.

2.4.7 Data Security—PCI Compliance

Acquirers, service providers, and merchants must ensure that the data contained in AFTs and any
other data about the cardholder collected during the transaction is handled in compliance with the
Payment Card Industry Data Security Standard (PCI DSS) and applicable law. Cardholder information
must be stored and transmitted securely, with regular reviews of data security policies to ensure that
criminals, hackers, or other unauthorized people cannot break into the data warehouses or intercept
data during transmission. In addition, acquirers, service providers, and merchants should follow
standard practices to identify and prevent phishing, account take-overs, and hacker attacks.

Sound data security practices reduce fraud risk and also foster customer confidence in the secure
handling of personal information.

Acquirers, service providers, and merchants should:

• Implement procedures to control employee access to customer account data and ensure that
customer service screens and customer receipts do not display full payment credentials
• Collect and store personal and financial information about customers involved in funds transfers
according to set standards of security and accountability (as required by legislation in most
countries)

For more information about the PCI DSS, refer to the PCI Security Standards Council web site at
https://www.pcisecuritystandards.org/pci_security/.

12 Available to Europe in May 2021.

21 October 2021 Visa Confidential 33

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

2.5 AFT Refund Use Case

When a cardholder attempts to send funds to a recipient, an AFT is used to pull the funds from the
cardholder’s account. If the recipient has rejected the funds, declined the transfer or the transfer
expires, the service provider must return the funds to the original cardholder. This can be
accomplished using an AFT reversal or a credit adjustment transaction.

The considerations for using these transactions depend on the acquirer’s connection to Visa and the
process flow for transfer and claim.

Note: A credit adjustment must be be processed within 30 calendar days of the original transaction.

The table below provides an overview of the reversal and adjustment transactions and associated
processing considerations.
Table 2-5: Reversal and Adjustment transactions overview

Processing Type Reversal Adjustment

SMS processing clients • A full financial AFT reversal • A credit adjustment transaction
(0420) must be used to refund (0220) with processing code 22
within the first 24 hours of the (Adjustment-Credit) and reason
original transaction time, but code 2140 (Account funding
before the settlement of the transaction: debit or credit
transaction. adjustment) must be used to
process refunds to the sender’s
Note: For refunds that need to be
card.
processed beyond the 24 hour
window, clients should consider an • These refunds can be applied
adjustment transaction (see the even beyond the 24 hours
adjustment column) window available with the
reversal transactions.

Note: Issuers may manage AFT

credit adjustments as a back-office
process instead of posting the
transaction directly into the
cardholder’s account. Therefore,
the timeframe for when the
cardholder should expect the
refund will vary by issuer.

Dual Message processing clients • Clients using Dual message An adjustment transaction (TC06
processing can utilize an with TCQ-1) can also be utilized to
authorization reversal (0400) as process refunds to the sender’s
a way to refund. This can only card after the original AFT has been
be utilized before the original cleared.
AFT has been cleared.

34 Visa Confidential 21 October 2021

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Processing Type Reversal Adjustment

Notes: o These get processed as batch
clearing transactions
o Visa rules presently require
clearing to be performed o Transaction ID of the original
within 7 days of the AFT should be included to
original authorization. make it easier for issuers to
However, as a best practice reconcile the adjustment with
Visa recommends clearing the original transaction.
the original AFT within 3
days to ensure better
cardholder experience.

o Clients should not be

submitting a clearing once
the authorization reversal
has been processed.

• Clients also have the option of

processing a reversal
transaction in the clearing (as
TC25, TCQ-1) if the original
transaction has been cleared.

o This is processed as a
batch clearing
transaction and can be
performed up to 30 days
from the original
transaction.

Important: If the service provider attempting to process an AFT Refund is missing the original Tran ID,
this may result in the issuers being unable to match the transaction to the original AFT. This can be an
unpleasant experience for the cardholder as they wait for the funds to be deposited to their card. The
Tran ID field is optional; however, it is key information that helps the issuers connect the original AFT
with the transaction used to perform the AFT refund.

For dispute information, see Section 3.2.2.

21 October 2021 Visa Confidential 35

 Requirements and Considerations for AFT Origination
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

2.6 AFT Reporting Requirements for Originating Entities

AFTs are included on existing VisaNet reports along with other purchase transactions. However, AFTs
are not reported separately on VisaNet Settlement Service (VSS) reports. They are reported under the
"PURCHASE" fee descriptor.

2.7 AFT Certification Requirements

For acquirers/processors that do not yet support AFTs, it is required to complete VisaNet testing using
the VisaNet Certification Management Service (VCMS) to ensure they meet all requirements before
submitting AFTs.

36 Visa Confidential 21 October 2021

 Issuer Requirements and Considerations
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

3 Issuer Requirements and Considerations

This section includes information for issuers to support the processing and authorization of AFTs for
their cardholders. Issuers must comply with the Visa Core Rules and Visa Product and Service Rules,
their applicable Visa regional operating regulations, and local law.

Note: All AFT-enabled issuers must be able to receive and process AFTs. AFT support is mandated for
issuers in U.S., Canada, and CEMEA regions.
Effective 15 October 2022, AFT support will be required in the Europe region.
AP and LAC must be aware that Visa has implemented changes to convert AFTs with the
processing code 10 (Account Funding) to a purchase transaction with the processing code 00
(Goods/Service purchase–debit) prior to sending the transaction to issuers that are not enabled,
or have not opted in, to receive the AFT processing code 10. AFTs that are converted to a
purchase transaction contain a BAI in Field 104 that issuers must be able to receive and process.

3.1 Receiving and Processing AFTs

To ensure a positive cardholder experience and comply with Visa Rules, issuers that support or receive
AFTs should consider the following in their AFT handling processes:
• Confirm AFTs are approved at a rate in line with approval rates of e-commerce purchase
transactions
• Validate that processor and Visa parameters are not configured to decline all AFTs
• Ensure that the use of AFT processing code 10 does not interfere with the ability to process and
authorize AFTs
• Verify that AFTs:
o Are processed similar to an e-commerce purchase transaction (i.e., not as an ATM withdrawal)
o Use appropriate statement messaging
o Do not generate unexpected cardholder fees
Note: For Russia: Issuers must not charge additional service fees or funds transfer fees for AFTs
received on debit payment credentials.
o Have reasonable transaction limits in accordance with an e-commerce purchase transaction
o Can be processed with a BAI
• Be aware that account information replacement may occur for issuers who participate in the Real
Time VAU service. Issuers that participate in Real Time VAU service must notify Visa of each VAU
primary account number (PAN) update when the cardholder has opted out of account information
replacement during authorization processing.

21 October 2021 Visa Confidential 37

 Issuer Requirements and Considerations
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Because the AFT is a type of purchase transaction, the message requirements for a purchase
transaction also apply. Full requirements for purchase transaction messages can be found in the
technical specifications V.I.P. System BASE I Technical Specifications, Volume 2 and V.I.P. System SMS
POS (VISA & VISA Electron) Technical Specifications, Volumes 1 & 2. This guide describes the message
requirements that are unique to an AFT. Key data elements for the AFT message are detailed in
Appendix A: AFT Data Elements and Processing Rules.

3.2 Risk and Disputes for Issuers

Issuers should monitor their AFT transactions for suspicious activity and potential fraud. Risk and fraud
monitoring is similar to how the issuer monitors typical purchase transactions for risk and fraud.
Standard fraud mitigation tools should be used, such as using VAA, CVV2 and the Address Verification
Service (AVS) on the account and the cardholder initiating the AFT. As with all transactions, AFT fraud
is required to be reported to the Visa Fraud Reporting System (FRS) as specified in the Fraud Reporting
System (FRS) User's Guide that can be found on Visa Online.

3.2.1 Using Visa Velocity Limit Checking to Mitigate Risk

To help reduce the risk of fraud and money laundering, Visa has set amount limits as shown in Table
3-1. The limits will apply to all domestic AFTs. If the transaction exceeds a Visa defined/enforced 1-
day, 7-day, or 30-day amount limit, VIP will decline the transaction with RC61 (Amount Limit/PAN
Limit).
Table 3-1: AFT Velocity Limits

AFT Transaction Type Time Period

One-Day Seven-Day Thirty-Day

Domestic Money Transfer USD 10,000 USD 25,000 USD 50,000
Domestic Non-Money Transfer USD 10,000 USD 25,000 USD 50,000
Cross-Border USD 10,000 USD 25,000 USD 50,000

In the U.S, if issuers apply internal limits, they must ensure the daily spend limit for AFTs is set to a
minimum of $5,000.

Effective 22 April 2022, cross-border AFTs will be made available and the above velocity limits will
apply.

Effective 16 April 2021, in the U.S., issuers and issuer processors are required to differentiate their daily
spend limits by AFT and purchase transactions. AFTs can be differentiated from a purchase transaction
by a unique Processing Code: AFT = 10, Purchase = 00 in ISO Field 3.1.

38 Visa Confidential 21 October 2021

 Issuer Requirements and Considerations
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Note: Per Issuer Requirement to Evaluate Each Transaction (IREET) rule, issuers must not systematically
decline all transactions based solely on transaction amount, and instead, must approve or decline
transactions on multiple factors. Issuers can still choose to decline an AFT irrespective of the
transaction amount, if it does not meet the issuer’s approval criteria.

3.2.2 Issuers – Dispute Resolution

AFTs have the same dispute rights as all other purchase transactions outlined in the Visa Core Rules
and Visa Product and Service Rules.

Refer to the Dispute Resolution section in the Visa Core Rules and Visa Product and Service Rules to
efficiently resolve disputed transactions.For VROL information, <<add link to VROL section within Visa
Online>> (https://secure.visaonline.com/SitePages/Section.aspx?pageid=2.1.1.0.0)
Table 3-2: Examples of AFT Dispute Situations

Condition Code Dispute Situations

10.4 - Fraud Category This dispute may be used when the cardholder did not
authorize or participate in a transaction conducted in a Card
Not Present environment.

11.2 – Declined Authorization This dispute may be used when an Authorization Request
received a Decline Response, or a Pickup Response and the
merchant completed the transaction.

11.3 – No Authorization The dispute may be used when Authorization was required but
was not obtained on the date. Refer to the Approval Response
Validity Timeframes section in the Visa Core Rules and Visa
Product and Service Rules.

12.1 – Late Presentment This dispute applies only if the Transaction was not processed
within the required time limit. Refer to the Acquirer Processing
Timeframes section in the Visa Core Rules and Visa Product and
Service Rules

12.4 – Incorrect Account Number This dispute applies when the transaction was processed using
an incorrect payment credential and for which either an Imprint
or an Authorization was not obtained.

12.5 – Incorrect Amount This dispute may be used for the following situations:
• Transaction Amount is incorrect
• An addition or transposition error occurred

12.6 – Duplicate Processing This dispute may be used when a duplicate AFT was submitted.

21 October 2021 Visa Confidential 39

 Issuer Requirements and Considerations
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Condition Code Dispute Situations

13.1 – Merchandise/ Services Not Received This dispute may be used for either of the following situations:
• Serviced not rendered by the expected date
• Merchandise was not received on the expected
date/agreed location
• If the customer participated in the AFT but the funding
never completed.

13.8 – Original Credit Transaction Not This dispute may be used for either of the following situations:
Accepted • Legal restrictions prevent accepting the credit
• Recipient refuses the credit

3.2.3 AFT Refund – Processing Considerations

In the event of an AFT reversal or credit adjustment, issuers must be aware of the considerations for
processing a reversal or adjustment.

Note: A credit adjustment should be processed within 30 calendar days of the original transaction.

Refer to Table 2-5: Reversal and Adjustment transactions overview for more information on the
reversal and adjustment transactions and associated processing considerations.

3.3 Issuer Reporting Requirements

AFTs must be reported on the Quarterly Operating Certificates with the issuer’s purchasing volume.
Notes:
• In the U.S. region, AFTs generated as part of a financial institution–offered P2P Money Transfer
service do not need to be reported on the Quarterly Operating Certificate.
• In Europe, Canada, CEMEA, and AP, acquirers are no longer required to submit Visa Direct
transactions manually. A new Global Operating Certificate (GOC) tool13 was introduced in VOL
and each client is required to submit Visa Direct volumes via the VOL platform. Each reporting
client has access to the GOC tool under “My Services” in VOL.

13 Available to LAC in April 2021, and U.S. in October 2021.

40 Visa Confidential 21 October 2021

 Issuer Requirements and Considerations
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

3.4 Issuer Certification Requirements

The issuers and issuer processors that are ready to support AFTs without downgrading to a purchase
transaction should test in VCMS if they meet all transaction requirements to receive AFTs. Once the
issuer meets the certification requirements, the issuing identifier flags will be enabled to receive AFT
processing code (10).

21 October 2021 Visa Confidential 41

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

A AFT Data Elements and Processing Rules

This appendix provides the data elements and message requirements unique to AFTs.
Table A-1: AFT Key Data Elements
V.I.P. BASE II Value Notes/VisaNet Edits/
(0100/0200) (TC05) Requirements
Field Name Field Name

Field 2 TCR 0, pos. 5-20 Sender’s Visa payment This field contains the sender’s
Primary Account Account Number credential. primary account number
Number (PAN).
Length: 16
Length: variable Format: UN
Format: 1 byte
binary + up to 19
N, 4-bit BCD
(unsigned packed);
maximum 11 bytes

Field 3 n/a Must contain a value of 10 Note: All U.S., Canada, and
(positions 1-2). CEMEA issuers are required to
Processing Code
support AFTs with Processing
Length: 3 Note: Positions 3-6 contain
Code 1014.
0000 for all countries but
Format: 6 BCD If an AFT is sent to an issuer
Brazil.
Brazil: Position 3-4 contains that is not set up, or has not
a default value of 20 for a opted in, to receive Processing
combo card. Position 5-6 Code 10, V.I.P. converts
contain 00. Processing Code 10 to
purchase Processing Code of
00 (Goods/Service purchase–
debit).

14 Effective April 2020, CEMEA is mandating support of AFT with Processing Code 10.

42 Visa Confidential 21 October 2021

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name
Brazil: Some issuers in Brazil
issue "Combo Cards" that have
both a checking/prepaid
account as well as a credit line
linked to the same card. For
such cards, it is important to
send "20" in position 3-4, so
that the AFT pulls funds from
the checking/prepaid account.
If the acquirer does not send
the value of 20, the system will
default position 3-4 to 20 if the
card range is identified as a
Combo Card.

Field 4 TCR 0, pos. 77-88 If acquirers, service The total amount of the AFT
Amount, Source Amount providers, or merchants use including all fees.
Transaction Field 28 Transaction Fee Conceptual Example:
Length: 12
Amount/AFT Service Fee or
Length: 6 Format: UN Transaction Amount: 50.00
Field 54 Additional
Format: 12 BCD Amount/AFT Foreign AFT Service Fee: 2.00
Exchange Markup Fee, they AFT Foreign Exchange
must include those amounts Markup Fee: 2% of 50.00
in Field 4. = 1.00 (n/a to prepaid
load)
Field 4 contains: 50.00 +
2.00 + 1.00 = 53.00
Field 28 contains: 2.00
Field 54 contains: 1.00
Notes:
• In this example, only the
AFT Service Fee and AFT
Foreign Exchange Fee are
applicable to the
transaction. Any additional
applicable fees would
increase the amount in
Field 4.
• In the V.I.P. manual, this
field is called “Transaction
Fee Amount.”

21 October 2021 Visa Confidential 43

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name

Field 18 TCR 0, pos. 133-136 Value depends on value of For AA, use 4829, 6012, or
Merchant Type Merchant Category BAI (Field 104): 6211

Length: 2 Code Merchant Category Code • 4829 - Non-Financial

Length: 4 (MCC): Institution Wire Transfer
Format: 4 BCD
For AA, use 4829, 6012, or Money Orders (WTMOs)
Format: UN
6211 (In the U.S, MCC 4829 (Not applicable in the U.S.
is not applicable with BAI with BAI AA)
AA) • 6012 – Financial Institution
- Merchandise Services
For BI, use 6012
• 6211 - Brokerage
For FD, use any MCC
associated to the merchant For FD, use any MCC
associated to the merchant
For PD, use 8931
For PD, use 8931 Accounting,
For PP, use 4829 or 6012
Auditing and Bookkeeping
For TU, use 6012, 6051 or services including Payroll
6540
For PP, use 4829 or 6012
For WT, use 605115
• 4829 - Non-Financial
For FT, use 4829, 6540 or Institution Wire Transfer
601216 Money Orders (WTMOs)
• 6012 - Financial
Institutions - Merchandise
and Services
For BI, use 6012
• Bank-Initiated P2P Money
Transfer (BI)
Note: For Money Transfer AFTs,
BASE II will return the
transaction with the return
reason code 23.
For TU, use 6012, 6051 or
6540
• 6012 - Financial
Institutions – Merchandise
and Services
• 6051 - Non-Financial
Institutions-Foreign

15 If the funds will be used for a High-Brand Risk Transaction, use the applicable high-brand risk MCC.
16 If the funds are used for a High-brand risk transaction, use the applicable High-brand risk MCC.

44 Visa Confidential 21 October 2021

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name
Currency, Non-Fiat
Currency (example,
Cryptocurrency), Money
Orders (not Money
Transfer), Travelers
Cheques, and Debt
Repayment
• 6540 - Non-Financial
Institutions –Stored Value
Card Purchase/Load
For WT, use 6051
• 6051 - Non-Financial
Foreign Currency, Non-Fiat
Currency (example,
Cryptocurrency), Money
Orders (not Money
Transfer), Travelers
Cheques, and Debt
Repayment
For FT, use 4289, 6540, or
6012
• 4829 - Non-Financial
Institution Wire Transfer
Money Orders (WTMOs)
• 6540 - Non-Financial
Institutions –Stored Value
Card Purchase/Load
• 6012- Financial
Institutions - Merchandise
and Services
• If the stored value wallet
is a Cryptocurrency
wallet the MCC must be
6051 - Non-Financial Foreign
Currency, Non-Fiat Currency
(example, Cryptocurrency),
Money Orders (not Money
Transfer), Travelers Cheques,
and Debt Repayment

Field 22 Valid values include: This field indicates:

POS Entry Mode • 01 Manual (key entry)
Code

21 October 2021 Visa Confidential 45

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name
Fixed Length: 3 N, • 02 Magnetic stripe read • The method used to enter
4-bit BCD • 05 Integrated chip card the payment credential
read and card expiration date,

Note: For Field 22, value • If an electronic terminal is

05 should be used only used, and,
in countries in CEMEA. • The capability of the
• 07 Contactless device- terminal to capture online
read-originated using PINs for transactions
qVSDC chip data rules processed through
VisaNet.
• 10 Credential-on-file:
Merchant initiates Notes:
transaction for • Any transaction that uses
cardholder using stored credentials should
credentials stored on use POS Entry Mode Code
file. = 10.
• 90 Magnetic stripe read • Merchants use POS Entry
Note: Acquirers must select Mode Code = 10 based on
the appropriate value for card the payment credentials
present or card not present they have associated with
transactions. If the the cardholder profile or
transaction data is not wallet.
accurate, Visa will charge For all valid values and for
Data Integrity Fees on the complete details on these
acquirer. fields, refer to the V.I.P.
manuals.

Field 25 n/a Examples of valid values Contains the POS Condition

POS Condition include the following: Code applicable to the access
Code 59 indicates an e-commerce channel.

Length: 2 transaction Note: The value 05 should not

01 indicates a cardholder not be used for online merchants,
Format: 2 BCD
present transaction including online gambling.

05 indicates a cardholder Note: For CPS qualification, a

present, card not present value 59 is required.
transaction For all valid values and
Note: Acquirers must select complete details on this field,
the appropriate value for card refer to the V.I.P. manuals.
present or card not present
transactions. If the
transaction data is not
accurate, Visa will charge

46 Visa Confidential 21 October 2021

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name
Data Integrity Fees on the
acquirer.

Field 28 TCR 4, pos. 51-58 Acquirers, service providers, Values in this field must be in
AFT Service Fee AFT Service Fee or merchants supporting the same currency and format
Field 28 and charging as the currency code outlined
Length: 9 Length: 8
senders a fee for the AFT in Field 49/TCR 0.
Format: AN Format: UN may provide the fee in this This field is not present in
field. When present, this field response messages.
contains the sender’s AFT
Refer to Field 4 for an example.
Service Fee as assessed by
the originator. Important: The Prefix value
(position 1) is for informational
For V.I.P.:
purposes only. Clients should
Position 1: Prefix—Must be not use the prefix for settlement
populated with a value of D purposes. Instead, they should
(Debit to cardholder). look at the message type and
Note: The 0220 Deferred Processing Code to determine if
Clearing Advice will contain a the amount is a credit or a
value of C (Credit to debit.
cardholder) even though this Note: Field is not sent unless
is actually a debit. the issuer opts in.
Positions 2-9: AFT Service
Fee—Contains the AFT
service fee assessed by the
originating entity (if
applicable). Must be right-
justified with leading zeros,
and include an implied
decimal relative to the
currency code specified in
Field 49.
The amount in this subfield
must be in the same
currency as Field 49.
Important: Originating
entity must include the
amount in this field in the
total amount in Field 4.

Field 32 n/a A valid number provided by This code identifies the

Visa. financial institution acting as
the acquirer of the AFT.

21 October 2021 Visa Confidential 47

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name
Acquiring Field 32 reject codes are:
Institution 0020 = Invalid length
Identification Code
0021 = Invalid value
Length: Variable
0287 = Field missing
and up to 11 digits
0531 = Non-domestic
Format: 4-Bit BCD
transaction

Field 42 n/a Must contain a unique The unique CAID from the
Card Acceptor identifier for the originator. original transaction message is
Identification Code required in any subsequent
messages, including reversals,
Length: 15
disputes, and representments.
Format: ANS,
V.I.P. Edit:
EBCDIC, 15 bytes
This field must contain a non-
zero value.

Field 43 TCR 0, pos. 92-132 Merchant Name position 1- Money Transfer Field Format
25
Card Acceptor Merchant Name, The Card Acceptor Name field
Merchant City Name
Name/Location, Merchant City, and must contain the “Doing
position 26-38
pos. 1-40 Merchant Country Business As” name or
Merchant Country Code
Length: 40 Code abbreviation of the merchant
position 39-40
Length: 40 (1–4 characters) and be the
Format: 40 ANS Transaction Type: name most recognizable to the
Format: AN Money Transfer (BAI=AA, cardholder in addition to the
BI, FT, PP, WT) recipient’s name.
This field must contain The Merchant Name field
merchant or service provider must contain the full Merchant
information (name, city, and Name or conform to the
country code). following format when
For an AFT that is used to including a recipient name:
fund a Money Transfer Format Field Position Data
transaction, this field may Pos. 1–4: Merchant Name
also contain the name of the (abbreviated)
recipient of the funds.17 Pos. 5: Asterisk (*)
All regions: Must contain Pos. 6–25: Recipient Name
Money Transfer provider's (optional, but recommended)
name or abbreviation. Examples:
Inclusion of recipient name
is optional but

17 The recipient’s name is not required but recommended in all regions.

48 Visa Confidential 21 October 2021

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name
recommended. If recipient Example #1: AFT for a P2P
name is included, the field payment (BAI – PP)
will contain an asterisk (*) in MTMT*MarySmith
position 5 followed by the
MTMT = generic example of a
recipient’s name.
Money Transfer Merchant
Transaction
Mary Smith = Recipient Name
Example #2: Bank-Initiated P2P
(BAI = BI)
FNBA*Mary Smith
FNBA = abbreviated name of
bank initiating the AFT
Mary Smith = Recipient Name
This information will appear on
the card statement to help the
cardholder identify the
transaction. Including the
recipient’s name can prevent
unnecessary calls from
cardholders to their issuers.
Note: Refer to the V.I.P. and
BASE II manuals for normal
processing instructions.

Field 48, Usage 2, TC05, TCR 1 Positions Position 1, Field Identifier: Data will be available in
Unformatted Text 24 – 73, Member This is a 1-position code, V22255 (Financial Transaction
in Authorization/ Message Text *(asterisk). This code Record/Fee Collections/Funds
Reversal Messages indicates that this field Disbursement Text Message
contains unformatted, user- Record) in the SMS raw data
Length: Variable
determined text for the report to include this data
maximum 256
destination acquirer or Visa Direct API Field name:
bytes
issuer. memberComments
Format: ANS,
Positions 2–255, Text: In
EBCDIC
authorization or reversal
requests, the input consists
of acquirer comments for
the issuer. In authorization
or reversal request
responses, the input consists
of issuer comments for the

21 October 2021 Visa Confidential 49

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name
acquirer, such as a referral
telephone number.

Field 49 TCR 0 If AFT Service Fee (Field

Currency Code, Source Currency Code 28/TCR 4) and/or AFT Foreign
Transaction Exchange Markup Fee (Field
Length: 3
54/TCR4) is present in the
Length: 3 Format: AN message, the fees in those
Format: 4 BCD fields must be in the same
currency and format as the
currency listed in this field.
Note: Refer to the V.I.P. and
BASE II manuals for normal
processing instructions.

Field 54 TCR 4, pos. 112-119 Note: This field is applicable When present, this field
AFT Foreign AFT Foreign Exchange only if using it with BAI WT contains the sender’s AFT
Exchange Markup Markup Fee as cross-border transaction. Foreign Exchange Markup Fee
Fee Otherwise, AFTs are as assessed by the originating
Length: 9
domestic-only and this field entity.
Length: 20 Format: UN will not be used, except for Values in this field must be in
Format: 1 byte EEA which may include the same currency and format
binary + 20 ANS foreign exchange between as the currency code outlined
intra-EEA countries. in Field 49/TCR 0.
Acquirers, service providers, This field is not present in
or merchants that support response messages.
Field 54 and charge senders
Refer to Field 4 for an example.
a Foreign Exchange Markup
Fee on cross-border AFTs Note: Field is not sent unless
may provide the foreign the issuer opts in.
exchange fee in this field. V.I.P. Edit:
The V.I.P. format of this field If the Currency Code (positions
follows: 5-7) is not the same currency
Positions 1-2: Account code as in Field 49, V.I.P. will
Type—Must contain a value decline the request message
of 00 (Not applicable or not with the response code value
specified). of 12 (Invalid transaction).
Positions 3-4: Amount Important: The Amount, Sign
Type—Must contain a value (position 8) is for informational
of 95 (VMT). purposes only. Clients should
not use the sign for settlement
Positions 5-7: Currency
purposes. Instead, they should
Code—Must contain the
look at the message type and
same currency code value as

50 Visa Confidential 21 October 2021

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name
in Field 49 Currency Code, Processing Code to determine if
Transaction. the amount is a credit or a
Position 8: Amount, Sign— debit.
Must contain a value of D Note: Refer to the V.I.P.
(Negative balance). manuals for complete details
Note: While C (Positive on the length and format of this
balance) is a valid value in field.
this field, it is not applicable V.I.P. Edit:
to this usage. If the Amount (positions 9-20)
is not correctly formatted
Positions 9-20: Amount—
according to the currency code
Contains the sender’s AFT
outlined in Field 49, V.I.P. will
Foreign Exchange Markup
decline the request message
Fee as assessed by the
acquirer, service provider, or with the response code 12
merchant (if applicable). This (Invalid transaction).
subfield must be right-
justified with leading zeros,
and include an implied
decimal relative to the
currency code specified in
Field 49. The amount in this
subfield must be in the same
currency as Field 49.
Important: Acquirers, service
providers, or merchants must
include the amount in this
field in the total amount in
Field 4.

Field 60.2 Valid values for Terminal Refer to V.I.P. System SMS POS
Terminal Entry Entry Capability are: (VISA & VISA Electron)
Capability • 1 Terminal not used Technical Specifications for a
complete list of valid values
Length: 1 Note: For card not
and for the details of this field.
Format: 1 N present transactions, use
this value.
• 2 Magnetic stripe read
capability
• 3 QR Code
• 5 Contact chip,
magnetic-stripe, or
proximity-capable
terminal, indicating that

21 October 2021 Visa Confidential 51

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name
the terminal can read
the chip and the
magnetic stripe on the
card.
If contact chip is
supported, value 5
should be used
regardless of whether
Visa Contactless is also
supported.
• 8 Proximity-read-
capable. For Visa
Contactless, an 8 should
be used only if Visa
Contactless is supported
and contact chip is not.
• 9 Terminal does not read
card data
Note: Acquirers must select
the appropriate value for card
present or card not present
transactions. If the
transactions data is not
accurate, Visa will charge
Data Integrity Fees on the
acquirer.

Field 60.4 Special 7 Cryptocurrency If the AFT is prefunding a

Condition Indicator wallet that will be used to
Conditional purchase cryptocurrency, this
field should contain a value of
7.

Field 60.8 n/a Examples of valid values for Refer to existing BASE I
Mail/Phone/ e-commerce transactions manuals for a complete list of
Electronic include 5–8. valid values and for the details
Commerce • 05 Fully authenticated e- of this field. For Europe, also
Payment Indicator commerce transaction refer to 3DS manual.

(BASE I only) • 06 Merchant attempted

Length: 1 to authenticate the
cardholder
Format: 2N, 4 bit
BCD

52 Visa Confidential 21 October 2021

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name
• 07 Non-authenticated e-
commerce transaction
• 08 Non-secure e-
commerce transaction

Field 62.1 TCR 0, pos. 151 Y – Request a CPS For U.S only: Send a value of
Authorizations For dual message, Qualification check Y to check transaction for CPS
Characteristics include the qualification.
Indicator Authorization
Fixed length; Characteristics
Format: 1 AN, Indicator that was sent
EBCDIC; 1 byte in the authorization
message.

Field 62.2 TCR 5, 5-19 Acquirers, service providers,

Transaction ID Transaction ID merchants and recipient
issuers must be prepared to
Length: 8 Length: 15
receive this field.
Format: 15 BCD Format: UN
Note: If an AFT has a
corresponding OCT, originators
are strongly recommended to
take the Transaction ID from
the AFT and populate it into the
OCT to link the two
transactions together. This is
required in Canada.

Field 62.20 n/a Visa assigns the first six MVV is used to identify
Merchant positions and assists the merchants that participate in a
Verification Value acquirer in assigning the last variety of programs. The MVV
(MVV) four. is unique to the merchant.

Length: 10 Acquirers are not required to V.I.P. edits:

provide the last four digits of If the MVV is not valid, V.I.P.
Format: 4-bit BCD,
the MVV. rejects the transaction with
5 bytes
reject code 0720.

Field 63.1 n/a Acquirers, service providers, Note: If an acquirer, service

or merchants must send a provider, or merchant
Network
value of 0000 (Priority sends the transaction with
Identification Code
Routing) or 0002 (Network a value of 0000 (Priority
Length: 2 Routing), it will be routed
ID 2).
Format: 4 BCD over network 2.
Issuers will receive a value of
0002 in this field.

21 October 2021 Visa Confidential 53

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name

Field 63.6, pos. 4 n/a Examples of valid values for Refer to existing SMS manuals
Mail/Phone/ e-commerce transactions for a complete list of valid
Electronic include 5–8. values and the details of this
Commerce and • 05 Fully authenticated e- field.
Payment Indicator commerce transaction
(SMS only) • 06 Merchant attempted
Length: 1 to authenticate the
cardholder
Format: 1 ANS,
EBCDIC • 07 Non-authenticated e-
commerce transaction
• 08 Non-secure e-
commerce transaction

Field 104, Usage 2, Values are 00–99 Contains the risk score for the
Dataset Value Hex Visa transaction.
5B Advisor E-Commerce Scoring
Visa Risk Service. It indicates the degree
Assessment Data of risk associated with a
Tag: 01 transaction.

Risk Score There is PCR level participation

to receive this score in the
Length: 2
response. A valid MVV is also
Format: AN required.
Note: Tag 01—Risk Score is
always present in Field
104, Usage 2, Dataset ID
5B.

Field 104, Usage 2, Values are 00–10 Contains the risk potential for
Dataset Value Hex fraud to occur on the card
5B account over the next 30 days.
Visa Risk Note: Tag 02—Risk Condition
Assessment Data Code may not be present in all
Tag: 02 transactions.
Risk Condition
Code
Length: 2
Format: AN

54 Visa Confidential 21 October 2021

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name

Field 104, Usage 2, TCR 3, pos. 19-20 AA (account-to-account Inclusion of a valid BAI is
Dataset Value Hex Business Application Money Transfer) required for AFTs as specified
57 Identifier (BAI) BI (Financial institution- in Table 2-1 AFT Categories.
Business offered P2P Money Transfer) Important: A valid BAI is
Application PP (person-to-person required for all AFTs globally.
Identifier (BAI) Money Transfer) Note: V.I.P will reject any AFT
Tag: 01 transaction without a valid BAI
TU (prepaid top-up/reload)
with reject code 0494 (Field or
Length: 2 WT (Wallet Transfer) data missing or invalid).
Format: AN FT (Funds Transfer)

Field 104, Usage 2, N/A LAC Only

Dataset Value Hex Added to support business
63 sender tax identification in
Business Sender AFTs. The recipient’s tax ID is
Tax Identification sent to the sender cardholder’s
Tag: 05; issuing bank.

Length: 20; Note: This field is mandatory

for domestic and cross-border
Format: AN
transactions originated in
Argentina, Brazil, Colombia,
Ecuador, and Peru. Issuers may
need this information for
reporting or for other
regulatory reasons. This list is
not exhaustive and not limited
only to the countries listed.
Contact your regional Visa
representative to confirm if this
field is required in your country.
V.I.P. Edit: For Brazil domestic
transactions, V.I.P. rejects
transactions with reject code
0494 (Field or data missing or
invalid) if the transaction does
not contain Business Sender
Tax ID (Tag 05) and Individual
Sender Tax ID (Tag 06).

21 October 2021 Visa Confidential 55

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name

Field 104, Usage 2, N/A LAC Only

Dataset Value Hex Added to support individual
63 sender tax identification in
Individual Sender OCTs. The recipient’s tax ID is
Tax Identification sent to the sender cardholder’s
Tag: 06; issuing bank.

Length: 13; Note: This field is mandatory

for domestic and cross-border
Format: AN
transactions in Argentina,
Brazil, Colombia, Ecuador, and
Peru. Issuers may need this
information for reporting or for
other regulatory reasons. This
list is not exhaustive and not
limited only to the countries
listed. Contact your regional
Visa representative to confirm if
this field is required in your
country.
V.I.P. Edit: For Brazil domestic
transactions, V.I.P. rejects
transactions with reject code
0494 (Field or data missing or
invalid) if the transaction does
not contain Individual Sender
Tax ID (Tag 06) and Business
Sender Tax ID (Tag 05).

56 Visa Confidential 21 October 2021

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name

Field 104, Usage 2, Field 104, Dataset ID 5F is a

Dataset ID 5F Tag-Length-Value (TLV)
Sender Data (Row 1 encoded field that is currently
of 3) effective from defined with eight different
23 April 2022 tags (Tag 01–Tag 08. 0A.)
Important:
All tags are conditional or
optional based on the
specific type of AFT (i.e.,
BAI), region and the
transaction specifics (e.g.,
domestic vs. cross-border).
Following basic TLV coding
principles, issuer systems
need to be flexible enough
to accommodate these
variations and flexible
enough to accommodate
new tags in this field as
they are introduced. If you
are not familiar with how
to code your system to
support TLV fields, please
contact your regional Visa
representative for support.
• Acquirers, service
providers, and merchants
must not format tags as
right-justified with leading
spaces.
• Acquirers, service
providers, and merchants
should not pad tags to
their maximum length with
spaces or binary zeros.

21 October 2021 Visa Confidential 57

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name

Field 104 Usage 2, V.I.P. Edit:

Dataset ID 5F This field should not be
Sender Data (Row 2 present in responses
of 3) effective from (authorization or full financial)
23 April 2022 and if present, it will be
dropped from the message by
V.I.P.
If the acquirer, service
provider, or merchant does not
provide a given tag in this
dataset, the tag must be
omitted from the message. If
any of Tags 01 to 07 are
included and filled with all
spaces or all zeros, V.I.P. will
decline the transaction with
the response code value of 64
(Transaction does not fulfill
AML requirements).
V.I.P. Edit (Money Transfers):
• On Money Transfer
transactions
(Processing Code 10
and BAI of AA/PP, or
BI), if the issuer PCR is
not set up in the
VisaNet system to
support Field 104 in
TLV format, V.I.P. will
decline the transaction
with the response
code value of 57
(Transaction not
permitted to
cardholder).

Field 104, Usage 2, V.I.P. Edit (All AFTs Other

Dataset Value Hex Than Money Transfer): If the
5F issuer PCR is not set up in the
Sender Data VisaNet system to support
Field 104 in TLV format and
this field is present in the
message, Visa drops Field 104

58 Visa Confidential 21 October 2021

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name
Note: This field is from the message and
Tag-Length-Value forwards the transaction to the
(TLV). issuer.
(Row 3 of 3) V.I.P. Edit (All AFTs) If the
effective from 23 issuer PCR is not set up to
April 2022 support Processing Code 10,
VIP will convert the AFT to a
purchase (processing code 00)
and drop Field 104, Dataset
Value Hex 5F Sender Data
V.I.P. Edit (All AFTs): VIP
rejects AFTs with the existing
reject code 0494 (Field or data
missing or invalid) for which
any of the following tags in
Field 104 Dataset ID 5F
exceeds its maximum length:
Tags 01–07 and 0A.

Field 104 (Row 1 of Positions: 74–103 Cross-border: Must contain This field contains the name of
2), Usage 2, Dataset Length: 30 sender’s name. the person or entity funding
Value Hex 5F U.S., Canada, and Europe the AFT.
Format: AN
Tag: 03 Domestic: Must contain Sender Name Example:
Length: 30 sender’s name. The Sender Name can be up to
Format: AN, AP Domestic: This field is thirty characters long and must
EBCDIC strongly recommended for be the sender’s legal name. If
issuer compliance purposes. the sender’s name is greater
Sender Name
Not including this field may than thirty (30) characters, use
effective from 23 result in poor acceptance only the first thirty characters
April 2022 rates. of the name. The required
Other Domestic: May format for the Sender Name
contain sender’s name; if not field is:
applicable, do not include • Last Name/Family Surname
the tag. 1 plus space
Note: Sender’s name must • Last Name/Family Surname
be populated using the Latin 2 (optional) plus space
(i.e., English) character set • First Name plus space
and be an actual person’s • Middle Initial or Middle
name. Use of a phone Name (optional) plus space
number, email address or •
alias is not permitted. Notes:

21 October 2021 Visa Confidential 59

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name
o This field must not
contain special
characters.
o Only a valid and legal
sender name should
be populated in this
field.
Examples:
• Doe Jane A.
• Vellaichary Jabachardinat
Savi

Field 104 (Row 1 of N/A Cross-border: This field contains the name
2), Usage 2, Dataset See Note. Recipient name mandatory of the person or entity
Value Hex 5F in cross-border Money receiving the funds. Recipient
Tag: 0A Transfer AFTs name is mandatory for cross
border money transfer AFTs.
Length: 30 U.S. Domestic:
Issuers must be prepared to
Format: AN, Optional in domestic AFTs
receive
EBCDIC Europe Domestic Tag 0A/Recipient Name in any
Recipient Name18 Recipient name mandatory AFT.
effective from 23 in domestic and intra-EEA The maximum length of the
April 2022 Money Transfer AFTs recipient name is 30
AP Domestic: This field is characters.
strongly recommended for Recipient Name Example:
issuer compliance purposes.
The Recipient Name can be up
Not including this field may
to thirty characters long, and
result in poor acceptance
must be the recipient’s legal
rates.
name. If the recipient’s name is
greater than thirty (30)
characters, use only the first
thirty characters of the name.
The suggested format for the
Recipient Name field is:
• Last Name/Family Surname
1 plus space
• Last Name/Family Surname
2 (optional) plus space

18 Effective 23 April 2022, Visa will also require recipient account number or reference number to be included in all AFTs.
Field number to be defined and published at a later date.

60 Visa Confidential 21 October 2021

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name
• First Name plus space
• Middle Initial or Middle
Name (optional) plus space
•
Notes:
• This field must not contain
special characters.
• Only a valid and legal
recipient name should be
populated in this field.
Examples:
• Doe Jane A.
• Vellaichary Jabachardinat
Savi
Requirements for support of
Recipient Name in responses,
etc., are the same as for
Sender Name in Field 104
Dataset ID 5F.
In case of money load
programs or money transfer
programs, the Recipient is the
person in whose name the
payment account is opened
with the regulated merchant
originating the AFT.
In case of pass-through money
transfer programs, where the
regulated merchant doesn’t
operate payment accounts, ,
the Recipient is the regulated
merchant effecting the money
transfer

Field 104, Usage 2, Positions: 104–138 Cross-border: Must contain For Money Transfer, prepaid
Dataset Value Hex Length: 35 sender’s address. load, this should be the
5F U.S. Domestic: Must contain sender’s primary address.
Format: AN
Tag: 04 sender’s address. For Funds Disbursement, this
Sender Address
Length: 35 Europe intra-EEA cross should be the merchant or
border: Must contain government entity’s primary
Format: AN
sender’s address business address in the

21 October 2021 Visa Confidential 61

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name
Sender Address Other Domestic: May country where the transaction
effective from 23 contain sender’s address; if was initiated
April 2022 not required, do not include
this tag.

Field 104, Usage 2, Positions: 139–163 Cross-border: Must contain

Dataset Value Hex Length: 25 sender’s city.
5F U.S. and Canada Domestic:
Format: AN
Tag: 05 Must contain sender’s city.
Sender City
Length: 25 Europe intra-EEA cross
Format: AN border: Must contain
sender’s address
Sender City
Other Domestic: May
effective from 23
contain sender’s city; if not
April 2022
required, do not include this
tag.

Field 104 (Row 1 of Positions: 164–165 Domestic and Cross-border The geographical state or
2); Usage 2; Dataset from U.S. or Canada: Must province associated with the
Length: 2
Value Hex 5F; Tag: contain sender’s sender’s primary residential
Format: AN address.
06; Length: 2; state/province in this field on
Format: AN Sender State/ cross-border transactions
Province when Sender Country (Tag
Sender
State/Province Other Domestic and 07) contains the value of 840
Cross-Border: May (U.S.) or
effective from 23
contain sender’s 124 (Canada).
April 2022
state/province; if not
required, do not
include this tag.

Field 104 (Row 1 of Positions: 166–168 Cross-border: Must contain

4), Usage 2, Dataset Length: 3 sender’s country.
Value Hex 5F U.S., Canada and Europe
Format: AN
Tag: 07 Domestic: Must contain
Sender Country
Length: 3 sender’s country.

Format: AN Note: Sender country must

be the sender’s place of
Sender Country
residence.
effective from 23
Other Domestic: May
April 2022
contain sender’s country; if
not required, do not include
this tag.

62 Visa Confidential 21 October 2021

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name
Notes:
• This is the
3-digit ISO numeric
country code.
• Sender country must be
the sender’s place of
residence.

Field 119, Usage 5; LAC only:

Settlement Service For domestic transactions in
Data Argentina, acquirers and
Length: 139 issuers can submit and settle
OCTs in the Argentina NNSS.
Format: ANS,
EBCDIC This field contains settlement
information unique to the
processing of Visa transactions
by participants in a given
country.
Note: This field is forwarded
from the acquirer to the issuer
only if the transaction qualifies
for the NNSS. If the transaction
does not qualify for the NNSS,
Visa removes the field from
the message.
V.I.P Edit: V.I.P. rejects the
transactions with reject code
0132 (Invalid Country Code) if
Positions 1–3, Country Code
does not contain a value of
032 (Argentina),

Field 123 Address n/a Zip code or full address AVS is required in the U.S for
Verification Data Note: Zip code can be 5 or 9 CPS qualification for card-not-
Length: 1 byte, characters. present transactions.
binary + Fixed Note: AVS Results Code will be
Format: 29 ANS, returned in Field 44.2 of the
EBCDIC; maximum response message.
30 bytes
Bytes 2-10: Postal
Code

21 October 2021 Visa Confidential 63

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name
Bytes 11-30: Card
holder street
address

Field 126.9 n/a This field may be present in an

CAVV Data AFT. Refer to the V.I.P. manuals
for information about this
Length: 20 bytes,
field.
fixed
Format: Binary

Field 127, Dataset Field 127 is a requirement

ID 41 when participating in Real-
Replacement PAN time Visa Account Updater
(VAU).
Length: 13-19
Required when the Primary
Format: N, BCD
Account Number (PAN)
Tag 01 contained in Field 2—Primary
Account Number is being
replaced with a new PAN.

Field 127, Dataset Contains the expiration date of

ID 41 the new PAN in Tag 01 or the
Replacement PAN updated expiration date of the
Expiration Date existing PAN.

Length: 4 Format = yymm.

Format: N, BCD
Tag 02

64 Visa Confidential 21 October 2021

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name

Field 127, Dataset • A (Account number Indicates the account status.

ID 41 change (the account
Account Status number or account
number and expiration
Length: 1
date are being updated))
Format: AN,
• C (Closed account
EBCDIC
advice)
Tag: 04
• E (Expiration date
change)
• Q (Contact cardholder
advice (the merchant
should contact the
cardholder for additional
information on the
account))

Field 127, Dataset Valid values are: This field indicates if

ID 41 • Y (Requesting for replacement occurred in the
Request from replacement PAN response message sent to the
Merchant for details) originating entity.
Updated Account • Y (Replacement
Length: 1 occurred)
Format: AN, • N (No replacement)
EBCDIC
Tag: 07

Field 127, Dataset • VAU001 (Transaction did Indicates the reason a

ID 41, not qualify for Real Time transaction did not qualify for
Error Reason Code Visa Account Updater account information
(VAU) because the replacement.
Length: 6
transaction contains
Tag: 09 token)
• VAU002 (Real Time VAU
is supported only for
Visa branded PAN)
• VAU003 (Real Time VAU
is not supported for the
network)
• VAU004 (Transaction is
not original purchase,
bill payment, account

21 October 2021 Visa Confidential 65

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name
funding, or original
credit)
• VAU005 (Transaction
contains CVV2)
• VAU006 (Transaction is
not a qualifying
recurring or installment
transaction type)
• VAU007 (Real Time VAU
is not supported for this
MCC)
• VAU008 (Acquirer of
processor is not
activated for Real Time
VAU)
• VAU009 (Issuer does not
support Real Time VAU)
• VAU010 (Issuer or Visa
blocked the merchant)
• VAU011 (PPCS has a
stop payment order for
this transaction)
• VAU012 (Credentials in
the authorization
request is the latest VAU
data)
• VAU013 (Expiry date in
the authorization
request is later than VAU
data)
• VAU014 (PAN has been
opted out of VAU)
• VAU015 (Transaction is a
face-to-face transaction
type)
• VAU016 (PAN has stop
advice set up)

66 Visa Confidential 21 October 2021

 AFT Data Elements and Processing Rules
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

V.I.P. BASE II Value Notes/VisaNet Edits/

(0100/0200) (TC05) Requirements
Field Name Field Name

n/a All TCRs, pos. 3 Value = 1 Note: TCQ value of 1 must be

present in all AFTs.
Transaction Code
Qualifier (TCQ)
Length: 1
Format: AN

21 October 2021 Visa Confidential 67

 BAI Acronyms and Glossary
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

B BAI Acronyms and Glossary

This appendix contains a list of BAI acronyms as well as a glossary of terms.

B.1 Business Application Identifier (BAI) Acronyms

Following is the complete list of Business Application Identifiers. Bold entries indicate BAIs permitted
for AFTs.

Note: VisaNet system does not have edits to prevent misuse of the BAI. The acquirer, service provider,
and merchant are responsible to ensure the use of the correct BAI.
Table B-1: Business Application Identifier (BAI) Acronyms (permitted BAIs for AFTs in bold)
Acronyms Meaning
AA Account-to-Account
BB Supplier Payments
BI Bank Initiated P2P Money Transfer
BP Non-card Bill Pay / Bill Pay
CD Cash Deposit
CI Cash In (Deposit)
CO Cash Out (Withdrawal)
CP Credit Card Bill Payment
FD Funds Disbursement
FT Funds Transfer
GD Government Disbursement
GP Gambling payout (non-online gambling)
LO Loyalty credits and rebates
MD Merchant Settlement
MP Merchant Payment
OG Online Gambling Payout
PD Payroll and pension disbursement
PP Person-to-Person or Peer-to-Peer
TU Top Up (Prepaid Load)
WT Wallet Transfer (for Staged Digital Wallets - wallets with a proprietary
merchant acceptance network).

68 Visa Confidential 21 October 2021

 BAI Acronyms and Glossary
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

B.2 Glossary

Table 3-3: Glossary

Term Definition

Access Channel A channel, such as an ATM or a mobile app, provided by an

originator to offer AFT program services to its customers.

Account Funding Transaction (AFT) A Transaction where funds are pulled from a Visa account and
are subsequently used to fund another Visa or non-Visa account.
Required when loading a prepaid card account, moving funds
into another financial account, funding a person-to-person
Money Transfer, funding payroll disbursements, or adding value
to a digital wallet.

Account-to-Account (AA) An AFT in which the funds will be transferred to another of the
cardholder’s own accounts at the same or a different financial
institution (Me-to-Me money transfer transaction).

Acquirer In relation to AFTs, a licensed Visa client that originates

transactions or that sponsors a third party agent to originate
transactions. Acquirers are responsible and liable for all AFT
programs that they operate or sponsor.

Address Verification Service (AVS) A VisaNet service through which a merchant verifies a
cardholder’s billing address. This service is available in the U.S.,
Canada, and Europe regions only.

AFT Program The AFT services and access channels that an originator offers to
its Visa cardholders.

Agent See third party agent.

Application Programming Interface (API) See Visa Direct Application Programming Interfaces (APIs)

Authorization Approving or declining a sales transaction before a purchase is

finalized or cash is disbursed. Issuers (or third party processors
acting on their behalf), or VisaNet, when standing in for issuers,
perform authorization.

21 October 2021 Visa Confidential 69

 BAI Acronyms and Glossary
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Term Definition

Business Application Identifier (BAI) A data element in the AFT message that identifies the business
application for which funds are being pulled from a Visa
account. Values are:
• AA (account-to-account Money Transfer)
• BI (Financial institution–offered P2P Money Transfer)
• FT (Funds Transfer)
• MP (Merchant Payment for scan-to-pay programs only)
• PP (person-to-person Money Transfer)
• TU (prepaid card top-up)
• WT (adding value to a Staged Digital Wallet)
Back-to-Back Funding A payment flow that automatically transfers value via a funding
transaction or transaction that is directly connected to a specific
purchase.
In Back-to-Back Funding:
• Two separate accounts are involved. One account is used to
make the purchase, and the other automatically funds or
reimburses that account.
• Both accounts are held by the same person or corporate
entity, and at least one account is a Visa account.
In Back-to-Back Funding, either:
• The funding or reimbursement amount exactly matches the
amount of the purchase.
• The purchase is partially funded by an existing balance, and
the funding or reimbursement transaction or transaction
amount equals the remainder of the purchase amount.
Back-to-Back Funding does not include:
• An Unscheduled credential-on-file transaction for a fixed
amount to reload the account
• The funding of a card that accesses funds on deposit at an
organization other than that of the issuer of the card
(“decoupled debit”)

Card Verification Value 2 (CVV2) A card verification tool used by issuers to validate that a genuine
payment card is present at the cardholder location during a
transaction.

Digital Wallet An electronic device that allows an individual to make electronic

commerce transactions, such as purchasing an item online with a
computer or using a smartphone to purchase something at a
store.

70 Visa Confidential 21 October 2021

 BAI Acronyms and Glossary
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Term Definition

European Economic Area (EEA) European Economic Area (EEA), which includes the member
states of the European Union, and Iceland, Liechtenstein and
Norway. Countries/member states include Austria, Belgium,
Bulgaria, Croatia, Republic of Cyprus, Czech Republic, Denmark,
Estonia, Finland, France, Germany, Greece, Hungary, Ireland,
Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland,
Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, in addition
to Iceland, Liechtenstein, and Norway.

Facilitator See third party agent.

Financial Institution–Offered P2P Money A P2P Money Transfer offered by a financial institution through
Transfer their own mobile or online banking application.

Foreign Exchange Rate API An API that allows the originator to look up the current day’s
foreign exchange rate using Visa rates and, using this rate, to
convert the amount in the originator’s currency to the amount in
the recipient’s currency.

Funds Transfer API The financial API used to initiate an AFT and its associated
reversal.

ISO 8583 Message International Organization for Standardization financial

transaction card–originated message specifications for systems
that exchange electronic transactions made by cardholders
using payment cards. Basis of Visa's V.I.P. message format (BASE
I and SMS).

Issuer The Visa client financial institution that has entered into a
contractual relationship with a cardholder for the issuance of
one or more Visa card products. Issuers receive authorization
requests for AFTs and debit the cardholder’s account
accordingly.

Merchant A merchant is defined as an entity that enters into an agreement

with an acquirer for the acceptance of cards for purposes of
originating payment transactions under the Visa-Owned Marks.

In the context of AFTs, a merchant is an entity requesting the

initiation of AFTs only for themselves and their customers.
Merchants must be sponsored directly by an acquirer or on
boarded through an acquirer-sponsored service provider.
Merchant Category Code (MCC) A code designating the principal trade, profession, or line of
business in which a merchant is engaged.

Money Transfer The ability for an individual to send funds from his or her Visa
account to a different, non-merchant account.

21 October 2021 Visa Confidential 71

 BAI Acronyms and Glossary
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Term Definition

Non-Merchant Account A financial account that is eligible to receive a funds transfer

initiated by an AFT.

Original Credit Transaction (OCT) A VisaNet transaction that can be used to send funds to an
eligible Visa account. Visa acquirers can use the OCT to enable
services such as Money Transfers, funds disbursements, prepaid
loads, and credit card bill payments.

Origination Program See AFT program.

Originator Term no longer used. Replaced with acquirer, service provider,

and/or merchant as applicable. Formerly: An entity (a Visa
acquirer or a sponsored third party agent) that generates AFTs as
a service to its customers.

Payment Account Attributes Inquiry API An API that allows the merchant, service provider or acquirer to
obtain information about the sender's account and to determine
whether domestic and cross-border AFT eligibility is available for
the sender’s or recipient’s non-Visa accounts.

Payment Account Validation API An API that allows the merchant, service provider or acquirer to
perform CVV2 and/or address verification on the sender’s
account.

Person-to-Person (PP) Money Transfer in which AFT funds will be sent to another
individual’s non-merchant account.

Prepaid Load (TU) An AFT in which the funds will be used to add value to a prepaid
card.

Purchase Transaction A VisaNet transaction using Transaction Code (TC) 05 or

Processing code of 00.

Push Payment Gateway Service (PPGS) (U.S. region only) Allows originators in the U.S. to send AFTs to
Visa for routing to multiple U.S. debit networks.

Real Time Visa Account Updater (VAU) Visa Account Updater (VAU) is a service that facilitates
exchanging updated account information between participating
merchants and Visa card issuers and thus encouraging customer
satisfaction, retention and loyalty. Real Time VAU is a feature
that eliminates the multi-step process to update account
information.

Receiving Account The account that will receive the funds that have been pulled by
an AFT.

Recipient The person who owns the account that receives the funds pulled
by an AFT.

72 Visa Confidential 21 October 2021

 BAI Acronyms and Glossary
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Term Definition

Recipient Issuer The issuer of the card account that receives the funds pulled by
an AFT.

Sender A customer of the merchant or service provider (consumer or

business) who initiates the transfer of funds (pull) from their Visa
card account to fund a different, non-merchant account.

Sender's Issuer The Visa client financial institution that issued the Visa card used
to fund an AFT. The issuer authorizes the transaction and debits
the sender’s Visa account.

Sending Account The Visa account from which the funds for an AFT are pulled.

Service Provider An acquirer sponsored third party entity that enables AFT-based
services on behalf of an acquirer or offers AFT-based services to
merchants.

Standard Purchase Transaction A transaction that pulls funds from a Visa account for the
purpose of purchasing goods and services or otherwise funding
a merchant account.

Staged Digital Wallet (SDW) A wallet where funds can be added and stored to a digital
account with a proprietary merchant acceptance network. The
funds can be used to:
• send to other wallet users
• to make payments at multiple merchants under the
operator’s proprietary brand mark
• Cashed out to an unaffiliated account
Staged Digital Wallets are permitted to facilitate Back-to-Back
Funding transactions, but must not have a general-purpose
payment network card/account at the “front” of the wallet.

Stored Value Digital Wallet A wallet where funds can be added and stored to a non-Staged
Digital Wallet account. The funds can be used to send to other
users, make payments to multiple merchants, or to cash out to
an unaffiliated account.
Stored Value Digital Wallets must limit usage to the available
balance in the wallet and must not facilitate real-time or live-
load Back-to-Back Funding. SVDW may have a general-purpose
payment network card/account at the “front” of the wallet.

21 October 2021 Visa Confidential 73

 BAI Acronyms and Glossary
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Term Definition

Third Party Agent An entity, not defined as a VisaNet Processor, that provides
payment-related services to a client and/or that stores,
transmits, or processes cardholder data. In the context of AFT
programs, any third party entity or service provider that
manages or facilitates AFT programs; e.g., payment facilitators,
load partners, etc.

Top Up (TU) See prepaid load.

Visa Account Updater (VAU) Is a key service to support payment continuity in recurring billing
and credential-on-file segments. Real Time VAU is a feature that
eliminates the multi-step process to update account
information.

Visa Secure A Visa-approved authentication method based on the 3-D

Secure Specification.

Visa Developer Center (VDC) A website (https://developer.visa.com/ ) (Visa Direct:

https://developer.visa.com/capabilities/visa_direct/ ) that
provides developers with information and resources for their
Visa Direct API development activities. Developers can access
functional codes, documentation, SDKs, and sandboxes.

Visa Developer Platform (VDP) See Visa Developer Center.

Visa Direct The Visa product platform that provides funds transfer
capabilities using AFTs and OCTs.

Visa Direct Application Programming Web services–based request and response messages that
Interfaces (APIs) originators can use to communicate with Visa to initiate AFTs
and to support related value-added services.

74 Visa Confidential 21 October 2021

 BAI Acronyms and Glossary
Account Funding Transaction (AFT): Processing Guide: Visa Supplemental Requirements

Term Definition

VisaNet The systems and services, including the V.I.P. System, and BASE
II, through which Visa delivers online financial processing,
authorization, clearing, and settlement services to clients.

Wallet Transfer (WT)

An AFT in which the funds will be used to add value to a digital
wallet with a non-general-purpose payment network brand
acceptance mark. BAI = WT is used only for Staged Digital
Wallets in the following circumstances:

• In AFTs when funding a Staged Digital Wallet before the

cardholder makes a purchase

• To fund a purchase when initiated by the Staged Digital

Wallet provider and corresponding to, or otherwise
directly connected to a specific purchase (also called
Back-to-Back Funding live-load or real-time funding). In
this scenario, the transaction must be processed as a
purchase transaction, with a BAI value = WT.

- When a transaction is performed to give back to a cardholder

funds that were held in a Staged Digital Wallet, this cash out
transaction must be processed as an Original Credit (OCT) with a
BAI = WT.

21 October 2021 Visa Confidential 75