Oct.

2025 Business Enhancement Release

Hong Kong and Macau
5 Aug. 2025
Hong Kong Client Services

©2024 Visa. All rights reserved. Visa Confidential 1

Notice of confidentiality
This presentation is furnished to you solely in your capacity as a customer of Visa Inc. and/or a
participant in the Visa payments system. By accepting this presentation, you acknowledge that the
information contained herein (the “Information”) is confidential and subject to the confidentiality
restrictions contained in Visa’s operating regulations and/or other confidentiality agreements,
which limit your use of the Information. You agree to keep the Information confidential and not to
use the Information for any purpose other than in your capacity as a customer of Visa Inc. or as a
participant in the Visa payments system. The Information may only be disseminated within your
organization on a need-to-know basis to enable your participation in the Visa payments system.
Please be advised that the Information may constitute material nonpublic information under U.S.
federal securities laws and that purchasing or selling securities of Visa Inc. while being aware of
material nonpublic information would constitute a violation of applicable U.S. federal securities
laws.

©2024 Visa. All rights reserved. Visa Confidential 2

Getting Started for the Webinar

Arrangement Presenters Questions

• Business Summary • Host: Jacky Xu • Pose your questions in the

• BER Articles: William Wong chat panel
• Technical Changes
• Testing and Activations • BER Articles: Elva Liu
• Frequently Asked Questions • BER Articles Jacky Xu
• Key Points

©2024 Visa. All rights reserved. Visa Confidential 3

Article 2.6

Changes to Support Visa Digital Commerce

Authentication Program for Domestic and
Cross-Border Transactions

©2024 Visa. All rights reserved. Visa Confidential 4

Article 2.6
Changes to Support Visa Digital Commerce Authentication Program for Domestic and Cross-Border Transactions

Key Details
Regional Impact About This Change
Acquirers: Issuers: Mandatory
✓ AP ✓ AP
✓ Canada ✓ Canada Testing Not Required
✓ CEMEA ✓ CEMEA Activation Not Required
✓ Europe ✓ Europe
✓ LAC ✓ LAC
✓ U.S. ✓ U.S. Effective
1000 GMT 17 October / CPD 18 October 2025

©2024 Visa. All rights reserved. Visa Confidential 5

Article 2.6
Changes to Support Visa Digital Commerce Authentication Program for Domestic and Cross-Border Transactions

Business Summary
Product Strategy
— Visa will expand support of the Visa Digital Commerce Authentication Program (VDCAP) indicator to all
regions for domestic and cross-border card-not-present transactions. This indicator will convey the
presence of certain key data elements and the eligible method used to share authentication data.

— The primary goal is to improve authorization rates, reduce fraud and enhance the cardholder
experience. By increasing adoption of Visa’s data-sharing and authentication solutions in the CNP
environment, Visa aims to provide a seamless and secure way to improve transaction performance
without adding friction for the end user.

©2024 Visa. All rights reserved. Visa Confidential 6

Article 2.6
Changes to Support Visa Digital Commerce Authentication Program for Domestic and Cross-Border Transactions

Business Summary
• Benefits to Acquirers
— Acquirers and merchants will benefit from the changes in this article to help identify transactions with
enhanced data, ensuring that they are processed securely and efficiently.

• Benefits to Issuers
— Issuers will benefit from the changes in this article by being able to easily identify transactions with
additional risk data in authorization requests, enabling better decision-making and potentially reducing
fraud.

©2024 Visa. All rights reserved. Visa Confidential 7

Article 2.6
Changes to Support Visa Digital Commerce Authentication Program for Domestic and Cross-Border Transactions

Mandatory Technical Changes

• Visa will implement an Indicator in V.I.P to identify transactions with enhanced data
— Issuers and Acquirers that receive the Additional Transaction Specific Data field must support this
indicator
— TLV Field 111 – Additional Transaction-Specific Data, Dataset ID 56, Tag 89 – Applied Special Service
— Acquirers must also be aware of the VDCAP indicator as it related to BASE II transactions
— BASE II Draft Data, TCR 6 – Limited-Use Data, position 157 – Applied Special Service

• Visa will implement additional values in the existing Authentication Program field
— Issuers that receive this field must support any of these values indicate which data sharing method was
used
— TLV Field 34, Dataset ID 01, Tag C0 – Authentication Program
— Values:
— 01 (DAF) ; 02 (Visa Secure) ; 03 (Visa Data Only) ; 04 (Visa Payment Passkey with Visa Secure) ;
05 (Visa Payment Passkey with Visa Token Service) ; 06 (IDX 3 rd Party) ; 07 (Visa Token Service Data Only)

©2024 Visa. All rights reserved. Visa Confidential 8

Article 2.6
Changes to Support Visa Digital Commerce Authentication Program for Domestic and Cross-Border Transactions

Technical Changes

• Acquirers that receive the Additional Transaction-Specific Data field must support receiving the VDCAP
indicator in V.I.P.
— Field 111 Dataset ID 56 Tag 89

• Issuers that receive the Acceptance Environment Data field, Additional Transaction Specific Data field,
and Customer Related Data field must support receiving the additional authentication data described in
this article.
— Field 34 Dataset ID 01, 06, and 56
— Field 56 Dataset ID 02 and 05
— Field 111 Dataset ID 56 Tag 89

©2024 Visa. All rights reserved. Visa Confidential 9

Article 2.6
Changes to Support Visa Digital Commerce Authentication Program for Domestic and Cross-Border Transactions

Mandatory Technical Changes

• Visa will implement sharing of additional customer related data in V.I.P.
— Issuers that receive TLV Field 56 – Customer Related Data must be prepared to receive contact
information including Phone Number
— TLV Field 56, Dataset ID 02, Tag 83 – Other phone number

©2024 Visa. All rights reserved. Visa Confidential 10

Article 2.6
Changes to Support Visa Digital Commerce Authentication Program for Domestic and Cross-Border Transactions

Version 2 updates
Removal of PAR activation dependency to receive email and/or address data in TLV Field 56
— Visa will remove the dependency on activating payment account reference (PAR) to receive other datasets in Field 56
– Customer Related Data in TLV format, including datasets that contain email and/or address data as previously
announced in the Clarifications and Amplifications published on 1 April 2026.

Mandated support of VDCAP fields, effective April 2026:

— Effective with the April 2026 release, Visa will mandate support of VDCAP fields to Acquirers in all regions and Issuers
in the AP, Europe, LAC and US regions.
— Endpoints that do not support the applicable data in Tag Length Value (TLV) fields will be required to begin processing
them with the April 2026 release.
— Acquirers in all regions that have not implemented support of the Additional Transaction Specific data field will be
mandated to support it. In addition, acquirers in all regions must retain and return the VDCAP indicator in the clearing
transaction.
— Issuers in the AP, Europe, LAC and US regions that have not implemented support of the Acceptance Environment
Data, Customer-Related Data (in two-byte length) and Additional Transaction Specific Data in TLV fields will be
mandated to support them.

©2024 Visa. All rights reserved. Visa Confidential 11

Article 2.6
Changes to Support Visa Digital Commerce Authentication Program for Domestic and Cross-Border Transactions

Use Cases
• For a given transaction, the Merchant / Acquirer shares all program defined consumer data elements using
Visa Data Only
— The transaction includes enhanced data and receives the VDCAP Indicator in Field 111
— The transaction receives an Authentication Program Indicator of 03 (Visa Data Only)
— Program defined consumer data elements are shared with the issuer in the V.I.P. authorization request

• For a given transaction, the Merchant / Acquirer shares all program defined consumer data elements using
Visa Token Service Data Only
— The transaction includes enhanced data and receives the VDCAP Indicator in Field 111
— The transaction receives an Authentication Program Indicator of 07 (Visa Token Service Data Only)
— Program defined consumer data elements are shared with the issuer in the V.I.P. authorization request

©2024 Visa. All rights reserved. Visa Confidential 12

Article 2.6
Changes to Support Visa Digital Commerce Authentication Program for Domestic and Cross-Border Transactions

Frequently Asked Questions

• What is VDCAP?
— Introducing the Visa Digital Commerce Authentication Program (VDCAP) – A global program that helps in
mitigating fraud and improving authorization approval rates without adding friction to the payment
experience. By adopting and using Visa-approved data sharing and authentication solutions, VDCAP
promotes effective data sharing between Merchants and Issuers, all while maintaining a seamless,
secure, and frictionless cardholder checkout experience in the Card-Not-Present environment.
• In which market is VDCAP available?
— VDCAP is a global program. Please refer to the regional VBNs on the effective date of domestic and
cross-border transactions.
• What are the program benefits?
— Each region offers unique VDCAP requirements to improve authorization rates, reduce fraud and
enhance the cardholder experience. For more information, please refer to the regional program guide.

©2024 Visa. All rights reserved. Visa Confidential 13

Article 2.6
Changes to Support Visa Digital Commerce Authentication Program for Domestic and Cross-Border Transactions

Resources
• Visa Business News Articles:
— Regional VBNs contain more program details:
— Europe: AI15285 – Introduction of the Visa E-Commerce Experience and the Future of Payments in
Europe, published June 26th 2025
— All other regions: VBNs to be published in the coming months

©2024 Visa. All rights reserved. Visa Confidential 14

©2024 Visa. All rights reserved. Visa Confidential 15
Article 2.11
Changes to Response
Code Processing

©2024 Visa. All rights reserved. Visa Confidential 16

Article 2.11
Changes to Response Code Processing

Visa will convert response code 57 received from Issuers in Authorization messages to 05

Regional Impact About This Change

Acquirers: Issuers: Mandatory
✓ AP ✓ AP
✓ Canada ✓ Canada Testing Not Available
✓ CEMEA ✓ CEMEA Activation Not Required
✓ Europe ✓ Europe
✓ LAC ✓ LAC
✓ U.S. ✓ U.S. Effective
1000 GMT 17 October 2025

©2024 Visa. All rights reserved. Visa Confidential 17

Article 2.11
Changes to Response Code Processing

Business Summary
Background
Response code quality is essential for merchants to determine the reasons for declined authorization requests
and to perform corrective actions to ensure the sale is completed. Visa is constantly striving to improve response
quality, thereby increasing recovery and satisfaction for all parties involved in a transaction.

What are we solving for?

• Some Response codes do not allow for corrective actions, retrying these transactions causes a reduction in
issuer authorization rates
• Response code 57 (Transaction not permitted to cardholder) falls in this category and has high volume of retries
• Approvals after decline due to Response Code 57 is only due to issuer misuse and needs to be corrected

Strategy
• Reserve response 57 for Visa use only, all issuer use would be considered generic and would be counted towards
issuer generic response code limit
• Introduction of additional response codes (Article 2.11 April 2025 BER) that better communicates the intent of the
decline
©2024 Visa. All rights reserved. Visa Confidential 18
Article 2.11
Changes to Response Code Processing

Summary of Change
Visa will reclassify response 57 in issuer responses to 05 for authorization and full financial requests

0100 request 0100 request

0110 response 0110 response

F39 - 05 F39 - 57
Acquirer/ Visa Issuer
Merchant
Visa would convert response code 57 Message Type – 0100 Authorization or
to 05 when received from Issuers when 0200 Full financial request
received for the conditions Processing Code (F3.1) – 00, 10, 11 & 50

For Issuers For Acquirers

• Review situations where response code 57 is • No change required, response code 57 may still
applied and select a more applicable response be issued by Visa in Stand-in processing (STIP)
code that clearly communicates the decline
reason
• The converted response code will be counted
as part of Issuers generic response code with
the applicable fee to drive compliance
©2024 Visa. All rights reserved. Visa Confidential 19
Article 2.11
Changes to Response Code Processing

Mandatory Technical Changes

©2024 Visa. All rights reserved. Visa Confidential 20

Article 2.11
Changes to Response Code Processing

Testing and Activation

• No testing or activation required

©2024 Visa. All rights reserved. Visa Confidential 21

Article 2.11
Changes to Response Code Processing

Key Points
• The changes to authorization response codes are effective globally from 17 October 2025.
• All Authorization and Full Financial requests declined with response code 57 from issuers will be
converted to 05 for the stated processing codes
• Issuer are strongly encouraged to review their use of response code 57 and use a more precise response
code to communicate the reason for the decline.
• Acquirers are reminded to expect the new values 9G & 5C introduced with the April 2025 BER
• No new change required from acquirers if 9G & 5C is supported. Response code 57 may still be sent by
Visa in Stand In Processing.

©2024 Visa. All rights reserved. Visa Confidential 22

Article 2.11
Changes to Response Code Processing

Resources
• Visa Business News Articles:
— AI14804 “Updated: Incorrect Use of Authorization Response Codes Will Be Reclassified”, Visa Business
News, 19 December 2024

• Other Documentation
— Visa Response Codes – Requirements and Best Practices, Risk Best Practices page on Visa Access

©2024 Visa. All rights reserved. Visa Confidential 23

©2024 Visa. All rights reserved. Visa Confidential 24
Article 3.4
Changes to Support Domestic and Cross-Border
Account Funding Transactions

©2024 Visa. All rights reserved. Visa Confidential 25

Article 3.4
Changes to Support Domestic and Cross-Border Account Funding Transactions

Key Details

Regional Impact About This Change

Acquirers: Issuers: Mandatory
✓ No Impact ✓ AP
✓ Canada Testing Available
✓ CEMEA Activation Not Required
✓ Europe
✓ LAC
✓ U.S. Effective
1000 GMT 17 October / CPD 18 October 2025

©2024 Visa. All rights reserved. Visa Confidential 26

Article 3.4
Changes to Support Domestic and Cross-Border Account Funding Transactions

Business Summary
• Currently, sender data contained in Field 104 and Field 56 is dropped from all domestic non-money
transfer AFTs, before sending it to Issuers.
• This change ensures that all sender data is forwarded to the Issuer’s authorization system
• As domestic data requirements may vary across each region/country, this could lead to Issuer non-
compliance with their regulatory requirements
• This feature aims to enhance regulatory compliance for Issuers and improving overall transaction
acceptance, by providing complete sender data

©2024 Visa. All rights reserved. Visa Confidential 27

Article 3.4
Changes to Support Domestic and Cross-Border Account Funding Transactions

Business Summary
• Benefits
• Enables Issuers to receive sender data in Field 104 and Field 56, which benefits the Visa Direct
ecosystem, including improved authorization rates
• Issuers benefit from improved overall acceptance by enabling regulatory compliance in the regions they
operate in

©2024 Visa. All rights reserved. Visa Confidential 28

Article 3.4
Changes to Support Domestic and Cross-Border Account Funding Transactions

Mandatory Technical Changes

• V.I.P. to include certain sender data in domestic and cross-border AFTs sent to issuers:

— Field 104, Usage 2, Dataset ID 5F (Sender Data)

— Sender Reference Number (Tag 01)
— Sender Account Number (Tag 02)
— Sender Name (Tag 03)
— Sender Address (Tag 04)
— Sender City (Tag 05)
— Sender State (Tag 06)
— Sender Country (Tag 07)

©2024 Visa. All rights reserved. Visa Confidential 29

Article 3.4
Changes to Support Domestic and Cross-Border Account Funding Transactions

Mandatory Technical Changes

• V.I.P. to include certain sender data in domestic and cross-border AFTs sent to issuers that are enabled to
receive F56 in a 2-byte format:

— Field 56, Dataset ID 05 (Account Owner Data)

— Entity Type (Tag C0) — Account Owner Postal Code (Tag 8A)
— Account Reference Code (Tag 80) — Account Owner City Name (Tag 8B)
— Account Owner Name, Given (Tag 83) — Account Owner Country Code (Tag 8E)
— Account Owner Name, Middle (Tag 84) — Account Owner Nationality (Tag 8F)
— Account Owner Name, Last (Tag 85) — Account Owner Country of Birth (Tag 90)
— Account Owner Address Line 1 (Tag 86) — Account Owner Occupation (Tag 91)
— Account Owner Address Line 2 (Tag 87) — Account Owner Date of Birth (Tag 92)
— Account Owner Street Name (Tag 88) — Account Owner Email Address Personal (Tag 97)
— Account Owner Building Number (Tag 89)

©2024 Visa. All rights reserved. Visa Confidential 30

Article 3.4
Changes to Support Domestic and Cross-Border Account Funding Transactions

Mandatory Technical Changes

• Jurisdiction: Domestic and XB AFTs

• BAIs in Scope:
— Non-Money Transfer: BB, FD, GD, GP, LO, MD, MI, OG, PD, BP, CP, VA

©2024 Visa. All rights reserved. Visa Confidential 31

Article 3.4
Changes to Support Domestic and Cross-Border Account Funding Transactions

Use Cases

• Sender Name (Tag 03) is sent by the Acquirer in Field 104 on a domestic AFT with a non-money transfer BAI:
• VIP will forward the data in Field 104 if the Issuer receives TLV Field 104
• VIP will drop the data in Field 104 if the Issuer is not set up to receive TLV Field 104

• Account Owner Name, Middle is sent by the Acquirer in Field 56, DSID 05 on a domestic AFT with a
non-money transfer BAI:
• VIP will forward the data in Field 56 if the Issuer is set up to receive 2-byte data in Field 56
• VIP will drop the data in Field 56 if the Issuer is not set up to receive 2-byte data in Field 56

©2024 Visa. All rights reserved. Visa Confidential 32

Article 3.4
Changes to Support Domestic and Cross-Border Account Funding Transactions

Testing and Activation

• Testing is available – 0000 GMT 14 September 2025

• Activation Not Required

©2024 Visa. All rights reserved. Visa Confidential 33

Article 3.4
Changes to Support Domestic and Cross-Border Account Funding Transactions

Frequently Asked Questions

• Why do we need these changes?
— The changes are required to assist Issuers in meeting their regulatory obligations thereby enabling
broader acceptance for Visa Direct.

• Which countries do the changes apply to?

— The requirements are applicable globally, as per the scope of transactions specified. Any AFTs where
the sender data in Field 104 or Field 56 gets dropped currently will be sent to Issuers in the authorization
message

• When are these changes effective?

— All changes are effective by October 25 BER.

©2024 Visa. All rights reserved. Visa Confidential 34

Article 3.4
Changes to Support Domestic and Cross-Border Account Funding Transactions

Key Points
• For domestic non-money transfer AFTs, Issuers will receive sender data in TLV Field 104 and/or TLV Field
56
• Issuers enabled to receive TLV Field 56 and TLV Field 104 will receive sender data in both fields.
• Issuers that do not receive TLV Field 104 or TLV Field 56
• The sender data fields will be dropped from the authorization message to the Issuer
• Transactions will not be declined as a result of this change

©2024 Visa. All rights reserved. Visa Confidential 35

Article 3.4
Changes to Support Domestic and Cross-Border Account Funding Transactions

Resources

• Other Documentation
— Technical Letter Article 3.4 v1 – Changes to Support Domestic and Cross Border AFTs (Published on Visa
Access)

©2024 Visa. All rights reserved. Visa Confidential 36

©2024 Visa. All rights reserved. Visa Confidential 37
Article 3.6
Changes to Support Domestic and Cross-Border
Account Funding Transactions and Original Credit
Transactions

©2024 Visa. All rights reserved. Visa Confidential 38

Article 3.6
Changes to Support Domestic and Cross-Border Account Funding Transactions and Original Credit
Transactions

Key Details
Regional Impact About This Change
Acquirers: Issuers: Mandatory
✓ AP ✓ AP
✓ Canada ✓ Canada Testing Not Required
✓ CEMEA ✓ CEMEA Activation Not Required
✓ Europe ✓ Europe
✓ LAC ✓ LAC
✓ U.S. ✓ U.S. Effective
1000 GMT 17 October 2025

©2024 Visa. All rights reserved. Visa Confidential 39

Article 3.6
Changes to Support Domestic and Cross-Border Account Funding Transactions and Original Credit
Transactions
Business Summary
• There will be updates to the requirements for Sender and Recipient fields across 2 dimensions:
• New requirements for presence of data in cross-border non-money transfer OCTs and AFTs
• Consistent data integrity requirements across OCTs and AFTs

• The rationale behind these updates is to assist clients in meeting their regulatory obligations and to build
overall acceptance for Visa Direct
• It enables Visa Direct transactions to be processed with high data integrity
• Aims to provide a consistent and reliable experience for all stakeholders involved in Visa Direct
transactions

©2024 Visa. All rights reserved. Visa Confidential 40

Article 3.6
Changes to Support Domestic and Cross-Border Account Funding Transactions and Original Credit
Transactions
Business Summary
• Benefits
• Ensure transactions contain robust data, which benefits the Visa Direct ecosystem, including improved
authorization rates
• Issuers benefit from improved overall acceptance by enabling regulatory compliance in the regions they
operate in
• Reduces the risk of inconsistent system edits across different fields within Visa Direct transactions
• Helps to govern data integrity rules to reduce bad data and improve authorization rates

©2024 Visa. All rights reserved. Visa Confidential 41

Article 3.6
Changes to Support Domestic and Cross-Border Account Funding Transactions and Original Credit
Transactions
Mandatory Technical Changes
• System edits on the presence of below fields for XB Non-Money Transfer OCTs and AFTs:
— Field 104, Usage 2, Dataset ID 5F (Sender Data) *
— Sender Name (Tag 03)
— Sender Address (Tag 04)
— Sender City (Tag 05)
— Sender Country (Tag 07)
— Recipient Name (Tag 0A) ** (Note: Recipient Name system edit will be enforced in April 2026 BER)
• BAIs in Scope: BB, FD, GD, GP, LO, MD, MI, OG, PD, BP, CP
• XB OCTs and AFTs with non-money transfer BAIs will be declined by VIP with response code 64
(Transaction does not fulfill AML requirement), if the above fields are not present, as per the BER cadence
specified.
• Acquirers must ensure to send the above fields for XB Non-Money Transfer OCTs and AFTs

* Fields are already required for MT OCTs and AFTs

©2024 Visa. All rights reserved. Visa Confidential 42

Article 3.6
Changes to Support Domestic and Cross-Border Account Funding Transactions and Original Credit
Transactions
Mandatory Technical Changes
• Data integrity checks and validations will be performed by VIP on the below fields for Domestic and XB,
Money-transfer and Non-Money Transfer OCTs and AFTs:
— Field 104, Usage 2, Dataset ID 5F (Sender Data):
— Sender Name (Tag 03) – Scope of data integrity and validations include domestic and XB Money-transfer OCTs and
AFTs, Non-MT OCTs and AFTs are out of scope
— Sender City (Tag 05) – Scope of data integrity and validations include all domestic and XB Money-transfer and Non-
Money transfer OCTs and AFTs
— Recipient Name (Tag 0A) – Scope of data integrity and validations include domestic and XB Money-transfer OCTs
and AFTs, and Non-money transfer OCTs. Non-MT AFTs are out of scope

• BAIs in Scope:
— Money-Transfer: AA, BI, CD, FT, LA, PP, WT
— Non-Money Transfer: BB, FD, GD, GP, LO, MD, MI, OG, PD, BP, CP, VA

©2024 Visa. All rights reserved. Visa Confidential 43

Article 3.6
Changes to Support Domestic and Cross-Border Account Funding Transactions and Original Credit
Transactions
Mandatory Technical Changes
• VIP will decline transactions if F104, DSID 5F, Tags 03, 05, and 0A contain:
o Special characters: ? # = $ ! & : ~ | _ + \ /
o All numeric characters, including all zeros (e.g., 123456)
o All spaces
o Less than 3 characters (Minimum character limit is 3 characters)

• As of October 25 BER, VIP will decline transactions that do not meet the data integrity and validation
criteria specified for the in-scope fields and transaction types, with response code 64 (Transaction does
not fulfill AML requirement)

• Acquirers must ensure the data integrity of the fields and transaction types in scope

©2024 Visa. All rights reserved. Visa Confidential 44

Article 3.6
Changes to Support Domestic and Cross-Border Account Funding Transactions and Original Credit
Transactions
Use Cases

• Sender Name or Recipient Name invalid field examples –

• J#e $mith (Use of special characters)
• 00000 (All numeric)
• AG (Less than 3 characters)

• Sender City invalid field examples –

• &ydney
• (all spaces)

©2024 Visa. All rights reserved. Visa Confidential 45

Article 3.6
Changes to Support Domestic and Cross-Border Account Funding Transactions and Original Credit
Transactions
Testing and Activation

• Testing Not Required

• Activation Not Required

©2024 Visa. All rights reserved. Visa Confidential 46

Article 3.6
Changes to Support Domestic and Cross-Border Account Funding Transactions and Original Credit
Transactions
Frequently Asked Questions
• Why do we need these changes?
— The changes are required to assist Issuers in meeting their regulatory obligations and for Acquirers to
improve their authorization rates, thereby enabling broader acceptance for Visa Direct.

• Which countries do the changes apply to?

— The system edits for the presence of the fields, and data integrity checks and validation requirements
are applicable globally, as per the scope of transactions specified

• When are these changes effective?

— All changes are effective by October 25 BER, except the changes on system edits for the presence of the
field Recipient Name. The system edit on Recipient Name will be effective by April 2026 BER.

©2024 Visa. All rights reserved. Visa Confidential 47

Article 3.6
Changes to Support Domestic and Cross-Border Account Funding Transactions and Original Credit
Transactions

Key Points
• System edits for the presence of Sender Data fields will be enforced – October 25 BER and Recipient
Name field – Apr 26 BER

• Data integrity and validations checks will be performed on Sender Name, Sender City, and Recipient
Name fields – October 25 BER

• Transactions that do not meet the system edits and data integrity criteria:
— Will be declined with response code 64 – Transaction does not fulfill AML requirement

©2024 Visa. All rights reserved. Visa Confidential 48

Article 3.6
Changes to Support Domestic and Cross-Border Account Funding Transactions and Original Credit
Transactions

Resources
• Visa Business News Articles:
— AI 14787 – Visa Direct: Data Field Requirement Changes for AFTs and OCTs (Published on Visa Access)

• Implementation/User Guides
— Not Applicable

• Other Documentation
— Technical Letter Article 3.6 v1 – Changes to Support Domestic and Cross Border AFTs and OCTs
(Published on Visa Access)

©2024 Visa. All rights reserved. Visa Confidential 49

©2024 Visa. All rights reserved. Visa Confidential 50
Article 2.7
Changes to Support Visa Digital
Commerce Authentication
Program for Token Transactions

©2024 Visa. All rights reserved. Visa Confidential 51

Article 2.7
Changes to Support Visa Digital Commerce Authentication Program for Token Transactions

Key Details

Regional Impact About This Change

Acquirers: Issuers: Mandatory
✓ AP ✓ AP
✓ Canada ✓ Canada Testing Available
✓ CEMEA ✓ CEMEA Activation Not Required
✓ Europe ✓ Europe
✓ LAC ✓ LAC
✓ U.S. ✓ U.S. Effective
1000 GMT 17 October / CPD 18 October 2025

©2024 Visa. All rights reserved. Visa Confidential 52

Article 2.7
Changes to Support Visa Digital Commerce Authentication Program for Token Transactions

Business Summary

Product Strategy
• Visa is introducing enhancements to the Visa Token Service to support the Visa Digital Commerce
Authentication Program (VDCAP). This program is designed to improve the security and efficiency of
token card-not-present transactions by including enhanced risk data elements. A new VDCAP indicator
will be included in the transaction data sent to issuers and acquirers, providing them with additional
information to make more informed authorization decisions.

• The primary goal is to improve authorization rates, reduce fraud, and enhance the cardholder experience.
By increasing the adoption of Visa’s data-sharing and authentication solutions in a card-not-present
environment, Visa aims to provide a seamless and secure transaction process without adding friction for
the end user. This enhancement simplifies the integration process for token requestors while maintaining
a seamless experience for issuers, allowing for better approval decision-making.

©2024 Visa. All rights reserved. Visa Confidential 53

Article 2.7
Changes to Support Visa Digital Commerce Authentication Program for Token Transactions

Business Summary

• Benefits to Acquirers
— Acquirers and their merchants will appreciate this feature as it helps identify transactions with enhanced
data, ensuring they are processed securely and efficiently.

• Benefits to Issuers
— Issuers will value this feature because it provides additional risk data in authorization requests, enabling
better decision-making and potentially reducing fraud.

©2024 Visa. All rights reserved. Visa Confidential 54

Article 2.7
Changes to Support Visa Digital Commerce Authentication Program for Token Transactions

Technical Changes
• Acquirers that receive the Additional Transaction-Specific Data field must support receiving the VDCAP
indicator in V.I.P.
— Field 111 Dataset ID 56 Tag 89
• Acquirers may populate the VDCAP indicator in BASE II
— BASE II Draft Data, TCR 6—Limited-Use Data, position 157—Applied Special Service
• Issuers that receive the Acceptance Environment Data field, Additional Transaction Specific Data field,
and Customer Related Data field must support receiving the additional authentication data described in
this article.
— Field 34 Dataset ID 01, 06, and 56
— Field 56 Dataset ID 02 and 05
— Field 111 Dataset ID 56 Tag 89
• Issuers must be prepared to receive the VDCAP indicator in BASE II
— BASE II Draft Data, TCR 6—Limited-Use Data, position 157—Applied Special Service

©2024 Visa. All rights reserved. Visa Confidential 55

Article 2.7
Changes to Support Visa Digital Commerce Authentication Program for Token Transactions

Merchant
Transaction Flow Token Requestor
Visa Token
Service
Request TAVV for
CNP transaction +
Risk Data
1
4 2
TAVV + ECI7

Auth with
3
Transaction
successful Token + TAVV +
ECI7 Visa Intelligent
Data Exchange

8
12
7
Auth with Auth with
Token + TAVV + ECI7 Token + ECI7 + Risk Data +
VDCAP
6 9

11 10
Approval + VDCAP Approval

Acquirer VisaNet Issuer

©2024 Visa. All rights reserved. Visa Confidential 56

Article 2.7
Changes to Support Visa Digital Commerce Authentication Program for Token Transactions

Testing and Activation

• Testing is available for this article, please contact your regional client support representative for additional
information.
• Acquirers: Activation of Field 111 is optional with this article.
• Issuers: Activation of Field 34, Field 56 and Field 111 is optional with this article.

©2024 Visa. All rights reserved. Visa Confidential 57

Article 2.7
Changes to Support Visa Digital Commerce Authentication Program for Token Transactions

Effective April 2026 Technical Changes

• Acquirers will be required to receive the VDCAP indicator in the Additional Transaction-Specific Data field
— Field 111 Dataset ID 56 Tag 89
• Acquirers must populate the VDCAP indicator in BASE II
— BASE II Draft Data, TCR 6—Limited-Use Data, position 157—Applied Special Service
• Issuers in AP, Europe, LAC, and U.S. will be required to receive the additional authentication data
described in this article in the Acceptance Environment Data field, Additional Transaction Specific Data
field, and Customer Related Data field.
— Field 34 Dataset ID 01, 06, and 56
— Field 56 Dataset ID 02 and 05
— Field 111 Dataset ID 56 Tag 89

©2024 Visa. All rights reserved. Visa Confidential 58

Article 2.7
Changes to Support Visa Digital Commerce Authentication Program for Token Transactions

Frequently Asked Questions

• What is VDCAP?
— Introducing the Visa Digital Commerce Authentication Program (VDCAP) – A global program that helps in
mitigating fraud and improving authorization approval rates without adding friction to the payment
experience. By adopting and using Visa-approved data sharing and authentication solutions, VDCAP
promotes effective data sharing between Merchants and Issuers, all while maintaining a seamless,
secure, and frictionless cardholder checkout experience in the Card-Not-Present environment.
• In which market is VDCAP available?
— VDCAP is a global program. Please refer to the regional VBNs on the effective date of domestic and
cross-border transactions.
• What are the program benefits?
— Each region offers unique VDCAP requirements to improve authorization rates, reduce fraud and
enhance the cardholder experience. For more information, please refer to the regional VBNs.

©2024 Visa. All rights reserved. Visa Confidential 59

Article 2.7
Changes to Support Visa Digital Commerce Authentication Program for Token Transactions

Resources
• Implementation/User Guides
— Tech Letter: Article 2.7 Changes to Support Visa Digital Commerce Authentication Program for Token
Transactions

©2024 Visa. All rights reserved. Visa Confidential 60

©2024 Visa. All rights reserved. Visa Confidential 61
Article 3.2
Changes to Support Visa Account
Attack Intelligence Score for
Certain Regions

©2024 Visa. All rights reserved. Visa Confidential 62

Article 3.2
Changes to Support Visa Account Attack Intelligence Score for Certain Regions

Key Details
Regional Impact About This Change
Acquirers: Issuers: Available,
✓ AP ✓ AP Mandatory (LAC and AP Issuers in Oct 2025)
✓ CEMEA ✓ CEMEA
✓ LAC ✓ LAC Testing is Available
✓ US ✓ Canada Activation is Required,
✓ Canada Activation Not Required (LAC and AP Issuers in
Oct 2025)
Effective
LAC – 6 Jun 2025
AP, CEMEA – 11 Jul 2025
US, Canada – 17 Oct 2025
©2024 Visa. All rights reserved. Visa Confidential 63
Article 3.2
Changes to Support Visa Account Attack Intelligence Score for Certain Regions

Business Summary
This enhancement helps to identify when a fraudster systematically submits transactions with enumerated
values such as primary account number (PAN), card verification value (CVV2), expiration date, and postal
code to derive legitimate payment account details. If successful, fraudsters can use the payment details for
illicit means or sell the information on the dark web.
• Benefits to Issuers and Acquirers
- This feature enables issuers and acquirers to identify and mitigate enumeration attacks in real-time
thereby improve the security of card-not-present transactions. It may help in reducing fraud losses and
operational costs & excessive fees associated with enumeration, as well as protect the brand
reputation for clients.

©2024 Visa. All rights reserved. Visa Confidential 64

Account enumeration is a growing threat in today’s digital landscape

ECOSYSTEM IMPACTS
COMMON TYPES

Fees Fraud impacts

Enumeration
“Brute force attack” Operational impacts Risk exposure

Systematic initiating of CNP transactions to obtain valid

payment credentials such as PAN, CVV2, Expiry Date, etc.

HOW THESE THREATS HAVE EVOLVED

Account testing
“BIN attack”
Account Account Cybercriminals
The process of initiating 1-2 low dollar transactions to verify 1 enumeration 2 enumeration is
3 are learning the
if an account is active to take it over for illicit means or to sell attacks date as becoming intricacies of
far back as the more prevalent fraud
Typically, these attacks focus on a single BIN range early 2000’s due to COVID mitigations

©2024 Visa. All rights reserved. Visa Confidential 65

Account enumeration affects the ecosystem globally

Clients globally are impacted from both the … and consequently, face higher fraud rates and
issuing and acquiring side… complexities managing fraud

Global Enumeration Percentage by Region

July 2024 – December 2024
• Globally, enumerated accounts have 22x higher fraud
Issuer Acquirer
LAC
rates than regular accounts
EU 6%
LAC CA 7%
28% 3% • And of all the enumerated accounts that saw fraud,
33% had the first fraud occur within 5 days of when
CE…
the enumeration transaction was approved.
US
E… 51% A…

CA
US • Hence, there’s a pressing need to tackle enumerated
1%
69% transaction on a real-time basis
CEMEA AP
5% 11%

Source: Visa Biannual Threats Report, June 2025 ©2024 Visa. All rights reserved. Visa Confidential 66
 WHAT

VAAI Score VAAI Score equips clients with

Visa Account Attack Intelligence Score Help reducing fraud Real-time Cutting-edge artificial
and operational losses transaction risk score intelligence model
Helps identify complex Provides a real-time risk
A risk score designed to enumeration attacks in real-
time which can help reduce
score which can help the
clients in identifying
Uses artificial intelligence for
better performance and
help detect and prevent fraud and operational losses
due to enumeration, and
enumeration and using it in
their authorization
accuracy

enumeration attacks in ensure clients are decisioning

safeguarded VAAI SCORE
CNP transactions
MEDIUM
01-29 30-49 50-74 75-94 95-99 RISK

70
LOW RISK MEDIUM-LOW MEDIUM RISK MEDIUM-HIGH VERY HIGH RISK
RISK RISK

Powered by artificial intelligence

to improve enumeration identification WHY
and deliver a better client experience.
VAAI Score is right for clients…
Highly accurate Higher CNP approval
rates
May mitigate May reduce Peace of mind with
Lower fraud and Two-digit risk score fraud losses due operational costs global network
operational losses that helps predict the
likelihood of to enumeration and excessive fees level support
enumeration

©2024 Visa. All rights reserved. Visa Confidential 67

VAAI uses cutting-edge artificial intelligence to identify enumeration and generate a risk s
enable clients to take appropriate action in real-time

CARDHOLDER or MERCHANT ACQUIRER VISANET

FRAUDSTER
Authorization request Authorization request
Initiates CNP 3
2
transaction 1

8 7 4

Auth response with Auth response with

VAAI Score if VAAI SCORING MODEL
VAAI Score
Acquirer Scores transaction
participates in real-time

Auth request with

6 5
Issuer decision VAAI Score if
(approve/decline) Issuer participates

ISSUER

©2024 Visa. All rights reserved. Visa Confidential 68

Article 3.2
Changes to Support Visa Account Attack Intelligence Score for Certain Regions

Business Summary
• Issuer Impact
— Effective 6 Jun 2025, Visa will introduce the Visa Account Attack Intelligence Score functionality to LAC Issuers if they
choose to participate in receiving the score.
— Effective 11 Jul 2025, Visa will introduce the Visa Account Attack Intelligence Score functionality to AP and CEMEA
Issuers if they choose to participate in receiving the score.
— Effective 17 October 2025, Visa will introduce the Visa Account Attack Intelligence Score functionality to Canada Issuers
if they choose to participate in receiving the score.
— Effective 17 October 2025, Visa will require issuers in the AP and LAC region that support the Transaction-Specific Data
field to support the Visa Account Attack Intelligence Score for card-not-present transactions.
• Acquirer Impact
— Effective 11 Jul 2025, Visa will introduce the Visa Account Attack Intelligence Score functionality to AP and CEMEA
Acquirers if they choose to participate in receiving the score.
— Effective 17 October 2025, Visa will introduce the Visa Account Attack Intelligence Score functionality to Canada and US
Acquirers if they choose to participate in receiving the score.
Issuers and Acquirers that choose to participate in the new Visa Account Attack Intelligence Score must be
prepared to support the new tag, values, and processing rules as described in the technical letter.

©2024 Visa. All rights reserved. Visa Confidential 69

Article 3.2
Changes to Support Visa Account Attack Intelligence Score for Certain Regions

Technical Changes
• Visa will implement a new tag, values, and processing rules for card-not-present transactions to
support the new Visa Account Attack Intelligence Score.

• Changes to TLV Field 104, Usage 2

- V.I.P. will send the Visa Account Attack Intelligence Score in the request message to the Issuer and in the
response message to the Acquirer based on the participation parameter defined in VisaNet to receive this
field.
- Issuers and Acquirers that choose to receive the Visa Account Attack Intelligence Score in the request or
response messages must be prepared to receive the Tag 85 in the existing TLV Field 104, Usage 2—
Transaction-Specific Data in TLV format, Dataset ID 5B—Visa Assessment Data.
- Effective 17 October 2025, Visa will require issuers in the AP and LAC region that support the existing TLV
Field 104, Usage 2 will be activated to receive the Visa Account Attack Intelligence Score Tag 85 for card-
not-present transactions.

©2024 Visa. All rights reserved. Visa Confidential 70

Article 3.2
Changes to Support Visa Account Attack Intelligence Score for Certain Regions

Testing
• Testing is NOT required
- Effective with the April 2025 release test period, testing will be available in V.I.P. for clients wishing to
test the functionality for the Visa Account Attack Intelligence Score. Contact your regional testing
support representative for testing assistance.
• The following table summarizes the testing availability and requirements for this enhancement.

©2024 Visa. All rights reserved. Visa Confidential 71

Article 3.2
Changes to Support Visa Account Attack Intelligence Score for Certain Regions

Frequently Asked Questions

• Are there any fees for receiving the Visa Account Attack Intelligence Score?
— Yes, please refer Visa fee schedule for the fee details.

• How is the Visa Account Attack Intelligence Score different from other scores at Visa?
— Visa Account Attack Intelligence focuses on a particular use case which is to identify enumeration attacks
in real-time.

• Is Visa Account Attack Intelligence Score data authorization or authentication?

— Visa Account Attack Intelligence Score will only include authorization data.

©2024 Visa. All rights reserved. Visa Confidential 72

Article 3.2
Changes to Support Visa Account Attack Intelligence Score for Certain Regions

Frequently Asked Questions

— How can the clients sign up for Visa Account Attack Intelligence Score?
— Clients can sign up by contacting their Account Executive/Client Support Manager or contacting Visa
Support Hub and enrolling through the Global Enrollment Portal.
— The Issuers in AP and LAC regions will be systematically activated with Oct 2025 BER and they don’t need
to sign up. The Issuers in these regions who support the existing TLV Field 104, Usage 2 must support the
Visa Account Attack Intelligence Score Tag 85 for card-not-present transactions.

©2024 Visa. All rights reserved. Visa Confidential 73

Client Resources

• Visa Account Attack Intelligence (VAAI) Score Visa Online page

• VAAI Client Deck
• VisaNet Business Enhancements—April 2024 and July 2024 Releases
• Refer to Article 11.4.1—Introduction of the New Visa Account Attack Intelligence Score in the April 2024
and July 2024 VisaNet Business Enhancements Global Technical Letter and Implementation Guide
• Visa Account Attack Intelligence (VAAI) Score Service Description (PDF)
• Updated Guidance to Guard Against Enumeration Attacks and Accounts Testing Schemes, Visa Business
News, 15 June 2023 (PDF)

©2024 Visa. All rights reserved. Visa Confidential 74

©2024 Visa. All rights reserved. Visa Confidential 75
Article 3.10
Changes to Token Activation Request
Messages to Support Token
Requestor Onboarding Information

©2024 Visa. All rights reserved. Visa Confidential 76

Article 3.10
Changes to Token Activation Request Messages to Support Token Requestor Onboarding Information

Key Details

Regional Impact About This Change

Acquirers: Issuers: Mandatory
✓ No impact ✓ AP
✓ Canada Testing Available
✓ CEMEA Activation Not Required
✓ Europe
✓ LAC
✓ U.S. Effective
1000 GMT 17 October 2025

©2024 Visa. All rights reserved. Visa Confidential 77

Enhanced Merchant Onboarding Process (Future)

Consumer Merchant/TR Visa Issuer

1 Merchant Onboarding Requested

Visa validates the request (e.g. OFAC 2

checks) and assigns a TRID

3 TRIDs sent to issuer (TC33, VAP,

API)
4 Initiates 4 In a batch
TR-TSP initiates a token provisioning request
Checkout
Visa attempts to route the
5 provisioning request but with the
full TRID and onboarding
metadata

Issuers will now receive all necessary TRID information inline during provisioning and can:
1. Approve Provisioning immediately, reducing onboarding delays
2. Avoid waiting for TC33 or batch reports
©2024 Visa. All rights reserved. Visa Confidential 78
Article 3.10
Changes to Token Activation Request Messages to Support Token Requestor Onboarding Information

Business Summary Our Purpose is to:

• Product Strategy
— Visa support of this topic as part of its vision to
streamline digital enablement and tokenization
Uplift
— Enables Token Requestors and Token
Requestor-Token Service Providers (TR-TSPs) to
everyone, everywhere
start provisioning immediately after onboarding
by being the best way to
— Enhances issuer experience by reducing offline
dependency and accelerating go-to-market
pay and be paid
readiness

©2024 Visa. All rights reserved. Visa Confidential 79

Article 3.10
Changes to Token Activation Request Messages to Support Token Requestor Onboarding Information

Business Summary
• Benefits
Industry Streamlined TRID onboarding promotes wider adoption of digital wallets and tokenized payments,
aligning with security and innovation trends.

Issuers Faster onboarding of token requestors, reduced operational delays, and improved approval accuracy
during token provisioning.

Merchant Supports quicker acceptance of tokenized credentials, driving higher auth success and better
customer experience.

Consumer
Faster availability of tokenized payment methods when enrolling new accounts, reducing friction at the
point of transaction.

©2024 Visa. All rights reserved. Visa Confidential 80

Article 3.10
Changes to Token Activation Request Messages to Support Token Requestor Onboarding Information

Business Summary
• Reason Why
— Visa believes this enhancement is the best solution because it provides real-time visibility into token
requestor onboarding, enabling immediate and secure provisioning.
— This solution minimizes the reliance on batch processes and offline reports, which historically caused
delays and manual intervention
— Lastly, this solution is scalable, standard-based (TLV format), and leverages existing infrastructure

©2024 Visa. All rights reserved. Visa Confidential 81

Article 3.10
Changes to Token Activation Request Messages to Support Token Requestor Onboarding Information

Mandatory Technical Changes

— Support required for new and existing tags in Field 123, Usage 2 – Verification and Token Data (TLV
Format)

— Accept new TLV tags in Dataset ID 68

— Tag 88 – Token Requestor ID Assigned Date [Format: ccyymmdd]
— Tag 89 – Token Requestor Type (3 values)
— Tag 8A – Token Requestor Name
— Tag 8B – Token Requestor – Token Service Provider Name

— Ensure readiness for 0100 Token Activation Request and 0120 STIP Advice messages with new TLV data

©2024 Visa. All rights reserved. Visa Confidential 82

Article 3.10
Changes to Token Activation Request Messages to Support Token Requestor Onboarding Information

Optional Technical Changes

— Build logic to identify when a new Token Requestor ID (Tag 03) is received and use the Assigned Date
(Tag 88) to managed TRID lifecycle status
— Reduces issuer decisioning latency and manual flagging of new TRIDs

— Ensure token provisioning risk engines ingest the new tags and dynamically react to unknown / new
TRIDs
— Immediate access to new TRID data enables faster fraud controls or limits for first-time requests

©2024 Visa. All rights reserved. Visa Confidential 83

Article 3.10
Changes to Token Activation Request Messages to Support Token Requestor Onboarding Information

Use Cases
• Use Case 1: Real-Time Provisioning for New Token Requestors [Example Flow]
— Eliminates the delay in enabling tokenization after a new TRID is onboarded
— TR-TSPs can tokenize and provision cards immediately after onboarding – no need to wait for batch
processing

• Use Case 2: Dynamic TRID Risk Scoring

— Previously, unknown TRIDs could be a risk blind spot for issuers
— Aside from relying more on Visa OFAC checks, new fields such as Token Requestor Type (Tag 89) and
Assigned Date (Tag 88) can be used to adjust risk models or apply approval logic based on provider
maturity

©2024 Visa. All rights reserved. Visa Confidential 84

Article 3.10
Changes to Token Activation Request Messages to Support Token Requestor Onboarding Information

Testing and Activation

©2024 Visa. All rights reserved. Visa Confidential 85

Article 3.10
Changes to Token Activation Request Messages to Support Token Requestor Onboarding Information

Frequently Asked Questions

• Question 1: Will this replace offline TRID onboarding reports (e.g. TC33, VAP)?
— No, this enhancement provides partial onboarding data in real time. Offline files are still required to
receive the full TRID profile.
• Question 2: What happens if an issuer receives a Token Activation Request with an unknown TRID?
— Visa recommends not declining these messages as issuers should treat hem as new TRIDs and wait for
onboarding data via real-time TLV tags and offline sources.
• Question 3: Could issuers see provisioning requests from unapproved or misconfigured TRIDs?
— Yes, it is possible during early onboarding stages – especially if a TRID is newly registered or incorrectly
mapped by the TR-TSP. One design proposal is that issuers should treat these as “unknown-new” and
rely on the assigned data and type tags to apply provisioning logic. Full validation can follow once offline
onboarding files arrive.
• Question 4: Is there a risk that the provisioning messages could be spoofed using fake TRID values?
— No. The TRID and associated data are issued and controlled by Visa. The Token Activation Request
message must pass Visa’s validation and routing layers before reaching the issuer. Additionally, the
TRID-to-TSP relationship is authenticated, and any unknown or mismatched values will trigger
monitoring and rejection upstream.
©2024 Visa. All rights reserved. Visa Confidential 86
Article 3.10
Changes to Token Activation Request Messages to Support Token Requestor Onboarding Information

Key Points

• The need to wait for offline reports before provisioning tokens for new TRIDs is being removed as Visa is
enhancing TAR messages to include real-time TRID onboarding data via TLV field 123 (Usage 2)

• Issuers must support new TLV tags: Tag 88, 89, 8A, and 8B across Token Activation Requests and STIP
Advice messages

• Go-Live is October 17th and testing is available and recommended but not mandatory

©2024 Visa. All rights reserved. Visa Confidential 87

Article 3.10
Changes to Token Activation Request Messages to Support Token Requestor Onboarding Information

Resources
• Visa Business News Articles:
— TR-TSP – Merchant Onboarding at the time of Provisioning Request

• Implementation/User Guides
— Visa Merchant Onboarding API

• Other Documentation
— BER Article: 3.10 – Changes to Token Activation Request Messages to Support Token Requestor
Onboarding Information

©2024 Visa. All rights reserved. Visa Confidential 88

©2024 Visa. All rights reserved. Visa Confidential 89
Article 4.3
Changes to Support the
Global Acceptor ID
Framework for Issuers

©2024 Visa. All rights reserved. Visa Confidential 90

Article 4.3
Changes to Support the Global Acceptor ID Framework for Issuers

Key Details

Regional Impact About This Change

Acquirers: Issuers: Testing not required
✓ NO ✓ AP
IMPACT ✓ Canada Testing available
✓ CEMEA Activation not required
✓ Europe
✓ LAC
✓ U.S Effective
1000 GMT 17 October 2025

©2024 Visa. All rights reserved. Visa Confidential 91

Article 4.3
Changes to Support the Global Acceptor ID Framework for Issuers

Business Summary
• Visa introduced Global Acceptor ID
Framework in April 2025
— Improves payments ecosystem
participant visibility
— Enhances data analysis, transactor
identification, and innovation
— Maintains compliance, improves risk
assessment, and ensures correct pricing
— Enhances efficiency and security for
payment acquirers and issuers
— April 2025: Changes to rename
datasets, introduce new tags for
acquirers
— October 2025: Issuers must support
new data elements in transactions

©2024 Visa. All rights reserved. Visa Confidential 92

Article 4.3
Changes to Support the Global Acceptor ID Framework for Issuers

Business Summary
• Benefits

— Enhanced Transaction Visibility: The framework helps improve transaction visibility by providing
detailed data fields for identifying acceptance entities, essential for managing complexity.
— Support for Business Needs and Compliance: It supports future business needs and compliance with
certain local regulations by standardizing acceptor data fields globally, and flexibility for future
requirements.

• Reason Why/ Use Cases

— The framework is designed to provide globally consistent data fields and harmonize global processing
standards for acceptance entity identification. Supporting programs launched in October 2025 BER
such as:
• Article 3.8 Changes to Support the Ramp Provider program
• Article 3.9 Changes to Support Digital Wallets, Marketplaces, Payment Facilitators and Ramp Providers

©2024 Visa. All rights reserved. Visa Confidential 93

Article 4.3
Changes to Support the Global Acceptor ID Framework for Issuers

Optional Technical Changes

• Available fields
• Issuers activated to receive TLV Field 34 and
TLV Field 104, Usage 2: must be prepared to
support receipt of the data with the October
2025 release, data has been withheld from
issuers until that time

IMPORTANT
After endpoints implement support for a TLV field, they must be able to
receive any dataset IDs and tags defined for that field in any order,
including those that they do not recognize or expect. Endpoints may
receive multiple datasets in the same TLV field. Not all defined dataset
IDs are documented in the V.I.P. technical documentation. Endpoints must
ignore any dataset IDs or tags they do not recognize and continue to
process the field

©2024 Visa. All rights reserved. Visa Confidential 94

Article 4.3
Changes to Support the Global Acceptor ID Framework for Issuers

Testing and Activation

• Testing Availability
— Testing is available for Issuers.
— There are no activation requirements

• Testing support
— Issuers may use the Visa Test Portal or VTS-V.I.P. for unattended testing
— Issuers may also conduct attended testing with Visa
— Test script is available
— Available test modes include Direct Connect to Host (VTS-V.I.P. only), and VisaNet Loopback

©2024 Visa. All rights reserved. Visa Confidential 95

Article 4.3
Changes to Support the Global Acceptor ID Framework for Issuers

Frequently Asked Questions

• Are changes to support Global Acceptor ID applicable to all transaction types?
— The Global Acceptor ID changes introduced in April 2025 applied to ATM and POS transactions.
However, as other use cases adopt usage of the framework, certain fields may be enabled for use to
other transaction types including AFTs and OCTs.
• Are changes to support Global Acceptor ID mandatory?
— Usage of these fields are not generally required: framework introduced to enable a globally consistent
set of data fields for use to support business needs
— Issuer usage of the framework and use of certain fields:
— May be required to meet local regulatory requirements
— May be required to participate in specific programs

©2024 Visa. All rights reserved. Visa Confidential 96

Article 4.3
Changes to Support the Global Acceptor ID Framework for Issuers

Key Points
• Global Acceptor ID is available for new use cases
• Increased visibility into specific transactions is increasingly important for ecosystem health
— The changes aim to improve transaction visibility and manage the complexity of the evolving payments
ecosystem. They also support compliance with local regulations and future business needs by providing
a standardized, globally consistent set of data fields for identifying acceptance entities.
• Testing is available, not required
— Issuers that are encouraged to complete testing

©2024 Visa. All rights reserved. Visa Confidential 97

Article 4.3
Changes to Support the Global Acceptor ID Framework for Issuers

Resources
• Visa Business News Articles (Article ID: AI14136):
— Global Acceptor Identification Framework Will Be Introduced
• Visa Access FAQs:
• Global Acceptor Identification FAQs

©2024 Visa. All rights reserved. Visa Confidential 98

©2024 Visa. All rights reserved. Visa Confidential 99
Article 2.8
Changes to Support Non-
Fungible Tokens for Visa
and Interlink

©2024 Visa. All rights reserved. Visa Confidential 100

Article 2.8
Changes to Support Non-Fungible Tokens for Visa and Interlink

Key Details

Regional Impact About This Change

Acquirers: Issuers: Mandatory by Service Participation
✓ AP ✓ AP
✓ Canada ✓ Canada Testing Not Required
✓ CEMEA ✓ CEMEA Activation Not Required
✓ Europe ✓ Europe
✓ LAC ✓ LAC
✓ U.S. ✓ U.S. Effective
1000 GMT 17 October / CPD 18 October 2025

©2024 Visa. All rights reserved. Visa Confidential 101

Article 2.8
Changes to Support Non-Fungible Tokens for Visa and Interlink

Summary
Visa believes that digital currencies will contribute to innovations and options for the future of financial services and money
movement and continues to pursue capabilities and services that allow Visa to serve as the bridge between the digital
currency ecosystem and its network of clients, customers, and merchants around the world.

Effective with the April 2024 and October 2024 release, Visa Rules were updated to enhance digital currency acceptance and
non-fungible token (NFT) policies, update dispute rules & launch the new Ramp Provider Program for all regions.

Effective with the April 2025 release, Visa introduced: New transaction indicators to increase transparency for digital
currency acceptance and with the October 2025 release Visa is introducing the changes to support the identification of non-
fungible tokens (NFTs).

These updates allow Visa to enable new partners to access its ecosystem safely and more seamlessly and at the same time,
provide enhanced transparency for consumer protection, oversight, and risk management.

©2024 Visa. All rights reserved. Visa Confidential 102

Article 2.8
Changes to Support Non-Fungible Tokens for Visa and Interlink

Benefits
To improve transparency in digital currency transactions, Visa implemented new identifiers for distinct types of digital assets
in the V.I.P. System and BASE II as part of Apr 25 BER. Currently, Visa uses a broad "cryptocurrency“ indicator, with the Apr
2025 BER the system includes specific values that identify the type of digital currency or coin involved. These values
categorize transactions as:
• Central Bank Digital Currency (CBDC) &/or tokenized deposits (Apr 25 BER)
• Stablecoins categorized as fiat-backed (Apr 25 BER)
• Blockchain native tokens or coins (e.g., Bitcoin, Ethereum, Solana) (Apr 25 BER)
• Non-Fungible Tokens (NFTs) (Oct 25 BER)

If the specific type of digital currency cannot be determined at the time of the transaction or does not fit into the new
categories, the existing "cryptocurrency" indicator will continue to be used. This enhancement aims to provide clients with
greater clarity and insight into their digital currency transactions.

Issuers or their processors that are capable of receiving the existing Special Condition Indicator field will receive the new
values in the same field within both the authorization request and the clearing record.

©2024 Visa. All rights reserved. Visa Confidential 103

Article 2.8
Changes to Support Non-Fungible Tokens for Visa and Interlink cont’d…

Benefits
Ramp Providers are third party agents (TPAs) that provide payment services to convert transactions from a fiat currency
(e.g., USD, GBP, EUR) to a non-fiat currency (e.g., Bitcoin [BTC], Ethereum [ETH]), or vice versa.

They support a wide variety of cryptocurrency clients and may sell non-fiat currency to holders directly or provide their
services under a contract to conversion affiliates. Examples of conversion affiliates include third-party cryptocurrency
exchanges or NFT marketplaces. Over time conversion affiliates may include so-called regular retail merchants that want to
sell products / services denominated in a digital currency.

The new program replicates elements of Visa’s existing payment facilitator (PF) requirements but also includes elements
specific to digital currency transactions.

Under the new program rules, ramp providers must be registered as TPAs and as High-Integrity Risk (HIR) merchants by their
acquirers. If the ramp provider supports a conversion affiliate that Visa qualifies as HIR, the conversion affiliate must also be
registered as an HIR merchant (e.g., if the ramp provider processes transactions for a conversion affiliate that conducts
online gambling).

©2024 Visa. All rights reserved. Visa Confidential 104

Article 2.8
Changes to Support Non-Fungible Tokens for Visa and Interlink

Impact Considerations
Acquirer Impact
• Acquirers that support merchants involved in the purchase of digital currencies or NFTs, or support Ramp Providers,
must support the changes described in Article 3.4, Requirements to Support Digital Currency Transactions for Visa and
Interlink (Apr25 BER) and Article 2.8 Changes to Support Non-Fungible Tokens for Visa and Interlink (Oct 25 BER)
• Acquirers that support transactions through non-Visa branded cards through the Interlink network must support the
changes described in this article for merchants involved in the purchase of digital currencies, NFTs, quasi-cash
transactions, or payments on existing debt.
• Testing is not required to implement this enhancement.
Issuer Impact
• Issuers that support digital currency must support the changes described in Article 3.4, Requirements to Support
Digital Currency Transactions for Visa and Interlink (Apr 25 BER) and Article 2.8 Changes to Support Non-Fungible
Tokens for Visa and Interlink (Oct 25 BER)
• Interlink issuers that support digital currency, quasi-cash or payment on debt transactions must support the changes
described in this article.
• Testing is not required to implement this enhancement.

©2024 Visa. All rights reserved. Visa Confidential 105

Article 2.8
Changes to Support Non-Fungible Tokens for Visa and Interlink
V.I.P. Changes to Support Non-Fungible Tokens
• V.I.P implemented new values in Field 60—Additional POS Information, position 4, Special Condition Indicator and Field
63.6—Chargeback Reduction/BASE II Flags, position 7, Special Condition Indicator, Merchant Transaction. These values
represent three types of digital currencies as part of Apr 25 BER, and a non-fungible token (NFT) as part of Oct 25 BER.
Processing Code must contain value of "00" (Goods/service purchase-debit)
• V.I.P. will implement changes to allow Interlink non-Visa branded card-not-present transactions to be included in the
purchase of digital currency, NFTs, quasi-cash, and payment on existing debt.
• The following table shows a new NFT transaction identifier, as well as the existing values in Field 60—Additional POS
Information, position 4, Special Condition Indicator.

©2024 Visa. All rights reserved. Visa Confidential 106

Article 2.8
Changes to Support Non-Fungible Tokens for Visa and Interlink
V.I.P. Changes to Support the Non-Fungible Tokens
• The following table shows the new NFT transaction identifier, as well as the existing values in Field 63.6—Chargeback
Reduction/BASE II Flags, position 7, Special Condition Indicator, Merchant Transaction.

• An NFT transaction is a purchase transaction and should be marked with a value of “00” in the processing code.

©2024 Visa. All rights reserved. Visa Confidential 107

Article 2.8
Changes to Support Non-Fungible Tokens for Visa and Interlink

BASE II Changes to Support the Digital Currencies

• BASE II has already implemented changes to support three values for digital currencies and a new value for NFT
transactions will be implemented in Oct 25. The digital currencies and new NFT value will be defined in TCR 1—Additional
Data, positions 74–75, Special Condition Indicator.
• BASE II will process the Special Condition Indicator with a new value of "4" as a purchase transaction.
• The following table shows the values for digital currencies and NFT transactions.

©2024 Visa. All rights reserved. Visa Confidential 108

Article 2.8
Changes to Support Non-Fungible Tokens for Visa and Interlink

Testing availability and requirements

©2024 Visa. All rights reserved. Visa Confidential 109

Article 2.8
Changes to Support Non-Fungible Tokens for Visa and Interlink

Frequently Asked Questions

Why are these changes being made?
Visa wants to ensure there is a consistent, “best in class” user experience for customers who choose to pay with Visa for
digital currency or NFT purchases. To give clients greater insight into digital currency transactions, the existing special
condition “cryptocurrency” indicator field will be expanded to include new values to identify what type of digital currency /
coin is being acquired (when known at the time of the transaction) or if an NFT was purchased.

What is a Ramp Provider?

Visa defines a Ramp Provider as a Third-Party Agent that provides payment services to convert Transactions from a fiat
currency to a non-fiat currency (for example: cryptocurrency), or vice versa. Ramp Providers may sell non-fiat currency to
Cardholders directly or provide their services under a contract to Affiliates (Seller). They are similar to Payment Facilitators
but are specific to digital currency transactions.

What is a Conversion Affiliate (“Affiliate”)?

Visa defines a Conversion Affiliate (“Affiliate”) as a third-party entity that is contracted to a Ramp Provider to provide
payment services to convert transactions from a fiat currency to a non-fiat currency (for example: cryptocurrency), or vice
versa. Affiliates of Ramp Providers include but are not limited to retailers, cryptocurrency exchanges or NFT marketplaces

©2024 Visa. All rights reserved. Visa Confidential 110

Article 2.8
Changes to Support Non-Fungible Tokens for Visa and Interlink

Resources
Visa Business News Articles
• AI13956 - “Interlink Rules Update to Enhance Digital Currency and Non-Fungible Token Acceptance Policies and Launch
New Ramp Provider Program,” Visa Business News, 21 March 2024 (Canada, U.S., U.S. territories only)

• AI13955 - “Details for Visa’s Ramp Provider Program for the Interlink Network,” Visa Business News, 21 March 2024 (Canada,
U.S., U.S. territories clients only)

• AI14715 - “Ramp Provider Program Update and FAQs,” Visa Business News, 21 November 2024

• AI13573 - “Rules Update to Enhance Digital Currency and Non-Fungible Token Acceptance Policies and Launch New
Ramp Provider Program,” Visa Business News, 21 December 2023

• Digital Currencies Transactions Guide - Ramp Provider Program Requirements (PDF) - Overview of enhancements being
made to Visa's Digital Currency Acceptance Framework

• Digital Currencies and NFTs - Visa Access Homepage

©2024 Visa. All rights reserved. Visa Confidential 111

©2024 Visa. All rights reserved. Visa Confidential 112
Article 2.13
Changes to Spend
Qualified Indicator
Processing

©2024 Visa. All rights reserved. Visa Confidential 113

Article 2.13
Changes to Spend Qualified Indicator Processing

Key Details

Regional Impact About This Change

Acquirers: Issuers: Mandatory
✓ AP ✓ AP
✓ Canada ✓ Canada Testing Not Available
✓ CEMEA ✓ CEMEA Activation Not Required
✓ Europe ✓ Europe
✓ LAC ✓ LAC
✓ U.S. ✓ U.S. Effective
10:00 GMT 17 October 2025 CPD 18 October 2025

©2024 Visa. All rights reserved. Visa Confidential 114

Article 2.13
Changes to Spend Qualified Indicator Processing

Business Summary
• Product Strategy
- Visa aims to enhance its spending qualification capabilities and facilitate the future introduction of more
advanced spend qualified product frameworks.
- By adding new spend qualified indicator values to the existing ones, Visa will be able to launch new spend
qualified products into the market.
• Reason Why
- The significance of spend qualification is growing, as it is essential for maintaining the relevance and
effectiveness of products introduced to the market.
- Emphasizing the amount of spend through a card will play a crucial role in influencing the economics of
the product.
- This initiative seeks to improve the overall quality of Visa’s portfolios and drive Purchase Volume (PV).
• Benefits
- Issuers and Acquirers will gain complete visibility into the economics of transactions. The newly
introduced spend qualified indicator values can be utilized in Interchange Reimbursement Fee (IRF)
programs in some markets, similar to the existing values.
©2024 Visa. All rights reserved. Visa Confidential 115
Article 2.13
Changes to Spend Qualified Indicator Processing

New and Existing Spend Qualified Indicators

existing value B Base Visa is introducing new spend qualified indicator values for future
use.
J Not Qualified Tier 5
These values will be systematically assigned to transactions for
K Not Qualified Tier 4 cards that qualify for spend assessment and meet a spend
threshold that will be determined in the future.
L Not Qualified Tier 3
The new values will be incorporated into the following:
M Not Qualified Tier 2
•V.I.P. Field 62.25—Spend Qualified Indicator
existing value N Not Qualified •BASE II Draft Data, TCR 5—Payment Service Data, position 149,
existing value Q Qualified Spend Qualified Indicator
•BASE II TC 04—Reclassification Advice, TCR 9, position 41, Settled
R Qualified Tier 2 Spend Qualified Indicator
S Qualified Tier 3
T Qualified Tier 4 Acquirers and Issuers that receive the Spend Qualified Indicator
field in V.I.P. are required to support these new values for future
U Qualified Tier 5 use.
V Qualified Tier 6 Acquirers should be informed about the new spend qualified
indicator values that Visa will transmit in the BASE II Draft Data for
W Qualified Tier 7 dispute transactions and reclassification advice moving forward.
Tiers 1-5 (Visa Business Credit cards in
1-5 Puerto Rico and U.S. only) Issuers need to be aware of the new spend qualified indicator
values that Visa will send in the BASE II Draft Data record for original
Note: New products/values should be called out in bolded red
transactions and their representments in the future.
©2024 Visa. All rights reserved. Visa Confidential 116
Article 2.13
Changes to Spend Qualified Indicator Processing
Use Cases
In the future, use cases will be defined for each market separately, encompassing the following:
— Spend-driven IRF structure for a Product ID
— Multi-tier spend qualification
Market A Market B Market C
Domestic

Impacted IRF
Intra

Inter

Applied IRF rates

Domestic Intra Inter Domestic Intra Inter Domestic Intra Inter

Tier 1 A A A A A A A A A

Tier 2 B A A B B B A A B
Configurable
periodic spend Tier 3 C A A C C C A A C
assessment
• Distribute card across
tiers based on spend
Tier 10 D A A D D D A A D
©2024 Visa. All rights reserved. Visa Confidential 117
Article 2.13
Changes to Spend Qualified Indicator Processing

Testing and Activation

• Activation is not required
• Testing is not available

©2024 Visa. All rights reserved. Visa Confidential 118

Article 2.13
Changes to Spend Qualified Indicator Processing

Frequently Asked Questions

• Will the new spend qualified indicator values be applied immediately?
— No, the article introduces new values which may be used in the future. The newly introduced spend
qualified indicator values can be utilized in Interchange Reimbursement Fee (IRF) programs in some
markets, similar to the existing values. Details of such programs will be announced in future
communications.

©2024 Visa. All rights reserved. Visa Confidential 119

©2024 Visa. All rights reserved. Visa Confidential 120
Article 3.8
Changes to Support the
Ramp Provider Program

©2024 Visa. All rights reserved. Visa Confidential 121

Article 3.8
Changes to Support the Ramp Provider Program

Key Details

Regional Impact About This Change

Acquirers: Issuers: Mandatory by Service Participation
✓ AP ✓ AP
✓ Canada ✓ Canada Testing Not Required
✓ CEMEA ✓ CEMEA Activation Not Required
✓ Europe ✓ Europe
✓ LAC ✓ LAC
✓ U.S. ✓ U.S. Effective
1000 GMT 17 October / CPD 18 October 2025

©2024 Visa. All rights reserved. Visa Confidential 122

Article 3.8
Changes to Support the Ramp Provider Program

Summary
To support ramp providers, prospective ramp providers and acquirers with a framework to operate in the Visa network, Visa
has launched the Ramp Provider Program.
As part of the Ramp Provider Program, new identifiers will be implemented for participants to track overall activity and
program participation. Acquirers must ensure that ramp providers include the new values and identifiers in all applicable
transactions.
Effective with the April 2024 and October 2024 release, Visa Rules were updated to enhance digital currency acceptance and
non-fungible token (NFT) policies, update dispute rules & launch the new Ramp Provider Program for all regions. These
updates allow Visa to enable new partners to access its ecosystem safely and more seamlessly and, at the same time,
provide enhanced transparency for consumer protection, oversight, and risk management.
Visa believes that digital currencies will contribute to innovations and options for the future of financial services and money
movement and continues to pursue capabilities and services that allow Visa to serve as the bridge between the digital
currency ecosystem and its network of clients, customers, and merchants around the world

©2024 Visa. All rights reserved. Visa Confidential 123

Article 3.8
Changes to Support the Ramp Provider Program

Benefits
Ramp Providers are third party agents (TPAs) that provide payment services to convert transactions from a fiat currency
(e.g., USD, GBP, EUR) to a non-fiat currency (e.g., Bitcoin [BTC], Ethereum [ETH]), or vice versa.

They support a wide variety of cryptocurrency clients and may sell non-fiat currency to holders directly or provide their
services under a contract to conversion affiliates. Examples of conversion affiliates include but are not limited to
cryptocurrency exchanges or NFT marketplaces, conversion affiliates may also include so-called regular retail merchants
that want to sell products / services denominated in a digital currency.

The new program replicates elements of Visa’s existing payment facilitator (PF) requirements but also includes elements
specific to digital currency transactions.

Under the new program rules, ramp providers must be registered as TPAs and as High-Integrity Risk (HIR) merchants by their
acquirers. If the ramp provider supports a conversion affiliate that Visa qualifies as HIR, the conversion affiliate must also be
registered as an HIR merchant (e.g., if the ramp provider processes transactions for a conversion affiliate that conducts
online gambling).

The new identifiers will enable tracking of program participants, including identifying whether conversion affiliates are
located in the same country as the Ramp Provider, or not.

©2024 Visa. All rights reserved. Visa Confidential 124

Article 3.8
Changes to Support the Ramp Provider Program

Impact Considerations
Acquirer Impact
• Acquirers with registered and qualified ramp providers must send their ramp provider’s data in the existing V.I.P fields
and BASE II as described in the Article 3.8 Changes to Support the Ramp Provider Program
• Testing is not required to implement this enhancement.

Issuer Impact
• V.I.P Issuers that support the existing transaction specific data field must be prepared to receive the new values as
described in the Article 3.8 Changes to Support the Ramp Provider Program.
• BASE II Issuers that receive the Supplemental Payment Data record must be prepared to receive the ramp provider
data.
• Testing is not required to implement this enhancement.

©2024 Visa. All rights reserved. Visa Confidential 125

Article 3.8
Changes to Support the Ramp Provider Program

V.I.P. Changes to Support Ramp Providers

• Acquirers that support ramp providers must provide the eight-digit ID for their Ramp provider in existing Tag 86- Ramp
Provider ID, in TLV format Field 104, Usage 2- Transaction-Specific Data, Dataset ID 56—Additional Acceptance Data in
the request message for Visa and Interlink transactions.

• To support the location of the Ramp provider for Visa transactions – Add new values in existing Tag 04- Foreign Retailer
Indicator, in TLV format Field 104, Usage 2 - Transaction-Specific Data, Dataset ID 56—Additional Acceptance Data

• To support the location of the Ramp provider for Interlink transactions – Enable Tag 04 to existing TLV field 104 Usage 2-
Transaction-Specific Data, Dataset ID 56—Additional Acceptance Data

• The following table shows the new values and value descriptions for existing Tag 04 – Foreign Retailer Indicator in TLV
Filed 104, Usage 2, Data ID 56. The length will change from a fixed 3-byte length to a variable length up to 3 bytes.

©2024 Visa. All rights reserved. Visa Confidential 126

Article 3.8
Changes to Support the Ramp Provider Program

BASE II Changes to Support Ramp Providers

• BASE II will use following new and existing fields “TCR E- Supplemental Payment Data” for the new Ramp provider's
information. Acquirers must enter the ramp provider ID in the Ramp Provider ID field and indicate if the ramp provider
and its Conversion Affiliate are located in the same or different countries in the Foreign Retailer Indicator field.

©2024 Visa. All rights reserved. Visa Confidential 127

Article 3.8
Changes to Support the Ramp Provider Program

Testing availability and requirements

©2024 Visa. All rights reserved. Visa Confidential 128

Article 3.8
Changes to Support the Ramp Provider Program

Frequently Asked Questions

What is a Ramp Provider?
Visa defines a Ramp Provider as a Third-Party Agent that provides payment services to convert Transactions from a fiat
currency to a non-fiat currency (for example: cryptocurrency), or vice versa. Ramp Providers may sell non-fiat currency to
Cardholders directly or provide their services under a contract to Affiliates (Seller). They are similar to Payment Facilitators
but are specific to digital currency transactions.

What is a Conversion Affiliate (“Affiliate”)?

Visa defines a Conversion Affiliate (“Affiliate”) as a third-party entity that is contracted to a Ramp Provider to provide
payment services to convert transactions from a fiat currency to a non-fiat currency (for example: cryptocurrency), or vice
versa. Affiliates of Ramp Providers include but are not limited to retailers, cryptocurrency exchanges or NFT marketplaces.

Do Ramp Providers need to be registered with Visa?

Yes, ramp providers must be registered in Visa’s TPA registration tool. Program Request Management (PRM) available on
Visa Access (formerly Visa Online). Acquirers can register their ramp providers, or ramp providers can use the self-service
tool to register on behalf of their acquirer partner(s).

©2024 Visa. All rights reserved. Visa Confidential 129

Article 3.8
On-Ramp Provider Use Case Consumer Experience

©2024 Visa. All rights reserved. Visa Confidential 130

Article 3.8
Changes to Support the Ramp Provider Program

Resources
Visa Business News Articles
• AI13956 - “Interlink Rules Update to Enhance Digital Currency and Non-Fungible Token Acceptance Policies and Launch
New Ramp Provider Program,” Visa Business News, 21 March 2024 (Canada, U.S., U.S. territories only)

• AI13955 - “Details for Visa’s Ramp Provider Program for the Interlink Network,” Visa Business News, 21 March 2024 (Canada,
U.S., U.S. territories clients only)

• AI14715 - “Ramp Provider Program Update and FAQs,” Visa Business News, 21 November 2024

• AI13573 - “Rules Update to Enhance Digital Currency and Non-Fungible Token Acceptance Policies and Launch New
Ramp Provider Program,” Visa Business News, 21 December 2023

• AI14989 - “Ramp Provider Program Updates,” Visa Business News, 27 February 2025

©2024 Visa. All rights reserved. Visa Confidential 131

©2024 Visa. All rights reserved. Visa Confidential 132
Article 4.5
Changes to Increase the
Maximum Single
Transaction Amount Limits

©2024 Visa. All rights reserved. Visa Confidential 133

Article 4.5
Changes to Increase the Maximum Single Transaction Amount Limits

Key Details

Regional Impact About This Change

Acquirers: Issuers: Available
✓ AP ✓ AP
✓ Canada ✓ Canada Testing Available
✓ CEMEA ✓ CEMEA Activation Not Required
✓ Europe ✓ Europe
✓ LAC ✓ LAC
✓ U.S. ✓ U.S. Effective
1000 GMT 18 July / CPD 19 July 2025

©2024 Visa. All rights reserved. Visa Confidential 134

Article 4.5
Changes to Increase the Maximum Single Transaction Amount Limits

Business Summary
• Product Strategy
— By increasing the maximum single purchase
transaction amount limits for Visa Credit and
Debit cards, Visa aims to enable issuers to better
support affluent cardholders who frequently
engage in large-ticket transactions. This change
is intended to reduce friction in the payment
experience for acquirers and merchants that
handle common large-ticket transactions,
thereby improving the overall payment
experience for affluent cardholders.
— Raised limits may vary by issuer and market, and
issuers and acquirers must continue to adhere to
local transaction processing requirements,
including but not limited to National Net
Settlement Service (NNSS) requirements.

©2024 Visa. All rights reserved. Visa Confidential 135

Article 4.5
Changes to Increase the Maximum Single Transaction Amount Limits

Optional Technical Changes

• Visa will increase the maximum single transaction Card Global Product Existing Credit New Credit and
amount limits in VisaNet for purchase and credit Product Name and Debit POS Debit POS
ID Maximum Single Maximum Single
voucher transactions for certain consumer and Transaction Transaction
commercial products for all countries and Amount Limit Amount Limit
jurisdictions except Turkey. A^ Visa Traditional US $249,999.99 US $749,999.99
B^ Visa Traditional US $249,999.99 US $749,999.99
• VisaNet will continue to decline attempted
Rewards
transactions over the maximum single transaction
C^ Visa Signature US $749,999.99 US $1,499,999.99
amount limits with existing response code 13
D^ Visa Signature US $999,999.99 US $1,999,999.99
(Invalid amount) in the existing Field 39 –
Preferred
Response Code
F^ Visa Classic US $249,999.99 US $749,999.99
• Cash, Quasi-cash, AFT, OCT, Prepaid purchase, G^ Visa Business US $749,999.99 US $1,999,999.99
and non-Visa product purchase transaction limits G1 Visa Signature US $749,999.99 US $1,499,999.99
remain unchanged Business
G3 Visa Business US $749,999.99 US $1,499,999.99
Enhanced/ Visa
Platinum
Business

For U.S.-issued cards, the globally applicable existing maximum single transaction amount limit for
©2024 Visa. All rights reserved. Visa Confidential 136
purchase and credit voucher transactions is US$1,499,999.99.
Article 4.5
Changes to Increase the Maximum Single Transaction Amount Limits

Optional Technical Changes Continued

Card Global Product Existing Credit New Credit and Card Global Product Existing Credit New Credit and
Product Name and Debit POS Debit POS Product Name and Debit POS Debit POS
ID Maximum Single Maximum Single ID Maximum Single Maximum Single
Transaction Transaction Transaction Transaction
Amount Limit Amount Limit Amount Limit Amount Limit
G4 Visa Infinite US $1,499,999.99 US $1,999,999.99 N^ Visa Platinum US $249,999.99 US $749,999.99
Business
G5 Visa Business US $749,999.99 US $1,499,999.99 N1 Visa Rewards US $249,999.99 US $749,999.99
Rewards
N2 Visa Select US $249,999.99 US $749,999.99
I^ Visa Infinite US $999,999.99 US $1,999,999.99
I1 Visa Infinite US $1,499,999.99 US $2,999,999.99 P^ Visa Gold US $249,999.99 US $749,999.99
Privilege
S^ Visa Purchasing US $749,999.99 US $2,999,999.99
I2 Visa Ultra High US $1,499,999.99 US $2,999,999.99
Net Worth S1 Visa Purchasing US $749,999.99 US $2,999,999.99
(UHNW) with Fleet
K^ Visa Corporate US $749,999.99 US $2,999,999.99 S2 Visa Government US $749,999.99 US $2,999,999.99
T&E Purchasing
K1 Visa Government US $749,999.99 US $2,999,999.99 S3 Visa Government US $749,999.99 US $2,999,999.99
Corporate T&E Purchasing with
L^ Visa Electron US $249,999.99 US $749,999.99 Fleet
©2024 Visa. All rights reserved. Visa Confidential 137
For U.S.-issued cards, the globally applicable existing maximum single transaction amount limit for
purchase and credit voucher transactions is US$1,499,999.99.
Article 4.5
Changes to Increase the Maximum Single Transaction Amount Limits

Optional Technical Changes Continued

Card Global Product Existing Credit New Credit and
Product Name and Debit POS Debit POS
ID Maximum Single Maximum Single
Transaction Transaction
Amount Limit Amount Limit

S4 Visa Commercial US $749,999.99 US $2,999,999.99

Agriculture

S5 Visa Commercial US $749,999.99 US $2,999,999.99

Transport

S6 Visa Commercial US $749,999.99 US $2,999,999.99

Marketplace

X^ Visa Commercial US $749,999.99 US $2,999,999.99

Choice Travel

X1 Visa Commercial US $749,999.99 US $2,999,999.99

Choice Omni

For U.S.-issued cards, the globally applicable existing maximum single transaction amount limit for
©2024 Visa. All rights reserved. Visa Confidential 138
purchase and credit voucher transactions is US$1,499,999.99.
Article 4.5
Changes to Increase the Maximum Single Transaction Amount Limits

Testing and Activation

• Testing is NOT required
• The following table summarizes the testing availability and requirements for this enhancement.

©2024 Visa. All rights reserved. Visa Confidential 139

Article 4.5
Changes to Increase the Maximum Single Transaction Amount Limits

Frequently Asked Questions

• Are endpoints required to adhere to these limits?
— Endpoints are not required to apply the new limits. Visa will not override existing higher or lower limits
set in VisaNet for the particular endpoints.

• What happens if a transaction is sent over the new limit?

— Same as today, VisaNet will decline any transaction over the limit with response code 13 – Invalid
transaction amount.

• What transaction types are impacted?

— Purchase and Credit Voucher transactions on certain credit and debit Visa products will have increased
limits. There will be NO change in limits for Prepaid, Cash, Quasi-cash, AFT, and OCT transactions.

©2024 Visa. All rights reserved. Visa Confidential 140

©2024 Visa. All rights reserved. Visa Confidential 141
Closing Remarks

©2024 Visa. All rights reserved. Visa Confidential 142

Business Enhancements Release Reminders

Return your GTAQ (Global Testing Oct. 2025 and Jan. 2026 Version Ensure you install your Edit
& Activation Questionnaire) 3.0 GTLIG will be published Package BIN/ARDEF Tables prior
as early as possible mid Oct. 2025 to CPD 17 Oct. 2025
Deadline: 15 Aug. 2025

Utilize VTS-VIP/ Questions on testing can be Presentation materials are

VTS-VCMS/VTP for self testing sent to itest@visa.com available on VOL

For all BER support, please contact your Visa Client Success Managers

©2024 Visa. All rights reserved. Visa Confidential 143

©2024 Visa. All rights reserved. Visa Confidential 144