0% found this document useful (0 votes)
193 views157 pages

Account Funding Transaction AFT Processing Guide

The Visa Direct Account Funding Transaction (AFT) Processing Guide outlines the procedures and requirements for executing AFTs, which allow funds to be pulled from a Visa account to fund another account. It emphasizes that AFTs are not intended for payments for goods or services and must adhere to specific guidelines regarding account ownership and transaction types. The guide also details the necessary compliance and technical considerations for participants involved in AFT transactions.

Uploaded by

badr eddine
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
193 views157 pages

Account Funding Transaction AFT Processing Guide

The Visa Direct Account Funding Transaction (AFT) Processing Guide outlines the procedures and requirements for executing AFTs, which allow funds to be pulled from a Visa account to fund another account. It emphasizes that AFTs are not intended for payments for goods or services and must adhere to specific guidelines regarding account ownership and transaction types. The guide also details the necessary compliance and technical considerations for participants involved in AFT transactions.

Uploaded by

badr eddine
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 157

Visa Direct Account Funding

Transaction (AFT)
Processing Guide

Effective: 15 April 2023

Version 1.12

Visa Supplemental Requirements

© 2021-2023 Visa. All Rights Reserved.


Visa Confidential
Important Information on Confidentiality and Copyright

Notice: The Visa Confidential label signifies that the information in this document 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.

Note:

This document is not part of the Visa 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 Rules, the Visa Rules shall govern and control.

Visa does not provide legal, regulatory, tax or financial advice. Each participant is fully responsible for ensuring that its
program operates in compliance with applicable legal and regulatory requirements and is responsible for conducting
independent legal and regulatory reviews through its legal counsel.

THIS PUBLICATION COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE
PERIODICALLY ADDED TO THE INFORMATION HEREIN: THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS
OF THE PUBLICATION. VISA MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE
PROGRAM(S) DESCRIBED IN THIS PUBLICATION AT ANY TIME.

If you have technical questions or questions regarding a Visa service or questions about this document, please
contact your Visa representative.
Contents
Chapter 1 • Account Funding Transaction (AFT) Overview
About This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Summary of Changes in This Version. . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Audience and Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Acronyms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Related Publications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Comparison of AFTs with Purchase and Quasi-Cash Transactions. . . . . . . . . . . . . . 16

Chapter 2 • Requirements and Considerations for AFT Origination


AFT Program Business Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . 20

Requirements for Submitting a PIF. . . . . . . . . . . . . . . . . . . . . . . . . .22

AFT Processing Requirements and Considerations. . . . . . . . . . . . . . . . . . . . . 23

AFT Processing and Message Format. . . . . . . . . . . . . . . . . . . . . . . . 23

Business Application Identifier (BAI). . . . . . . . . . . . . . . . . . . . . . . 24

Merchant-Initiated Transactions/Recurring Transactions. . . . . . . . . . . . . . . 31

Cross-Border AFTs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Partial Authorization (U.S. Domestic Only). . . . . . . . . . . . . . . . . . . . . . 34

Key AFT Data Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Custom Payment Service (CPS) (U.S. Only). . . . . . . . . . . . . . . . . . . . 34

Acquirer, Service Provider, and Merchant Network Routing Options. . . . . . . . . . . 35

VisaNet Connectivity Using ISO Messaging. . . . . . . . . . . . . . . . . . . . 35

Application Programming Interfaces (APIs). . . . . . . . . . . . . . . . . . . . 35

Push Payment Gateway Service . . . . . . . . . . . . . . . . . . . . . . . . . 37

AFTs for Proprietary Card Products. . . . . . . . . . . . . . . . . . . . . . . . 37

Transaction Coding at Remote Channels (CEMEA). . . . . . . . . . . . . . . . . . . 38

AFT Program Customer Requirements and Considerations. . . . . . . . . . . . . . . . . 38

AFT Risk Requirements and Considerations. . . . . . . . . . . . . . . . . . . . . . . .39

Risk Management – General Considerations. . . . . . . . . . . . . . . . . . . . . 39

15 April 2023 Visa Confidential 3


Visa Direct Account Funding Transaction (AFT) – Processing Guide

Cardholder Data Authentication Requirements. . . . . . . . . . . . . . . . . . . . 40

Digital Authentication Framework. . . . . . . . . . . . . . . . . . . . . . . . . . 40

Transaction Monitoring and Screening. . . . . . . . . . . . . . . . . . . . . . . . 41

Fraud Detection and Prevention. . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Push Payments Tokenization. . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Real Time Visa Account Updater (VAU). . . . . . . . . . . . . . . . . . . . . . . . 44

Account Verification and Related Services. . . . . . . . . . . . . . . . . . . . . . 44

Data Security – PCI Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . 45

AFT Refund Use Case. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

AFT Reporting Requirements for Originating Entities. . . . . . . . . . . . . . . . . . . .54

AFT Certification Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Chapter 3 • Issuer Requirements and Considerations


Receiving and Processing AFTs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Risk and Disputes for Issuers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Using Visa Velocity Limit Checking to Mitigate Risk. . . . . . . . . . . . . . . . . . 57

Issuers – Dispute Resolution. . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

AFT Refund – Processing Considerations. . . . . . . . . . . . . . . . . . . . . . . 60

Sanctions Screening Scoring Service. . . . . . . . . . . . . . . . . . . . . . . . . . .60

Issuer Reporting Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Issuer Certification Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Appendix A • AFT Data Elements and Processing Rules


AFT Key Data Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Appendix B • Purpose of Payment – Standardized Codes List

Appendix C • API Formats


ISO Fields – API Field Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Appendix D • Transaction Flows

15 April 2023 Visa Confidential 4


Visa Direct Account Funding Transaction (AFT) – Processing Guide

AFT Flow – SMS Originating Entity to SMS Issuer (Approval/Decline). . . . . . . . . . . . 135

AFT Flow – SMS Originating Entity to Dual Message/BASE II Issuer (Approval/Decline). . . . 136

AFT Flow – Dual Message Originating Entity to SMS Issuer (Approval/Decline). . . . . . . . 138

AFT Flow – Dual Message Originating Entity to Dual Message/BASE II Issuer (Approval/
Decline). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139

Credit Adjustment: SMS Originating Entity to SMS Recipient Issuer. . . . . . . . . . . . . 140

Credit Adjustment: SMS Originating Entity to Dual Message/BASE II Recipient Issuer. . . . . 141

Credit Adjustment: Dual Message Originating Entity to SMS Recipient Issuer. . . . . . . . .142

Credit Adjustment: Dual Message Originating Entity to Dual Message/BASE II Recipient Issuer 143

Issuer Response Delay – SMS Originating Entity to SMS Issuer (Results in Decline). . . . . . 144

Issuer Response Delay – SMS Originating Entity to Dual Message/BASE II Issuer (Results in
Decline). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145

Issuer Response Delay – Dual Message Originating Entity to SMS Issuer (Results in Decline). . 147

Issuer Response Delay – Dual Message Originating Entity to Dual Message/BASE II Issuer
(Results in Decline). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Appendix E • BAI Acronyms and Glossary


Business Application Identifier (BAI) Acronyms. . . . . . . . . . . . . . . . . . . . . . 149

Glossary

15 April 2023 Visa Confidential 5


Chapter 1
Account Funding Transaction (AFT)
Overview

The Account Funding Transaction (AFT) is a transaction in which 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.

15 April 2023 Visa Confidential 6


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Account Funding Transaction (AFT) Overview

The following is a requirement for all acquirers supporting merchant programs:


l 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.
l An AFT is the required pull transaction to be used to fund the following scenarios in a card
not present environment:
n Disbursement of funds from Visa Corporate cards, Visa Business Debit cards, or Visa
Business Check cards (e.g., payroll)
n Funding a person-to-person account (P2P) Money Transfer via a subsequent transaction
(e.g., funding an OCT, bank transfer, etc.)
n Moving funds from one account to another (A2A) (e.g., funding a checking account,
savings deposit, or retirement account) where the funding account belongs to the same
individual or entity holding the wallet account.
n 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.
n Prepaid card load/reload.
Note: Effective 23 April 2022 – EU is required to comply with the above requirements.
Note: Effective October 2022 – All issuers are required to support Domestic and Cross-
border AFTs in AP and EU.
*When a Visa card is used to fund a registered Staged Digital Wallet, 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:
l In AFTs when funding a digital wallet before the cardholder makes a purchase
l 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: 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).
As shown in the figure, 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, or other non-merchant
account, a wallet, or a prepaid card.

15 April 2023 Visa Confidential 7


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Account Funding Transaction (AFT) Overview

AFT "Pull" Transaction with Subsequent "Push" Transaction

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.

15 April 2023 Visa Confidential 8


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Account Funding Transaction (AFT) Overview

About This Guide


The Account Funding Transaction (AFT) is a transaction in which 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 account), acting as a
funding source for person-to-person (P2P) Money Transfers or loading third-party digital wallets.
This document provides:
l An overview of the AFT
l AFT requirements and guidelines for acquirers
l Program considerations for acquirers, service providers, and merchants
l Processing guidelines and best practices for issuers

Summary of Changes in This Version


This version of the Account Funding Transaction (AFT): Processing Guide contains updates for these
topics. Changes also include minor edits and modifications for clarity and accuracy of rules. Principal
changes are highlighted in the Guide with change bars.

Table 1: Version 1.12 Summary of Changes (1 of 4)

Chapter Description
2 – Requirements and Consider­ Requirements for Submitting a PIF
ations for AFT Origination
Updated this section to clarify when to submit a new PIF.

2 Business Application Identifier (BAI)


Table – AFT Categories - Money Transfer

l BAI – FT: Added MCC 6051


l BAI – WT: Added a note to mandate Sender and Recipient information
for cross-border AFTs
l BAI – TU: Added to Money Transfer category
Table – BAI and MCC usage for P2P and Digital Wallet Programs

l Clarified MCC 6051 usage under Financial Institution

2 Cryptocurrency – Use Case


Updated the AFT data requirements.

15 April 2023 Visa Confidential 9


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Account Funding Transaction (AFT) Overview

Table 1: Version 1.12 Summary of Changes (2 of 4)

Chapter Description
2 Partial Authorization
Minor updates to the section.

2 Application Programming Interfaces (APIs)


Added Funds Transfer Attributes Inquiry (FTAI) API

2 Transaction Coding at Remote Channels (CEMEA)


Updated the section to announce:

l the effective end date to use other ECI values


l transactions of participating merchants and token requestors are now
eligible for Digital Authentication Framework (DAF)

2 Digital Authentication Framework (DAF)


Added Japan to the list of countries that are required to support receiving a
DAF indicator.

2 Account Verification and Related Services


Added a new section.

2 AFT Refund Use Case

l Minor updates to the section


l Updated TC06 to TC25 in Credit Adjustment flows
l Added new AFT Reversal flows

3 – Issuer Requirements and l Added LAC to the list of countries mandated to support AFTs
Considerations
l Added a new section – Sanctions Screening Scoring Service

15 April 2023 Visa Confidential 10


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Account Funding Transaction (AFT) Overview

Table 1: Version 1.12 Summary of Changes (3 of 4)

Chapter Description
Appendix A – AFT Key Data Table – AFT Key Data Elements
Elements
Updated the AFT Data Elements table with these changes relevant to AFTs.
Added:

l Field 34: New dataset and Tags C0, C1, C2, C3, C4, C5 and C6 to support
acquirer and merchant information
l Field 44.13: CAVV Results Code
l Field 59: New Dataset to support National Point-of-Service Geographical
Data
l Field 104: New Dataset to support Transaction Description and
Transaction-Specific Data
Updated:

l Field 3: Note – Added Europe and LAC to the list of countries


l Field 43: Card Acceptor Name/Location, including changes for Pos. 26 -
38
l Field 56: Account Identifier Reference Code - updated Valid Values
description
l Field 56: Customer Reference Number – Customer ID recipient required
for transactions within and out of Brazil
l Field 60.2: Updated the technical specification document name
l Field 60.10: Additional Authorization Indicators – mandated partial
authorization for U.S. Domestic only
l Field 104: Acceptor Legal Business Name – updated the note
l Field 104: Purpose of Payment – updated the note
l Field 104: Sender Data – V.I.P. edit
l Field 104: Recipient Name – V.I.P. edit
l Field 104: Business Sender Tax Identification – updated the field name,
note and V.I.P. edit
l Field 104: Individual Sender Tax Identification – updated the field name,
note and V.I.P. edit
l Field 126.8: Updated the value description
l Field 126.9: Updated the value description and technical specification
document name

Appendix B – Purpose of Payment Added a note to clarify not all codes may be applicable to an AFT.
- Standardized Codes List

15 April 2023 Visa Confidential 11


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Account Funding Transaction (AFT) Overview

Table 1: Version 1.12 Summary of Changes (4 of 4)

Chapter Description
Appendix C – API Formats ISO Field - API Field Mapping
Added and updated these V.I.P. fields and their corresponding API field
name:

l Field 60.10 – Additional Authorization Indicators


l Field 104 – Sender Account Number
l Field 104 – Merchant VAT Registration/Single Business Reference Number
l Field 104 – Customer VAT Registration Number

Appendix D – Transaction Flows Added these transaction flows under:


AFT Flow:

l SMS Originating Entity to SMS Issuer (Approval/Decline)


l SMS Originating Entity to Dual Message/BASE II Issuer (Approval/Decline)
l Dual Message Originating Entity to SMS Issuer (Approval/Decline)
l Dual Message Originating Entity to Dual Message/BASE II Issuer
(Approval/Decline)
Credit Adjustment:

l SMS Originating Entity to SMS Recipient Issuer


l SMS Originating Entity to Dual Message/BASE II Recipient Issuer
l Dual Message Originating Entity to SMS Recipient Issuer
l Dual Message Originating Entity to Dual Message/BASE II Recipient Issuer
Issuer Response Delay:

l SMS Originating Entity to SMS Issuer – Results in Decline


l SMS Originating Entity to Dual Message/BASE II Issuer – Results in
Decline
l Dual Message Originating Entity to SMS Issuer – Results in Decline
l Dual Message Originating Entity to Dual Message/BASE II Issuer – Results
in Decline

Glossary Added new terms:

l Account Name Inquiry (ANI)


l Account Verification
Updated:

l Account Funding Transaction (AFT)


l Merchant

15 April 2023 Visa Confidential 12


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Account Funding Transaction (AFT) Overview

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.
Note: 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 has been replaced with originating entities and may refer to
acquirers, merchants, and service providers, as applicable, throughout the guide.
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.

Acronyms
This table contains a list of AFT-related acronyms.

Table 2: Acronyms (1 of 3)

Acronyms Meaning
3DS 3-D Secure

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

ACNL Account Lookup

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

CAVV Card Account Verification Value

CVV2 Card Verification Value 2

15 April 2023 Visa Confidential 13


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Account Funding Transaction (AFT) Overview

Table 2: Acronyms (2 of 3)

Acronyms Meaning
DAF Digital Authentication Framework

DEX Direct Exchange

DPP Digital Payment Platform

ECI Electronic Commerce Indicator

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

SDW Staged Digital Wallet

SDWO Staged Digital Wallet Operators

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

SVDW Stored Value Digital Wallet

TAVV Token Authentication Verification Value

TCQ Transaction Code Qualifier

TU Top-Up (Prepaid Load)

VAA Visa Advanced Authorization

VAU Visa Account Updater

VCMS VisaNet Certification Management Service

VOL Visa Online

VRM Visa Risk Manager

VSS VisaNet Settlement Service

VTA Visa Transaction Advisor

15 April 2023 Visa Confidential 14


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Account Funding Transaction (AFT) Overview

Table 2: Acronyms (3 of 3)

Acronyms Meaning
WT Wallet Transfer (Staged Digital Wallets only)

WTMO Wire Transfer Money Orders

Related Publications
Below is a list of other relevant documents.
The current versions of these documents are available on Visa Online (www.visaonline.com) or
through your Visa representative:
l Visa Direct Original Credit Transaction: Global Implementation Guide
l Push Payment Gateway Client Implementation Guide
l Visa Core Rules and Visa Product and Service Rules
l V.I.P. System BASE I Technical Specifications, Volume 2
l Full Service POS Online Messages – Technical Specifications
l Fraud Reporting System (FRS) User's Guide
l Global Visa Acquirer Risk Quick Reference Guide
l Global Visa Acquirer Fraud Control Manual
l Visa Partial Authorization Service Description and Implementation Guide, Visa Supplemental
Requirements, Version 3.1
l April 2023 Global Technical Letter and Implementation Guide, Articles 3.1, 3.2, 3.19, 4.3
l October 2022 Global Technical Letter and Implementation Guide, Articles 3.1, 3.5, 3.14 and
3.18
l April 2022 Global Technical Letter and Implementation Guide, Articles 3.1 and 3.10
l April 2022 Global Technical Letter and Implementation Guide, Articles 3.9, 3.12
l April 2021 Global Technical Letter and Implementation Guide, Articles 3.2, 11.2.12
l April 2020 Global Technical Letter and Implementation Guide, Articles 2.3, 4.8, 8.1.2, 7.4.1,
10.1.1
l October2019 Global Technical Letter and Implementation Guide, Article 2.11
l April 2019 Global Technical Letter and Implementation Guide, Article 3.4
l October 2018 Global Technical Letter (Business Enhancement Release (BER)), Articles 3.4, 3.14
l October 2017 Global Technical Letter and Implementation Guide, Articles 2.12, 2.15, 11.2.1

15 April 2023 Visa Confidential 15


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Account Funding Transaction (AFT) Overview

Comparison of AFTs with Purchase


and Quasi-Cash Transactions
An AFT is a type of purchase transaction.
This table summarizes the differences between an AFT, quasi-cash, and general–purpose purchase
transactions.

Table 3: Comparison of AFTs with Purchase and Quasi-Cash Transactions (1 of 4)

Account Funding Purchase Quasi-Cash


Transaction Transaction
Business Definition A transaction that pulls funds A transaction that A transaction that pulls funds
Description: from any Visa account with moves funds from any for the purchase of an item
the intent of funding a non- Visa account to fund a that is representative of
merchant account. merchant account. actual cash or a substitution
AFTs, when used for cash. It can easily convert
independently to fund to cash.
another Visa or non-Visa
account, must only be used
to fund an account
belonging to the same
individual or entity holding
the Visa account.

Examples l Account-to-account Any purchase of goods Examples of Quasi-cash


Money Transfer and services from a purchases include:
merchant; examples
l Person-to-person Money l Gambling chips
include:
Transfer
l Travelers cheques
l Traditional goods
l Prepaid card top-up
and services l Foreign currency
l Adding value to a digital
l Bill payments l Lottery tickets
wallet
l Debt repayment l Money Orders
l Funding for funds
disbursements (e.g., l Donations l Wire transfer (legacy)
pulling from a business
l Gift card purchase
debit to fund payroll
OCTs). l Closed-loop,
merchant-specific
accounts (e.g.,
Starbucks app)

15 April 2023 Visa Confidential 16


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Account Funding Transaction (AFT) Overview

Table 3: Comparison of AFTs with Purchase and Quasi-Cash Transactions (2 of 4)

Account Funding Purchase Quasi-Cash


Transaction Transaction

Risk l Use existing authorization l Use existing author­ l Use existing authorization
Management tools; CVV2, AVS, Visa ization tools; CVV2, tools; CVV2, AVS, Visa
Secure, etc. AVS, Visa Secure, Secure, etc.
etc.
l Authorize and make l Authorize and make
approval decisions using l Authorize and make approval decisions using
standard decline reason approval decisions standard decline reason
codes using standard codes
decline reason
l Apply new or existing l Apply new or existing
codes
spending limits and purchase limits and
monitoring l Apply new or monitoring
existing purchase
l Include Velocity limits to
limits and
mitigate possible fraud
monitoring
and money laundering
risk if the subsequent OCT
is a money transfer
transaction

Pricing Existing AFT rates apply Existing purchase rates Existing purchase rates apply
apply

Data Processing 10 00 11
Elements: Code

Transaction 05 05 05
Code

Tran Code 1 0 0
Qualifier

Business l AA (account-to-account) WT is used in Purchase WT is used in Purchase


Application transactions for Staged transactions for Staged
l BI (Financial institution-
Identifier Wallet transactions Wallet transactions.
initiated person-to-
(BAI)
person)
l FT (funds transfer)
l MP (merchant payment
for Scan to Pay programs
only)
l PP (person-to-person)
l TU (prepaid top-up)
l WT (wallet transfer)
l FD (funds disbursement)
l PD (payroll disbursement)

15 April 2023 Visa Confidential 17


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Account Funding Transaction (AFT) Overview

Table 3: Comparison of AFTs with Purchase and Quasi-Cash Transactions (3 of 4)

Account Funding Purchase Quasi-Cash


Transaction Transaction
Eligible Depends on BAI: All except MCC 6010 All except MCC 6010 and
MCCs and 6011 6011
l For AA, use MCC 4829,
6012, or 6211 (In the U.S.,
MCC 4829 is not
applicable with BAI AA)
l For BI, use MCC 6012
l For FT, use the MCC
1
based on use case
l 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.
l For PP, use MCC 4829 or
6012
l For TU, use MCC 6012,
6540 or 6051
2
l For WT, use MCC 6051
l For FD, use the MCC
associated with the
appropriate merchant.
l For PD, use the MCC
associated with the
appropriate merchant.

15 April 2023 Visa Confidential 18


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Account Funding Transaction (AFT) Overview

Table 3: Comparison of AFTs with Purchase and Quasi-Cash Transactions (4 of 4)

Account Funding Purchase Quasi-Cash


Transaction Transaction

Merchant Merchant name is required in Merchant Merchant


3
Name Field all transactions.

l For Money Transfer, the


format should be
Merchant*recipient name
(i.e., ABCD*Alex Miller)
l For Funds Disbursements
and Wallets, the format
should be Merchant or
Wallet name
Note: Recipient Name for
the purpose of visibility on
the cardholder's statement 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.

1 If the funds will be used for a high-brand risk transaction, use the applicable high-brand risk MCC.
2 If the funds will be used for a high-brand risk transaction, use the applicable high-brand risk MCC.
3 Will be used by issuers on the cardholder’s statement.

15 April 2023 Visa Confidential 19


Chapter 2
Requirements and Considerations
for AFT Origination

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

AFT Program Business Requirements


These requirements apply to AFT programs.

Acquiring Relationship
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 must take all liability and responsibility for AFT origination
programs operated using their Visa acquiring identifier.

15 April 2023 Visa Confidential 20


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Licensing and Registration


Acquirers and their agents must ensure that all necessary licenses, registrations, notifications,
authorizations, and approvals necessary to engage in AFT programs, are obtained from the
appropriate authorities in the originating entity’s 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 these activities:
l Stores, processes, or transmits cardholder information
l Manages or has access to funds related to the AFT origination services
l 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 activities
associated with the Visa programs.

Transaction Usage
AFTs cannot be used for the purchase of goods, 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:
l Transaction size
l Transaction frequency
l 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.

15 April 2023 Visa Confidential 21


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

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 before program launch. Acquirers
must obtain approval by completing the Visa Direct—Program Information Form (PIF). A PIF is
required for new Visa Direct programs and for any updates or changes to existing Visa Direct
programs (e.g., 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 Program Request Management (PRM).
For domestic-only AFT programs without OCT enabled, the acquirer must register the program with
Visa by using the Domestic AFT Registration form, as found in Program Request Management (PRM)
tool.
Refer to Visa Direct Program Approval for registration requirements for domestic AFT programs
without OCT enabled.

Requirements for Submitting a PIF


A new PIF must be submitted in these situations:
l For AFT-only programs where the OCT is not enabled as the push payment transaction.
Note: For domestic AFT-only programs without OCT enabled, use the Domestic AFT
Registration form as found in Program Request Management (PRM) tool.
l Initiating a new Visa Direct program type1 or BAIs2 not indicated in a prior PIF.
l Any updates or changes to existing Visa Direct programs that were previously approved,
including adding or changing acquiring identifiers, program types, use cases, or addition of
cross-border countries.
l When a client needs to change or add a third-party agent.

1A program is defined as a product or service offered by an acquirer, service provider, or merchant. Visa-
defined Program Types are listed in the table in the Business Application Identifier (BAI) section of this
chapter.
2A single PIF submission may only request BAIs within one BAI category (i.e., Money Transfer or Funds
Disbursement (non-Money Transfer). If a proposed program requires BAIs from both categories, then two
PIFs must be submitted.

15 April 2023 Visa Confidential 22


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

l 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 onboarded 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.
l 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.
l For high-risk programs, such as cryptocurrency wallet programs (FT), a new PIF is required for
every new merchant origination program.

AFT Processing Requirements and


Considerations
This section outlines the transaction processing and AFT message format requirements for
originating entities.

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 the appendix AFT Data Elements and
Processing Rules.
Originating entities can use a unique or 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 authorization.
Note: Cross-border AFTs are supported if enabled by the acquirer and issuer. The
authorization/clearing amount may be different from the authorized amount due to foreign
exchange.
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 domestic AFTs with the processing code 10 (Account Funding) to a purchase
transaction with the processing code 00 (Goods/Service purchase–debit) before sending the
transaction to issuers that are not enabled to receive/have opted not to process the AFT processing

15 April 2023 Visa Confidential 23


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

code. AFTs converted to purchase will include a Business Application Identifier in Field 104 based on
Core configuration. Refer to the appendix AFT Data Elements and Processing Rules, AFT Key Data
Elements for more information on the data elements for Field 104.

Identifying Domestic and Cross-border AFTs


An AFT is considered domestic when the merchant, acquirer and issuer are in the same country. The
AFT is cross-border when the issuer is in a different country than the merchant and acquirer, except
for Europe (see AFT Jurisdiction for the EEA, U.K., and Gibraltar).

AFT Jurisdiction for the EEA, U.K., and Gibraltar


This table shows the AFT jurisdiction based on the location of the issuer, acquirer, and merchant.

Table 4: AFT Jurisdiction for the EEA, U.K., and Gibraltar

Location AFT Jurisdiction


The issuer, acquirer, and merchant are in the same Domestic
country

The issuer, acquirer, or merchant are in different countries Intra-EEA, including the U.K. and Gibraltar
within the EEA, U.K., or Gibraltar

The issuer, acquirer, or merchant is outside the EEA, U.K., International


or Gibraltar

Note: European Economic Area (EEA), which includes the member states of the European
Union, 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.

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 the appendix 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 the table in appendix Business Application Identifier (BAI) Acronyms of 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.
This table summarizes AFT categories, their BAIs, corresponding MCCs, and regional usage
requirements.

15 April 2023 Visa Confidential 24


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Table 5: AFT Categories – Money Transfer (1 of 2)

BAI AFT Category Merchant Category Code (MCC) BAI Usage Requirements

AA Account-to-account Money l 4829 Non-Financial Institution Used in a me-to-me Money Transfer


Transfer (funding of the Wire Transfer Money Orders (Not transaction, both accounts are
cardholder’s own account applicable in the U.S. with BAI owned by the same cardholder.
at the same or a different AA)
financial institution)
l 6012 Financial Institutions –
Note: If funding a prepaid Merchandise and Services
account, use TU.
l 6211 Brokerage

BI Financial Institution-offered 6012 Financial Institutions – P2P Money Transfer is initiated from
Bank-Initiated P2P Money Merchandise and Services an online banking system, making it
Transfer a bank-initiated transaction.
Important: BAI BI is used Note: BAI BI should only be used in
for very specific scenarios combination with MCC 6012.
and is enabled only in
Note: Domestic AFT from a bank/
limited markets. Contact
financial institution can use BAI=BI
your Visa Representative
for me-to-me, person-to-person
for information on the
transactions (e.g., AA, PP type of use
availability of BAI BI in your
cases).
market, and applicability of
BAI BI to your program.

FT Funds Transfer l 4829 Non-Financial Institution Adding funds to or cashing out a


Wire Transfer Money Orders Stored Value Digital Wallet (SVDW)
(WTMOs) account.

l 6012 Financial Institutions – Funding a Money Transfer where the


Merchandise and Services OCT is not enabled as the push
mechanism to the recipient.
l 6540 Non-Financial Institutions –
Stored Value Card Purchase/Load For the direct acquisition of crypto­
currency.
l If the funds will be used for a
high-brand risk transaction, the
applicable high-brand risk MCC
must be used.
l If the wallet is used to purchase
non-fiat currency (e.g., crypto­
currency), the applicable special
condition indicator must be used.
MCC 6051 Non-Financial
Institutions – Non-Fiat Currency
(e.g., Cryptocurrency).

PP Person-to-person (P2P) l 4829 Non-Financial Institution This is applicable for services that
Money Transfer Wire Transfer Money Orders support AFT and OCT. If only AFT is
(transferring funds to supported, BAI FT must be used.
l 6012 Financial Institutions –
another individual’s non-
Merchandise and Services
merchant account)

15 April 2023 Visa Confidential 25


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Table 5: AFT Categories – Money Transfer (2 of 2)

BAI AFT Category Merchant Category Code (MCC) BAI Usage Requirements

WT Staged Digital Wallet (SDW) l 6051 Non-Financial Institutions – Note: When a Visa card is used to
transfer (adding value to a Foreign Currency, Non-Fiat fund a Staged Digital Wallet before
digital wallet with a Currency (example, Crypto­ the cardholder makes a purchase, an
proprietary merchant currency), Money Orders (not AFT with a BAI of WT must be used.
acceptance network) Money Transfer), Account WT must be used only by registered
Funding (not Stored Value Load), Staged Digital Wallet Operators
Travelers Cheques, and Debt (SDWO).
Repayment For additional information on
l If the funds will be used for a Staged Digital Wallet transactions,
high-brand risk transaction, the visit the Staged Digital Wallet
applicable high-brand risk MCC Operators section at Visa Online
must be used. (VOL). Contact your Visa represen­
tative for additional information and
l If the funds are used for a
requirements for digital wallets.
gambling transaction, the
applicable gambling MCC must Note: Effective October 2023: Field
be used. 104 – Sender Data and Recipient
Name will be required to support
l If the wallet is used to purchase
cross-border AFT.
non-fiat currency (for example:
cryptocurrency), the applicable V.I.P. will reject AFTs with the existing
special condition indicator must reject code 0494 (when Field or data
be used. is missing or invalid).

TU Prepaid card load or top-up l 6012 Financial Institutions – Note: Merchants that sell other
(adding value to an eligible Merchandise and Services goods and services in addition to
reloadable prepaid card or stored value cards and offer prepaid
l 6051 Non-Financial Institutions –
funding the cardholder’s card load capability can use the
Foreign Currency, Non-Fiat
own prepaid account) MCC associated with the merchant’s
Currency (example, Crypto­
primary business in accordance with
currency), Money Orders (not
the Visa Merchant Data Standards
Money Transfer), Travelers
Manual.
Cheques, and Debt Repayment
l 6540 Non-Financial Institutions –
Stored Value Card Purchase/Load

Table 6: AFT Categories – Funds Disbursement/Non-Money Transfer

BAI AFT Category Merchant Category Code BAI Usage Requirements

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.

PD Payroll Disbursement 8931 Accounting, Auditing, and When a payroll provider is


Bookkeeping services including disbursing payroll on behalf of the
Payroll small business who funds the
transactions.

15 April 2023 Visa Confidential 26


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

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:
l Implementing the right economics
l Managing risks: arbitrage, fraud, money laundering, etc.
l Maintaining compliance and transparency across all parties in the payments chain
l 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.
This table 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.

15 April 2023 Visa Confidential 27


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Table 7: 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 l 4829 l 6012 l 4829 l 6051
l 6012 (if bank- l 6211 l 6540 l Merchant's
offered) MCC if High-
l 6051 (non- l 6012 (if bank-
Risk or
financial offered)
otherwise
institution
l Merchant's Back-to-Back
moving funds
MCC if High- funding
on behalf of
Risk
financial
If the wallet is
institutions) 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.

Use Me-to-me funding/adding cash N/A AFT (AA) AFT (FT) AFT (WT)
Cases
Me-to-me withdrawal/Cash out N/A OCT (AA) OCT (FT) OCT (WT)

OCT not
Send funds to AFT (FT) AFT (FT) AFT (FT) AFT (WT)
enabled
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

Note:
l AFTs with BAI = WT should only be used by registered Staged Digital Wallet
Operators (SDWO).
l 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.

15 April 2023 Visa Confidential 28


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Table 8: Digital Wallets Comparison (1 of 2)

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

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

Add/Store Yes Yes


funds

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


complete a
purchase

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

15 April 2023 Visa Confidential 29


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Table 8: Digital Wallets Comparison (2 of 2)

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

Stored funds to Stored funds may be used to pay Payments to merchants include:
pay merchants merchants.
l Face-to-face SDW brand acceptance mark at a
Payments to merchants include: physical POS
l Face-to-face SVDW-brand or general- l e-Commerce SDW brand acceptance mark
purpose payment network acceptance
l Merchant wallets where users instruct buyers to
mark at a physical POS
send money to a merchant’s digital wallet
l eCommerce SVDW-brand or general-
l Back-to-Back Funding purchase transaction
purpose payment network acceptance
mark
l Merchant wallets where users instruct
buyers to send money to a merchant's
digital wallet
Note: A wallet 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 Wallet Stored Value Digital Wallet may be The Staged Digital Wallet may be structured as a
as a prepaid structured as a prepaid account or offer a prepaid account but must not offer or attach a
account general-purpose payment network prepaid general-purpose payment network card as a physical
card as a physical access tool to the funds access tool to the funds in the digital wallet. This
in the digital wallet. This scenario does not scenario does not alter the transaction or BAI
alter the transaction or BAI coding. coding.

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

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 these requirements:
l The AFT must be offered in parity with a compliant OCT
l 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
l AFTs must be submitted with a BAI of “BI”
l 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

15 April 2023 Visa Confidential 30


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Important: BAI BI is used for very specific scenarios and is enabled only in limited markets.
Contact your Visa Representative for information on:
l the availability of BAI BI in your market, and
l 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 before enabling
bank P2P services on behalf of the bank and its customers. The processes 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.

Cryptocurrency – Use Case


Direct cryptocurrency purchases are completed using a Quasi-Cash purchase.
Note: For U.S. only – AFTs are used to directly acquire cryptocurrency, using debit or
prepaid card only.
A cryptocurrency wallet may be prefunded using an AFT and the funds are later used to purchase
cryptocurrency. Stored Value Digital Wallet and Staged Digital Wallet models can support
cryptocurrency wallets. The AFT must include these data requirements:
l BAI must be FT or WT
l Applicable Merchant Category Codes include:
n 6051: Non-financial institution
n 6211: Brokerage (if greater than 50% of client annual sales volume, measured in the
client’s local fiat currency comes from non-cryptocurrency (e.g., stocks, bonds, etc.)
n 6012: Financial Institution (if client holds a US bank charter)
l Special Condition indicator (Field 60.4) must be 7 to identify this pull transaction is for a
cryptocurrency-related program.
Acquirers must follow the high-brand risk registration process for their cryptocurrency merchants to
obtain PIF approval before launching any new programs.
Refer to Visa Direct Program Approval for registration requirements for domestic AFT programs
without OCT enabled.

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 here:
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).

15 April 2023 Visa Confidential 31


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Note: Not all MITs are relevant for AFTs (e.g., Installments, No Show).
Examples of MITs relevant to AFTs are:
l Recurring: Reload $50 every week into digital wallet or move $500 every month from bank
account #1 to bank account #2.
l Use Card-on-File: When digital wallet balance hits $10, automatically reload $50.
l 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 these transaction coding:
Initial AFT (full 3D Secure):
l MCC 6012 (if bank led), if not bank led, MCC must represent the appropriate merchant for
the pull.
l Field 60.8 = 05 (ECI)
l Field 22 = 0100
l Field 25 = 59
l Field 126.9 = CAVV
l Field 126.13 = C or R
n C, if being captured for the first time. C is used for unscheduled payment using a Card-
on-File.
n R, if using in the first of a recurring payment and card is already on file.
Recurring AFT:
l MCC 6012
l Field 22 = 1000
l Field 25 = 59
l Field 60.8 = 07 (ECI)
l Field 126.13 = C or R
n R, if being captured for use in a recurring payment.
n 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.
l Field 62.2 or Field 125, DS 03, Tag 03 = original transaction ID

15 April 2023 Visa Confidential 32


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Cross-Border AFTs
AFTs are available for domestic and cross-border transactions in certain countries. AFTs must be
enabled for acquirers and issuers to participate.
Acquirers must have an approved PIF that specifically includes cross-border AFTs. As with all
domestic AFTs, for cross-border AFTs, Visa requires that acquirers and their agents must ensure that
all necessary licenses, registrations, notifications, authorizations, and approvals necessary to engage
in AFT programs are obtained from the appropriate authorities in the originating entity’s jurisdiction.
Cross-border AFTs must be processed using the unique AFT processing code 10.
Effective 23 April 2022, cross-border AFTs will be made available globally for merchants and
acquirers, except in the U.S. U.S. acquirers will not be allowed to originate cross-border AFTs. U.S.
issuers can continue to receive cross-border AFTs and must fulfill requirements for additional data
elements. Please contact your Visa representative for more information.
Exceptions that were available for select cross-border AFTs will continue to be supported. The
exceptions included:
l U.K., Gibraltar, and 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.
l All Regions – Wallet transfer (WT) can be cross-border in all regions.
Note: In the EU:
l Effective 23 April 2022: participating acquirers must support domestic and cross-
border AFTs
l Effective October 2022: issuers are required to support domestic and cross-border
AFTs
Note: Issuers and participating acquirers must be compliant with these mandates:
l Effective October 2022: AP will be required to support domestic and cross-border
AFTs.
l Effective April 2023: LAC, CEMEA, and Canada will be required to support domestic
and cross-border AFTs.

15 April 2023 Visa Confidential 33


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Partial Authorization (U.S. Domestic Only)


Partial Authorization is a service intended to address insufficient funds declines, with the goal of
enhancing the cardholder and merchant experience.
Visa Direct supports Partial Authorization for AFTs in the U.S.
Participating U.S. acquirers must include code 1 in Field 60.10—Partial Authorization Indicator, for
AFTs.
U.S. issuers that support Partial Authorization, check for the Partial Authorization Indicator and, if
present, respond with a partial approval for an amount less than the requested amount.
For more information, refer to the Visa Partial Authorization Service Description and Implementation
Guide, Visa Supplemental Requirements, Version 3.1.

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 the appendix: AFT Data Elements and Processing Rules for the data elements and message
requirements unique to AFTs. The appendix AFT Data Elements and Processing Rules 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 VisaNet
Authorization-Only Online Messages – Technical Specifications and Full Service POS Online Messages –
Technical Specifications.

Custom Payment Service (CPS) (U.S. Only)


AFTs can participate in the Custom Payment Service (CPS) in the U.S.
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 the appendix AFT Data Elements and Processing Rules.

15 April 2023 Visa Confidential 34


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Acquirer, Service Provider, and Merchant


Network Routing Options
This section outlines the available routing configurations.
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.

VisaNet Connectivity Using ISO Messaging


Visa provides flexible, reliable, and secure access to Visa's payment systems using one of two single-
pipe connections.
l 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.
l 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.

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.
These APIs are applicable to AFTs. Acquirers, service providers, and merchants may choose to use all
or some of the available APIs.
l Funds Transfer: The financial API used to initiate an AFT and its associated reversal
l Payment Account Validation: Allows the acquirers, service providers, and merchants to
perform address verification and/or CVV2 validation on the sender’s account

15 April 2023 Visa Confidential 35


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

l Funds Transfer Attributes Inquiry: Allows the acquirers, service providers, and merchants to
determine whether the sender’s or recipient’s non-Visa account is eligible for domestic AFTs.
The Funds Transfer Attributes Inquiry (FTAI) API is often used with AFTs to determine key
characteristics of a recipient card before initiating the transfer like country, card-type, block
status, etc. Refer to the Visa Developer Center at https://developer.visa.com/products/paai for
additional information on this API.
Note:
n Effective 1 January 2020: Visa Direct clients are recommended to use the latest
ACNL file.
n Effective 15 January 2023: Originating entities in Canada and U.S. will be required
to use Version 5 of the FTAI API.
l 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.
Funds Transfer APIs
l Create Multi Push Funds Transaction POST
l Create Push Funds Transaction POST
l Read Multi Pull Funds Transaction GET
l Create Pull Funds Transaction POST
l Read Reverse Funds Transaction GET
l Read Multi Reverse Funds Transaction GET
l Create Reverse Funds Transaction POST
l Create Multi Reverse Funds Transaction POST
l Read Multi Push Funds Transaction GET
l Read Push Funds Transaction GET
l Read Pull Funds Transaction GET
l Create Multi Pull Funds Transaction 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.

API Terms of Use


Below are the terms of use for Visa Developer Center APIs.
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 Center in

15 April 2023 Visa Confidential 36


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

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.

Push Payment Gateway Service


The Visa Push Payment Gateway Service (PPGS) allows acquirers, service providers, and merchants to
send AFTs to Visa for routing to multiple debit networks.
The service provides authorization, clearing, settlement, reporting, and exception processing support
for the 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.
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.

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.

15 April 2023 Visa Confidential 37


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Transaction Coding at Remote Channels (CEMEA)


This section covers the rules for transaction coding at remote channels for the CEMEA region.
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.
The exception allowing for the use of other ECI values for the CIS SEE subregion will cease, effective
September 30, 2023. The ECI Field 63.6 could contain these ECI value that represent the result of the
Visa Secure authentication:
l 05 Fully authenticated e-commerce transaction
l 06 Merchant attempted to authenticate the cardholder
l 07 Non-authenticated e-commerce transaction
After September 30, 2023, electronic commerce transactions of participating merchants or token
requestors will be deemed eligible for DAF following successful cryptogram validation by Visa. These
transactions will be allocated the ECI value of 05 and be covered by fraud and dispute-related rules,
as set forth by Visa’s operating rules limited to the merchant liability framework.
Note: Any exception to the use of other ECI values must be approved prior to coding. Please contact
your regional Visa representative.
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 this 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 Field
126.10 into the authorization request and must expect to receive CVV2 results in Field 44.10 (as per
standard CVV2 processing).

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 applicable laws.

15 April 2023 Visa Confidential 38


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Customer considerations include:


l Disclosures: The program’s user interface should include all appropriate disclosures and
communications to cardholders.
l 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 cancel the
transaction.
l Confirmation of transaction details: Acquirers, service providers, and merchants should
provide senders a process to review and confirm the transfer amount and other applicable
details before submitting the transaction.
l 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.
l 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. If so,
capture the sender’s email address or mobile phone number.

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.

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.

15 April 2023 Visa Confidential 39


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

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 watchlists 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, as well as 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.

Digital Authentication Framework


Visa has expanded its authentication rules and processing requirements to support the introduction
of the Digital Authentication Framework (DAF) that will apply to Primary Account Number (PAN) and
Visa Payment Token e-commerce transactions using Visa Secure or Visa Token Service.
Transactions of participating merchants or token requestors (TRs) are deemed eligible for DAF
following successful cryptogram validation by Visa. These transactions will be allocated the ECI
(Electronic Commerce Indicator) value of 05 and be covered by fraud and dispute-related rules, as set
forth by Visa’s operating rules limited to the merchant liability framework.
Under this new framework, a new DAF indicator may be sent to issuers to identify qualifying
authorization transactions that include Cardholder Account Verification Value (CAVV), Token
Authentication Verification Value (TAVV), or both CAVV and TAVV. When issuers are activated to
receive the enhancement data tags in authenticated transactions, the tags included in the message
are dependent on the type of validation data present in the transaction and whether the enhanced
data is available for sending to the issuer.
Effective April 2022: Purchase transactions (PAN and Token) and AFTs with PAN are eligible for
merchant liability protection.

15 April 2023 Visa Confidential 40


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Effective October 2022:


l AFTs containing a valid token cryptogram will be included in the type of transactions that can
be processed as a secure e-commerce transaction and assigned the ECI value of 5.
l AFTs will be eligible for merchant liability protection for DAF (Host Card Emulation (HCE)
tokens, e-commerce (ECOM), Card-on-File (COF) etc.) and non-DAF (e.g., secure element
tokens).
Note: Effective October 2022:
l Acquirers that send e-commerce AFTs with a payment token must support the
changes to cryptogram validation and ECI processing.
l Issuers in the AP (except Bangladesh, India, Nepal and Japan), CEMEA, Europe, and
LAC regions that participate in the Visa Token Service must support changes to e-
commerce AFT cryptogram validation and ECI processing.
Note: Effective April 2023: Participating acquirers in Japan must support receiving a DAF
indicator on eligible e-commerce transactions.
Note: Effective 15 April 2023: Issuers in the U.S., Japan, and Canada that participate in the
Visa Token Service must support changes to e-commerce AFT cryptogram validation and ECI
processing.
For more details, refer to:
l April 2022 Global Technical Letter and Implementation Guide, Articles 3.1 and 3.10
l October 2022 Global Technical Letter and Implementation Guide, Articles 3.1, 3.5, and 3.18
l April 2023 Global Technical Letter and Implementation Guide, Articles 3.1 and 3.2

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 before 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 client-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).

15 April 2023 Visa Confidential 41


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

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)3, 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 Application Programming Interfaces (APIs) for more information.
These risk management reference materials can be found on Visa Online or obtained from your Visa
representative:
l Global Visa Acquirer Risk Quick Reference Guide: Provides acquirers with best practices for
managing card-absent acceptance risk
l Global Visa Acquirer Fraud Control Manual: Covers the merchant lifecycle, from underwriting
through monitoring and termination, and provides information and resources for reducing
and preventing fraud losses
l Fraud and dispute risk information, including:
n Fraud Reporting Service (FRS): AFT origination entities are required to report
fraudulent AFTs to the FRS
n Address Verification Service (AVS): Verifies a cardholder’s billing statement address
when processing card not present or key-entered transactions
n 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 these risk materials:
l Acquirer Risk Monitoring and Detection
l Issuer Fraud Monitoring and Detection
l Merchant and Cardholder Lifecycle Risks—Best Practice Guide
l Managing Fraud in the Card Not Present Environment
l Payment Services Directive 2 (PSD2) Strong Customer Authentication (SCA) Guide

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

15 April 2023 Visa Confidential 42


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

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.

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 Primary Account Numbers (PANs) to
process with tokens.
Visa supports Visa Token Service for AFTs and OCTs for available token types.
l AFTs and OCTs that are submitted for token processing must comply with the existing
processing rules for AFTs and OCTs
l 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 enabled for Visa Direct. Please contact
your tokenization service provider for details.
l 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.
l 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
l 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.

15 April 2023 Visa Confidential 43


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Real Time Visa Account Updater (VAU)


This section presents an overview of the Real Time VAU service that integrates the VAU updates into
the VisaNet authorization process.
Visa Account Updater (VAU) (available to Europe in May 2021), 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.

Account Verification and Related Services


Account Verification, Address Verification, and CVV2 Verification are existing services that Visa Direct
merchants can leverage through their acquirers and acquirer processors to verify a card account at
the time of cardholder onboarding and before sending a Visa Direct AFT. This can help merchants
ensure the account is in good standing, help mitigate fraud, and improve authorization approval
rates.
The Account Name Inquiry (ANI) functionality was introduced in April 2022 as a mechanism for card
not present merchants and cash payout originators to validate the identity of the customer before
initiating a financial transaction. To perform ANI, the merchant collects the full legal name of the
cardholder and sends it in a zero-amount account verification message. In response to the ANI
request, the merchant will receive an ANI result code that indicates whether the cardholder name
matched, partially matched, or did not match the cardholder’s legal name associated with the
payment account in the issuer’s systems. If the issuer does not participate in ANI, the merchant will
receive a result code indicating that the cardholder name was not verified.
Effective 14 October 2023
Visa Direct acquirers must be able to send and receive ANI fields and values for their merchants that
choose to use ANI. Acquirers that choose to support ANI through 0100 Account Verification
messages must:
l Be able to send cardholder name data in the 0100 message.
l Be able to receive the name verification result in the 0110 response message.
l Establish participation through their Visa representative.
Acquirers that choose to support ANI through Visa’s Payment Account Validation (PAV) API must be
able to send and receive ANI fields. For more information on this API, please visit Visa Developer
Center.

15 April 2023 Visa Confidential 44


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Acquirers are currently able to test and activate ANI through either ISO or API.
Refer to this page on Visa Online for additional information on Account Name Inquiry, Account
Verification and Address Verification: https://secure.visaonline.com/SitePages/Content.aspx?
pageid=3.1.9.10.0.

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 takeovers,
and hacker attacks.
Sound data security practices reduce fraud risk and foster customer confidence in the secure
handling of personal information.
Acquirers, service providers, and merchants should:
l 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.
l 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/.

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 AFT credit adjustment advice. AFT reversals are full-financial transactions (0420) requests
and AFT credit adjustments are advice (0220) requests.
Considerations for which transaction to use depends on the acquirer’s connection type to Visa
(Single Message or Dual Message) and the amount of time after the authorization when the reversal
of funds will be initiated.

15 April 2023 Visa Confidential 45


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

The general guidance on the timeframe for when to use an AFT reversal or an AFT credit adjustment
should be based on whether the transaction was already cleared and settled in Visa’s end-of-day
settlement and reconciliation process.
To provide a better experience for cardholders and standardize timeframes for processing AFT credit
adjustment advice, issuers are required to process and post AFT credit adjustment advice within
these timeframes:
l In the AP, CEMEA, LAC, and North American (Canada, U.S.) regions: Within two business days
after receipt of the acquirer’s AFT credit adjustment advice.
l In the Europe region: The next business day after receipt of the acquirer’s AFT credit
adjustment advice.
For all credit adjustment advices, an acquirer must originate the credit adjustment containing the
original AFT transaction ID. It must also be originated in 30 calendar days or less of the original
transaction and cannot be originated if the original transaction is over 30 days old.
This table provides an overview of the reversal and credit adjustment advice and associated
processing considerations.

15 April 2023 Visa Confidential 46


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Table 9: Reversal and Adjustment Transactions Overview

Acquirer Connection Type Reversal Adjustment

SMS processing clients l A full-financial AFT reversal (0420) l A credit adjustment transaction
must be used to refund within the (0220) with processing code 22
first 24 hours of the original (Adjustment-Credit) and reason
transaction time, but before the code 2140 (Account funding
settlement of the transaction. transaction: credit adjustment)
must be used to process refunds
to the sender's card.
l These refunds can be applied
before and after the settlement
cut-off window.
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 l Originating clients using Dual An adjustment transaction (TC25 with
Message Processing can use an TCQ1) can also be used to process
authorization reversal (0400) as a refunds to the sender's card after the
way to refund. This can only be original AFT has been cleared.
used before the original AFT has
l These get processed as batch
been cleared and settled.
clearing transactions
Note:
l Transaction ID of the original AFT
– Visa rules presently require should be included to make it
clearing to be performed easier for issuers to reconcile the
within seven (7) days of the adjustment with the original
original authorization.
transaction.
However, as a best practice,
Visa recommends clearing the
original AFT within three (3)
days to ensure better
cardholder experience.
– Clients should not be
submitting a clearing once the
authorization reversal has been
processed. They should be
deleted from the batch.
l Clients also have the option of
processing a reversal transaction
in the clearing (as TC25, TCQ-1) if
the original transaction has been
cleared.

– This is processed as a batch


clearing transaction and can be
performed up to 30 days from
the original transaction.

15 April 2023 Visa Confidential 47


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Important: If the service provider is attempting to process an AFT Refund request that is
missing the transaction ID of the original AFT, this may result in issuers being unable to
process the refund quickly. This can be an unpleasant experience for the cardholder as they
wait for the funds to be deposited to their card. It is a best practice to include the original
AFT transaction ID in the OCT transactions and also in the refund request to enable faster
reconciliation and return of funds when needed.
The flows presented here are used to give a more detailed understanding of how the AFT credit
adjustment advice and the AFT reversal work from the origination of the adjustment through to the
issuer processing of the adjustment, based on the originating entity and issuer connections to Visa.

Credit Adjustment Flow – SMS Originating Entity to SMS Recipient Issuer

1. Originating entity submits 0220 advice message to Visa to request refund of money to
sender's account.
2. Visa sends 0220 authorization message to issuer.
3. Issuer uses the 0220 message to restore balance to the Cardholder's account.
4. Issuer responds with 0230.
5. Visa receives 0230 message.
6. Visa sends 0230 confirmation back to originating entity to confirm success of submission.

15 April 2023 Visa Confidential 48


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Credit Adjustment Flow – SMS Originating Entity to Dual Message/BASE II Recipient Issuer

1. Originating entity submits a 0220 advice message to Visa to request refund of money to
sender's account.
2. Visa receives 0220 advice message to issuer.
3. Visa creates 0230 STIP advice and returns to originating entity to confirm.
4. Visa creates TC25 TCQ1 and sends to issuer for processing.
5. The issuer receives the TC25 and restores the balance to the Cardholder. The balance must be
restored within the rule timeline of one business day for Europe and two business days for all
other regions.

15 April 2023 Visa Confidential 49


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Credit Adjustment Flow – Dual Message Originating Entity to SMS Recipient Issuer

1. Originating entity raises TC25 to Visa to request refund of money to sender's account.
2. Visa receives TC25 in incoming files.
3. Visa creates 0220 advice and forwards to SMS recipient issuer.
4. SMS issuer receives 0220 and creates 0230 message.
5. SMS issuer creates 0230 response and sends to Visa.
6. Visa receives the 0230 response confirming receipt and processing of 0220 advice.

15 April 2023 Visa Confidential 50


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

Credit Adjustment Flow – Dual Message Originating Entity to Dual Message/BASE II Recipient
Issuer

1. Originating entity submits a TC25 outgoing to Visa to request refund of money to sender's
account.
2. Visa receives TC25 and forwards to issuer for processing.
3. Issuer processes TC25 and restores balance to Cardholder’s account. This balance must be
restored within the rule timeline of one business day for Europe and two business days for all
other regions.

AFT Reversals

AFT Reversal Flow – SMS Originating Entity to SMS Recipient Issuer

1. Originating entity submits 0420 advice message to Visa to initiate refund of money to
sender’s account.
2. Visa sends 0420 authorization message to issuer.
3. Issuer uses the 0420 advice message to restore balance to cardholder’s account.
4. Issuer responds with 0430 advice message, which must be an approval.
Note: If an issuer were to decline a 0420 message, V.I.P. will reject that decline response
from the issuer and respond in STIP with a 0430 approval to the originating entity).

15 April 2023 Visa Confidential 51


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

5. Visa receives 0430 advice message.


6. Visa sends 0430 confirmation back to originating entity to confirm reversal advice submitted
to issuer.

AFT Reversal Flow – SMS Originating entity to Dual Messaging/BASE II Recipient Issuer

1. Originating entity submits 0420 advice message to Visa to request refund of money to
sender’s account.
2. Visa receives 0420 advice and converts it to a 0400 reversal request.
3. Visa sends 0400 reversal request to the recipient issuer. The issuer should use this 0400
reversal request to memo post the balance to the Cardholders’ account using the “Open to
Buy” parameters.
4. Issuer receives 0400 reversal request and responds with a 0410 reversal response to Visa.
5. Visa receives 0410 reversal response.
6. Visa forwards 0430 confirmation advice to the SMS Originating entity.
7. Visa creates a TC25 outgoing to the issuer.
8. The issuer receives the TC25 from Visa and uses this to complete processing of refund back
to Cardholders’ account.

15 April 2023 Visa Confidential 52


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

AFT Reversal Flow – Dual Message Originating Entity to SMS Recipient Issuer

1. Originating entity raises TC25 to Visa to request refund of money to sender's account.
2. Visa receives TC25 in incoming files.
3. Visa creates 0220 advice and forwards to SMS recipient issuer.
4. SMS issuer receives 0220 and creates 0230 message.
5. SMS issuer creates 0230 response and sends to Visa.
6. Visa receives the 0230 response confirming receipt and processing of 0220 advice.

15 April 2023 Visa Confidential 53


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Requirements and Considerations for AFT Origination

AFT Reversal Flow – Dual Message Originating entity to Dual Message/BASE II Recipient Issuer

1. Originating entity submits a TC25 outgoing to Visa to request refund of money to sender's
account.
2. Visa receives TC25 and forwards to issuer for processing.
3. Issuer processes TC25 and restores balance to Cardholder’s account. This balance must be
restored within the rule timeline of one business day for Europe and two business days for all
other regions.
For dispute information, see Issuers - Dispute Resolutions.

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.

AFT Certification Requirements


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

15 April 2023 Visa Confidential 54


Chapter 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 Canada, CEMEA, LAC and U.S. regions.
Effective 15 October 2022: AFT support will be required in the Europe Region.
AP, EU, and LAC must be aware that Visa has implemented changes to convert domestic AFTs
with the processing code 10 (Account Funding) to a purchase transaction with the processing
code 00 (Goods/Service purchase–debit) before sending the transaction to issuers that are
not enabled, or have not opted in, to receive the AFT processing code 10. AFTs converted to
a purchase transaction contain a BAI in Field 104 that issuers must be able to receive and
process.

15 April 2023 Visa Confidential 55


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Issuer Requirements and Considerations

Receiving and Processing AFTs


To ensure a positive cardholder experience, and to comply with Visa Rules, issuers that support or
receive AFTs must implement these points in their AFT handling processes:
l Confirm AFTs are approved at a rate in line with approval rates of e-commerce purchase
transactions
l Validate that processor and Visa parameters are not configured to decline all AFTs
l Ensure that the use of AFT processing code 10 does not interfere with the ability to process
and authorize AFTs
l Verify that AFTs:
n Are processed similar to an e-commerce purchase transaction (i.e., not as an ATM
withdrawal)
n Use appropriate statement messaging
n Do not generate unexpected cardholder fees
n Have reasonable transaction limits in accordance with an e-commerce purchase
transaction
n Can be processed with a BAI
l 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.
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 the
appendix AFT Data Elements and Processing Rules.

15 April 2023 Visa Confidential 56


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Issuer Requirements and Considerations

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.

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 this
table.
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).
The current maximum Transaction Amount for AFT is USD 10,000 (based on the one-day velocity
limit).

Table 10: AFT Velocity Limits

AFT Transaction Type One-Day Time Seven-Day Time Thirty-Day Time


Period Period Period

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

Note: U.S. acquirers cannot originate cross-border AFTs. U.S. issuers can continue to receive
cross-border AFTs and must fulfill requirements for additional data elements.
Effective 22 April 2022: cross-border AFTs will be made available and the above velocity limits will
apply.
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.

15 April 2023 Visa Confidential 57


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Issuer Requirements and Considerations

New AFT Velocity Limits


The new velocity limits will apply:
l Effective 4 November 2022: in AP, CEMEA and EU regions
l Effective April 2023: in LAC, U.S. and Canada
The maximum Transaction Amounts for AFT are:
l Domestic AFT: Velocity limit for one-day is applied
l Non-Money Transfer AFT: USD 50,000
l Cross-border Money Transfer AFT: USD 25,000

Table 11: New AFT Velocity Limits

AFT Transaction Type One-Day Time Seven-Day Time Thirty-Day Time


Period Period Period
Domestic Money Transfer USD 100,000 USD 250,000 USD 500,000

Cross-Border Money Transfer USD 50,000 USD 100,000 USD 200,000

Domestic Non-Money Transfer USD 100,000 USD 250,000 USD 500,000

Cross-Border Non-Money Transfer USD 50,000 USD 100,000 USD 200,000

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.
In the U.S., if issuers apply internal limits, it is recommended that issuers and issuer processors set
AFT spend limits to a minimum of $5000 to drive adoption of new higher-ticket use cases, such as
brokerage and small-business payroll accounts. Visa also recommends issuers review AFT limits
proactively on a periodic basis based on cardholder and merchant risk profiles, cardholder tenure
(e.g., raise limit after 30 days, raise limit again after 60 days, etc.), and based on history of accounts
that have previously received a velocity limit decline.

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, visit https://secure.visaonline.com/
SitePages/Section.aspx?pageid=2.1.1.0.0.

15 April 2023 Visa Confidential 58


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Issuer Requirements and Considerations

Table 12: 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 these situations:

l Transaction Amount is incorrect


l An addition or transposition error occurred

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

13.1—Merchandise/ Services Not Received This dispute may be used for either of these situations:

l Serviced not rendered by the expected date


l Merchandise was not received on the expected date/agreed
location
l 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 these situations:
Accepted
l Legal restrictions prevent accepting the credit
l Recipient refuses the credit

15 April 2023 Visa Confidential 59


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Issuer Requirements and Considerations

AFT Refund – Processing Considerations


In the event of an AFT reversal or credit adjustment advice, issuers must be aware of the
considerations for processing a reversal or adjustment.
An issuer must post an AFT credit adjustment advice within two business days. In Europe, the AFT
credit adjustment advice must be posted in the next business day upon receipt of the AFT credit
adjustment advice from the acquirer. Issuers that are not compliant may be subject to
noncompliance assessments.
Note: The AFT credit adjustment advice must also be originated in 30 calendar days or less
of the original transaction and cannot be originated if the original transaction is over 30 days
old.
Refer to the table Reversal and Adjustment Transactions Overview in AFT Refund Use Case for more
information on the reversal and adjustment transactions and associated processing considerations.

Sanctions Screening Scoring Service


This section provides issuers with implementation considerations related to the sanctions screening
scoring service.
Important: Visa provides sanctions screening scoring service solely for the convenience of issuers.
Visa makes no representations or warranties with respect to the sanctions screening scoring service
or their results. The issuer should always consult and seek approval from their internal compliance
teams on sanctions screening controls and processes and are solely responsible for their own
compliance with applicable laws and regulations. The issuer is solely responsible for its own
compliance with applicable laws and regulations.
Overview
Visa provides a sanctions screening scoring service for cross-border AFTs with Money Transfer BAIs.
Note: Issuers must subscribe to this (optional) service to receive the score.
The acquirer, service provider, or merchant sends the Money Transfer AFT. VisaNet checks sender
data against applicable sanctions lists to arrive at a score that indicates how closely the sender and
recipient data matches any sanctions list entries. Visa will approve or decline a transaction based on
the sanction screening results.
For the Europe Regions processing EEA money transfer AFTs, the sanctions screening score will be
shared with issuers that have opted to receive it.
Eligible Money Transfer BAIs are AA, BI, PP, WT, and FT.

15 April 2023 Visa Confidential 60


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Issuer Requirements and Considerations

Issuer Reporting Requirements


AFTs must be reported on the Quarterly Operating Certificates with the issuer's purchasing volume.
Note:
l In the U.S. region, AFTs generated as part of a financial institution-offered P2P Money
Transfer service do not have be reported on the Quarterly Operating Certificate.
l In Europe, Canada, CEMEA, and AP, acquirers are no longer required to submit Visa
Direct transactions manually. A new Global Operating Certificate (GOC) tool1 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.

Issuer Certification Requirements


The issuers and issuer processors 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).

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

15 April 2023 Visa Confidential 61


Appendix A
AFT Data Elements and Processing
Rules

This appendix provides the data elements and message requirements unique to AFTs.

15 April 2023 Visa Confidential 62


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

AFT Key Data Elements


Table 13: AFT Key Data Elements (1 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

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

Field 3 Not applicable Must contain a value of 10 (positions Note:


1-2).
Processing Code l All Canada, CEMEA, Europe,
When processing an adjustment for LAC and U.S. issuers are
Length: 3
an AFT the processing code should required to support AFTs with
Format: 6 BCD be: Processing Code 10 .
1

02 (Adjustment-debit) l Acquirers must not send cross-


22 (Adjustment-credit) border AFTs to issuers not
enabled to receive Processing
Note: Positions 3-6 contain 0000 for Code 10.
all countries but Brazil.
Brazil: Position 3-4 contains a If an AFT is sent to an issuer that is
default value of 20 for a combo card. not set up, or has not opted in, to
Position 5-6 contain 00. receive Processing Code 10, V.I.P.
converts Processing Code 10 to
purchase Processing Code of 00
(Goods/Service purchase-debit).
Brazil: Some issuers in Brazil issue
"Combo Cards" that have 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.

15 April 2023 Visa Confidential 63


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (2 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 4 TCR 0, pos. 77-88 If acquirers, service providers, or The total amount of the AFT
merchants use Field 28 Transaction including all fees.
Amount, Source Amount
Fee Amount/AFT Service Fee or Field
Transaction Conceptual Example:
Length: 12 54 Additional Amount/AFT Foreign
Length: 6 Exchange Markup Fee, they must Transaction Amount: 50.00
Format: UN
Format: 12 BCD include those amounts in Field 4. AFT Service Fee: 2.00
AFT Foreign Exchange Markup
Fee: 2% of 50.00 = 1.00 (not
applicable to prepaid load)
Field 4 contains: 50.00 + 2.00 +
1.00 = 53.00
Field 28 contains: 2.00
Field 54 contains: 1.00
Note:

l 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.
l In the V.I.P. manual, this field is
called "Transaction Fee
Amount."

15 April 2023 Visa Confidential 64


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (3 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 18 TCR 0, pos. 133-136 Value depends on value of BAI (Field For AA, use 4829, 6012, or 6211
104) and the type of merchant
Merchant Type Merchant Category l 4829 – Non-Financial
performing the transaction:
(Row 1 of 2) Code Institution Wire Transfer Money
Merchant Category Code (MCC): Orders (WTMOs) (Not
Length: 2 Length: 4
For AA, use 4829, 6012, or 6211 (In applicable in the U.S. with BAI
Format: 4 BCD Format: UN AA)
the U.S, MCC 4829 is not applicable
with BAI AA) l 6012 – Financial Institution -
For BI, use 6012 Merchandise Services

For FD, use any MCC associated to l 6211 – Brokerage


the merchant For FD, use any MCC associated to
For PD, use 8931 the merchant

For PP, use 4829 or 6012 For PD, use 8931 Accounting,
Auditing and Bookkeeping services
For TU, use 6012, 6051 or 6540 including Payroll
2
For WT, use 6051 For PP, use 4829 or 6012
3
For FT, use 4829, 6540 or 6012
l 4829 – Non-Financial
Institution Wire Transfer Money
Orders (WTMOs)
l 6012 – Financial Institutions -
Merchandise and Services
For BI, use 6012

l 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

l 6012 Financial Institutions –


Merchandise and Services
l 6051 Non-Financial
Institutions-Foreign Currency,
Non-Fiat Currency (example,
Cryptocurrency), Money Orders
(not Money Transfer), Travelers
Cheques, and Debt Repayment
l 6540 Non-Financial Institutions
– Stored Value Card Purchase/
Load

15 April 2023 Visa Confidential 65


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (4 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 18 For WT, use 6051


Merchant Type l 6051 – Non-Financial Foreign
(Row 2 of 2) Currency, Non-Fiat Currency
Length: 2 (example, Cryptocurrency),
Money Orders (not Money
Format: 4 BCD Transfer), Travelers Cheques,
and Debt Repayment
For FT, use 4289, 6540, or 6012

l 4829 – Non-Financial
Institution Wire Transfer Money
Orders (WTMOs)
l 6540 – Non-Financial
Institutions –Stored Value Card
Purchase/Load
l 6012 – Financial Institutions –
Merchandise and Services
l 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
Mandatory for Domestic and
Cross-border (Money and Non-
money Transfer) AFTs.

15 April 2023 Visa Confidential 66


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (5 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 22 Valid values include: This field indicates:


POS Entry Mode l 01 Manual (key entry) l The method used to enter the
Code payment credential and card
l 02 Magnetic stripe read
Fixed Length: 3 expiration date,
l 05 Integrated chip card read
N, 4-bit BCD l If an electronic terminal is used,
Note: For Field 22, value 05 should and,
be used only in countries in CEMEA
l The capability of the terminal to
and for Transferencias 3.0
capture online PINs for
transactions in Argentina.
transactions processed through
l 07 Contactless device-read- VisaNet.
originated using qVSDC chip data
Note:
rules
l Any transaction that uses stored
l 10 Credential-on-File: Merchant
credentials should use POS
initiates transaction for
Entry Mode Code = 10.
cardholder using credentials
stored on file l Merchants use POS Entry Mode
Code = 10 based on the
l 90 Magnetic stripe read
payment credentials they have
Note: Acquirers must select the associated with the cardholder
appropriate value for card present or profile or wallet.
card not present transactions. If the
For all valid values and for
transaction data is not accurate, Visa
complete details on these fields,
will charge Data Integrity Fees on
refer to the V.I.P. manuals.
the acquirer.

Field 25 Not applicable Examples of valid values include: Contains the POS Condition Code
applicable to the access channel.
POS Condition 59 indicates an e-commerce
Code transaction Note: The value 05 should not be
used for online merchants,
Length: 2 01 indicates a cardholder not
including online gambling.
present transaction
Format: 2 BCD
Note: For CPS qualification, a value
05 indicates a cardholder present,
59 is required.
card not present transaction
For all valid values and complete
Note: Acquirers must select the
details on this field, refer to the
appropriate value for card present or
V.I.P. manuals.
card not present transactions. If the
transaction data is not accurate, Visa
will charge Data Integrity Fees on
the acquirer.

15 April 2023 Visa Confidential 67


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (6 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 28 TCR 4, pos. 51-58 Acquirers, service providers, or Values in this field must be in the
merchants supporting Field 28 and same currency and format as the
AFT Service Fee AFT Service Fee
charging senders a fee for the AFT currency code outlined in Field
Length: 9 Length: 8 may provide the fee in this field. 49/TCR 0.
Format: AN Format: UN When present, this field contains the
This field is not present in response
sender’s AFT Service Fee as assessed
messages.
by the originating entity.
Refer to Field 4 for an example.
For V.I.P:
Important: The Prefix value
Position 1: Prefix—Must be
(position 1) is for informational
populated with a value of D (Debit
purposes only. Clients should not
to cardholder).
use the prefix for settlement
Note: The 0220 Deferred Clearing purposes. Instead, they should
Advice will contain a value of C look at the message type and
(Credit to cardholder) even though Processing Code to determine if
this is actually a debit. the amount is a credit or a debit.
Positions 2-9: AFT Service Fee— Note: Field is not sent unless the
Contains the AFT service fee issuer opts in.
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 Not applicable A valid number provided by Visa. This code identifies the financial
institution acting as the acquirer of
Acquiring
the AFT.
Institution
Identification Field 32 reject codes are:
Code
0020 = Invalid length
Length: Variable
0021 = Invalid value
and up to 11
digits 0287 = Field missing

Format: 4-Bit 0531 = Non-domestic transaction


BCD Mandatory for Domestic and
Cross-border (Money and Non-
money Transfer) AFTs.

15 April 2023 Visa Confidential 68


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (7 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 34 Not Applicable Contains value of 01 (DAF indicator) This field is Tag-Length-Value
(TLV).
Dataset ID: 01
Testing and activation are required
Authentication
to implement this field for the first
Data
time.
Tag: C0
Acquirers and issuers in the AP
Authentication (except for Bangladesh, India,
Program Japan, and Nepal), Canada, CEMEA,
Length: 2 Europe, LAC, and U.S. regions that
support receiving Field 34 will
Format: AN receive the Authentication
Program tag in AFT request and
response messages to identify
transactions that are authenticated
as part of the Digital Authenti­
cation Framework.

Field 34 Not Applicable This field is Tag-Length-Value


(TLV).
Dataset ID: 02
This field has these new tags
Acquirer and
added to Dataset ID 02 that will
Merchant
contain merchant and acquirer
Information
information:

l C0: Merchant Address Street


l C1: Acquirer Name
l C2: Acquirer Street Address
l C3: Acquirer City Name
l C4: Acquirer State/Province
Code
l C5: Acquirer Postal Code
l C6: Acquirer Country Code
Note: Effective 29 May 2023, for
cross-border AFTs destined to
issuers in Australia or Canada, Visa
will insert the acquirer address
data in this field in the these tags
C1–C6 into the message before
forwarding it to the issuer.

15 April 2023 Visa Confidential 69


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (8 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 34 Not Applicable This field will contain the merchant


street address.
Dataset ID: 02
Merchant
Address Street
Tag: C0
Length: 99
Format: ANS,
EBCDIC

Field 34 Not Applicable This field will contain the acquirer


name.
Dataset ID: 02
Acquirer Name
Tag: C1
Length: 25
Format: ANS,
EBCDIC

Field 34 Not Applicable This field will contain the street


address.
Dataset ID: 02
Acquirer Street
Address
Tag: C2
Length: 99
Format: ANS,
EBCDIC

Field 34 Not Applicable This field will contain the acquirer


city name.
Dataset ID: 02
Acquirer City
Name
Tag: C3
Length: 50
Format: ANS,
EBCDIC

15 April 2023 Visa Confidential 70


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (9 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 34 Not Applicable This field will contain the state/


province code, where applicable.
Dataset ID: 02
Acquirer State/
Province Code
Name
Tag: C4
Length: 3
Format: AN,
EBCDIC

Field 34 Not Applicable This field will contain the acquirer


postal code.
Dataset ID: 02
Acquirer Postal
Code
Tag: C5
Length: 5–9
Format: AN,
EBCDIC

Field 34 Not Applicable This field will contain the character


country code of the acquirer.
Dataset ID: 02
Acquirer
Country Code
Tag: C6
Length: 3
Format: A,
EBCDIC

Field 42 Not applicable Must contain a unique identifier for The unique CAID from the original
the originating entity. transaction message is required in
Card Acceptor
any subsequent messages,
Identification
including reversals, disputes, and
Code
representments.
Length: 15
V.I.P. Edit:
Format: ANS,
This field must contain a non-zero
EBCDIC, 15
value.
bytes
Mandatory for Domestic and
Cross-border (Money and Non-
money Transfer) AFTs.

15 April 2023 Visa Confidential 71


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (10 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 43 TCR 0, pos. 92-132 Merchant Name position 1-25 Mandatory for Domestic and
Cross-border (Money and Non-
Card Acceptor Merchant Name, Merchant City Name position 26-38
money Transfer) AFTs.
Name/Location, Merchant City, and
Merchant Country Code position
pos. 1–40 Merchant Country Money Transfer Field Format
39-40 (two-character country code)
Code
Length: 40 The Card Acceptor Name field
Transaction Type: Money Transfer
Length: 40 must contain the "Doing Business
Format: 40 ANS , (BAI = AA, BI, FT, PP, WT)
As" name or abbreviation of the
EBCDIC Format: AN
This field must contain merchant or merchant (1-4 characters) and be
Row 1 of 2 service provider information (name, the name most recognizable to the
city, and country code). cardholder in addition to the
For an AFT that is used to fund a recipient's name.
Money Transfer transaction, this field The Merchant Name field must
may also contain the name of the contain the full Merchant Name or
4
recipient of the funds . conform to this format when
All regions: Must contain Money including a recipient name:
Transfer provider's name or Format Field Position Data
abbreviation. Inclusion of recipient
Pos. 1-4: Merchant Name
name is optional but recommended.
(abbreviated)
If recipient name is included, the
field will contain an asterisk (*) in Pos. 5: Asterisk (*)
position 5, followed by the
Pos. 6-25: Recipient Name
recipient's name.
(optional, but recommended)
Examples:
Example #1: AFT for a P2P
payment (BAI – PP)
MTMT*MarySmith
MTMT = generic example of a
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.

15 April 2023 Visa Confidential 72


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (11 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 43 Not applicable Note: Pos. 26-38: Merchant City


Name – Do not use the value of
Card Acceptor
“Visa Direct” in the merchant city
Name/Location,
name subfield for cross-border
pos. 1–40
AFTs destined to Australia or
Length: 40 Canada, and always populate the
Format: 40 ANS , actual merchant city name.
EBCDIC Note: Refer to the V.I.P. and BASE II
Row 2 of 2 manuals for normal processing
instructions.

Field 44.13 Not applicable Contains the Cardholder Authenti­


cation Verification Value (CAVV)
CAVV Results
results code that identifies the
Code
outcome of CAVV validation.
Length: Fixed
Refer to the Full Service POS
Format: 1 ANS, Technical Specifications for
EBCDIC; 1 byte complete details about this field.

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

Field 49 TCR 0 This field contains a 3-digit code If AFT Service Fee (Field 28/TCR 4)
that identifies the currency of and/or AFT Foreign Exchange
Currency Code, Source Currency Code
transaction amount. Markup Fee (Field 54/TCR4) is
Transaction
Length: 3 present in the message, the fees in
Length: 3 those fields must be in the same
Format: AN
Format: 4 BCD 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.

15 April 2023 Visa Confidential 73


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (12 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 54 TCR 4, pos. 112-119 Note: This field is applicable only if When present, this field contains
the AFT is a cross-border the sender’s AFT Foreign Exchange
AFT Foreign AFT Foreign Exchange
transaction. Markup Fee as assessed by the
Exchange Markup Fee
originating entity.
Markup Fee Acquirers, service providers, or
Length: 9
merchants that support Field 54 and Values in this field must be in the
Length: 20
Format: UN charge senders a Foreign Exchange same currency and format as the
Format: 1 byte Markup Fee on cross-border AFTs currency code outlined in Field
binary + 20 ANS may provide the foreign exchange 49/TCR 0.
fee in this field.
This field is not present in response
The V.I.P. format of this field follows: messages.
Positions 1-2: Account Type—Must Refer to Field 4 for an example.
contain a value of 00 (Not applicable
Note: Field is not sent unless the
or not specified).
issuer opts in.
Positions 3-4: Amount Type—Must
V.I.P. Edit:
contain a value of 95 (VMT).
If the Currency Code (positions
Positions 5-7: Currency Code—Must
5-7) is not the same currency code
contain the same currency code
as in Field 49, V.I.P. will decline the
value as in Field 49 Currency Code,
request message with the response
Transaction.
code value of 12 (Invalid
Position 8: Amount, Sign—Must transaction).
contain a value of D (Negative
Important: The Amount, Sign
balance).
(position 8) is for informational
Note: While C (Positive balance) is a purposes only. Clients should not
valid value in this field, it is not use the sign for settlement
applicable to this usage. purposes. Instead, they should
look at the message type and
Positions 9-20: Amount—Contains
Processing Code to determine if
the sender's AFT Foreign Exchange
the amount is a credit or a debit.
Markup Fee as assessed by the
acquirer, service provider, or Note: Refer to the V.I.P. manuals
merchant (if applicable). This for complete details on the length
subfield must be right-justified with and format of this field.
leading zeros, and include an
V.I.P. Edit:
implied decimal relative to the
currency code specified in Field 49. If the Amount (positions 9-20) is
The amount in this subfield must be not correctly formatted according
in the same currency as Field 49. to the currency code outlined in
Field 49, V.I.P. will decline the
Note: Acquirers, service providers,
request message with the response
or merchants must include the
code 12 (Invalid transaction).
amount in this field in the total
amount in Field 4.

15 April 2023 Visa Confidential 74


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (13 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 56 Not applicable Valid values are: This field is Tag-Length-Value


(TLV).
Dataset ID 01 l 05 (Payer (sender))
Contains values that identify if an
Tag: 82 l 06 ( Payee (recipient))
account is a sender account or
Account recipient account.
Identifier
Note:
Reference Code
Length: 2 l If this tag contains the value 06,
V.I.P. will send it to the recipient
Format: N issuer.
l If this tag contains the value 05,
V.I.P. will not send it to the
recipient issuer.

Field 56 Not applicable This field is Tag-Length-Value


(TLV).
Dataset ID 01
Contains the account identifier
Tag: 83
value of the sender or recipient.
Account
Note: V.I.P. will only send Tag 83 to
Identifier Value
the recipient issuer if Tag 82
Length: 34 contains the value of 06.
Format: ANS

Field 56 Not applicable Valid values are: This field is Tag-Length-Value


(TLV).
Dataset ID 01 l 00 (Other)
Contains the account identifier
Tag: 84 l 01 (Routing transit number (RTN)
type.
Account and bank account)
Note: V.I.P. will only send Tag 84 to
Identifier Type l 02 (IBAN)
the recipient issuer if Tag 82
Code
l 03 (Card Account) contains the value of 06.
Length: 2
l 04 (Email)
Format: AN
l 05 (Phone Number)
l 06 (Bank account number (BAN)
and bank identification code
(BIC))
l 07 (Wallet ID)
l 08 (Social network ID)

15 April 2023 Visa Confidential 75


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (14 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 56 Not applicable Optional for Domestic and Cross-


border (Money-Transfers and Non-
Dataset ID 03
money Transfers) AFTs. Tags
Customer ID include:
Length: Various l 9F1F – Customer Reference
Format: Various Number
l 9F20 – Identification Type Code
l 9F21 – Identification Sub-Type
l 9F22 – Identification Value
l 9F24 – Identification Issuing
Country

Field: 56 Not applicable The valid values are: This field is Tag-Length-Value
(TLV).
Tag: 9F1F l 05 (Payer (sender))
Containing a code that denotes
Length: 2 l 06 (Payee (recipient))
whether the customer identifi­
Customer cation data belongs to the sender
Reference or the recipient.
Number
Required: Customer ID of recipient
Format: N is required for transactions out of
and within Brazil.
Optional: for all other countries,
but strongly recommended.
Important: If this tag is present,
the following tags must also be
present:

l Tag 9F20
l Tag 9F22
Tag 9F21 is optional. Tag 9F24 is
conditional, depending on the
value populated in Tag 9F20.

15 April 2023 Visa Confidential 76


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (15 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field: 56 Not applicable This tag will contain the type of This field is Tag-Length-Value
sender or recipient identification. (TLV).
Tag: 9F20
The valid values are: Containing the type of sender
Length: 4
identification.
Identification l BTHD (Date of birth)
Type Code l CUID (Customer identification
Format: A (unspecified))
l NTID (National identification)
l PASN (Passport number)
l DRLN (Driver license)
l TXIN (Tax identification)
l CPNY (Company registration
number)
l PRXY (Proxy identification)
l SSNB (Social security number)
l ARNB (Alien registration number)
l LAWE (Law enforcement identifi­
cation)
l MILI (Military identification)
l TRVL (Travel identification (non-
passport))
l EMAL (Email)
l PHON (Phone number)

Field: 56 Not applicable The valid values are: This field is Tag-Length-Value
(TLV).
Tag: 9F21 l 0B (Business)
This tag denotes whether the tax
Length: 2 l 0I (Individual)
ID pertains to a business or
Identification individual, when Tag 9F20 contains
Subtype the value of TXIN (Tax identifi­
Format: AN cation).

Field: 56 Not applicable When Tag 9F20 contains the value of This field is Tag-Length-Value
BTHD (Date of birth), this tag must (TLV).
Tag: 9F22
contain a date of birth in ccyymmdd
This tag will contain an acquirer-
Length: 35 format where:
populated value associated with
Identification l cc = century the Identification Type Code
Value provided in Tag 9F20.
l yy = year
Format: ANS
l mm = month
l dd = day

15 April 2023 Visa Confidential 77


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (16 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field: 56 Not applicable This tag will contain the 3-digit ISO This field is Tag-Length-Value
country code of the issuing country (TLV).
Tag: 9F24
when Tag 9F20 contains an
Length: 3 applicable value.
Identification
Issuing Country
Format: N

Field: 56 Not applicable Required for cross-border and This field is Tag-Length-Value
domestic money transfer and non- (TLV).
Usage 2
money transfer out of and within
Required for transactions out of
Dataset ID 05 South Africa.
and within South Africa, optional
Account Owner In Canada, Cross-border transactions for all other countries.
Data into and out of Canada must include
The field is defined with the
Length: Various the address of the person or entity
following tags:
receiving the funds from the AFT.
Format: ANS l Tag 80: Account Reference
Number
l Tag 83: Account Owner Name,
Given
l Tag 84: Account Owner Name,
Middle
l Tag 85: Account Owner Name,
Last

15 April 2023 Visa Confidential 78


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (17 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 56 Not applicable Required for cross-border money This tag identifies to which account
and non-money transfer transactions or entity the name data belongs.
Account
out of South Africa.
Reference If this tag is present, it must
Number Sender Name and/or Recipient contain one of the these values:
Name is mandatory.
Tag: 80 l 05 (Sender Name)

Length: 1 Sender: From where the funds


Format: N are pulled.
l 06 (Recipient Name)
Recipient: To whom the funds
are sent.
The originating entity can use code
05 to share additional validation
performed on the Sender at the
time of processing the AFT.
Note:

l Field 56 should not contain


more than one Account
Reference code 05 (Sender
Name) and one Account
Reference code 06 (Recipient
Name).
l The tags are mandatory in
certain markets for them to
follow the instructions as
defined in the detail for each
tag. In the markets it is not
listed as mandatory, it is
considered optional.

15 April 2023 Visa Confidential 79


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (18 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 56 Not applicable Required for cross-border money This tag identifies the first name of
and non-money transfer transactions the account or entity.
Account Owner
out of South Africa.
Name, Given If this tag is present, it must only
Sender Name and/or Recipient contain alphanumeric characters A
Tag: 83
Name is mandatory. - Z and 0 - 9.
Length: 35
This field must not contain:
Format: AN
l All spaces
l All zeroes
l A question mark
l All numeric
Note: The tags are mandatory in
certain markets for them to follow
the instructions as defined in the
detail for each tag. In the markets
it is not listed as mandatory, it is
considered optional.

Field 56 Not applicable Required for cross-border money This tag identifies the middle name
and non -money transfer of the account or entity.
Account Owner
transactions out of South Africa.
Name, Middle If this tag is present, it must only
Sender Name and/or Recipient contain alphanumeric characters A
Tag: 84
Name is mandatory. - Z and 0 - 9.
Length: 35
This field must not contain:
Format: AN
l All spaces
l All zeroes
l A question mark
l All numeric
Note: The tags are mandatory in
certain markets for them to follow
the instructions as defined in the
detail for each tag. In the markets
it is not listed as mandatory, it is
considered optional.

15 April 2023 Visa Confidential 80


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (19 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 56 Not applicable Required for cross-border money This tag identifies the last name of
and non -money transfer the account or entity.
Account Owner
transactions out of South Africa.
Name, Last If this tag is present, it must only
Sender Name and/or Recipient contain alphanumeric characters A
Tag: 85
Name is mandatory. - Z and 0 - 9.
Length: 35
This field must not contain:
Format: AN
l All spaces
l All zeroes
l A question mark
l All numeric
Note: The tags are mandatory in
certain markets for them to follow
the instructions as defined in the
detail for each tag. In the markets
it is not listed as mandatory, it is
considered optional.

15 April 2023 Visa Confidential 81


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (20 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field: 56 Not applicable Optional for Domestic and Cross- This field is Tag-Length-Value
border money and non-money (TLV).
Usage 2
transfer AFTs.
Contains the recipient's full
Dataset ID 05
In Canada, Cross Border transactions address.
Length: Various into and out of Canada must include
Note: Must be the recipients
Recipient the address of the person or entity
primary residential address and
Address receiving the funds from the AFT.
not a P.O. Box Address.
Format: ANS The field is defined with the these
tags:

l Tag 86: Account Owner Address


Line 1
l Tag 87: Account Owner Address
Line 2
l Tag 88: Account Owner Street
Name
l Tag 89: Account Owner Building
Number
l Tag 8A: Account Owner Postal
Code
l Tag 8B: Account Owner City
Name
l Tag 8C: Account Owner Country
Subdivision Code, Minor
l Tag 8D: Account Owner Country
Subdivision Code, Major
l Tag 8E: Account Owner Country
Code

Field 56 Not applicable Required for cross-border money This tag will contain the first line of
and non-money transfer the recipient address.
Account Owner
transcriptions into and out of
Address Line 1 Note: This tag is required for
Canada.
transactions into and out of
Tag 86
Canada. Otherwise, it is optional.
Length: 99
Format: ANS

15 April 2023 Visa Confidential 82


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (21 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 56 Not applicable This tag will contain the second line Note: This tag is optional.
of the recipient address.
Account Owner
Address Line 2
Tag: 87
Length: 99
Format: ANS

Field 56 Not applicable This tag will contain the street name Note: This tag is optional.
of the recipient address.
Account Owner
Street Name
Tag: 88
Length: 99
Format: ANS

Field 56 Not applicable This tag will contain the house or Note: This tag is optional.
building number of the recipient
Account Owner
address.
Building
Number
Tag: 89
Length: 16
Format: ANS

Field 56 Not applicable This tag will contain the postal code Note: This tag is optional.
of the recipient address.
Account Owner
Postal Code
Tag: 8A
Length: 16
Format: ANS

Field 56 Not applicable This tag will contain the city name of Note: This tag is mandatory for
the recipient address. transactions into and out of
Account Owner
Canada. Otherwise, it is optional.
City Name
Tag: 8B
Length: 25
Format: ANS

15 April 2023 Visa Confidential 83


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (22 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 56 Not applicable This tag will contain the country ISO Note: This tag is optional.
subdivision code of the recipient
Account Owner
address.
Country
Subdivision
Code, Minor
Tag: 8C
Length: 16
Format: ANS

Field 56 Not applicable This tag will contain the state or Note: This tag is mandatory if Tag
province ISO subdivision code of the 8E contains the value of CAN or
Account Owner
recipient address. USA. Otherwise, it is optional.
Country
Subdivision
Code, Major
Tag: 8D
Length: 3
Format: ANS

Field 56 Not applicable This tag will contain the fixed length Note: This tag is mandatory for
alpha-3 ISO country code of the transactions into and out of
Account Owner
recipient address. Canada. Otherwise, it is optional.
Country Code
Tag: 8E
Length: 3
Format: A

Field 59 Not applicable This field contains geographical


data for the card acceptor.
National Point-
of-Service Note: For transactions originating
Geographical in Brazil, Canada, or the U.S. only,
Data refer to:
Length: Variable l VisaNet Authorization-Only
length up to 14 Online Messages Technical
Format: ANS, Specifications
EBCDIC l Full Service POS Online
Messages Technical Specifi­
cations

15 April 2023 Visa Confidential 84


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (23 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 59 Not applicable This is a new subfield in an existing


field and contains the merchant
National Point-
postal code.
of-Service
Geographical The subfield is left-justified and
Data space-filled.
Card Acceptor Note: This field is for cross-border
Postal Code AFTs destined to Australia or
Canada originating outside Brazil,
Positions 1–8
Canada and the U.S.
Length: 8
Format: ANS,
EBCDIC

Field 59 Not applicable This is a new subfield in an existing


field and contains the major and
National Point-
minor geographical division codes
of-Service
in a country, where applicable,
Geographical
according to the country’s
Data
standard format.
Card Acceptor
The subfield is left-justified and
State or
must be space-filled when minor
Province Code
and/or major division codes are
Positions 9–14 not applicable.
Length: 6 Note: This field is for cross-border
Format: ANS, AFTs destined to Australia or
EBCDIC Canada originating outside Brazil,
Canada and the U.S.

15 April 2023 Visa Confidential 85


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (24 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 60.2 Not applicable Valid values for Terminal Entry Refer to Full Service POS Online
Capability are: Messages – Technical Specifications
Terminal Entry
for a complete list of valid values
Capability l 1 Terminal not used
and for the details of this field.
Length: 1 Note: For card not present
Format: 1 N transactions, use this value.
l 2 Magnetic stripe read capability
l 3 QR Code
l 5 Contact chip, magnetic stripe,
or proximity-capable terminal,
indicating that 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.
l 8 Proximity-read-capable. For
Visa contactless, an 8 should be
used only if Visa contactless is
supported and contact chip is
not.
l 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 Not applicable 7 Cryptocurrency If the AFT is prefunding a wallet


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

15 April 2023 Visa Confidential 86


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (25 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 60.8 Not applicable Examples of valid values for e- Refer to existing BASE I manuals
commerce transactions include 5–8. for a complete list of valid values
Mail/Phone/
and for the details of this field. For
Electronic l 05 Fully authenticated e-
Europe, also refer to 3DS manual.
Commerce commerce transaction
Payment
l 06 Merchant attempted to
Indicator
authenticate the cardholder
(BASE I only)
l 07 Non-authenticated e-
Length: 1 commerce transaction
Format: 2N, 4- l 08 Non-secure e-commerce
bit BCD transaction

Field 60.10 Not Applicable Value: 1 Mandated for U.S. domestic


only.
Additional
Authorization Indicates that the Terminal accepts
Indicators partial authorization responses.
Position: 12 Participating acquirers must
include code 1 in this field.
Partial Authori­
zation
Refer to the Visa Partial Authori­
Length: 1 zation Service Description and
Implementation Guide, Visa Supple­
Format: 1 N
mental Requirements, Version 3.1.

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

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


merchants, and recipient issuers
Transaction ID Transaction ID
must be prepared to receive this
Length: 8 Length: 15 field.
Format: 15 BCD Format: UN Note: If an AFT has a
corresponding OCT, originating
entities 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.

15 April 2023 Visa Confidential 87


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (26 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 62.20 Not applicable Visa assigns the first six positions MVV is used to identify merchants
and assists the acquirer in assigning that participate in a variety of
Merchant Verifi­
the last four. programs. The MVV is unique to
cation Value
the merchant.
(MVV) Acquirers are not required to provide
the last four digits of the MVV. V.I.P. edits:
Length: 10
If the MVV is not valid, V.I.P. rejects
Format: 4-bit
the transaction with reject code
BCD, 5 bytes
0720.

Field 63.1 Not applicable Acquirers, service providers, or Note: If an acquirer, service
merchants must send a value of provider, or merchant sends the
Network Identi­
0000 (Priority Routing) or 0002 transaction with a value of 0000
fication Code
(Network ID 2). (Priority Routing), it will be routed
Length: 2 over network 2.
Issuers will receive a value of 0002 in
Format: 4 BCD this field.

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

Field 63.6, pos. 7 TCR 1—Additional This field must contain the value of 7
Data cryptocurrency, if the AFT is used to
Special
fund a wallet that can be used to
Condition position 74 - 75
purchase cryptocurrency.
Indicator,
Merchant Transaction
Merchant
Indicator
Transaction

15 April 2023 Visa Confidential 88


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (27 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field: 104 This field is Tag-Length-Value


(TLV).
Usage 2
This field will increase the length
Transaction
from one byte to two bytes to
Description and
allow acquirers and issuers that
Transaction-
choose to send and receive more
Specific Data
data.
Length: 1 byte
Note: Acquirers and issuers may
or 2 bytes
continue to send or receive the
field in one-byte length. However,
acquirers and issuers must only
support receiving the field in either
one-byte or two-byte and not
both.
Testing and activation are required
to implement this enhancement.

Field: 104 Not applicable Contains the Payment Facilitator ID This field is Tag-Length-Value
(TLV).
Usage 2
Required when the AFT transaction
Dataset ID 56
is related to facilitating payments
Tag: 01 such as funds disbursements.
Length: 11
Payment
Facilitator ID
Format: AN

Field: 104 Not applicable Contains the Sponsored Merchant This field is Tag-Length-Value
ID, where Payment Facilitator is (TLV).
Usage 2
included.
Required when the AFT transaction
Dataset ID 56
is related to facilitating payments
Tag: 02 such as funds disbursements.
Length: 15
Sponsored
Merchant ID
Format: AN

15 April 2023 Visa Confidential 89


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (28 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 104 Not applicable Contains the Full Acceptor Legal Full acceptor legal business name
Business name required
Usage 2
Optional for Domestic Money and
Dataset ID 56
Non-money Transfer transactions.
Acceptor Legal
Mandatory for Cross-border
Business Name
Money and Non-money Transfer
Tag: 81 AFTs.
Length: 25 Use this field to populate the
Format: ANS, merchant name for all cross-border
EBCDIC AFTs destined to Canada and
Australia (for all BAIs).

Field: 104 Not applicable Contains the Full Payment Facilitator This field is Tag-Length-Value
Name (TLV).
Usage 2
Full Payment Facilitator name is
Dataset ID 56
required to assist issuer screening.
Tag: 82
Required when the AFT transaction
Length: 25 is related to facilitating payments
Payment such as funds disbursements.
Facilitator Name
Format: ANS

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

15 April 2023 Visa Confidential 90


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (29 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field: 104 Not applicable Contains acquirer-populated This field is Tag-Length-Value


purpose of payment code, that vary (TLV).
Usage 2
by country.
Optional for Domestic Money
Dataset ID 57
Transfer and Non-money Transfer
Tag: 82 AFTs.
Length: 12 This field must contain a code
Purpose of reflecting the purpose of payment
Payment to classify and report the nature
and purpose of the Transaction.
Format: AN The acquirer must submit the
correct purpose of payment code
for the recipient issuer’s
jurisdiction and restrict clients to a
predetermined list of purpose of
payment codes.
The only valid values for this field
include regulatory published/
recognized codes or a code from
the Visa Standardized Purpose of
Payment list. See Appendix
Purpose of Payment –
Standardized Codes List.
Note: Effective October 2021, this
field will be available to all regions.
This field is mandatory for
outbound transactions sent into
India, Bangladesh, Argentina, and
Egypt.
Note: Effective 2 September
2023

l Acquirers must send this field in


cross-border AFTs sent to Chile,
Colombia and Mexico.
l Issuers in Mexico, Chile and
Colombia must be ready to
receive and process this field.

15 April 2023 Visa Confidential 91


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (30 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 104, Usage Not applicable Values are 00-99 Contains the risk score for the Visa
2, Dataset Value transaction.
Hex 5B
Advisor E-Commerce Scoring
Visa Risk Service. It indicates the degree of
Assessment risk associated with a transaction.
Data
There is PCR level participation to
Tag: 01 receive this score in the response.
A valid MVV is also required.
Risk Score
Note: Tag 01—Risk Score is always
Length: 2
present in Field 104, Usage 2,
Format: N Dataset ID 5B.

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

Field 104 Not applicable Tag 84 will contain the sanctions This field is Tag-Length-Value
screening scoring results code for (TLV).
Usage 2
AFT messages and will be present in
Full financial request messages are
Dataset ID 5B 0100 Authorization and 0200
sent to issuers that choose to
Tag: 84 receive screening scores.
Length: 3
Sanctions
Screening
Scoring Results
Code
Format: N

15 April 2023 Visa Confidential 92


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (31 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 104, Usage Not applicable Field 104, Dataset ID 5F is a Tag-


2, Length-Value (TLV) encoded field
that is currently defined with eight
Dataset ID 5F
different tags (Tag 01–Tag 08. 0A.)
Sender Data
Important: All tags are conditional
(Row 1 of 3)
or optional based on the specific
effective from type of AFT (i.e., BAI), region and
23 April 2022 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.

l Acquirers, service providers, and


merchants must not format tags
as right-justified with leading
spaces.
l Acquirers, service providers, and
merchants should not pad tags
to their maximum length with
spaces or binary zeros.

15 April 2023 Visa Confidential 93


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (32 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 104 Not applicable V.I.P. Edit:


Usage 2, Dataset This field should not be present in
ID 5F responses (authorization or full-
financial) and, if present, it will be
Sender Data
dropped from the message by V.I.P.
(Row 2 of 3)
If the acquirer, service provider, or
effective from
merchant does not provide a given
23 April 2022
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):

l 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).

15 April 2023 Visa Confidential 94


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (33 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 104 Not applicable This field is Tag-Length-Value


(TLV).
Usage 2, Dataset
V.I.P. Edit (All AFTs Other Than
Value Hex 5F
Money Transfer): If the issuer PCR
Sender Data is not set up in the VisaNet system
(Row 3 of 3) to support Field 104 in TLV format
effective from and this field is present in the
23 April 2022 message, Visa drops Field 104 from
the message and forwards the
transaction to the issuer.
V.I.P. Edit (All AFTs): If the issuer
PCR is not set up to 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): V.I.P. 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.
V.I.P. Edit: Effective October
2023, V.I.P. rejects AFTs with the
existing reject code 0494 (Field or
data missing or invalid) if this field
is not populated for cross-border
AFTs.

Field: 104 Not applicable A numeric identifier provided to This field is Tag-Length-Value
uniquely identify the recipient of the (TLV).
Usage 2
AFT funds. Could represent an
This field is optional for Domestic
Dataset ID 5F invoice number, other account
and Cross-Border Money and Non-
Tag: 01 identifier, or specific transaction
money Transfer AFTs.
reference number.
Length: 16 Inclusion of this tag is conditional;
This tag is conditional; if the
Sender if the sender’s account number
recipient’s account number (Tag 02)
Reference (Tag 02) is not available or not
is not available or not applicable this
Number applicable to the transaction, this
tag must be present and contain a
tag must be present and contain a
Format: AN reference number for the intended
reference number for the sender.
recipient of the funds. This tag can
also be present along with Tag 01.

15 April 2023 Visa Confidential 95


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (34 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field: 104 Not applicable Cross-border: Account number of In an AFT this field contains the
the recipient account being funded account number of the Recipient
Usage 2
by the AFT, is mandatory in cross- Account being funded by the AFT.
Dataset ID 5F border Money Transfer AFTs.
Note: Inclusion of this tag is
Tag: 02 Domestic: Optional in domestic conditional; Tag 01 or Tag 02 are
Length: 34 AFTs. required. If this tag is not included,
Sender Reference number (Tag 01)
Sender Account Europe intra-EEA cross-border:
must be present and contain a
number Account number of the recipient
reference number for the recipient
account being funded is mandatory
Format: AN account.
in domestic and intra-EEA Money
Transfer AFTs.

15 April 2023 Visa Confidential 96


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (35 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

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

l ? (Question mark) any special


characters (?, @, #, $, &, *, etc.)
l All numeric
l Only one character
l Fictitious name or nicknames
l Incomplete names (missing first
name or last name)
Examples:

l Doe Jane A.
l Vellaichary Jabachardinat Savi
Optional for Domestic Money and
Non-money Transfer AFTs, except
in:

l Europe
Mandatory for Cross-border
Money and Non-Money Transfer
AFTs.

15 April 2023 Visa Confidential 97


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (36 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 104, Positions: 104–138 Cross-border (including Europe Should include the details that the
intra-EEA): Must contain sender’s originating entity has collected
Usage 2, Length: 35
address. from their customer and should
Dataset Value Format: AN Domestic: May contain sender’s ideally reflect the details registered
Hex 5F Sender Address address; if not required, do not by the sender with the sender’s
Tag: 04 include this tag. issuer to whom the AFT request is
made.
Length: 35
Note: Must be the sender's
Format: AN primary residential address and
Sender Address not a P.O. Box Address.
effective from Optional for Domestic Money and
23 April 2022 Non-Money Transfer AFTs.
Mandatory for Cross-border
Money and Non-Money Transfer
AFTs.

Field 104, Usage Positions: 139–163 Cross-border (including Europe Should include the details that the
2, intra-EEA): Must contain sender’s originating entity has collected
Length: 25
city. from their customer and should
Dataset Value
Format: AN ideally reflect the details registered
Hex 5F Domestic: May contain sender’s city;
Sender City by the sender with the sender’s
if not required, do not include this
Tag: 05 issuer to whom the AFT request is
tag.
Length: 25 made.

Format: AN l Optional for Domestic Money


and Non-money Transfer AFTs.
Sender City
effective from l Mandatory for Cross-border
23 April 2022 Money and Non-money
Transfer AFTs.

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

15 April 2023 Visa Confidential 98


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (37 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 104 Positions: 166–168 Cross-border: Must contain Contains the Country of the person
sender’s country. funding the transaction.
Usage 2 Length: 3
Note: Sender country must be the Optional for Domestic Money
Dataset Value Format: AN l
sender’s country based on the and Non-money Transfer AFTs.
Hex 5F Sender Country
primary residential address.
Tag: 07 l Mandatory for Cross-border
Other Domestic: May contain Money and Non-money
Length: 3 sender’s country; if not required, do Transfer AFTs.
Format: AN not include this tag.

Sender Country This is the 3-digit ISO numeric


effective from country code.
23 April 2022

15 April 2023 Visa Confidential 99


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (38 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 104, Not applicable Cross-border: Recipient name is This field contains the name of
mandatory in cross-border Money the individual or entity that is
Usage 2, See Note.
Transfer AFTs. the intended recipient of the
Dataset Value funds. Recipient name is
U.S. Domestic: Optional in domestic
Hex 5F mandatory for cross-border money
AFTs.
Tag: 0A transfer AFTs.
Europe Domestic and Europe
Length: 30 Issuers must be prepared to
intra-EEA cross border: Recipient
receive Tag 0A/Recipient Name in
Format: AN, name is mandatory in domestic and
any AFT.
EBCDIC intra-EEA Money Transfer AFTs.
5 The maximum length of the
Recipient Name recipient name is 30 characters.
(Row 1 of 2)
effective from Recipient Name Example:
23 April 2022 The Recipient Name can be up to
thirty characters long and must be
the recipient individual or entity's
legal 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 for individual recipient
is:

l Last Name/Family Surname 1


plus space
l Last Name/Family Surname 2
(optional) plus space
l First Name plus space
l Middle Initial or Middle Name
(optional) plus space
Note: Only a valid and legal
recipient name should be
populated in this field.

15 April 2023 Visa Confidential 100


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (39 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 104, V.I.P. declines AFTs with RC 64


(Transaction does not fulfil AML
Usage 2,
requirements) if the recipient name
Dataset Value contains:
Hex 5F
l ? (Question mark) any special
Tag: 0A characters (?, @, #, $, &, *, etc.)
Length: 30 l All numeric
Format: AN, l Only one character
EBCDIC
5 l Fictitious name or nicknames
Recipient Name
(Row 2 of 2) l Incomplete names (missing first
effective from name or last name)
23 April 2022 These values are accepted:

l 0-9
l A-Z
Examples:

l Doe Jane A.
l 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.
V.I.P. Edit: Effective October
2023, V.I.P. rejects AFTs with the
existing reject code 0494 (Field or
data missing or invalid) if this field
is not populated for cross-border
AFTs.

15 April 2023 Visa Confidential 101


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (40 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 104, Usage Not applicable LAC Only


2, Dataset Value
Added to support business
Hex 63
recipient tax identification in AFTs.
Merchant VAT The recipient's tax ID is sent to the
Registration/ sender cardholder's issuing bank.
Single Business
Note: This field is Mandatory for
Reference
domestic transactions in Brazil.
Number
Issuers may need this information
Tag: 05; for reporting or for other
regulatory reasons. Contact your
Length: 20;
regional Visa representative to
Format: AN confirm if this field is required in
your country.
V.I.P. Edit: For Brazil domestic
transactions, either Tag 05 or Tag
06 must be present in an AFT, but
cannot contain both Tag 05 and
Tag 06. V.I.P. rejects transactions
with reject code 0494 (Field or data
missing or invalid) if the
transaction contains both Business
Recipient Tax ID (Tag 05) and
Individual Recipient Tax ID (Tag 06).

15 April 2023 Visa Confidential 102


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (41 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 104, Usage Not applicable LAC Only


2, Dataset Value
Added to support individual
Hex 63
recipient tax identification in AFTs.
Customer VAT The recipient’s tax ID is sent to the
Registration sender cardholder’s issuing bank.
Number
Note: This field is mandatory for
Tag: 06 domestic transactions in Brazil.
Issuers may need this information
Length: 13
for reporting or for other
Format: AN regulatory reasons. Contact your
regional Visa representative to
confirm if this field is required in
your country.
V.I.P. Edit: For Brazil domestic
transactions, either Tag 06 or Tag
05 must be present in an AFT, but
cannot contain both Tag 06 and
Tag 05. V.I.P. rejects transactions
with reject code 0494 (Field or data
missing or invalid) if the
transaction contains both
Individual Recipient Tax ID (Tag 06
and Business Recipient Tax ID (Tag
05).

Field 119, Usage Not applicable LAC only:


5;
For domestic transactions in
Settlement Argentina, acquirers and issuers
Service Data can submit and settle OCTs in the
Argentina NNSS.
Length: 139
This field contains settlement
Format: ANS,
information unique to the
EBCDIC
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),

15 April 2023 Visa Confidential 103


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (42 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

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

Field 123 Usage Not applicable This field is Tag-Length-Value


2, Dataset ID 68 (TLV).
Verification & Testing and activation are required
Token Data to implement TLV Field 123 for the
first time.
Length: Variable;
1 byte, binary + This field is defined with valid
TLV Format: 255 values in these tags:
binary and ANS,
l Tag 01: Token
EBCIDIC;
maximum 256 l Tag 03: Token Requestor ID
bytes
l Tag 80: Bound Device Index
l Tag 81: Token User Identifier
l Tag 82: Token User Application
Type
l Tag 83: Token Authentication
Factor A
l Tag 84: Token Authentication
Factor B
l Tag 85: Token Authentication
Amount

Field 123 Usage Not applicable Token that is used to replace the
2, Dataset ID 68 cardholder PAN and is a required
data element for token processing.
Tag: 01
Token
Length: 13 - 19
Format: N

15 April 2023 Visa Confidential 104


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (43 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 123 Usage Not applicable Contains the Token Requestor ID.
2, Dataset ID 68
Tag: 03
Token Requestor
ID
Length: 11
Format: N

Field 123 Usage Not applicable Value can be 01–63 (in hexadecimal Contains the Index number from
2, Dataset ID 68 format). (Decimal 1-99). the Visa database where the device
ID is stored.
Tag: 80
Note: Authorization transactions
Bound Device
with a token can contain tag 80
Index
with a zero value. This indicates
Length: 1 a device index is not available
Format: Binary for the transaction.

Field 123 Usage Not applicable Contains unique value that


2, Dataset ID 68 identifies the token user. Token
user is an entity that initiates a
Tag: 81
payment request.
Token User
Applicable for e-commerce
Identifier
transactions (device and card-on-
Length: 1 - 11 file token types).
Format: N In Europe, token user identifier
may be used to support dynamic
linking requirements of PSD2/RTS.

Field 123 Usage Not applicable Application types are: Application type of token user.
2, Dataset ID 68 Entities can be a merchant, a
l 00 = Unknown
marketplace, or a check out host.
Tag: 82
l 01 = Web
Token User
l 02 = Mobile web
Application Type
l 03 = Mobile application
Length: 1
l 04 = Marketplace application
Format: Binary
l 05 = Voice application
l 06 = Biometric application
l 07-FF = Reserved

15 April 2023 Visa Confidential 105


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (44 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 123 Usage Not applicable Authentication Values are: Contains authentication factor
2, Dataset ID 68 used by token requestors and
l 00 = No authentication method
merchants to authenticate
Tag: 83, acquired
cardholder at the time of
Token Authenti­ l 01 = Username/password transaction.
cation Factor A
l 02 = Passcode or password Applicable for e-commerce
Length: 1 transactions (device and card-on-
Consumer Device Cardholder
Format: Binary file token types).
Verification Method (CDCVM):
Row 1 of 2 l 10 = Passcode
l 11 = Password
l 12 = Pattern
l 13 = Biometric fingerprint
l 14 = Biometric facial recognition
l 15 = Biometric iris recognition
l 16 = Biometric voice recognition
l 17 = Behavioral biometric
One Time Passcode (OTP):
l 30 = Short message system
(SMS)
l 31 = Email
l 32 = Hardware token without
user verification
l 33 = Hardware token with user
verification
l 34 = Soft token
l 35 = Any other method
l 40 = Knowledge based authenti­
cation
l 41 = Out of band (OOB) authenti­
cation
l 42 = Local authentication
Fast Identity Online (FIDO):

15 April 2023 Visa Confidential 106


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (45 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 123 Usage l 50 = Possession only. No user


2, Dataset ID 68 verification.
Tag: 83 l 51 = With user verification
Token Authenti­ (biometric)
cation Factor A l 52 = With user verification
Length: 1 (passcode/password)

Format: Binary l 60 = SE based token: cryptogram


generated from a SE device for a
Row 2 of 2 device-bound token was
provided, establishes possession
factor.
l 61 = Device bound token: device-
bound token (token reference)
was provided by token requestor
along with proof of device used
for binding token, establishes
possession factor.
In Europe, token user identifier may
be used to support dynamic linking
requirements of PSD2/RTS.

15 April 2023 Visa Confidential 107


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (46 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 123 Usage Not applicable Authentication Values are:


2, Dataset ID 68
l 00 = No authentication method
Tag 84 acquired
Token Authenti­ l 01 = Username/password
cation Factor B
l 02 = Passcode or password
Length: 1
Consumer Device Cardholder
Format: Binary Verification Method (CDCVM):
Row 1 of 2 l 10 = Passcode
l 11 = Password
l 12 = Pattern
l 13 = Biometric fingerprint
l 14 = Biometric facial recognition
l 15 = Biometric iris recognition
l 16 = Biometric voice recognition
l 17 = Behavioral biometric
One Time Passcode (OTP):
l 30 = Short message system
(SMS)
l 31 = Email
l 32 = Hardware token without
user verification
l 33 = Hardware token with user
verification
l 34 = Soft token
l 35 = Any other method
l 40 = Knowledge based authenti­
cation
l 41 = Out of band (OOB) authenti­
cation
l 42 = Local authentication
Fast Identity Online (FIDO):

15 April 2023 Visa Confidential 108


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (47 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 123 Usage l 50 = Possession only. No user


2, Dataset ID 68 verification.
Tag 84 l 51 = With user verification
Token Authenti­ (biometric)
cation Factor B l 52 = With user verification
Length: 1 (passcode/password)

Format: Binary l 60 = SE based token: cryptogram


generated from a SE device for a
Row 2 of 2 device-bound token was
provided, establishes possession
factor.
l 61 = Device bound token: device-
bound token (token reference)
was provided by token requestor
along with proof of device used
for binding token, establishes
possession factor.
In Europe, token user identifier may
be used to support dynamic linking
requirements of PSD2/RTS.

Field 123 Usage Not applicable Contains the payment amount


2, Dataset ID 68 made visible by the token
requestor to consumer at time of
Tag: 85
purchase.
Token Authenti­
Applicable for e-commerce
cation Amount
transactions (device and card-on-
Length: 3 file token types).
Format: Binary In Europe, token user identifier
may be used to support dynamic
linking requirements of PSD2/RTS.
This amount is seven right-most
digit of payable amount excluding
minor units, converted from
decimal to binary. Minor units
excluded specified by country
code in Field 49-Currency Code,
Transaction.

15 April 2023 Visa Confidential 109


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (48 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 125 Usage Not applicable This field is Supporting


2, Dataset ID 01 Information, Tag-Length-Value
(TLV).
Token Device
Testing and activation are required
Length: Variable;
to implement TLV Field 125 for the
1 byte, binary +
first time.
255 binary and
ANS, EBCIDIC; This field is defined with valid
maximum 256 values in the following tags:
bytes
l Tag 03: Device ID
l Tag 04: Device Number
l Tag 06: Device Location
l Tag 07: IP Address

Field 125 Usage Not applicable This tag contains the Device ID.
2, Dataset ID 01
Tag: 03
Device ID
Length: 48
Format: ANS

Field 125 Usage Not applicable This tag contains the full phone
2, Dataset ID 01 number or partial phone number
when available.
Tag: 04
Device Number
Length: 15
Format: N

Field 125 Usage Not applicable This tag contains the obfuscated
2, Dataset ID 01 geographic location of the device
or the coarse location of the
Tag: 06
device. Location is latitude/
Device Location longitude with 4 digits of precision,
Length: 25 for instance, +37.7799/-122.4290.
Precision is rounded off to a less
Format: ANS granular level, for instance,
+37/-122 or +37.78/-122.43.

15 April 2023 Visa Confidential 110


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (49 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 125 Usage Not applicable The value will be in the format: This tag contains the IP address of
2, Dataset ID 01 255.255.255.255. Each octet (255) the device at the time of the
may be 1–3 digits in length. provisioning request.
Tag: 07
IP Address
Length: 15
Format: ANS

Field 125 Usage Not applicable This field is Supporting


2, Dataset ID 02 Information, Tag-Length-Value
(TLV).
Wallet Provider
This tag contains the Wallet
Tag: 0A
Account E-mail Address.
Wallet Account
Testing and activation are required
E-mail Address
to implement TLV Field 125 for the
Length: 32 first time.
Format:
Hexadecimal

Field 126.8 Not applicable For 3DS and token transactions, the 3-D Secure TAVV, Version and
acquirer can: Authentication Action for payment
Transaction ID
tokens and token cryptograms
(XID) l Populate Field 126.8 with the
present in e-commerce POS
Length: 20 TAVV
authorization and full financial
bytes, fixed l Populate Field 126.9 with the messages, is used in conjunction
Format: Binary CAVV with Field 126.9 for 3-D Secure
(3DS) and non-3DS token
For transaction with Visa tokeni­
transactions.
zation only (acquirer not using 3DS),
the acquirer should : Testing and activation are required
to implement Field 126.8 for the
l Populate Field 126.8 with the
first time.
TAVV
There is no CAVV here.

Field 126.9 Not applicable For transactions with 3DS authenti­ This field may be present in an AFT.
cation & authorization only (not Refer to the Full Service POS
CAVV Data
including tokenization), the acquirer Technical Specifications for
Length: 20 should populate this field with the information about this field.
bytes, fixed CAVV.
Format: Binary

15 April 2023 Visa Confidential 111


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (50 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 127, Not applicable Field 127 is a requirement when


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

Field 127, Not applicable Contains the expiration date of the


Dataset ID 41 new PAN in Tag 01 or the updated
expiration date of the existing PAN.
Replacement
PAN Expiration Format = yymm.
Date
Length: 4
Format: N, BCD
Tag 02

Field 127, Not applicable l A (Account number change (the Indicates the account status.
Dataset ID 41 account number or account
Account Status number and expiration date are
being updated))
Length: 1
l C (Closed account advice)
Format: AN,
EBCDIC l E (Expiration date change)

Tag: 04 l Q (Contact cardholder advice (the


merchant should contact the
cardholder for additional
information on the account))

Field 127, Not applicable Valid values are: This field indicates if replacement
Dataset ID 41 occurred in the response message
l Y (Requesting for replacement
sent to the originating entity.
Request from PAN details)
Merchant for
l Y (Replacement occurred)
Updated
Account l N (No replacement)
Length: 1
Format: AN,
EBCDIC
Tag: 07

15 April 2023 Visa Confidential 112


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (51 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name

Field 127, Not applicable l VAU001 (Transaction did not Indicates the reason a transaction
Dataset ID 41, qualify for Real Time Visa Account did not qualify for account
Updater (VAU) because the information replacement.
Error Reason
Code transaction contains token)

Length: 6 l VAU002 (Real Time VAU is


supported only for Visa-branded
Tag: 09 PAN)
l VAU003 (Real Time VAU is not
supported for the network)
l VAU004 (Transaction is not
original purchase, bill payment,
account funding, or original
credit)
l VAU005 (Transaction contains
CVV2)
l VAU006 (Transaction is not a
qualifying recurring or installment
transaction type)
l VAU007 (Real Time VAU is not
supported for this MCC)
l VAU008 (Acquirer of processor is
not activated for Real Time VAU)
l VAU009 (Issuer does not support
Real Time VAU)
l VAU010 (Issuer or Visa blocked
the merchant)
l VAU011 (PPCS has a stop
payment order for this
transaction)
l VAU012 (Credentials in the
authorization request is the latest
VAU data)
l VAU013 (Expiry date in the
authorization request is later than
VAU data)
l VAU014 (PAN has been opted
out of VAU)
l VAU015 (Transaction is a face-to-
face transaction type)
l VAU016 (PAN has stop advice set
up)

15 April 2023 Visa Confidential 113


Visa Direct Account Funding Transaction (AFT) – Processing Guide
AFT Data Elements and Processing Rules

Table 13: AFT Key Data Elements (52 of 52)

V.I.P. BASE II (TC05) Field Value Notes/VisaNet Edits/


(0100/0200) Name Requirements
Field Name
Not applicable 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

Not Applicable Business Format Code Value = CR Code indicating the type of
(AI) business that is applicable to this
transaction.
Positions: 17–18
This field must contain CR (for
Length: 2
Business Application Data).
Format: AN

1 Effective April 2020, CEMEA is mandating support of AFT with Processing Code 10.
2 If the funds will be used for a high-brand risk transaction, use the applicable high-brand risk MCC.
3 If the funds are used for a high-brand risk transaction, use the applicable high-brand risk MCC.
4 The recipient’s name is not required but recommended in all regions.
5 Effective 23 April 2022, Visa will also require recipient account number or reference number to be included in all AFTs.

15 April 2023 Visa Confidential 114


Appendix B
Purpose of Payment –
Standardized Codes List

The Purpose of Payment code list is required to classify and report the nature and purpose of the
payment.
Note: This is a standardized list and not all codes may be applicable to an AFT. The acquirer must
submit the correct purpose of payment code for the recipient issuer's jurisdiction and restrict clients
to a predetermined list.
Important: An AFT is not intended for:
l payment of goods and services
l funding of a merchant account
l debt repayment

Table 14: Code List (1 of 4)

Code Code Description


ISACCT Account management

ISAIRB Air transport related business

ISALLW Transaction is the payment of allowance

ISANNI Settlement of annuity

15 April 2023 Visa Confidential 115


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Purpose of Payment – Standardized Codes List

Table 14: Code List (2 of 4)

Code Code Description


ISBENE Unemployment disability benefit

ISBEXP Business expenses

ISBONU Bonus payment

ISBUSB Bus transport related business

ISCASH Cash management transfer

ISCBTV Payment of cable TV bill

ISCCHD Government institute issued related to cash compen­


sation, helplessness, disability

ISCCRD Credit card payment

ISCDBL Payment of credit card bill

ISCHAR Payment for charity reasons

ISCOLL Collection payment

ISCOMC Commercial payment

ISCOMM Commission

ISCOMP Compensation relating to interest loss/value date


adjustment and can include fees

ISCPYR Payment of copyright

ISDCRD Related to a debit card payment

ISDEPT Payment of a deposit

ISDIVD Payment of dividend

ISEDUC Payment of study/tuition fees

ISELEC Payment of electricity bill

ISENRG Energies

ISFEES General fees

ISFERB Payment for ferry related business

ISFREX Foreign exchange

ISGASB Payment of gas bill

ISGFRP Compensation to unemployed persons during insolvency


procedures

ISGOVT Government payment

ISHLTI Health insurance

ISICCP Reimbursement of credit card payment

ISIDCP Reimbursement of debit card payment

ISINPC Payment of car insurance premium

15 April 2023 Visa Confidential 116


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Purpose of Payment – Standardized Codes List

Table 14: Code List (3 of 4)

Code Code Description


ISINSC Transaction is related to the payment of an insurance
claim

ISINSM Installment

ISINSU Insurance premium

ISINVS Payment of mutual funds, investment products and


shares

ISINTC Intra company payment

ISINTE Interest

ISINTX Income tax

ISINVS Investment

ISLBRI Labor insurance

ISLICF License fee

ISLIFI Life insurance

ISLOAN Loan

ISMDCS Medical services

ISMP2B Mobile P2B payment

ISMP2P Mobile P2P payment

ISMTUP Mobile top up

ISNOWS Not otherwise specified

ISOTHR Other

ISOTLC Transaction is related to a payment of other telecom


related bill

ISPAYR Payroll

ISPEFC Contribution to pension fund

ISPENS Pension payment

ISPHON Payment of telephone bill

ISPPTI Property insurance

ISRELG Transaction is for general rental/lease

ISRENT The payment of rent

ISRLWY Payment for railway transport related business

ISROYA Royalties

ISSALA Salary payment

ISSAVG Payment to savings/retirement account

ISSECU Securities

15 April 2023 Visa Confidential 117


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Purpose of Payment – Standardized Codes List

Table 14: Code List (4 of 4)

Code Code Description


ISSSBE Social security benefit

ISSTDY Study

ISSUBS Subscription

ISSUPP Supplier payment

ISTAXR Refund of a tax payment or obligation

ISTAXS Tax payment

ISTBIL Transaction is related to a payment of telecommuni­


cations related bill

ISTRAD Trade services operation

ISTREA Treasury payment

ISTRPT Payment for travel

ISUBIL Utility bill payment

ISVATX Value added tax payment

ISWHLD With holding

ISWTER Payment of water bill

15 April 2023 Visa Confidential 118


Appendix C
API Formats

ISO Fields – API Field Mapping


This section lists the ISO field and its corresponding API field name.
Acquirers, service providers, and merchants can use this table to interpret the API information in the
Visa Developer Center (VDC).

V.I.P. (0100/0200) Field Name API Field Name API Type

Field 2 – Primary Account Number senderPrimaryAccountNumber l AFT Request


Length: Variable l AFT Reversal Request
Format: 1-byte binary and up to 19
N, 4-bit BCD (unsigned packed);
maximum 11 bytes

Field 3 – Processing Code accountType l AFT Request


Length: 3 l AFT Reversal Request
Format: 6 BCD (unsigned packed); 3
bytes

15 April 2023 Visa Confidential 119


Visa Direct Account Funding Transaction (AFT) – Processing Guide
API Formats

V.I.P. (0100/0200) Field Name API Field Name API Type

Field 4 – Amount, Transaction amount l AFT Request


Length: 6 l AFT Reversal Request
Format: 12 BCD

Filed 7 – Transmission Date and Time transmissionDateTime l AFT Response


Fixed length 10 N, 4-bit BCD l AFT Reversal Response
(unsigned packed); 5 bytes
Format: MMDDhhmmss

Field 9 – Settlement Flags settlementFlags AFT Response


Contains various settlement related
flags (currently all in VIP Header Field
9)

Field 9 – Settlement Flags givPreviouslyUpdatedFlag AFT Response

Field 9 – Settlement Flags settlementResponsibilityFlag AFT Response

Field 9 – Settlement Flags settlementServiceFlag AFT Response

Field 11 – System Trace Audit systemsTraceAuditNumber l AFT Request


Number
l AFT Reversal Request
Fixed length 6 N, 4-bit BCD (unsigned
packed); 3 bytes

Field 12 – Time, Local Transaction localTransactionDateTime l AFT Request


Fixed length 6 N, 4-bit BCD (unsigned l AFT Reversal Request
packed); 3 bytes
Format: hhmmss

Field 13 – Date, Local Transaction localTransactionDateTime l AFT Request


Fixed length 4 N, 4-bit BCD (unsigned l AFT Reversal Request
packed); 2 bytes
Format: mmdd

Field 14 – Date, Expiration senderCardExpiryDate l AFT Request


Fixed length 4 N, 4-bit BCD (unsigned l AFT Reversal Request
packed); 2 bytes
Format: yymm

Field 15 – Settlement Date settlementDate l AFT Request


Fixed length: 4 N, 4-bit BCD l AFT Reversal Response
(unsigned packed); 2 bytes
Format: mmdd

Field 18 – Merchant Type merchantCategoryCode AFT Request


Fixed length: 4 N, 4-bit BCD
(unsigned packed); 2 bytes

15 April 2023 Visa Confidential 120


Visa Direct Account Funding Transaction (AFT) – Processing Guide
API Formats

V.I.P. (0100/0200) Field Name API Field Name API Type

Field 19 – Acquiring Institution acquirerCountryCode l AFT Request


Country Code
l AFT Reversal Request
Fixed length: 3 N, 4-bit BCD
(unsigned packed); 2 bytes

Field 21 – Transaction Identifier transactionIdentifier l AFT Reversal Request


l AFT Reversal Response

Field 22 – POS Entry Mode Code <pointOfServiceData>panEntryMode l AFT Request


Fixed length 4 N, 4-bit BCD (unsigned l AFT Reversal Request
packed); 2 bytes

Field 25 – POS Condition Code <pointOfServiceData>posCondi­ l AFT Request


tionCode
Fixed length 2 N, 4-bit BCD (unsigned l AFT Reversal Request
packed); 1 byte

Field 27 – Point-of-Service Capability <pointOfServiceCapability> l AFT Request


l AFT Reversal Request

Field 28 – AFT Service Fee surcharge l AFT Request


Fixed length 1 AN, EBCDIC + 8 N, l AFT Reversal Request
EBCDIC total: 9 bytes

Field 32 – Acquiring Institution acquiringBin l AFT Request


Identification Code
l AFT Reversal Request
Variable length 1 byte, binary + 11 N,
4-bit BCD (unsigned packed);
maximum 7 bytes

Field 35 – Track 2 Data magneticStripeData.track2Data AFT Request


Variable length 1 byte, binary + 37 N,
4-bit BCD (unsigned packed);
maximum 20 bytes

Field 37 – Retrieval Reference retrievalReferenceNumber l AFT Request


Number
l AFT Reversal Response
Fixed length 12 AN [content limited
to numerics], EBCDIC; 12 bytes
Format: ydddnnnnnnnn

Field 38 – Authorization Identification approvalCode l AFT Response


Response
l AFT Reversal Response
Fixed length 6 AN, EBCDIC; 6 bytes

Field 39 – Action Code actionCode l AFT Response


Fixed length 2 AN, EBCDIC; 2 bytes l AFT Reversal Response

15 April 2023 Visa Confidential 121


Visa Direct Account Funding Transaction (AFT) – Processing Guide
API Formats

V.I.P. (0100/0200) Field Name API Field Name API Type

Field 41 – Card Acceptor Terminal cardAcceptor.terminalId AFT Request


Identification
fixed length 8 ANS, EBCDIC; 8 bytes

Field 42 – Card Acceptor Identifi­ cardAcceptor.idCode AFT Request


cation Code
Fixed length 15 ANS, EBCDIC; 15
bytes

Field 43 – Card Acceptor Name cardAcceptor.name l AFT Response


Fixed length 40 ANS, EBCDIC; 40 l AFT Reversal Request
bytes

Field 43 – Card Acceptor City cardAcceptor.city l AFT Response


Fixed length 40 ANS, EBCDIC; 40 l AFT Reversal Request
bytes

Field 43 – Card Acceptor Country cardAcceptor.address.country l AFT Response


Code
l AFT Reversal Request
Fixed length 40 ANS, EBCDIC; 40
bytes

Field 44.1 – Response Source/Reason responseCode AFT Response


Code
Fixed length 1 ANS, EBCDIC; 1 byte

Field 44.13 – CAVV Result Code cavvResultCode AFT Response


Fixed length 1 ANS, EBCDIC; 1 byte

Field 45 – Track 1 Data magneticStripeData.track1Data AFT Request


Variable length 1 byte, binary + 76
ANS, EBCDIC; maximum 77 bytes

Field 48 – Unformatted Text in FinancialAccountFundingRequestFro­ l AFT Request


Authorization/Reversal Messages mAcquirer.unformattedText
l AFT Response
Variable length 1 byte, binary + 255 FinancialAccountFundingResponse­
ANS, EBCDIC; maximum 256 bytes ToAcquirer.unformattedText

Field 49 – Currency Code, Transaction transactionCurrencyCode AFT Request


Fixed length 3 N, 4-bit BCD (unsigned
packed); 2 bytes

Field 52 – Personal Identification pinDataBlock AFT Request


Number (PIN) Data Block
Fixed length 64 N, bit string; 8 bytes

15 April 2023 Visa Confidential 122


Visa Direct Account Funding Transaction (AFT) – Processing Guide
API Formats

V.I.P. (0100/0200) Field Name API Field Name API Type


Field 52 & 53 pinData AFT Request
Personal Identification Number (PIN)
Data
Fixed length 64 N, bit string; 8 bytes

Field 53 – Security-Related Control securityRelatedControlInfo AFT Request


Information
Fixed length 16 N, 4-bit BCD
(unsigned packed); 8 bytes

Field 53.1 – Security-Related Control securityRelatedControlInfo.security­ AFT Request


Information (Security format code Format
pos 1-2)
Fixed length 16 N, 4-bit BCD
(unsigned packed); 8 bytes

Field 53.2 – Security-Related Control securityRelatedCon­ AFT Request


Information (Algorithm Identifier pos trolInfo.algorithmID
3-4)
Fixed length 16 N, 4-bit BCD
(unsigned packed); 8 bytes

Field 53.3 – Personal Identification pinBlockFormatCode AFT Request


Number (PIN) Block format code pos
5-6
Fixed length 16 N, 4-bit BCD
(unsigned packed); 8 bytes

Field 53.4 – Security-Related Control securityRelatedCon­ AFT Request


Information Zone key index pos 7-8) trolInfo.zoneKeyIndex
Fixed length 16 N, 4-bit BCD
(unsigned packed); 8 bytes

Field 54 – AFT Foreign Exchange foreignExchangeFeeTransaction AFT Reversal Request


Markup Fee
Length 20
Format: 1 byte binary + 20 ANS

Field 56 – Customer Reference customerReference AFT Request


Number
Dataset ID 03
Tag 9F1F
Format: N

15 April 2023 Visa Confidential 123


Visa Direct Account Funding Transaction (AFT) – Processing Guide
API Formats

V.I.P. (0100/0200) Field Name API Field Name API Type

Field 56 – Identification Type Code recipientAdditionalData.senderIdenti­ AFT Request


ficationList[].idType
Dataset ID 03
Tag 9F20
Length: 4
Format: A

Field 56 – Identification Type Code senderAdditionalData.senderIdentifi­ AFT Request


cationList[].idType
Dataset ID 03
Tag 9F20
Length: 4
Format: A

Field 56 – Identification Value recipientAdditionalData.recipientI­ AFT Request


dentificationList[].idNumber
Dataset ID 03
Tag 9F22
Length: 35
Format: ANS

Field 56 – Identification Value senderAdditionalData.senderIdentifi­ AFT Request


cationList[].idNumber
Dataset ID 03
Tag 9F22
Length: 35
Format: ANS

Field 56 – Identification Issuing recipientAdditionalData.recipientI­ AFT Request


Country dentificationList[].idIssueCountry
Dataset ID 03
Tag 9F24
Length: 3
Format: N

Field 56 – Identification Issuing senderAdditionalData.senderIdentifi­ AFT Request


Country cationList[].idIssueCountry
Dataset ID 03
Tag 9F24
Length: 3
Format: N

15 April 2023 Visa Confidential 124


Visa Direct Account Funding Transaction (AFT) – Processing Guide
API Formats

V.I.P. (0100/0200) Field Name API Field Name API Type

Field 56 – Account Owner Name, senderFirstName AFT Request


Given
Usage 2, Dataset ID 05
Tag 83
Length: 35
Format: AN

Field 56 – Account Owner Name, recipientFirstName AFT Request


Given
Usage 2, Dataset ID 05
Tag 83
Length: 35
Format: AN

Field 56 – Account Owner Name, recipientMiddleName AFT Request


Middle
Usage 2, Dataset ID 05
Tag 84
Length: 35
Format: AN

Field 56 – Account Owner Name, senderMiddleName AFT Request


Middle
Usage 2, Dataset ID 05
Tag 84
Length: 35
Format: AN

Field 56 – Account Owner Name, Last recipientLastName AFT Request


Usage 2, Dataset ID 05
Tag 85
Length: 35
Format: AN

Field 56 – Account Owner Name, Last senderLastName AFT Request


Usage 2, Dataset ID 05
Tag 85
Length: 35
Format: AN

15 April 2023 Visa Confidential 125


Visa Direct Account Funding Transaction (AFT) – Processing Guide
API Formats

V.I.P. (0100/0200) Field Name API Field Name API Type

Field 56 – Account Owner Address recipientAddressLine1 AFT Request


Line 1
Usage 2, Dataset ID 05
Tag 86
Length: 99
Format: ANS

Field 56 – Account Owner Address recipientAddressLine2 AFT Request


Line 2
Usage 2, Dataset ID 05
Tag 87
Length: 99
Format: ANS

Field 56 – Account Owner Street recipientStreetName AFT Request


Name
Usage 2, Dataset ID 05
Tag 88
Length: 99
Format: ANS

Field 56 – Account Owner Building recipientBuildingNumber AFT Request


Number
Usage 2, Dataset ID 05
Tag 89
Length: 16
Format: ANS

Field 56 – Account Owner Postal recipientPostalCode AFT Request


Code
Usage 2, Dataset ID 05
Tag 8A
Length: 16
Format: ANS

Field 56 – Account Owner City Name recipientCity AFT Request


Usage 2, Dataset ID 05
Tag 8B
Length: 25
Format: ANS

15 April 2023 Visa Confidential 126


Visa Direct Account Funding Transaction (AFT) – Processing Guide
API Formats

V.I.P. (0100/0200) Field Name API Field Name API Type

Field 56 – Account Owner Country recipientSubDivisionMinorCode AFT Request


Subdivision Code, Minor
Usage 2, Dataset ID 05
Tag 8C
Length: 16
Format: ANS

Field 56 – Account Owner Country recipientState AFT Request


Subdivision Code, Major
Usage 2, Dataset ID 05
Tag 8D
Length: 3
Format: ANS

Field 56 – Account Owner Country recipientCountryCode AFT Request


Code
Usage 2, Dataset ID 05
Tag 8E
Length: 3
Format: A

Field 60.1 – Point-of-Service terminal posTerminalType l AFT Request


type
l AFT Reversal Request
Variable length 1 byte, binary + 12 N,
4-bit BCD (unsigned packed), 7 bytes
total

Field 60.2 – Terminal Entry Capability posTerminalEntryCapability l AFT Request


pos. 1 - 2 l AFT Response

Field 60.4/63.6 – Special Condition specialConditionIndicatorMerchant AFT Request


Indicator, Merchant Transaction
Length: 1
Format: 2N, 4-bit BCD

Field 60.8/63.6 – Mail/Phone/ pointOfServiceData.motoECIIndicator l AFT Request


Electronic Commerce Payment
l AFT Reversal Request
Indicator; Point-of-service indicator;
Position 4
Length: 1
Format: 2N, 4-bit BCD

15 April 2023 Visa Confidential 127


Visa Direct Account Funding Transaction (AFT) – Processing Guide
API Formats

V.I.P. (0100/0200) Field Name API Field Name API Type

Field 60.10 pointOfServiceCapability.acceptsPar­ AFT Request


tialAuthorizations
Additional Authorization Indicators
Partial Authorization
Position: 12
Length: 1
Format: 1 N

Field 62.1 – Authorizations Character­ cpsAuthorizationCharacteristicsIn­ AFT Request


istics Indicator dicator
Fixed length
Format: 1 AN, EBCIDIC; 1 byte

Field 62.2 – Merchant Verification <merchantVerificationValue> AFT Request


Value (MVV)
Length: 10
Format: 4-bit BCD, 5 bytes

Field 62.2 – Merchant Verification <merchantVerificationValue> l AFT Request


Value (MVV) mvvAcquirerAssigned
l AFT Reversal Request
Length: 10
Format: Numeric

Field 62.2 - Merchant Verification <merchantVerificationValue> l AFT Request


Value (MVV) mvvVisaAssigned
l AFT Reversal Request
Length: 10
Format: Numeric

Field 62.2 - Merchant Verification merchantVerificationValue l AFT Response


Value (MVV)
l AFT Reversal Request
Length: 10
l AFT Reversal Response
Format: 4-bit BCD, 5 bytes

Field 62.2 – Transaction Identifier transactionIdentifier AFT Response


Length: 8
Format: 15 BCD

Field 63.1 – Gateway Merchant Data merchantPseudoAbaNumber l AFT Request


Fixed length l AFT Reversal Request
13 ANS, EBCDIC, 13 bytes

Field 63.1 – Network Identification networkId l AFT Response


Code
l AFT Reversal Request
4 N, 4-bit BCD (unsigned packed); 2
bytes

15 April 2023 Visa Confidential 128


Visa Direct Account Funding Transaction (AFT) – Processing Guide
API Formats

V.I.P. (0100/0200) Field Name API Field Name API Type

Field 63.12 – Sharing Group Code sharingGroupCode l AFT Request


Fixed length l AFT Reversal Request
30 bytes 30 ANS, EBCDIC

Field 63.19 – Fee Program Indicator feeProgramIndicator l AFT Request


Length: 3 l AFT Reversal Request
Format: 1 ANS; EBCDIC l AFT Reversal Response

Field 63.6 – Mail/Phone/ Electronic motoECIIndicator AFT Request


Commerce and Payment Indicator
(SMS Only)
Length: 1
Format: 1 ANS; EBCDIC

Field 90 – Original Data Elements originalDataElements AFT Reversal Request


Fixed length
42 N, 4-bit BCD (unsigned packed);
21 bytes

Field 104 – Sponsored Merchant ID paymentFacilitator.subMerchantId AFT Request


Usage 2, Dataset ID 56
Tag 02
Length: Variable, up to 15 bytes
Format: AN

Field 104 – Acceptor Legal Business legalBusinessName AFT Request


Name
Usage 2 Dataset ID 56
Tag 81
Length: Variable up to 25 bytes
Format: ANS

Field 104 – Payment Facilitator Name paymentFacilitator.name AFT Request


Usage 2 Dataset ID 56
Tag 82
Length: Variable, up to 25 bytes
Format: ANS

15 April 2023 Visa Confidential 129


Visa Direct Account Funding Transaction (AFT) – Processing Guide
API Formats

V.I.P. (0100/0200) Field Name API Field Name API Type

Field 104 – Business Application businessApplicationId AFT Request


Identifier (BAI)
Usage 2 Dataset ID 57
Tag 01
Length: 2
Format: AN

Field 104 – Purpose of Payment purposeOfPayment AFT Request


Usage 2, Dataset ID 57
Tag: 82
Length: 12
Format: AN

Field 104 – Visa Risk Assessment Data merchantRiskScore l AFT Response


(Risk Score); Merchant Risk Score
l AFT Reversal Response
Usage 2 Dataset ID 5B
Tag 01
Length: 2
Format: N

Field 104 – Visa Risk Assessment Data merchantRiskConditionCode l AFT Response


(Risk Condition Code); Merchant Risk
l AFT Reversal Response
Condition Code
Usage 2 Dataset ID 5B
Tag 02
Length: 2
Format: N

Field 104 – Sanctions Screening ComplianceResponse.data.score AFT Request


Scoring Results Code
Usage 2, Dataset ID 5B
Tag: 84
Length: 3
Format: N

Field 104 – Sender Account Number senderAccountNumber AFT Request


Usage 2, Dataset Value Hex 5F
Tag: 02
Length: 34
Format: AN

15 April 2023 Visa Confidential 130


Visa Direct Account Funding Transaction (AFT) – Processing Guide
API Formats

V.I.P. (0100/0200) Field Name API Field Name API Type

Field 104 – Sender Name senderName AFT Request


Usage 2, Dataset Value Hex 5F
Tag: 03
Length: 30
Format: AN, EBCDIC

Field 104 – Sender Address/Sender senderAddress AFT Request


Data, Address
Usage 2, Dataset Value Hex 5F
Tag: 04
Length: 35
Format: AN

Field 104 – Sender City senderCity AFT Request


Usage 2, Dataset Value Hex 5F
Tag: 05
Length: 25
Format: AN

Field 104 – Sender State/Province senderStateCode AFT Request


Usage 2, Dataset Value Hex 5F
Tag: 06
Length: 2
Format: AN

Field 104 – Sender Country senderCountry AFT Request


Usage 2, Dataset Value Hex 5F
Tag: 07
Length: 3
Format: AN

Field 104 – Sender Postal Code senderPostalCode l AFT Request


Usage 2, Dataset ID 5F l AFT Reversal Request
Tag: 10
Length: 5 - 10
Format: AN

15 April 2023 Visa Confidential 131


Visa Direct Account Funding Transaction (AFT) – Processing Guide
API Formats

V.I.P. (0100/0200) Field Name API Field Name API Type

Field 104 – Recipient Name recipientName l AFT Request


Usage 2, Dataset Value Hex 5F l AFT Reversal Request
Tag: 0A
Length: 30
Format: AN, EBCDIC

Field 104 – Merchant VAT recipientIdentificationNumber­ AFT Request


Registration/Single Business Business
AFT Response
Reference Number
Usage 2, Dataset ID 63
Tag: 05
Length: 20
Format: AN

Field 104 – Customer VAT recipientIdentificationNumberIndi­ AFT Request


Registration Number vidual
AFT Response
Usage 2, Dataset ID 63
Tag: 06
Length: 13
Format: AN

Field 114 freeFormDescriptionData AFT Request


Free-form Description Data
Dataset ID 70
Length: 300 bytes

Field 119 – Settlement Service Data nationalReimbursementFee AFT Request


Usage 5
Format: ANS, EBCDIC

Filed 123 – Address Verification Data addressVerificationData AFT Request


Length: 1 byte, binary +
Fixed Format: 29 ANS, EBCDIC;
maximum 30 bytes

Field 126.1 – Card verification data cardCvv2Value AFT Request

Field 126.9 – CAVV Data cavv AFT Request


Length: 20 bytes, fixed
Format: Binary

15 April 2023 Visa Confidential 132


Visa Direct Account Funding Transaction (AFT) – Processing Guide
API Formats

V.I.P. (0100/0200) Field Name API Field Name API Type

Field 127 – Replacement PAN replacementDateExpiration AFT Response


Expiration Date
Dataset ID 41
Tag 02
Length: 4
Format: N, BCD

Field 127 – Account Status vauAccntStatus AFT Response


Dataset ID 41
Tag: 04
Length: 1
Format: AN, EBCDIC

Field 127 - Error/Reason Code vauErrorReasonCode AFT Response


Dataset ID 41
Tag: 09
Length: 6

Field 127 - Request from Merchant vauFlag AFT Response


for Updated Account
Dataset ID 41
Tag: 07
Format: EBCDIC

Field 127 - Replacement PAN vauRTAuthReplacementData AFT Response


Dataset ID 41
Tag: 01
Format: BCD

15 April 2023 Visa Confidential 133


Appendix D
Transaction Flows

This appendix provides AFT-related transaction flows as outlined in the table.


The actor in the diagram enabled as Originating Entity could be a merchant, acquirer, or service
provider.
Note: These flows are for informational purposes only; check the Full Service POS Online
Messages Technical Specifications on Visa Online for the most recent requirements.

15 April 2023 Visa Confidential 134


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Transaction Flows

AFT Flow – SMS Originating Entity to


SMS Issuer (Approval/Decline)

1. Originating entity submits 0200 message to VisaNet.


2. VisaNet forwards the 0200 message to issuer.
3. Issuer receives 0200 message, processes, and responds with an approval or decline.
4. The issuer creates the 0210 response and sends it back to VisaNet.
5. VisaNet sends the 0210 message to the originating entity.
6. The originating entity receives the 0210 message.

15 April 2023 Visa Confidential 135


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Transaction Flows

AFT Flow – SMS Originating Entity to


Dual Message/BASE II Issuer
(Approval/Decline)

1. Originating entity submits 0200 message to VisaNet.


2. VisaNet receives the 0200 message from originating entity.
3. VisaNet converts 0200 message into a 0100 message and sends it to the issuer.
4. Issuer receives 0100 message, processes, and responds with an approval or decline.
5. The issuer sends 0110 response to VisaNet.
6. VisaNet receives 0110 response and converts it to a 0210 response and forwards it to the
originating entity.
7. The originating entity receives 0210 response and completes the transaction.

15 April 2023 Visa Confidential 136


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Transaction Flows

8. VisaNet creates a TC05 message and sends it to the issuer.


9. The issuer receives the TC05.
Note: If the transaction is declined, steps 8 and 9 are not executed.

15 April 2023 Visa Confidential 137


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Transaction Flows

AFT Flow – Dual Message Originating


Entity to SMS Issuer (Approval/
Decline)

1. Originating entity submits 0100 message to VisaNet.


2. VisaNet receives the 0100 message from originating entity.
3. VisaNet sends the 0100 message to the issuer.
4. Issuer receives 0100 message, processes, and responds with an approval or decline.
5. The issuer sends 0110 response to VisaNet.
6. VisaNet receives 0110 response and forwards it to the originating entity.
7. The originating entity creates a TC05 and sends it to VisaNet.
8. VisaNet sends the 0220 deferral advice to the issuer.
Note: If the transaction is declined, steps 7 and 8 are not executed.

15 April 2023 Visa Confidential 138


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Transaction Flows

AFT Flow – Dual Message Originating


Entity to Dual Message/BASE II Issuer
(Approval/Decline)

1. Originating entity submits 0100 message to VisaNet.


2. VisaNet receives the 0100 message from originating entity.
3. VisaNet sends the 0100 to the issuer, and the issuer responds with an approval or decline.
4. The issuer sends 0110 response to VisaNet.
5. VisaNet receives 0110 response and forwards it to the originating entity.
6. The originating entity receives 0110 response and completes the transaction.
7. The originating entity creates a TC05 message and sends it to VisaNet.
8. VisaNet sends the TC05 to the issuer.
Note: If the transaction is declined, steps 7 and 8 are not executed.

15 April 2023 Visa Confidential 139


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Transaction Flows

Credit Adjustment: SMS Originating


Entity to SMS Recipient Issuer

1. Originating entity submits 0220 advice message to Visa to request refund of money to
sender's account.
2. Visa sends 0220 auth message to recipient issuer.
3. Recipient issuer uses the 0220 message to restore balance to the cardholder’s account.
4. Recipient issuer responds with 0230.
5. Visa receives the 0230.
6. Visa sends the 0230 confirmation back to originating entity to confirm success of submission.

15 April 2023 Visa Confidential 140


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Transaction Flows

Credit Adjustment: SMS Originating


Entity to Dual Message/BASE II
Recipient Issuer

1. Originating entity submits 0220 advice message to Visa to request refund of money to
sender's account.
2. Visa receives the 0220 advice message.
3. Visa creates 0230 STIP advice and returns to originating entity to confirm.
4. Visa creates TC25 TCQ01 and sends to recipient issuer for processing.
5. The recipient issuer receives the TC25 TCQ01 and restores the balance to the cardholder.

15 April 2023 Visa Confidential 141


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Transaction Flows

Credit Adjustment: Dual Message


Originating Entity to SMS Recipient
Issuer

1. Originating entity raises TC25 TCQ 01 to Visa to request refund of money to senders account.
2. Visa receives the TC25 TCQ01 incoming files.
3. Visa creates 0220 advice and forwards to recipient issuer.
4. Recipient issuer receives 0220 advice and creates 0230 message.
5. Recipient issuer creates 0230 response and sends to Visa.
6. Visa receives the 0230 response confirming receipt and processing of 0230 advice.

15 April 2023 Visa Confidential 142


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Transaction Flows

Credit Adjustment: Dual Message


Originating Entity to Dual Message/
BASE II Recipient Issuer

1. Originating entity submits TC025 TCQ01 outgoing to Visa to request refund of money to
sender’s account.
2. Visa receives the TC25 TCQ01 and forwards to the recipient issuer for processing.
3. Recipient issuer processes the TC25 TCQ 01 and restores balance to cardholder’s account.

15 April 2023 Visa Confidential 143


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Transaction Flows

Issuer Response Delay – SMS


Originating Entity to SMS Issuer
(Results in Decline)

1. Originating entity submits 0200 message to VisaNet.


2. VisaNet forwards the 0200 message to issuer.
3. Issuer receives 0200 message, processes, and approves it.
4. The issuer creates the 0210 response and sends it back to VisaNet.
5. VisaNet receives the 0210 response from the issuer but the response took too long. VisaNet
sends the issuer a timeout advice and sends the issuer a reject.
6. The issuer receives the 0220 advice and reject message.
7. VisaNet sends a 0210 response to the originating entity with a response code (RC) value that
indicates that the recipient issuer is unavailable (response code 91).
8. The originating entity receives 0210 response and is notified that the transaction cannot be
successfully completed (Declined).

15 April 2023 Visa Confidential 144


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Transaction Flows

Issuer Response Delay – SMS


Originating Entity to Dual Message/
BASE II Issuer (Results in Decline)

1. Originating entity submits 0200 message to VisaNet.


2. VisaNet receives the 0200 message from originating entity.
3. VisaNet converts 0200 message into a 0100 message and sends it to the issuer.
4. Issuer receives 0100 message, processes, and approves it.
5. The issuer creates a 0110 response and sends to VisaNet.
6. VisaNet receives a 0110 response, but the response took too long.
7. VisaNet sends the issuer a 0120 timeout advice indicating that the response was received
outside of the response window.

15 April 2023 Visa Confidential 145


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Transaction Flows

8. Issuer receives the advice.


9. VisaNet creates a 0210 response, includes a response code indicating that the issuer is
unavailable (response code 91) and forwards it to the originating entity. The originating
entity receives 0210 response and is notified that the transaction cannot be successfully
completed (Declined).

15 April 2023 Visa Confidential 146


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Transaction Flows

Issuer Response Delay – Dual Message


Originating Entity to SMS Issuer
(Results in Decline)

1. Originating entity submits 0100 message to VisaNet.


2. VisaNet forwards the 0100 message to issuer.
3. issuer receives 0100 message, processes, and approves it.
4. The issuer creates the 0110 response and sends it back to VisaNet.
5. VisaNet receives the 0110 response from the issuer but the response took too long. VisaNet
sends the issuer a timeout advice and sends the issuer a reject.
6. The issuer receives the 0220 advice and reject.
7. VisaNet sends a 0110 response to the originating entity with a response code (RC) value
indicating that the issuer is unavailable (response code 91).
8. The originating entity receives 0110 response and is notified that the transaction cannot be
successfully completed (Declined).

15 April 2023 Visa Confidential 147


Visa Direct Account Funding Transaction (AFT) – Processing Guide
Transaction Flows

Issuer Response Delay – Dual Message


Originating Entity to Dual Message/
BASE II Issuer (Results in Decline)

1. Originating entity submits 0100 message to VisaNet.


2. VisaNet forwards the 0100 message to issuer.
3. issuer receives 0100 message, processes, and approves it.
4. The issuer creates the 0110 response and sends it back to VisaNet.
5. VisaNet receives the 0110 response from the issuer, but the response took too long. VisaNet
sends the issuer a timeout advice and sends the issuer a reject.
6. The issuer receives the 0120 advice and reject message.
7. VisaNet sends the 0110 response to the originating entity with a response code (RC) value
that indicates that the issuer is unavailable (response code 91).
8. The originating entity receives 0110 response and is notified that the transaction cannot be
successfully completed (Declined).

15 April 2023 Visa Confidential 148


Appendix E
BAI Acronyms and Glossary

This appendix contains a list of BAI acronyms.

Business Application Identifier (BAI)


Acronyms
This table lists acronyms related to the Business Application Identifier.

Table 15: Business Application Identifier (BAI) Acronyms (Permitted BAIs for AFTs in Bold)
(1 of 2)

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)

15 April 2023 Visa Confidential 149


Visa Direct Account Funding Transaction (AFT) – Processing Guide
BAI Acronyms and Glossary

Table 15: Business Application Identifier (BAI) Acronyms (Permitted BAIs for AFTs in Bold)
(2 of 2)

Acronyms Meaning
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).

15 April 2023 Visa Confidential 150


Glossary

3-D Secure (3DS) 3-D Secure is the name of a security protocol used for online credit and debit
card transactions. The name refers to the three domains governed by the
protocol: the merchant/acquirer domain, the issuer domain, and the
interoperability domain. The interoperability domain refers to the underlying
infrastructure that supports the payment card or scheme.

Access Channel A channel, such as an ATM or a mobile app, provided by an originating entity to
offer AFT program services to its customers.

Account Funding Transaction A Transaction where funds are pulled from a Visa account and are subsequently
(AFT) 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.

An AFT is not intended for:

l payment of goods and services


l funding of a merchant account
l debt repayment

Account Name Inquiry (ANI) Account Name Inquiry (ANI) is a functionality offered by Visa that enables an
account cardholder’s name to be checked against the name held by their issuing
bank. The check is carried out by Visa or the issuing bank in advance of a
transaction at the time of customer onboarding, just before a transaction,
periodically, or on an ad hoc basis.

Verifying the name provided by a cardholder can help reduce exposure to fraud
and scams in many types of payment flows, such as Card-Not-Present
transactions, but in particular in push and pull transactions (OCTs/AFTs).

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.

15 April 2023 Visa Confidential 151


Visa Direct Account Funding Transaction (AFT) – Processing Guide

Account Verification A message sent by an acquirer to the issuer, using a currency unit of zero, for
confirmation that a transaction can be completed using the Card.

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

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

Agent See Third-Party Agent.

Application Programming See Visa Direct Application Programming Interfaces (APIs).


Interface (API)

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.

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:

l Two separate accounts are involved. One account is used to make the
purchase, and the other automatically funds or reimburses that account.
l 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:

l The funding or reimbursement amount exactly matches the amount of the


purchase.
l 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:

l An Unscheduled Credential-on-File transaction for a fixed amount to reload


the account.
l The funding of a card that accesses funds on deposit at an organization other
than that of the issuer of the card (“decoupled debit”).

Business Application Identifier A data element in the AFT message that identifies the business application for
(BAI) which funds are being pulled from a Visa account. Values are:

l AA (account-to-account Money Transfer)


l BI (Financial institution–offered P2P Money Transfer)
l FT (Funds Transfer)
l MP (Merchant Payment for Scan to Pay programs only)
l PP (person-to-person Money Transfer)
l TU (prepaid card top-up)
l WT (adding value to a Staged Digital Wallet)

15 April 2023 Visa Confidential 152


Visa Direct Account Funding Transaction (AFT) – Processing Guide

Card-on-File (COF) This is most applicable to merchants who store user credentials, including the
PAN.

Cardholder Account Verification The Cardholder Authentication Verification Value (CAVV) is a cryptographic value
Value (CAVV) the issuer or V.I.P. generates and sends to the merchant during the authentication
process in a Visa Secure transaction.

Card Verification Method (CVM) Instructions encoded within a chip that define how the authenticity of a
cardholder's identity is to be verified.

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 Authentication DAF builds upon Visa Secure for authentication and Visa Token Service for
Framework (DAF) network tokenization. This framework is designed to elevate the performance of
merchants’ for Card Not Present transactions. Merchants and token requestors
that meet the DAF criteria (as set by Visa) will be allocated ECI value of 05 on
qualified authenticated transactions and will receive fraud dispute protection (as
per Visa rules) on those transactions.

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.

Electronic Commerce Indicator Numeric code specifying the type of mail order, phone order, or electronic
(ECI) commerce transaction.

E-Commerce (ECOM) A platform that allows sales and purchases of goods and services over an
electronic network – typically the internet.

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 A P2P Money Transfer offered by a financial institution through their own mobile
P2P Money Transfer or online banking application.

Foreign Exchange Rate API An API that allows the originating entity to look up the current day’s foreign
exchange rate using Visa rates and, using this rate, to convert the amount in the
originating entity’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.

15 April 2023 Visa Confidential 153


Visa Direct Account Funding Transaction (AFT) – Processing Guide

Host Card Emulation (HCE) HCE enables mobile applications running on supported operating systems with
the ability to offer payment card and access card solutions independently of third
parties while leveraging cryptographic processes traditionally used by hardware-
based secure elements without the need for a physical secure element.

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 an AFT four-party model, 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 their Visa account to a different,
non-merchant account.

Non-Merchant Account A financial account that is eligible to receive a funds transfer initiated by an AFT.

Original Credit Transaction A VisaNet transaction that can be used to send funds to an eligible Visa account.
(OCT) 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, merchant and/or
originating entity as applicable. Formerly: An entity (a Visa acquirer or a sponsored
third-party agent) that generates AFTs as a service to its customers.

Primary Account Number (PAN) The 16 to 19-digit number assigned to the payment account. Also known as the
Card Number.

15 April 2023 Visa Confidential 154


Visa Direct Account Funding Transaction (AFT) – Processing Guide

Payment Account Attributes An API that allows the merchant, service provider or acquirer to obtain
Inquiry API 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 An API that allows the merchant, service provider or acquirer to perform CVV2
(PAV) API 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 (U.S. region only) Allows originating entities in the U.S. to send AFTs to Visa for
(PPGS) routing to multiple U.S. debit networks.

Real Time Visa Account Updater Visa Account Updater (VAU) is a service that facilitates exchanging updated
(VAU) 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.

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.

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.

15 April 2023 Visa Confidential 155


Visa Direct Account Funding Transaction (AFT) – Processing Guide

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:

l send to other wallet users


l to make payments at multiple merchants under the operator’s proprietary
brand mark
l 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.

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.

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.

Token Authentication E-commerce token transactions require the use of a token authentication
Verification Value (TAVV) verification value (TAVV) with the token as part of the capabilities provided by the
Visa Token Service.

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; for example, payment facilitators, load
partners, etc.

Token Substitute values that replace the cardholder primary account number in
payment transactions during transaction processing.

Token Requestor (TR) A token requestor - token service provider is a third-party, Visa-compliant
business entity that provides products and services to participating token
requestors under and subject to the Visa Digital Enablement Program Token
Service Provider Program. Token requestor-token service providers are directly
connected to the Visa Token Service and enable token requestors to develop
consumer digital payment solutions powered by the Visa Token Service. The
token requestor-token service provider will be the integration partner facilitating
the provisioning, cryptogram request, and lifecycle management of Visa payment
tokens to the token requestor.

Top-Up (TU) See prepaid load.

15 April 2023 Visa Confidential 156


Visa Direct Account Funding Transaction (AFT) – Processing Guide

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 Developer Center 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 Direct The Visa product platform that provides funds transfer capabilities using AFTs and
OCTs.

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

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.

VisaNet Integrated Payment The online component of VisaNet that provides routing and processing of
(V.I.P.) System authorizations and financial messages.

Visa Payment Token A Payment Token is an “alternate identifier” that can be used in place of a PAN to
initiate a payment transaction.

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

Visa Token Service The Visa Token Service (VTS) replaces Primary Account Numbers (PANs) with
Payment Tokens that can be used as payment credentials during payment
transaction processing. VTS stores the Payment Tokens and performs PAN
mapping to enable functions like detokenization and life-cycle management.

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 these circumstances:

l In AFTs when funding a Staged Digital Wallet before the cardholder makes a
purchase.
l 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 Transaction (OCT) with a BAI = WT.

15 April 2023 Visa Confidential 157

You might also like