Operational Support Client Forum

July 2018
Jakarta, Indonesia
Notice of Confidentiality
This presentation is furnished to you solely in your capacity as a client of Visa 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 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 non-public information
under U.S. federal securities laws and that purchasing or selling securities of Visa Inc. while being aware of
material non-public information would constitute a violation of applicable U.S. federal securities laws.

2 | Operational Support Client Forum | July – August 2018 Visa Confidential

Processing Enhancements and
Upcoming Mandates
Article 2.7
Mandate for Credit Voucher and
Merchandise Return Authorization Messages
Article 2.7
Mandate for Credit Voucher and Merchandise Return
Authorization Messages

REGION(S) ABOUT THIS CHANGE

• Acquirers: • Mandatory
AP, Canada, CEMEA, Europe, LAC,
U.S. • Testing Available
• Issuers:
AP, Canada, CEMEA, Europe, LAC,
U.S.

EFFECTIVE: October 2019

5 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.7
Mandate for Credit Voucher and Merchandise Return
Authorization Messages
BUSINESS SUMMARY
A 0100 authorization message will be required for merchandise
returns. Why?
‒ Identified as a ‘pain point’ by a broad range of merchants
‒ Identified as a ‘point of dissatisfaction’ by consumers / cardholders
‒ In May 2015, the Merchant Advisory Group (MAG) responds to a Consumer
Finance Protection Bureau’s Request for Information regarding credit
markets and the MAG cited several concerns with the current return process

6 | Operational Support Client Forum | July – August 2018 Visa Confidential

Top Issues With The Purchase Returns Process
Purchase Returns ~ 1.4B Annually1 <Consumer Research Responses*>
40% said they were dissatisfied or very
dissatisfied about the time it takes for a refund to
On average takes 3-5 days to post appear in their account
transactions to a cardholder’s account 66% of consumers said it should take 0 - 2 days
to credit their account
No information beyond the paper receipt, to 93% said it would be useful to receive a text
confirm that a credit is in process message notifying them of the refund

Cardholders often believe that the merchant 52% said the store is 55% said they have
responsible for called the store for
is responsible for the delay in returning funds crediting their account status on a credit

Purchase returns to closed or re-issued accounts may impact issuer’s ability to return
funds promptly

No mechanism to prevent sending credits to closed or re-issued accounts; impacting

issuer’s ability to reconcile
* Consumer research online survey conducted in January 2016 with300 respondents
1Source: VisaNet Data – All Regions (excludes Interlink) - Oct 2015 – Sept 2016 from Asia Pacific.
7 | Operational Support Client Forum | July – August 2018 Visa Confidential
Summary of Benefits

Merchants Issuers Acquirers Cardholder

• Helps improve customer • Allow issuers to identify • Enhanced • Receives timely
experience unusual or suspected infrastructure information
• May reduce the number fraud activity sooner, as helps address a regarding the
of customer service it’s processed in real-time merchant pain- status of funds
inquiries • Enable issuers to provide point being returned to
their account
• Authorizations on valuable information to
purchase returns, plus cardholders, through • Less likely to
VCR, can help minimize alerts and online banking contact the
potential chargebacks for applications. merchant for
“Credit Not Processed” • May reduce the number status
of customer service calls
8 | Operational Support Client Forum | July – August 2018 Visa Confidential
Article 2.7
Mandate for Credit Voucher and Merchandise Return
Authorization Messages
TECHNICAL CHANGES – Acquirer
• It is currently optional for merchants to send an 0100 authorization message
• Effective with the October 2019 release, acquirers must be prepared to send
an 0100 credit voucher and merchandise return authorization transactions to
Visa, with a value of 20 in Field 3
‒ In AP, on 13 October 2019, all merchants must send authorization messages
on credit vouchers / purchase returns

Reference:
− VBN - New Implementation Dates for Purchase Return Authorization Messages, dated 08 March 2018 (AP, CEMEA)

9 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.7
Mandate for Credit Voucher and Merchandise Return
Authorization Messages
TECHNICAL CHANGES – Acquirer (cont)
• Field 62.2 (Transaction ID) and Field 38 (Authorization Identification Response)
are two of the required data elements that must be submitted into TC06.
• Field 22 POS Entry Mode Code and Field 55—Integrated Circuit Card (ICC)
Related Data, should apply to the merchandise return and credit voucher
authorization message and should not be copied from the original
authorization message.

10 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.7
Mandate for Credit Voucher and Merchandise Return
Authorization Messages
TECHNICAL CHANGES – Issuer
Effective with the April 2018 release:
− Issuers were mandated to receive and respond to an 0100 authorization
message, with a value of 20 in Field 3—Processing Code
• If declined, the acquirer cannot submit the TC 06 credit voucher into BASE II

Effective with the October 2019 release:

− Issuers are required to update their online statements with the “pending”
information, as they do today with purchases
• There is no expectation that the issuer will modify the cardholder’s open to
buy
11 | Operational Support Client Forum | July – August 2018 Visa Confidential
Article 2.7
Mandate for Credit Voucher and Merchandise Return
Authorization Messages
TECHNICAL CHANGES – Issuer (cont)
Effective with the October 2019 release:
− If issuers offer a text alert service to their cardholders for notification of
purchases, this option must also be available to cardholders for purchase returns
− Credit voucher and merchandise return authorization messages may or may not
contain chip data. This should not impact the response from Issuer.
− If chip data is present, be aware that the specific cryptogram type is irrelevant
to the transaction

12 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.7
Mandate for Credit Voucher and Merchandise Return
Authorization Messages
Credit, debit, and reloadable prepaid issuing BINs globally will be set
to route transactions to issuer. Default to approve if processed in STIP

VisaNet

Acquirer 00* (Approve) in F39 Issuer STIP advice sent Issuer

STIP

*Note: Processed in STIP using issuer parameters

13 | Operational Support Client Forum | July – August 2018 Visa Confidential
Article 2.7
Mandate for Credit Voucher and Merchandise Return
Authorization Messages
KEY POINTS AND CONSIDERATIONS
• The required changes in this article do not apply to 0200 full financial
transactions.
• Non-reloadable gift cards are excluded from requirement and can
choose whether to receive purchase return authorization messages.
• Chip data is optional and authentication is not required for EMV merchandise
return authorization transactions.

14 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.7
Mandate for Credit Voucher and Merchandise Return
Authorization Messages
FREQUENTLY ASKED QUESTIONS
Must issuers always return an approval?
Primarily, these are refunds that the cardholder is expecting; therefore it is
unlikely that issuers would decline these transactions. However, if the account
does not exist or has been closed, the issuer could decline the transaction. A
merchant in these situations may default to store policy on purchase returns.

15 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.7
Mandate for Credit Voucher and Merchandise Return
Authorization Messages
FREQUENTLY ASKED QUESTIONS (cont.)
In what other situations are merchants allowed to provide an alternate form
of purchase return?
U.S. merchants are permitted to provide an alternate form of purchase return in
the following situations:
– Cash can be given for a Visa Easy Payment Service transaction
– Cash or another form of credit can be given to the recipient of a gift (e.g.,
not the cardholder)
– Cash or store credit can be given for a Visa prepaid card transactions if the
card has been discarded

16 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.7
Mandate for Credit Voucher and Merchandise Return
Authorization Messages
FREQUENTLY ASKED QUESTIONS (cont.)
Do issuers have to reflect the amount of the return in the customers balance
or are they allowed to simply update the cardholder notification with the
merchandise-return notification?
Visa does not expect that most issuers would want to release funds based on the
authorization but would simply provide the information to the cardholder. If an
issuer can receive and process the authorization message and make the information
available to a cardholder as a “pending” item, it would align the return process
more closely to that of a purchase

17 | Operational Support Client Forum | July – August 2018 Visa Confidential

 Questions?

References:
New Purchase Return Authorization Messages Will Be Implemented in the Visa Business News, dated 25 August 2016 (AP, Canada, CEMEA, LAC)
New Implementation Dates for Purchase Return Authorization Messages, dated 20 July 2017 (Global)
New Implementation Dates for Purchase Return Authorization Messages in the Visa Business News, dated 20 July 2017 (Japan)
Article 3.1
Changes to ATM Messages to Support
the Routing Table Unique Identifier
Article 3.1
Changes to ATM Messages to Support the Routing Table
Unique Identifier
REGION(S) ABOUT THIS CHANGE
• Acquirers: • Mandatory
AP, Canada, CEMEA, Europe,
• Testing Required
LAC, & U.S.
• Issuers:
No Impact

EFFECTIVE: 1000 GMT 12 October 2018

20 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 3.1
Changes to ATM Messages to Support the Routing Table
Unique Identifier
BUSINESS SUMMARY
Why?
− ATM acquirers sometimes use outdated routing tables, causing declines
or service denial to Visa cardholders.
− Because these ATM transactions are never routed to VisaNet for
authorization, compliance monitoring is a challenge.
− This problem is experienced only at ATMs, not at the point-of-sale (POS).

21 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 3.1
Changes to ATM Messages to Support the Routing Table
Unique Identifier
BUSINESS SUMMARY (cont.)
Benefits
− Visa cardholders expect their cards to be accepted at any ATM that
displays the Visa or Plus logo. Effective with April 18 release, a new unique
identifier was added to the header of each week’s routing tables. This must
now be returned by acquirers in transactions to confirm to Visa that they
are using the most recent routing tables.
− This enhancement enables Visa to identify those acquirers that aren’t
updating their tables and initiate proactive compliance to mitigate the risk
of cardholders being declined at the ATMs.

22 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 3.1
Changes to ATM Messages to Support the Routing Table
Unique Identifier
TECHNICAL CHANGES
• Visa has added a unique identifier to • Acquirers must send the routing table
the header of each week’s routing table unique identifier in Field 62.27 for:
- 0200 ATM full financial request
• Acquirers must send the routing table
unique identifier in original ATM full - 0420 ATM financial reversal advice
financial transactions and their reversals • Routing tables must be loaded/applied
• Acquirers participating in Priority routing, within the time frames specified in the SMS
by populating the value of 0000 (Priority ATM Technical Specifications, Volume 2
routing) in Field 63.2 for Visa to • Visa will take into account the various
determine the network for transmission, routing table schedules when
are not required to send the routing determining that the unique identifier is
table unique identifier in Field 62.27 valid for the current week

23 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 3.1
Changes to ATM Messages to Support the Routing Table
Unique Identifier
New Processing Rules for Field 62.27 ATM Routing Table
Unique Identifier
• If an eligible ATM transaction is received, MCC=6011, transaction is processed via
network 0002 (Visa) or 0004 (Plus), and the new Field 62.27
− contains a current ATM Routing Table Unique Identifier, then V.I.P. removes the
field before passing to the issuer
− is omitted or contains a non-current ATM Routing Table Unique Identifier, then
V.I.P. will log the transaction for compliance tracking and, if applicable, remove
the field before routing to the issuer

24 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 3.1
Changes to ATM Messages to Support the Routing Table
Unique Identifier
TESTING AND ACTIVATION

System Testing Required Testing Data Testing Available

V.I.P. Full Service Yes Yes Yes

Notes:
• Testing is applicable for V.I.P. full service acquirers only
• For subscription to routing tables for the first time, contact your regional client
support representative
• Issuers are not impacted

25 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 3.1
Changes to ATM Messages to Support the Routing Table
Unique Identifier
FREQUENTLY ASKED QUESTIONS
We are not subscribed to any Visa Routing tables, am I still required to send
field 62.27 with Unique Identifier?
ATM 0200 full financial transactions with a network value of 0002 (Visa) or 0004 (Plus)
in Field 63.1, should already have a subscription to one of the routing files. If you do
not have a routing table subscription, please contact your VisaNet representative to
subscribe to one. Project is not required.
How could a client enroll / register to priority routing service?
The Priority Routing Service is an existing service that is not impacted by this change.
Clients can review information about the service in the V.I.P. System Services manual,
Volume 1 and contact their Visa representative for further info.

26 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 3.1
Changes to ATM Messages to Support the Routing Table
Unique Identifier
FREQUENTLY ASKED QUESTIONS (cont.)
Can you confirm that ATM acquirers will be expected to send Visa this
value in the 0100/0200 transactions? If so, what edits be enforced?
There is no reject if the value is missing or invalid, but V.I.P will log the
transaction and Visa has the right to initiate compliance

27 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 3.1
Changes to ATM Messages to Support the Routing Table
Unique Identifier
KEY POINTS
• Acquirers must send the routing table unique identifier in Field 62.27—ATM
Routing Table Unique Identifier in an
– 0200 ATM full financial request
– 0420 ATM financial reversal advice
• Routing tables must be loaded/applied within the time frames specified in the
SMS ATM Technical Specifications, Volume 2

28 | Operational Support Client Forum | July – August 2018 Visa Confidential

Questions?
Article 3.11
Support of Mass Transit Transactions
Article 3.11
Support of Mass Transit Transactions

REGION(S) ABOUT THIS CHANGE

• Acquirers: • Mandatory for Acquirers with mass
AP, Canada, CEMEA, transit merchants
Europe, LAC, & U.S. • Mandatory for Contactless Issuers
• Issuers:
• Testing Required
AP, Canada, CEMEA,
Europe, LAC, & U.S.

EFFECTIVE: Now available

31 | Operational Support Client Forum | July – August 2018 Visa Confidential

 Launching mass transit EMV payment solutions
unlocks benefits for the entire transit payments
ecosystem

PTOs Acquirers Issuers Tech Providers Cardholders

 Increase ridership  Increase transaction  Increase transaction  Increase product  Seamless, non-physical
volumes volumes sales & access new ticketing
 Improve passenger markets 
experience  New market  Drive top-of-wallet  Flexible, clear charging
segment - reusable preference  Gain economies of 
 Reduce operational & scalable scale  Habituation - use of
costs  Opportunity for contactless going
 Wider opportunity further innovation &  Increase investment beyond transit: the
 for cash differentiation & innovation ‘halo-effect’
Improve operations
displacement opportunities 
 Buy-in for
future initiatives
32 | Operational Support Client Forum | July – August 2018 Visa Confidential 32
 Currently over 100 transit projects globally, in
various phases, are being supported by Visa

Norway Sweden
Russia
Canada UK Poland
Czech Republic
France
United States Spain Italy Turkey

India

Malaysia
Singapore

Australia
Brazil South Africa

33 | Operational Support Client Forum | July – August 2018 Visa Confidential 33

Visa has developed three global transit models to suit
different Public Transit Operator requirements

Retail model Known Fare Transaction Mass Transit Transaction

Versatile solution where high Simple contactless-only solution for Flexible contactless-only solution for
transaction speed is not a primary environments with high passenger multimodal mass transport environments.
requirement. Payment is made to throughput. The payment card or The Visa contactless card or contactless
buy a ticket using contact or device may be used as the ticket. payment-device is the ticket.
contactless interfaces.

34 | Operational Support Client Forum | July – August 2018 Visa Confidential

 Visa Mass Transit Transaction (MTT) Model

Features
Contactless-only Shared merchant/issuer liability

Deferred authorizations Deny list/back office management

The MTT model enables
multi-modal ticketing in No financial transaction at point of tap
environments where
transaction speed can
be critical Benefits
High passenger throughput No purchase required

Versatile, adaptable solution Drives down PTO operating costs

Suited to multi-modal transit systems

35 | Operational Support Client Forum | July – August 2018 Visa Confidential 35

 MTT Process Flow
Intra-day process

Happens in real-time when a transit journey

starts Approved

OR

Card tapped ODA Performed Deny list checked Data sent to Received by
at reader merchant’s back office merchant

Declined Travel not

permitted

On first transit journey

Issuer AVR

36 | Operational Support Client Forum | July – August 2018 Visa Confidential

 MTT Process Flow
End-of-day process

Issuer approved

1 OR

Transit journeys Single fare & Acquirer Issuer Transaction

are accumulated transaction settled
created Below threshold
Issuer declined

OR

Added to deny list

Above threshold Debt recovery

process begins

37 | Operational Support Client Forum | July – August 2018 Visa Confidential

 Debt Recovery – MTT Model
There are multiple options for recovering debt and removing cardholders from deny lists

Merchant Initiated Cardholder Initiated

4 times in 14 days Merchant Call Center Merchant Website Tap Initiated

Merchant Initiated Transaction eCom with CVV2,

MOTO with CVV2 Contactless PEM 7
(MIT) – no CVV2 VbV

38 | Operational Support Client Forum | July – August 2018 Visa Confidential 38

Article 3.11
Support of Mass Transit Transactions
TECHNICAL CHANGES – Acquirers
• There are no new changes to the VisaNet systems with this enhancement.
• Effective immediately, acquirers that process mass transit transactions
must modify their systems to support processing of these transactions.
• Acquirers who want to start processing Mass Transit merchants for the first must
contact their Client Representative

39 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 3.11
Support of Mass Transit Transactions
TECHNICAL CHANGES – Issuers
• There are no new changes to the VisaNet systems with this enhancement.
• All contactless-enabled issuers must modify their systems to support processing of these
transactions

• Field 4—Amount, Transaction, with the amount of the mass transit transaction
• Field 7—Transmission Date and Time, with the date and time when the acquirer submits the authorization
message. It may differ from the transaction date if it is a deferred authorization.
• Field 18—Merchant Type, with MCCs 4111, 4112, or 4131
• Field 22—Point-of-Service Entry Mode Code, with one of the following values:
– 01 (Manual (key entry))
– 07 (Contactless device-read-originated using VSDC chip data rules; Online CAM authentication method;
iCVV checking possible)

40 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 3.11
Support of Mass Transit Transactions
TECHNICAL CHANGES – Issuers
• Field 55—Integrated Circuit Card (ICC)-Related Data, Tag 9A—Transaction Data
• Field 55—Integrated Circuit Card (ICC)-Related Data, Tag 9F02—Amount, Authorized
• Field 60.1—Terminal Type, with a value of 3 (Authorized UCAT)
• Field 60.2—Terminal Entry Capability with a value of 8 (Proximity-read-capable, indicating that the terminal
can read a proximity chip using a Visa contactless specification but cannot read a contact chip on a card)
• Field 60.9—Cardholder ID Method Indicator, with a value of 3 (Unattended terminal, no PIN pad)

41 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 3.11
Support of Mass Transit Transactions
KEY POINTS

Benefit Detail

Fare is aggregated and authorized daily; considerably minimizes risk and gives
1 One day travel period
Issuer better control of cardholder account

The very first time a card is used in public transport, an Account Verification
2 Account Verification Request
Request (AVR) is sent in near real-time

Only one authorization is sent at the end of travel period reducing processing
3 Fewer authorization requests
overhead, compared to retail model

4 No Open-to-Buy impact The cardholder open-to-buy (OTB) value will not impacted

Account notifications will show the exact fare authorized at end of travel
5 Correct account notifications
period. Eg: SMS alerts, Apple Pay logs
Transactions can be submitted to clearing, even if the authorization request
6 Liability sharing was declined, if the transaction value is below or equal to chargeback
threshold

42 | Operational Support Client Forum | July – August 2018 Visa Confidential

 Card Issuance &
AVR Liability sharing
ODA
Typically no different from a standard
low value low risk contactless payment

However…
Bypass ATC check-
Debt Recovery PAR & MIT deferred Auth
There are unique aspects to MTT that
will require adaptations to processing

CVL Technical Fees & testing

considerations readiness timelines
43 | Operational Support Client Forum | July – August 2018 Visa Confidential
Questions?
Article 6.1.1
Acquirer Merchant Master File in the
AP Region
Article 6.1.1
Acquirer Merchant Master File in the AP Region

REGION(S) ABOUT THIS CHANGE

• Acquirers: AP • Mandatory
• Issuers: No Impact • Testing Required

EFFECTIVE: 12 April 2019

46 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 6.1.1
Acquirer Merchant Master File in the AP Region
BUSINESS SUMMARY
History
– The Acquirer Merchant Master File (AMMF) is a global, standardized, and flexible format
which is used between Visa acquirers/acquirer processors and Visa to exchange
merchant detail information
Why?
– AMMF helps improve the merchant identity and quality in the overall Visa Payment System
Benefits
– A single consistent view of merchants while providing data for operational and analytical
services
– Validation and improvement of merchant information coming as part of authorization and
clearing data to resolve potential discrepancies
– Drive business efficiencies for better dispute resolution and authorization improvement

47 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 6.1.1
Acquirer Merchant Master File in the AP Region
TECHNICAL CHANGES
Mandatory:
• Effective with the April 2019 release, acquirers in the AP region must be able to
– Submit the Acquirer Merchant Master File (AMMF) monthly at a minimum either via
manual submissions* or the automated file exchange in an agreed upon format
– Deliver the required merchant detail information
– If the automated file exchange method is adopted, acquirers must be able to
o Support and act on exchange messages with Visa
o Acquirers must be able to submit the files through Extended Access Server (EAS) or Visa
File Exchange Service (VFES)

* Manual submissions will be available for a limited time

48 | Operational Support Client Forum | July – August 2018 Visa Confidential
Article 6.1.1
Acquirer Merchant Master File in the AP Region
TECHNICAL CHANGES (cont.)
Optional:
• Effective immediately, acquirers in the AP region will be able to optionally
support manual AMMF submission.
• Effective 12 October 2018, acquirers in the AP region will be able to optionally support
automated AMMF exchange.

49 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 6.1.1
Acquirer Merchant Master File in the AP Region
Acquirer Onboarding Timelines
2018 2019
JUL AUG SEP OCT … APR

VBN announcement

Clients must send

Acquirer onboarding
AMMF from
Apr ‘19 BER
Manual AMMF submissions – Testing/submission can begin immediately

AMMF Automated Batch – Testing begins Sep ‘18

50 | Operational Support Client Forum | July – August 2018 Visa Confidential

 Article 6.1.1
Acquirer Merchant Master File in the AP Region
Required Fields
Mandatory data elements required from acquirers as part of AMMF submission process. Additional optional
data elements may be included in future and will be included as part of the detailed technical specifications.

Attributes Description
Processor CIB (ID & Name) The processor CIB information; this should match with the CIB that appears in the settlement data in VisaNet.
Acquirer
details

Acquirer Business ID (BID & Name) The Business Identification Number (BID) of the acquiring financial institution; this should match with the BID that appears
in the settlement data in VisaNet.
Acquirer BIN The Visa-assigned Bank Identification Number of the acquiring financial institution; this should match with the BIN that
appears in the settlement data in VisaNet.
Identifiers
Merchant

Acquirer-Assigned Merchant ID The number used by the acquirer to uniquely identify the merchant at a location.
Card Acceptor ID (CAID) The Card Acceptor ID number assigned to the merchant location; this should match with what appears in the settlement
data in VisaNet.
Merchant DBA Name The DBA (“doing business as”) name of the merchant at this location; this could be the consumer-facing name of the
merchant.
Merchant Business Legal Name The merchant’s business legal name, which may be different from the DBA name.
Merchant
Details

Location Address (Street Address, City, Physical location details of the merchant location/store. Cannot be a PO Box in the street address. The country needs to be
State, Postal Code, Country) ISO Country Code.
Merchant Category Code (MCC) The primary merchant category code for the merchant location.

Note: Refer to the AMMF Implementation Guide 2.4 for more details.

51 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 6.1.1
Acquirer Merchant Master File in the AP Region
Process Flow – Manual file submissions (AMMF lite)
• A client is registered as a Visa endpoint and agreed to manually send AMMF to Visa
• Initial file in any electronic-readable format (CSV, Excel) is sent via secure email
to [email protected]
• Data that passed record level validation from successfully certified files are loaded for processing
• AMMF response files are not available for manual AMMF submission; however, the acquirer
will receive the email with validation results.
• Onboarding process is completed and data exchange moves to Business As Usual (BAU)
1 2 3
Endpoint File/Record
File Delivery
Registration Validation

Manual response
with rejected Data Load Certification One Time
records
Incremental
5 4
6
52 | Operational Support Client Forum | July – August 2018 Visa Confidential
Article 6.1.1
Acquirer Merchant Master File in the AP Region
Process Flow – Automated file exchange
• A client is registered as a Visa endpoint and a file transmission mechanism is established
• Initial file goes through certification process
• Data that passed record level validation from successfully certified files are loaded for processing
• Appropriate response files are sent back to the client
• Onboarding process is completed and data exchange moves to Business As Usual (BAU)

1 2 3
Endpoint File/Record
File Delivery
Registration Validation

Response
Files Data Load Certification One Time

6 5 4 Incremental

53 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 6.1.1
Acquirer Merchant Master File in the AP Region
Validations & Certification
• AMMF Processing
– The initial file should contain all the merchant locations in the acquirer’s portfolio.
Certification will be performed on this file. Endpoints* have the option of sending
subsequent files as incremental updates or full refresh
• Certification (one time)
– As part of certification, AMMF data is matched against VisaNet transactions
– File is certified if it crosses a certain threshold (~85% and configurable)
– Once certified response files will be sent out with the relevant details
– Move to BAU for future files
• File & Record Validations (one time and incremental)
– Record level validations are performed; if 50% (configurable) of the records fail the edits,
the entire file is rejected
– Rejected records are not loaded and are sent back for corrections from endpoint

*Endpoints could be acquirers or their processors that will be sending the AMMF data
54 | Operational Support Client Forum | July – August 2018 Visa Confidential
Article 6.1.1
Acquirer Merchant Master File in the AP Region
Response Files
Message Type When Message Content Acquirer/Endpoint Action

Details for BINs which passed/failed certification. It

If certification failed, resend the records with the
Certification Status Certification results are available also will list the missing BINs for which data was not
corrected details
received

Statistics of the submitted file i.e. ADD record count,

Merchant Statistic After each AMMF is processed Validate if counts match the submitted file
CHANGE record count

When the entire AMMF is

File Reject Reject reason for the file Correct the data and resubmit the file
rejected

When records get rejected List of records in the file that were rejected with Correct the issues for the records and resubmit
Record Reject
reject reason the records

A list of fields in the file that did not pass Visa ‘s data Correct the data quality issues for the records
Field Quality Error Ongoing and weekly
quality edits (if any defined) and resubmit the records

Unlinkable Merchant to Ongoing and weekly List of merchants from VisaNet transactions for the Include the missing merchants in a follow-up file
AMMF CIB/BIN that could not be matched to AMMF

Assigned AMMF ID When a new AMMF record is Visa assigned identifier for the merchants submitted
Store these values for future reference
Number sent in the AMMF file

55 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 6.1.1
Acquirer Merchant Master File in the AP Region
Key Points & Considerations
• Testing
– Required to validate file structure and formatting
– Contact your Visa representative for detail steps
– Move to production after successful testing

• Production
– First file with entire merchant portfolio, updates going forward
– Receive and act on reject records, missing data and data quality messages

Refer to the Acquirer Merchant Master File Implementation Guide on Visa Online for details.
Version 2.4 will be available Effective Mid-July

56 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 6.1.1
Acquirer Merchant Master File in the AP Region
FREQUENTLY ASKED QUESTIONS
How frequently does Visa expect an AMMF?
Weekly or monthly transmissions are recommended but Visa can accept at any frequency
including multiple files in a day

What is expected from the response files that Visa sends out?
Address any rejected records, send any missing information and fix and resend records with
data quality errors

What is the recommended data refresh strategy?

Visa can receive a full file refresh or incremental updates

57 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 6.1.1
Acquirer Merchant Master File in the AP Region
FREQUENTLY ASKED QUESTIONS (cont.)
When can testing be made available?
AMMF is a production process and as long as file transmission methodologies are in place testing
can start any day. For details please contact your Visa representative

In double-byte language countries, should acquirers send merchant data in English?

There is no requirement for acquirers to translate into English; they should send merchant data in
the language they use to send transactions to VisaNet today.

Will acquirers need to clean up data before they send AMMF?

Acquirers are expected to send their merchant data as-is.

When will the new file exchange methods via the EAS be available?
Visa does not have a date yet and will make an announcement on this with technical details
when available. Acquirers already have options to send AMMF manually or via VFES.
58 | Operational Support Client Forum | July – August 2018 Visa Confidential
Questions?
Article 2.2
Changes to Stand-In Processing
Article 2.2
Changes to Stand-In Processing

REGION(S) ABOUT THIS CHANGE

• Acquirers: • Mandatory
No impact • Testing Available
• Issuers:
AP, Canada, CEMEA,
Europe, LAC, U.S.

EFFECTIVE: 1000 GMT 12 October 2018

61 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.2
Changes to Stand-In Processing
BUSINESS SUMMARY
History
– Stand-In Processing (STIP) is a Visa service which responds to
authorizations on behalf of issuers when they are unavailable
– Over the last several releases, the STIP redesign has provided improved
risk management and simplified STIP processing
Why?
– To create an easy to manage STIP service available to all products
Benefits
– Consolidation of BASE I & SMS STIP functionality into a single service called
V.I.P. STIP

62 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.2
Changes to Stand-In Processing
TECHNICAL CHANGES
• The name of SMS STIP will be changed to V.I.P. STIP to more
accurately reflect availability to all issuers
• Effective with the April 2019 Business Enhancements, issuers that participate
in the Positive Cardholder Authorization Service (PCAS) will be migrated to
the V.I.P. STIP service
• Visa will automatically migrate the issuers existing PCAS processing options,
activity limits, and VAA scores to the corresponding parameters in V.I.P. STIP
• No issuer action is required however issuers are encouraged to review
their STIP parameters

63 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.2
Changes to Stand-In Processing
TECHNICAL CHANGES (cont.)
• New STIP processing options will be available to clients who are current
V.I.P. STIP participants
‒ Allow/decline approvals for mail order/telephone order transactions when the
expiration date is not present
‒ Allow/decline recurring payment transactions with an expired or missing
expiration date
‒ Allow/decline all key-entered transactions without authentication data in STIP
‒ Decline authorizations without authentication data in STIP when:
o There is no previous activity on the account (in 2 years) o
The previous authorization on the account was declined

64 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.2
Changes to Stand-In Processing
TECHNICAL CHANGES (cont.)
• V.I.P. STIP activity limits for ATM transactions will be used for processing
all cash transactions including manual cash and quasi-cash

65 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.2
Changes to Stand-In Processing
TECHNICAL CHANGES (cont.)
• Visa will implement a new STIP reason code value and redefine an existing value
for Field 63.4-STIP/Switch Reason Code
– 9218, new code that will be used to validate that product subtype MB
(Interoperable mobile branchless) is used with the correct business application
identifier (BAI) of MP (Merchant payment) and vice versa, for non domestic
PIN change transactions
– 9212, existing code that will have a new description and be used to identify
transactions “Declined due to fraud condition”
– SMS Raw Data record V22210 (positions 54-57)
– SMS Raw data record V22401 (positions 17-20)
– Authorization Profile Reports (APR)

66 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.2
Changes to Stand-In Processing
TESTING AND ACTIVATION
• Issuers that choose to participate in one or more of the new STIP
options must contact their Visa representative
• Testing is available for issuers that choose to implement the new
STIP processing options for the first time
• Testing is available for the new 63.4—STIP/Switch Reason Code value of
9218

Note: V.I.P STIP participants are encouraged to review their STIP parameters to ensure
their current ATM activity limits are adequate to approve STIP transactions in the
additional cash categories

67 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.2
Changes to Stand-In Processing
FREQUENTLY ASKED QUESTIONS
What is the impact to issuers for cash transactions processed in STIP?
• The change to ATM activity limits applies only to issuers who are currently using SMS
STIP (renamed VIP STIP with this release)
• Issuers that use V.I.P. STIP must be aware that all types of cash transactions processed
in STIP will use the activity limits that were previously used only for ATM transactions
What is the purpose of the STIP/Switch Reason Code?
• The STIP/Switch Reason code identifies the reason a transaction was routed to STIP
instead of being forwarded to the issuer
• Issuers can review STIP/Switch Reason codes to identify transactions routed to STIP due to
maintenance versus those that have failed verification, or were declined due to the issuers’
processing options

68 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.2
Changes to Stand-In Processing
KEY POINTS
• The renamed V.I.P. STIP Service is available to all issuers and all product types
• ATM activity limits in V.I.P. STIP will be used to process all cash transactions.
This change will align V.I.P. STIP activity limits with Positive Cardholder
Authentication (PCAS) STIP processing
• The introduction of a new STIP/Switch Reason code value will help issuers
better understand why the transactions are processed in STIP
• No issuer action is required and issuers should not experience any change to
the processing of STIP transactions

69 | Operational Support Client Forum | July – August 2018 Visa Confidential

Questions?
Push Payments
Article 2.8
Changes to Support Sales Tax Rebates
in Original Credit Transactions
Article 2.8
Changes to Support Sales Tax Rebates in Original Credit Transactions

REGION(S) ABOUT THIS CHANGE

• Acquirers: • Optional from Oct 18,
AP, Canada, CEMEA, Mandatory from Apr 19
Europe, LAC, U.S. • Testing Available
• Issuers:
AP, Canada, CEMEA,
Europe, LAC, U.S.

EFFECTIVE: 1000 GMT 12 October 2018 and April 2019

73 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.8
Changes to Support Sales Tax Rebates in Original Credit Transactions
BACKGROUND
History
• Some governments allow tax-free shopping for foreign travelers
• Merchants, acquirers, and solution providers offer sales tax / value-
added tax (VAT) rebates to foreign travelers
• Traditionally, merchants submit these tax rebates via Merchandise returns
or checks
• Funds don’t post in real-time

74 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.8
Changes to Support Sales Tax Rebates in Original Credit Transactions
BACKGROUND
Summary
• Usage of merchandise returns to rebate local taxes does not align
with Visa rules
• To ensure this practice is conducted according to the Visa Rules, Visa
is mandating that merchants:
– Use original credit transactions (OCTs) for sales tax disbursements
– Follow dynamic currency conversion (DCC) rules if the amount rebate is
converted from a merchant’s local currency to a cardholder’s billing currency

75 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.8
Changes to Support Sales Tax Rebates in Original Credit Transactions
BACKGROUND

Benefits
• OCTs with additional data elements allow issuers to recognize this use case
• Additional revenue for financial institutions
• Fast-funds allow funds to be made available to customers in real-time
and allow for a better user experience

76 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.8
Changes to Support Sales Tax Rebates in Original Credit Transactions
TECHNICAL CHANGES
• Acquirers can submit sales tax rebates as 0200 full financial OCTs
• Sales tax rebate must be identified by existing reason code 5120 (Sales Tax/Value
added tax) and BAI value of FD (Funds Disbursements)
• OCTs for sales tax rebates will be supported on following networks; 0002 (Visa), 0003
(Interlink), and 0004 (Plus)
• OCTs for sales tax rebates will be converted to merchandise return transactions in the
following scenarios
– Destined to Issuers do not accept OCTs
– OCTs are restricted due to government regulations

77 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.8
Changes to Support Sales Tax Rebates in Original Credit Transactions
TECHNICAL CHANGES (cont.)
• Transaction amount must not exceed maximum transaction limits:
– Defined for OCTs with BAI value of FD
– Defined for OCTs in a particular jurisdiction
• No impact to OCT Interchange
• Following fields must be sent in the OCT in order to identify it as a sales tax rebate:
– Field 104, Usage 2—Transaction-Specific Data in TLV format, Dataset ID 57—
Business Application Identifier with existing value of FD
– Field 63.3—Message Reason Code with existing value of 5120 (Sales tax/Value added tax)

78 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.8
Changes to Support Sales Tax Rebates in Original Credit Transactions
TECHNICAL CHANGES (cont.)

• Field 63.3 will not be sent to issuers in the original sales tax rebate
transaction
• Adjustment transactions of sales tax rebates must contain the appropriate
reason code for the adjustment
• For more information, refer to Sales Tax Rebate Processing Requirements
in the Visa Business News, dated 21 December 2017

79 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.8
Changes to Support Sales Tax Rebates in Original Credit Transactions
TECHNICAL CHANGES (cont.)
V.I.P. Processing Rule

Transaction Amount within allowable limits for the OCT Jurisdiction

and disbursements

V.I.P. sends OCT to the

TLV Field 104, Usage 2—Transaction Specific Data, Dataset ID 57— issuer for sales tax rebate
Business Application Identifier contains the existing value of FD
(Funds Disbursement)
Acquirer submits 0200
OCT for Sales tax rebate
Field 63.3—Message Reason Code contains the existing value of
5120 (Value-added tax)
V.I.P. drops F63.3 from
OCT request to issuer
The transaction contains all the valid fields and values for OCTs

Issuer accepts OCTs

80 | Operational Support Client Forum | July – August 2018 Visa Confidential

Article 2.8
Changes to Support Sales Tax Rebates in Original Credit Transactions
TECHNICAL CHANGES (cont.)
V.I.P. Processing Rule

Transaction Amount within allowable limits for the OCT Jurisdiction

and disbursements
V.I.P. converts sales tax rebate
OCT to Merchandise return
TLV Field 104, Usage 2—Transaction Specific Data, Dataset ID 57— prior to sending transaction to
Business Application Identifier contains the existing value of FD the issuer
(Funds Disbursement)
Acquirer submits 0200
OCT for Sales tax rebate
Field 63.3—Message Reason Code contains the existing value of
5120 (Value-added tax)
V.I.P. drops F63.3 and TLV Field
104, Usage 2, Dataset ID 57-
The transaction contains all the valid fields and values for OCTs Business Application Identifier
from OCT request to issuer
Issuer does not accept OCTs

81 | Operational Support Client Forum | July – August 2018 Visa Confidential

Questions?
Additional Articles
Additional Articles – Processing Enhancements
Article Title Acquiring Issuing

2.1 Changes to Edit Package √ √

By CPD 13 October 2018, all Edit Package endpoints must use a supported operating system and install mandatory Edit Package
software updates in support of the October 2018 release enhancements.

If the updates are not applied by the software effective date, Edit Package will not start effective CPD 13 October 2018, and acquirers
and issuers will be unable to send or receive files using Edit Package.

Key dates:
− Edit Package software updates distributed - CPD 1 September 2018.
− Earliest date to receive the VCMS Edit Package full file replacement - 4 September 2018
− PC Edit Package for Windows, Version 4.01.0020 available on Visa Online - 7 September 2018
− Edit Package BIN/ARDEF Tables distributed - CPD 12 October 2018

Note the upcoming sunset dates for the following operating systems:
• IBM z/OS 1.12 and IBM z/OS 1.13 will sunset on 30 September 2018.
• Windows 7 Ent SP1, Windows 8.1 Ent and Win Server 2008 R2 ENT SP1 will sunset on 14 January 2020.

84 | Operational Support Client Forum | July – August 2018 Visa Confidential

Additional Articles – Processing Enhancements
Article Title Acquiring Issuing
√ √
2.3 Changes to Assured Transaction Response
(excl. EU) (excl. EU)
Effective 12 October 2018, Visa will implement changes to assured transaction response (ATR) processing options to ensure
merchants receive a timely response to authorization request messages.

As defined in the Visa Rules, VisaNet allows issuers in AP 15 seconds to respond to authorization requests and 30 seconds to respond
to ATM transactions with PIN. Issuers are allowed to define additional seconds to respond at the BIN station and PCR level.

Visa will eliminate this option and all BIN, station, and PCR settings will be restored to the system-default values of 10 seconds for POS
authorization requests and 25 seconds for ATM transactions with PIN.

1. Acquirers must ensure that merchant terminals do not time out prior to the defined length of time for the authorization
response type.
2. Issuers must be aware of the changes to ATR time limits and must ensure that they respond within ten seconds for
authorization requests and within 25 seconds to respond to ATM transactions with PIN.
3. Transactions that are not responded to within the system defined limits of ten and 25 seconds will be routed to STIP
for authorization decision.

85 | Operational Support Client Forum | July – August 2018 Visa Confidential

Additional Articles – Processing Enhancements
Article Title Acquiring Issuing

3.3 Changes to Adjustment Advice Messages for Issuers √

Effective 12 October 2018, Visa will implement changes to send existing Field 104—Usage 1 (Transaction Description) & Usage 2
(Transaction-Specific Data) in adjustment advice messages of purchase transactions, including account funding transactions
(AFTs), depending on issuer usage participation.

Issuers that receive Field 104 must support the field in adjustment advice messages for purchase transactions and AFTs.

The following purchase transactions, including AFTs, are impacted by this change:
- Mail order/telephone order and e-commerce
- Custom Payment Service (CPS) and non-CPS
- Manual cash, bill payment, and purchase
- Card present and card-not-present

86 | Operational Support Client Forum | July – August 2018 Visa Confidential

Additional Articles – VSS
Article Title Acquiring Issuing

3.7 Changes to Visa Settlement Service Reports √ √

Effective CPD 13 October 2018, Visa will implement changes to machine-readable Visa Settlement Service (VSS) reports. The changes
impact machine-readable report group V, subgroup 4 reports.

When TCR 0, position 57, No Data Indicator contains the existing value of Y (No data):
- TCR 0, positions 50–52, Settlement Currency Code will contain spaces,
- TCR 0, positions 53–55, Clearing Currency Code will contain spaces

Currently these positions contain zeros when the no data indicator = Y.

Acquirers and issuers that receive VSS reports in machine-readable format TC 46 may need to update their systems to recognize spaces in
TCR 0 Report subgroup = 4, positions 50–52, and positions 53–55 when TCR 0, position 57, contains the existing value of Y (No data).

87 | Operational Support Client Forum | July – August 2018 Visa Confidential

Additional Articles – Keys
Article Title Acquiring Issuing

5.4 Required Changes to Visa-Provided Test Encryption Keys √ √

Effective with the April 2019 release, to enhance the troubleshooting capabilities, endpoints must use Visa-provided encryption keys
for testing with the VisaNet Certification Management Service (VCMS).

- Client’s endpoint test host system used for VCMS testing, must employ a host security module (HSM) for use
in encryption/decryption processing of the Visa test encryption keys to provide a production-like environment

- Software HSM emulation must not be used

- Acquirers and Issuers are encouraged to migrate to the Visa-provided test encryption keys at their earliest opportunity

- VCMS also supports testing of new technologies related to encryption keys and key management such as the Payment Card Industry
(PCI) PIN security requirement to use the key block format for exchanging encryption keys

- Endpoints migrating to complex VCMS encryption keys are encouraged to combine testing of key block format with complex VCMS
encryption keys

88 | Operational Support Client Forum | July – August 2018 Visa Confidential

Additional Articles - Processing Enhancements
Article Title Acquiring Issuing

5.8 Retirement of Selected Cryptogram Version Numbers for Chip Transactions √

Effective 17 October 2020, cryptogram version numbers (CVNs) 10 and 17, as well as proprietary CVNs that use a static key in the
cryptogram calculation process may no longer be used to personalize non-tokenized products.

- Issuers must personalize their new and replacement PAN-based card products with CVN 18, CVN ‘22’ or a proprietary CVN using
session keys, as applicable.

- Check with their card vendors to see if their existing card products can be personalized with CVN 18 or CVN '22', and if not, plan for
a migration to a new card product

- Check with their personalization bureau about the process for creating a new profile that supports CVN 18 or CVN '22‘

- Check with their hardware security module (HSM) vendor to see if their firmware supports CVN 18 or CVN '22', if performing card
authentication in-house

Cards personalized with CVN 10, CVN 17, or proprietary CVN’s that use static keys that have been distributed to cardholders prior to 17
October 2020 may remain in use until their natural expiration date.

89 | Operational Support Client Forum | July – August 2018 Visa Confidential

Additional Articles – Keys
Article Title Acquiring Issuing

5.3 Mandate to Support Key Block Requirement √ √

Effective June 2021, acquirers and issuers are required to be compliant with the Payment Card Industry (PCI) PIN security
requirement to use the key block format.

Visa will eventually no longer support variant format key in Field 105—Double-Length DES Key (Triple DES) and TLV Field 110—
Encryption Data, Dataset ID 04—Key Data, and the key check value in Field 48—Additional Data—Private, Usage 14—Dynamic Key
Exchange Working Key Check Value.

The date that Visa will no longer support these fields will be aligned with the key block requirement implementation dates set by the
Payment Card Industry (PCI) Security Standards Council.

4.4 Changes to Support Key Block Format for Static Key Processing √ √

Effective 27 July 2018, Visa will include the new key block format and the existing variant format keys in the Client Copy printed
form that is sent to acquirers and issuers when they request Visa to create new static keys. Acquirers and issuers that choose to
support the key block format have an option to suppress the printing of the variant format.

References:
VBN dated 4 May 2017, Implementation Date Change for PCI PIN Security Key Bundling Requirement
90 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles –
No Review
Additional Articles – no review
Article Title
2.4 Changes to Support Enhanced Money Transfer Original Credit Transactions
2.6 Changes to Floor Limits
2.10 Changes to the Edit Package ARDEF Table
2.11 Changes to Currency Codes
2.12 New Merchant Category Codes for Marketplaces
3.4 Changes to Support the Business Application Identifier Value in Adjustment Transactions
3.5 Changes to Token Provisioning for the Visa Token Service
3.6 Mandate for the Visa Token Service That Supports Token Transactions With 3-D Secure
3.8 Changes to Reject Original Credit Reversal Transactions
3.10 Changes to Token Expiry Date for E-Commerce/Card-on-File and E-Commerce Enabler Token Types
3.12 New Reject Reason Codes for Cardholder Maintenance File
3.13 Support of the Visa Token Service for Account Funding and Original Credit Transactions
3.14 Changes to the Authorization Gateway Service for Mastercard Token Processing
3.15 Changes to the Authorization Gateway Service for Mastercard Transactions
3.16 Changes to the Visa Token Service for Secure Element
3.17 Changes to the Enhanced TC 33 Acquirer Capture File
3.18 Changes to the TC 33 Merchant Capture File

92 | Operational Support Client Forum | July – August 2018 Visa Confidential

Additional Articles – no review
Article Title
3.19 New Visa Token Service Basic Issuer Participation
3.20 Changes to Support BASE II-Originated Original Credit Transactions for the Visa Token Service
3.21 Changes to the Authorization Gateway Service for American Express Transactions
4.1 Changes to Support Key Block Processing for Dynamic Key Exchange Participants
4.2 Changes to Support an Issuer Option for Cardholder Billing Currency
4.5 New Issuer TC 33 Record for Payment Account Reference
4.6 Changes to the Visa Token Service to Support Visa Digital Commerce Transactions
4.7 Changes to Support Enhanced Original Credit Transactions for Plus Recipient Issuers That Process Visa Products
4.8 Changes to Support Electronic Commerce Using Authentication Data
4.9 Changes to the Visa Token Service to Support Contactless ATM Transactions
4.10 New V.I.P. Payment Account Reference Inquiry Messages.
5.1 Mandate for Eight-Digit Issuing BIN
5.2 Mandate for Support of Eight-Digit Issuing BIN
5.5 Changes to Support Velocity Limits for Account Funding Transactions
5.6 Reminder for Acquirers to Deliver Payment Account Reference to Merchants
5.7 Requirement to Include Local Transaction Date and Time in Authorization Messages
5.9 New Business Product for V PAY

93 | Operational Support Client Forum | July – August 2018 Visa Confidential

Additional Articles – no review
Article Title
5.10 Changes to Basic Format Original Credit Transactions
5.11 Requirement to Support 3-D Secure
5.12 Increase of File Size for ARDEF and Routing Tables
6.1.2 Requirement to Support Domestic Account Funding and Original Credit Transactions in Japan
6.5.1 Mandate to Support Cashback for Issuers in Malaysia

94 | Operational Support Client Forum | July – August 2018 Visa Confidential

Additional Articles
Article Title Acquiring Issuing

2.4 Changes to Support Enhanced Money Transfer Original Credit Transactions √ √

Visa will implement changes to redefine the existing BAI value of WT (Wallet transfer) as money transfer for enhanced money
transfer OCTs.

Acquirers and issuers must be aware of the existing BAI value that will be processed as money transfer for enhanced money transfer
OCTs and must be prepared to support the OCTs as money transfer that contain the BAI value. OCTs that are submitted with the
BAI value of WT will be processed using the existing money transfer processing rules.

95 | Operational Support Client Forum | July – August 2018 Visa Confidential

Additional Articles
Article Title Acquiring Issuing

2.6 Changes to Floor Limits √ √

Effective with the October 2018 release, Visa will implement the following changes to floor limits in the following countries:

Thailand
• Floor limits will be reduced to zero for all transactions for all MCCs

Denmark and Norway

• Floor limits will be reduced to zero for all transactions with the exception of:
- Unattended transactions for MCC 4111, 4112, 4131, 4784, 7523
- Attended and unattended transactions for MCC 8398

Turkey
• Floor limits will be increased to 90 for contactless chip transactions for all MCCs
• Existing floor limits will continue to apply for contact chip unattended transactions for MCCs 4111 , 4112, 413, 4784, and 7523

96 | Operational Support Client Forum | July – August 2018 Visa Confidential

Additional Articles
Article Title Acquiring Issuing

2.10 Changes to the Edit Package ARDEF Table √ √

Effective CPD 13 October 2018, Visa will change the definition of product subtype VM from Visa Vale Meal Voucher to Meal Voucher.

2.11 Changes to Currency Codes √ √

Effective TBA (4 August 2018*), the new currency code VES/928 for Venezuela will be added to VisaNet. The new currency code will also
have a different denomination, where the amount of 1,000 VEF/937 will be equal to one VES/928. The minor units will not change and
remain as two.

V.I.P. transactions submitted with the existing alphanumeric currency code VEF/937 after TBA will be rejected with V.I.P. reject code
0037 (Invalid value).

97 | Operational Support Client Forum | July – August 2018 Visa Confidential

Additional Articles
Article Title Acquiring Issuing

2.12 New Merchant Category Code for Marketplaces √ √

Visa will add new MCC 5262 for marketplaces to V.I.P. Field 18—Merchant Type and BASE II, Draft Data, TCR 0, positions 133–
136, Merchant Category Code.

Acquirers that are registered with qualified and registered marketplaces must submit applicable transactions with the new MCC and
issuers must be able to process the new MCC.

Refer to Table 2.12.A for a description of the new Merchant Name.

98 | Operational Support Client Forum | July – August 2018 Visa Confidential

Additional Articles
Article Title Acquiring Issuing
Changes to Support the Business Application Identifier Value in Adjustment
3.4 √ √
Transactions

Effective with the October 2018 release, Visa will

• reject or return AFT adjustments and OCT adjustments, and their reversals that do not contain a valid BAI value. Acquirers and
originators must submit the same valid BAI value in AFT adjustments and OCT adjustments that was submitted in the original AFT or
OCT, respectively.
• no longer remove TLV Field 104, Usage 2 from the AFT adjustment advice and will forward the field with the BAI value to the
issuer. Issuers must be aware that AFT adjustments and OCT adjustments will contain a valid BAI value.

99 | Operational Support Client Forum | July – August 2018 Visa Confidential

Additional Articles
Article Title Acquiring Issuing

3.5 Changes to Token Provisioning for the Visa Token Service √

Visa will enhance the Visa Token Service to support new wallet provider reason code values for issuers that choose to push card data to
Token Requestor applications.

New wallet reason codes will be defined in existing Field 125—Usage 2: Supporting Information (TLV Format), Dataset ID 02—Wallet
Provider, Tag 07—Wallet Provider Reason Codes when Field 63.3—Message Reason Code is 3700 (Token create) in the following
messages:
• 0100 Token activation request messages
• 0120 Token activation request STIP messages
• 0600 Issuer token notification online messages
• 0620 Issuer token notification advice messages

These values will only be returned for issuers that have explicitly implemented push provisioning implementations as per Network Hub
Push Provisioning (NHPP) specifications. Issuers who have already implemented push provisioning using push provisioning
specifications may start seeing these new values as well.

100 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing
Mandate for the Visa Token Service That Supports Token
3.6 √
Transactions With 3-D Secure

Visa will require all acquirers that participate in the VTS and 3DS to carry the TAVV cryptogram data in Field 126.8—Transaction ID
(XID) in combination with the 3DS CAVV cryptogram data in Field 126.9—Usage 3: 3-D Secure CAVV, Revised Format for token-based,
card-on-file, e-commerce, and application-based e-commerce transactions with 3DS.

101 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing

3.8 Changes to Reject Original Credit Reversal Transactions √

Visa will implement changes to enforce the existing rule that prohibits originators from submitting reversals of V.I.P. full financial
original credit transactions (OCTs).

Acquirers must be aware that Visa will reject originator-initiated 0400 Reversal and 0420 Reversal advice transactions of original
0200 Full financial OCTs.

102 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing
Changes to Token Expiry Date for E-Commerce/Card-on-File
3.10 √
and E-Commerce Enabler Token Types

Effective 2 November 2018, Visa will implement changes to the token expiry date for new and existing tokens with e-
commerce/card-on-file (COF) and e-commerce enabler token types.

Currently, the token expiry date assigned by the Visa Token Service is dated after the primary account number (PAN) expiry date.
With this change, the token expiry date will equal the PAN expiry date.

• For CoF and eComm tokens that have been provisioned previously, there will be a gradual alignment of token and PAN expiry dates
• A new message reason code 3716 (Token expiry update) in Field 63.3—Message Reason Code will be defined for the V.I.P.
0620 advice
• Issuers must request Visa through their Visa representatives to receive 0620 advice notifications with new message reason code
3716 when Visa makes the change to token expiry date of existing CoF and eComm tokens to equal PAN expiry date

103 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing

3.12 New Reject Reason Codes for Cardholder Maintenance File √

Effective 1300 GMT 12 October 2018, Visa will implement two new reject reason codes and processing rules for the existing
Cardholder Maintenance File (CMF) Type 1 Detail Record.

Issuers must be aware of the new reject reason codes that will be carried in existing positions 400–401, Reject Reason of the Cardholder
Maintenance Return File Detail Record as shown in Table 3.12.A, and the new processing rules as shown in Table 3.12.B.

104 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing
Support of the Visa Token Service for Account Funding and
3.13 √ √
Original Credit Transactions

Visa currently supports Visa Token Service for account funding transactions (AFTs) and original credit transactions (OCTs) for all
available token types, including secure element (SE) and host card emulation (HCE) token types.

Acquirers of third-party agent service providers and merchants that participate in the VTS can submit AFTs and OCTs for token
processing. When submitting AFTs or OCTs with a token, all required fields and values for both token transactions and AFTs/OCTs
must be supported.

Issuers that participate in the VTS must be aware that AFTs and OCTs may contain a token for all available token types, and
must support all the related token fields.

For detailed information about all supported fields and values for the Visa Token Service, AFTs, and OCTs, refer to:
• SMS POS (Visa & Visa Electron) Technical Specifications, Volume 1 and Volume 2
• BASE II Clearing Interchange Formats, TC 01 to TC 48
• BASE II Clearing Interchange Formats, TC 50 to TC 92
• Account Funding Transaction Processing Guide
• Visa Original Credit Transaction Global Implementation Guide
• Visa Token Service Technical Specifications Guide for Issuers

105 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing
Changes to the Authorization Gateway Service for Mastercard
3.14 √
Token Processing

Visa will implement changes to support account information on file for Mastercard transactions. Effective with the October 2018 release,
acquirers that submit token and non-token Mastercard transactions through Visa can submit the value of 10 in Field 22 for Mastercard
transactions to identify transactions initiated with account information that is already on file.

106 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing
Changes to the Authorization Gateway Service for Mastercard
3.15 √
Transactions
Visa will implement the following changes to support Mastercard enhancements:
• Add a new product code in existing Field 62.17 of 0110 Authorization response messages
• Add new processing rules for authorization request messages submitted with a card associated with an existing product code MAP
for the country of Brazil and countries in the Mastercard EEA Subregion
• Add 2 new values in existing Tag 06 of TLV Field 104, Usage 2, Dataset ID 65 to support changes to the Mastercard
Installment Payment Service
• Allow the credential on file indicator in Field 22, positions 1–2, to be used in all Mastercard-branded transaction with the account
information on file.
• Add new values to existing Field 126.16—Mastercard UCAF Field to support accountholder authentication values (AAV) for EMV 3-D
secure

Mastercard is reminding acquirers to support the 8-digit BIN Standard and Account Range Specifications.

107 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing

3.16 Changes to the Visa Token Service for Secure Element √

Issuers that participate in VTS and support the SE device type must support the following new and existing fields and values that will be
sent in the 0100 Token activation request, 0120 Token activation STIP advice, and 0620 Token creation advice.

New and Revised Tags in Field 120, Dataset ID 57:

• Rename an existing tag for the primary account number capture method and consumer entry mode
• Create a new tag for the wallet account email address age
• Create a new tag for the phone number score

TLV Field 120 is mandatory with the enriched format of the 0100 Token activation request.

New values will be defined for existing tags in Field 125, Usage 2: Supporting Information (TLV Format) for the following:
• Dataset ID 01—Token Device, Tag 01—Device Type with the new value of 05 (Personal computer)
• Dataset ID 02—Wallet Provider, Tag 07—Wallet Provider Reason Code with the new value of 0H (Phone score<3)

This field is not mandatory with this enhancement.

108 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing

3.17 Changes to the Enhanced TC 33 Acquirer Capture File √

Effective CPD 22 October 2018, Visa will implement changes to the enhanced TC 33 Acquirer Capture File to add new fields and
new values and change existing fields in existing TCR records.

Acquirers with standard TCR subscriptions for the enhanced TC 33 Acquirer Capture File will automatically receive the new
fields available for subscribed TCRs.

3.18 Changes to the TC 33 Merchant Capture File √

Effective CPD 22 October 2018, Visa will implement changes to the TC 33 Merchant Capture File to add new fields and new values
and change existing fields in existing TCR records.

Acquirers of MDEX endpoints must be able to support the changes that will apply to their merchants that are directly connected to Visa.
Participating MDEX endpoints must be able to correctly format and send the TC 33 Merchant Capture Files and receive the TC 33
Merchant Acknowledgement Files. Acquirers with MDEX endpoints must support the existing Enhanced TC 33 Acquirer Capture File.

109 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing

3.19 New Visa Token Service Basic Issuer Participation √

Visa is creating a basic participation framework for enrolling issuers in the Visa Token Service for specific markets to participate in
tokenized e-commerce transactions through e-commerce and credential-on-file token requestors without detailed Visa Token
Service integration efforts.

This framework is specifically designed for issuers that do not currently participate in the Visa Token Service for mobile contactless
payment services. This service will be rolled out on a country-by-country basis, as appropriate. Issuers in the affected countries will be
notified prior to their enrollment.

For more information, refer to VBN dated 10 May 2018, Visa Token Service Basic Issuer Participation in E-commerce and Credential-On-File Token Requestors.

110 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing
Changes to Support BASE II-Originated Original Credit Transactions for the
3.20 √ √
Visa Token Service

Effective CPD 13 October 2018, Visa will no longer return or reject BASE II-originated OCTs with a token provisioned by the VTS if
they do not contain sender data. Visa will implement changes to remove the requirement for sender data in OCTs with a token
provisioned by the Visa Token Service in BASE II TC 06—Credit Voucher—Original Credit and TC 26—Reversal, Credit Voucher—
Original Credit transactions. The OCTs with a token must contain a BAI value that is valid for the Visa Direct Service in TCR 3.

111 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing
Changes to the Authorization Gateway Service for American Express
3.21 √
Transactions

Visa will implement changes in V.I.P. to support the Zero Value Account Verification (ZVAV) service offered by American Express.
The service is similar to the Visa Account Number Verification Service.

Acquirers that choose to submit American Express ZVAV transactions through the Authorization Gateway Service must be able to send and
receive the existing 0100/0110 Account Verification Service request and response messages with the required fields and values.

Changes to Support Key Block Processing for Dynamic Key Exchange

4.1 √ √
Participants (DKE)

Effective 27 July 2018, acquirers and issuers that participate in the DKE Service will have the option to support a new optional TLV Field
110—Encryption Data in 0800 Dynamic key exchange request and response messages. This new field will be used to carry the new key
block format and/or the existing variant format keys.

Testing and activation are required to implement the new TLV Field 110 for the first time.

112 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing

4.2 Changes to Support an Issuer Option for Cardholder Billing Currency √

Effective CPD 13 October 2018, Visa will implement changes to optionally send the cardholder’s billing amount in the issuer’s
settlement currency to issuers. This allows for separation of the billing currency used for fee assessment purposes by Visa from the
currency in which Issuers receive transaction data used for billing the cardholder.

Visa will implement the following optional changes for issuers in BASE II original, reversal, dispute response financial, and dispute
response financial reversal transactions:

- Send the cardholder’s billing amount converted to the issuer’s settlement currency in Draft Data, TCR 0, positions 62–73, Destination
Amount
- Send the issuer’s settlement currency code in Draft Data, TCR 0, positions 74–76, Destination Currency Code
- New Field in the V22260 Record – position 68-79, Cardholder Billing Amount in Settlement Currency (V.I.P Full Service Issuers)

- Issuers that choose to receive the cardholder’s billing amount in the settlement currency must modify their systems to support the
existing positions 62–73, Destination Amount converted to the issuer’s settlement currency, and positions 74–76, Destination
Currency Code set to the issuer’s settlement currency code, in Draft Data, TCR 0.

113 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing

4.5 New Issuer TC 33 Record for Payment Account Reference √

Effective immediately, Visa will implement a new optional BASE II TC 33—Payment Account Reference
Report for issuers that will list PAR values that have been assigned by Visa for the issuer.

Issuers can choose to receive daily, weekly, or monthly BASE II TC 33 records that list new PAR values assigned in that period. Issuers
can also receive a TC 33 report with all currently assigned PAR values.

114 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing
Changes to the Visa Token Service to Support Visa Digital
4.6 √
Commerce Transactions

Visa will implement a new TLV Field 34—Electronic Commerce Data in authorization and full financial messages to carry a new
indicator with a value of 01 (Visa digital commerce) in Dataset ID 56, Tag DF21. This value will identify that a token-based e-commerce
or card-on-file request was initiated using Visa Digital Commerce.

Issuers that choose to participate in the Visa Digital Commerce must be aware of the additional changes to TLV Field 34, Dataset ID 56.

For more information about TLV Field 34, Dataset ID 56, refer to Article 4.8, Changes to Support Electronic Commerce Using Authentication Data

115 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing
Changes to Support Enhanced Original Credit Transactions for Plus Recipient
4.7 √
Issuers That Process Visa Products

Effective with the October 2018 release, recipient issuers may optionally support enhanced original credit transactions (OCTs)
for Visa-branded products processed on network 0004 (Plus).

Visa will implement changes to support enhanced OCTs for Visa-branded products sent by acquirers and originators on network 0002
(Visa) and delivered to recipient issuers on network 0004.

116 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing

4.8 Changes to Support Electronic Commerce Using Authentication Data √

Visa will implement the following changes in V.I.P. to support electronic commerce using authentication data:
• Define the following:
- New International Organization for Standardization (ISO) TLV Field 34—Electronic Commerce Data
- New Dataset ID 56—Supplemental Data within TLV Field 34
- New TLV tags within Dataset ID 56
- Tag 9F1F—Consumer Device IP Address
- Tag DF1F—VCAS Score
• Add new processing rules to include the new TLV Field 34—Electronic Commerce Data in 0100 Authorization request and 0200 Full
financial request

Issuers that choose to receive supplemental data must support the new TLV Field 34, Dataset ID 56 that will be used to carry the
consumer device IP address and VCAS score that may be present in the 0100 Authorization request messages. Issuers should also be
aware of the processing rule in Table 4.8.C that will apply to supplemental data.

Testing and activation is required for issuers to implement TLV Field 34 for the first time.

117 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing
Changes to the Visa Token Service to Support Contactless
4.9 √ √
ATM Transactions

Visa will implement changes to enable the use of tokens provisioned by the Visa Token Service (VTS) for contactless ATM transactions.

Acquirers that participate in VTS can submit contactless ATM transactions, and Issuers that participate in VTS must be aware that
contactless ATM transactions may contain a token for certain token types, including all the related token fields.

Transactions must comply with quick Visa Smart Debit/Credit (qVSDC) processing rules. Testing and activation are required to
support contactless ATM transactions with a token.

118 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing

4.10 New V.I.P. Payment Account Reference Inquiry Messages √ √

Visa will implement the following new V.I.P. inquiry and response messages for acquirers and issuers to inquire on a PAR value
associated with a primary account number (PAN) or payment token:
• V.I.P. 0300/0310 Acquirer Payment Account Reference Inquiry and Response
• V.I.P. 0302/0312 Issuer Payment Account Reference Inquiry and Response

Acquirers/Issuers must provide the following in the V.I.P. 0300/0302 inquiry message: (is this necessary?)
• One of the following values:
‐ Primary account number in Field 2—Primary Account Number, or
‐ Token in TLV Field 123, Usage 2, Dataset ID 68, Tag 01
• File update code in Field 91—File Update Code must be 5 (Inquire)
• New file name in Field 101—File Name must be PAR

Acquirers and issuers that submit an inquiry message must be prepared to receive existing TLV Field 56—Customer Related Data,
Dataset ID 01—Account Data, Tag 01—Payment Account Reference and New Tag 02—Payment Account Reference Creation Date in
the response message.

119 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing

5.1 Mandate for Eight-Digit Issuing BIN √ √

Effective with the April 2022 release, Visa will assign eight-digit issuer BINs and will require all endpoints to process using the eight-
digit BIN structure. Each existing six-digit BIN will become 100 eight-digit BINs.

Key points and considerations:

− PAN length will remain the same (i.e. 16 digits for most Visa products)
− Account range length will remain at nine digits
− Each eight-digit BIN will have 10 account ranges versus 1000 account ranges in a six-digit BIN
− The following existing Visa-assigned numeric identifiers will remain as six-digit:
• Acquirer Identifier
• BASE II Core Identifier
• Issuing Identifier
• VSS Processor

120 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing

5.2 Mandate for Support of Eight-Digit Issuing BIN √ √

The Visa payments systems will be updated with the April 2019 release to allow endpoints to start migrating to eight-digit issuer
identification numbers (IINs) required by April 2022.

This article also identifies the following systems and fields that will be impacted by the expansion of Visa-assigned numeric identifiers
effective with the April 2019 release:
• V.I.P. Field 100 to support 11-digit routing IDs
• V.I.P. and BASE II to support 11-digit request for copy routing IDs
• Edit Package
• Dynamic Key Exchange (DKE) messages to support 11-digit routing IDs

121 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing

5.5 Changes to Support Velocity Limits for Account Funding Transactions √

Visa will implement changes to apply default 1-day, 7-day, and 30-day velocity limit checking for cumulative amounts on all
domestic account funding transactions (AFTs). Acquirers must be aware that domestic AFTs that exceed the 1-day, 7-day, or 30-day
default velocity limit checking will be declined with existing response code 12 (Invalid transaction).

Refer to Table 5.5.A for the default velocity limits for domestic AFTs.

122 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing

5.6 Reminder for Acquirers to Deliver Payment Account Reference to Merchants √

Effective with the October 2018 business release, acquirers outside of the Europe region that choose to receive the payment account
reference (PAR) in V.I.P. responses are reminded that they must be able to process a transaction that includes PAR in it and distribute
the value to the merchant.

For more information, refer to VBN dated 8 June 2017, Payment Account Reference Clarifications.

123 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing
Requirement to Include Local Transaction Date and Time in
5.7 √ √
Authorization Messages

With the October 2018 release, Field 12 and Field 13 will be designated as mandatory in 0100 Authorization requests and 0120
Completion advices.

Acquirers are strongly encouraged to send accurate data in Field 12—Time, Local Transaction and Field 13—Date, Local Transaction
in 0100 Authorization messages and 0120 Completion advices. Issuers must be aware that Visa will not reject transactions that do not
contain data in Field 12 and Field 13.

At this time, no new edits will be introduced in VisaNet for Field 12 or Field 13. Existing reject codes for these fields will continue to
apply.

124 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing
√
5.9 New Business Product for V PAY √
(EU only)
Effective with the April 2019 release, Visa will implement changes to introduce a new product, V PAY Business, for small and
medium businesses. This new product is designed for existing V PAY markets.

Acquirers must be aware of the new product ID value of V1 (V PAY Business) that will be used for V PAY markets.

5.10 Changes to Basic Format Original Credit Transactions √

Effective with the April 2019 release, Visa will no long optionally downgrade the business application identifier (BAI) values sent to
recipient issuers that support basic format original credit transactions (OCTs). Issuers that support basic format OCTs must support all
BAI values sent from the originator.

125 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing

5.11 Requirement to Support 3-D Secure √ √

Effective with the April 2019 release, acquirers that participate in 3-D Secure (3DS) and support card-on-file, e-commerce, or
application-based e-commerce transactions for PAN must be prepared to support electronic commerce indicator (ECI) with
non-authenticated security transaction along with CAVV data.

Acquirers must be prepared to support the following:

• ECI value of 07 (Non-authenticated security transaction) in existing Field 60.8 in authorization request messages
• ECI value of 7 (Non-authenticated security transaction) in existing Field 63.6 in full financial request messages
• CAVV data in existing Field 126.9—CAVV Data, Usage 3: 3-D Secure CAVV, Revised Format in authorization and full financial
request messages
• ECI value of 7 (Non-authenticated security transaction) in BASE II Draft Data

Issuers will continue to have the option to receive the following existing fields to support CAVV processing:
• Field 60.8—Mail/Phone/Electronic Commerce and Payment Indicator in the authorization request message
• CAVV data in Usage 2: 3-D Secure CAVV or Usage 3: 3-D Secure CAVV, Revised Format of Field 126.9—CAVV Data

126 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing

5.12 Increase of File Size for ARDEF and Routing Tables √ √

Visa is anticipating an increase in the size of the Edit Package ARDEF Table and Visa Routing Tables for Visa product account ranges
as the Visa Token Service basic issuer participation service is rolled out. Endpoints must be aware of this anticipated increase when
preforming capacity planning activities.

127 | Operational Support Client Forum | July – August 2018 Visa Confidential
Additional Articles
Article Title Acquiring Issuing
Requirement to Support Domestic Account Funding and Original Credit
6.1.2 √
Transactions in Japan

Effective 1000 GMT 12 October 2018 CPD 13 October 2018, Visa requires debit issuers in Japan to support domestic account
funding transactions (AFTs), domestic enhanced original credit transactions (OCTs), and fast funds processing OCTs.

6.5.1 Mandate to Support Cashback for Issuers in Malaysia √

Effective with the April 2019 release, all issuers in Malaysia must support VisaNet Cashback Service for qualifying domestic debit card
transactions. Issuers must not approve any portion of the cashback amount during a partial authorization approval.

128 | Operational Support Client Forum | July – August 2018 Visa Confidential