Clarifications and Amplifications

The following table provides corrections, clarifications and updates to articles that appear in the October 2022 and January
2023 VisaNet Business Enhancements Global Technical Letter and Implementation Guide, Effective: 8 September 2022.
Clients are encouraged to review this table to ensure all updates are included in release planning.

Article
Date Published Article Name Updated Information
No.

27 October 2022 4.4 Introduction of the New This article announced the requirements, processing rules
Payment Message and message formats for the new Payment Message
Augmentation Service Augmentation Service. Visa is clarifying the following
requirements for the new service:
• A separate project is required to support the implementation,
including testing, to support the new Payment Message
Augmentation Service. Contact your regional client support
representative for additional information.

• Existing V.I.P. System Full Service acquirers that choose to

participate in the new Payment Message Augmentation
Service must modify their existing processor control
record (PCR) to support the service.

• Acquirer processors must be aware that authorization,

0220 Deferred clearing advice, 0220 Merchandise return
and 0400 / 0420 Reversal messages using the new
Payment Message Augmentation Service must contain
the same acquirer identifier in Field 32—Acquiring
Institution Identification Code in both the approved
authorization and 0220 / 0400 / 0420 request messages.

• V.I.P. System Authorization Only acquirer processors

connected to BASE II that choose to participate in the
new Payment Message Augmentation Service must
request a new V.I.P. System Full Service PCR and acquiring
identifier to support the new service.

• For 0220 Deferred clearing advice or 0220 Merchandise

return messages that will be processed by the V.I.P.
System with existing response code 76 (No matching
original transaction found) in Field 39—Response Code
with the new service, the V.I.P. System will send the
following reduced number of existing fields in the 0230
response message to the acquirer:

o Field 3—Processing Code

o Field 15—Date, Settlement

o Field 25—Point-of-Service Condition Code

o Field 39—Response Code

o Field 44.1—Response Source / Reason Code

o Field 62—Custom Payment Service Fields (Bitmap Format)

Visa Confidential
 o Field 62.2—Transaction Identifier (Bitmap Format)

o Field 63.1—Network Identification Code

• For 0400 / 0420 Full financial reversal messages that will be

processed by the V.I.P. System with existing response
code 76 (No matching original transaction found) in Field
39—Response Code with the new service, the V.I.P. System
will send the following reduced number of existing fields in
the 0410 / 0430 response message to the acquirer:

o Field 3—Processing Code

o Field 15—Date, Settlement

o Field 25—Point-of-Service Condition Code

o Field 39—Response Code

o Field 44.1—Response Source / Reason Code

o Field 62—Custom Payment Service Fields (Bitmap Format)

o Field 62.2—Transaction Identifier (Bitmap Format)

o Field 63.1—Network Identification Code

o Field 90—Original Data Elements

Note: There is no PDF attached to this article.

15 October 2022 2.9 Changes to Private Label
Products
2.11 Changes to Visa B2B Virtual
Payments Program Products
Transaction Processing
Visa is updating the field positions in the SMS Raw Data and
Reports row in the Implementation Summary table for each
article. The V22261 and V23210 records in Article 2.9 and
Article 11.3.2 now contain the Reimbursement Fee amount
in positions 7-21. Additionally, the V22261 record in Article
2.11 and Article 2.14 now contains the B2B Program ID in
positions 55-56.

2.14 For more information about the changes to the SMS Raw
New Visa Flexible Rate B2B
Data, acquirers and issuers are encouraged to review Article
Virtual Program Products
3.12—Changes to SMS Raw Data, or to contact their
regional client support representative.
11.3.2 Changes to Visa ReadyLink
Note: There is no PDF attached to this article.
Products

13 October 2022 9.1.1 Changes to Usage of SCA This article previously announced that original credit
Exemption Indicators and transactions (OCTs) are impacted by strong customer
Visa Delegated authentication (SCA) changes as indicated in the Processing
Authentication Processing Impact table of the article. Visa is clarifying that effective
immediately, OCTs are not impacted by the SCA changes.

Note: There is no PDF attached to this article.

13 October 2022 2.8 New Charge Types for Non- Visa is notifying acquirers that the Non-Domestic Settlement
Domestic and Multi-Currency Charge type, as shown in Table 2.8.A, and the Multi-
Settlement Charges Currency Settlement Charge Type, as shown in table 2.8.C,
will now be implemented effective 1000 GMT 4 November
2022 / Central Processing Date (CPD) 5 November 2022.
Additionally, acquirers must be aware that automatic billing
will also be effective with the new implementation date of
4 November / CPD 5 November 2022.

Acquirers are encouraged to review the Visa Business News

publications mentioned in the article “New Charge Types for

Visa Confidential
 Non-Domestic and Multi-Currency Settlement Charges” if
their respective region is currently being billed outside the
automated billing structure, as this process will continue
until the above new effective implementation date.
Additionally, acquirers can contact their regional client
support representative for more information.

There is no change to the implementation date or the

automatic billing schedule effective date for issuers.

Note: There is no PDF attached to this article.

6 October 2022 2.13 Changes to the Fraud This article has been updated to clarify that the following
Reporting System fields are being added to the Edit Package EP-740—Fraud
Advice report:

• Fraud Reporting Entity

• Fraud Type Classification

• Processing Code

Note: There is no PDF attached to this article.

4 October 2022 9.1.3 Requirements to Support This announcement originally appeared in the 29 September
Account Funding 2022 edition of the Visa Business News. It has been republished
Transactions in the Europe to add an additional required tag, Tag 02—Sender Account
Region Number. Please use this version going forward.

This article has been updated to defer the processing rules

for European Economic Area (EEA) countries, the UK and
Gibraltar until 1000 GMT 20 January 2023. The processing
rules state that the V.I.P. System will:

• Reject the transaction with existing reject code 0494

(Field or data missing or invalid) if Field 104, Usage 2—
Transaction-Specific Data in TLV format, Dataset ID 5F—
Sender Data is missing or invalid, or all of the following
required tags are missing:

o Tag 02—Sender Account Number

o Tag 03—Sender Name

o Tag 04—Sender Address

o Tag 05—Sender City

o Tag 06—Sender State

o Tag 07—Sender Country

o Tag 0A—Recipient Name

• Decline the transaction with existing response code 64

(Transaction does not fulfill AML requirement)1 in Field
39—Response Code if TLV Field 104, Usage 2, Dataset ID
5F, and one of the following required tags is missing:

o Tag 02

o Tag 03

o Tag 04

o Tag 05

Visa Confidential

27 September 2022 2.11 Changes to Visa B2B Virtual
2.14 Payments Program Products
Transaction Processing
New Visa Flexible Rate B2B
Virtual Program Products
19 September 2022 3.8 Changes to CAVV Processing
15 September 2022 2.13 Changes to the Fraud
Reporting System
Visa Confidential
o Tag 06
o Tag 07
o Tag 0A
Until 1000 GMT 20 January 2023, the V.I.P. System will
process the transaction without rejecting or declining a
domestic or intra-EEA jurisdiction account funding
transaction (AFT) sent from and destined to countries in the
EEA, the UK and Gibraltar regardless of whether the data in
TLV Field 104, Usage 2, Dataset ID 5F is missing or invalid.
Effective 1000 GMT 20 January 2023, the V.I.P. System will
reject or decline those transactions if the requirements
stated in this article are not met.
Note: The processing rules for international jurisdiction
AFTs for the EEA, the UK and Gibraltar are existing.
Note: There is no PDF attached to this article.
1
Anti-money laundering (AML)
Effective 18 October 2022, Visa will provide VisaNet
Certification Management Service (VCMS) Responder IDs
and account ranges for acquirers to test the Visa B2B Virtual
Payments Program products and Visa Flexible Rate B2B
Virtual Program products. Acquirers should contact their
client service representatives for the new VCMS Responder
IDs and account ranges.
Visa is also clarifying that issuers will not issue products with
the new program IDs prior to January 2023.
Note: There is no PDF attached to this article.
This article previously announced that the V.I.P. System will return
the value of 8 (CAVV passed verification-attempted authentication)
in Field 44.13—CAVV Results Code for successful validation of
electronic commerce indicator (ECI) 07 (Non-authenticated
security transaction) or 7 (Non-authenticated security
transaction) transactions with a delegated trusted authentication
Cardholder Authentication Verification Value (CAVV).
Visa is clarifying that ECI 07 or 7 transactions with a delegated
trusted authentication CAVV will be validated by the V.I.P. System
and will return the value of B (CAVV passed verification-
attempted authentication, no liability shift) instead of 8 in Field
44.13 when the delegated trusted authentication CAVV passes
validation. Only the V.I.P. System is allowed to generate the value
of B. There are no changes to the published CAVV result code for
processing of a failed delegated trusted authentication CAVV.
Note: There is no PDF attached to this article.
Visa is notifying acquirers and issuers that the requirement
to submit fraud advices for fraud that occurs in original
credit transactions (OCTs) will now be effective with the
April 2023 Business Enhancements release.
 The changes to the Fraud Reporting System (FRS) described
in Article 2.13 will still be implemented with the October
2022 Business Enhancements release.

Acquirers and issuers may optionally report fraud on OCTs

and receive the reporting beginning with the October 2022
release. Acquirers and issuers must make system changes to
support submitting this data by April 2023.

Note: There is no PDF attached to this article.

12 September 2022 3.15 Changes to the Authorization Visa is notifying acquirers that the Changes to Support Account
Gateway Service for Funding Transactions section that was published in the October
Mastercard POS Transactions 2022 and January 2023 VisaNet Business Enhancements Global
Technical Letter and Implementation Guide, Effective: 16 June
2022 was not included in the October 2022 and January 2023
VisaNet Business Enhancements Global Technical Letter and
Implementation Guide, Effective: 8 September 2022. This section
will be re-introduced with the October 2022 VisaNet
Business Enhancements release.

Changes to Support Account Funding Transactions

Mastercard will implement changes to support account

funding transactions (AFTs) where funds are pulled from a
Mastercard account and are subsequently used to fund a
Visa or non-Visa account. Acquirers must include the
recipient name, recipient state / province code and the
recipient country when submitting an AFT.

Acquirers should include the following fields and values to

submit an AFT:

• Field 3—Processing Code with the following values:

o 10 (Account funding) in positions 1–2, Transaction Type

o A valid value in positions 3–4, Account Type (From)

o A valid value in positions 5–6, Account Type (To)

• A valid value in Field 18—Merchant Type

• A valid value in Field 42—Card Acceptor Identification Code

• Field 43—Card Acceptor Name / Location with the
following values:

o The merchant name in positions 1–25

o The city, telephone number or IP address in positions

26–38

o The country code in positions 39–40

• The account identifier reference code in Field 56—

Customer Related Data in TLV format, Dataset ID 01—
Account Data, Tag 82—Account Identifier Reference Code
• The account identifier value in TLV Field 56, Dataset ID 01,
Tag 83—Account Identifier Value

• The account identifier type code in TLV Field 56, Dataset

ID 01, Tag 84—Account Identifier Type Code

Visa Confidential
 REFERENCE: For more information about Tag 82, Tag 83 and
Tag 84 in TLV Field 56, Dataset ID 01, refer to the Section 3
article “Changes to Support Account Funding Transactions.”

• The account reference code in TLV Field 56, Dataset ID 05—

Account Owner Data, Tag 80—Account Reference Code

• The account owner given name in TLV Field 56, Dataset ID

05, Tag 83—Account Owner Name, Given

• The account owner middle name in TLV Field 56, Dataset

ID 05, Tag 84—Account Owner Name, Middle

• The account owner last name in TLV Field 56, Dataset ID

05, Tag 85—Account Owner Name, Last

• The account owner address in TLV Field 56, Dataset ID 05,

Tag 86—Account Owner Address Line 1

• The account owner address in TLV Field 56, Dataset ID 05,

Tag 87—Account Owner Address Line 2

• The account owner address in TLV Field 56, Dataset ID 05,

Tag 88—Account Owner Street Name

• The account owner building number in TLV Field 56,

Dataset ID 05, Tag 89—Account Owner Building Number

• The account owner postal code in TLV Field 56, Dataset ID

05, Tag 8A—Account Owner Postal Code

• The account owner city name in TLV Field 56, Dataset ID

05, Tag 8B—Account Owner City Name

• The account owner country code in TLV Field 56, Dataset

ID 05, Tag 8E—Account Owner Country Code

• The state code or country code in Field 59—National

Point-of-Service Geographical Data

• A valid business application identifier (BAI) in TLV Field 104,

Usage 2, Dataset ID 57—Business Application Identifier

• The sender reference number in TLV Field 104, Usage

2, Dataset ID 5F—Sender Data, Tag 01—Sender
Reference Number

• The sender account number in TLV Field 104, Usage 2,

Dataset ID 5F, Tag 02—Sender Account Number

• The source of funds in TLV Field 104, Usage 2, Dataset ID

5F, Tag 08—Source of Funds
V.I.P. Testing for Changes to Support Account
Funding Transactions

Table 3.15—V.I.P. Testing Approach for Changes to Support

Account Funding Transactions lists the V.I.P. System
messages, key fields and values, test results validation, and
the available test script and test modes for this
enhancement. The full table is available in the Visa Business
News article titled “Changes to the Authorization Gateway
Service for Mastercard POS Transactions Modified in Global
Technical Letter,” published 12 September 2022.

Note: There is no PDF attached to this article.

Visa Confidential
12 September 2022 3.17 Changes to Support the This article has been updated to clarify that acquirers and issuers
Recurring Payment must recognize that the currency code associated with the
Transaction Mandate for Maximum Recurring Payment Amount, TCR D, positions 48–59,
Cards Issued in India should contain the Source Currency Code, TCR 0, positions 89–
91, and not the Destination Currency Code, TCR 0, positions 74–
76, as currently documented in Table 3.17.E—New Draft Data,
TCR D—Recurring Payments Record Layout.

Note: There is no PDF attached to this article.

Visa Confidential