V.I.P.

System SMS ATM Processing

Specifications
INTERNATIONAL
V.I.P. System
Effective: 1 June 2018

Visa Supplemental Requirements

© 1999 - 2018 Visa. All Rights Reserved. 0839–32

Visa Confidential
Important Note on Confidentiality and Copyright

The Visa Confidential label signifies that the information in this document is confidential
and proprietary to Visa and is intended for use only by Visa Clients subject to the
restrictionsand feedback provisions in the Visa Core Rules and Visa Product and Service
Rules, non-Client Third Party Processors that have an executed and valid VisaNet Letter
of Agreement on file with Visa, and other third parties that have a current participation
agreement with Visa that covers confidentiality of the information contained herein and
Visa’s use of feedback.

This document is protected by copyright restricting its use, copying, distribution, and
decompilation. No part of this document may be reproduced in any form by any means
without prior written authorization of Visa.

Visa and other trademarks are trademarks or registered trademarks of Visa.

All other product names mentioned herein are the trademarks of their respective owners.

About Visa Supplemental Documents

This document is a supplement of the Visa Core Rules and Visa Product and Service
Rules. In the event of any conflict between any content in this document, any document
referenced herein, any exhibit to this document, or any communications concerning this
document, and any content in the Visa Core Rules and Visa Product and Service Rules, the
Visa Core Rules and Visa Product and Service Rules shall govern and control.

THIS PUBLICATION COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL

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

If you have technical questions or questions regarding a Visa service or questions about
this document, please contact your Visa representative.
Contents

About This Manual............................................................................................1

Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Organization of This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Document Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Documentation Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Information Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Report Samples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

More Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Chapter 1 • Single Message System Overview

1.1 VisaNet Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

1.2 VisaNet Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

1.2.1 VisaNet Integrated Payment (V.I.P.) System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

1.2.2 BASE I System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

1.2.3 Single Message System (SMS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

1.2.4 BASE II System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5

1.2.5 VisaNet Settlement Service (VSS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5

1.3 Common Member Interface (CMI) and Interface Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7

1.4 SMS Processing Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7

1.4.1 SMS ATM Online Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7

1.4.2 Stand-In Processing (STIP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8

1.4.3 End-of-Day Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8

1.5 SMS ATM Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications i
 Contents

1.5.1 SMS Acquirers and Issuers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9

1.5.2 Dual-Message Acquirers and Issuers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9

1.6 SMS Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10

1.6.1 Routing Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10

1.6.1.1 ATM/POS Split Routing Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10

1.6.1.2 Gateway Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11

1.6.1.3 PIN/No-PIN Split Routing Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11

1.6.1.4 Priority Routing Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11

1.6.2 Online Request Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-12

1.6.2.1 Visa Advanced Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-12

1.6.2.2 Advice Retrieval Service—SMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-12

1.6.2.3 Automatic Cardholder Database Update (Auto-CDB) Service. . . . . . . . . . . .1-12

1.6.2.4 Card Verification Value (CVV) Service, the Integrated Chip

Card Card Verification Value (iCVV), and the Card Verification
Value 2 (CVV2) Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-12

1.6.2.5 Card Verification Value 2 (CVV2) Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-15

1.6.2.6 Deferred Clearing Advice File (DCAF) Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-15

1.6.2.7 Flexible Times for Online Delivery of Advices From BASE II Endpoints.1-15

1.6.2.8 Dynamic Key Exchange (DKE) Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-16

1.6.2.9 Merchant Initiated Transactions (MIT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-16

1.6.2.10 MIT Categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-17

1.6.2.11 Mobile Location Confirmation Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-20

1.6.2.12 Multicurrency Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-20

1.6.2.13 PIN Verification Service (PVS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-20

1.6.2.14 Prepaid Activation, Load, and Partial Approval Processing. . . . . . . . . . . . . . . .1-21

1.6.2.15 Contactless Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-21

1.6.2.16 Visa Smart Debit/Smart Credit (VSDC) Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-22

1.6.2.17 Visa iCVV Convert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-23

1.6.2.18 VSDC PIN Management Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-24

1.6.2.19 Merchant Verification Value (MVV) Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-24

1.6.2.20 Mobile Location Confirmation Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-25

ii Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
 Contents

1.6.3 Risk Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-25

1.6.3.1 Fraud Reporting System (FRS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-25

1.6.3.2 Visa Transaction Advisor E-Commerce Scoring Service. . . . . . . . . . . . . . . . . . . . .1-25

1.6.4 Additional Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-26

1.6.4.1 Visa Mobile Prepaid (VMP) Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-26

1.7 Fees and Charges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-26

1.7.1 Client-to-Client Fees. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-26

1.7.1.1 Interchange Reimbursement Fees and Cash Disbursement Fees. . . . . . . .1-26

1.7.2 Fees Assessed by Visa. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-28

1.7.2.1 International Acquiring Fees (IAFs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-28

1.7.2.2 Special Handling Fees. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-28

1.7.3 Charges Assessed by Visa. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-28

1.7.3.1 Transaction Processing Charges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-29

1.7.3.2 Administrative and Service Charges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-29

1.7.3.3 Currency Conversion Charges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-29

1.7.4 Reporting Fees and Charges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-29

1.7.4.1 Daily Fee Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-29

1.7.4.2 Monthly Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-29

Chapter 2 • SMS Transactions

2.1 Transaction Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

2.1.1 Cardholder Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2

2.1.2 System-Generated Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3

2.1.2.1 Reversals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3

2.1.2.2 Cash Disbursement Adjustments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4

2.1.3 Exception Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4

2.1.4 Fee-Related Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5

2.1.5 Reconciliation Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5

2.1.6 File Maintenance Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5

2.1.7 Administrative Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6

2.1.8 Network Management Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications iii
 Contents

2.1.9 VSDC Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7

2.2 Transaction Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7

2.3 Message Integrity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8

2.3.1 The Inter-Task Table (ITT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9

2.3.1.1 Transaction Identifier (TID). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9

2.3.2 Message Validity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10

2.3.3 Transaction Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10

2.3.4 Account Number Consistency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10

2.3.5 Amount Consistency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10

2.3.6 Processing Duplicate Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10

Chapter 3 • SMS Participation Requirements

3.1 General Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

3.1.1 Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2

3.2 Acquirer System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2

3.2.1 Online Transaction Processing Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2

3.2.2 Required Capabilities for Acquirers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3

3.3 Acquirer Service Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3

3.4 Issuer System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4

3.4.1 Required Capabilities for Issuers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5

3.5 Issuer Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6

Chapter 4 • Message Types and Flows

4.1 Standard Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

4.1.1 Cardholder Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2

4.1.1.1 Purchase and Cash Disbursement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2

4.1.1.2 Balance Inquiry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3

4.1.1.3 Account Transfer (Domestic ATM Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-5

4.1.2 System-Generated Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-6

4.1.2.1 Reversal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-6

4.1.2.2 Cash Disbursement Adjustment—Misdispense (ATM Only). . . . . . . . . . . . . . . . .4-8

4.1.3 Exception Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-9

iv Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
 Contents

4.1.3.1 Adjustments Including Adjusting Duplicates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-10

4.1.3.2 Chargeback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-11

4.1.3.3 Chargeback Reversal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-12

4.1.3.4 Representment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-13

4.1.3.5 Fee-Related Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-14

4.1.4 Reconciliation Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-16

4.1.4.1 Funds Transfer Totals Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-16

4.1.4.2 Reconciliation Advice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-17

4.1.5 File Maintenance Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-18

4.1.5.1 Online File Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-18

4.1.5.2 Automatic Cardholder Database Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-19

4.1.6 Administrative Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-20

4.1.6.1 Free-Text Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-20

4.1.6.2 Funds Transfer Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-22

4.1.6.3 Online Fraud Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-23

4.1.7 Network Management Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-24

4.1.7.1 Sign-On and Sign-Off Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-24

4.1.7.2 Echo Test Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-26

4.1.7.3 Recovery Sign-On and Sign-Off Message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-27

4.1.7.4 Dynamic Key Exchange. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-29

4.2 Exception Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-32

4.2.1 Financial Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-32

4.2.1.1 Issuer Unavailable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-32

4.2.1.2 Issuer Unavailable—Account Listed on Exception File. . . . . . . . . . . . . . . . . . . . . .4-34

4.2.1.3 Issuer Fails to Respond. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-36

4.2.1.4 Issuer Responds Late. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-37

4.2.1.5 Approval Response Cannot Be Delivered to the Acquirer. . . . . . . . . . . . . . . . .4-40

4.2.1.6 Decline Response Cannot Be Delivered to the Acquirer. . . . . . . . . . . . . . . . . . .4-41

4.2.2 Reversals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-42

4.2.2.1 Reversal—Advice Response Cannot Be Delivered to the Acquirer. . . . . .4-42

4.2.2.2 Reversal—Issuer Unavailable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-43

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications v
 Contents

4.2.2.3 Reversal—Unsolicited. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-45

4.2.3 Exception Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-46

4.2.3.1 Adjustment or Representment—Issuer Unavailable. . . . . . . . . . . . . . . . . . . . . . . . .4-46

4.2.3.2 Adjustment or Representment—Acquirer Unavailable After Advice. . . .4-47

4.2.3.3 Chargeback—Acquirer Unavailable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-50

4.2.3.4 Chargeback—Issuer Unavailable After Chargeback. . . . . . . . . . . . . . . . . . . . . . . . . .4-51

Chapter 5 • Multicurrency Support

5.1 Currencies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1

5.2 How Currency Conversion Works. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2

5.3 What the Issuer Receives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-2

5.4 Variations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3

5.5 Decimal Places in Amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3

5.6 Currency Precision Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3

5.6.1 Adding a Decimal Position. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-4

5.6.2 Removing a Decimal Position. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-4

5.7 Clients Not Participating in the Multicurrency Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5

5.8 Multicurrency Field Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5

Chapter 6 • Stand-In, CVV, and CVV2 Processing

6.1 Stand-In Processing (STIP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1

6.1.1 Conditions Requiring Stand-In Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1

6.1.2 Issuer STIP Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2

6.1.3 Acquirer STIP Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2

6.1.4 STIP Authorization Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2

6.1.4.1 VSDC Chip Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-3

6.1.4.2 Expiration Date Editing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-4

6.1.4.3 Retrieving BIN-Level Default STIP Response Codes. . . . . . . . . . . . . . . . . . . . . . . . . . .6-4

6.1.4.4 Ranking Response Codes and Identifying Highest Priority Code. . . . . . . . .6-4

6.1.4.5 Exception File Checking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-4

6.1.4.6 Activity Checking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-5

6.1.4.7 Identifying Highest Priority Response Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-7

vi Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
 Contents

6.1.4.8 Creating an Advice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-7

6.1.4.9 Retrieving Default CVV Response Code for Request. . . . . . . . . . . . . . . . . . . . . . . . . .6-7

6.1.5 SMS Functions in Support of STIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-7

6.1.5.1 Account Number Editing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-7

6.1.5.2 Invalid Country Editing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-8

6.1.5.3 Cardholder Database Checking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-8

6.1.5.4 Currency Conversion and Invalid Amounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-8

6.1.5.5 Destination Not Available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-8

6.1.5.6 Issuer Not Found. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9

6.1.5.7 Invalid Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9

6.1.5.8 PIN Translation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9

6.1.5.9 PIN Verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9

6.1.5.10 9240 and 9242 FRS Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-11

6.1.6 Assigning a Response Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-12

6.1.7 Updating the Activity File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-12

6.1.8 Reversal Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-13

6.1.8.1 Updating the Activity File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-13

6.1.8.2 Creating an Advice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-13

6.1.9 Acquirer Stand-In Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-14

6.2 Advice File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-14

6.2.1 File Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-14

6.2.2 Unique Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-15

6.2.3 Maintenance and Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-15

6.2.4 Purging Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-15

6.2.5 Recovering Advices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-15

6.2.5.1 Timing of Recovery Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-15

6.2.5.2 Advice Recovery Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-16

6.2.5.3 Advice Flags in the Message Header. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-18

6.3 Card Verification Value (CVV) Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-18

6.4 Card Verification Value 2 (CVV2) Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-19

6.5 Cardholder Authentication Verification Value (CAVV) Verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-19

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications vii
 Contents

6.6 Other Risk Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-22

Chapter 7 • Routing
7.1 Transaction Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-1

7.2 Routing Options, Tables, and Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2

7.2.1 Routing Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2

7.2.1.1 Visa/Plus ATM Routing Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2

7.2.2 Routing Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3

7.2.2.1 ATM Routing Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3

7.2.3 Routing Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-4

7.2.3.1 Priority Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-4

7.2.3.2 Split Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-4

Chapter 8 • Settlement and Reconciliation

8.1 Settlement Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-1

8.1.1 Transactions Qualifying for Settlement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-1

8.1.2 Settlement Day. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2

8.1.3 Accumulation and Reconciliation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2

8.1.4 Clearing and Settlement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-3

8.1.4.1 Valuation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-4

8.2 VisaNet Settlement Service (VSS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-4

8.2.1 Settlement Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-5

8.2.2 Settlement Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-5

8.2.3 Settlement Schedule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-5

8.2.4 Alternately Routed Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-6

8.2.5 Funds Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-7

8.2.5.1 VSS 0620 Funds Transfer Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-7

8.2.5.2 Movement of Funds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-7

8.2.5.3 Funds Transfer Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-7

8.2.6 VSS Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-7

8.2.6.1 Layouts and Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-7

8.2.6.2 Delivery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-7

viii Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
 Contents

8.2.7 Reconciliation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-8

8.2.7.1 Processors and VSS Settlement Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-8

8.2.7.2 Reports and Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-9

8.2.7.3 SMS Reconciliation Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-10

8.3 For More Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-10

Chapter 9 • Client-to-Visa Connection Options

9.1 Direct Exchange. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-1

9.2 Extended Access Servers (EA Servers). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2

9.3 VisaNet Connection Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2

9.3.1 VisaNet Connection Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2

9.3.1.1 VisaNet Connection File Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-2

9.3.2 File Transfer Connectivity Between VisaNet Connection and Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3

9.3.2.1 Client Host Processing of Files Received From VisaNet Connection. . . . .9-3

9.3.3 VisaNet Connection With V.I.P. and BASE II Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4

9.3.4 VisaNet Connection With V.I.P. and DAS Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4

9.4 Report and File Delivery Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4

9.4.1 VSS Report Delivery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-5

9.4.2 More Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-5

9.5 SMS Functions To Be Supported. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-5

9.5.1 Online Transaction Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-5

9.5.1.1 Online Message Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-6

9.5.1.2 Online Transaction Delivery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-6

9.5.2 Exception Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-6

9.5.2.1 Visa Resolve Online (VROL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-6

Chapter 10 • Considerations for Dual-Message Acquirers

10.1 CPS/ATM vs. V.I.P. SMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-1

10.2 Dual-Message CPS/ATM vs. V.I.P. SMS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-2

10.2.1 Online Transaction Processing Differences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-4

10.2.1.1 Message Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-4

10.2.1.2 Message Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-4

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications ix
 Contents

10.2.1.3 Network ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-4

10.2.1.4 Reversals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-5

10.2.1.5 Partial Dispense. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-5

10.2.1.6 CPS Transaction Identifier. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-5

10.2.1.7 CPS Authorization Characteristics Indicator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-5

10.2.1.8 CPS Validation Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-5

10.2.2 Clearing and Settlement Differences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-6

10.2.2.1 Clearing and Settlement Step. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-7

10.2.2.2 Reconciliation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-7

10.2.2.3 Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-7

10.2.3 Exception Handling Differences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-7

10.2.3.1 Chargebacks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-8

10.2.3.2 Representments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-8

10.2.3.3 Back-Office Adjustments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-8

10.3 Recommendation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-8

Appendix A • ATM Processing Integration

A.1 ATM Transaction Standardization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-1

A.1.1 Client Impacts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .IX-1

x Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Figures

1-1 The VisaNet Communications Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

1-2 VisaNet Software System Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5
1-3 VSS Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6
1-4 Typical ATM Online Message Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8
4-1 Cash Disbursement Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3
4-2 Balance Inquiry Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-4
4-3 Account Transfer Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-6
4-4 Reversal Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-8
4-5 Cash Disbursement Adjustment Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-9
4-6 Adjustment (Back-Office) Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-11
4-7 Chargeback Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-12
4-8 Chargeback Reversal Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-13
4-9 Representment Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-14
4-10 Fee-Related Transaction Flow (Acquirer-Initiated). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-15
4-11 Fee-Related Transaction Flow (Issuer-Initiated). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-16
4-12 Funds Transfer Totals Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-17
4-13 Reconciliation Advice Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-18
4-14 Online File Maintenance Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-19
4-15 Auto-CDB File Maintenance Transaction Flow (Visa Only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-20
4-16 Free-Text Message Transaction Flow (Acquirer to Issuer). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-21
4-17 Free-Text Message Transaction Flow (Issuer to Acquirer). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-22
4-18 Funds Transfer Message Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-23
4-19 Fraud Reporting Message Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-24
4-20 Sign-On and Sign-Off Message Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-25
4-21 Echo Test Message Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-27
4-22 Recovery Sign-On and Sign-Off Message Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-29
4-23 Dynamic Key Exchange Message Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-31
4-24 Issuer Unavailable Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-33
4-25 Issuer Unavailable—Account Listed on Exception File Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-35
4-26 Issuer Fails to Respond Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-37
4-27 Issuer Responds Late Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-39
4-28 Approval Response Cannot Be Delivered to the Acquirer
Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-41
4-29 Decline Response Cannot Be Delivered to the Acquirer Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-42
4-30 Reversal—Advice Response Cannot Be Delivered to the Acquirer Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . .4-43
4-31 Reversal—Issuer Unavailable Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-45
4-32 Reversal—Unsolicited Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-46

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications xi
 Figures

4-33 Adjustment or Representment—Issuer Unavailable Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-47

4-34 Adjustment or Representment—Acquirer Unavailable Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-49
4-35 Chargeback—Acquirer Unavailable Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-51
4-36 Chargeback—Issuer Unavailable After Chargeback Transaction Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-53
5-1 Example of One-Decimal Position Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-4
5-2 Example of Two-Decimal Position Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5
5-3 Cash Disbursement With Balance Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-8
5-4 Adjustment Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-9
5-5 Representment Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-11
5-6 Balance Inquiry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-12
5-7 Reversal Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-13
5-8 Chargeback and Chargeback Reversal Transaction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-14
6-1 Advice Recovery Process Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-17
8-1 Overview of Online Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-3
8-2 VisaNet Settlement Service (VSS) Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-4
8-3 Settlement Hierarchy Example—Processor Performing Funds Transfer for All Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . .8-9

xii Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Tables

1 Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
2 V.I.P. System Manual Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
1-1 Incremental Authorization Transaction—Message Reason Code 3900. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-17
1-2 Resubmission Transaction—Message Reason Code 3901. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-17
1-3 Delayed Charges Transaction—Message Reason Code 3902. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-17
1-4 Reauthorization Transaction—Message Reason Code 3903. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-18
1-5 No-Show Transaction—Message Reason Code 3904. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-18
1-6 Installment Payment Transaction—Value I in POS Environment Field 126.13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-19
1-7 Recurring Payment Transaction—Value R in POS Environment Field 126.13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-19
1-8 Unscheduled COF Transaction—Value C in POS Environment Field 126.13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-19
2-1 ATM Transaction Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1
2-2 Visa ATM and Plus Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8
3-1 Required Transaction Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2
3-2 ATM Acquirer Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
3-3 ATM Issuer Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6
5-1 Field 63.13 Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-4
6-1 Acquirer Advices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-14
6-2 Signing On and Off Advice Recovery Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-15
7-1 SMS Transaction Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-1
7-2 ATM Routing Table and Service Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2
8-1 Settlement Cutoff Timing—SMS and BASE II Transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-5
8-2 Daily Settlement Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-6
8-3 Timing of Settlement Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-6
9-1 VisaNet Connection File Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3
10-1 Example of Savings Comparison. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-2
10-2 Online Transaction Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-3
10-3 Clearing and Settlement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-3
10-4 Exception Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-3
A-1 ATM Transaction Standardization Option. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications xiii
 Tables

THIS PAGE INTENTIONALLY LEFT BLANK.

xiv Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
About This Manual

V.I.P. System International SMS ATM Processing Specifications contains processing

specifications for the V.I.P. International SMS ATM Service. The V.I.P. International SMS ATM
Service is an optional service available to issuers and to acquirers worldwide.

This manual contains:

• Suitable technical detail for Visa and Plus issuers and acquirers to plan the systems
development efforts needed to implement the Single Message System (SMS) Service
for ATM transaction processing.
• Information about online financial processing of ATM transactions.
The first three chapters describe the service and processing requirements from a business
and a functional perspective. The next group of chapters contains detailed information
about message types, processing considerations, related services, and VisaNet connection
methods. The last two chapters address SMS ATM issuers also processing deferred
clearing transactions, and Visa and Plus acquirers considering making SMS ATM or
Custom Payment Service (CPS)/ATM changes to their systems.

A companion manual, V.I.P. System SMS ATM Technical Specifications, Volume 1 and
Volume 2, contains detailed specifications for message formats, field descriptions, codes,
and files.

Audience
The processing specifications in this manual are intended for technical and systems
professionals responsible for implementing SMS software for Visa and Plus ATM
processing and for those managing the individual ATM programs after they are installed.

Organization of This Manual

This manual contains the following chapters:

Chapter 1, Single Message System Overview—Provides a high-level description of

the Single Message System (SMS) and identifies related SMS ATM Service features and
services.

Chapter 2, SMS Transactions—Describes the ATM transactions, transaction sets,

and methods for maintaining message integrity.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1
Document Conventions About This Manual

Chapter 3, SMS Participation Requirements—Summarizes the requirements and the

options for SMS ATM participants, from issuer and acquirer perspectives.

Chapter 4, Message Types and Flows—Provides descriptions and message flow diagrams
for SMS ATM transactions.

Chapter 5, Multicurrency Support—Explains how V.I.P. performs currency conversion.

Chapter 6, Stand-In, CVV, and CVV2 Processing—Provides a detailed description of

stand-in processing (STIP) and card verification services available to SMS ATM participants.
The chapter summarizes additional risk services and lists references to sources of
additional information.

Chapter 7, Routing—Contains information about ATM transaction routing and routing

tables.

Chapter 8, Settlement and Reconciliation—Contains information about the settlement

and reconciliation process, including the accumulation and advice-generation process,
settlement relationships, settlement schedules, funds transfer, reporting, and reconciliation.

Chapter 9, Client-to-Visa Connection Options—Contains information about SMS

connectivity requirements and options.

Chapter 10, Considerations for Dual-Message Acquirers—Provides information for

acquirers considering changing their systems to process Custom Payment Service
(CPS)/ATM or single-message transactions.

Appendix A, ATM Processing Integration—Contains a description of the way in which

SMS ATM participants can format and process all ATM transactions without distinguishing
between Visa ATM and Plus ATM transactions.

Document Conventions
Table 1 Conventions

Convention Purpose
boldface Extra emphasis (stronger than italics); field values, codes.

EXAMPLE Identifies what accompanying text describes or explains.

IMPORTANT Highlights information in text.

italics Document titles; emphasis; variables; terms or acronyms being defined.
Section names; first instance of word used in unconventional
text in quote marks
or technical context.
text in Courier New
Uniform Resource Locator (URL)s and email addresses.
font

NOTE Provides details about preceding topic.

n/a Not applicable.
shaded illustrations Systems or procedures not directly involved in process being illustrated.
white boxes in flow
Request messages.
diagrams
shaded boxes in flow
Response messages.
diagrams

2 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
About This Manual Documentation Descriptions

Table 1 Conventions (continued)

Convention Purpose
dotted line boxes in flow
Advice messages.
diagrams

Documentation Descriptions
VisaNet Integrated Payment (V.I.P.) System Overview, V.I.P. System Services, and V.I.P. System
Reports, apply to BASE I and Single Message System (SMS) processing.

V.I.P. System BASE I Processing Specifications and V.I.P. System BASE I Technical Specifications,
Volume 1 and Volume 2, are specific to BASE I.

For SMS,Visa U.S.A. (U.S.) region processing specifications for Automated Teller Machine
(ATM), Interlink, and Point of Sale (POS) are consolidated in V.I.P. System SMS Processing
Specifications (U.S.). Different manuals for ATM and POS are available for international
clients.

Table 2 V.I.P. System Manual Descriptions

General Information
V.I.P. System Overview

Describes VisaNet and components, connection methods, processing concepts, requirements,

and options. Defines V.I.P., BASE I, and SMS, Direct Exchange (DEX) and Extended Access Server
(EAS), issuer and acquirer responsibilities, and VisaNet Interchange Center (VIC) operations.
Introduces V.I.P. services.

Doc ID 0851-33
V.I.P. System Reports

Provides samples.

Doc ID 0852-32
V.I.P. System Services, Volume 1

Describes available services. Descriptions include processing requirements, options, features,

key message fields, and message flows.

Part 1: V.I.P. Basics

Part 2: Routing Services
Part 3: Risk Management Services
Part 4: Visa Secure Electronic Commerce (VSEC) Services
Part 5: Chip Card Services

Doc ID 0853A-32
V.I.P. System Services, Volume 2

Describes available services. Descriptions include processing requirements, options, features,

key message fields, and message flows.

Part 6: Authorization Database Files and Services

Part 7: Authorization Services

Doc ID 0853B-32

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 3
Documentation Descriptions About This Manual

Table 2 V.I.P. System Manual Descriptions (continued)

BASE I
V.I.P. System BASE I Processing Specifications

Describes BASE I processing, including message types, processing considerations, related services,
and VisaNet connection methods.

Doc ID 0847-32
V.I.P. System BASE I Technical Specifications, Volume 1

Defines technical specifications of BASE I processing and fields.

Doc ID 0844A-33
V.I.P. System BASE I Technical Specifications, Volume 2

Defines technical specifications of BASE I processing, message formats, and file specifications.

Doc ID 0844B-33
Interlink
V.I.P. System SMS Processing Specifications (U.S.)

Contains SMS information, including message types, processing considerations, connection

methods, and services for Interlink, Visa and Plus ATM, Visa POS, and Visa Electron.

Doc ID 0857-32
V.I.P. System SMS Interlink Technical Specifications

Describes message formats, field descriptions, and file specifications for Interlink.

Doc ID 0866-31
SMS ATM
V.I.P. System SMS Processing Specifications (U.S.)

Contains SMS information, including message types, processing considerations, connection

methods, and services for Visa and Plus ATM, Interlink, Visa POS, and Visa Electron for U.S. region
clients.

Doc ID 0857-32
V.I.P. System International SMS ATM Processing Specifications

Contains SMS ATM information, including message types, processing considerations, connection
methods, and services for clients outside U.S. region.

Doc ID 0839-32
V.I.P. System SMS ATM Technical Specifications, Volume 1

Contains field descriptions for ATM.

Doc ID 0868A-31
V.I.P. System SMS ATM Technical Specifications, Volume 2

Contains message formats and file specifications for ATM.

Doc ID 0868B-31

4 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
About This Manual Report Samples

Table 2 V.I.P. System Manual Descriptions (continued)

SMS POS
V.I.P. System SMS Processing Specifications (U.S.)

Contains SMS information, including message types, processing considerations, connection

methods, and services for Visa POS, Visa Electron, Visa and Plus ATM, and Interlink for U.S. region
clients.

Doc ID 0857-32
V.I.P. System International SMS POS (Visa & Visa Electron) Processing Specifications

Contains SMS POS information, including message types, processing considerations, connection
methods, and services for clients outside U.S. region.

Doc ID 0835-32
V.I.P. System SMS POS (Visa & Visa Electron) Technical Specifications, Volume 1

Describes fields for Visa POS and Visa Electron.

Doc ID 0869A-32
V.I.P. System SMS POS (Visa & Visa Electron) Technical Specifications, Volume 2

Describes message formats and file specifications for Visa POS and Visa Electron.

Doc ID 0869B-31

Information Sources
Information is analyzed, rewritten, and reorganized. Technical staff and subject matter
experts review and verify updates. Approved comments and change requests received
from clients and Visa staff are incorporated.

V.I.P. Manuals
See Table 2.

VisaNet Business Enhancements Global Technical Letters and

Implementation Guides
V.I.P. System International SMS ATM Processing Specifications includes information from
the April 2018 and July 2018 VisaNet Business Enhancements Global Technical Letter and
Implementation Guide (GTLIG), Version 3.0, effective 08 March 2018.

Report Samples
• V.I.P. System Reports
• VisaNet Settlement Service (VSS) User's Guide, Volume 2, Reports

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 5
Related Publications About This Manual

More Information
Visa provides product and service documentation. Clients get guides from Visa
representatives. If you have comments or questions about this document or technical
questions about Visa services or capabilities, contact your Visa representative.

Related Publications
Visa Global ATM Planning Guide contains details about Visa and Plus International ATM
Program. It includes program overview, business requirements, optional services,
risk management, processing options, testing procedures, and back-office management.

Visa Rules

Visa Core Rules and Visa Product and Service Rules contain Visa Rules.

Deferred Clearing Advice File (DCAF) Service

V.I.P. System Services, Volume 2.

PIN Management Requirements

Payment Card Industry PIN Security Requirements Manual: Contains requirements for
managing, processing, and transmitting PIN data.

PIN Entry Device (PED) Security Requirements and Management Procedures:

• Payment Card Industry Encrypting PIN Pad (EPP) Security Requirements Manual
• Payment Card Industry POS PIN Entry Device (PED) Security Requirements Manual

Risk Management Services

Card Recovery Bulletin Service User's Guide

Fraud Reporting Service (FRS) User's Guide

Issuer's Clearinghouse Service User's Guide

Risk Management Process Guide

V.I.P. System Services, Volume 1

Visa Fraud Monitoring Program Guide

Visa Risk Manager

Security

Payment Technology Standards Manual—Contains standards for PINs and encoding data
on Visa payment form factors.

6 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
About This Manual Related Publications

Visa Extended Access Servers (EA Servers)

Extended Access Administration and Installation Guide

Extended Access Management Installation Guide

Extended Access Management Operators Guide

Extended Access Security Administration Guide

Extended Access Server Endpoint Guide

Visa Extended Access Server Endpoint Guide

Visa Incentive Network (VIN)

Credit Rewards Key Implementation Tasks and Best Practices

Credit Rewards: Visa Incentive Network and Credit Interchange Frequently Asked Questions

Visa Incentive Network Member Implementation Guide

Visa Incentive Network Service Description

Visa Signature Registration Toolkit

Visa Traditional Rewards Registration Toolkit

Visa Resolve Online (VROL)

Visa Resolve Online Administrator's Guide

Visa Resolve Online Bulk Systems Interface Development Guide

Visa Resolve Online Member Implementation Guide

Visa Resolve Online Real-Time Systems Interface Development Guide

Visa Resolve Online Reference Manual

Visa Resolve Online User's Guide

Visa Smart Debit/Smart Credit (VSDC) Service

V.I.P. System Services, Volume 1—Contains service description.

Europay, MasterCard, Visa (EMV) Specifications, United States Dollar (USD$)EMV '96
Version 3.1.1 and EMV 2000 Version 4.0—Contain industry standards for chip card and
terminal interaction: www.emvco.com.

Visa Integrated Circuit Card Specifications (VIS)—Contains technical specifications for Visa
Smart Debit/Credit (VSDC) card application, describing VSDC transaction functionality
and flow.

Visa Smart Debit and Credit Member Implementation Guide for Acquirers—Provides
guidelines for acquirers implementing VSDC programs.

Visa Smart Debit and Credit Member Implementation Guide for Issuers—Provides guidelines
for issuers implementing VSDC programs.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 7
Related Publications About This Manual

Visa Smart Debit and Credit Planning Guide—Helps clients plan VSDC programs and
migration strategies.

Visa Smart Debit and Visa Smart Credit Service Description—Describes VSDC program
features and benefits.

Visa Smart Debit/Visa Smart Credit System Technical Manual—Provides information for
clients and Visa staff implementing and operating VSDC programs.

Miscellaneous Systems and Services

Authorization Gateway Service Cross-Reference Guide—Includes field-by-field data transfer

descriptions between V.I.P.-format dual-message transactions, and American Express- and
Mastercard-format transactions.

V.I.P. System Services, Volume 1 and Volume 2

Visa Global ATM Planning Guide—Includes program overview, business requirements,

optional services, risk management, processing options, testing procedures,
and back-office management for Visa and Plus International ATM Program.

Visa Information System User's Guide

Visa Test System—V.I.P. User's Guide

VisaNet Settlement Service (VSS) User's Guide, Volume 1, Specifications

VisaNet Settlement Service (VSS) User's Guide, Volume 2, Reports

8 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
 Single Message System Overview 1
The V.I.P. Single Message System (SMS) allows clients worldwide to process point-of-sale
and point-of-service (POS) transactions and automated teller machine (ATM) transactions
using one, single connection to VisaNet.

VisaNet supports SMS for the following cards in all regions (except as noted below):
• Visa cards
• Visa Electron cards
• Cards bearing the Plus mark
• Cards bearing the Interlink or the Visa Interlink mark (Asia-Pacific [AP], Latin America
and Caribbean [LAC], Visa Canada, and Visa U.S.A. regions only)

VisaNet also supports some non-Visa products in some countries.

SMS accepts all VisaNet messages from acquirers and from issuers. Clients can use a single
connection for authorization, clearing, settlement, exception, and administrative messages.

Understanding SMS requires a basic understanding of VisaNet and the interaction of

its system components. This chapter provides a groundwork for understanding SMS
information, including:
• A brief description of the VisaNet network and of its major systems.
• An overview of SMS message processing and SMS transactions.
• Brief summaries of related services.

A complete overview of VisaNet and of the V.I.P. System appears in the V.I.P. System
Overview.

1.1 VisaNet Network

VisaNet is the Visa transaction processing network, supporting transactions routed among
acquirers and issuers in Visa regions. VisaNet applies to the network’s hardware, software,
and communications components and facilities, and client regional systems and networks.

Main components of VisaNet are:

• VisaNet Interchange Centers (VICs).
• VisaNet Communications Network.
• VisaNet connection methods, such as Direct Exchange (DEX), and Visa Extended Access
Servers (EA Servers).

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1-1
VisaNet Network Chapter 1: Single Message System Overview

NOTE
Clients in the Visa U.S.A. (U.S.) region access VisaNet through DEX. Clients in other Visa regions use DEX
or EA Servers.

• Processing Centers.
VisaNet Interchange Centers (VICs)—VICs are Visa data processing centers that house
computer systems performing VisaNet transaction processing and serve as control
points for telecommunications facilities of VisaNet. VisaNet connects clients to the
closest VIC. If one VIC experiences system disturbances interrupting system processing,
VisaNet automatically routes clients' transactions to another VIC.

VICs house BASE I as a component of the VisaNet Integrated Payment (V.I.P.) System,
the main Visa transaction processing system. Two of the VICs house the Single Message
System (SMS) as a software component of V.I.P.

VisaNet Communications Network—Visa operates telecommunications lines and

facilities worldwide to link systems users to VICs and thus to each other.

VisaNet Connection Methods—Visa provides methods for connecting to VisaNet for

transaction processing:
• Direct Exchange Network (DEX)
DEX provides clients one network connection for message processing and file delivery.
DEX components are:
- Visa Message Gateway handles online transaction processing, resides at VICs, and
supports V.I.P. messages. It is a routing “switch” for V.I.P. transactions and controls
traffic between VisaNet connections and VICs.
- Open File Delivery (OFD) Service handles delivery of Automated Clearing House (ACH)
data, BASE II data, Point-of-Sale Authorization (POSA) File, and various reports and
raw data.
• Visa Extended Access Servers (EA Servers)
EA Servers perform authorization routing, file staging, and delivery services, and provide
secure connectivity to VisaNet.
EA Servers allow accessibility and flexibility for customization. Their modular interface
adapts to front-end systems and integrates standard, off-the-shelf components clients
can scale to meet service needs.
Clients can choose options for receiving reports and raw data and routing files.

Options vary by region.

Processing Center—Processing centers, often called processors, are data processing

facilities operated or designated by issuers or acquirers. Processing centers house card
processing systems supporting merchant and business locations, maintaining cardholder
data and billing systems, or both. Centers host computers communicating with VisaNet

1-2 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 1: Single Message System Overview VisaNet Systems

connection methods must run computer interfaces to connections. Visa tests interfaces
before centers connect to VisaNet.

Figure 1-1 The VisaNet Communications Network

1.2 VisaNet Systems

Three systems provide transaction processing:
• VisaNet Integrated Payment (V.I.P.), which includes:
- BASE I
- Single Message System (SMS)
• BASE II
• VisaNet Settlement Service (VSS)

1.2.1 VisaNet Integrated Payment (V.I.P.) System

V.I.P. is the primary transaction routing (switching) and processing system for online
authorization and financial requests entering VisaNet.

V.I.P. has one system supporting Dual Message Processing (DMP) (clients request
transaction authorization in a first message, and financial clearing information in a second
message), and another system supporting Single-Message Processing (SMP) (processing
interchange card transactions containing authorization and clearing information in one
message). Settlement occurs separately.

1.2.2 BASE I System

BASE I is the system processing authorization-only requests online. Authorization request
messages are the first sent in DMP; BASE II clearing messages are the second.

BASE I supports online and offline functions and BASE I files, including internal system
tables and the Merchant Central File (MCF).

See V.I.P. System Services, Volume 2, about the MCF.

BASE I Online Functions—Support DMP and include routing, cardholder and card
verification, Stand-In Processing (STIP), Card Verification Value (CVV) validation, Personal
Identification Number (PIN) verification, and file maintenance. A bridge from BASE I to
SMS enables BASE I clients to communicate with SMS clients and access SMS gateways
to outside networks.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1-3
VisaNet Systems Chapter 1: Single Message System Overview

BASE I Offline Functions—Include reporting and generating Visa Card Recovery Bulletin
(CRB)s. BASE I reporting includes authorization, Exception File, Advice File, and Point of
Sale (POS) reports.

1.2.3 Single Message System (SMS)

SMS processes full-financial transactions containing authorization and clearing information.
Because one message contains both, this is called SMP. SMS also supports DMP
(participants submit authorization requests first, then clearing and settlement in
financial request messages), communicating with BASE I and accessing outside networks
to complete processing. Only SMS performs SMP.

A bridge from SMS to BASE I lets SMS users communicate with BASE I users and access
BASE I gateways to outside networks.

SMS supports online and offline functions and SMS internal system tables controlling
access and processing. SMS supports the MCF for Visa U.S.A. (U.S.)-region clients.

SMS Online Functions—Perform real-time cardholder transaction and exception

processing, supporting authorization and full-financial transactions and transaction
delivery to BASE II for clients using DMP.

SMS accumulates reconciliation totals, performs activity reporting, and passes activity
data to VisaNet, which supports settlement and funds transfer processing for SMS.
VisaNet handles settlement and funds transfer as follow-up to SMS transaction processing.
VSS performs settlement and delivers results through advices and reports.

SMS supports SMS Automated Teller Machine (ATM) transactions for:

• Visa.
• Visa Electron.
• Plus ATM.
• Some non-Visa products.
Issuers can have SMS, or BASE I, BASE II, and SMS, process transactions. Issuers can use
different processing methods for different Visa products.

1-4 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 1: Single Message System Overview VisaNet Systems

SMS Offline Functions—Process settlement and funds transfer requests and provide
settlement and activity reporting. (SMS clients can also receive BASE I reports.)
Offline systems support a bridge to and from BASE II for Visa and Plus clearing
transactions VisaNet sends between SMS clients and BASE II clients.

1.2.4 BASE II System

BASE II is an international electronic batch transaction clearing system facilitating
interchange data exchange between acquirers and issuers and calculating interchange fees.

BASE II performs the second part of DMP. Through BASE I or SMS connections,
clients submit authorization messages, which V.I.P. clears through VisaNet connections
to BASE II. A bridge to V.I.P. permits interchange between BASE II centers and SMS centers.

BASE II passes message data to VSS, which settles with issuers and acquirers.

Figure 1-2 VisaNet Software System Components

VisaNet
V.I.P. System BASE II System

BASE I

SMS

Clients and processors using BASE I and BASE II can use SMS to process transactions
or use different processing methods for transaction types.
EXAMPLE
Issuers can use BASE I and BASE II for POS and use SMS for ATM.

1.2.5 VisaNet Settlement Service (VSS)

VisaNet processes interchange transactions for SMS and BASE II through separate
systems. SMS and BASE II perform their own clearing functions. Clearing is collecting
transactions from clients or processors and delivering them to other clients or processors.
Clearing includes valuation, calculating fees and charges. Once systems clear transactions,

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1-5
VisaNet Systems Chapter 1: Single Message System Overview

they are ready for settlement. Settlement is calculating and determining clients’ net
financial positions for transactions cleared by VisaNet, and funds exchange.

VSS consolidates SMS and BASE II settlement functions into one service. VisaNet sends
settlement information to clients and processors from SMS and BASE II in standardized
reports. VSS provides flexibility in defining financial relationships, selecting reports and
report destinations, and establishing funds transfer points.

Figure 1-3 VSS Process

BASE II Clearing SMS Clearing

SMS Reports

VisaNet Settlement Service

Funds Transfer

Settlement Reports

1-6 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 1: Single Message System Overview SMS Processing Summary

1.3 Common Member Interface (CMI) and Interface Methods

The Common Member Interface (CMI) allows clients and centers to use one communications
line to send and receive BASE I and SMS messages. Lines from VisaNet connections,
or stations, to V.I.P. connect at the CMI at VisaNet Interchange Center (VIC)s.
NOTE
Clients establish processing and routing parameters for their stations in system tables through the Customer
Online Repository (CORE). Clients contact Visa representatives to establish or change CORE settings.

The CMI accepts all message formats. CMI functions include basic editing and routing.

With the CMI, BASE I centers, including those using BASE I and SMS, can send BASE I
messages. SMS centers, including those using SMS and BASE I, can send SMS messages.
The CMI chooses systems based on request sources, processing requested, and processing
networks when messages specify networks.

Besides the CMI, other interface methods are available to clients and processors.
These allow users to communicate with only one V.I.P. component—BASE I or SMS.

1.4 SMS Processing Summary

This section provides a brief description of the way a typical online financial SMS ATM
transaction with a personal identification number (PIN) flows from the merchant to the
issuer and back, what occurs when the issuer system is not available, and what happens at
the end of the processing day.

1.4.1 SMS ATM Online Transaction Flow

Although not all online financial transactions require a PIN, ATM transactions always
require a PIN and PIN verification.
1. The transaction begins when a cardholder inserts a card into an ATM and enters
the PIN.
2. The ATM creates a formatted electronic message and forwards it to the acquirer.
The request includes the transaction type, transaction amount, encrypted PIN,
acquirer's identification, and full Track 2 (magnetic stripe) data.
3. The ATM acquirer creates an 0200 financial request message, logs the event,
and forwards the message to VisaNet.
4. V.I.P. logs and tracks the message, performs applicable message content editing,
initiates service functions such as currency conversion or PIN verification, and routes
the message to the issuer or processes the message in stand-in according to issuer
availability and predetermined routing and stand-in-processing (STIP) parameters.
5. The issuer verifies the PIN, if necessary, checks the transaction amount against the
account's available balance, and checks daily activity limits and other controls.
The issuer logs the message and, for approved messages, reduces the cardholder's
available balance by the amount of the transaction. The issuer creates an 0210 financial
response message based on the processing results and sends it to VisaNet.
6. V.I.P. logs the response and forwards it to the acquirer.
7. The acquirer logs the financial response and forwards it to the ATM to complete the
transaction. The acquirer ensures it successfully delivers the response. If approved,
VisaNet settles the transaction after the next settlement cutoff time.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1-7
SMS Processing Summary Chapter 1: Single Message System Overview

Figure 1-4 illustrates how VisaNet processes an online financial ATM transaction.

Figure 1-4 Typical ATM Online Message Flow

Request Request
(0200) (0200)

Response Response
(0210) (0210)
ATM Acquirer V.I.P. System Issuer

1.4.2 Stand-In Processing (STIP)

Although Visa designed SMS to have issuers authorize transactions online, VisaNet has
provisions to continue processing when the issuer's system is not available due to
hardware, software, or communications failure. This stand-in processing (STIP) is available
for all Visa and Visa Electron transactions. It is available for some non-Visa card types
depending on the region and issuer participation. STIP is not available for Mastercard
transactions.

While performing stand-in processing, V.I.P. can also verify the Card Verification Value
(CVV), or the Integrated Chip Card card verification value (iCVV) for chip-based
transactions, to detect the alteration of magnetic stripe or chip data.

For each SMS ATM transaction handled by STIP, V.I.P. creates an advice for the issuer
detailing the request and the STIP response. Issuers recover these advices by signing on
to Advice Recovery mode.

See Chapter 6, Stand-In, CVV, and CVV2 Processing, for information about STIP, the CVV
Service, and the CVV2 Service.

For detailed information about the exception file, refer to the Cardholder Database
chapter in V.I.P. System Services, Volume 2, and to V.I.P. System ATM Technical Specifications,
Volume 1 and Volume 2.

1.4.3 End-of-Day Processing

At settlement cutoff, VisaNet determines issuer and acquirer settlement positions and
prepares daily reports and raw data files. Raw data files contain detailed information
about the day's messages for a given participant. Similarly, issuers and acquirers use
their internal transaction logs to account for the day's work and to prepare daily reports
or files to reconcile to the reports and files they receive from VisaNet. The final step
in the settlement process is funds transfer, during which VisaNet collects funds from
settlement entities with net debit positions and pays funds to settlement entities with
net credit positions.

See Chapter 8, Settlement and Reconciliation, for detailed information about the
settlement process.

1-8 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 1: Single Message System Overview SMS ATM Products

VisaNet provides V.I.P. SMS users with a raw data file of all transactions. Clients can use
this file to match transactions on a one-to-one basis to their systems' records to identify
mismatched transactions and calculate settlement totals.

Each client's operations staff reconcile data between VisaNet and the client, as well as the
sponsored client, processor, or directly connected merchant. Operations staff compare the
data from VisaNet against the client's internal transaction data to identify discrepancies.

VisaNet includes a reporting facility producing daily and monthly reports for SMS issuers
and acquirers. The reports fall into two broad categories:
• Transaction detail reports
• Settlement summary reports
Transaction detail reports contain details about the day's message activity. The detail
reports list each transaction, including the settlement disposition. The detail reports
also include reconciliation totals.

Settlement summary reports contain summary information about the day's work.
The summary reports provide totals for the various components including interchange
totals and fee totals.

VisaNet provides the Point-of-Sale Authorization (POSA) File to subscribing SMS acquirers.
The file contains transaction data and other authorization information improving billing
accuracy and reducing fraud and chargeback losses for acquirers.

The POSA File provides a single daily file with debit and credit transaction data,
contributing to increased operational efficiency. The file includes all of the data elements
contained in the TC 33, SMS raw data records, and the POS reporting raw data and report
files, besides providing additional data, such as card results-level data.

1.5 SMS ATM Products

Clients can process all of their ATM transactions through a single SMS connection.
The Visa ATM program supports SMS and dual-message acquirers and issuers. However,
Visa requires new acquirers wanting to use Visa ATM, Visa Electron ATM, or Plus ATM
to connect to SMS.

1.5.1 SMS Acquirers and Issuers

SMS acquirers and issuers connect to the Single Message System. SMS acquirers process
all transactions as full financials. SMS issuers of proprietary cards with the Plus mark
process all Plus transactions as full financials.

SMS issuers of Visa cards can process all ATM transactions as full financials, or as a
combination of full financials and authorizations with deferred clearing transactions.

1.5.2 Dual-Message Acquirers and Issuers

Dual-message acquirers and issuers connect to the BASE I authorization and BASE II
clearing systems. VisaNet processes all ATM transactions as authorizations (BASE I
messages) with deferred clearing transactions (BASE II messages).

Features of the CPS/ATM Service include linking related messages, leveraging expanded
ATM data, and clearing transactions within three days. The CPS/ATM Service requires the

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1-9
SMS Services Chapter 1: Single Message System Overview

presence of the authorization characteristics indicator (ACI) and the transaction identifier
(TID) in the clearing transaction. For consistency, VisaNet incorporates the use of these
fields into ATM messages in the Single Message System.
NOTE
VisaNet assigns a TID to all transactions, regardless of region or CPS participation.

For information about the CPS/ATM Service, see the service description in V.I.P. System
Services, Volume 2, and the Visa Global ATM Planning Guide.

1.6 SMS Services

This section identifies the services SMS supports. See V.I.P. System Services, Volume 1
and Volume 2.

1.6.1 Routing Services

Routing refers to sending messages between VisaNet and acquirer and issuer processing
centers. Routing also refers to issuer-specified conditions triggering Visa stand-in
processing (STIP) to authorize a transaction on an issuer's behalf.

Visa assumes responsibility for routing a request to its proper destination. For instance,
acquirers do not have to determine the destination of their authorization or financial
requests because V.I.P. routes requests based on the account number in the message.
In some cases, V.I.P. uses data other than the account number to determine message
routing. For SMS transactions, V.I.P. also uses the value in the network ID field to route
messages.

Issuers designate which of their issuer processing centers should receive the requests.
The issuer associates each issuer BIN (a range of card numbers for a specific card
program, such as Visa Classic) with a specific issuer processing center. Optionally, issuers
can control which processing center receives requests for their cardholders by designating
multiple processing centers and specifying the types of transactions VisaNet should
route to each processing center.

In addition to basic routing functionality, Visa provides a variety of routing services

enabling issuers and acquirers to specify alternate routing for transactions with specified
characteristics. Most of the routing services V.I.P. provides are optional. Issuers can
designate an alternate path for routing particular transaction types. For instance, issuers
can route ATM transactions differently from POS transactions; they can route PIN
transactions differently from non-PIN transactions; they can route exception transactions
differently from authorizations and financial transactions.

The following subsections briefly describe available routing services. For details, refer
to Chapter 7, Routing, in this manual, and to V.I.P. System Services, Volume 1, for more
information about routing services.

1.6.1.1 ATM/POS Split Routing Service

The ATM/POS Split Routing Service enables BASE I and SMS issuers processing Visa,
Visa Electron, and Plus transactions to separate types of transactions and to accept or
to route these transactions to or from two or more processing endpoints. The service
offers the following options:

1-10 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 1: Single Message System Overview SMS Services

• The ATM/POS Split Routing option allows acquirers and issuers to use separate
processing centers for ATM and POS transactions.
NOTE
An emergency shutoff flag in V.I.P. ensures V.I.P. directs ATM loads to ATM load issuers only.

• The ATM/POS Account-Type Split Routing option is available to issuers processing ATM
transactions. The POS option supports POS and multipurpose card transactions for
BASE I and SMS issuers in the Asia-Pacific (AP) region only. This routing option allows
issuers to direct V.I.P. to route ATM transactions based on the account the cardholder
selects when using a multipurpose card at an ATM. BASE I and SMS issuers in the
AP region can have VisaNet route POS transactions based on the account the cardholder
selects when using a multipurpose card at the POS. Issuers can specify two endpoints:
one for deposit account processing, and one for credit account processing.
• The Alternate Routing option is available to SMS acquirers and issuers. This option
allows SMS entities to choose separate routing for certain transaction types, including
exception items and other back-office transactions. Issuers and acquirers may designate
their primary processing center to process online original transactions and one or more
alternate processing centers to process exception and back-office transactions.

1.6.1.2 Gateway Services

Both the BASE I component and the SMS component of the V.I.P. System have connections,
or gateways, to various systems and networks.

V.I.P. is connected with the Cirrus Gateway (V.I.P. Network 0006) and the Mastercard
Gateway (V.I.P. Network 0007) through the Mastercard Debit Switch (M.D.S.) for
the exchange of transactions for ATM processing. This gateway supports chip and
multicurrency processing.

Gateway Services link acquirers accepting non-Visa card products and services to other
networks outside of VisaNet using the same connections they use for Visa transactions.

For details concerning how the gateway function transfers data between network formats,
refer to the Authorization Gateway Service Cross-Reference Guide. This document includes
field-by-field data transfer descriptions between VisaNet-format dual-message 0100
authorization requests and responses, and American Express- and Mastercard-format
authorization requests and responses.

1.6.1.3 PIN/No-PIN Split Routing Service

This service enables issuers to separate message traffic according to the following options:
• The PIN/No-PIN Split Routing option enables issuers to separate transaction message
traffic requiring PINs from message traffic not requiring PINs (called “no-PIN
transactions”).
• The POS PIN Routing option allows issuers to route POS financial transactions with PINs
to SMS and other transactions to BASE I.

1.6.1.4 Priority Routing Service

This service allows SMS acquirers accepting more than one card brand (or mark) to assign
each of them a priority. Prioritization enables V.I.P. to determine the actual network and
set of program rules to use for each transaction. The Priority Routing Service does not
require the acquirer to assign a specific network identifier to a transaction.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1-11
SMS Services Chapter 1: Single Message System Overview

Clients can use the Priority Routing Service with the Alternate Routing option. Clients can
also use the Priority Routing Service to prioritize non-Visa programs destined for VisaNet
gateways to other systems and networks provided by Gateway Services.

1.6.2 Online Request Services

Visa offers the following online request services SMS participants can use.
(Unless otherwise indicated, see V.I.P. System Services, Volume 1 and Volume 2,
for comprehensive descriptions of all of the services summarized in this chapter.)

1.6.2.1 Visa Advanced Authorization

Visa Advanced Authorization provides transaction risk assessment to issuers for Visa card
cardholders during the POS and ATM authorization request process. Visa Advanced
Authorization is required for U.S. issuers and is a subscription-based service for issuers
in Visa Canada and the Asia-Pacific (AP), Latin America and Caribbean (LAC), and
Central and Eastern Europe, Middle East, and Africa (CEMEA) regions. To receive the
Visa Advanced Authorization fields, Field 62.21—Advanced Authorization Risk Score
and Field 62.22—Advanced Authorization Condition Code, in an authorization request,
the issuer must first successfully complete testing. Issuers can optionally include Visa
Advanced Authorization risk score threshholds as part of their STIP processing parameters.

1.6.2.2 Advice Retrieval Service—SMS

The SMS Advice Retrieval Service enables acquirers and issuers to use online connections
to recover all types of advices from the Advice File. The service allows clients to decide
when they want to retrieve advices so they can manage their advice volume efficiently.

Clients can use the Deferred Clearing Advice File (DCAF) Service to retrieve original BASE II
draft transactions in a file instead of individually from the online advice queue. All other
types of advices from BASE II endpoints, those not original BASE II draft transactions,
must be recovered through the online connection—not through the DCAF Service.
See “DCAF Service.”

Clients can also choose to have VisaNet hold advices from BASE II endpoints until a
certain time of day to manage the volume of advices efficiently. “Flexible Times for Online
Delivery of Advices From BASE II Endpoints” in this chapter explains this option.

For more information about advice recovery, refer to Chapter 4, Message Types and Flows,
Chapter 6, Stand-In, CVV, and CVV2 Processing, and V.I.P. System Services, Volume 2.

1.6.2.3 Automatic Cardholder Database Update (Auto-CDB) Service

The Automatic Cardholder Database Update (Auto-CDB) Service enables V.I.P. to update
records in the Exception File when issuers return a pick-up response code in authorization
response messages.

The Auto-CDB Service helps issuers prevent losses from problem accounts and improves
the accuracy of cardholder information available to V.I.P. for stand-in processing (STIP).

For details about this service, refer to V.I.P. System Services, Volume 2.

1.6.2.4 Card Verification Value (CVV) Service, the Integrated Chip Card Card
Verification Value (iCVV), and the Card Verification Value 2 (CVV2) Service
Issuers can choose to have the BASE I Visa Security Module (VSM) verify the following
verification values all of the time or only when the issuer is unavailable and STIP processes
the transaction.

1-12 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 1: Single Message System Overview SMS Services

• A card verification value (CVV) is a 3-digit number encoded on the card's physical
magnetic stripe or in the chip's image on a Visa Smart Debit/Smart Credit (VSDC) card.
• An Integrated Chip Card card verification value (iCVV) is a 3-digit number issuers may
encode in the chip's image on a VSDC chip card instead of the CVV. (The iCVV is also
referred to as the alternate CVV.) A VSDC card's chip image may contain the CVV or
iCVV. A card's physical magnetic stripe does not use an iCVV.
• The Card Verification Value 2 (CVV2) is an embossed 3-digit security number appearing
on the reverse side of the card. Clients can use the CVV2 in card-present and
card-not-present transactions.
Visa offers a verification service for the following:
• Card Verification Value (CVV or iCVV) for card-present transactions.
• Card Verification Value 2 (CVV2) for card-present and card-not-present transactions.
NOTE
The CPS/Account Funding program requirements include the CVV2 for electronic commerce (e-commerce)
stored-value transactions. For stored-value cards refilled more than once, the program requires the CVV2 only
in the initial funding request for the request to qualify; subsequent transactions can qualify for the CPS
program without the CVV2 being present.

CVV and iCVV—Determining whether the CVV or the iCVV requires verification depends
on the issuer's system parameters and on the code in Field 22—Point-of-Service Entry
Mode Code in the request. Also, the verification entity performs CVV processing only if
the CVV is in the correct position in the track. Refer to the Payment Technology Standards
Manual for technical specifications for CVV placement.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1-13
SMS Services Chapter 1: Single Message System Overview

• If field 22, positions 1 and 2, contain 90 or 05 and the issuer's system settings indicate
V.I.P. is to perform CVV checking, the security module performs the verification using
the CVV algorithm. Validation of the CVV from the physical magnetic stripe does not
occur if field 22, positions 1 and 2, contain 02 or 95, because the values 02 and 95
indicate the track data in Field 35—Track 2 Data or in Field 45—Track 1 Data may be
unreliable and accurate CVV processing may not be possible.
NOTE
For Plus ATM transactions only, the value 02 indicates the exact contents of Track 2 were read and CVV
checking is possible. For Visa ATM transactions, acquirers can use values 02 or 90 to indicate the complete,
unaltered magnetic stripe content has been read and CVV processing may not be possible.

• If field 22, positions 1 and 2, contain 05, V.I.P. assumes the track data originated from the
chip. V.I.P. checks the issuer's system settings (in CORE) to determine if the verification
value in the track data is a CVV or an iCVV. (Set A indicates a CVV; Set B indicates
an iCVV.)
- If the issuer's system settings indicate it supports CVV checking for chip cards but
does not support iCVV checking, the security module performs the verification using
the CVV algorithm.
- If the issuer's system parameters indicate it supports CVV checking and iCVV checking
for chip cards, the security module performs the verification using the CVV algorithm
except the system substitutes 999 for the service restriction code.
NOTE
The presence of code 90 in field 22 does not guarantee CVV processing. If a non-participating acquirer
submits code 90 in field 22, V.I.P. rejects the message.

Validation of the CVV or the iCVV residing in the chip's magnetic stripe image does not
occur if field 22, positions 1 and 2, contain 95, because the value 95 indicates the track
data in field 35 or in field 45 may be unreliable.
To verify the CVV, V.I.P. (or the issuer) uses the DES key and other information from the
stripe to calculate a CVV and compares it with the stripe's encoded CVV. For the CVV to
be valid, the two values must match exactly; otherwise, the CVV fails validation.

As indicated above, iCVV processing uses all options, parameters, and keys used in CVV
processing. V.I.P. or the issuer uses the same algorithm for the CVV and for the iCVV,
but they substitute the value 999 for the service restriction code for iCVV processing.
As part of the issuer participation procedure, the issuer specifies expiration date ranges
and whether the CVV check is to be based on the chip image of the magnetic stripe data.

STIP can respond to CVV failures with an issuer-specified decline response code or can
forward failures to the issuer for processing. Issuers or V.I.P. can approve, refer, or decline
transactions failing CVV validation depending on issuer-specified parameters.

Refer to the Card Verification Value (CVV) Service chapter in V.I.P. System Services,
Volume 2, for a description of the service. Refer to the Payment Technology Standards
Manual for technical specifications for CVV placement, calculation, and verification.

For details about this service, refer to the Stand-In, CVV, and CVV2 Processing chapter
in this manual, and to V.I.P. System Services, Volume 2. Refer to the Payment Technology
Standards Manual for technical specifications for CVV placement, calculation, and
verification.

1-14 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 1: Single Message System Overview SMS Services

1.6.2.5 Card Verification Value 2 (CVV2) Service

The Card Verification Value 2 (CVV2) Service is a card verification tool designed to reduce
fraud losses on card-present and card-not-present transactions.

Issuers must imprint a 3-digit security number (the CVV2) on the back of all new or
reissued Visa cards, in accordance with the Visa Rules. Clients can use the CVV2 number
to validate a genuine Visa card is used during a transaction. The CVV2 is calculated using
a secure cryptographic process and a key known only to the issuer and to Visa.

Participating merchants manually enter the CVV2 numeric value for validation by the V.I.P.
System, the issuer, or both. V.I.P., the issuer, or both, verifies the CVV2 and returns the
CVV2 result code to the merchant.

Although a CVV2 value is never passed in ATM transactions, ATM issuers (including issuers
of Plus cards) can optionally use CVV2 numbers for purposes of card activation, address
changes, voice response unit (VRU) cardholder validation, and other bank customer service
options to ensure the cardholder has the “real” card in hand.

For details about this service, refer to Stand-In, CVV, and CVV2 Processing chapter, in this
manual, and to V.I.P. System Services, Volume 2.

1.6.2.6 Deferred Clearing Advice File (DCAF) Service

The Deferred Clearing Advice File (DCAF) Service enables SMS issuers to receive deferred
clearing advices in bulk files, in addition to receiving advices individually online.

Deferred advices are those not created and sent immediately in response to the
single-message request, but are deferred—created later—and sent to the issuer after
they are generated. Deferred clearing advices originate from dual-message, BASE II
acquirersnot generating online clearing messages.

V.I.P. can also create online deferred clearing advices for SMS issuers in response to BASE II
clearing messages. These advices are also called force post advices.

The DCAF Service can help issuers manage large volumes of advices without negatively
affecting system capacity and resource allocation.

Refer to “Flexible Times for Online Delivery of Advices From BASE II Endpoints” in this
chapter for ways in which clients can specify times for retrieving BASE II advices from
online queues.

1.6.2.7 Flexible Times for Online Delivery of Advices From BASE II Endpoints
To manage the volume of advices from BASE II endpoints, clients can specify times for
retrieving these advices from online queues. (Refer to “DCAF Service” in this chapter, which
explains how SMS issuers can receive original BASE II clearing transactions in bulk files.)

DCAF Service processing options relate specifically to original BASE II deferred clearing
transactions received through file delivery. The flexible timing options described in this
section, however, apply to all advices received online from acquirer or issuer BASE II
endpoints.

With implementation of the flexible timing options, advices from BASE II endpoints
are available to SMS issuers shortly after clearing BASE II. To facilitate different clients'
processing needs, SMS issuers can specify one of the following options at the BIN
or processor level:

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1-15
SMS Services Chapter 1: Single Message System Overview

• Define a specific delivery time for advices from BASE II endpoints.

• Retrieve advices from BASE II endpoints as soon as they become available to V.I.P.,
currently as early as noon Pacific standard time (PST).
• Retrieve advices from BASE II endpoints at the standard system default time.
For more information about these options, clients can contact their Visa representatives.

1.6.2.8 Dynamic Key Exchange (DKE) Service

The Dynamic Key Exchange (DKE) Service is an optional service enabling SMS clients
to change Data Encryption Standard (DES) cryptographic keys with Visa using online
messages.

Entities use working keys to encrypt and de-encrypt customer PINs when they transmit
them between the SMS participant and VisaNet. An SMS participant can periodically
change acquirer working keys, issuer working keys, or both, by exchanging online
messages with VisaNet. Two options are available:
• A participant can request new working keys any time.
• A participant can request in advance that VisaNet automatically create working keys on
a daily basis.
To ensure the participant and VisaNet are using the same keys, the participant must
acknowledge successful receipt of a new key.

1.6.2.9 Merchant Initiated Transactions (MIT)

Merchant Initiated Transactions (MIT) are supported by VisaNet. These transactions are
commonly performed without cardholder participation to:
• Perform a pre-agreed standing instruction from a cardholder to provide goods or
services.
• Perform a transaction as a follow-up to a cardholder-initiated transaction (CIT).
The MIT framework is necessary to identify transaction intent or the cardholder’s active
participation.

The MIT framework:

• Uses a global standard to identify transaction intent and whether a transaction is
merchant initiated—i.e., a cardholder is actively participating and is available for
authentication. It also enables merchants, acquirers, and issuers to link a series of
related transactions together.
• Enables consistent MIT processing.
• Provides transaction transparency, resulting in higher authorization rates and improved
cardholder experience.
• Allows merchant-initiated, token-based transactions to be processed without
authentication data elements.
MITs are a follow-up to a cardholder-initiated transaction (CIT). Merchants and acquirers
accepting CITs with a payment token must comply with the MIT framework. Payment
tokens are accepted in:
• payWave transactions.
• Online payments via digital wallets that use payment tokens.
• Payment transactions from devices equipped with Magnetic Secure Transmission (MST)
The MIT framework:

1-16 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 1: Single Message System Overview SMS Services

• Identifies the intent of the MIT by providing appropriate identifiers in the transaction
using Field 63.3—Message Reason Code or Field 126.13—POS Environment.
• Provides proof of a preceding transaction by creating a linkage with it by using the
transaction identifier of the previous or original transaction in Field 62.2—Transaction
Identifier or Field 125, Usage 2, Dataset ID 03.
NOTE
With the exception of incremental authorizations, the MIT framework is not required for PAN-based
transactions. However, Visa encourages all merchants and acquirers to implement the MIT framework for
payment token and PAN transactions.

1.6.2.10 MIT Categories

The Merchant Initiated Transactions (MIT) framework covers two types of MITs:
• Industry-Specific Business Practice MITs
• Standing-Instruction MITs

Table 1-1 Incremental Authorization Transaction—Message Reason Code 3900

Description Incremental authorizations are used to increase the total amount authorized
if the authorized amount is insufficient.
Maximum Incremental authorizations can be performed during the approval response
Timeframe validity period of the original estimated/initial authorization. For more
Between Original details, see Visa Rules (ID# 0029524).
Transaction and
MIT
Relevant Incremental transactions are limited to certain merchant categories. For a
Merchant complete list of eligible MCCs, see Visa Rules (ID# 0025596).
Segments

NOTE
Incremental transactions in the U.S. already meet the requirements specified in the MIT framework.

Table 1-2 Resubmission Transaction—Message Reason Code 3901

Description A resubmission is submitted when a merchant requested an authorization

but received a decline for insufficient funds after goods or services were
delivered.
Maximum (14) days from the original. This limit applies to token-based resubmissions
Timeframe only.
Between Original
Transaction and
MIT
Relevant Commuter transportation.
Merchant
Segments

Table 1-3 Delayed Charges Transaction—Message Reason Code 3902

Description An account charge after original services have been rendered and payment
processed.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1-17
SMS Services Chapter 1: Single Message System Overview

Table 1-3 Delayed Charges Transaction—Message Reason Code 3902 (continued)

Maximum (90) days from the date of rental return, check-out, or disembarkation date.
Timeframe See Visa Rules (ID# 0007398).
Between Original
Transaction and
MIT
Relevant Limited to vehicle rental, lodging, cruise lines, and other rentals. See Visa
Merchant Rules (ID# 0007398).
Segments

Table 1-4 Reauthorization Transaction—Message Reason Code 3903

Description There are two common reauthorization scenarios:

• Split or delayed shipments at e-commerce retailers.
• Extended stay hotels, car rentals, and cruise lines.
Maximum Token-based reauthorizations only. A reauthorization can be submitted up
Timeframe to 90 days from original purchase except for the following MCCs, which can
Between Original submit a reauthorization up to 120 days from the original date of purchase.
Transaction and • 3351–3500—Car Rental Agencies
MIT • 3501–3999—Lodging—Hotels, Motels, Resorts
• 4411—Steamship and Cruise Lines
• 4457—Boat Rentals and Leasing
• 7011—Hotels, Motels, Resorts, Central Reservations Services (Not
Elsewhere Classified)
• 7033—Trailer Parks and Campgrounds
• 7394—Equipment, Tool, Furniture, and Appliance Rental and Leasing
• 7512—Car Rental Agencies (Not Elsewhere Classified)
• 7513— Truck and Utility Trailer Rentals
• 7519—Motor Home and Recreational Vehicle Rentals
• 7999—Recreation Services (Not Elsewhere Classified)
Relevant Any merchant category.
Merchant
Segments
Requirement Reauthorization submitted with a payment token must include TAVV
When Using the in Field 126.9— CAVV Data, Usage 3: 3-D Secure CAVV, Revised Format to
MIT framework qualify for U.S. CPS programs.

NOTE
Prior to this framework, Visa allowed merchants to submit the same authentication data (CAVV) in multiple
authorization requests, that is, once for each of the shipments against a single order. Merchants did not
need to send special fields or set special values for the multiple authorization requests. The authentication
data limits still apply to those merchants. Visa reserves the right to terminate this interim solution at any
time, now that a standard MIT framework is in place.

Table 1-5 No-Show Transaction—Message Reason Code 3904

Description Cardholders can use their Visa cards to make a guaranteed reservation
with certain merchant segments. A guaranteed reservation ensures that
the reservation will be honored and allows a merchant to perform a
no-show transaction to charge the cardholder a penalty according to
the merchant’s cancellation policy. For merchants accepting token-based
payment credentials to guarantee a reservation, it is necessary to perform a
CIT (Account Verification Service) at the time of the reservation to be able
perform a no-show transaction later.

1-18 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 1: Single Message System Overview SMS Services

Table 1-5 No-Show Transaction—Message Reason Code 3904 (continued)

Maximum No timeframe.
Timeframe
Between Original
Transaction and
MIT
Relevant For a complete list of all eligible MCCs that can submit no-show transactions,
Merchant see Visa Rules (ID#: 0029266).
Segments

Table 1-6 Installment Payment Transaction—Value I in POS

Environment Field 126.13

Description A transaction in a series of transactions using a stored credential and

representing a cardholder agreement for the merchant to initiate one or
more future transactions over a period of time for a single purchase of
goods or services.
Maximum The timeframe is governed by a contract between the cardholder and the
Timeframe merchant for that specific installment relationship.
Between Original
Transaction and
MIT
Relevant Any merchant category.
Merchant
Segments

Table 1-7 Recurring Payment Transaction—Value R in POS

Environment Field 126.13

Description A transaction in a series of transactions using a stored credential and

processed at fixed, regular intervals (not to exceed (1) year between
transactions), representing cardholder agreement for the merchant to initiate
future transactions for the purchase of goods or services provided at regular
intervals.
Maximum The timeframe is governed by a contract between the cardholder and the
Timeframe merchant for that specific recurring relationship.
Between Original
Transaction and
MIT
Relevant Any merchant category.
Merchant
Segments

NOTE
Acquirers that cannot use the Transaction Identifier to link the token-based merchant-initiated recurring
payment to the previous transaction should contact their Visa representative.

Table 1-8 Unscheduled COF Transaction—Value C in POS Environment Field 126.13

Description A transaction using a stored credential for a fixed or variable amount that
does not occur on a scheduled, or regularly occurring, transaction date,
where the cardholder has provided consent for the merchant to initiate one
or more future transactions.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1-19
SMS Services Chapter 1: Single Message System Overview

Table 1-8 Unscheduled COF Transaction—Value C in POS Environment

Field 126.13 (continued)

Maximum The timeframe is generally undetermined, because payment is prompted by

Timeframe a pre-agreed event between the cardholder and the merchant.
Between Original
Transaction and
MIT
Relevant Any merchant category.
Merchant
Segments

1.6.2.11 Mobile Location Confirmation Service

This service provides participating issuers with a field in authorization or full-financial
requests and merchandise return messages indicating whether the cardholder's mobile
phone location matches the location of the merchant or ATM. Issuers can use this
information in their authorization approval process.

Issuers participating in the Mobile Location Confirmation Service must support Field 104,
Usage 2—Transaction-Specific Data in TLV format. Issuers must be prepared to receive
Dataset ID 6C—Travel Tag, with the Tag 02—Mobile Location Confirmation. Issuers may
incorporate the values received in Tag 02 in their authorization processes.

Participating issuers must be prepared to make an application download available to their

cardholders transmitting the location of a mobile phone to Visa.

Contact your regional client support representative for more information.

1.6.2.12 Multicurrency Service

The Multicurrency Service supports authorization, clearing, and settlement processing in
international currencies. Plus issuers and acquirers must be directly attached to VisaNet to
participate. For information about this service, see the Multicurrency Support chapter.

The Multicurrency Service supports authorization, clearing, and settlement processing in

international currencies.

1.6.2.13 PIN Verification Service (PVS)

The PIN Verification Service (PVS) is a V.I.P. service providing full-time or stand-in
verification of personal identification numbers (PINs) used for Visa and Plus ATM
transactions, for Visa point of service (POS), Visa Electron POS, and Interlink POS
transactions, and for Visa Smart Debit/Smart Credit (VSDC) transactions. A personal
identification number is a secret code identifying a cardholder at an ATM or at a terminal.
A PIN serves as an electronic substitute for a cardholder's signature.

At the issuer's option, the V.I.P. System can verify PINs on behalf of the issuer center at
all times or only when the center is unavailable. When V.I.P. verifies PINs, it intercepts all
authorization requests containing PINs, verifies the PINs, and passes the requests to the
issuers or to the V.I.P. stand-in processor (STIP) for authorization processing.

Participation in PVS is optional for Visa issuers, Visa Electron issuers, Plus issuers, Interlink
issuers, VSDC issuers, and issuers of all other card products.

For more information, refer to V.I.P. System Services, Volume 2.

1-20 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 1: Single Message System Overview SMS Services

1.6.2.14 Prepaid Activation, Load, and Partial Approval Processing

V.I.P. processes prepaid cards for Visa and private-label card products, as well as for
Interlink. Merchants and issuers submit transactions to activate prepaid cards and to load
spending amounts onto activated cards. They can also submit load requests without
submitting activation requests, and can activate and load value to cards in a single request
message.

When merchants submit authorizations for an amount greater than the amount loaded
onto the card, issuers can return partial authorizations for the available amount on the
card.

An emergency shutoff flag in V.I.P. shields POS-load issuers from receiving ATM loads.

Prepaid transactions, including partial authorizations, are eligible for STIP.

Participation in prepaid card processing services is optional for issuers, acquirers,

processors, and merchants. Visa requires acquirers participating in prepaid transactions
to support partial approval amounts. Visa requires issuers participating in prepaid
transactions to support the partial authorization value in request messages, but may
optionally support partial authorization responses. Acquirers and issuers must complete
testing for sending and receiving prepaid transactions.

1.6.2.15 Contactless Processing

Contactless transactions are made using contactless chip Visa cards. The Dynamic Card
Verification Value (dCVV) resides in the contactless card. dCVV verification processing
occurs when a terminal (or contactless device) equipped to accept contactless chip cards
reads the chip card. The contactless chip creates the dCVV value and inserts it into the
Track 1 or Track 2 magnetic stripe data it transmits to the terminal along with other data.
The dCVV replaces CVV data in track data.

Visa contactless cards are one of the following:

• A magnetic stripe Visa card with an embedded contactless chip.
• A Visa Smart Debit/Smart Credit (VSDC) chip card having a magnetic stripe and
supporting contactless chip.
NOTE
Clients accepting and processing VSDC chip cards for contactless transactions must be participants in the
VSDC Service.

A card can include a contactless chip with its dCVV algorithm as well as a CVV in the
Track 1 or Track 2 magnetic stripe. A VSDC chip card can also contain a contactless chip
with its dCVV algorithm as well as a CVV or an iCVV.

V.I.P. identifies a contactless authorization or financial request if the POS entry mode code
in field 22 is 07 (contactless chip transaction originated using VSDC chip data rules) or is
91 (contactless chip using magnetic stripe data rules).
NOTE
VisaNet supports the use of contactless chip cards for ATM transactions.

Additionally, in the United States (U.S.) region, acquirers must insert code 8 in
Field 60.2—Terminal Entry Capability. Acquirers in other regions do not have to use
code 8 in field 60.2

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1-21
SMS Services Chapter 1: Single Message System Overview

V.I.P. supports contactless chip cards having an alternative primary account number (PAN)
stored on the chip. This PAN is different from the PAN embossed on the card; it serves
as a security measure to prevent counterfeit chip cards from being used for non-chip
transactions. Alternative PAN processing applies to contactless chip cards using qVSDC,
VSDC, and magnetic stripe data. V.I.P. account ranges can be set up to indicate alternative
PAN support. V.I.P. declines a transaction with response code 59 (suspected fraud) if
all of the following apply:
• The account range of the card indicates it supports an alternative PAN.
• Field 22 does not contain 05, 07, 91, or 95.
• Chip data is not present in field 55 or the third bitmap fields.
Visa payWave ATM Transactions—V.I.P supports Visa payWave ATM transactions in
network 0002 and network 0004. Acquirers implementing Visa payWave ATM transactions
must support full chip data.

Acquirers implementing these transactions for the first time must use full chip data in
Field 55, Usage 1—VSDC Chip Data. However, acquirers using the expanded third bitmap
format can continue to use their format for processing Visa payWave ATM transactions.

American Express Transactions—Acquirers processing transactions in American Express

U.S. territories must support Amercian Express EMV chip-based contact and contactless
transactions. For details of American Express regions, refer to the American Express
documentation.

1.6.2.16 Visa Smart Debit/Smart Credit (VSDC) Service

Visa Smart Debit/Smart Credit (VSDC) is a chip-based Visa card product supporting offline
and online transactions, including Plus ATM transactions. VSDC cards work in conjunction
with special chip-read terminals to approve or to decline transactions. VSDC offline
transactions occur only between the cardholder's chip card and the terminal and do not
go through VisaNet. VisaNet processes transactions online when processing triggers
predetermined offline risk management procedures, or because of random selection
parameters established by the issuer.

For purchase transactions, the issuer may determine whether a cardholder signature or a
PIN is required for cardholder verification. ATM transactions require a PIN.

VSDC cards rely on cryptograms to ensure their security and the integrity of their offline
and online transactions. Issuers selecting the Full Data implementation option verify
the cryptogram submitted by Full Data acquirers in the 0100 authorization request.
The card terminal authenticates the issuer's cryptogram in the 0110 authorization
response to ensure the issuer that created the card is the issuer that approved the
transaction. If V.I.P. performs processing for the Card Authentication feature on behalf of
the issuer, V.I.P. validates the Authorization Request Cryptogram (ARQC) and provides the
Authorization Response Cryptogram (ARPC) in the response. If the issuer participates in
the Issuer Authentication feature, the issuer or V.I.P. generates a cryptogram (Authorization
Response Cryptogram) sent to the card in the response so the card can validate the
authorization response came from the correct issuer.
NOTE
Issuer participation is optional in the VSDC Card Authentication feature and in the Issuer Authentication feature.

V.I.P. identifies a VSDC-based authorization request by the value in

Field 22—Point-of-Service Entry Mode Code indicating a chip card was read at a

1-22 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 1: Single Message System Overview SMS Services

VSDC terminal (05 or 95) and the service restriction code in the magnetic stripe is 2
(international card, alternate technology) or is 6 (national use, alternate technology).

V.I.P. processes VSDC transactions according to card type. VisaNet supports the following
card types:

Visa Integrated Circuit Card Specification (VIS)—This card type uses the initial Visa
chip card type specifications for communicating between EMV (JCB, Mastercard, Visa)
cards and their issuer processors.

Common Core Definition (CCD)—CCD is a newer EMV card type containing the same
data as a VIS card but in a more flexible message format transmitting more chip data.

Generic EMV Transport—This card type is also EMV-compliant but carries issuer-defined
online chip information not processed by VisaNet. V.I.P. treats Generic EMV Transport
transactions as “pass-through” transactions, valid for PIN translation but ineligible for field
edit, Visa chip or issuer authentication services, or STIP.

V.I.P. supports chip cards having an alternative primary account number (PAN) stored
on the chip. This PAN is different from the PAN embossed on the card and serves as
a security measure to prevent counterfeit chip cards from being used for non-chip
transactions. Alternative PAN processing applies to VIS, CCD, and Generic EMV Transport
cards and to all supported cryptogram version numbers (CVNs). V.I.P. account ranges can
be set up to indicate alternative PAN support. V.I.P. declines a transaction with response
code 59 (suspected fraud) if all of the following apply:
• The account range of the card indicates it supports an alternative PAN.
• Field 22 does not contain 05, 07, 91, or 95.
• Chip data is not present in field 55 or the third bitmap fields.

1.6.2.17 Visa iCVV Convert

The Visa iCVV Convert Service validates and converts a chip-based transaction to appear
as a magnetic stripe-based transaction. VisaNet validates the cryptogram, removes
unnecessary chip data, and submits the authorization request to participating issuers.
Issuers can participate in this service optionally. Visa iCVV Convert is available for BASE I
and SMS users, and also supports contactless chip transactions.

For participating issuers, VisaNet makes changes to the following fields before forwarding
the authorization request:
• Field 55—Integrated Circuit Card (ICC)-Related Data is removed.
• Field 23—Card Sequence Number is removed.
• Field 44.8—Card Authentication Results Code is removed.
• Field 60.3 (Chip Condition Code), Field 60.6 (Chip Transaction Indicator), and Field 60.7
(Chip Card Authentication Reliability Indicator) are zero-filled, or dropped, if no
subsequent field 60 subfields are present.
• Field 39—VisaNet does not send Online CAM authentication results (response code 82),
and offline approval (Y1, Y3) or decline (Z1, Z3) response codes to participating
issuers—VisaNet converts Y1 and Y3 to 00 (Approved) and Z1 and Z3 to 05 (Do not
honor) before sending them to participating issuers. However, the response codes Y1,
Y2, Z1 and Z3 are sent in 0120/0220 advices to participating issuers. CVV results are
sent in field 44.5.
If the issuer participates in Visa iCVV Convert and the transaction passes Online Card
Authentication Method (Online CAM), VisaNet replaces the iCVV present in the track data

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1-23
SMS Services Chapter 1: Single Message System Overview

(field 35 or field 45) with a VisaNet-generated CVV. In such instances, iCVV checking is not
performed. However, If the issuer participates in Visa iCVV Convert, but the transaction
fails Online CAM, VisaNet declines the transaction with a response code value of 05
(Do Not Honor) in field 39.

If chip data for Online CAM validation is not present in the request message, VisaNet
performs iCVV validation. If the transaction passes iCVV validation, VisaNet replaces
the iCVV present in the track data (field 35 or field 45) with a VisaNet-generated CVV.
However, if the transaction fails iCVV validation, VisaNet declines the transaction with
response code 05 (do not honor).

VisaNet declines the transaction with response code 05 (do not honor) if the issuer
participates in Visa iCVV Convert, but the issuer's MDK (Online CAM) and CVK (CVV)
are not present.

1.6.2.18 VSDC PIN Management Service

The VSDC PIN Management Service allows Visa card cardholders to change or to
unblock PINs in VSDC cards. Acquirers and issuers must successfully complete testing to
participate in the service to provide this capability. Both must complete VSDC Service
testing; issuers must be full VSDC participants.

After the cardholder enters the new PIN twice, the acquirer forwards the new PIN in a
“zero amount” 0100 authorization request to the issuer for approval. Processing code 70
in Field 3—Processing Code indicates a PIN change; processing code 72 indicates a PIN
unblock. The current PIN information is in Field 52—Personal Identification Number
(PIN) Data and in Field 53—Security-Related Control Information; the new PIN is in
Field 152—Secondary PIN Block. Approvals receive response code 85 (no reason to
decline) in Field 39—Response Code. PIN change or unblock requests bypass activity
checking and are not eligible for PACM processing or for STIP. If the issuer is unavailable
or if the request times out, STIP responds with response code 91 in field 39.

V.I.P. does not include CVV or PVS PIN verification with PIN management processing,
only PIN translation. However, VSDC PIN Management Service participants may also
participate in the PIN Verification Service (PVS) and in the Card Verification Value (CVV)
Service. (Refer to V.I.P. System Services, Volume 1, for more information about the VSDC
PIN Management Service.)

1.6.2.19 Merchant Verification Value (MVV) Processing

V.I.P. uses Field 62.20—Merchant Verification Value (MVV) to identify and authenticate
merchants in authorization and reversal requests. It also validates the relationship between
the merchant and its Visa client. Acquirers and issuers must successfully complete testing
to send and receive this field.
NOTE
To be able to send and receive field 62.20, acquirers and issuers must be able to send field 62 in bitmap format.

Visa assigns MVVs to specific merchants, and each MVV is unique. Visa assigns the
first six positions and helps the acquirer assign the last four. If the MVV field format is
invalid in requests, V.I.P. drops the field.

The MVV is not necessarily a component of the Custom Payment Service. U.S. tax payment
transactions must include an MVV. MVVs can also be used to allow individual clients to
process transactions while belonging to an otherwise blocked merchant category such

1-24 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 1: Single Message System Overview SMS Services

as 7995 (online gambling). MVVs are stored in the cardholder database (CDB) and are
maintained by the client.

1.6.2.20 Mobile Location Confirmation Service

This service provides participating issuers with a field in authorization or full-financial
requests and merchandise return messages indicating whether the cardholder's mobile
phone location matches the location of the merchant or ATM. Issuers can use this
information in their authorization approval process.

Issuers participating in the Mobile Location Confirmation Service must support Field 104,
Usage 2—Transaction-Specific Data in TLV format. Issuers must be prepared to receive
Dataset ID 6C—Travel Tag, with the Tag 02—Mobile Location Confirmation. Issuers may
incorporate the values received in Tag 02 in their authorization processes.

Participating issuers must be prepared to make an application download available to their

cardholders transmitting the location of a mobile phone to Visa.

Contact your regional client support representative.

1.6.3 Risk Services

Visa offers the following tools to issuers and to acquirers enabling them to minimize their
exposure to fraud. Most of the risk services are optional.

1.6.3.1 Fraud Reporting System (FRS)

The Fraud Reporting System (FRS) is a V.I.P. service helping clients report, track, and
analyze fraudulent transactions. FRS consolidates fraud information, helping clients detect
fraud patterns and reduce losses.

Visa requires clients to electronically report confirmed fraud transactions on all Visa cards.
Acquirers and issuers must comply with the fraud reporting rules as defined in Visa Core
Rules and Visa Product and Service Rules.

The SMS Online Fraud Reporting option, available through V.I.P., allows single-message
users to report fraud using SMS advice messages.

1.6.3.2 Visa Transaction Advisor E-Commerce Scoring Service

This service is optional for all acquirers and their e-commerce merchants. This service
provides participating acquirers and their e-commerce merchants with the Visa Transaction
Advisor (VTA) e-commerce risk score and risk condition code. Acquirers and their
e-commerce merchants can use this information in assessing transaction risk when
deciding whether to proceed with a transaction.

In order for an e-commerce transaction to receive the VTA e-commerce risk score and risk
condition code, the PCR for the acquirer’s BIN and the MVV must be set up to participate
in the Visa Transaction Advisor E-Commerce Scoring Service.

Acquirers participating in the Visa Transaction Advisor E-Commerce Scoring Service must
be able to receive Field 104, Usage 2—Transaction-Specific Data, with Dataset ID 5B—Visa
Risk Assessment Data, in approved 0110 Authorization response and 0210 Full financial
response messages.

For more information, contact your regional client support representative.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1-25
Fees and Charges Chapter 1: Single Message System Overview

1.6.4 Additional Services

This section includes additional services available to SMS ATM clients.

1.6.4.1 Visa Mobile Prepaid (VMP) Service

The Visa Mobile Prepaid (VMP) service allows financially underserved consumers in
emerging markets to gain access to interoperable financial services. VMP uses mobile
money accounts to turn cash into digital currency that can be used in financial transactions
such as purchasing, paying bills, buying airtime, sending funds to acquaintances, or
loading or withdrawing funds.
NOTE
VMP transactions are supported in certain countries within the Visa AP, Visa CEMEA, and Visa LAC regions
only. Contact your Visa representative for more information.

VMP accounts can be used for the following:

• Agent Cash In: Cash in transactions enable the addition of money to a mobile money
account using OCTs.
• Agent Cash Out: Cash out transactions enable withdrawal of funds from a mobile
money account.
• Agent Cash Claim: Cash claim transactions enable withdrawal of funds from a mobile
money account using a manual cash transaction.
• Agent Bill Pay: Bill pay transactions enable withdrawal of funds from a mobile money
account using AFTs to pay bills or make airtime top up purchases.
• Person-to-Person (P2P) Money Transfer: P2P money transfer enable sending and
receiving of funds to a mobile money account using an OCT.
• Purchase and ATM: VMP accounts can be used for retail purchases, including electronic
commerce. Transactions can be initiated at ATMs.
• Bulk Business-to-Consumer (B2C) Funds Disbursement Transactions.

1.7 Fees and Charges

Fees and charges for SMS users are collected daily through the daily settlement process
or monthly through Visa's monthly billing process.

1.7.1 Client-to-Client Fees

A fee is a vehicle for passing costs between clients. An interchange reimbursement fee
(IRF) is an example of a fee. Fees are paid by the acquirer to the issuer or by the issuer
to the acquirer.

1.7.1.1 Interchange Reimbursement Fees and Cash Disbursement Fees

There are three types of interchange reimbursement fees (IRFs).
NOTE
For ATM, these IRFs are called cash disbursement fees; however, in the generic portions of this discussion,
all such fees (IRFs and ATM cash disbursement fees) are called IRFs unless otherwise noted.

Domestic Interchange Reimbursement Fees—Fees paid by one participant to another

for transactions acquired and issued in the same country.

1-26 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 1: Single Message System Overview Fees and Charges

Intraregional Interchange Reimbursement Fees—Fees paid by one participant to

another for transactions acquired and issued in different countries within the same Visa
region.

Interregional Interchange Reimbursement Fees—Fees paid by one participant to

another for transactions acquired and issued in different Visa regions. For ATM, these are
also referred to as international ATM cash disbursement fees.

In this context, transaction country is the country in which the transaction takes place,
and issuing country is the country of the issuer of the card used in the transaction.

If no domestic IRF has been established, the intraregional IRF applies. If no intraregional
IRF has been established, the interregional (international) IRF applies.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1-27
Fees and Charges Chapter 1: Single Message System Overview

IRFs are settled daily through the settlement process.

IMPORTANT
For National Net Settlement Service transactions, there is only one settlement currency, so balancing does
not involve currency conversion. For International Settlement Service transactions, however, there are
many settlement currencies. Visa uses buy and sell rates for currency conversion. These rates are paired
into USD-based rates used when converting non-USD currencies against the U.S. dollar, and cross-rates
(non-USD-based rates) used for selected currencies in which the rates quoted are against a currency other than
the U.S. dollar. The Multicurrency Service automatically converts the transaction currency to the acquirer's
settlement currency (if the two are different), and automatically converts the cardholder's billing currency to the
issuer's settlement currency (if the two are different), to one of the settlement currencies.

U.S.-domestic ATM cash disbursement fees are based on a tiered fee-pricing

structure. Tiers are based on the issuer’s ATM transaction volume. Once a tier is
established, the issuer pays a fixed interchange fee to the acquirer for each domestic Visa
or Plus ATM cash disbursement transaction.

(Refer to the pertinent regional fee guide for domestic ATM cash disbursement fee
structures.)

Account Transfer Fees

Account transfer fees are established by each region as applicable to each domestic
market.

Balance Inquiry and Decline Fees

Balance inquiry and decline fees are assessed to issuers and paid to acquirers. These
fees are settled monthly.

1.7.2 Fees Assessed by Visa

Some fees are passed between a client and Visa.

Access and Use Fees—These fees are for clients and processors directly connected to
VisaNet.

1.7.2.1 International Acquiring Fees (IAFs)

International acquiring fees (IAFs) are assessed by Visa to the sender of a transaction when
a transaction is acquired outside of the card issuer's country. IAFs may vary by Visa region.
The fees are usually calculated as a percentage of the transaction amount.

1.7.2.2 Special Handling Fees

Visa charges a special handling fee for international ATM transactions not submitted
for CPS/ATM consideration or fail to meet CPS/ATM fee edit criteria. This special ATM
handling fee is USD$5, and it appears on the monthly Integrated Billing statement.
The fee is not charged on a representment or returned to the acquirer on a chargeback.
Additionally, a CPS/ATM transaction submitted for clearing after the 3-calendar-day
processing limit is not returned to the acquirer but is settled and the acquirer assessed a
minimum special ATM handling fee of USD$5.

1.7.3 Charges Assessed by Visa

A charge is a vehicle used to bill clients for Visa processing costs. There are transaction
processing charges, administrative and service charges, and currency conversion charges.
A charge can be issuer- or acquirer-unique or it can apply to both. The charge paid by
the client is credited to the client's Visa region. Charging requirements vary by region

1-28 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 1: Single Message System Overview Fees and Charges

and are subject to approval by the regional board. Each region establishes the specific
criteria by which its charges are assessed.

1.7.3.1 Transaction Processing Charges

Transaction processing charges are assessed by Visa to issuers and acquirers for
transactions processed through VisaNet. These charges, which may vary by transaction
type, are billed monthly.

1.7.3.2 Administrative and Service Charges

Administrative and service charges include:
• Cardholder Database Residency Charges—These charges are for items maintained on
the Exception File and on the PIN Verification File.
• Cardholder Database File Update Charges—These charges are for updates made to
the Exception File and to the PIN Verification File.
• Settlement and Reconciliation Charges—These charges are for additional funds
transfers over and above the single transfer per VisaNet endpoint per day, which can
be made at no charge.
Most administrative and service charges are billed monthly.

1.7.3.3 Currency Conversion Charges

Currency conversion charges are assessed by Visa when the transaction currency (currency
dispensed at the ATM) and the issuer's cardholder billing currency (currency posted to the
cardholder's account) are different. Visa assesses and settles charges daily.

See Chapter 5, Multicurrency Support, for more information about currency conversion.

Refer to the applicable Visa Rules for detailed descriptions of fees and charges.

1.7.4 Reporting Fees and Charges

Visa reports fees and charges on a daily and monthly basis. Individual transactions
processing systems pass SMS charges to an internal billing system, which consolidates
them for reporting to clients. Visa also reports administrative and service charges, such as
monthly VisaNet connection and VisaNet connection method access charges. Transaction
processing charges are accumulated daily and billed monthly. Charges settled by other
Visa systems are included in the reports to provide a complete accounting of Visa charges
for clients. IBS reports are produced monthly.

1.7.4.1 Daily Fee Reporting

Reimbursement fees are listed on the daily reconciliation summary reports. Fees and
charges assessed by Visa are reported on the daily settlement reports.

1.7.4.2 Monthly Reporting

Monthly reports list transaction processing charges and administrative and service
charges. Monthly reports include accumulated daily charges.

The internal billing system reports all client-to-Visa charges on a monthly basis,
accumulating daily charges for this billing. Categories reported include:
• Transaction processing charges.
• Administrative and service charges.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1-29
Fees and Charges Chapter 1: Single Message System Overview

THIS PAGE INTENTIONALLY LEFT BLANK.

1-30 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
 SMS Transactions 2
This chapter identifies the transactions VisaNet supports for the SMS ATM Service, gives a
brief description of each transaction type, and explains how SMS ATM participants
maintain message integrity for transactions.

Cardholders at ATMs initiate most SMS ATM transactions. Acquirers and issuer initiate
other transactions. Systems generate some transactions; the issuer's or the acquirer's
back-office initiate some others.
IMPORTANT
The term mandatory refers to a client requirement and means a field must be present in a message and must
contain certain values. Conditional refers to a client requirement applying under specified conditions. While
the V.I.P. System enforces edits and rejects transactions for some violations of mandatory requirements, V.I.P.
does not enforce edits for all mandatory or conditional fields and values.
Visa strongly urges clients and their processors to comply with mandatory field requirements. Failure to
do so can result in greater risk to the client or increased processing cost, and may result in exposure to
chargebacks and compliance claims, elevated decline rates, and disqualification for preferential interchange
rates. Visa also advises clients not to rely on the V.I.P. System to reject all transactions not complying with
mandatory or conditional requirements.

2.1 Transaction Types

Table 2-1 lists the transaction types supported by SMS for ATM.

Table 2-1 ATM Transaction Types

Transaction Type Message Type Visa ATM/Plus Visa ATM Only

Cardholder (or Customer) Transactions
ATM Cash Disbursement 0200
Account Transfer (domestic only) 0200
Balance Inquiry 0200
Plus Shared Deposit 0200

(Plus domestic only)

System-Generated Transactions
Reversal 0420
Cash Disbursement 0220
Adjustment—Misdispense
Exception Transactions (Can Be Submitted Using Visa Resolve Online [VROL])
Adjustment 0220
Chargeback 0422

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 2-1
Transaction Types Chapter 2: SMS Transactions

Table 2-1 ATM Transaction Types (continued)

Transaction Type Message Type Visa ATM/Plus Visa ATM Only

Chargeback Reversal 0422
Representment 0220
Fee-Related Transactions
Acquirer-Generated Fee Collection/Funds 0220
Disbursement
Issuer-Generated Fee Collection/Funds 0422
Disbursement
Reconciliation Transactions 0520
File Maintenance Transactions
Online File Maintenance 0120
Online File Maintenance 0302
Automatic Cardholder Database Update 0322
(Auto-CDB) Service
Administrative Transactions (Can Be Submitted Using Visa Resolve Online [VROL])
Free-Text 0600
Funds Transfer 0620
Collection-Only 9240/9242

NOTE:
9240 messages cannot be submitted using
VROL.

Online Fraud Reporting 9620

VSDC Administrative Transactions
Chip-Based POS Offline Decline 0120
Chip-Based POS Authentication Failure 0620
and/or Script Update Results
Network Management Transactions
Network Management Transactions 0800

For details about message types, see Chapter 4, Message Types and Flows. For details
about message formats and field descriptions, refer to V.I.P. System SMS ATM Technical
Specifications, Volume 1 and Volume 2.

2.1.1 Cardholder Transactions

The following transactions are initiated by a cardholder at an ATM.

ATM Cash Disbursement—The cash disbursement is the basic ATM transaction illustrated
in Figure 1-4, in Chapter 1, Single Message System Overview. Issuers and acquirers must
support it.

Account Transfer (Domestic Only)—An account transfer is an ATM request to transfer

funds between a cardholder's two accounts at the same financial institution.

2-2 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 2: SMS Transactions Transaction Types

Balance Inquiry—Balance inquiry transactions enable cardholders to check their balances

at ATMs. The inquiry is initiated when the ATM reads the card electronically and the
cardholder enters the PIN.

If the issuer system cannot be reached, V.I.P. stand-in processing (STIP) responds the issuer
is not available. If the issuer is available and supports balance inquiries, VisaNet returns
the account balance to the acquirer for display or for printing in the currency of the ATM.

Acquirers in the U.S. region must support balance inquiries; support of this transaction is
optional for all other participants.

Plus Shared Deposit (U.S. Domestic Only)—Plus shared deposit is available for
U.S.-domestic Plus ATM.

2.1.2 System-Generated Transactions

The following transactions are system-generated:
• Reversals
• ATM cash disbursement adjustment and misdispense transactions
The following subsections describe system-generated transactions SMS supports for ATM.

2.1.2.1 Reversals
Acquirers and V.I.P. use reversals to reverse approved cash disbursements not completed
as requested. Reversals must immediately follow the transactions being reversed.

A reversal transaction can be initiated by an ATM, by an acquirer's host system, or by V.I.P.

A reversal transaction is system-generated.

Issuers and acquirers must match reversals to the corresponding financial transactions by
using tracing data, as described in “Message Integrity” in this chapter.

There are two types of reversal transactions: reversal requests and reversal advices.
Visa prefers reversal advices. Each must occur on the same calendar day as the transaction
being reversed.

Acquirer-Generated Reversals—Acquirers generate a reversal in the following

circumstances:
• When the cardholder cancels the financial transaction or when the transaction is
cancelled for other reasons.
• To reverse a prior request when the acquirer's system did not receive a response,
received a late response, or is unable to forward an approval response to the ATM.
• When the ATM fails to dispense funds or when a completion message is not received
from the ATM.
• When a communications failure prevents transmission of a reversal request, as described
in this section. The acquirer system stores the reversal and forwards it to VisaNet when
communications are restored.
V.I.P.-Initiated Reversals—V.I.P. initiates reversal advices in the following circumstances:
• When a reversal cannot be forwarded to an issuer. In this case, V.I.P. responds to the
acquirer and stores a reversal advice for later delivery to the issuer.
• When an approval response cannot be delivered to an acquirer. In this case, V.I.P.
generates a reversal request for the issuer.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 2-3
Transaction Types Chapter 2: SMS Transactions

NOTE
SMS rejects reversal response messages without response codes of 00 in field 39 with reject code 0087—Invalid
Value or Reject Code 0590—Invalid Value (Not 00 or 55 When it Should Be).

2.1.2.2 Cash Disbursement Adjustments

There are three situations in which an SMS ATM acquirer uses a debit or credit cash
disbursement adjustment:

Partial Dispense or Misdispense—The amount dispensed from the ATM does not match
the previously approved financial transaction amount.

Late Completion—The acquirer receives an approval and passes it to the ATM.

The acquirer cannot confirm the transaction was completed successfully, so it reverses
the transaction. After the reversal is processed, the acquirer determines whether the
transaction actually completed at the ATM.

Partial Dispense Detected, Previously Reversed (Plus Only)—After the transaction is

reversed, the acquirer determines a partial dispense occurred at the ATM.

VisaNet generates ATM Format Conversion (AFC) adjustment transactions to credit SMS
issuers for AFC items uncleared by acquirers within the required timeframe.

Acquirers and issuers must support this transaction.

2.1.3 Exception Transactions

The following transactions are used to correct errors that occur at the point of transaction
or in a participant's system:
• Adjustment (back-office)
• Chargeback
• Chargeback reversal
• Representment
Field 62.2—Transaction Identifier must be present in back-office exception transactions;
otherwise, the exceptions will be rejected with reason code 0153 or 0483.

Visa issuers and acquirers must support exception-related transactions. Issuer systems
must be able to create chargebacks and chargeback reversals, and to receive adjustments
and representments. Acquirer systems must be able to receive chargebacks and to
create adjustments and representments. Because authorization is not required and
exception-related transactions cannot be declined, V.I.P. always processes them as advices.

Adjustments, chargebacks, and representments must be submitted in accordance with

the Visa Core Rules and Visa Product and Service Rules.
NOTE
Chargebacks, chargeback reversals, and representments must contain field 136 and field 137 if the original
message contains them.

Adjustment (Back-Office)—An acquirer initiates an adjustment to the cardholder's

account for an original transaction to correct an error found during ATM balancing. The
adjustment can be a debit or a credit (because the cardholder's account was charged less
than or more than the actual amount agreed on at the time of the transaction).

2-4 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 2: SMS Transactions Transaction Types

Chargeback—A chargeback transaction is used to credit a cardholder's account for the

transaction amount under certain conditions.

An issuer can create a chargeback when:

• A cardholder disputes a transaction.
• The issuer itself disputes a transaction.
Chargeback Reversal—Issuers can initiate a chargeback reversal to cancel a prior
chargeback transaction that was sent in error to the acquirer.

Representment—Acquirers can initiate a representment transaction to debit a cardholder's

account when the validity of a chargeback can be disproved. The representment must be
for the exact amount of the chargeback.

Exception Handling—Acquirers and issuers need a way to create the required electronic
exception transactions. Clients can use Visa Resolve Online (VROL), or they can include
the needed data entry and transaction creation functions in their own systems.
For information about VROL, clients can contact their Visa representatives.

For SMS ATM participants that choose to do the development themselves, a key
consideration is the data source for creating exception transactions. Participants can:
• Store transaction data for later look-up, as needed, during the creation of exception
transactions.
• Include transaction data on routine reports, key-enter all needed data as the exception
transaction is created.
Developing and maintaining a database may require more development work, but
creating exception transactions is less labor intensive and less error prone. The second
approach may require less development effort, but requires more manual work to create
electronic exception transactions.

2.1.4 Fee-Related Transactions

Fee-related transactions can be submitted by an issuer, by an acquirer, or by V.I.P. and
do not require authorization. Because authorization is not required and fee-related
transactions cannot be declined, V.I.P. always processes them as advices. Visa issuers and
acquirers must support fee-related transactions.

There are two types of fee-related transactions for ATM having financial value:

Fee Collection—This transaction is used to collect miscellaneous fees.

Funds Disbursement—This transaction is used to remit miscellaneous fees.

2.1.5 Reconciliation Transactions

VisaNet uses an automatic reconciliation advice to indicate that the settlement day is
closed and that no more transactions will be processed for that settlement date.

2.1.6 File Maintenance Transactions

File maintenance transactions are used by issuers that subscribe to one or both of the
following:

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 2-5
Transaction Types Chapter 2: SMS Transactions

• PIN Verification Service (PVS)

• Automatic Cardholder Database Update (Auto-CDB) Service
For information about these services, refer to V.I.P. System Services, Volume 2.

There are two types of file maintenance transactions:

File Update—Issuers use this transaction to update their entries in the PIN Verification File
or in the Exception File. V.I.P. provides update advices for Auto-CDB Service participants.

File Inquiry—Issuers use this transaction to review their entries in the PIN Verification File
or in the Exception File.

Issuers can submit file maintenance transactions as individual messages or in batch mode.

For details about online file maintenance messages, refer to Chapter 4, Message Types
and Flows, and to the message formats chapter of V.I.P. System SMS ATM Technical
Specifications, Volume 1 and Volume 2.

For details about batch file maintenance, refer to the files appendix of V.I.P. System SMS
ATM Technical Specifications, Volume 1 and Volume 2.

2.1.7 Administrative Transactions

Administrative messages, which are initiated by an SMS ATM participant's operations staff,
are used to request or to convey information between participants.

ATM administrative messages consist of:

Free-Text Message—This message is used to provide or to request information of a

general nature for ATM transactions. Because these messages contain free text, rather
than codes, they can be routed to a printer, for manual evaluation, or can be documented
on a report.

Administrative free-text messages must be supported by all issuers and acquirers other
than Interlink issuers and acquirers. Supporting these messages is optional for Interlink
issuers and acquirers.

Funds Transfer—This message is used to send the day's final funds transfer totals after
completion of settlement and reconciliation.

Collection-Only Transaction—Collection-only transactions are intraprocessor Visa

transactions processed entirely outside of VisaNet. SMS collection-only transactions
submitted to VisaNet are not cleared, settled, or reported. Instead, VisaNet channels
these transactions into special data warehouses where the transactions are available
for selection for various Visa promotional programs, such as Visa Rewards and Our
Treat. Submission of these transactions is optional. No client action is required for Visa
to warehouse these transactions.

Online Fraud Reporting—This message is used to report fraud transactions that VisaNet
passes to the Fraud Reporting System (FRS). These messages are available to Visa and
Visa Electron.
NOTE
SMS rejects all administrative response messages that do not contain a response code of 00 in field 39 with
reject code 0087—Invalid Value or Reject Code 0590—Invalid Value (Not 00 or 55 When it Should Be).

2-6 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 2: SMS Transactions Transaction Sets

2.1.8 Network Management Transactions

SMS ATM acquirers and issuers must support all network management transactions,
except the reconciliation request and the dynamic key exchange message, which are
optional.

Clients use network management transactions to communicate information about system

status between VisaNet and clients. Clients also use them to initiate various types of
failure recovery and reconciliation activities.

Clients use network management transactions to perform the following functions:

Sign-On—Issuers and acquirers use this function to notify VisaNet that they are available
to send and to receive messages.

Sign-Off—Issuers and acquirers use this function to notify VisaNet that they are not
available.

Recovery Sign-On—Issuers and acquirers use this function to request delivery of advice
messages.

Recovery Sign-Off—Issuers and acquirers use this function to indicate that they do not
want to receive advice messages.

Reconciliation Request—Issuers and acquirers use this function to request the current
day's processing totals.

Echo Test—Issuers, acquirers, and VisaNet use this function to confirm the availability of
the communications link between the client's host system and VisaNet.

Dynamic Key Exchange—Issuers, acquirers, and VisaNet use this function to update
working keys online. Refer also to V.I.P. System Services, Volume 2, for a description of
the Dynamic Key Exchange (DKE) Service.

2.1.9 VSDC Transactions

For information about Visa Smart Debit/Smart Credit (VSDC) transactions, refer to the
sources listed in About This Manual.

For field values and message formats that pertain to the VSDC product, refer to
V.I.P. System SMS ATM Technical Specifications, Volume 1 and Volume 2.

2.2 Transaction Sets

VisaNet uses transaction sets to manage all authorizations and financial messages.
A transaction set consists of related messages. It enables the acquirer to establish
relationships between messages and allows VisaNet and the issuer to identify those
relationships. A transaction set provides all three parties with the controls needed for
real-time account posting and for updating settlement accumulators.

A transaction set consists of one or more transactions. A transaction consists of one or

more system transactions. A system transaction is a pair of messages: a request and a
response, or an advice and an advice response.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 2-7
Message Integrity Chapter 2: SMS Transactions

Within a given transaction set, SMS allows only certain transactions, and within a given
transaction, SMS allows only certain system transactions.

Table 2-2 lists the valid ATM transaction sets, and within each set, the allowable
transactions and valid system transactions. System transactions are, from left to right in the
table, the original request, reversal, chargeback, chargeback reversal, and representment.

Note that this table shows all transactions permitted in a transaction set, not those that
would be present for a typical transaction set. If a transaction is completed satisfactorily
under normal conditions, the set contains only the original submission.

Table 2-2 Visa ATM and Plus Transactions

System Transactions

Allowable Chargeback
Transaction Set Transactions Request Reversal Chargeback Reversal Representment
ATM Cash Cash Disbursement
Disbursement
Cash Disbursement
Adjustment
Back-Office
Adjustment
Balance Inquiry Balance Inquiry
Plus Shared Deposit Plus Shared Deposit

2.3 Message Integrity

Maintaining message integrity is critical to V.I.P. SMS processing. Message integrity assures
participants that all other participants have followed Visa processing rules and that a
participant can act on a message or a transaction as defined—for instance, a completed
transaction was actually completed and a cancelled transaction was, in fact, cancelled.

Ensuring message integrity requires that all participants keep track of incoming and
outgoing messages and generate reversals for transactions that cannot be completed.
This process involves concepts of transaction tracing, transaction control, and transaction
sets.

Transaction tracing can be accomplished by using the message type and one or more other
key data elements to match request and response messages, to match reversals to original
transactions, and to tie a transaction, such as a chargeback, to the original transaction.

Key data elements include:

• Transmission date and time.
• System trace audit number.
• Transaction identifier (TID).
• Acquiring institution ID.

2-8 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 2: SMS Transactions Message Integrity

• Retrieval reference number.

• Original data elements.
NOTE
V.I.P. assigns a transaction identifier (TID) in field 62.2 to all POS and ATM dual- and single- message
transactions, including preauthorization messages and V.I.P.-format Plus transactions.

The acquirer must use messages that are consistent within a transaction set. SMS enforces
these rules by comparing an incoming message with previous messages containing the
same key data elements. In general, SMS rejects messages that are out of context or out
of sequence. SMS issues reject code 0514 if the response message cannot be matched
with the request.

VisaNet performs consistency editing to prevent invalid, out-of-context messages from

being sent to an issuer.

2.3.1 The Inter-Task Table (ITT)

The Inter-Task Table (ITT) uses the following fields to match requests and responses and
to identify repeat or duplicate requests:
• Field 32—Acquiring Institution Identification Code
• Field 37—Retrieval Reference Number
• Field 41—Card Acceptor Terminal Identification
• Field 42—Card Acceptor Identification Code
• Field 63.1—Network Identification Code
NOTE
Acquirers must exercise caution if reusing field 37 values when submitting authorization requests.

IMPORTANT
The first four digits of field 37 must contain a valid Julian date in the yddd format, where the first digit =
0–9 and the next three digits = 001–366.

SMS can also use other message fields, such as Field 7—Transmission Date and Time and
Field 11—System Trace Audit Number to link messages, although the system does not
retain them in the ITT. The ITT retains a transaction’s key field information until the issuer
or STIP sends a response to that transaction.

Certain card type transactions require that the ITT not restore values from certain fields
when those values differ between the request and the response, for instance, when the
amount in field 4 in the response to certain private-label requests is different from the
amount in field 4 in its corresponding original request.

2.3.1.1 Transaction Identifier (TID)

Field 62.2—Transaction Identifier is a key field for message identification and matching.
V.I.P. assigns a TID to all transactions.

SMS assigns a TID to all 0100 authorizations, 0200 full financial requests, 0120 and 0220
STIP advices. SMS returns the TID to acquirers in 0110, 0130, 0210, and 0230 responses.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 2-9
Message Integrity Chapter 2: SMS Transactions

Field 62.2 is mandatory in 0400 reversals (including partial reversals) and 0420 reversal
advices. SMS returns this field in 0410 and 0430 responses even if the issuer does not
include it in the response.

This field is also present in 0220 representments, 0282 representment status advices, 0422
chargebacks, 0432 chargeback responses, and in chargeback reversals and their responses.

V.I.P. does not send field 62.2 to gateway issuers. V.I.P. returns this field to acquirers
in gateway response messages.

2.3.2 Message Validity

A transaction set cannot include invalid transactions. For instance, a cash disbursement
transaction set cannot include a balance inquiry.

A transaction cannot be processed with invalid system transactions. For instance, a cash
disbursement adjustment cannot be reversed.

In addition, the function of a response must correspond to the function of the request.
For instance, a reversal response to a cash disbursement request is not valid.

2.3.3 Transaction Sequence

Within a transaction set, transactions must be processed in a logical sequence.
For instance, in a cash disbursement transaction set containing an adjustment, the original
cash disbursement must precede the adjustment.

2.3.4 Account Number Consistency

Within a transaction set, all messages requiring an account number must contain the
same account number. If the first message in a transaction set contains an account
number, the same account number must be used in all subsequent messages that require
an account number.

2.3.5 Amount Consistency

The value in Field 4—Amount, Transaction must be identical in all request and response
pairs that require an amount.

All transactions within a transaction set must contain the same transaction amount except
for chargebacks, chargeback reversals, representments, and adjustments. Chargeback
reversals and representments must be for the same amount as for the chargebacks.

The requirement for amount consistency has the following impacts:

• Approvals must be for the amounts requested.
• Reversals must always be for the full amounts.

2.3.6 Processing Duplicate Messages

A duplicate message has the same message type and key data elements (acquiring
institution ID, retrieval reference number, trace number, transmission date and time, and
transaction identifier) as a prior message. V.I.P. processes duplicates as follows:

2-10 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 2: SMS Transactions Message Integrity

• If processing of the original request was completed (a response was sent), V.I.P. responds
to the acquirer with response code 94 (duplicate transmission) in field 39 and, optionally,
includes the original response value in field 44.11. In this case, V.I.P. does not involve
STIP or the issuer. V.I.P. logs the request and the response.
For duplicate transactions from BASE I acquirers to SMS issuers, SMS sends to BASE I
the field 39 response code and the field 38 authorization code from the original.
• If processing of the original request is still in progress, V.I.P. logs the duplicate and
discards it. (V.I.P. assumes that the original will be completed; therefore the duplicate is
not needed.)
If a time-out occurs and an acquirer chooses to retry the authorization request, it must
generate a reversal followed by a new request. Repeats are not allowed for SMS ATM
transactions.

For ATM transactions destined for SMS issuers that do not participate in the ATM Format
Conversion Service, V.I.P. converts 0101 repeat messages from BASE I acquirers to 0100
messages and converts 0401 messages to 0420 messages before forwarding them to
SMS issuers.

For ATM transactions destined for SMS issuers that participate in the ATM Format
Conversion Service, V.I.P. converts 0101 repeat messages from BASE I acquirers to 0200
messages and converts 0401 messages to 0420 messages before forwarding them to
SMS issuers.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 2-11
Message Integrity Chapter 2: SMS Transactions

THIS PAGE INTENTIONALLY LEFT BLANK.

2-12 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
 SMS Participation Requirements 3
This chapter summarizes the required and optional functionality for acquirers and for
issuers that participate in the SMS ATM Service. The subsequent chapters of this manual
describe these functions in detail.

3.1 General Requirements

Participating acquirers and issuers must meet certain processing and operations
requirements. Issuers and acquirers also have a variety of service and processing options
from which to choose when developing their individual SMS ATM programs.

SMS ATM acquirers and issuers must establish an in-house processing center or must
designate another center or third-party processor to perform the necessary processing
functions. The processing center needs to have the systems necessary to supply merchant
support services, cardholder support services, or both. Support services include the
ability to communicate with the merchant sites and cardholders, and with VisaNet at the
VisaNet Interchange Center (VIC).

Acquirers and issuers must be able to send and to receive the transactions described
in this chapter.

Except where noted, all SMS ATM acquirers and issuers must:
• Use the VisaNet standard International Organization for Standardization (ISO) message
format and observe all rules for its use. To ensure message integrity, acquirers and
issuers must keep track of incoming and outgoing messages, recognize and eliminate
repeats, and generate reversals for transactions that cannot be completed.
• Use VisaNet connections—Visa Extended Access Servers (EA Servers).
• Comply with all applicable Visa Rules.
• Log all transactions, whether approved or declined, to reconcile to Visa settlement
positions.
• Support exception processing, as described later in this chapter.
• Support personal identification numbers (PINs). Processing requirements must meet the
standards specified in the Payment Technology Standards Manual. PINs are required
for ATM.
• Participate in the Multicurrency Service and be able to receive multicurrency fields
in online messages and in raw data files if the client chooses the raw data option.
(Multicurrency processing is not required for issuers whose cardholder billing and
settlement currencies are U.S. dollars.)
• Participate in the Card Verification Value (CVV) Service, which is mandatory for Visa cards
in all regions. Participation in the CVV Service is optional for Plus issuers connected to
VisaNet. Refer to Chapter 6, Stand-In, CVV, and CVV2 Processing, for more information.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 3-1
Acquirer System Requirements Chapter 3: SMS Participation Requirements

• Participate in the Cardholder Authentication Verification Value (CAVV) Verification

Service if they participate in Verified by Visa.
• Participate in the Fraud Reporting System (FRS) and be able to create 9620 advice
messages. (The 9620 message requirement does not apply to Plus ATM participants.)
For more information, refer to Chapter 4, Message Types and Flows.
• Participate in the VisaNet Settlement Service (VSS).

3.1.1 Testing
Visa must test clients' connections to VisaNet and must test centers' message processing
capabilities before they can use SMS. During the testing process, the processing center
sends and receives test messages. Visa monitors the transactions to ensure that the
processing center is able to process all message types correctly. The process covers all
relevant message types, raw data, and reports.

Once successfully tested, clients can begin initiating and receiving SMS transactions.
Alternatively, clients can designate third-party processors to complete the testing process
and process SMS transactions on the client's behalf.

Online testing services are available from your Visa representative. Clients can contact
their Visa representatives for complete information about testing.

3.2 Acquirer System Requirements

The processing center must establish a means of communication between itself and all of
its acquirers' ATMs. Acquirer systems must support merchant magnetic stripe-reading
terminals and PIN pads.

3.2.1 Online Transaction Processing Requirements

Table 3-1 lists the transaction types that all SMS ATM issuers and acquirers must support.

Table 3-1 Required Transaction Types

Transaction Type Visa ATM/Plus Visa ATM Only

Cash Disbursement
Reversal
Cash Disbursement Adjustment
Adjustment (Back-Office)
Chargeback
Chargeback Reversal
Representment
Fee-Related Transactions
Administrative Transactions

(Many types can be submitted

using Visa Resolve Online [VROL].)
Free-Text Message
Online Fraud Reporting

3-2 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 3: SMS Participation Requirements Acquirer Service Options

Table 3-1 Required Transaction Types (continued)

Transaction Type Visa ATM/Plus Visa ATM Only

Funds Transfer
Network Management
Responses to All Transactions

U.S. issuers must support balance inquiries. Balance inquiries are optional for all other
participants.

3.2.2 Required Capabilities for Acquirers

The following capabilities are required for acquirers.

PIN Security
Acquirers must provide PIN security from the moment the cardholder enters the PIN until
the transaction leaves the acquirer's system. Each ATM acquirer must be capable of
accepting and translating encrypted PINs and of performing key management.

For complete and definitive PIN standards and requirements, refer to the Payment
Technology Standards Manual.

Exception Processing
Acquirers must support automated exception processing. This requirement includes the
ability to initiate adjustment, representment, and administrative messages, and the ability
to receive chargebacks, chargeback reversals, and administrative messages. Acquirers can
use Visa Resolve Online to meet this requirement.

ATM Routing Tables

Visa and Plus acquirers are required to use the Visa and Plus routing tables or the
Combined Visa/Plus Routing Table. Acquirers can contact their Visa representatives to
make arrangements for receiving the tables.

3.3 Acquirer Service Options

In addition to the transactions listed in Table 3-1, SMS ATM acquirers can use or can
support the services and the capabilities listed in Table 3-2.

Table 3-2 ATM Acquirer Options

Options Restrictions References

ATM Processing Integration n/a Appendix A, ATM Processing
(Recommended) Integration
Optional Message Types: n/a Chapter 4, Message Types and Flows
• Account Transfer (Domestic
Only)
• Balance Inquiry
• Reconciliation
Cardholder Authentication Chapter 6, Stand-In, CVV, and CVV2
Verification Value (CAVV) Processing
Verification Service
V.I.P. System Services, Volume 2

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 3-3
Issuer System Requirements Chapter 3: SMS Participation Requirements

Table 3-2 ATM Acquirer Options (continued)

Options Restrictions References

Currency Precision Service Chapter 5, Multicurrency Support

V.I.P. System Services, Volume 2

Dynamic Key Exchange (DKE) n/a Payment Technology Standards
Service Manual

V.I.P. System Services, Volume 2

Choice of Routing Tables n/a Chapter 7, Routing
Priority Routing Service n/a Chapter 7, Routing
Choice of Settlement Options n/a Chapter 8, Settlement and
Reconciliation

Visa Settlement Service (VSS) User's

Guide
Choice of Detail Reports n/a Visa Settlement Service (VSS) User's
Guide
Visa Resolve Online (VROL) Available at region's Chapter 9, Client-to-Visa Connection
discretion Options
Choice of VisaNet connection n/a Chapter 9, Client-to-Visa Connection
methods. (Clients in the U.S. Options
region connect to VisaNet through
DEX. Clients in all non-U.S. regions
connect to VisaNet through DEX
or EA Servers.)
Choice of Report Delivery Options n/a Chapter 9, Client-to-Visa Connection
Options
Receipt of Raw Data Files n/a VisaNet Settlement Service (VSS)
User's Guide, Volume 2, Reports
Visa Smart Debit/Visa Smart Credit For Visa ATM Visa Smart Debit and Credit Planning
(VSDC) Service acquirers Guide

Visa Smart Debit and Credit Member

Implementation Guide

Visa Smart Debit/Visa Smart Credit

System Technical Manual

3.4 Issuer System Requirements

Issuer systems are required to respond to SMS messages sent from VisaNet. This response
capability is a primary function of issuer systems.

In addition, issuers need to:

• Send chargebacks, administrative messages, and network management messages.
• Send online file maintenance messages.
• Receive transaction requests and approve or decline them according to internally
defined parameters. Responses must occur within a specified issuer response time or
V.I.P. processes them using stand-in processing (STIP).
• Receive and process advices from STIP.

3-4 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 3: SMS Participation Requirements Issuer System Requirements

• Issue cards in accordance with all applicable Visa Rules.

• Support PIN processing requirements as defined in the Payment Technology Standards
Manual.
In addition, all Visa cards must support the Card Verification Value 2 (CVV2) Service.
However, CVV2 values are not passed in ATM transactions. For more information, see
Chapter 6, Stand-In, CVV, and CVV2 Processing. The CVV2 requirement does not apply
to Plus cards.

SMS ATM Service issuers must support the capabilities specified in the following section.

3.4.1 Required Capabilities for Issuers

The following capabilities are required for issuers.

PIN Verification
All ATM issuers must provide PIN verification capability or must subscribe to the PIN
Verification Service (PVS).

Issuers that support ATM traditionally use the Online PIN option but may choose to add
Offline PIN functionality through the Visa Smart Debit/Smart Credit (VSDC) Service. For
more information, refer to the Visa Smart Debit and Visa Smart Credit Service Description.

Exception Processing
SMS participants must support exception processing. For issuers, this requirement includes
the ability to initiate chargebacks and chargeback reversals, and to accept adjustments,
representments, and administrative messages. Issuers can meet this requirement by using
Visa Resolve Online (VROL). (VROL is available for network ID 0002 only.)

For information about processing clearing, reconciliation, and exception messages, clients
can contact their Visa representatives.

Stand-In Processing Parameters

All issuers must supply Visa with parameters to use when the issuer systems are
unavailable or do not respond to request messages within the required time limit and
SMS makes processing decisions on the issuers' behalf.

The time limit may vary by issuer and by the type of transaction.

Depending on the Visa card product, the parameters can be as simple as specifying that
VisaNet should decline all authorizations if the issuer system cannot be reached.

ATM Format Conversion Service

All issuers must participate in the ATM Format Conversion Service, which enables SMS
issuers to receive ATM transactions from dual-message acquirers as full financial messages
(0200s). For more information about this service, see Chapter 1, Single Message System
Overview, and V.I.P. System Services, Volume 2.

SMS Advice Retrieval Service

All issuers must participate in the SMS Advice Retrieval Service, which enables issuers to
use online connections to recover all types of advices from the SMS advice file.

For information about recovering advices, see Chapter 4, Message Types and Flows,
and Chapter 6, Stand-In, CVV, and CVV2 Processing. For a full description of the SMS
Advice Retrieval Service, refer to V.I.P. System Services, Volume 2.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 3-5
Issuer Options Chapter 3: SMS Participation Requirements

3.5 Issuer Options

Table 3-3 lists additional services and features that can be used by ATM issuers.

Table 3-3 ATM Issuer Options

Options Restrictions References

ATM Processing Integration n/a Appendix A, ATM Processing
(Recommended) Integration
Optional Message Types: n/a Chapter 4, Message Types and Flows
• Account Transfer (Domestic
Only)
• Balance Inquiry
• Reconciliation messages
Optional Issuer Fee for Currency n/a Chapter 4, Message Types and Flows
Conversion
Currency Precision Service n/a Chapter 4, Message Types and Flows
STIP processing: n/a Chapter 6, Stand-In, CVV, and CVV2
• PIN Verification Service (PVS) Processing
• Modulus-10 Check-Digit
Verification
• Transaction Activity Limits
• Negative Account Control
• Expiration Date Requirement
• PIN-Entry Attempt Limits
Card Verification Value (CVV) Optional for Plus Chapter 6, Stand-In, CVV, and CVV2
Service issuers connected Processing
to VisaNet; required
for all Visa cards V.I.P. System Services, Volume 2

Cardholder Authentication n/a Chapter 6, Stand-In, CVV, and CVV2

Verification Value (CAVV) Processing
Verification Service
V.I.P. System Services, Volume 2
Flexible Times for Online Delivery n/a Chapter 1, Single Message System
of BASE II Advices Overview
Automatic Cardholder Database For Visa ATM issuers Chapter 6, Stand-In, CVV, and CVV2
Update (Auto-CDB) Service Processing

V.I.P. System Services, Volume 2

Dynamic Key Exchange (DKE) n/a Payment Technology Standards
Service Manual
Account Selection Routing n/a Chapter 7, Routing
Choice of Settlement Options n/a VisaNet Settlement Service (VSS)
User's Guide
Choice of Detail Reports n/a VisaNet Settlement Service (VSS)
User's Guide
Visa Resolve Online (VROL) Available at region's Chapter 9, Client-to-Visa Connection
discretion Options

3-6 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 3: SMS Participation Requirements Issuer Options

Table 3-3 ATM Issuer Options (continued)

Options Restrictions References

Choice of VisaNet connection n/a Chapter 9, Client-to-Visa Connection
methods. (Clients in the U.S. Options
region connect to VisaNet through
DEX. Clients in all non-U.S. regions
connect to VisaNet through DEX
or EA Servers.)
Choice of Report Delivery Options n/a Chapter 9, Client-to-Visa Connection
Options
Receipt of Raw Data Files n/a VisaNet Settlement Service (VSS)
User's Guide, Volume 2, Reports
Visa Smart Debit/Smart Credit For Visa ATM issuers V.I.P. System Services, Volume 1
(VSDC) Service
Visa Smart Debit and Credit Planning
Guide

Visa Smart Debit and Credit Member

Implementation Guide

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 3-7
Issuer Options Chapter 3: SMS Participation Requirements

THIS PAGE INTENTIONALLY LEFT BLANK.

3-8 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
 Message Types and Flows 4
This chapter describes the message flows for SMS ATM transactions. It explains which
message types are used and how messages are exchanged. Each flow description includes
a diagram showing which messages are passed between the acquirer, the issuer, and SMS.

This chapter contains two sections:

• Standard Processing—This section describes the flows for the following transactions
processed under standard conditions:
- Cardholder Transactions
- System-Generated Transactions
- Exception Transactions
- Reconciliation Transactions
- File Maintenance Transactions
- Administrative Transactions
- Network Management Transactions
• Exception Conditions—This section describes the flows for the following transactions
when an endpoint is not available, responds late, or fails to respond:
- Financial Transactions
- Reversals
- Exception Transactions

4.1 Standard Processing

This section describes the following transactions processed under standard conditions.
• Cardholder Transactions
- Purchase and Cash Disbursement
- Balance Inquiry
- Account Transfer (Domestic ATM Only)
• System-Generated Transactions
- Reversal
- Cash Disbursement Adjustment—Misdispense (ATM Only)
• Exception Transactions
- Adjustments Including Adjusting Duplicates
- Chargeback
- Chargeback Reversal
- Representment
- Fee-Related Transaction
• Reconciliation Transactions
- Funds Transfer Totals Message
- Reconciliation Advice

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-1
Purchase and Cash Disbursement Chapter 4: Message Types and Flows

• File Maintenance Transactions

- Online File Maintenance
- Automatic Cardholder Database Update
• Administrative Transactions
- Free-Text Message
- Funds Transfer Message
- Online Fraud Reporting
• Network Management Transactions
- Sign-On and Sign-Off Message
- Echo Test Message
- Recovery Sign-On and Sign-Off Message
- Dynamic Key Exchange

4.1.1 Cardholder Transactions

The following flow diagrams and descriptions illustrate the flows for ATM transactions
initiated by the cardholder.

4.1.1.1 Purchase and Cash Disbursement

Acquirers in the U.S. region that do not participate in real-time clearing (RTC) must follow
0100 Visa AFD transactions with an 0120 acquirer confirmation advice that contains the
actual transaction amount. If the issuer supports 0120 confirmation advices, VisaNet
forwards the message to the issuer. If the issuer does not support these advices, VisaNet
processes the transaction in STIP and responds to the acquirer with an 0130 message.

Issuers must be able to support AFD status check and confirmation advices. In these
messages, field 25 must contain valid values other than 06, which should only be received
in real-time clearing fuel transactions.

An ATM cash disbursement is a request to authorize, post, and settle a transaction for the
withdrawal of cash from an ATM. The withdrawal can come from a cardholder's checking,
savings, or credit card account.

Approved cash disbursements have financial impact on cardholder accounts. They result
in the updating of system settlement totals for the acquirer and issuer.

A standard cash disbursement transaction is composed of two messages:

• An 0200 request generated by the acquirer
• An 0210 response sent by the issuer
The acquirer must submit the ATM surcharge amount in Field 28—Surcharge Amount in
an ATM request message. Field 28 is mandatory for all domestic, intra-regional, and
international transactions, even if there is no surcharge and the value is zero. V.I.P. requires
field 28 in all ATM originals (0100s and 0200s) and reversals (0400s and 0420s); otherwise,
V.I.P. rejects the transaction with Reject Code 0308—Field Missing. V.I.P. does not require
field 28 in exception transactions, such as chargebacks or representments. If the issuer
participates in the Multicurrency Service, V.I.P. sends the calculated surcharge to the issuer
in field 54. Issuers must receive field 28 even when the value is zero.

4-2 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Balance Inquiry

Figure 4-1 illustrates the standard flow of a cash disbursement transaction.

Figure 4-1 Cash Disbursement Transaction Flow

Acquirer SMS Issuer

0200 Request 0200 Request

0210 Response 0210 Response

4.1.1.2 Balance Inquiry

A balance inquiry requests that a savings, a checking, or a credit card account balance
be displayed at an ATM.

For ATM, the issuer returns an amount in Field 54—Additional Amount of an 0210
response message. If the issuer does not support balance Inquiries, it can send field 54 in
0210 cash disbursement responses. Amounts are displayed in the currency of the ATM.
Acquirers in the U.S. region must support balance inquiry transactions; this transaction is
optional for acquirers in all other regions.
NOTE
For SMS POS eFunds transactions (network 0029), the acquirer receives balance information in
Field 54—Additional Amounts regardless of the issuer's selected response options. (This processing does not
apply to stand-alone balance inquiries.)

If the balance is a negative amount, the issuer returns zeros.

NOTE
If the converted transaction currency amount in field 54 exceeds the 12-character converted amount limit,
the converted currency amount value is 999999999999 (12 nines).

A balance inquiry has no financial interchange value and cannot be reversed.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-3
Balance Inquiry Chapter 4: Message Types and Flows

To distinguish the balance inquiry from other 0200 requests, the ATM puts code 30
(available funds inquiry) in the first two positions of Field 3—Processing Code. Whether
the message is a 0100 or 0200, if the acquirer has included field 3 = 30 in a balance
inquiry, Field 4—Amount, Transaction is not required. If field 4 is present, V.I.P. removes it
before the message is sent to the issuer and reinstates it in the reply to the acquirer.

If STIP returns a decline decision on behalf of the issuer, STIP creates an advice for the
issuer at the issuer's option. Issuers can set parameters in the system tables (using
the Customer Online Repository [CORE]) to prevent V.I.P. from creating advices for all
transactions processed in STIP.

If a balance inquiry transaction is processed in STIP because the transaction timed out,
STIP sets the value in Field 63.4—STIP/Switch Reason Code to 9020 (CAS response timed
out). If the default response code in STIP for a balance inquiry is 57, STIP declines
balance inquiry transactions with reason code 57 (even if the issuer is available) without
creating advices.

Figure 4-2 illustrates the standard flow of a balance inquiry transaction. It consists of a
balance inquiry request (0200) originated by the acquirer, followed by a balance inquiry
response (0210) generated by the issuer.

Figure 4-2 Balance Inquiry Transaction Flow

Acquirer SMS Issuer

0200 Request 0200 Request

0210 Response 0210 Response

4-4 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Account Transfer (Domestic ATM Only)

4.1.1.3 Account Transfer (Domestic ATM Only)

An account transfer is a request to transfer funds between a cardholder's two accounts
at the same financial institution.
NOTE
ATM account transfers are currently available for domestic transactions only.

This transaction is strictly between the cardholder and the issuer. Because there is no
settlement between the acquirer and the issuer, this transaction cannot be adjusted,
charged back, or re-presented. An account transfer can be reversed if it is necessary to
cancel the cardholder charge when the acquirer cannot deliver the response to the ATM.

STIP cannot process an account transfer on behalf of an unavailable issuer, but it does
check the account against the exception file. STIP responds and creates an advice if a
decline or pick-up code is on file.

To distinguish an account transfer from other 0200 requests, ATMs put code 40 in the first
two positions of Field 3—Processing Code.

Figure 4-3 illustrates the standard flow of an account transfer transaction. It consists of an
account transfer request (0200) originated by the acquirer, followed by an account transfer
response (0210) generated by the issuer.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-5
Reversal Chapter 4: Message Types and Flows

Figure 4-3 Account Transfer Transaction Flow

Acquirer SMS Issuer

0200 Request 0200 Request

0210 Response 0210 Response

4.1.2 System-Generated Transactions

System-generated transactions consist of reversals and cash disbursement adjustments.

4.1.2.1 Reversal
A reversal voids a financial transaction. SMS or the acquirer can generate a reversal.

ATM cash disbursements and account transfers are reversed by 0420 reversal advices.
Balance inquiries and adjustments (cash disbursement adjustments and back-office
adjustments) cannot be reversed.

ATM partial dispenses that need to be reversed must be processed as cash disbursement
adjustment transactions.

Reversals can have settlement impact. An acquirer-generated reversal of a declined

transaction has no settlement impact.

Acquirers use 0420 reversal advices for the following reasons:

4-6 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Reversal

• A previously approved financial transaction (0200) is cancelled:

- By the cardholder.
- For another reason.
Message reason code 2501 applies to such advices.
• The acquirer does not receive a response to an 0200 request and does not know if the
request was approved or was declined (message reason code 2502).
• The acquirer cannot send an approved response to the ATM (message reason
code 2502).
• The acquirer receives an approval response from SMS after it has been timed out by its
host or by the ATM (message reason code 2502).
• The acquirer receives approval of an 0200 request and sends it to the ATM but does not
receive a completion message from the ATM (message reason code 2503).
• An ATM fails to dispense funds when a transaction was approved by SMS (message
reason code 2502).
SMS uses 0420 advices when it cannot return an 0210 approval to an acquirer or cannot
forward a reversal request to an issuer.

A reversal cannot be declined nor reversed. On receipt of a reversal, the issuer should
release its hold on funds or reverse the posted transaction from the cardholder's account
and from its settlement totals. Reversals are generated to prevent errors in settlement
and in reconciliation and to enable an issuer to adjust service charges to the cardholder's
account.
NOTE
If the acquirer is reversing an original authorization that timed out, they are allowed to send zeros or blanks
in field 38.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-7
Cash Disbursement Adjustment—Misdispense (ATM Only) Chapter 4: Message Types and Flows

Figure 4-4 illustrates a standard reversal transaction flow.

Figure 4-4 Reversal Transaction Flow

Acquirer SMS

0420 Advice

0430 Advice Response

4.1.2.2 Cash Disbursement Adjustment—Misdispense (ATM Only)

Acquirers use an ATM cash disbursement adjustment to adjust the value of an ATM
withdrawal, usually within a minute or two of the original transaction. The adjustment
can be for a debit amount or for a credit amount. Cash disbursement adjustments are
used under the following circumstances:
• Partial Dispense or Misdispense—Reason Code 2002
The amount dispensed by the ATM did not match the amount approved by the issuer.
A credit or a debit adjustment for the difference is needed so that the cardholder's
account can be debited or be credited.
• Late Completion—Reason Code 2102 (Visa) or 2201 (Plus)
The acquirer received an approval and passed it to the ATM, but could not confirm
that the transaction was completed, and therefore reversed the transaction. After the
reversal was processed, the acquirer determined that the transaction was actually
completed at the ATM.
• Partial Dispense Detected, Previously Reversed—Reason Code 2202 (Plus Only)
The acquirer reversed the transaction; after the reversal was processed, the acquirer
determined that a partial dispense had occurred at the ATM.
VisaNet generates ATM Format Conversion (AFC) adjustment transactions to credit SMS
issuers for AFC items that are uncleared by acquirers within the required timeframe.

4-8 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Cash Disbursement Adjustment—Misdispense (ATM Only)

• ATM Format Conversion (AFC) Issuer Credit or Debit— Reason Code 2013 (Visa only)
Acquirers and issuers must support this transaction.

For debit adjustments, the first two positions of Field 3—Processing Code must contain
code 02, and for credit adjustments, the first two positions of field 3 must contain code 22.

Acquirers cannot reverse adjustments, but issuers can charge them back, and acquirers can
re-present adjustments. Under normal conditions, the acquirer sends an 0220 adjustment
advice to the issuer, and the issuer acknowledges with an 0230 advice response.

Figure 4-5 illustrates a cash disbursement adjustment transaction flow.

Figure 4-5 Cash Disbursement Adjustment Transaction Flow

Acquirer SMS Issuer

0220 Advice 0220 Advice

0230 Advice Response 0230 Advice Response

NOTE
For AFC issuer credit or debit transactions, VisaNet, not the acquirer, generates the advice.

4.1.3 Exception Transactions

The V.I.P. System supports the following exception transactions for the international ATM
Service:
• Adjustment (Back-Office)
• Chargeback
• Chargeback Reversal

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-9
Adjustments Including Adjusting Duplicates Chapter 4: Message Types and Flows

• Representment
• Fee-Related Transactions

4.1.3.1 Adjustments Including Adjusting Duplicates

Acquirers use a back-office adjustment when a processing error is identified, usually
through the reconciliation process. For instance, during reconciliation an ATM misdispense
or a duplication of a transaction is discovered. Adjustment advices are entered by the
acquirer's operations staff, not by the ATM.

There are debit and credit adjustment transactions:

• Debit adjustments (processing code 02xxxx)—Acquirers use this transaction when an
ATM dispensed more than the actual transaction amount.
• Credit adjustments (processing code 22xxxx)—Acquirers use this transaction when
one of the following conditions applies:
- An ATM dispensed less than the actual amount.
- The cardholder was charged for an invalid transaction.
V.I.P. also can initiate adjustment transactions (sometimes referred to as “standalone”
adjustments); for instance, an ATM Format Conversion Service adjustment to credit an
SMS issuer for ATM format conversion items that the acquirer has not cleared within the
allowed timeframe. The message reason code in field 63.3 for these ATM standalone
transactions is 2013. A transaction identifier in field 62.2 from an original transaction is
not present in the 0220 message.

The acquirer has the option of entering adjustments using Visa Resolve Online (VROL).
The issuer can receive adjustments through VROL.

Only one adjustment can be issued for a transaction.

To distinguish the adjustment from other transactions, the message reason code in
Field 63.3—Message Reason Code must be 2004 (acquirer error correction) for ATM
transactions.

Acquirers send 0220 adjustment advices. The issuer or STIP returns an 0230 advice
response to acknowledge to the acquirer that it successfully received the adjustment
advice. Issuers cannot decline an adjustment, although they can charge it back if
chargeback or return rights exist. The approval by the issuer indicates that the adjustment
has been received; it does not indicate that the issuer is in agreement with the adjustment.

Acquirers cannot reverse an adjustment. Issuers can return invalid debit adjustments
or credit adjustments through chargeback transactions, and acquirers can re-present
adjustments.

If an adjustment transaction times out (that is, an 0230 advice response is not received),
the acquirer must resend the adjustment unchanged with the same tracing elements.

4-10 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Chargeback

Figure 4-6 illustrates a standard (back-office) adjustment transaction flow.

Figure 4-6 Adjustment (Back-Office) Transaction Flow

Acquirer SMS Issuer

0220 Advice 0220 Advice

0230 Advice Response 0230 Advice Response

4.1.3.2 Chargeback
Issuers use a chargeback transaction to return a previously accepted financial transaction
to an acquirer. Issuers have the right to charge back to the acquirer posted transactions
that are disputed by the cardholder or are identified as invalid by the issuer. Chargebacks
must adhere to applicable Visa Core Rules and Visa Product and Service Rules.

Chargebacks must be submitted within a set number of calendar days from the origination
date of the transaction being charged back. The set number of days varies by the type of
chargeback and is within 45 to 180 calendar days of the original transaction.

The chargeback amount should be for the original amount and should not include
optional issuer fees. Partial chargebacks are allowed when the cleared amount exceeds
the authorized amount.

The issuer has the option of entering chargebacks using Visa Resolve Online (VROL). The
acquirer can choose to receive chargebacks through VROL.

The chargeback flows from the issuer to the acquirer—the opposite direction from other
financial transactions. The response by the acquirer acknowledges that it successfully
received and processed the chargeback. The response does not signify that the acquirer is
in agreement with the request.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-11
Chargeback Reversal Chapter 4: Message Types and Flows

Acquirers use representments to return invalid chargebacks.

If the chargeback times out at the issuer, the issuer should resend the chargeback
transaction unchanged.

A chargeback is distinguished from other messages of the same message type by code 17
in Field 25—Point-of-Service Condition Code. The reason for the chargeback is identified
in Field 63.3—Message Reason Code.
NOTE
Clients can receive Field 63.6—Chargeback Reduction/BASE II Flags in chargebacks initiated by BASE II
endpoints.

Visa allows only one chargeback transaction for an ATM cardholder transaction.
V.I.P. rejects second chargebacks for ATM transactions with Reject Code 0724—Second
Chargeback Not Permitted.

Figure 4-7 illustrates a chargeback transaction flow.

Figure 4-7 Chargeback Transaction Flow

Acquirer SMS Issuer

0422 Advice 0422 Advice

0432 Advice Response 0432 Advice Response

4.1.3.3 Chargeback Reversal

Chargeback reversals are used by issuers to cancel chargebacks that were sent in error to
acquirers. Chargeback reversals have settlement impact.

4-12 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Representment

Issuers send 0422 advices to acquirers to reverse in full chargebacks that were sent in
error. If SMS cannot deliver the advice to the acquirer, it stores the advice for later
recovery by the acquirer.
NOTE
V.I.P. stores SMS advices online for 30 days. SMS issuers that want to retrieve their advices need to retrieve
them within this 30-day period.

If the chargeback reversal times out at the issuer, the issuer should resubmit the
transaction.

A chargeback reversal must contain code 54 in Field 25—Point-of-Service Condition Code.

Under standard conditions, the acquirer receives an 0422 chargeback reversal advice from
the issuer and acknowledges it with an 0432 advice response.

Figure 4-8 illustrates a chargeback reversal transaction flow.

Figure 4-8 Chargeback Reversal Transaction Flow

Acquirer SMS Issuer

0422 Advice 0422 Advice

0432 Advice Response 0432 Advice Response

4.1.3.4 Representment
Acquirers use representments to resubmit transactions that were charged back by issuers.
An acquirer can resubmit to the issuer items that were previously charged back by the
issuer. Representments must adhere to applicable Visa Rules.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-13
Fee-Related Transaction Chapter 4: Message Types and Flows

Acquirers have the option of entering representments using Visa Resolve Online (VROL).
Issuers can choose to receive representments through VROL.

A representment cannot be reversed or be declined.

An approval response from the issuer or from STIP acknowledges that the issuer received
the request, not that the issuer agrees with the request.

If the representment times out at the acquirer, the acquirer should resend the
representment unchanged.

A representment is distinguished from other messages of the same message type by

code 13 in Field 25—Point-of-Service Condition Code. The reason for the representment
is identified in Field 63.3—Message Reason Code.

An acquirer sends an 0220 representment advice to the issuer. The issuer acknowledges
it with an 0230 advice response.

Figure 4-9 illustrates a representment transaction flow.

Figure 4-9 Representment Transaction Flow

Acquirer SMS Issuer

0220 Advice 0220 Advice

0230 Advice Response 0230 Advice Response

4.1.3.5 Fee-Related Transaction

A fee-related transaction is a fee collection or a funds disbursement transaction. Clients use
this transaction to collect or to remit miscellaneous fees such as recovered card rewards.

SMS supports fee-related transactions for Visa ATM and Plus.

4-14 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Fee-Related Transaction

Acquirers use 0220 advices to send fee-related transactions to issuers. Issuers use 0422
advices to send fee-related transactions to acquirers. These advices contain all of the
information needed for settlement. Visa Resolve Online (VROL) supports 0220 and 0422
fee messages.

Fee transactions usually do not relate directly to cardholder transactions, and therefore
usually do not result in postings to cardholders' accounts. They are financial in nature,
however, and they update settlement totals for the sender and for the receiver. Because
fee-related transactions do not require authorization and cannot be declined, they are
always processed as advice message types.

The value in Field 3—Processing Code of a fee collection must be 19xxxx. The value in
field 3 of a funds disbursement must be 29xxxx. Clients use these values to distinguish
fee-related transactions from other transactions with the same message types.

For acquirer-initiated, fee-related transactions, the acquirer sends an 0220 fee-related

advice to the issuer, and the issuer acknowledges with an 0230 advice response.

Figure 4-10 illustrates an acquirer-initiated, fee-related transaction flow.

Figure 4-10 Fee-Related Transaction Flow (Acquirer-Initiated)

Acquirer SMS Issuer

0220 Advice 0220 Advice

0230 Advice Response 0230 Advice Response

For issuer-initiated, fee-related transactions, the issuer sends an 0422 fee-related advice,
and the acquirer acknowledges receipt with an 0432 advice response.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-15
Funds Transfer Totals Message Chapter 4: Message Types and Flows

Figure 4-11 illustrates an issuer-initiated, fee-related transaction flow.

Figure 4-11 Fee-Related Transaction Flow (Issuer-Initiated)

Acquirer SMS Issuer

0422 Advice 0422 Advice

0432 Advice Response 0432 Advice Response

4.1.4 Reconciliation Transactions

SMS can send automatic reconciliation advices that indicate that the settlement day is
closed and that no more transactions will be processed for that settlement day. (Refer to
“Reconciliation Advice” in this chapter.)

Throughout the day, SMS accumulates counts and amounts of transactions that have an
effect on a participant's financial positions.

The following subsections describe processing for funds transfer totals messages and
for reconciliation advices.

4.1.4.1 Funds Transfer Totals Message

SMS creates an 0620 funds transfer totals message at the end of a processing day.
This message provides an accounting of all settlement activity that has been processed by
VisaNet. Clients can use this message for reconciliation. Clients respond with an 0630
funds transfer totals advice response message.

Figure 4-12 illustrates the funds transfer totals transaction process flow.

4-16 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Reconciliation Advice

Figure 4-12 Funds Transfer Totals Transaction Flow

Acquirer Issuer SMS

0620 Message

Funds Transfer Total

0630 Response

4.1.4.2 Reconciliation Advice

Both issuers and acquirers can receive an 0520 reconciliation advice message that indicates
that the settlement date has been cut off. These advices contain code 289 (notification of
settlement date cutoff) in Field 70—Network Management Information Code.

Clients acknowledge receipt of an advice with an 0530 reconciliation advice response

message.

Receipt of 0520 advices is optional; they can be sent at the end of day or not at
all. The option to receive 0520 messages is set up in SMS when a participant first
successfully completes testing. Participants can change this option by contacting their
Visa representatives. Clients must sign on to Advice Recovery mode to receive advices.

Figure 4-13 illustrates a reconciliation advice transaction flow with an optional 0520
advice message.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-17
Online File Maintenance Chapter 4: Message Types and Flows

Figure 4-13 Reconciliation Advice Transaction Flow

Acquirer SMS Issuer

0520 Advice 0520 Advice

0530 Advice Response 0530 Advice Response

4.1.5 File Maintenance Transactions

This section covers two types of file maintenance transactions:
• Online file maintenance
• Automatic Cardholder Database Update (Auto-CDB)
For information about batch file updates, refer to V.I.P. System SMS ATM Technical
Specifications, Volume 1 and Volume 2.

4.1.5.1 Online File Maintenance

Issuers use file-related messages to update or to review the cardholder records in the
Exception File and PIN Verification File. Issuers use 0120 and 0302 requests to:
• Update cardholder records.
• Inquire about a specific cardholder record.
Issuers use 0120 and 0302 requests to query or to update the Exception File and the PIN
Verification File. SMS does not create advices for undeliverable 0302 requests. Issuers
send 0120 and 0302 requests to SMS, and SMS responds with 0130 and 0312 responses,
respectively. Because SMS does not create file-related advices, the issuer must resend the
request later if it does not receive an 0130 and 0312 response from SMS.

Figure 4-14 illustrates a file maintenance transaction flow.

4-18 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Automatic Cardholder Database Update

Figure 4-14 Online File Maintenance Transaction Flow

SMS Issuer

0302 Request

0312 Response

4.1.5.2 Automatic Cardholder Database Update

The Automatic Cardholder Database Update (Auto-CDB) Service allows V.I.P. to update
the Exception File when issuers return pick-up response codes in authorization response
messages. Issuers receive advices of Exception File additions or updates.

Refer to Chapter 6, Stand-In, CVV, and CVV2 Processing, for more information.
See V.I.P. System Services, Volume 2, for a complete description of the Auto-CDB Service.

Figure 4-15 illustrates the flow of an Auto-CDB file maintenance transaction.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-19
Free-Text Message Chapter 4: Message Types and Flows

Figure 4-15 Auto-CDB File Maintenance Transaction Flow (Visa Only)

SMS Issuer

0322 Advice

0332 Response

4.1.6 Administrative Transactions

There are three types of administrative transactions for the SMS ATM Service:
• Free-text message
• Funds transfer message
• Online fraud reporting
The following subsections describe each of these transactions.

4.1.6.1 Free-Text Message

A free-text message is an administrative message used to convey information from a
sender (identified by the code in Field 33—Forwarding Institution Identification Code) to a
receiver (identified by the code in Field 100—Receiving Institution Identification Code).
Acquirers and issuers can communicate with each other and can get general information
from each other by sending free-text messages.

The originating center submits an 0600 request to the destination center and receives an
0610 response from the destination center. This response contains no text reply. If the
text from the originating center's 0600 request requires a text reply, the destination center
must initiate an 0600 text message in addition to the reply.

SMS accepts free-text messages for the destination client when the destination is
unavailable. The system stores an 0620 advice in the advice queue for recovery by the

4-20 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Free-Text Message

destination client. The 0620 advice requires an 0630 response from the destination client
once it recovers the advice.

Visa Resolve Online (VROL) supports these messages.

Figure 4-16 illustrates the free-text message transaction flow from acquirer to issuer.

Figure 4-16 Free-Text Message Transaction Flow (Acquirer to Issuer)

Acquirer SMS Issuer

0600 Request 0600 Request

0610 Response 0610 Response

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-21
Funds Transfer Message Chapter 4: Message Types and Flows

Figure 4-17 illustrates the free-text message transaction flow from issuer to acquirer.

Figure 4-17 Free-Text Message Transaction Flow (Issuer to Acquirer)

Acquirer SMS Issuer

0600 Request 0600 Request

0610 Response 0610 Response

4.1.6.2 Funds Transfer Message

SMS uses 0620 advices to send the day's final funds transfer totals after completion of
settlement and reconciliation. Field 48—Funds Transfer Totals, usage 6, contains the
settlement totals for the day, including subfields with acquirer, issuer, and net funds
transfer totals. The funds transfer message specifies the amount to be transferred
to or from the settlement account for the settlement ID identified by the code in
Field 99—Settlement Institution ID Code. Clients must respond to each 0620 request with
an 0630 advice response.

Clients must sign on to Advice Recovery mode to receive funds transfer messages.

Figure 4-18 illustrates a funds transfer message transaction flow.

4-22 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Online Fraud Reporting

Figure 4-18 Funds Transfer Message Transaction Flow

Acquirer Issuer SMS

0620 Advice

0630 Advice Response

4.1.6.3 Online Fraud Reporting

The online fraud reporting capability allows successfully tested clients to report fraud
transactions to the Fraud Reporting System (FRS) using online messages. Clients can send
fraud notifications through Visa Resolve Online (VROL).

Online fraud reporting is not supported for Plus.

SMS passes the fraud advices to FRS. The fraud transactions are reported to clients on the
FRS reports. Failure to comply with the fraud reporting rules as defined in the Visa Rules
can result in the loss of chargeback rights and in potential fines and penalties.

Issuers and acquirers use 9620 requests to report confirmed fraud transactions. Field 125,
usage 5, is mandatory in 9620 messages. It must be used by ICS (Issuers' Clearinghouse
Service) and NRI (Not Received as Issued) issuers reporting fraud for Visa Network 0002,
Interlink Network 0003, Plus Network 0004, and Network 0005. When SMS receives a
9620 request from the client, it generates a 9630 response.

When SMS issuers respond to 0100 authorization requests from BASE I acquirers, they can
use response code 59 in field 39 to alert Visa of suspected fraud. Along with converting
the 0210 response message to an 0110 response message, V.I.P. also changes code 59
to code 05 (decline) before forwarding the 0110 response to the acquirer. Code 05
minimizes the possibility of problems between merchant and cardholder.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-23
Sign-On and Sign-Off Message Chapter 4: Message Types and Flows

Figure 4-19 illustrates the fraud reporting message transaction flow.

Figure 4-19 Fraud Reporting Message Transaction Flow

Acquirer Issuer SMS

9620 Request

9630 Response

4.1.7 Network Management Transactions

All network management transactions are supported for ATM.

Acquirers and issuers use network management messages to:

• Sign on to and sign off from the system network.
• Perform an echo test of the communications line. (SMS also uses 0800 messages
to perform echo tests.)
• Start and stop recovery of advices.
• Perform online dynamic key exchange.
• Solicit the gross interchange totals accumulated for a settlement entity (shown in the
reconciliation message flows).
The following subsections describe the processing flows for all of these tasks.

4.1.7.1 Sign-On and Sign-Off Message

Each network endpoint must sign on to the network to identify itself. An endpoint can
sign on as an acquirer and issuer. An endpoint signs on to notify SMS that it is ready
to send and receive messages. Conversely, an endpoint signs off to notify SMS that it
is not available. Endpoints use network management requests and responses (0800s

4-24 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Sign-On and Sign-Off Message

and 0810s) with code 071 (to sign on) or code 072 (to sign off) in Field 70— Network
Management Information Code.

Issuers and acquirers typically sign off for planned maintenance activity or to attend to
software or hardware malfunctions.

Figure 4-20 illustrates the sign-on and sign-off message transaction flow.

Figure 4-20 Sign-On and Sign-Off Message Transaction Flow

Acquirer Issuer SMS

0800 Request

Sign-On

0810 Response

0800 Request

Sign-Off

0810 Response

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-25
Echo Test Message Chapter 4: Message Types and Flows

4.1.7.2 Echo Test Message

Network management requests and responses (message types 0800 and 0810,
respectively) are sent by issuers, by acquirers, or by SMS to perform echo tests. Echo test
message initiators set the value in Field 70—Network Management Information Code
to 301. Echo tests confirm the availability of the communications link between the
acquirer or the issuer and SMS.

4-26 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Recovery Sign-On and Sign-Off Message

Figure 4-21 illustrates the echo test message transaction flow.

Figure 4-21 Echo Test Message Transaction Flow

Acquirer Issuer SMS

0800 Request

Echo Test

0810 Response

0800 Request

Echo Test

0810 Response

Echo Test

4.1.7.3 Recovery Sign-On and Sign-Off Message

These messages are used by issuers and by acquirers to request and to receive advices for
transactions that were processed by STIP because there was no response, a late response,
or the issuer or the acquirer was not available to respond. Network management requests
and responses (message types 0800 and 0810, respectively) contain code 078 (for sign-on

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-27
Recovery Sign-On and Sign-Off Message Chapter 4: Message Types and Flows

recovery) or code 079 (for sign-off recovery) in Field 70—Network Management

Information Code.

Acquirer and Issuer Recovery

After an issuer or an acquirer signs on to Advice Recovery mode, SMS sends all of
the advices (0x2x messages) authorized by STIP while the issuer or the acquirer was
unavailable. The issuer or the acquirer has the option of remaining signed on to recovery
or signing off from recovery.

Typically, an issuer or an acquirer remains signed on to Advice Recovery mode so that its
system can obtain transactions processed by STIP as soon as possible.

4-28 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Dynamic Key Exchange

Figure 4-22 illustrates the recovery sign-on and sign-off message transaction flow.

Figure 4-22 Recovery Sign-On and Sign-Off Message Transaction Flow

Acquirer Issuer SMS

0800 Request

Recovery Sign-On

0810 Response

0x2x Advice

0x3x Advice Response

0800 Request

Recovery Sign-Off

0810 Response

4.1.7.4 Dynamic Key Exchange

The Dynamic Key Exchange (DKE) Service is an optional service that enables SMS clients
to change Data Encryption Standard (DES) cryptographic keys with VisaNet through the

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-29
Dynamic Key Exchange Chapter 4: Message Types and Flows

use of online 0800 and 0810 messages. For a comprehensive description of the DKE
Service, refer to V.I.P. System Services, Volume 2.

The following fields in the 0800 request are used for a DKE Service key exchange request:

Field 11—System Trace Audit Number

Field 33—Forwarding Institution Identification Code

Field 39—Response Code

Field 48, Usage 14—Dynamic Key Exchange Working Key Check Value

Field 52—Personal Identification Number (PIN) Data

Field 53—Security-Related Control Information

Field 63.1—Network ID Code

Field 70—Network Management Information Code

Field 96—Message Security Code

Field 105—Double-Length DES Key (Triple DES)

Clients use 0800 requests to request and to deliver new working keys for PIN encryption;
clients use 0810 responses to acknowledge their receipt. The 0800 message initiator, which
can be a participating acquirer or issuer, or SMS, assigns the trace number (in field 11).
Clients must return the trace number unchanged in the 0810 response. If a request must
be re-sent, its trace number comes from the original request. The message originator must
indicate which key is to be changed in Field 53—Security-Related Control Information.

Acquirers can begin using the new key after the 0810 response is sent to SMS.
For acquirers supporting a single working key, SMS has the option of processing
messages with the new key or with the old key for five minutes. After five minutes, all
acquirer-initiated messages must have PINs encrypted with the new working key.

For issuers, SMS begins using the new key upon receipt of the 0810 response (in
which the code in Field 39—Response Code is 00). For issuers supporting a single
working key, they immediately update their copy of the key upon receipt of the 0800
request from SMS. SMS continues sending messages with the old key until it receives
the 0810 response. Therefore, single-key issuers must keep a copy of the old key until
SMS begins using the new one.

If SMS encounters PIN block errors during standard message processing, SMS returns
response code 81 (cryptographic error found) in PIN in the 0800 request and initiates
an automatic acquirer key change. If the issuer encounters a PIN block error during
verification, it returns response code 81 in the 0810 response. SMS initiates an automatic
issuer working key change.

SMS has a 10-second time-out for all dynamic key exchange messages containing new
working keys. If the client does not respond within 10 seconds, SMS makes a second
delivery attempt. If the client still fails to respond, SMS cancels the key exchange attempt.

An 0800 online message includes a 4-digit key check value (in field 48, usage 14) to
verify receipt of the new cryptographic key. Clients should compare the four check digits
returned from their security module with the key check value in the message.

4-30 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Dynamic Key Exchange

If the key check value (KCV) does not match or if the client encounters a security module
error while attempting to translate the new key for storage, the client should return
response code 06 in field 39. This response code indicates that the new cryptographic key
has not been received properly.

Figure 4-23 illustrates a dynamic key exchange message transaction flow.

Figure 4-23 Dynamic Key Exchange Message Transaction Flow

Acquirer Issuer SMS

0800 Request

New Key Request or Delivery

0810 Response

0800 Request

0810 Response

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-31
Issuer Unavailable Chapter 4: Message Types and Flows

4.2 Exception Conditions

This section describes the transaction processing that occurs when an endpoint:
• Is not available.
• Fails to respond.
• Responds late.
IMPORTANT
Clients must sign on to Advice Recovery mode to receive advices.

Exception conditions apply to the following transactions:

• Financial Transactions
- Issuer Unavailable
- Issuer Unavailable—Account Listed on Exception File
- Issuer Fails to Respond
- Issuer Responds Late
- Approval Response Cannot Be Delivered to the Acquirer
- Decline Response Cannot Be Delivered to the Acquirer
• Reversals
- Reversal—Advice Response Cannot Be Delivered to the Acquirer
- Reversal—Issuer Unavailable
- Reversal—Unsolicited
• Exception Transactions
- Adjustment or Representment—Issuer Unavailable
- Adjustment or Representment—Acquirer Unavailable After Advice
- Chargeback—Acquirer Unavailable
- Chargeback—Issuer Unavailable After Chargeback
The following subsections describe processing procedures for each of these conditions.

4.2.1 Financial Transactions

Exception conditions for financial transactions include the following situations:
• Issuer unavailable
• Issuer unavailable and account listed on exception file
• Issuer fails to respond
• Issuer responds late
• Approval response cannot be delivered to the acquirer
• Decline response cannot be delivered to the acquirer
The following subsections describe processing flows for each of these financial transaction
exception conditions.

4.2.1.1 Issuer Unavailable

If the issuer is unavailable, STIP responds to the 0200 request and creates an 0220 advice
for the issuer to recover and to post. This advice indicates the request and STIP reply.
When the issuer recovers the 0220 advice, it acknowledges receipt with an 0230 advice
response.

SMS responds with response code 91 (destination unavailable) in Field 39—Response

Code if the 0200 request was for a balance inquiry or for an account transfer.

4-32 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Issuer Unavailable

Figure 4-24 illustrates the transaction flow when STIP processes an 0200 request for an
issuer that is unavailable to send a response to an acquirer's authorization request.

Figure 4-24 Issuer Unavailable Transaction Flow

Acquirer SMS Issuer

0200 Request

Unavailable

0210 Response

STIP

0220 Advice

0230 Advice Response

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-33
Issuer Unavailable—Account Listed on Exception File Chapter 4: Message Types and Flows

4.2.1.2 Issuer Unavailable—Account Listed on Exception File

If the issuer is unavailable and the account is listed on the Exception File with a pick-up
response code, STIP returns a decline response to the acquirer and stores an 0220 advice
for the issuer to recover. When the issuer recovers the advice, it acknowledges with
an 0230 advice response.
NOTE
V.I.P. stores SMS advices online for 30 days. SMS issuers that want to retrieve their advices need to retrieve
them within this 30-day period.

Figure 4-25 illustrates stand-in processing for an issuer that is unavailable to respond to an
authorization request regarding a cardholder account that is listed on the Exception File.
The issuer acknowledges the STIP advice when the issuer becomes available to recover it.

4-34 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Issuer Unavailable—Account Listed on Exception File

Figure 4-25 Issuer Unavailable—Account Listed on Exception File Transaction Flow

Acquirer SMS Issuer

0200 Request

Unavailable

0210 Response

STIP
Decline

0220 Advice

0230 Advice Response

This flow provides only one example of STIP exception conditions. STIP can also decline for
PIN verification errors or for transactions that exceed activity limits. It can approve if the
card involved appears on the Exception File as having VIP (Very Important Person) status.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-35
Issuer Fails to Respond Chapter 4: Message Types and Flows

If the issuer participates in the Automatic Cardholder Database Update (Auto-CDB)

Service, SMS updates the cardholder records in the Exception File when the issuer
responds with a response code indicating “pick up card.” This feature facilitates the file
maintenance function.

4.2.1.3 Issuer Fails to Respond

If an issuer receives a request and becomes unavailable and fails to respond within
the required time limit, SMS times out the issuer and passes the transaction to STIP.
STIP creates an 0220 advice to notify the issuer that STIP has responded to the financial
request on the issuer's behalf.

Figure 4-26 illustrates STIP standing in when the issuer has received the request but is
unable to respond before the time-out occurs.

4-36 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Issuer Responds Late

Figure 4-26 Issuer Fails to Respond Transaction Flow

Acquirer SMS Issuer

0200 Request 0200 Request

0210 Response

Unavailable
STIP

0220 Advice

0230 Advice Response

4.2.1.4 Issuer Responds Late

If the issuer is available but does not respond within the required time limit, SMS times
out the issuer and sends the transaction to STIP. STIP processes the transaction on behalf

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-37
Issuer Responds Late Chapter 4: Message Types and Flows

of the issuer and sends an 0210 response to the acquirer. Simultaneously, STIP sends an
0220 advice to the issuer.

When SMS receives an 0210 response from the issuer after the transaction was processed
by STIP, SMS :
• Rejects the 0210 response with Reject Code 515—Late Response in the reject header.
This option is issuer-selected. OR
• Discards the 0210 response. This option is the default.
Because the 0220 advice is approved or is denied based on the issuer's parameters,
the STIP financial impact to the cardholder's account may be different from that indicated
in the issuer's 0210 response.

Figure 4-27 illustrates the transaction flow when STIP stands in when the issuer receives
the request but responds late.

4-38 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Issuer Responds Late

Figure 4-27 Issuer Responds Late Transaction Flow

Acquirer SMS Issuer

0200 Request 0200 Request

0210 Response 0220 Advice

STIP

0210 Response

0210 Reject

(Issuer option)

0230 Advice Response

Discarded (default)

0210 Response

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-39
Approval Response Cannot Be Delivered to the Acquirer Chapter 4: Message Types and Flows

4.2.1.5 Approval Response Cannot Be Delivered to the Acquirer

If SMS cannot return an 0210 approval response to the acquirer because the acquirer is
unavailable, SMS reverses the transaction by creating an 0420 advice that it immediately
sends to the issuer.

The acquirer should send an 0420 reversal advice to SMS after determining that it has
not received an 0210 response.

The acquirer should send the 0420 reversal advice because there is no way for the
acquirer to know whether SMS reversed the 0200 or whether the 0210 approval response
simply never made it back to the acquirer's system in time.

If SMS has not reversed the 0200, it treats the acquirer's 0420 like a normal reversal and
forwards it to the issuer.

SMS returns an 0430 response with a response code indicating that the transaction was
reversed.

Figure 4-28 illustrates the transaction flow of an approval that cannot be delivered to the
acquirer.

4-40 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Decline Response Cannot Be Delivered to the Acquirer

Figure 4-28 Approval Response Cannot Be Delivered to the Acquirer

Transaction Flow

Acquirer SMS Issuer

0200 Request 0200 Request

0210 Response
Unavailable
Approval

0420 Advice

0430 Advice Response

0420 Advice

0430 Advice Response

4.2.1.6 Decline Response Cannot Be Delivered to the Acquirer

If SMS cannot return an 0210 decline response to the acquirer because the acquirer is
unavailable, SMS logs and discards the 0210 decline response.

Figure 4-29 illustrates the transaction flow of a decline response that cannot be delivered
to the acquirer.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-41
Reversal—Advice Response Cannot Be Delivered to the Acquirer Chapter 4: Message Types and Flows

Figure 4-29 Decline Response Cannot Be Delivered to the Acquirer Transaction

Flow

Acquirer SMS Issuer

0200 Request 0200 Request

0210 Response

Unavailable
Decline

Discarded

0210 Response

4.2.2 Reversals
There are three types of reversal transaction scenarios:
• Reversal advice response cannot be delivered to acquirer
• Reversal with issuer unavailable
• Reversal that is unsolicited
The following subsections describe processing flows for each of these reversal scenarios.

4.2.2.1 Reversal—Advice Response Cannot Be Delivered to the Acquirer

If SMS cannot forward an 0430 advice response to the acquirer because the acquirer is
unavailable, SMS logs and discards the advice response. When the acquirer becomes
available, it must resend the 0420 advice. SMS acknowledges with an 0430 advice
response.

Figure 4-30 illustrates the transaction flow when a reversal advice response cannot be
delivered to the acquirer.

4-42 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Reversal—Issuer Unavailable

Figure 4-30 Reversal—Advice Response Cannot Be Delivered to the Acquirer

Transaction Flow

Acquirer SMS Issuer

0420 Advice 0420 Advice

0430 Advice Response

Unavailable

Discarded

0430 Advice Response

0420 Advice (resend)

0430 Advice Response

4.2.2.2 Reversal—Issuer Unavailable

If the issuer times out or is unavailable, SMS responds to the acquirer and stores an 0420
advice for recovery by the issuer. The issuer acknowledges with an 0430 response.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-43
Reversal—Issuer Unavailable Chapter 4: Message Types and Flows

NOTE
V.I.P. stores SMS advices online for 30 days. SMS issuers that want to retrieve their advices need to retrieve
them within this 30-day period.

In certain cases, when SMS processes an 0420 reversal, SMS finds no activity count
for the previous transaction during its routine activity check. This situation occurs
because in the previous transaction, the issuer approved the corresponding 0200 original
and consequently, V.I.P. did not update the activity count in the CDB. In such cases,
V.I.P. responds with response code 21 (no action taken) in field 39. Therefore, issuers must
be able to accept response code 21 in field 39 in 0420 SMS ATM reversal advices.

Figure 4-31 illustrates the transaction flow of a reversal when the issuer is not available.

4-44 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Reversal—Unsolicited

Figure 4-31 Reversal—Issuer Unavailable Transaction Flow

Acquirer SMS Issuer

0420 Request

Unavailable

0430 Response

STIP

0420 Advice

0430 Advice Response

4.2.2.3 Reversal—Unsolicited
If SMS receives an 0420 reversal request which has no original transaction history,
that is, if the reversal does not match an earlier financial request, SMS declines the

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-45
Adjustment or Representment—Issuer Unavailable Chapter 4: Message Types and Flows

transaction with response code 76 (unsolicited reversal) in the 0430 response message.
The transaction has no financial impact.

Figure 4-32 illustrates the transaction flow of an unsolicited reversal.

Figure 4-32 Reversal—Unsolicited Transaction Flow

Acquirer SMS

0420 Advice

0430 Advice Response

4.2.3 Exception Transactions

The following exception transactions include STIP processing and some other transaction
processing performed when the issuer or the acquirer is unavailable.

4.2.3.1 Adjustment or Representment—Issuer Unavailable

If the issuer is unavailable, STIP authorizes the adjustment or the representment advice
and responds to the acquirer. STIP builds and stores an 0220 advice for issuer recovery.
NOTE
V.I.P. stores SMS advices online for 30 days. SMS issuers that want to retrieve their advices need to retrieve
them within this 30-day period.

Figure 4-33 illustrates the transaction flow of an adjustment or a representment when

the issuer is unavailable.

4-46 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Adjustment or Representment—Acquirer Unavailable
After Advice

Figure 4-33 Adjustment or Representment—Issuer Unavailable Transaction Flow

Acquirer SMS Issuer

0220 Advice

Unavailable

0230 Advice Response

STIP

0220 Advice

0230 Advice Response

4.2.3.2 Adjustment or Representment—Acquirer Unavailable After Advice

If the acquirer becomes unavailable after sending the 0220 adjustment or the
representment advice and cannot receive the response, the acquirer must resend the 0220

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-47
Adjustment or Representment—Acquirer Unavailable Chapter 4: Message Types and Flows
After Advice

advice unchanged. SMS recognizes the duplicate advice and builds a response to the
acquirer as though the duplicate advice were the original transaction.

Figure 4-34 illustrates the transaction flow of an adjustment or a representment when

the acquirer is unavailable.

4-48 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Adjustment or Representment—Acquirer Unavailable
After Advice

Figure 4-34 Adjustment or Representment—Acquirer Unavailable Transaction

Flow

Acquirer SMS Issuer

0220 Advice 0220 Advice

0230 Advice Response

Unavailable

0220 Advice (resend)

0230 Advice Response

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-49
Chargeback—Acquirer Unavailable Chapter 4: Message Types and Flows

4.2.3.3 Chargeback—Acquirer Unavailable

If the acquirer is unavailable when the issuer sends a chargeback, STIP accepts the
transaction, responds to the issuer, and builds and stores the chargeback advice for
the acquirer to recover.

Figure 4-35 illustrates the transaction flow when STIP authorizes a chargeback.

4-50 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Chargeback—Issuer Unavailable After Chargeback

Figure 4-35 Chargeback—Acquirer Unavailable Transaction Flow

Acquirer SMS Issuer

0422 Advice

Unavailable

0432 Advice Response

STIP

0422 Advice

0432 Advice Response

4.2.3.4 Chargeback—Issuer Unavailable After Chargeback

If the issuer becomes unavailable after sending an 0422 chargeback advice and before
receiving the response, the issuer must resend the chargeback unchanged. Upon receipt
of the re-sent 0422 advice, SMS recognizes that the original request was processed and

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-51
Chargeback—Issuer Unavailable After Chargeback Chapter 4: Message Types and Flows

forwards to the issuer the 0432 advice received from the acquirer in response to the
original request.

Figure 4-36 illustrates the transaction flow when the issuer is unavailable after it sends a
chargeback advice.

4-52 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 4: Message Types and Flows Chargeback—Issuer Unavailable After Chargeback

Figure 4-36 Chargeback—Issuer Unavailable After Chargeback Transaction Flow

Acquirer SMS Issuer

0422 Advice 0422 Advice

0432 Advice Response

Unavailable

0422 Advice (resend)

0432 Advice Response

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 4-53
Chargeback—Issuer Unavailable After Chargeback Chapter 4: Message Types and Flows

THIS PAGE INTENTIONALLY LEFT BLANK.

4-54 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
 Multicurrency Support 5
Multicurrency support is required for all SMS ATM acquirers and issuers except those
whose cardholder billing currency and settlement currency are United States (U.S.) dollars.

SMS features full multicurrency support for international ATM transactions.

The Multicurrency Service includes:
• Automatic conversion from the transaction currency to the currency of the cardholder's
account.
• Automatic conversion from the transaction currency to the acquirer's settlement
currency (if the two are different).
• Automatic conversion from the currency of the cardholder's account to the issuer's
settlement currency (if the two are different).

The transaction currency is generally the currency of the country in which a transaction
takes place. The cardholder billing currency is generally the currency of the country in
which the account is domiciled.

SMS messages contain several multicurrency fields supporting the various amounts
involved in currency exchange calculation. These fields contain the following data:
• The transaction amount in the transaction currency
• The transaction amount in the cardholder billing currency
• The settlement amount
• The conversion rates
• The date of the conversion rate table used by SMS
Participating clients receive these standard multicurrency fields in their online messages,
reports, and raw data.

For non-participating clients, transaction and settlement amounts appear in online

messages, raw data, and reports in U.S. dollars only. Non-participating clients that migrate
to the Multicurrency Service have the advantage of using the additional information.

5.1 Currencies
SMS determines applicable currencies for a given transaction as follows:
• The acquirer indicates the transaction amount and the transaction currency in the
request message. For an ATM cash disbursement transaction, this is the currency that
was dispensed at the ATM.
• SMS determines the issuer's currencies based on the first several digits of the primary
account number (PAN), which is read from the magnetic stripe on the card used for
the transaction. These initial digits, called the BIN, are used to locate issuer-supplied

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 5-1
What the Issuer Receives Chapter 5: Multicurrency Support

data, including the cardholder billing currency and the issuer's settlement currency,
on SMS databases.
• SMS determines the acquirer's settlement currency based on the acquirer ID in the
request message. This ID is used to locate acquirer-supplied data on SMS databases.
SMS supports transaction and cardholder billing currencies recognized by the International
Organization for Standardization (ISO). Some of these currencies are also supported
as settlement currencies.

For the current list of supported currencies, see V.I.P. System SMS ATM Technical
Specifications, Volume 1 and Volume 2.

5.2 How Currency Conversion Works

VisaNet uses buy and sell rates for currency conversion. VisaNet pairs these rates into:
• USD-based rates that are used when converting non-USD currencies against the U.S.
dollar.
• Cross rates (non-USD-based rates) that VisaNet use for selected currencies for which the
rates quoted are against a currency other than the U.S. dollar.
The Multicurrency Chapter in V.I.P. System Services, Volume 2, contains a complete
description of the currency conversion process and examples of currency conversion.

Visa determines the wholesale rate five days a week (Monday through Friday) based
on the cost to Visa of buying and selling currencies on the foreign exchange markets:
Currency conversion charges vary by region.

Refer to the Visa Rules for more information.

Issuers can choose to charge an optional issuer fee to the cardholder for transactions
that require currency conversion. The issuer can specify an intraregional or interregional
optional issuer fee, or can specify both.

VisaNet maintains the optional issuer fee, which may be a mark-up or a rebate, in SMS
databases according to issuer BINs. VisaNet calculates this optional fee at the time of
currency conversion using the percentage rate the issuer establishes. To implement an
optional issuer currency conversion fee, the client must contact Visa.

All VisaNet systems that support Multicurrency Service processing use common
conversion rates.

SMS performs currency conversion in calculating settlement amounts when the acquirer's
settlement currency is not the same as the transaction currency, or when the issuer's
settlement currency is not the same as the cardholder billing currency.
NOTE
There is no settlement amount for non-financial transactions, and VisaNet does not charge currency conversion
charges to the issuer. However, to accurately reflect funds availability, VisaNet includes conversion charges
when SMS converts balance inquiry amounts for the acquirer.

5.3 What the Issuer Receives

When SMS performs currency conversion, as described in “How Currency Conversion
Works” in this chapter, the issuer receives the following. (The values are from the same
example.)

5-2 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 5: Multicurrency Support Currency Precision Service

• The transaction amount and the currency code (USD$100)

• The cardholder billing amount and the currency code (AU$126.56)
• The settlement amount and the currency code (AU$125.00)
Raw data identifies another amount, the Visa currency conversion charge (AU$1.25 in
this example), as the Conversion Charge. VisaNet charges the settlement amount plus
the currency conversion charge to the issuer. The difference between this total and the
cardholder billing amount—the optional issuer fee (in this example, AU$.31)—is revenue
for the issuer.

The issuer also receives the currency conversion rate VisaNet used for the cardholder
billing amount, and the currency conversion rate VisaNet used for the settlement amount.

5.4 Variations
The effective rate SMS uses to perform currency conversion varies based on the type
of transaction.

See V.I.P. System SMS ATM Technical Specifications, Volume 1 and Volume 2, for details
about field descriptions and message formats.

5.5 Decimal Places in Amounts

Currencies are defined as having zero, two, or three minor units of currency. For instance,
the U.S. dollar has two minor units of currency (the two positions to the right of the
decimal point); the Japanese yen has no minor units.

In online transactions processed by SMS, amounts have an implied decimal point

preceding the right-most zero, two, or three digits to handle these minor units of
currency. Based on the definition, VisaNet interprets a numeric value of 6789 as 6.789
(three minor units of currency), 67.89 (two minor units of currency), or 6789 (no minor
units of currency).

The list of currency codes in V.I.P. System SMS ATM Technical Specifications, Volume 1 and
Volume 2, indicates the number of implied decimal points in the amount fields.

Although SMS supports up to three significant decimal places in amount fields in online
messages, VisaNet assumes the third digit is zero. Therefore, the user of a currency
with three decimal places must:
1. Round the amount to a two-place accuracy, or replace the third decimal position
with zero when generating amount fields.
2. Be able to receive two-place accuracy in amount fields supplied by SMS.
For instance, entities can round the amount 9.246 to 9.250, or they can drop the third
digit for a value of 9.240.

5.6 Currency Precision Service

Multicurrency Service participants can also participate in the Currency Precision Service,
which uses Field 63.13—Decimal Positions Indicator to indicate how many decimal
positions are in the message's amount fields. The field accommodates three different
values for transaction, settlement, and cardholder amounts. SMS checks them against
the Currency Table.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 5-3
Currency Precision Service Chapter 5: Multicurrency Support

Table 5-1 lists the values allowable in field 63.13.

Table 5-1 Field 63.13 Values

Value Number of Decimal Positions

00 No decimal positions
02 Two decimal positions
03 Three decimal positions
99 Decimal positions do not apply

5.6.1 Adding a Decimal Position

If the number of decimal positions specified in field 63.13 is less than that in the Currency
Table, SMS adjusts the applicable amount fields.
EXAMPLE
An acquirer sends a transaction amount of 12345 and puts 02 in positions 1 and 2 of the decimal positions
indicator field. However, the Currency Table indicates that the currency has three decimal positions. VisaNet
reports the amount as 123450 and sends the issuer a transaction amount of 123450.
A participating issuer also receives a decimal positions indicator with 03 in positions 1 and 2 of the field.
A non-participating issuer receives 123450 in Field 4—Amount, Transaction but no decimal positions indicator
in the request.
The acquirer receives the transaction amount 123450 and 03 in positions 1 and 2 of the decimal positions
indicator field. VisaNet calculates the settlement amount based on 123450. All reports and raw data reflect
the transaction amount 123450.

Figure 5-1 illustrates an example of decimal position conversion—adding one position.

Figure 5-1 Example of One-Decimal Position Conversion

Incoming Message

Currency = Pa’anga
Amount = 12345
Decimal Positions = 02
Visa Currency Table

Pa’anga Decimal Positions = 03

Currency = Pa’anga
Amount = 123450
Decimal Positions = 03

5.6.2 Removing a Decimal Position

If the number of decimal positions specified in field 63.13 is greater than that in the table,
VisaNet removes the last digit (which must be zero).

5-4 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 5: Multicurrency Support Multicurrency Field Flows

EXAMPLE
An acquirer sends a transaction amount of 12340 with 03 in the transaction amounts subfield of the decimal
positions indicator, but the Currency Table indicates the currency has two decimal positions (see Figure 5-2).
The issuer receives 1234. A participating issuer also receives a decimal positions indicator with 02 in the
transaction amounts subfield. Non-participating issuers receive 1234 but no decimal positions indicator.
VisaNet calculates the settlement amount based on 1234. All reports and raw data reflect 1234.

Figure 5-2 illustrates an example of decimal position conversion—adding two positions.

Figure 5-2 Example of Two-Decimal Position Conversion

Incoming Message

Currency = Pa’anga
Amount = 12340
Decimal Positions = 03
Visa Currency Table

Pa’anga Decimal Positions = 02

Currency = Pa’anga
Amount = 1234
Decimal Positions = 02

The Currency Precision Service is only available to SMS participants that use the
Multicurrency Service.
NOTE
Plus acquirers and issuers participating in this service must be directly attached to SMS.

5.7 Clients Not Participating in the Multicurrency Service

Although participation in the Multicurrency Service is not currently required for issuers
whose cardholder billing and settlement currencies are U.S. dollars, VisaNet supports
currency conversion for all international transactions in that:
• The participating client will not be aware that the non-participating client is not
receiving the multicurrency data fields.
• The non-participating acquirer can receive the country code of the issuer in Field 20—
PAN Extended, Country Code.
• The non-participating issuer can identify the country of the acquirer from the value in
Field 19—Acquiring Institution Country Code.

5.8 Multicurrency Field Flows

This section provides examples of the content and the processing of amount-related fields
for online multicurrency support of SMS ATM transactions. The examples assume that the
acquirer and issuer participate in Multicurrency Service. Examples show:

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 5-5
Multicurrency Field Flows Chapter 5: Multicurrency Support

1. The fields the message originator must provide.

2. The processing performed by SMS.
3. The fields forwarded to the message recipient.
Examples are:
• Cash Disbursement With Balance Information Transaction (Figure 5-3)
• Adjustment Transaction (Figure 5-4)
• Representment Transaction (Figure 5-5)
• Balance Inquiry Transaction (Figure 5-6)
• Reversal Transaction (Figure 5-7)
• Chargeback and Chargeback Reversal Transaction (Figure 5-8)
The amounts contained in 0520 reconciliation messages are in the settlement currency
of the issuer or of the acquirer receiving the message. Settlement currencies can differ
from the local transaction currency, for an acquirer, and from the cardholder billing
currency, for an issuer.

Each example in this section assumes that the ATM has a local currency of Japanese yen,
the cardholder is billed in Australian dollars, the acquirer receives the settled amount in
U.S. dollars, and the issuer settles in Australian dollars.

The currency codes used are:

036 = Australian dollars

392 = Japanese yen

840 = U.S. dollars

The following fields are used in the multicurrency flows:

Field 3—Processing Code

Field 4—Amount, Transaction

Field 5—Amount, Settlement

Field 6—Amount, Cardholder Billing

Field 9—Conversion Rate, Settlement

Field 10—Conversion Rate, Cardholder Billing

Field 16—Date, Conversion

Field 49—Currency Code, Transaction

Field 50—Currency Code, Settlement

Field 51—Currency Code, Cardholder Billing

Field 54—Additional Amounts

Field 126.19—Dynamic Currency Conversion Indicator

Field 54 is used for account balance information. It contains the following information for
up to four different balance amounts: account type, amount type, currency code, and sign.

5-6 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 5: Multicurrency Support Multicurrency Field Flows

The issuer provides account balance information in the first amount field and optionally in
the second amount field, in the cardholder billing currency. SMS converts the first amount
and (if present) the second amount to the transaction currency and sends the converted
amounts to the acquirer in the third and fourth amount fields, respectively. In the
following examples, these amounts are referred to as fields 54A, 54B, 54A-converted,
and 54B-converted.

Field 126.19 is used to indicate if the merchant has performed Dynamic Currency
Conversion (DCC). DCC occurs when a registered merchant performs currency conversion
locally and submits the transaction in the cardholder's billing currency. Acquirers
must provide Field 126.19—Dynamic Currency Conversion Indicator in all non-ATM,
authorization, and full-financial original transactions when the merchant performs currency
conversion at the point of sale. V.I.P. logs this field but does not send it to issuers.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 5-7
Multicurrency Field Flows Chapter 5: Multicurrency Support

Figure 5-3 Cash Disbursement With Balance Information

Acquirer V.I.P. Issuer

0200 Request or
0200 Request 0220 Advice
Sends: • SMS Processing: Receives:

Fld 4 = ¥20000 • Convert value in Fld 4 Fld 4 = ¥20000

•
to billing currency and Fld 49 = 392
Fld 49 = 392
include conversion Fld 6 = AU$252.50
charges and fees;
Fld 10 = .012625
use to add Fld 6
Fld 51 = 036
•
Calculate and add Fld 10
Fld 5 = AU$250.00
•
Add Fld 51
Fld 9 = .0125
• Convert transaction
amount to settlement Fld 16 = 09/28
currency; add Fld 5 Fld 50 = 036
•
Add Fld 9
• Add Fld 16
•
Add Fld 50
0210 Response 0210 or 0230 Response

Receives: •
SMS Processing: Sends:
Fld 4 = ¥20000
• If transaction qualifies for Fld 41 = ¥20000
settlement:
Fld 49 = 392 •
Convert value in Fld 4 to
Fld 491 = 392
Fld 5 = US$200.00 settlement currency; use Fld 54A = AU$5000.00
to add Fld 5
Fld 9 = .01 • Add Fld 9
Fld 16 = 09/28 •
Add Fld 16 1
An 0230 message does not
Fld 50 = 840 • Add Fld 50 contain field 4 or field 49
•
Add Fld 54B (zero-filled) because it is an advice message.
Fld 54A = AU$5000.00
Fld 54B = zero-filled
• Convert value in Fld 54A
and subtract conversion
Fld 54A-converted = fee(s) for Fld 54A-
¥396000 converted
•
Add Fld 54A-converted

For this example, ¥100 = USD$1.00 and AU$1.25 = USD$1.00.

5-8 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 5: Multicurrency Support Multicurrency Field Flows

If the issuer does not provide field 54B, the acquirer receives it from VisaNet zero-filled
and does not receive field 54B-converted. See Figure 5-4 for a more detailed example of
all components of field 54. Account balance information contained in field 54 is optional.

Figure 5-4 Adjustment Transaction

Acquirer V.I.P. Issuer

0220 Advice SMS Processing 0220 Advice

Sends: • Convert value in Fld 4 to Receives:
billing currency and include
conversion charges and
Field 4 = ¥01000 fees; use to add Fld 6 Field 4 = ¥1000
Field 49 = 392 • Calculate and add Field 10 Field 49 - 392
Field 3 = 22xxxx • Add Field 51 Field 6 = AU$12.63
(credit adjustment) • Convert value in Field 4 to Field 51 = 036
settlement currency;
Field 5 = AU$12.50
• Add Field 9
Field 9 = .0125
• Add Field 16
Field 16 = 09/28
• Add Field 50
Field 50 = 036

0230 Response SMS Processing 0230 Response

Receives: If transaction qualifies for Sends:
settlement
No multicurrency fields1
• Add Field 5
Field 5 =US$10.00
• Add Field 9 1 An 0230 message does not
Field 9 = .01
• Add Field 16 contain field 4 or field 49
Field 16 = 09/28
because it is an advice message.
• Add Field 50
Field 50 = 840

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 5-9
Multicurrency Field Flows Chapter 5: Multicurrency Support

For this example, ¥100 = USD$1.00 and AU$1.25 = USD$1.00.

Currency conversion rates used for a back-office adjustment can be different from the
rates used for the original transaction. The rates used for an adjustment resulting from
a cash disbursement adjustment are the same as the rates used for the corresponding
cash disbursement.

5-10 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 5: Multicurrency Support Multicurrency Field Flows

Figure 5-5 Representment Transaction

Acquirer V.I.P. Issuer

0220 Advice SMS Processing 0220 Advice

Sends: • Convert value in Fld 4 to Receives:
billing currency and include
conversion charges
Field 4 = ¥01000 and fees; Field 4 = ¥20000
use to add Fld 6
Field 49 = 392 Field 49 - 392
• Calculate and add Field 10
Field 6 = AU$269.32
• Add Field 51
Field 51 = 036
• Convert value in Field 4 to
Field 5 = AU$266.66
settlement currency; use to
add Field 5 Field 9 = .01333
• Add Field 9 Field 16 = 10/27
• Add Field 16 Field 50 = 036
• Add Field 50

0230 Response SMS Processing 0230 Response

Receives: • Add Field 5 Sends:
• Add Field 9 No multicurrency fields1
Field 5 =US$190.48 • Add Field 16
1 An 0230 message does not
Field 9 = .0095238 • Add Field 50
contain field 4 or field 49
Field 16 = 10/27
because it is an advice message.
Field 50 = 840

For this example, ¥105 = USD$1.00 and AU$1.40 = USD$1.00.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 5-11
Multicurrency Field Flows Chapter 5: Multicurrency Support

This example illustrates that the currency conversion rates used for a representment can
differ from the rates used for the corresponding chargeback. (See the rates used in the
chargeback example in Figure 5-8.)

Figure 5-6 Balance Inquiry

Acquirer V.I.P. Issuer

0200 Request 0200 Request

Sends: SMS Processing: Receives:
Fld 3 = 3020xx No multicurrency Fld 49 = 392
Fld 49 = 392 processing

0210 Response 0210 Response

Receives: SMS Processing: Sends:

Fld 54A = •
Convert value in Fld 54A Fld 54A =
20 (checking) to transaction currency 20 (checking)
01 (total) for Fld 54A-converted 01 (total)
036 (AU $) 036 (AU $)
•
Calculate conversion
C (positive) C (positive)
fee(s) and subtract
AU$5000.00 AU$5000.00
from value for
Fld 54B = Fld 54A-converted Fld 54B =
20 (checking) 20 (checking)
•
Add Fld 54A-converted
02 (available) 02 (available)
036 (AU $) •
Convert value in Fld 54B 036 (AU $)
C (positive) to transaction currency C (positive)
AU$500.00 for Fld 54B-converted AU$500.00
Fld 54A-converted = • Calculate conversion
20 (checking) fee(s) and subtract
01 (total) from value for
392 (Japan ¥) Fld 54B-converted
C (positive) •
Add Fld 54B-converted
¥39600
Fld 54B-converted =
20 (checking)
02 (available)
392 (Japan ¥)
C (positive)
¥39600

For this example, ¥100 = USD$1.00 and AU$1.25 = USD$1.00.

Fields 54A, 54B, 54A-converted, and 54B-converted contain the following components:
(1) account type, (2) amount type, (3) currency code, (4) amount and sign, and (5) amount.

5-12 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 5: Multicurrency Support Multicurrency Field Flows

If the issuer does not provide field 54B in the response, the acquirer receives it from
VisaNet zero-filled and does not receive field 54B-converted.

Figure 5-7 Reversal Transaction

Acquirer V.I.P. Issuer

0400 Request or SMS Processing 0400 Request or

0420 Advice • Convert value in Field 4 to 0420 Advice
Sends: billing currency and include Receives:
conversion charges
Field 4 = ¥20000 Field 4 = ¥20000
and fees;
Field 49 = 392 use to add Field 6 Field 49 = 392
• Calculate and add Field 10 Field 6 = AU$252.50
• Add Field 51 Field 10 = .012625
For reversal of 02xx settled Field 51 = 036
transactions:
Field 5 = AU$250.00
• Convert value in Field 4 to
settlement currency; use to Field 9 = .0125
add Field 5 Field 16 = 09/28
• Add Field 9 Field 50 = 036
• Add Field 16
• Add Field 50

0410 or 0430 Response SMS Processing 0410 or 0432 Response

Receives: For reversal of 02xx settled Sends:
transactions:
Field 5 = US$200.00 Field 41 = 20000
• Add Field 5
Field 9 = .01 Field 491 = 392
• Add Field 9
Field 16 = 09/28
• Add Field 16
Field 50 = 840 1
• Add Field 50 An 0430 message does not
contain Field 4 or Field 49.

For this example, ¥100 = USD$1.00 and AU$1.25 = USD$1.00.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 5-13
Multicurrency Field Flows Chapter 5: Multicurrency Support

Under normal circumstances, the acquirer sends an 0420 request to the issuer. Because
pre-existing acquirers can also generate 0400 request messages, issuers respond with
0410 messages that include field 4 and field 49.

Figure 5-8 Chargeback and Chargeback Reversal Transaction

Acquirer V.I.P. Issuer

0422 Advice SMS Processing 0422 Advice

Receives: Convert value in Field 4 to Sends:
settlement currency; use to add
Field 4 = AU$252.50 Field 4 = AU$252.50
Field 5
Field 49 = 036 Field 49 = 036
• Add Field 9
Field 5 = US$194.23
• Add Field 16
Field 9 = .7692307
• Add Field 50
Field 16 = 10/15
Field 50 = 840

0432 Response SMS Processing 0432 Response

Sends: • Add Field 5 Receives:
No multicurrency fields • Add Field 9 Field 5 = US$252.50
• Add Field 16 Field 9 = 1.000
• Add Field 50 Field 16 = 10/15
Field 50 = 036

For this example, ¥100 = USD$1.00 and AU$1.30 = USD$1.00.

The issuer provides the chargeback amount in the cardholder billing currency as it
received it in field 6 of the original request or advice.

This example illustrates that the currency conversion rates for a chargeback can differ
from the rates used for the original cash disbursement. (See the rates used in the cash
disbursement transaction example in Figure 5-3).

5-14 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
 Stand-In, CVV, and CVV2 6
Processing
This chapter includes descriptions of:
• Stand-in processing.
• SMS advice file content and advice recovery procedures for acquirers and issuers.
• The Card Verification Value (CVV) Service and the Card Verification Value 2 (CVV2)
Service.

This chapter also includes a list of other risk services.

6.1 Stand-In Processing (STIP)

When an issuer is not available, SMS acts as a back-up processor and authorizes or
declines transactions on the issuer's behalf. This V.I.P. function is referred to as stand-in
processing, or STIP.

All issuers specify the STIP parameters that SMS is to use. Issuers must specify these
parameters even if they want to have SMS decline all transactions.

When an acquirer is not available to receive issuer-generated transactions such as

chargebacks, SMS acts as a back-up processor and accepts the transactions on the
acquirer's behalf.

STIP is available for Visa and Visa Electron transactions. It is available for most other card
types. Participation is optional and varies by region.
NOTE
STIP is not available for Mastercard transactions regardless of region.

6.1.1 Conditions Requiring Stand-In Processing

STIP processes financial requests (0200s), reversal requests (0400s), and reversal advices
(0420s) destined for an issuer under the following conditions:
• The line to the issuer is not available, or the V.I.P. System encounters an error condition.
• The issuer is signed off.
• The issuer is in Advice Recovery-only mode.
• The request is a reversal, the original transaction was approved by STIP, and the STIP
advice of the original has not been recovered by the issuer. The issuer responds with
response code 91 (destination unavailable). This response is an issuer option.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 6-1
Stand-In Processing (STIP) Chapter 6: Stand-In, CVV, and CVV2 Processing

NOTE
V.I.P. stores SMS advices online for 30 days. SMS issuers that want to retrieve their advices need to retrieve
them within this 30-day period.

For descriptions of additional STIP reversals, see “Reversal Processing” in this chapter.
• The issuer does not respond within a specified time limit. When the time limit for the
client to respond expires, the expiration triggers a time-out condition and SMS invokes
STIP.
• SMS signs off the issuer due to 10 consecutive time-outs.

6.1.2 Issuer STIP Options

Issuers can specify the following options for STIP:
• Setting transaction activity limits for card ranges and for individual cardholders, such
as the:
- Number of approved transactions for a particular account in one day (count)
- Total value of approved transactions for this account in one day (amount)
NOTE
Activity limits are often referred to as count and amount limits, or simply counts and amounts.

• Using positive account controls through the Exception File for accounts that have VIP
(Very Important Person) status.
• Using negative account controls through the Exception File.
• Using modulus-10 check digit verification.
• Requiring a valid card expiration date, always or only if the expiration date is present.
• Checking personal identification numbers (PINs).
• Establishing PIN-entry attempt limits (if PIN checking is specified).
• Using the CVV Service, the CVV2 Service, the Dynamic Card Verification Value (dCVV)
Service, and the Cardholder Authentication Verification Value (CAVV) Verification Service.
• Having STIP decline all transactions when the issuer is not available.

6.1.3 Acquirer STIP Options

V.I.P. provides SMS acquirers with stand-in processing for issuer-generated messages such
as chargebacks, fee collections and funds disbursements, and text messages. STIP occurs
when the acquirer has signed off, does not respond within a specified time limit, or is
otherwise not active. Acquirers use advice recovery to retrieve transactions processed
in STIP.

6.1.4 STIP Authorization Processing

This section explains how STIP processes financial transactions. (Reversals are covered
later in this chapter.)

STIP performs the following steps when processing financial transactions:

• Chip card processing for Visa Smart Debit/Smart Credit (VSDC) transactions that are
eligible for Online Card Authentication Method (Online CAM) verification.
• Expiration date editing.
• Retrieving BIN-level default STIP response codes.

6-2 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 6: Stand-In, CVV, and CVV2 Processing Stand-In Processing (STIP)

• Exception File checking.

• Activity checking.
• Ranking all response codes and Identifying the highest priority (most severe) response
code.
• Creating advices.
• If the transaction is a request, retrieving the default CVV response code.
STIP does not perform all tests for all transactions:
• STIP checks balance inquiries against the Exception File but does not test them for
activity.
• STIP only performs PIN checking for advices.
• STIP performs PIN checking only if specified by the issuer.
STIP approves financial requests unless it finds a negative condition. If the request passes
all tests, STIP responds with an approval and creates an advice for later recovery by the
issuer. STIP also updates the Activity File to reflect approvals made during the day.
NOTE
V.I.P. stores SMS advices online for 30 days. SMS issuers that want to retrieve their advices need to retrieve
them within this 30-day period.

If STIP finds a negative condition during testing, it assigns a decline response code to
the request. STIP returns this code in Field 39—Response Code of the response, unless
STIP finds a more serious decline condition in a subsequent test. If STIP assigns multiple
response codes to a transaction, STIP returns the code identifying the most serious
decline reason.

STIP rejects messages that contain consistency or syntax errors.

Issuers can optionally include Visa Advanced Authorization risk score threshholds as
part of their STIP processing parameters.

For balance inquiries and account transfers, STIP assumes that requests are to be declined
with response code 91 (destination unavailable). If, however, the account is listed in the
Exception File with a pick-up response code, STIP returns that code instead.

6.1.4.1 VSDC Chip Processing

STIP processes chip transactions when:
• The issuer is unavailable.
• The issuer chooses to have V.I.P. perform Online Card Authentication Method (Online
CAM) verification or issuer authentication on its behalf.
• The issuer has specified certain “route to issuer” conditions.
NOTE
STIP is not available for VSDC PIN Management transactions, but is available for transactions when the
Issuer Application Data (IAD) length exceeds specified limits.

When STIP performs Online CAM verification, it is authenticating that the issuer's card is
genuine, not counterfeit.
NOTE
If STIP performs Online CAM and CVV verification and the transaction passes Online CAM validation but fails
CVV verification, STIP does not decline the transaction. Online CAM validation takes precedence over CVV
verification.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 6-3
Stand-In Processing (STIP) Chapter 6: Stand-In, CVV, and CVV2 Processing

When STIP performs issuer authentication, it generates a response cryptogram for the
card to validate. This process ensures that the approval is coming from a valid issuer,
not from an imposter.
NOTE
The cryptogram used differs, depending on card type.

Issuers can set the following preferences separately for domestic and international chip
transactions (in which the chip magnetic-stripe is read, or in which no PIN is entered when
it is required and a PIN pad is present):
• Route to issuer (yes or no).
• STIP response (approve or decline).
For information about CVV, Integrated Chip Card card verification value (iCVV), and
Dynamic Card Verification Value (dCVV) processing, refer to “Card Verification Value (CVV)
Service” in this chapter.

6.1.4.2 Expiration Date Editing

SMS always checks expiration dates on transactions routed to STIP. If the issuer specifies
that STIP is to check expiration dates, STIP declines transactions that lack them.

Visa cards must contain standard data in Track 1 and in Track 2. If a card expiration date is
present in the request, the date must not be expired. Expiration dates cannot be more than
20 years from the date the card was issued. Unless issuer specifications direct otherwise,
when STIP discovers a missing or an expired date, STIP assigns response code 54 (expired
card or expiration date is missing) to the request. If the date is valid and there are no edit
failures for other reasons, STIP assigns response code 00 (approved) to the request.

Issuers must use a value representing a year that is not greater than 20 years from the issue
date or use the value 4912 in Field 35—Track 2 Data to designate a non-expiring card.

6.1.4.3 Retrieving BIN-Level Default STIP Response Codes

If a transaction is eligible for stand-in processing, STIP retrieves the default response
codes that may apply, depending on the transaction class.

6.1.4.4 Ranking Response Codes and Identifying Highest Priority Code

STIP ranks all response codes and uses the one with the highest priority. STIP compares
the response codes gathered and selects the most severe, or most serious, response code
and inserts it in Field 39—Response Code of the response message.

6.1.4.5 Exception File Checking

The Exception File contains account numbers that require special handling. Each Exception
File record consists of an account number and a purge date, and a response code,
cardholder spending limits, or both.

For a full description of the Exception File, refer to the Cardholder Database chapter in
V.I.P System Services, Volume 2.

Cash Disbursements
STIP checks cash disbursements against the Exception File to determine if a response code
or a cardholder spending limit is on file for the cardholder's account.

6-4 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 6: Stand-In, CVV, and CVV2 Processing Stand-In Processing (STIP)

• If the account-level activity limits are not specified, STIP uses activity limits specified at
the BIN level.
• If STIP finds a response code for the account, it assigns that code to the request.
The codes allowed in Exception File records for ATM are:
04 = Pick up (non-fraud).
07 = Pick up, special condition (fraud).
11 = Approval for VIP (Very Important Person).
NOTE
Response code 11 is never sent to the acquirer. STIP converts it to 00 (approval).

41 = Lost card; pick up (fraud).

43 = Stolen card; pick up (fraud).
• If STIP finds cardholder spending limits but no response code, STIP uses the limits on
file to check activity instead of the basic cardholder spending limits. STIP also checks
the transaction limit and daily limits.

Balance Inquiries
STIP checks balance inquiries against the Exception File to determine if a pick-up response
code is on file.
• If the account is not on file, STIP assigns response code 91 (destination unavailable).
• If the account is listed with a specific code, STIP assigns that code to the transaction.
STIP ignores records containing response code 11 (approval for VIP), activity limits,
or both, for balance inquiries.

For balance inquiry transactions that fail CVV or iCVV validation, STIP declines the
transaction with response code 05.

6.1.4.6 Activity Checking

This section describes the activity checking procedures STIP performs when it receives
a request.
NOTE
This section does not apply to balance inquiries.

SMS checks activity only if the issuer has specified a value other than zero for the issuer
BIN's activity count.

STIP checks cardholder activity using the contents of the Exception File and the following
issuer-specified activity limits:
• Transaction limits
• Daily limits
• Cardholder spending limits
The activity check determines whether or not approval of the request causes the card
usage to exceed these limits. If the activity is over the specified limits, STIP assigns
response code 61 (exceeds approval amount limit).

The activity check is based on activity accumulated daily in the Activity File, which contains
only STIP approvals.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 6-5
Stand-In Processing (STIP) Chapter 6: Stand-In, CVV, and CVV2 Processing

For a full description of the Activity File, refer to the Cardholder Database chapter in
V.I.P. System Services, Volume 2.

VisaNet resets the accumulated totals in the Activity File to zero every 24 hours so that
the file always reflects the current day's activity.

Standard Activity Checking

If activity checking is to be performed, STIP sets the indicator for “only cardholder total
activity check” if it finds that an exception record has a response code.

If STIP is to check the cardholder limit and the BIN limit, STIP performs processing
as follows:
1. If the sum of today's non-STIP activity count and STIP activity count plus one (for this
transaction) is greater than the issuer BIN maximum, STIP sets the activity check
response to response code 65 (exceeds withdrawal frequency limit).
2. If the above sum is not greater than the BIN maximum limit, STIP checks the
transaction amount against the transaction amount limit. If the transaction amount is
greater, STIP declines the transaction and sets the amount exceeded limit indicator.
3. STIP compares the sum of the transaction amount plus today's non-STIP activity
amount and STIP activity amount to the BIN maximum transaction amount. If the sum
is greater than the BIN maximum amount, STIP declines the transaction and sets the
amount exceeded limit indicator.
STIP compares the sum of the transaction amount plus today's non-STIP activity
amount and STIP activity amount to the BIN maximum transaction amount. If the sum
is greater than the BIN maximum amount, STIP declines the transaction and sets the
amount exceeded limit indicator.
If STIP has set the amount exceeded limit indicator and did not set the activity response
code to 65 during the processing steps above, STIP sets the activity response code to 61.

STIP performs the standard activity checking on all requests it receives for processing
unless the issuer has specified non-standard activity checking for particular account
numbers. The following subsection describes non-standard activity checking.

Non-Standard Activity Checking

STIP can perform non-standard activity checking on accounts that the issuer lists in the
Exception File as high-risk or as low-risk accounts. If STIP finds a response code listed in
the Exception File, it checks the limits in the Exception File instead of the standard activity
limits. Refer to “Exception File Checking” in this chapter for more information.

When STIP Does Not Check Activity

STIP does not perform activity checking in some cases because it is not needed to make
an authorization decision. STIP does not perform activity checking in the following cases:
• The request (for instance, a credit adjustment transaction) results in a credit to the
cardholder's account.
• STIP assigned a decline response code during editing, Exception File checking, or PIN
checking.

Excessive Activity
STIP responds with response code 65 (exceeds withdrawal frequency limit) if the sum of
the non-STIP activity (count and amount) and the STIP activity exceeds the issuer's limits.

STIP responds with response code 61 (exceeds approval amount limit) if:

6-6 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 6: Stand-In, CVV, and CVV2 Processing Stand-In Processing (STIP)

• The activity amount is exceeded but not the activity count.

• Activity amount and activity count limits are exceeded.

6.1.4.7 Identifying Highest Priority Response Code

When processing finishes, STIP selects the response code that represents the highest
priority and inserts it in field 39 of the response to the acquirer.

6.1.4.8 Creating an Advice

Under normal conditions, when STIP responds to a financial transaction, it creates an
advice (an 0220 for an 0200 request) for the issuer.

A STIP advice contains all of the data from the acquirer's request, except the PIN,
security-related control information, and track data.

In addition to the data from the acquirer's request, a STIP advice contains:
• The STIP response code (in Field 39—Response Code).
• The reason STIP processed the request (in Subfield 63.4—STIP/Switch Reason Code).
• Code 1 in the Advices-Created-By flag in the message header. (This code indicates that
STIP created the advice while standing in for the issuer.)
• Settlement flags in the message header of the advice. (STIP sets these flags as needed
to indicate the settlement impact.) For more information, see the Message Structure
and Header Field Specifications chapter of V.I.P. System SMS ATM Technical Specifications,
Volume 1 and Volume 2.
Advices remain on file until the issuer signs on to Advice Recovery mode using an 0800
network management message.
NOTE
SMS rejects all advice response messages that do not contain a response code of 00 in field 39 with Reject
Code 0087—Invalid Value or Reject Code 0590—Invalid Value (Not 00 or 55 When it Should Be).

6.1.4.9 Retrieving Default CVV Response Code for Request

If the issuer has specified the ALL RESPOND option in the system files, or if no error has
been detected during the SMS CVV validation process, STIP uses the following CVV
default response codes:
• If the CVV default response code is 00, STIP responds with response code 00 (approved).
• If the CVV default response code is 01, STIP responds with response code 01 (refer
to card issuer).
• If the CVV default response code is 04, STIP responds with response code 04 (pick
up card (No Fraud).
• If the CVV default response code is 05, STIP responds with response code 05 (do not
honor).

6.1.5 SMS Functions in Support of STIP

During transaction processing, SMS performs several functions to facilitate STIP's approval
or decline decision. If these SMS functions detect an error, they call STIP to resolve
them and determine the response code.

6.1.5.1 Account Number Editing

STIP edits the account number in Field 2—Primary Account Number for all requests.
STIP also performs check-digit verification and checks the expiration date when specified

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 6-7
Stand-In Processing (STIP) Chapter 6: Stand-In, CVV, and CVV2 Processing

by the client. STIP uses the date in Field 14—Date, Expiration or takes the date from the
magnetic stripe data in Field 35—Track 2 Data.

The values in the account number, date, and time limit fields must meet syntax and
consistency requirements. For instance, if a request contains an incorrectly formatted
expiration date or if the date is not present, STIP rejects the request.

Account Number
The account number must have a valid modulus-10 check digit (if specified by the issuer).

The account number must be all numerics, and the length must be valid for the range or
ranges of numbers serviced by the issuer.

If the check digit or the length is invalid, STIP assigns response code 14 (invalid card
number, no such number) as the decline response. STIP does not perform Exception File,
PIN, or activity checking once the account number is determined to be invalid.

6.1.5.2 Invalid Country Editing

SMS checks cards against its valid country table and its country exclusion table. STIP
responds with response code 62 if:
• The card is being used in a country not in the SMS valid country table.
• The card was issued in a country that is in the country exclusion table.

6.1.5.3 Cardholder Database Checking

If V.I.P. encounters an error when comparing the transaction information with the
corresponding cardholder record in the Cardholder Database, STIP responds with response
code 96 (system malfunction).

If the issuer has a positive PIN Verification Value (PVV) file and the card number is not
listed, STIP responds with response code 14 (invalid card number, no such number).

6.1.5.4 Currency Conversion and Invalid Amounts

STIP responds with response code 13 (invalid amount or currency conversion field
overflow) if:
• SMS encounters an overflow condition during currency conversion for Visa card
transactions (network ID 0002).
• Field 4 is missing and the request is not a balance inquiry.
• The amount in field 4 is the equivalent of USD$0.00.
If STIP encounters other error conditions during currency conversion, it returns response
code 96 (system malfunction).

6.1.5.5 Destination Not Available

STIP responds with response code 91 (destination unavailable) if:

6-8 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 6: Stand-In, CVV, and CVV2 Processing Stand-In Processing (STIP)

• The destination is not available (for instance, the line to the client is down, the client is
signed off or is in Advice Recovery-only mode, or the client has exceeded the response
time limit).
• The request is a returned message and all of the following conditions apply:
- There is no Inter-Task Table (ITT) entry for the transaction.
NOTE
The ITT retains a transaction's key field information until a response to that transaction by the issuer
or by STIP has been sent. The ITT matches requests and responses and identifies repeat or duplicate
requests by using these fields:
Field 32—Acquiring Institution Identification Code
Field 37—Retrieval Reference Number
Field 41—Card Acceptor Terminal Identification
Field 42—Card Acceptor Identification Code
Field 63.1—Network Identification Code

- The transaction is a chargeback, a representment, or an 0220 adjustment.

- The transaction is not an inter-VIC returned message.
• An issuer station cannot be found.

6.1.5.6 Issuer Not Found

STIP responds with response code 15 (no such issuer) if SMS cannot determine or is
unable to resolve the issuer BIN.

6.1.5.7 Invalid Transaction

STIP responds with response code 12 (invalid transaction) if:
• The request is for an account transfer for which the card range currency is not equal to
the transaction currency.
• The BIN currency code is not equal to the transaction currency code on an account
transfer.
• The request is an adjustment for a misdispense and there is no transaction history.

6.1.5.8 PIN Translation

If the acquirer key, V.I.P. key, or PIN block format is invalid, STIP returns response code 81
(cryptographic error found in PIN). This condition also triggers a key change if the acquirer
subscribes to the Dynamic Key Exchange (DKE) Service and SMS keeps the master key.

STIP also responds with response code 81 whenever the security control information is
submitted in field 53 and fails verification. STIP responds with response code 96 (system
malfunction) to other PIN translation errors.

STIP also returns response code 81 if the contents of field 53 fail verification.

6.1.5.9 PIN Verification

V.I.P. verifies PINs for PIN Verification Service (PVS) participants. STIP responds with
response code 86 (cannot verify PIN) if:
• The VSM encounters an error during the verification.
• The acquirer requests PVS processing and there is no PIN Verification Value (PVV) on file.
• V.I.P. encounters a PVS error other than invalid PIN, keys in error, or PIN block format
error.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 6-9
Stand-In Processing (STIP) Chapter 6: Stand-In, CVV, and CVV2 Processing

STIP responds with response code 55 (incorrect PIN or PIN missing) if the VSM returns
with no errors but was unable to verify the PIN. STIP also responds with response code 55
if the transaction requires a PIN but a PIN is not present in the message.
NOTE
V.I.P. forwards field 52 and field 53 or drops them from a request message depending on what the issuer
has chosen.
If the issuer has chosen to have both, V.I.P. and the issuer's processor perform verification, and when the issuer
is available to translate (decrypt) PINS, VisaNet forwards field 52 and field 53 to the issuer. When the issuer is
unavailable, VisaNet forwards the two PIN fields to STIP.
If the issuer has chosen to have V.I.P. perform PIN Verification and if PIN Verification is successful, V.I.P. drops
field 52 and field 53 from the request message.

STIP responds with response code 81 (cryptographic error found in PIN) if:
• The issuer option is set for PVV but the PVV is not found in Track 1 or Track 2.
• If the acquirer key or the V.I.P. key is invalid or if the PIN block format is invalid.
This condition also triggers a key change if the acquirer participates in the DKE Service
and SMS is the master.

Unsuccessful PIN-Entry Attempts

For PVS participants, STIP continues PIN processing after SMS decrypts and verifies the
PIN. If a PIN is invalid, STIP checks to determine if the limit for unsuccessful PIN-entry
attempts has been exceeded. STIP maintains a count of consecutive unsuccessful
PIN-entry attempts made on the current day for a given account number.

STIP performs processing based on the current unsuccessful PIN-entry attempt count,
as follows:
• If the PIN is valid, STIP clears the count to zero.
• If the PIN is invalid, STIP increases the count by one. STIP compares the updated count
to the limit. If the updated count now exceeds the limit, STIP updates the count and
assigns the interim response code 55 (incorrect PIN or PIN missing) to the request.
• STIP checks the SMS exception file for a negative code. If STIP does not find a negative
code, it declines the response with response code 55.
• STIP creates an advice for the issuer that contains the interim response code 55
to clarify the reason for the decline.
NOTE
PIN Verification Service (PVS) can also be used on a subscription basis for checking all PINs for an issuer,
in addition to the STIP checking.

For complete and definitive information about the use of PINs, refer to the Payment
Technology Standards Manual. For a full description of the PIN Verification Service, refer to
V.I.P. System Services, Volume 2.

Offline VSDC PIN-Try Limits Exceeded

STIP uses the issuer’s STIP parameters for online PIN processing when it receives a VSDC
request that indicates that an offline PIN was verified but the cardholder’s attempts
to enter it exceeded the issuer’s specified limit for online PIN-entry attempts. This
condition is indicated in the request with Field 131—Terminal Verification Results and in
Field 134.3—Card Verification Results. Only Full Data participating issuers receive these
two fields.

6-10 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 6: Stand-In, CVV, and CVV2 Processing Stand-In Processing (STIP)

6.1.5.10 9240 and 9242 FRS Messages

STIP responds with response code 06 (error) if a required field is missing in one of these
Fraud Reporting System (FRS) messages.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 6-11
Stand-In Processing (STIP) Chapter 6: Stand-In, CVV, and CVV2 Processing

6.1.6 Assigning a Response Code

After editing the transaction and checking the Exception File, PIN, and activity, STIP assigns
the response code to return in the response message.
• If only one code was assigned to a request, STIP returns that code in the response
message.
EXAMPLE
If STIP assigns response code 54 (expired card) or expiration date Is missing during the edit and finds no other
decline conditions in subsequent tests, STIP returns the same response code 54 in the response message.

• If STIP assigns response code 00 (approved) or response code 11 (approval) for VIP and
finds no decline or referral conditions, STIP returns response code 00 in the response
message. STIP never returns response code 11 in response messages to acquirers.
• If STIP assigns more than one decline or referral response code, STIP returns the most
severe decline or referral response code. The issuer receives the response code in an
advice when required. The Referral Reduction Service converts the acquirer referral
response code to a decline.
EXAMPLE
If STIP assigns response code 54 (expired card or Expiration Date Is Missing), response code 55(incorrect
PIN), and response code 04 (pick up card (Non-Fraud)) to the request, STIP puts response code 04 in the
response message because it is the most serious of the three.

The response code severity is ranked in the following order: 14, 43, 07, 41, 04, 05, 55, 61,
65, 54, 86, 91, 00, with 14 ranked as most severe.

“Field 39—Response Code” in V.I.P. System SMS ATM Technical Specifications, Volume 1,
lists response codes.

6.1.7 Updating the Activity File

When STIP approves a financial transaction, it updates the transaction totals in the
cardholder's activity record.
NOTE
V.I.P. does not allow network 0002 and network 0003 Interlink POS cancellation messages (Field 63.3—Message
Reason Code contains 2005) and rejects them.

For financial requests and reversals, STIP updates:

• The count and the amount totals for the approved request.
• The cardholder's grand totals.
Balance inquiries do not affect activity totals.

The accumulated activity totals increase or decrease, depending on the code in

Field 3—Processing Code in the request. Processing codes defined as having a debit
value increase the totals, while credit processing codes decrease the totals. In reversals,
debit processing codes decrease the totals, while credit processing codes increase
the totals.

For a description of Field 3—Processing Code, refer to V.I.P. System SMS ATM Technical
Specifications, Volume 1.

6-12 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 6: Stand-In, CVV, and CVV2 Processing Stand-In Processing (STIP)

Activity counts and amounts are never reduced to less than zero. If a credit adjustment
exceeds the activity totals, STIP resets the activity record to zero.

For a full description of the Activity File, refer to the Cardholder Database chapter of
V.I.P. System Services, Volume 2.

6.1.8 Reversal Processing

Reversals cannot be declined. When STIP receives a reversal, it always approves the
reversal and creates an advice for the issuer. STIP, however, edits the reversal for
validity. STIP checks the reversal for proper syntax and consistency, and searches for the
corresponding original transaction being reversed. If STIP finds the original transaction,
STIP updates the activity records, and the reversal has financial impact. If STIP does not
find the financial record, the reversal has no financial impact so STIP does not update the
activity records. The issuer may still receive response code 00 (approved).

SMS generates a reversal for the issuer if STIP cannot deliver an 0210 response to an
approved 0200 request to the acquirer. STIP also generates reversals to the issuer for
returned responses or for late responses to approved requests.

STIP responds with response code 79 (already reversed) if an acquirer sends a reversal
and the history record shows that a previous reversal was processed for the same
transaction. This response code value is only used by SMS. Issuers must not use this
value in response messages.

STIP responds with response code 80 (no financial impact) if an acquirer sends a reversal
and the history records show that the original request was declined. This response code
value has a different meaning in SMS than in BASE I. Issuers must not use this value for
the purpose as defined in BASE I.

STIP responds with response code 76 (unsolicited reversal) if there is no history for the
transaction in question and the reversal is inter-VIC, or if V.I.P. is in single-center mode.

6.1.8.1 Updating the Activity File

When STIP approves a reversal, it updates the cardholder's activity record if the reversal
has settlement impact. For instance, STIP decreases ATM counts and amounts for a
valid reversal of a financial transaction. STIP also decreases the cardholder's grand
totals accordingly.

When a reversal has a credit effect on the cardholder's account, activity counts and
amounts on file are never set to less than zero.

6.1.8.2 Creating an Advice

When STIP responds to a reversal, it creates an 0420 advice for the issuer to recover.
V.I.P. stores SMS advices online for 30 days. SMS issuers that want to retrieve their advices
need to retrieve them within this 30-day period.

The 0420 advice contains data from the undeliverable reversal and the STIP response.

The Advice-Created-By flag of the 0420 message header contains code 1, indicating that
STIP created the advice while standing in for the issuer. STIP also sets the settlement
flags in the message header of the advice as needed, to indicate the settlement impact.
In addition, the 0420 advice contains a reason code in Subfield 63.4—STIP/Switch Reason
Code.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 6-13
Advice File Chapter 6: Stand-In, CVV, and CVV2 Processing

For more information, see the Message Structure and Header Field Specifications chapter
of V.I.P. System SMS ATM Technical Specifications, Volume 1 and Volume 2.

6.1.9 Acquirer Stand-In Processing

STIP provides stand-in processing for an acquirer when the acquirer is unable to
receive issuer-generated messages including chargebacks, fee collections and funds
disbursements, and text messages. Stand-in processing occurs under the following
conditions:
• The line to the acquirer is not active.
• The acquirer is signed off.
• The acquirer does not respond within a specified time limit.
SMS accepts the transaction on the acquirer's behalf and stores the transaction for the
acquirer to receive through the advice recovery process. The advice contains information
from the original issuer-generated request and includes Field 63.4—STIP/Switch Reason
Code.

Table 6-1 lists the advices that acquirers can receive.

Table 6-1 Acquirer Advices

Issuer-Generated Request STIP Advice to Acquirer

Chargeback (0422) Chargeback (0422)
Chargeback Reversal (0422) Chargeback Reversal (0422)
Text Message (0600) Text Message Advice (0620)
Fee Collection or Funds Disbursement (0422) Fee Collection or Funds Disbursement (0422)

6.2 Advice File

Each VIC maintains an Advice File containing records of STIP responses. Each record
includes information from the original request, the STIP response, and the reason why
STIP processed the request.

6.2.1 File Content

The Advice File can contain:
• 0420 reversal advices.
• 0120 and 0322 advices of Exception File additions and changes processed by VisaNet
for the Automatic Cardholder Database Update (Auto-CDB) Service.
• 0220 financial transaction advices, STIP advices, and BASE II fee transaction advices.
• 0480 chargeback status advices.
• 0520 reconciliation advices.
• 0620 administrative advices.
• 9620 fraud notification advices.
Refer to V.I.P. System Services, Volume 2, for a full description of the SMS Advice Retrieval
Service.

6-14 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 6: Stand-In, CVV, and CVV2 Processing Advice File

6.2.2 Unique Fields

Advices contain specific fields from the original request and response messages. Refer to
V.I.P. System SMS ATM Technical Specifications, Volume 1 and Volume 2, for details about
the fields contained in advice messages.

6.2.3 Maintenance and Update

Advice records are kept on file at the VIC for 30 days. V.I.P. stores SMS advices online for
30 days. SMS issuers that want to retrieve their advices need to retrieve them within this
30-day period. An issuer processing center recovers its advice records online through SMS.

6.2.4 Purging Records

SMS purges records in the SMS advice file after they have been recovered or when they
have not been recovered within 30 days.

6.2.5 Recovering Advices

An issuer or an acquirer controls advice recovery by changing its network status
maintained by SMS. (For a detailed description of SMS advice retrieval, refer to V.I.P. System
Services, Volume 2.)

To start and to stop the recovery of advices from SMS, acquirers and issuers use 0800
messages.

Table 6-2 shows the recommended values in the 0800 messages to sign on to and off of
Advice Recovery mode.

Table 6-2 Signing On and Off Advice Recovery Status

Field 70 Field 70
Station Type (Sign On) (Sign Off)
Common interface link: V.I.P. 078 079
message format

A station can be in Normal mode, in Advice Recovery mode, or in both modes concurrently.

Normal Mode—If the station is signed on to Normal mode, it can receive and can send
real-time messages but cannot receive advices from SMS.

Advice Recovery-Mode—If the station is signed on to Advice Recovery mode,

SMS sends advices as it stores them. The station cannot initiate messages other than the
acknowledgment of advices or sign-on messages.

Normal and Advice Recovery Mode—If the station is signed on to Normal mode and
Advice Recovery mode, it can send and can receive real-time messages and can receive
stored advices.

6.2.5.1 Timing of Recovery Status

Other than the system-induced advice recovery, there are no system requirements that
dictate when or how often clients should recover advices. An acquirer or an issuer can
recover advices throughout the day or only during certain periods as it sees fit.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 6-15
Advice File Chapter 6: Stand-In, CVV, and CVV2 Processing

When an issuer designs its system, however, it should consider the impact of STIP
authorization on advice recovery processing. STIP advices reflect authorization decisions
that can affect the available funds in a cardholder's account. If the issuer restricts advice
recovery only to certain periods, it may find that account balances are insufficient to cover
the total value of issuer-approved and STIP-approved transactions.

Also, issuers and acquirers should recover advices after a downtime condition, because
advices from SMS can affect settlement accumulators as well as issuers' cardholder
account balances.
NOTE
V.I.P. stores SMS advices online for 30 days. SMS issuers that want to retrieve their advices need to retrieve
them within this 30-day period.

6.2.5.2 Advice Recovery Flows

SMS keeps the following categories of advices until they are recovered by the issuer
or by the acquirer:
• STIP processing advices
• SMS reversal advices
• Funds transfer totals messages
• BASE II transaction advices
As previously stated, acquirers and issuers use 0800 messages to start and to stop advice
recovery from SMS.

Figure 6-1 illustrates the process flow of advice recovery by an issuer. The flow for the
process used by an acquirer is comparable.

> To sign on to Advice Recovery mode:

1. To initiate advice recovery, the issuer sends an 0800 request containing network
management iInformation code 078.
2. SMS replies with an 0810 response.
> To recover the advices:
1. SMS sends the highest priority advice on file.
2. The issuer replies with the acknowledgment.
SMS continues to send advices, one at a time, in order of priority. If the issuer does not
acknowledge an advice, SMS resends the advice until it receives the acknowledgment.

> To stop advice recovery:

1. To stop advice recovery, the issuer sends an 0800 message containing network
management information code 079.
2. SMS replies with an 0810 response.
Figure 6-1 illustrates the message flow for advice recovery.

6-16 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 6: Stand-In, CVV, and CVV2 Processing Advice File

IMPORTANT
The client should remain signed on during this process.

Figure 6-1 Advice Recovery Process Flow

Acquirer Issuer SMS

0800 Sign On to Recovery

Network Management
Information Code = 078

0810 Response

Network Management
Information Code = 078

0x2x Advice 1

0x3x Acknowledgment

0x2x Advice 2

0x3x Acknowledgment

0x2x Advice 3

0x3x Acknowledgment

0800 Recovery Sign Off

Network Management
Information Code = 079

0810 Response

Network Management
Information Code = 079

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 6-17
Card Verification Value (CVV) Service Chapter 6: Stand-In, CVV, and CVV2 Processing

6.2.5.3 Advice Flags in the Message Header

To provide additional information, Field 9—Message Status Flags in the message header
contains three bits that are used as advice-related flags. SMS sets flags, and the issuer or
the acquirer can examine them during incoming message processing.

For more information, see the Message Structure and Header Field Specifications chapter
of V.I.P. System SMS ATM Technical Specifications, Volume 1 and Volume 2.

6.3 Card Verification Value (CVV) Service

The Card Verification Value (CVV) Service is a POS and ATM risk control service that
protects issuers and acquirers from fraud losses associated with counterfeit Visa cards.
The CVV is a unique value calculated from data encoded on the magnetic stripe using the
Data Encryption Standard (DES) algorithm. The Integrated Chip Card card verification value
(iCVV) is a unique value calculated from data encoded on the chip image using the DES
algorithm. The Dynamic Card Verification Value (dCVV) is a unique value calculated from
the data encoded on the chip in a contactless transaction.
NOTE
The CVV Service refers to the Visa verification service available through the VisaNet Integrated Payment (V.I.P.)
System. The CVV Service processes CVVs and iCVVs.

Participation in the CVV Service is mandatory for issuers of all Visa card products.
Participation is optional for Plus issuers. Using iCVVs is optional for chip card issuers.

Acquirers of all Visa card products must provide complete, unaltered magnetic stripe
data (from the magnetic stripe or from the chip) in 0100 authorization messages and in
0200 financial messages.

The CVV Service allows issuers to detect invalid cards by checking the content on a
card's magnetic stripe or its chip image.
• The CVV resides on the magnetic stripe on the back of the card.
• Visa Smart Debit/Smart Credit (VSDC) chip cards have a magnetic stripe and a chip,
which contains an image of the magnetic stripe data. VSDC cards can contain the same
CVV values on its magnetic stripe and on its magnetic stripe image (MSI) on the chip.
At the issuer's option, the value of the CVV (on Track 2 of the magnetic stripe) and that
in the chip image's CVV can be different. In this case, the MSI contains an iCVV.
The contents on the magnetic stripe and in the chip are identical, unless the chip contains
an iCVV.

6-18 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 6: Stand-In, CVV, and CVV2 Processing Cardholder Authentication Verification Value
(CAVV) Verification

IMPORTANT
Having one verification value for the magnetic stripe (CVV) and a different one for the chip image (iCVV)
causes CVV validation to fail if chip information has been used to create a fraudulent magnetic stripe.

For more information about this service, refer to V.I.P. System Services, Volume 2.

6.4 Card Verification Value 2 (CVV2) Service

The Card Verification Value 2 (CVV2) Service is a card verification tool designed to reduce
fraud losses on transactions when the card is present and when the card is not present.
The service confirms that a genuine Visa card is used during the transaction.

Although a CVV2 value is never passed in ATM transactions, issuers of ATM cards
(including Plus cards) can optionally use CVV2s for purposes of card activation, address
changes, voice response unit (VRU) cardholder validation, and other bank customer service
options to ensure that the cardholder has the genuine card in hand.

For more information about this service, refer to V.I.P. System Services, Volume 2.

6.5 Cardholder Authentication Verification Value (CAVV)

Verification
The Cardholder Authentication Verification Value (CAVV) Verification Service provides
the functionality to verify that the Cardholder Authentication Verification Value (CAVV)
submitted by an acquirer in a Verified by Visa (3-D Secure) authorization message
matches the CAVV generated by VisaNet or by an issuer's Access Control Server (ACS)
during authentication.

The CAVV is a cryptographic value generated by the issuer and sent to the merchant
during the authentication process in a Verified by Visa transaction.

The verification process involves two phases:

1. Verified by Visa
2. CAVV Verification Service
During the Verified by Visa phase, the issuer or V.I.P. electronically identifies the cardholder
and generates a CAVV that is associated with the purchase or financial transaction.

The CAVV Verification Service begins when the acquirer submits the authorization or the
full financial message and includes the CAVV that was generated during the Verified
by Visa phase in the request. When the CAVV is present in the transaction, the issuer
or V.I.P. verifies that the CAVV in the message matches the CAVV generated during the
Verified by Visa phase. If the CAVV is verified, the transaction is protected from certain
chargebacks should disputes arise later.

When the validation is completed, the issuer or V.I.P. populates the results in the CAVV
Results Code field depending on which entity performed the validation. The value in this
field indicates the outcome of the validation, which entity performed the validation,
and the classification of the transaction (Authentication, Attempt, or non-secure). Reject
Code 0193 in the CAVV results code field indicates that the CAVV is invalid.

To validate the CAVV, the issuer or V.I.P. uses Data Encryption Standard (DES) keys and
other CAVV parameters to calculate the CAVV and compare it to the CAVV generated

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 6-19
Cardholder Authentication Verification Value Chapter 6: Stand-In, CVV, and CVV2 Processing
(CAVV) Verification

by the ACS. Issuers that choose to have Visa perform verification on their behalf must
provide Visa with their DES keys.

Visa offers two CAVV Verification Service processing options to issuers that participate in
Verified by Visa: Authentication or Attempt.

Authentication—With this option, the issuer is a full participant in the service and has
cardholders enrolled in Verified by Visa. Transactions are classified as Authentication
transactions when the acquirer, the issuer, and the cardholder all participate in Verified by
Visa.

Attempt—With this option, the issuer or V.I.P. generates a CAVV for attempted
transactions. Transactions submitted by a participating acquirer are classified as Attempts
when the issuer or cardholder does not participate in Verified by Visa. Liability shifts for
these types of transactions. This option is mandatory in some regions.

Visa encourages issuers to participate in both.

Both allow issuers to select a predefined process by which their transactions are to be
processed in Normal mode and in Stand-In Processing (STIP) mode:

Standard Issuer CAVV Service/Standard Decline/Failure Option—With this option,

V.I.P. performs all validations on the issuer's behalf, declines transactions when the CAVV
validation fails, and forwards the status results of transactions that were not declined
to the issuer.

All CAVV Verification Results to the Issuer Option—With this option, V.I.P. performs
all validations on the issuer's behalf and forwards all status results of transactions to
the issuer.

Issuer Supports Own CAVV Verification Option—With this option, VisaNet forwards the
transactions to the issuer to perform validation. The issuer returns the status results in
the response messages.

If issuers participating in the CAVV Verification Service have VisaNet perform CAVV
validation, V.I.P. performs the verification before acting upon issuer availability. The Visa
Security Module (VSM) uses authentication data elements in Field 126.9—CAVV Data and
Field 126.8—Transaction ID (XID) (or just field 126.9 if Field 126.9, usage 3—3-D Secure
CAVV, Revised Format is being used) along with issuer-supplied keys. (Authentication and
Attempt transaction keys may be the same.)
NOTE
Field 126.9 is an optional field for quasi–cash 0100 transactions.

Depending on issuer option selections for CAVV authentication transactions, V.I.P.:

• Performs all CAVV validation on the issuer's behalf, declines transactions when CAVV
validation fails, and forwards status results on transactions that were not declined to
the issuer.
• Validates the CAVV using issuer-supplied keys and passes all results to the issuer
regardless of the outcome.
• Forwards the transaction to the issuer without validating the CAVV.
Depending on issuer option selections for CAVV Attempt transactions, V.I.P.:

6-20 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 6: Stand-In, CVV, and CVV2 Processing Cardholder Authentication Verification Value
(CAVV) Verification

• Validates the CAVV using issuer-supplied keys and passes the CAVV result for
non-declined transactions to the issuer in the request message.
• Validates the CAVV using issuer-supplied keys and passes all results to the issuer
regardless of the outcome.
• Forwards the transaction to the issuer without validating the CAVV.
For issuers that validate CAVVs, V.I.P. checks the code in Field 44.13—CAVV Results Code.
If the code is 0, which indicates that the CAVV authentication results are invalid, V.I.P.
performs one of the following checks:
• If V.I.P. has the CAVV keys, and the CAVV results code validated by V.I.P. is not 0
(indicating that the first three positions of field 126.9 are valid), V.I.P. replaces the 0
value in field 44.13 with a valid CAVV results code and forwards the response message
to the acquirer.
• If V.I.P. does not have the CAVV keys and V.I.P. determines that the first three positions
of field 126.9 do contain valid values, V.I.P. replaces the 0 value in field 44.13 with C
(CAVV was not validated—Attempt) or D (CAVV was not validated—Authentication) and
forwards the response message to the acquirer.
• If V.I.P. has the CAVV keys, and the CAVV results code validated by V.I.P. is 0 (indicating
the first three positions of field 126.9 are not valid), V.I.P. forwards results code 0 in the
response message to the acquirer.
CAVV transaction processing rules depend on transaction characteristics and on
issuer-specified STIP processing parameters. If STIP processes a CAVV request and the
validation fails, the default response code is 05 (do not honor).

Depending on the region, VisaNet assesses interchange reimbursement fees based on

the CAVV Verification Service classification of the electronic commerce (e-commerce)
transaction.

V.I.P. accepts Visa authorization and full financial requests submitted with a CAVV and a
CVV2. When V.I.P. receives a request containing a CAVV and a CVV2, the CAVV validation
result takes precedence over the other risk control's verification result. This priority
processing also applies to issuer-unavailable transactions sent to STIP: if the CAVV passes
but the CVV2 fails, STIP does not decline the transaction because of the CVV2 failure.

V.I.P. accepts Visa full financial requests submitted with a CAVV and a CVV2. When V.I.P.
receives a request containing a CAVV and a CVV2, the CAVV validation result takes
precedence over the other risk control's verification result. This priority processing also
applies to issuer-unavailable transactions sent to STIP: if the CAVV passes but the CVV2
fails, STIP does not decline the transaction because of the CVV2 failure.

When a CAVV and a CVV2 are present, V.I.P. validates the CAVV first:
• If the CAVV validation is successful, V.I.P. verifies the CVV2, and forwards both results
to the issuer and to the acquirer in the response. (The CVV2 result is contained in
field 44.10; the CAVV result is contained in field 44.13).
• If the CAVV validation fails, CAVV Verification Service rules apply:
- If the issuer specifies that V.I.P. is to decline all transactions that fail the CAVV check,
V.I.P. declines the transaction without verifying the CVV2.
- If the issuer specifies that V.I.P. is to forward all results to the issuer regardless of
the outcome, V.I.P. validates the CVV2 and includes both field results in the request
to the issuer.
If STIP validates the CAVV in a request that includes a CVV2 value:

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 6-21
Other Risk Services Chapter 6: Stand-In, CVV, and CVV2 Processing

• If the CAVV value is valid, STIP validates the CVV2 value and follows the issuer’s CVV2
STIP parameter rules.
- If the CAVV value is valid but the CVV2 value fails verification, the CAVV result takes
precedence and STIP follows the CAVV-related processing specifications.
• If the CAVV validation fails, STIP declines the transaction without validating the CVV2.
If STIP cannot complete the CAVV validation process, STIP still uses the issuer-specified
CAVV processing parameters:
• If STIP is to continue processing, it verifies the CVV2 according to the related processing
parameters.
• If STIP is to decline the transaction if CAVV validation fails, STIP validates the CVV2
and sends a decline response.
NOTE
See Cardholder Authentication Verification Value (CAVV) Verification Service in V.I.P. System Services, Volume 2.

The CAVV Verification Service supports magnetic stripe Visa cards and Visa Smart
Debit/Smart Credit (VSDC) cards.

See Visa Secure Electronic Commerce (VSEC) With Verified by Visa (3-D Secure) in
V.I.P. System Services, Volume 1. See also Cardholder Authentication Verification Value
(CAVV) Service in V.I.P. System Services, Volume 2.

6.6 Other Risk Services

The following fraud tools are available to SMS clients:
• Automatic Cardholder Database Update (Auto-CDB) Service.
• Fraud Reporting System (FRS).
These services are briefly summarized in Chapter 1, Single Message System Overview.
For more information, refer to V.I.P. System Services, Volume 1 and Volume 2.

6-22 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
 Routing 7
Routing refers to sending messages between VisaNet and acquirer and issuer processing
centers. Routing also refers to sending a message to V.I.P. stand-in processing (STIP) for
authorizing a transaction on an issuer's behalf.

This chapter describes:

• How SMS determines transaction routing from one client to another.
• The routing services available to acquirers and to issuers.

7.1 Transaction Routing

To route messages, SMS uses client-supplied information stored in the SMS system tables
along with information in the message header, message type identifier, and data fields.
SMS compares the message information to the applicable BIN (a range of card numbers
for a specific card program, such as Visa Classic) and processing center information stored
in the system databases. This information includes:
• Network ID.
• Account number.
• Card type.
• Source address.
• Destination address.
Table 7-1 lists each SMS ATM transaction and on which field the routing decision is based.

Table 7-1 SMS Transaction Routing

Transaction Message Type Routing Decision Based on...

Cash Disbursement 0200 The ABA number in Field 125—Supporting
Information, and the issuer ID contained in
Reversal 0420
Field 100—Receiving Institution Identification Code.
Adjustment, Representment 0220
Chargeback, Chargeback Reversal, 0422 The acquirer ID contained in Field 32—Acquiring
Issuer-Initiated Fee Collection/Funds Institution Identification Code.
Disbursement
Acquirer-Initiated Fee Collection/Funds 0220 The issuer ID contained in Field 100—Receiving
Disbursement1 Institution Identification Code or in Field 2—Primary
Account Number. (Field 2 takes priority over field 100
if both are provided.)
Text Message 0600 The client identified in Field 100—Receiving
Institution Identification Code.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 7-1
Routing Options, Tables, and Services Chapter 7: Routing

Table 7-1 SMS Transaction Routing (continued)

Transaction Message Type Routing Decision Based on...

Fraud Notification 9620 The issuer identified in Field 100—Receiving
Institution Identification Code.
1. Plus issuers can receive Visa-generated 0220 funds disbursement messages that credit Plus ATM Format Conversion issuers with the fee for
BASE II-acquired ATM transactions that fail CPS/ATM edit criteria.

For details concerning the use of these messages with the routing services, refer to the
individual routing service descriptions in V.I.P. System Services, Volume 1.

7.2 Routing Options, Tables, and Services

Issuers and acquirers select the routing options they prefer. This section discusses the
relationship between SMS ATM products and the following items:
• Routing tables
• ATM/POS Split Routing Service
• PIN/No-PIN Split Routing Service
• Priority Routing Service
Visa also offers the following routing service to international SMS ATM acquirers. Refer to
V.I.P. System Services, Volume 1, for a complete service description.

Gateway Services—VisaNet has connections, or gateways, to various other systems and

networks. Gateway Services enable acquirers to obtain authorizations for non-Visa-brand
transactions using the same connections they use for Visa transactions.

7.2.1 Routing Options

This subsection identifies the routing options that apply to SMS ATM. It also indicates
issuer and acquirer applicability.

7.2.1.1 Visa/Plus ATM Routing Options

For Visa and Plus ATM clients, the routing services provided by Visa are optional—but not
the routing tables, which are required. Visa and Plus acquirers are required to use the Visa
and Plus tables or use the Combined Visa/Plus Routing Table. Acquirers can contact their
Visa representatives to make arrangements for receiving the tables.

The routing tables and the Priority Routing Service are for acquirers; the PIN/No-PIN
Split Routing Service is for issuers. Acquirers and issuers can use the ATM/POS Split
Routing Service. However, acquirers can only select the ATM/POS Split Routing option
or the Alternate Routing option; acquirers cannot select the ATM/POS Account-Type
Split Routing option.

Table 7-2 lists the routing service options for ATM.

Table 7-2 ATM Routing Table and Service Options

Routing Tables and

Services Acquirer Issuer
Routing Tables Required n/a
ATM/POS Split Routing Service Optional Optional

7-2 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 7: Routing Routing Options, Tables, and Services

Table 7-2 ATM Routing Table and Service Options (continued)

Routing Tables and

Services Acquirer Issuer
PIN/No-PIN Split Routing n/a Optional
Service
Priority Routing Service Optional n/a

Visa ATM acquirers can use the Visa-supplied account range routing tables and must
specify, in Field 63.1—Network ID:
• The preferred card program in which they want to participate (for instance,
Network ID 0002 = Visa, 0003 = Interlink).
• 0000 if they want to participate in the Priority Routing Service. Before participating in
Priority Routing, clients must contact their Visa representatives.

7.2.2 Routing Tables

This subsection describes the following tables:
• Visa Routing File
• Plus BIN Table
• Combined Visa/Plus Routing Table
Routing tables are also referred to as BIN tables or as account range tables.

7.2.2.1 ATM Routing Tables

Acquirers can use:
• Visa Routing Table (which can also be used for routing Visa POS transactions)
• Plus BIN Table
• Combined Visa/Plus Routing Table
The Visa, Plus, and Combined Visa/Plus routing tables are batch data files that list all ATM
card prefixes, prefix lengths, and account number lengths. The tables help Visa and Plus
acquirers determine which account ranges belong to ATM issuers and help them make
authorization routing decisions.

Acquirers use routing tables to determine which transactions should be sent to VisaNet
for processing. Entries in the Visa, Plus, and Combined Visa/Plus routing tables consist of
whatever number of digits are required to identify a card range or a card portfolio.
EXAMPLE
A routing table entry may be simply a BIN (for instance, 412345) or a longer number for a Plus proprietary
card program (for instance, 504667214). Entries can be up to 12 digits. The Visa, Plus, and Combined
Visa/Plus routing tables each include the issuer institution country code.

VisaNet delivers the tables as follows:

• Visa Routing File: weekly on Tuesday
• Plus BIN Table: weekly on Thursday
• Combined Visa/Plus Routing Table: weekly on Friday
Acquirers using the routing tables must install them as follows:

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 7-3
Routing Options, Tables, and Services Chapter 7: Routing

• Visa Routing File: within six business days of receipt from VisaNet
• Plus BIN Table: within three business days of receipt from VisaNet
• Combined Visa/Plus Routing Table: within three business days of receipt from VisaNet
Each transmission is a full file replacement. The acquirer must modify the BIN table
between regularly scheduled updates if VisaNet identifies needed changes.

Acquirers receive the Visa, Plus, and Combined Visa/Plus routing tables through the file
delivery options identified in Chapter 9, Client-to-Visa Connection Options.

Refer to V.I.P. System SMS ATM Technical Specifications, Volume 1 and Volume 2, for more
information about routing table files.

7.2.3 Routing Services

This section describes optional routing services referenced in this chapter. For complete
service descriptions of all available routing services, refer to V.I.P. System Services, Volume 1.

7.2.3.1 Priority Routing

Acquirers that process two or more card products using SMS can use the Priority Routing
Service. The service enables SMS to determine which network and card program rules to
apply to message routing decisions for the following SMS products and message types:

SMS POS—Original authorizations, financial messages, and their reversals, and balance
inquiry requests

ATM—Cash disbursements, cash disbursement misdispense adjustments, reversals,

and balance inquiry requests

To initiate the Priority Routing Service, acquirers specify network ID 0000 in

Field 63.1—Network Identification Code.

Upon receipt of the request, SMS compares the networks of the acquirer and the issuer,
identifies a common network, and routes the message accordingly. If SMS detects more
than one common network, it selects the network based on the merchant's sharing group
order and available networks as defined in the issuer-supplied BIN file.

SMS assigns the network ID and forwards the request to the issuer with only those fields
that pertain to the network's programming rules.

SMS includes the assigned network ID in the response to the acquirer.

NOTE
If an acquirer wants a transaction to be processed through a particular network, the acquirer should use the
specific network ID; for instance, network ID 0002 = Visa, 0003 = Interlink, 0004 = Plus.

For a complete description of the Priority Routing Service, refer to V.I.P. System Services,
Volume 1.

7.2.3.2 Split Routing

Visa offers two optional routing services that allow issuers to separate types of transactions
and to route these transactions to two or more issuer processing centers.

ATM/POS Split Routing Service—This service is available to SMS clients that process
Visa, Visa Electron, and Plus transactions. It allows acquirers and issuers to separate types

7-4 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 7: Routing Routing Options, Tables, and Services

of transactions and to accept or to route these transactions to or from two or more

processing endpoints. The service offers the following options:
• The ATM/POS Split Routing option provides SMS acquirers and issuers that process Visa,
Visa Electron, and Plus transactions the ability to use separate processing centers for
ATM transactions and for POS transactions.
• The ATM/POS Account-Type Split Routing option enables V.I.P. to route ATM and POS
transactions by BASE I or SMS account type. (The capability to route a POS transaction
is currently available only in the Asia-Pacific [AP] region.) BASE I and SMS issuers can
specify that VisaNet route ATM transactions based on the account the cardholder selects
when using a multipurpose card at an ATM. BASE I and SMS issuers in the AP region
can specify that VisaNet route POS transactions based on the account the cardholder
selects when using a multipurpose card at the POS. Issuers can specify up to three
endpoints: one for deposit accounts, one for credit accounts, and one for universal and
non-specified accounts.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 7-5
Routing Options, Tables, and Services Chapter 7: Routing

• The Alternate Routing option allows acquirers and issuers to designate one or two
alternate processing centers to handle exceptions and other back-office transactions. The
alternate processing center may be connected to SMS or to Visa Resolve Online (VROL).
This option allows SMS issuers to receive back-office items from acquirers connected to
BASE I and BASE II or to SMS.
Alternate routing can apply to:
- Clients using third-party processors for back-office items at alternate sites.
- Clients using regional centers that want to consolidate back-office processing by
product, rather than by region.
- Issuers attached to SMS and BASE II.
- Issuers using separate systems for ATM and POS transaction processing.
Service participants can specify that POS exception transactions, fee-related transactions,
back-office adjustments, and administrative messages be routed to distinct processing
centers, and ATM exception transactions, fee-related transactions, back-office
adjustments, and administrative messages be routed to other distinct processing centers.
They can also route ATM and POS transactions to specific processing centers.
IMPORTANT
If participants use two alternate processing centers, one processing center must be designated for ATM
transactions and the other designated for POS transactions.

The Alternate Routing option also allows issuers that operate as alternate processors to
update and to access Exception File or PIN Verification File account records on behalf of
the primary issuer.
VisaNet settles transactions routed to an alternate destination according to the
settlement attributes specified for the original issuer or acquirer unless the endpoint
specifies alternate settlement.
Issuers can use these routing options individually or in combination.

PIN/No-PIN Split Routing Service—This optional service is available to SMS issuers

that process Visa and Visa Electron transactions. The PIN/No-PIN Split Routing Service
allows issuers to separate transactions requiring PIN verification from those that do not
and to route these transactions to a separate processing center. The service offers the
following options:
• The PIN/No-PIN Split Routing option for separating PIN-based transactions from
transactions not requiring a PIN.
• The POS PIN Routing option for routing all POS financial transactions with PINs to SMS
and routing all other transactions to the BASE I System.
Issuers can use these split routing options individually only; they cannot be combined.

Routing Option for Cash Disbursement Issuer Credits—Issuers can choose where
VisaNet is to route ATM cash disbursement issuer credits containing message reason
code 5310 (which identifies VisaNet-generated adjustment transactions). They can
receive ATM fee adjustments on a different system from that on which they receive POS
adjustments. Clients can contact their Visa representatives about this routing option for
cash disbursement issuer credits.

7-6 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
 Settlement and Reconciliation 8
The SMS settlement and reconciliation process is described in the following sections:
• Settlement Overview
• VisaNet Settlement Service (VSS)

8.1 Settlement Overview

The settlement process consists of various tasks that VisaNet performs so that funds can
be transferred. VisaNet performs settlement tasks during and after transaction processing
(clearing), the process that delivers transaction data to participants.

The settlement process includes the following tasks performed by VisaNet:

• Accumulating transaction counts and amounts during transaction processing.
• Calculating a net amount for the settlement day after transaction processing.
• Reporting the net amount to a funds-transfer agent that manages the actual debiting
and crediting to participants' settlement accounts.
When SMS processes transactions, it delivers them for account posting in real time using
02xx and 04xx messages. Thus, settlement refers to accumulating these transaction
counts and amounts and determining the net amount to be transferred to and from the
participant's settlement account.

8.1.1 Transactions Qualifying for Settlement

VisaNet settles all SMS financial transactions. A transaction qualifies for settlement if it
meets the following criteria:
• The account number must be within account ranges belonging to an SMS issuer set
up for SMS participation.
• The transaction must be one of the following types of financial transactions:
- Cash disbursements
- Reversals of cash disbursements
- Chargebacks
- Representments
- Adjustments
VisaNet does not include the values of the following transactions in settlement totals;
however, processing charges apply and are billed at month end.
• Balance inquiries
• Account transfers
• Declined financial transactions

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 8-1
Settlement Overview Chapter 8: Settlement and Reconciliation

VisaNet Settlement Service (VSS) reconciliation reports include daily counts for these
transactions.

8.1.2 Settlement Day

For V.I.P. online processing, VisaNet performs settlement accumulation and reporting
daily; however, funds transfer occurs only on banking days. Thus, the term settlement
day refers to a 24-hour period during which VisaNet accumulates transactions. At the
end of a settlement day, VisaNet clears accumulators, advances the system settlement
date, and prepares reports.

VSS runs regardless of whether VisaNet has completed a cycle and prepares reports for
the transactions that have been sent through to the clearing system. (Refer to “Clearing
and Settlement” in this chapter for more details.) VSS and SMS reports are the definitive
sources for determining which transactions are included in a specific day's settlement.

Each banking day, VisaNet wire transfers the net settlement amount for the settlement
day to or from the participant's settlement account. For non-U.S. dollar settlement, the
wire transfer occurs two business days after the processing date.
NOTE
If a client processes BASE II messages as well as SMS messages, SMS and BASE II settlement can be combined
in one wire transfer. Clients can contact their Visa representatives to exercise this option.

8.1.3 Accumulation and Reconciliation

As transactions occur, SMS logs them and accumulates counts and gross amounts of
those transactions qualifying for settlement. At the end of the settlement day, SMS places
accumulated totals in 0520 reconciliation advices. The advices contain the number and
the value of transactions accumulated since the beginning of the settlement day.

VisaNet optionally delivers end-of-day (EOD) 0520 reconciliation advices automatically

when participating issuers and acquirers sign on to Advice Recovery mode. For details,
refer to “Network Management Transactions” in Chapter 4, Message Types and Flows.

In addition, clients can request 0520 reconciliation advices that contain the cumulative
settlement totals for the day, from start of processing to the time of the request for
the advice.

Clients can contact their Visa representatives to exercise these options.

After clients recover their advices, they can use them to cross-check acquirer center and
issuer center totals with those accumulated by SMS.

8-2 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 8: Settlement and Reconciliation Settlement Overview

Figure 8-1 illustrates the accumulation and advice-generation processes.

Figure 8-1 Overview of Online Process

ONLINE ACCUMULATION
Online Accumulators

Log Counts Gross

Amounts

Request
Acquirer SMS Issuer
Response

EOD CUTOFF
Online Accumulators

0520 0520
Advice Advice

Advice
File

Acquirer SMS Issuer

8.1.4 Clearing and Settlement

V.I.P. sends its logs for clearing and settlement, which are defined as follows:
• Clearing is the process of collecting an individual transaction from one client or
processor and delivering it to another. Clearing also includes the calculation of fees and
charges. (See “Valuation” in this chapter.)
• Settlement is the process of calculating and determining the net financial position of
each client for all transactions that are cleared.
The result of this process is a net settlement value for each settlement endpoint and
the production of daily settlement reports.

VisaNet accumulates transactions for each settlement day throughout the monthly cycle.
It stores pertinent information to produce month-end bills for processing charges. VisaNet
stores records of all chargebacks, representments, and adjustments processed during the
cycle and uses them to produce monthly exception transaction compliance reports.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 8-3
VisaNet Settlement Service (VSS) Chapter 8: Settlement and Reconciliation

8.1.4.1 Valuation
A key aspect of the clearing process is valuation, which includes the calculation of many
types of fees and charges. Although VisaNet performs certain aspects of valuation, not all
types of fees and charges are established by the SMS online component. The clearing
system calculates all of these values—for instance, fees, charges, and discounts.

VSS, described in the next section, does not perform valuation. VSS reports transactions
processed through the clearing system— BASE II and V.I.P. transactions. VSS aggregates
settlement advices created by the clearing system into a net settlement position at the
end of the cycle.

8.2 VisaNet Settlement Service (VSS)

SMS clients settle through VSS. VisaNet processes interchange transactions for SMS
and for BASE II through separate systems. SMS and BASE II perform their own clearing
functions. VSS performs the settlement functions for SMS and for BASE II in one
centralized service that ensures consistency in settlement and in reporting.

Figure 8-2 VisaNet Settlement Service (VSS) Process

BASE II Clearing SMS Clearing

SMS Reports

VisaNet Settlement Service

Funds Transfer

Settlement Reports

VSS provides clients with the following features:

• Flexibility in establishing settlement relationships.
• Standardized report layouts in print-ready and machine-readable formats.
• Several report delivery options.

8-4 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 8: Settlement and Reconciliation VisaNet Settlement Service (VSS)

• Client-defined funds transfer points.

• Choice of settlement options for alternately-routed transactions.
The following subsections describe these features along with key elements of the
settlement and reconciliation process in the VSS environment.

8.2.1 Settlement Services

Through VSS, Visa offers three settlement services:
• International Settlement Service.
• National Net Settlement Service.
• Area Net Settlement Service.
The International Settlement Service settles all international transactions and domestic
transactions for clients that do not participate in the National Net Settlement Service.

The National Net Settlement Service allows clients within a country to settle qualifying
domestic transactions through a central settlement agent bank. Qualifying transactions
are those for which the merchant, the acquirer, and the issuer are in the same country,
and for which the transaction currency is the local currency for that country.

The Area Net Settlement Service allows a group of countries to settle their transactions
domestically through an agent rather than through VisaNet. An example of an Area Net is
the OEAC Area Net (Caribbean).

8.2.2 Settlement Relationships

VSS provides flexibility for clients when they define settlement relationships.

Clients can define up to eight levels of settlement relationships in a hierarchy of settlement

reporting entities (SREs).

The different levels allow clients to build and to maintain optimum settlement relationships
for their business needs. For instance, clients can use the settlement relationship levels
to reflect the products in their organization. With this flexibility, clients can easily and
efficiently manage settlement functions.

8.2.3 Settlement Schedule

Both SMS and BASE II clear transactions seven days per week. Table 8-1 identifies the
standard cutoff time for SMS and for BASE II. The cutoff time changes by one hour when
times change because of daylight savings.

Table 8-1 Settlement Cutoff Timing—SMS and BASE II Transactions

Dates Cutoff Time

Second Sunday in March to first Sunday in 1000
November
First Sunday in November to second Sunday 1100
in March

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 8-5
VisaNet Settlement Service (VSS) Chapter 8: Settlement and Reconciliation

Table 8-2 identifies other key times in the daily settlement process.

Table 8-2 Daily Settlement Process

Key Time
Event Apr – Oct Oct – Apr
Settlement report processing and report 1000 1100
delivery begins.
Delivery of SMS reports and raw data to 1500 1600
VisaNet endpoints is completed.
Reporting of net settlement positions to 1500 1600
the national settlement banks for domestic
transactions occurs.
Delivery of funds transfer positions to the 1630 1730
Visa settlement banks is completed.

Table 8-3 summarizes the relative timing of these events.

Table 8-3 Timing of Settlement Process

For work of
Mon Tue Wed Thu Fri Sat Sun
SMS detail reports and raw Tue Wed Thu Fri Sat Sun Mon
data delivered seven days
a week
VSS summary reports Tue Wed Thu Fri Sat Sun Mon
prepared and delivered
seven days a week
Funds transfers for USD$ Tue Wed Thu Fri Mon Mon Mon
settlement
Funds transfers for Thu Fri Mon Tue Wed Wed Wed
non-USD$ settlement

NOTE
Clients that settle with the International Settlement Service now receive a single, consolidated funds transfer for
settlement amounts for Saturday, Sunday, and Monday, rather than three separate funds transfers. Transfer
occurs on Monday. Additionally, settlement amounts (In United States [U.S.] dollar settlement only) for holidays
observed by the United States Federal Reserve Bank are now consolidated into a single funds transfer that
occurs on the next business day.

8.2.4 Alternately Routed Transactions

Clients can use an alternate processor, such as Visa Resolve Online (VROL), to collect and
to deliver exception transactions and other back-office transactions. To do so, SMS clients
participate in the ATM/POS Split Routing Service and select the Alternate Routing option.

Clients can specify whether to settle these transactions with their normally routed
transactions or to settle them separately.

8-6 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 8: Settlement and Reconciliation VisaNet Settlement Service (VSS)

8.2.5 Funds Transfer

This section describes:
• SMS messages containing settlement-totals data.
• The movement of actual funds.

8.2.5.1 VSS 0620 Funds Transfer Messages

After the completion of the settlement process, VSS uses 0620 advices to send the day's
final funds transfer totals (but not the funds themselves) to issuers and to acquirers.
For information about these advices, see “Funds Transfer Message” in Chapter 4, Message
Types and Flows.

8.2.5.2 Movement of Funds

The final step in the settlement process is the actual funds transfer, during which funds
are collected from settlement entities with a net debit position and are paid to settlement
entities with a net credit position.

Funds transfer refers to the movement of funds between the client's settlement bank and
Visa's settlement bank for the purpose of settlement. Funds transfers are a net of the
client's credits and debits.

Funds can be settled in U.S. dollars (USD) or in non-USD currency with a client-selected
settlement bank.

Each funds transfer is associated with only one settlement account, although several funds
transfers can be associated with the same account.

8.2.5.3 Funds Transfer Point

The funds transfer point can be defined at any level in the settlement structure. This
flexibility allows clients using third-party processors to be responsible for their own funds
transfers.

8.2.6 VSS Reports

VSS offers control over settlement reporting and the ability to send reports to multiple
locations.

8.2.6.1 Layouts and Formats

VSS reports use a common layout for BASE II and SMS clients. This common layout allows
all clients to streamline their internal procedures. It eliminates the need to cross-train
personnel on different back-office reconciliation layouts for SMS and BASE II settlement
reports.

All VSS reports are available in print-ready and machine-readable formats. Receiving
reports in machine-readable formats allows clients and processors to:
• Provide automated interfaces to internal systems.
• Automate their reconciliation process.
To reflect the business needs of clients, VSS reports use common, business-oriented
terminology, which makes them easy to read and to reconcile.

8.2.6.2 Delivery
Clients can have their reports sent to multiple locations of their choice, including locations
other than their processing centers. Interchange routing does not determine the routing
of settlement information.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 8-7
VisaNet Settlement Service (VSS) Chapter 8: Settlement and Reconciliation

8.2.7 Reconciliation
SMS clients and processors must be able to reconcile their internal totals to those
provided by VisaNet. VSS is designed to help clients meet each of the following
reconciliation requirements:
• Match counts and amounts of financial transactions cleared by VisaNet.
• Match counts of non-financial transactions cleared by VisaNet.
• Match counts and amounts of transactions sent to or received from VisaNet for
settlement with clients' and processors' settlement totals.
• Find specific fields on the VSS reports that are needed for reconciliation.
Key elements of the reconciliation process include:
• Processors and VSS settlement hierarchies.
• Reports and files.
• SMS reconciliation messages.
The following subsections describe these elements.

8.2.7.1 Processors and VSS Settlement Hierarchies

Effective reconciliation procedures are based on the relationships between processors and
VSS settlement hierarchies. Possible relationships include:
• The processor performs funds transfer for all clients.
• The processor performs funds transfer for some clients and not for others.
• The processor supports National Net Settlement Service transactions.
Reports and files used in the reconciliation process reflect such hierarchies.

Figure 8-3 contains an example of a settlement hierarchy, in which a processor performs

funds transfer for all of its clients. In this case, Processor 1 (SRE 4) represents:
• The funds transfer totals for Banks A, B, and C.
• The total work performed by the processor.

8-8 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 8: Settlement and Reconciliation VisaNet Settlement Service (VSS)

Figure 8-3 Settlement Hierarchy Example—Processor Performing Funds Transfer

for All Clients

Funds Transfer

Processor 1
SRE 4

Bank A Bank B Bank C

SRE 1 SRE 2 SRE 3

8.2.7.2 Reports and Files

SMS clients and processors can reconcile their daily activity using the following reports
and files:
• VSS reconciliation reports—VSS reconciliation reports provide totals for all transactions
sent to or received from VisaNet, including non-financial transactions such as declines
and balance inquiries. The reports provide daily counts for these transactions.
• VSS settlement reports—VSS settlement reports provide interchange, reimbursement
fee, and charge totals settled by VSS.
• SMS transaction detail reports—Optional SMS transaction detail reports provide an
audit trail of all SMS transactions in the day's settlement total. Recipients can use the
reports to research differences between totals reported by VisaNet on the VSS reports
and those reported by the client's or the processor's system.
• Point-of-Sale Authorization (POSA) File—The POSA File provides debit and credit
transaction data, compiled on a daily basis. Participating acquirers get authorization
information that can improve billing accuracy and reduce fraud and chargeback
losses. The file also provides accurate point-of-entry information, enabling acquirers
to differentiate between a transaction originating from a manual key entry from one
originating from a proximity payment terminal, and distinguish between a transaction
made with a chip card containing a CVV from a transaction made with a chip card
without a CVV.
• Raw data files—Recipients can use raw data files, in conjunction with VSS
machine-readable reports, to automate the reconciliation process.
As an optional service, Visa provides raw data files that contain detailed information
about the settlement day's transactions for a given participant. Raw data is available
to all SMS issuers and acquirers. Users of this service can use the data to create
customized reports and to reconcile data reported by their own systems.
Raw data is distinguished from report data in that it is suited for automated processing.
The raw data records are produced from the same sources as SMS reports.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 8-9
For More Information Chapter 8: Settlement and Reconciliation

8.2.7.3 SMS Reconciliation Messages

In addition to using the reports mentioned in the previous subsection, issuers and
acquirers can optionally reconcile their online activity by using SMS reconciliation (0520)
messages that contain the current day's gross interchange totals (that is, the financial
position exclusive of fees and charges) accumulated online. Each message contains the
counts and amounts accumulated by VisaNet for approved, settled transactions.

VisaNet accumulates online totals at the processor level. The processor's totals include
the totals of each affiliate. A processor can use these messages to balance its online
totals to the totals accumulated by VisaNet.

VisaNet generates an 0520 message for each settlement currency. VisaNet accumulates
totals separately for International Settlement Service and National Net Settlement Service
transactions. A processor whose International Settlement Service and National Net
Settlement Service transactions are in the same settlement currency has the option of
getting reconciliation messages that include a combined total.

8.3 For More Information

For detailed information about the VSS topics in this section, refer to the VisaNet
Settlement Service (VSS) User's Guide.

8-10 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
 Client-to-Visa Connection Options 9
As described in Chapter 1, Single Message System Overview, issuers can choose to have
all of their transactions processed by SMS or can use BASE I and BASE II, and SMS,
to process their transactions.
• SMS supports all products in full financial mode.
• The BASE I and BASE II dual-message systems support all products except Interlink.
This chapter covers the VisaNet connection methods available to acquirers of Visa and
Plus transactions and issuers of proprietary cards with Plus marks that choose to receive
all Plus transactions in single-message format.

All Visa and Plus acquirer endpoints must process all ATM transactions in full financial
mode through VisaNet's Single Message System (SMS).

Issuers can also choose to use different processing methods for different Visa products.
Acquirers and issuers should review the requirements of their product mix when making
decisions regarding client-to-Visa connection options.

This chapter contains the following major sections:

• Direct Exchange (DEX)
• Extended Access Servers (EA Servers)
• VisaNet Connection Options
• Report and File Delivery Options
• SMS Functions To Be Supported

9.1 Direct Exchange

The Visa Direct Exchange (DEX) network provides a single network connection for all
message processing and file delivery services. The network has two major components:
• The Visa Message Gateway, which handles online transaction processing, resides at the
VIC and supports all V.I.P. messages. The Visa Message Gateway operates as a routing
switch for all V.I.P. transactions processed through it, controls the flow of traffic between
endpoints and the VIC, and replaces a VisaNet connection in end-to-end BASE I and
SMS online processing.
• The Open File Delivery (OFD) Service, which handles report and file delivery, including
the delivery of Automated Clearing House (ACH) data, BASE II data, and various SMS
reports and raw data.
For information about using DEX for report and file deliveries, refer to “Report and File
Delivery Options” in this chapter.

Clients can contact their Visa representatives for more information about DEX connections.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 9-1
VisaNet Connection Options Chapter 9: Client-to-Visa Connection Options

9.2 Extended Access Servers (EA Servers)

EA Servers are based on open systems technology and on a hardened Solaris operating
system. EA Servers are located at participating endpoint sites. The servers perform
authorization routing, file staging, and delivery services, and provide secure connectivity
to VisaNet.

EA Servers are flexible, thereby enabling easy deployment for future Visa product and
service offerings, as well as other customization. Their modular interface adapts to
front-end systems and integrates standard, off-the-shelf components that are scalable
to meet specific service needs.

9.3 VisaNet Connection Options

A client can connect to SMS through a VisaNet connection method, which is a Visa-owned
system located in the client's processing center. A VisaNet connection method can
connect the client to the BASE I and BASE II dual-message systems, to SMS, or to all three.
VisaNet connection methods can support online interchange and batch processing.

Online interchange is processed by the V.I.P. component of the connection, which

handles BASE I and SMS online traffic. The V.I.P. component can reside on the same
connection method as the BASE II component, or on a separate connection. The following
descriptions assume that the V.I.P. component is loaded on the same connection as the
BASE II component.

Various options are also available for host-to-host report and file delivery. This chapter
describes these options.

9.3.1 VisaNet Connection Files

VisaNet delivers report and data files to the VisaNet connection with the files' records
inside “envelopes” called Transaction Code (TC) records.

For information about TC records, refer to the files chapter of V.I.P. System SMS ATM
Technical Specifications, Volume 1 and Volume 2.

If the client is not ready to receive files at its host as soon as the VisaNet connection
receives them from VisaNet, the connection stores the files for later delivery to the client.

9.3.1.1 VisaNet Connection File Types

SMS clients can receive all data and report records at the VisaNet connection in a single,
undifferentiated file (file type UNDIF). Alternatively, the Customized Delivery feature allows
clients to request individual files for some types of data and reports.

9-2 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 9: Client-to-Visa Connection Options VisaNet Connection Options

Routing table files are not available through the Customized Delivery feature and are
delivered as shown in Table 9–1, VisaNet Connection File Types.

Table 9-1 VisaNet Connection File Types

File Type
(VisaNet TC Records Used for
Connection Data Records or for
File Name and Description Pullkey) Printlines
Undifferentiated UNDIF Routing Table: TC 33
• Visa Routing File
• Combined Visa/Plus ATM Routing Table
• All data and report records not selected for
Customized Delivery
Raw Data DBRAW TC 33
Machine-readable raw data for reconciliation
VSS Reports—Machine-Readable SETLM TC 46
VSS Reports—Print-Ready SETLP TC 47
VSS Reports—Machine-Readable and SETLR TC 46
Print-Ready TC 47

9.3.2 File Transfer Connectivity Between VisaNet Connection and Host

Clients can choose from among the following connectivity options to transfer files
between their VisaNet connection and their host:
• TCP/IP File Transfer Program (FTP) file delivery over token ring or over Ethernet
Visa provides the client with procedures for TCP/IP FTP delivery. Receipt of a file on
the host requires no additional design.
• Visa File Transfer Program (VFTP)
Visa provides this program to clients running MVS on IBM or IBM-compatible hosts.
Clients choosing to transfer files using VFTP may select one of the following protocol
connectivity options:
- SNA LU0 using token ring
- SNA LU0 Synchronous Data Link Control (SDLC)
- 2780 Point-to-Point protocol on a Binary Synchronous Communications (BSC)
- 3270 BSC Multipoint
- Coax
• Client-designed file transfer
Visa provides specifications for clients to use for developing a connection-to-host file
transfer application.
• Tape or Disk
The BASE II and DAS file processors on the VisaNet connection enable delivery of files
to tape or to disk. Various labeling options are available for tape transfer.
For more information about options for transferring report and data files from the
connection to a client's host, refer to About This Manual for a list of pertinent documents.

9.3.2.1 Client Host Processing of Files Received From VisaNet Connection

Visa provides reports and data in Visa-defined formats. If clients require additional
formats, clients must write their own software to print or to manipulate data transferred
to their hosts.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 9-3
Report and File Delivery Options Chapter 9: Client-to-Visa Connection Options

9.3.3 VisaNet Connection With V.I.P. and BASE II Components

A VisaNet connection configured for V.I.P. and for BASE II supports online and batch
processing for all Visa products. This connection configuration allows clients to:
• Send and receive online authorizations and full financial transactions through the V.I.P.
component.
• Send and receive clearing and exception transactions for products, BINs, or card ranges
not converted to SMS processing through the BASE II component.
• Receive end-of-day reports and files from SMS, from BASE II, and from VSS through
the BASE II component.
The BASE II component sends files to, and receives files from, a Visa-supplied Edit
Package. The Edit Package resides in the client's host or in an independent PC running
DOS. It is designed to:
• Ensure the integrity of the batch clearing and exception transactions that the client
sends to the BASE II System.
• Perform final processing of transactions that BASE II sends to the client, including the
transactions (TC records) that make up end-of-day reports and files.
For more information about the functions of the Edit Package, refer to the BASE II
Clearing: Edit Package Operations Guide or to the BASE II Clearing PC Edit Package for
Windows User's Guide.

9.3.4 VisaNet Connection With V.I.P. and DAS Components

Clients that process V.I.P. messages through SMS can use a VisaNet connection configured
for V.I.P. and for the Direct Access Service (DAS). This connection configuration allows
clients to:
• Send and receive online authorizations and full financial transactions through the V.I.P.
component.
• Receive end-of-day report and data files from SMS and from the BASE II Clearing
System through the DAS component.
• Receive deferred clearing draft transactions through bulk retrieval. For more information
about receiving deferred clearing advices in bulk files, refer to “DCAF Service” in
Chapter 1, Single Message System Overview.
DAS handles report files differently from data files. DAS strips all data files of hash bytes
but does not strip header and trailer records.

Clients can contact their Visa representatives for more information about DAS.

9.4 Report and File Delivery Options

The following options are available for delivering SMS reports, raw data, and routing
files to clients.
• Direct Access Service (DAS) with VisaNet connection.
• BASE II connection, which can be one of the following:
- VisaNet connection.
- Direct Exchange Open File Delivery (OFD), with TC 33 and TC 45 wrappers.
NOTE
All BASE II options, including the DEX OFD option, use TC 33 and TC 45 wrappers around SMS data and
reports; the following non-BASE II options do not use TC formats.

9-4 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 9: Client-to-Visa Connection Options SMS Functions To Be Supported

• SMS, DEX OFD connection, without TC wrappers.

• Remote Job Entry (RJE). This is the standard SMS option for non-VSS-migrated clients. It
is also an option for clients that have migrated to VSS.
Visa supports the 3770 SNA RJE protocols for point-to-point file transfer. RJE
transmissions can optionally include a client-specified Supertracks header.
• CONNECT:Direct (C:D). This is a standard option for all SMS clients.

9.4.1 VSS Report Delivery

VisaNet always delivers VSS machine-readable report data in TC 46 wrappers in TC 46
format, regardless of whether the client is using a BASE II connection or is using one of
the other options. CONNECT:Direct is not supported (except through DEX).

VisaNet handles VSS print-ready reports in TC 47 wrappers in one of two ways, depending
on the delivery method chosen by the client and entered in the system tables:
• Platform Option: Data in TC 47 wrappers is delivered to the BASE II connection in
TC 47 format.
• SMS Option: Data in TC 47 wrappers is sent to SMS to be combined with SMS detail
reports.
SMS strips the TC 47 wrapper to reveal the print-ready VSS reports, combines them
with the SMS detail reports, and delivers the resulting file through delivery methods
specified earlier.
If a BASE II connection is used to deliver this file of combined SMS and VSS reports,
which, like SMS reports alone, are in TC 45 wrappers, not TC 47 wrappers.

9.4.2 More Information

Clients can contact their Visa representatives for more information about the options
described above.

Information about the C:D product, which comes from Sterling Commerce, Inc., is available
at http://www.stercomm.com.

For information about VisaNet connections, see “VisaNet Connection Options” in this
chapter.

9.5 SMS Functions To Be Supported

There are three basic functions that SMS participants must support:
• Online transaction processing
• Settlement and reconciliation (see Chapter 8, Settlement and Reconciliation)
• Exception handling
The following sections describe each of these functions.

9.5.1 Online Transaction Processing

This section identifies the message format and delivery requirements for online transaction
processing.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 9-5
SMS Functions To Be Supported Chapter 9: Client-to-Visa Connection Options

9.5.1.1 Online Message Format

The V.I.P. message format supports all message types, financial and non-financial. Clients
must use the V.I.P. format for online financial processing.

9.5.1.2 Online Transaction Delivery

VisaNet always delivers real-time messages through:
• Direct Exchange (DEX) and the Visa Message Gateway.
• EA Servers
• The V.I.P. System component of the client's VisaNet connection.
The V.I.P. System component can be on the same connection as the BASE II or DAS
components or on a separate VisaNet connection.

9.5.2 Exception Handling

A client must decide how to set up its exception handling interface. Exception handling is
a process in which staff:
• Accumulate exceptions during the day.
• Conduct inquiries.
• Follow up on correspondence.
• Submit adjustment transactions to the interchange system.
Clients typically establish a workstation platform for this purpose. The workstation can be
a stand-alone system, connected to client's host, or connected to both.

Once a client is ready to transmit the accumulated exception items, the exception
handling system is connected to SMS. This connection is often through a dial-up line,
and transactions are transmitted verbally.

9.5.2.1 Visa Resolve Online (VROL)

Clients must use VROL for transmitting dispute documentation. Clients can also choose to
use VROL for processing SMS financial exception transactions. VROL is a web application
hosted on Visa Online that clients can access through the Internet. VROL also uses a Bulk
System Interface that works over a client’s OFD or VFES connection to Visa.

For an SMS client that uses VROL, financial exceptions are supported on all V.I.P.-supported
networks.

Acquirers can initiate the following transactions from the VROL web application or Bulk
System Interface:
• Adjustments
• Representments
• Fee collections and funds disbursements
• Free-text messages
Acquirers can receive the following transactions through VROL:
• Chargebacks
• Fee collections and funds disbursements (issuer-generated. Plus issuers can receive
Visa-generated 0220 funds disbursement messages that credit Plus ATM Format
Conversion issuers with the fee for BASE II-acquired ATM transactions that fail CPS/ATM
edit criteria.)
• Free-text messages

9-6 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 9: Client-to-Visa Connection Options SMS Functions To Be Supported

Issuers can initiate the following transactions from the VROL web application or Bulk
System Interface:
• Chargebacks
• Chargeback reversals
• Fee collections and funds disbursements (Plus issuers can receive Visa-generated 0220
funds disbursement messages that credit Plus ATM Format Conversion issuers with the
fee for BASE II-acquired ATM transactions that fail CPS/ATM edit criteria.)
• File maintenance messages
- Exception File listing messages
- PPCS/stop payment messages
- Fraud reporting
• Free-text messages
Issuers can receive the following transactions through VROL:
• Adjustments
• Representments
• Fee collections and funds disbursements (acquirer-generated)
• Free-text messages
For more information about Visa Resolve Online (VROL), clients can contact their Visa
representatives.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 9-7
SMS Functions To Be Supported Chapter 9: Client-to-Visa Connection Options

THIS PAGE INTENTIONALLY LEFT BLANK.

9-8 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
 Considerations for Dual-Message 10
Acquirers
Dual-message acquirers of Visa or Plus ATM transactions receive Tier II rates when they
comply with Tier II business requirements and either:
• Enhance their dual-message system with dual-message Custom Payment Service
(CPS)/ATM features
• Use the Single Message System (SMS) to process ATM transactions in full financial mode

See V.I.P. System Services, Volume 2, and to the Visa Global ATM Planning Guide.

10.1 CPS/ATM vs. V.I.P. SMS

Dual-message acquirers need to make a decision regarding which option to implement
for their ATM transaction processing. Which option is best for each acquirer depends on
many factors that are specific to the acquirer's own operating environment.

For instance, if the acquirer's ATM network operates in single-message mode, that
infrastructure can serve as the base with which to participate in V.I.P SMS ATM Service. On
the other hand, if the acquirer's ATM system operates in dual-message mode, upgrading
it to dual-message Custom Payment Service (CPS)/ATM may provide an adequate
enhancement path.

The acquirer's future product expansion plans can also influence the ATM processing
decision. For instance, a client that is an acquirer and issuer may plan to add the Interlink
and Plus marks to its own proprietary ATM card. Because Interlink operates only in
the single-message mode, this client may choose to connect to SMS for its Interlink
processing as well as for its ATM traffic, which uses the same card.

The decision can be made based on monetary savings. The projected three-year benefits
in back-office and operations savings, as shown in the following hypothetical example,
may result in the acquirer deciding to upgrade to single-message processing rather than
to enhance its dual-message system with dual-message CPS/ATM.

In Table 10-1, the Tier II differential of USD$0.75 is applied to 50,000 international

transactions per year, to produce incentive fees of USD$112,500 over a three-year
period. The cost to upgrade the system is subtracted from the revenue generated by

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 10-1
Dual-Message CPS/ATM vs. V.I.P. SMS Chapter 10: Considerations for Dual-Message Acquirers

the incentive fees. Savings in operations and back-office costs are calculated over the
same three-year period.

Table 10-1 Example of Savings Comparison

Items Dual-Message CPS/ATM Single- Message

Total incentive fees multiplied USD$112,500.00 USD$112,500.00
by 3 years
Cost to upgrade (USD$100,000.00) (USD$140,000.00)
Back-office savings per year USD$75,000.00 USD$150,000.00
multiplied by 3 years
(reduced exceptions)
Operations savings per year USD$0.00 USD$75,000.00
multiplied by 3 years
(settlement)
Three-year benefit projection USD$87,500.00 USD$197,500.00

The benefits of enhancing the system with dual-message CPS/ATM features or converting
to single-message processing vary by acquirer and decrease back-office work because
fewer chargebacks and inquiries can be expected when the integrity of online and batch
transactions is improved.

The single-message option provides the following added ongoing benefits:

• A better cash flow: the acquirer may be reimbursed faster than if the acquirer sends the
clearing and settlement message in a separate later step.
• Fewer operational steps: no separate settlement programs need to be coordinated
and executed.
• A single point for reconciliation and research: an online transaction log contains all
clearing data.

10.2 Dual-Message CPS/ATM vs. V.I.P. SMS

The following chart contains points that acquirers should consider when evaluating the
changes necessary to upgrade to dual-message CPS/ATM Service or to V.I.P. SMS, and
when calculating the costs associated with these changes. Each item is explained in
more detail in the descriptions following the chart. The assumption made in the chart is
that the acquirer currently supports Visa and Plus ATM transactions in a dual-message
environment and is connected to the BASE I System and to the BASE II Clearing System.

Points for consideration are presented in three categories:

10-2 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 10: Considerations for Dual-Message Acquirers Dual-Message CPS/ATM vs. V.I.P. SMS

• Online Transaction Processing (Table 10-2)

• Clearing and Settlement (Table 10-3)
• Exception Handling (Table 10-4)

Table 10-2 Online Transaction Processing

Dual-Message
Item Dual-Message CPS/ATM SMS
Message Types 01xx Same as dual 02xx
• authorizations • originals
• confirmations • adjustments
• balance inquiries • balance inquiries
04xx 04xx
• reversals • reversals
06xx 06xx
• free-text • free-text
Message Format V.I.P. V.I.P. V.I.P.
Network ID Not used Same as dual Network 0002 = VISA

Network 0004 = Plus

Reversals Required Same as dual Required
Partial Reversal message Same as dual Online adjustment
Dispense Detected 0400 0220
by ATM
CPS Transaction Not applicable Required Required for new
Identifier participants
CPS Authorization Not applicable Required Required for new
Characteristics participants
Indicator
CPS Validation Code Not applicable Required Not applicable

Table 10-3 Clearing and Settlement

Dual-Message
Item Dual-Message CPS/ATM Single-Message
Clearing and Submits batch of Submits batch of Automatic clearing as
Settlement Step clearing records to clearing records to part of authorization
BASE II within 4 days BASE II within 3 days
Reconciliation Host draft capture Same as dual Optional raw data file
system to VSS reports
Reports Received through Same as dual Received through
the BASE II VisaNet BASE II VisaNet
connection connection

Table 10-4 Exception Handling

Dual-Message
Item Dual-Message CPS/ATM Single-Message
Chargebacks Through BASE II or Same as dual Online 0422 or VROL
Visa Resolve Online
(VROL)

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 10-3
Dual-Message CPS/ATM vs. V.I.P. SMS Chapter 10: Considerations for Dual-Message Acquirers

Table 10-4 Exception Handling (continued)

Dual-Message
Item Dual-Message CPS/ATM Single-Message
Representments Through BASE II or Same as dual Online 0220 or VROL
Visa Resolve Online
(VROL)
Adjustments Through BASE II or Same as dual Online 0220 or VROL
Visa Resolve Online
(VROL)

10.2.1 Online Transaction Processing Differences

The following sections describe processing differences between single-message processing
and dual-message processing.

10.2.1.1 Message Types

• Dual-message mode:
VisaNet support the following online transactions: authorizations, confirmations (online
adjustments), balance inquiries, and reversals. VisaNet supports the same set with
dual-message CPS/ATM. These transactions are submitted to the BASE I System and
have no financial impact. Financial transactions are cleared and settled in batch mode
in a subsequent step using a file created by the acquirer one to four days after the
authorization transaction took place. Exception transactions are also handled in batch
mode.
• Single-message mode:
All ATM transactions are handled online, including exception transactions. All
transactions except balance inquiries have financial impact and are cleared and settled
as part of the authorization request. There is no subsequent batch step to clear and
settle the transaction.

10.2.1.2 Message Format

The V.I.P. message format applies to dual-message mode as well as for single-message
mode.

10.2.1.3 Network ID
• Dual-message mode:
The concept of network ID is not used. The same concept applies to dual-message
CPS/ATM.
• Single-message mode:
A network identifier (ID) is used to denote the ATM or POS network with which the card
is affiliated. For instance, Plus transactions are processed as network ID 0004, Interlink
transactions as network ID 0003, and Visa transactions as network ID 0002. Co-branded
cards (for instance, a Visa card with a Plus mark on it) can be processed as network
ID 0002 or 0004 at the option of the acquirer or of VisaNet. Different networks can
have different rules, fees, and data requirements.

10-4 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 10: Considerations for Dual-Message Acquirers Dual-Message CPS/ATM vs. V.I.P. SMS

10.2.1.4 Reversals
• Dual-message mode:
A reversal is required if the cardholder cancels the authorization transaction before
it is completed, or if the acquirer's system detects a malfunction that prevents the
cardholder from receiving the requested withdrawal amount. Because there is no
financial impact, some acquirers do not send reversals and simply do not include the
transaction in the subsequent clearing and settlement step. Although this has the
desired effect from the acquirer's perspective, it creates a burden for issuers because
it could affect the cardholder's available funds if the issuer places a hold on funds
based on an authorization that never clears.
• Dual-message CPS/ATM:
Reversals are required as above, and the test scripts include reversal conditions.
• Single-message mode:
All online transactions have financial impact. Therefore, the acquirer must create a
reversal for the circumstances described above to avoid subsequent chargebacks. Test
scripts include reversal conditions.

10.2.1.5 Partial Dispense

• Dual-message mode:
A reversal transaction (0400) is needed if the ATM detects a failure to dispense funds
that causes less funds to be dispensed than were authorized. The subsequent batch
clearing and settlement record reflects the lesser amount dispensed. The same applies
to dual-message CPS/ATM.
• Single-message mode:
There is no confirmation transaction. When the ATM detects a misdispense, the acquirer
submits an adjustment (0220) transaction backing out the amount not dispensed.
This transaction is done immediately after the misdispense, without intervening
transactions occurring at the ATM.

10.2.1.6 CPS Transaction Identifier

The transaction identifier (TID) is a unique number assigned by VisaNet to all transactions.
The TID is returned to the acquirer in every approved transaction response in the
following ATM modes:
• Dual-message mode.
• Dual-message CPS/ATM.
• Single-message mode.

10.2.1.7 CPS Authorization Characteristics Indicator

• Dual-message mode:
The authorization characteristics indicator (ACI) field is not used.
• Dual-message CPS/ATM:
The acquirer uses the ACI to request Tier II fees.
• Single-message mode:
The acquirer provides the ACI to maintain consistency across VisaNet-provided services.

10.2.1.8 CPS Validation Code

• Dual-message mode:
The validation code is not used.
• Dual-message CPS/ATM:

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 10-5
Dual-Message CPS/ATM vs. V.I.P. SMS Chapter 10: Considerations for Dual-Message Acquirers

VisaNet returns a validation code to the acquirer in every approved transaction

response. The validation code is a value calculated from key fields in the authorization
transaction. The acquirer places the same key fields and the validation code in the
clearing message for verification by VisaNet.
• Single-message mode:
The validation code is not necessary because there is no subsequent clearing message.

10.2.2 Clearing and Settlement Differences

The following sections describe differences in clearing and settlement between
single-message processing and dual-message processing.

10-6 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Chapter 10: Considerations for Dual-Message Acquirers Dual-Message CPS/ATM vs. V.I.P. SMS

10.2.2.1 Clearing and Settlement Step

• Dual-message mode:
The acquirer submits an authorization request (0100) when the transaction is performed.
Up to four days later, the acquirer submits a clearing and settlement batch record (TC 07).
• Dual-message CPS/ATM:
The acquirer performs the same functions as in dual-message mode, but the clearing
cycle is shortened to a maximum of three days. The validation code and the TID
received from VisaNet in the authorization response must be included in the TC 07
along with other key fields, such as the account number and transaction amount fields,
that were present in the authorization. VisaNet uses the validation code to determine
that the key authorization fields are unaltered in the clearing message.
• Single-message mode:
The acquirer does not go through a separate batch step to clear and settle its ATM
transactions. The 0200 original transaction is a financial transaction that contains
sufficient information to clear and settle, and to allow the issuer to post to the
cardholder's account.

10.2.2.2 Reconciliation
• Dual-message mode and dual-message CPS/ATM:
The acquirer needs to reconcile its host draft capture system to the BASE II Edit Package
reports and to the BASE II settlement reports.
• Single-message mode:
VisaNet produces detail reports of all transactions processed by VisaNet as well as
settlement summary reports. VisaNet also provides this data in a raw data file, which
some clients use to reconcile their transaction logs to the activity reported by VisaNet.
The issuer and acquirer may choose to write software to automate the identification of
discrepancies between VisaNet's raw data file and the clients' logs.

10.2.2.3 Reports
• Dual-message mode and dual-message CPS/ATM:
All client reports are produced by BASE II and delivered through the BASE II VisaNet
connection at the client's site for printing by the Edit Package. These are summary
settlement reports.
• Single-message mode:
Detail reports, summary reports, and files are transmitted to the client's VisaNet
connection. The client has several options for receiving and for processing the reports
and files. These options are set up in the VisaNet connection at installation time and
can be subsequently modified as needed.

10.2.3 Exception Handling Differences

The following sections describe differences in exception handling between single-message
processing and dual-message processing.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications 10-7
Recommendation Chapter 10: Considerations for Dual-Message Acquirers

10.2.3.1 Chargebacks
• Dual-message mode and dual-message CPS/ATM:
The acquirer receives chargebacks as TC 17 batch records. In dual-message CPS/ATM,
the chargeback must include the TID of the original TC 07 record.
• Single-message mode:
The acquirer receives chargebacks online as ISO 0422 transactions or through Visa
Resolve Online (VROL). The chargeback must include the TID of the original transaction.

10.2.3.2 Representments
• Dual-message mode and dual-message CPS/ATM:
The acquirer submits representments as TC 27 batch records. In dual-message CPS/ATM,
the representment must include the TID.
• Single-message mode:
The acquirer submits representments online as ISO 0220 transactions or through VROL.
The acquirer must include the TID in the representment.

10.2.3.3 Back-Office Adjustments

• Dual-message mode and dual-message CPS/ATM:
Discrepancies found when balancing the ATM are submitted as batch credit or debit
transactions. In dual-message CPS/ATM, these adjustments should include the TIDs
of the original transactions.
• Single-message mode:
Adjustments are submitted online as 0220 advices.
Regardless of the processing method, VROL can be used for back-office adjustments.

10.3 Recommendation
Visa recommends that the acquirer perform a cost-to-benefit analysis of the following
two options:
• Enhance system with dual-message CPS/ATM
• Upgrade system to single-message
Points made in the chart in this chapter could serve as a guideline for the analysis, which
should also factor in system and future product direction.

Once the analysis is complete, the acquirer is better prepared to choose the best option
for its environment.

10-8 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
ATM Processing Integration A

SMS participants that want to format and to process all ATM transactions without
distinguishing between Visa ATM and Plus ATM transactions can do so by using ATM
Transaction Standardization.

A.1 ATM Transaction Standardization

Clients that use the ATM Transaction Standardization option do not need to:
• Send or receive Plus contact information in Field 44—Additional Response Data.
Field usage must conform to the Visa SMS usage defined in V.I.P. System SMS ATM
Technical Specifications, Volume 1 and Volume 2. Acquirers and issuers that want
to receive Plus contact information in field 44 should not use the ATM Transaction
Standardization option.
• Receive the state code in positions 1–2 of Field 59—National Point-of-Service
Geographic Data when the country code in the transaction is for the United States
(U.S.) or for Visa Canada (CAN).
For clients that use the ATM Transaction Standardization option, SMS does not forward
field 59 unless the country code is US (United States) or CAN (Visa Canada). The state
or the province code is required in field 59 if the country code is US or is CAN.
For Plus transactions (network ID 0004), SMS forwards 00 in field 59 to issuers when the
country code is not US or CAN. Issuers that want to receive 00 in field 59 should not
use the ATM Transaction Standardization option.
• Send or receive Plus message reason codes in Field 63.3—Message Reason Code.
Acquirers and issuers that want to convert to a single set of message reason codes for
all ATM transactions processed by VisaNet may do so by selecting the ATM Transaction
Standardization option. Clients that choose this option must use Visa message reason
codes for Visa and Plus transactions. See V.I.P. System SMS ATM Technical Specifications,
Volume 1 and Volume 2.
Acquirers and issuers that want to use Plus and Visa message reason codes in field 63.3
should not select the ATM Transaction Standardization option.

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications A-1
ATM Transaction Standardization Appendix A: ATM Processing Integration

Clients may continue to send and to receive Plus data as they currently do, regardless
of whether they choose to use the ATM Transaction Standardization option. Table A-1
provides a field-by-field description of the differences of using this option.

Table A-1 ATM Transaction Standardization Option

No Change Options Chosen

Option Field Number, Name Acquirer Issuer Acquirer Issuer
ATM Field 44—Plus Contact Must send and Must send and Will receive only Will receive only
Transaction receive Plus and receive Plus and the Visa usage of the Visa usage of
Standardization Visa usages of Visa usages of field 44 field 44
field 44 field 44
Field 59—State/Province Must send and Always receive No change Will no longer
Code receive if the field even if the receive 00 in
country code is transaction is not field 59 for
US or is CAN for the U.S. or for non-U.S. or for
Canada non-Canada
Field 63.3—Message Must send and Must send and Will send and Will send and
Reason Code receive Plus and receive Plus and receive only Visa receive only Visa
Visa reason codes Visa reason codes reason codes for reason codes for
Visa and Plus Visa and Plus
transactions transactions

A.1.1 Client Impacts

ATM acquirers and issuers that use the ATM Transaction Standardization option no longer
need to:
• Send or receive field 44 (Plus usage).
• Use Plus message reason codes in field 63.3.
In addition, issuers do not need to receive field 59 (for non-U.S. or for non-CAN).

Acquirers and issuers that choose to continue sending or receiving these fields or to
continue using Plus reason codes may do so. There are no changes to reports and to raw
data, even for clients that choose this option.

Client testing is required for this change. Clients can contact their Visa representatives to
make the arrangements.

A-2 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Index

A advice
recovery sign-on and off 6-15
access and use fees 1-28
response cannot be delivered 4-42
account number edit, STIP 6-8
Advice File 6-14
account transfer transaction 4-5
Advice Recovery
acquirer
mode, changing 6-15
dual-message considerations
Advice Retrieval Service—SMS 1-12
clearing and settlement differences 10-6
advice retrieval, SMS 6-15
exception handling differences 10-7
Advice Retrieval—SMS 4-27
online transaction processing differences 10-4
advices, STIP
exception processing 3-1
creating 6-7
participation requirements
evaluation of 6-18
exception processing 3-3
flags in header 6-18
online transaction processing 3-2
recovering 6-14
PIN security 3-3
recovery status 6-16
services
reversal processing 6-13
optional 3-3
Alternate Routing option 7-6
Stand-In Processing (STIP) 6-14
amount, decimal places 5-3
acquirer responsibilities
approval response cannot be delivered 4-40
establishing POS connection 3-2
ATM cash disbursement adjustment/misdispense transaction 2-3
activity
ATM cash disbursement transaction 2-2
checks, STIP
ATM Format Conversion Service 3-5
excessive activity 6-6
ATM participation requirements
non-standard activity 6-6
issuer 3-4
not checked 6-6
service options
standard activity 6-6
issuer 3-4, 3-6
file, STIP 6-13
ATM Processing Integration
adjustment transaction 4-10
transaction standardization A-1
acquirer unavailable 4-47
ATM products 1-9
issuer unavailable 4-46
ATM/POS Account-Type Split Routing option 7-5
usage 2-4
ATM/POS Split Routing option 7-5
administrative
ATM/POS Split Routing Service 1-10
charges 1-29
ATM/POS Split Routing. Service 7-4
administrative transactions
Automatic Cardholder Database Update (Auto-CDB) Service 1-12
free-text message 4-20
funds transfer message 4-22
types of 2-6

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications IX-1
 Index

B charges
assessed by Visa
back-office adjustments, exception handling differences 10-8
administrative 1-29
balance inquiry and decline fees 1-28
currency conversion 1-29
balance inquiry transaction 4-3, 6-5
processing 1-29
BASE I System
cardholder database residency 1-29
description 1-3
cardholder database update 1-29
overview 1-3
daily reports listing 1-29
BASE II
monthly reporting 1-29
components 9-4
processing 1-29
BASE II System 1-5
reconciliation 1-29
reporting 1-29
C settlement 1-29
Card Verification Value (CVV) Service 6-18 transaction processing 1-29
description of 1-14 VisaNet connection method access 1-29
Card Verification Value 2 (CVV2) Service 1-15, 6-19 clearing
cardholder definition 1-5
billing currency 5-1 definition of 8-3
transactions valuation 8-4
ATM cash disbursement 2-2 clearing and settlement differences
Plus shared deposit 2-3 clearing and settlement step 10-7
Cardholder Database reconciliation 10-7
Advice File 6-14 reports 10-7
file update charges 1-29 client-to-client fees 1-26, 1-28
residency charges 1-29 client-to-Visa connection options
cardholder transactions exception handling 9-6
account transfer 4-5 online transaction processing 9-5
balance inquiry 4-3 CMI, See Common Member Interface (CMI)
definitions 2-2 collection-only transaction 2-6
quasi-cash 4-2 Common Member Interface (CMI)
cash disbursement adjustment transaction 4-8 overview 1-7
CAVV, See Cardholder Authentication Verification Value (CAVV) processes 1-7
Verification Service connection methods
chargeback VisaNet 1-2
reversal transaction 2-5 connection options 9-2
transactions CPS, transaction processing differences
usage 2-5 authorization characteristics indicator 10-5
chargeback reversal transaction 4-12 transaction identifier 10-5
chargeback transaction 4-11 validation code 10-5
chargeback transactions currencies
acquirer unavailable 4-50 applicable to transactions 5-1
issuer unavailable after chargeback conversion
4-51 calculation 5-2
chargebacks variations 5-3
exception handling differences 10-8 decimal places 5-3
currency conversion charges 1-29
Currency Precision Service 5-3
cutoff time 8-5

IX-2 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Index

CVV 6-18 exception file

CVV2 6-19 checked by STIP for balance inquiries 6-5
CVV2 Service, See Card Verification Value 2 (CVV2) Service exception processing
acquirer 3-1, 3-3

D chargeback reversal 4-12

client-to-Visa connection 9-6
DAS, See Direct Access Service (DAS)
exception transactions 4-46
DCAF Service, See Deferred Clearing Advice File (DCAF) Service
financial transactions
declined financial transactions, settlement impact of 8-1
approval response cannot be delivered 4-40
deferred clearing
decline response cannot be delivered 4-41
advice retrieval 1-15
issuer fails to respond 4-36
Deferred Clearing Advice File (DCAF) Service 1-15
issuer responds late 4-37
DES (Data Encryption Set) encryption working keys 4-29
issuer unavailable 4-32, 4-34
Direct Access Service (DAS)
issuer 3-1, 3-5
components 9-4
reversal transactions
DKE Service, See Dynamic Key Exchange (DKE) Service
advice response cannot be delivered 4-42
domestic interchange reimbursement fees (IRFs) 1-26
issuer unavailable 4-43
dual-message
unsolicited 4-45
considerations
Exception processing
acquirer 10-1
file edit, STIP 6-4
clearing and settlement differences 10-6
exception transactions
exception handling differences 10-7
adjustment 4-10
online transaction processing differences 10-4
acquirer unavailable 4-47
service options 10-1
definition 2-4
CPS/ATM transaction processing differences
issuer unavailable 4-46
back-office adjustments 10-8
chargeback 4-11
chargebacks 10-8
acquirer unavailable 4-50
clearing and settlement step 10-7
definition 2-5
CPS authorization characteristics indicator 10-5
issuer unavailable after chargeback 4-51
CPS transaction identifier 10-5
chargeback reversal 2-5
CPS validation code 10-5
handling 2-5
message types 10-4
representment 4-13
network ID 10-4
acquirer unavailable 4-47
partial dispense 10-5
definition 2-5
reconciliation 10-7
issuer unavailable 4-46
reports 10-7
excessive activity edit, STIP 6-6
representments 10-8
reversals 10-5
Dynamic Key Exchange (DKE) Service 1-16, 4-29 F
fee collection transactions 2-5

E fees
access and use 1-28
echo test messages 4-26
assessed by Visa
edit checks, STIP, account number 6-8
client-to-client 1-28
end-of-day processing 1-8
international acquiring (IAF) 1-28
exception differences
balance inquiry and decline 1-28
back-office adjustments 10-8
client-to-client 1-26
chargebacks 10-8
daily reports listing 1-29
representments 10-8

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications IX-3
 Index

interchange reimbursement fees (IRFs) interregional 1-27

types 1-26 intraregional 1-27
monthly reporting 1-29 types 1-26
related transactions 2-5, 4-14 international acquiring fees (IAFs) 1-28
reporting 1-29 international interchange reimbursement fees (IRFs) 1-27
field flows International Settlement Service 8-5
multicurrency 5-5 interregional interchange reimbursement fees (IRFs) 1-27
file intraregional interchange reimbursement fees (IRFs) 1-27
maintenance transactions 4-18 IRFs, See interchange reimbursement fees (IRFs)
file maintenance transactions 2-5 ISO
files message format 3-1
delivery options, VisaNet connection 9-2 issuer
transfer connectivity 9-3 exception processing 3-1
types, VisaNet connection 9-2 fails to respond transaction 4-36
flags Multicurrency Service 5-2
advice evaluation 6-18 participation requirements
flexible times for online delivery of advices from BASE II ATM Format Conversion Service 3-5
endpoints 1-15 exception processing 3-5
Fraud Reporting System (FRS) 1-25, 4-23 online transaction processing 3-2
free-text message transaction 4-20 other functions 3-4
FRS, See Fraud Reporting System (FRS) PIN verification 3-5
funds disbursement transaction SMS Advice Retrieval Service 3-5
definition 2-5 stand-in processing (STIP) 3-5
funds transfer responds late transaction 4-37
defining endpoint 8-7 service options 3-4, 3-6
description 8-7 STIP options 6-2
in U.S. and non-U.S. dollars 8-7 unavailable transaction 4-32, 4-43
message 4-22 unavailable, account listed on exception file 4-34
process 8-7 issuing country 1-27
processor performing for all clients 8-8
funds transfer totals message
reconciliation 4-16
M
message
format, transaction processing differences 10-4
G message flows
gateway exception processing 4-32
Visa Message 9-1 exception transactions 4-46
Gateway Services 7-2 reversal transactions 4-42
normal processing
H administrative transactions 4-20
exception transactions 4-10
hierarchy, settlement 8-8
file maintenance transactions 4-18
network management transactions 4-24
I reconciliation transactions 4-16
IAFs, See international acquiring fees (IAFs) system-generated transactions 4-6
Integrated Billing System (IBS) 1-29 message integrity 2-8
interchange reimbursement fees (IRFs) 1-26 Message Status Flags field 6-18
domestic 1-26 messages
international 1-27 types, transaction processing differences 10-4

IX-4 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Index

multicurrency field flows 5-5 transaction processing differences

Multicurrency Service 5-1 CPS authorization characteristics indicator 10-5
clients not participating 5-5 CPS transaction identifier 10-5
currency conversion variations 5-3 CPS validation code 10-5
Currency Precision Service 5-3 message format 10-4
definition 1-20 message types 10-4
issuer 5-2 network ID 10-4
partial dispense 10-5
N reversals 10-5
online fraud reporting transaction 2-6
National Net Settlement Service 8-5
Open File Delivery (OFD) Service 9-1
network ID, transaction processing differences 10-4
operating modes
network management
advice recovery 6-15
messages
normal 6-15
advice recovery 6-15
Normal (operating) mode change 6-15
network management transactions P
dynamic key exchange 4-29 partial dispense, transaction processing differences 10-5
echo test messages 4-26 participation requirements
recovery sign-on/off messages 4-27 acquirer 3-1
sign-on/off messages 4-24 issuer 3-4
usage 2-7 PIN (personal identification number)
non-standard activity edit, STIP 6-6 security, acquirer 3-3
normal processing STIP processing check 6-10
administrative transactions 4-20 verification, issuer 3-5
exception transactions 4-10 PIN Verification Service (PVS) 1-20, 3-5
file maintenance transactions 4-18 PIN/No-PIN Split Routing Service 1-11
network management transactions 4-24 PIN/No-PIN Split Routing. Service 7-6
reconciliation transactions 4-16 Plus shared deposit transaction 2-3
system-generated transactions 4-6 POS Visa and Visa Electron
functions supported

O exception handling 9-6

online transaction processing 9-5
OFD, See Open File Delivery (OFD) Service
POS—Visa and Visa Electron
online
participation requirements
dynamic key exchange transaction 4-29
acquirer 3-1
fraud reporting 4-23
VisaNet connection method 3-1
message format 9-6
testing 3-2
transaction delivery 9-6
Priority Routing Service 7-4
transaction processing
processing
message format 9-5
BASE I 1-3
transaction delivery 9-6
BASE II 1-5
charges 1-29
Common Member Interface (CMI) 1-7
networks 1-1
Single Message System (SMS) 1-4
VisaNet Settlement Service (VSS) 1-5
processing center
establishing 3-1

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications IX-5
 Index

testing 3-2 response cannot be delivered 4-41

processors response codes, STIP 6-12
funds transfer for all clients 8-8 reversal
settlement hierarchy 8-8 processing, STIP
products creating advices 6-13
Visa 1-1 recovering advices 6-14
PVS, See PIN Verification Service (PVS) updating Activity File 6-13
transaction

R system-generated 4-6
usage 2-3
raw data files, contents of 8-9
transaction processing differences 10-5
reconciliation
reversal transaction
0520 messages 8-10
advice response cannot be delivered
charges 1-29
4-42
definition 8-8
issuer unavailable
network management message 4-16
4-43
processor performing funds transfer for all clients 8-8
reversal transactions
settlement hierarchy 8-8
unsolicited
SMS to VSS
4-45
using raw data files 8-9
routing
using SMS transaction detail reports 8-9
alternatives 1-10
using VSS reports 8-9
services
transactions
Gateway Services 7-2
clearing and settlement differences 10-7
Priority Routing 7-4
usage 2-5
Split Routing 7-4
reconciliation advices 4-17
tables
reconciliation transaction
Plus BIN table 7-3
funds transfer totals message 4-16
transaction 7-1
reconciliation advices 4-17
Visa/Plus ATM 7-2
recovery
routing services
sign-on/off messages 4-27
ATM/POS Split Routing Service 1-10
reporting fees and charges 1-29
Gateway Services 1-11
reports
PIN/No-PIN Split Routing Service 1-11
clearing and settlement differences 10-7
Priority Routing Service 1-11
listing fees and charges 1-29
SMS to VSS
using raw data files 8-9 S
using SMS transaction detail reports 8-9 security
using VSS reports 8-9 PIN 3-3
representment transaction services
acquirer unavailable 4-47 Advice Retrieval Service—SMS 1-12
definition 2-5 advice retrieval, SMS 6-15
issuer unavailable 4-46 Advice Retrieval—SMS 4-27
message flow 4-13 ATM Format Conversion Service 3-5
representments ATM/POS Split Routing. Service 7-4
dual- versus single-message differences 10-8 Automatic Cardholder Database Update (Auto-CDB)
single-message mode, transaction processing differences 10-8 Service 1-12
requirements Card Verification Value 2 (CVV2) 1-15
acquirer 3-2

IX-6 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Index

Cardholder Authentication Verification Value (CAVV) sign-on and sign-off

Verification Service 6-19 advice recovery 6-15
CVV 6-18 sign-on/off
CVV2 6-19 message transaction 4-24
Deferred Clearing Advice File (DCAF) 1-15 Single Message Service (SMS)
Dynamic Key Exchange (DKE) 1-16, 4-29 description 1-1
flexible times for online delivery of advices from BASE II Single Message System (SMS)
endpoints 1-15 ATM Products 1-9
Fraud Reporting System 4-23 benefits 1-7
Fraud Reporting System (FRS) 1-25 description 1-4
Gateway 7-2 end-of-day processing 1-8
Multicurrency 1-20, 5-1 message integrity 2-8
online fraud reporting 4-23 online transaction flow (ATM) 1-7
optional overview 1-4
acquirer 3-3 processing summary 1-7
issuer 3-6 raw data 8-9
PIN Verification 1-20 reporting fees and charges 1-29
PIN/No-PIN Split Routing. Service 7-6 routing 1-10
Priority Routing 7-4 Services 1-10
required single-message mode, transaction processing differences
acquirer 3-2 back-office adjustments 10-8
both acquirer and issuer 3-1 chargebacks 10-8
issuer 3-4 clearing and settlement step 10-7
routing 1-10 CPS
SMS Advice Retrieval Service 3-5 authorization characteristics indicator 10-5
Split Routing 7-4 transaction identifier 10-5
VisaNet Settlement Service (VSS) 8-4 validation code 10-6
VMP 1-26 messages
settlement types 10-4
accumulation and reconciliation, relationship between 8-2 network ID 10-4
charges 1-29 partial dispense 10-5
criteria 8-1 reconciliation 10-7
day 8-2 reports 10-7
defining relationships 8-5 representments 10-8
definition 1-5 reversals 10-5
definition of 8-3 SMS, See Single Message System (SMS)
funds transfer 8-7 SMS Advice Retrieval Service 3-5
processing description 8-1 SMS ATM Transactions
reconciliation 8-8 transaction types supported 2-2
schedule 8-5 Split Routing Service 7-4
transactions qualifying for 8-1 stand-in processing (STIP)
VisaNet Settlement Service (VSS) 8-4 issuer parameters 3-5
settlement hierarchy and processors 8-8 standard activity edit, STIP 6-6
settlement services station
international 8-5 Normal (operating) mode 6-15
national net 8-5 operating status 6-15
overview 8-5 types 6-15

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications IX-7
 Index

STIP chargeback reversal 2-5

acquirer processing 6-14 collection-only 2-6
Activity File 6-12 currencies applicable 5-1
advices currency conversion variations 5-3
creating 6-7 exception processing
flags 6-18 adjustment, acquirer unavailable 4-47
recovering 6-14 adjustment, issuer unavailable 4-46
recovery status 6-16 adjustments 4-10
authorization processing checks chargeback 4-11
Exception File 6-4 chargeback reversal 4-12
PIN for Visa Electron 6-10 chargeback, acquirer unavailable 4-50
excessive activity 6-6 representment 4-13
issuer options 6-2 representment, acquirer unavailable 4-47
response codes 6-12 fee-related
reversal processing acquirer initiated 4-15
creating advices 6-13 definitions 2-5
updating Activity File 6-13 issuer initiated 4-15
, See stand-in processing (STIP) file maintenance 2-5, 4-18
system-generated transaction financial
reversal 4-6 approval response cannot be delivered 4-40
system-generated transactions decline response cannot be delivered 4-41
cash disbursement adjustment 4-8 issuer fails to respond 4-36
reversal 2-3 issuer responds late 4-37
issuer unavailable 4-32
T issuer unavailable, listed on exception file 4-34
network management
testing 3-2
definitions 2-7
transaction
dynamic key exchange 4-29
country 1-27
echo test messages 4-26
counts and amounts, accumulating 8-2
recovery sign-on/off messages 4-27
currency 5-1
sign-on/off messages 4-24
processing charges 1-29
online
routing 7-1
delivery 9-6
transaction sets 2-7 to 2-8
processing 9-5
transactions
online fraud reporting 2-6
adjustment 2-4
Plus shared deposit 2-3
administrative
reconciliation
definitions 2-6
definition 2-5
free-text message 4-20
funds transfer totals message 4-16
funds transfer message 4-22
reconciliation advices 4-17
advice response cannot be delivered 4-42
representment 2-5
alternately-routed 8-6
reversal
ATM cash disbursement 2-2
issuer unavailable 4-43
balance inquiry 6-5
system-generated 2-3, 4-6
cardholder
unsolicited 4-45
account transfer 4-5
split-routed 8-6
balance inquiry 4-3
system-generated
VSDC 2-7
cash disbursement adjustment 4-8
chargeback 2-5

IX-8 Visa Confidential V.I.P. System SMS ATM Processing Specifications 1 June 2018
Index

transfer connectivity 9-3 Area Net Settlement Service 8-5

definition 1-5

U features 8-4
funds transfer 8-7
unsolicited reversal transaction 4-45
illustration 1-6
International Settlement Service 8-5
V National Net Settlement Service 8-5
valuation 8-4 overview 8-4
VIC, See VisaNet Interchange Center (VIC) reports 8-7
Visa Message Gateway 9-1 delivery 8-7
Visa Mobile Prepaid (VMP) 1-26 layouts and formats 8-7
Visa products 1-1 settlement schedule 8-5
Visa Resolve Online 3-3, 9-6 VisaNet VisaNet connection method
Visa Security Module (VSM) 1-12 options 9-2
Visa Smart Debit/Smart Credit (VSDC), description of 1-22 VSDC, See Visa Smart Debit/Smart Credit (VSDC)
VisaNet VSDC transactions 2-7
BASE II System 1-5 VSS, See VisaNet Settlement Service (VSS)
connection methods 1-2
definition of 1-1
systems 1-3
VisaNet connection
file names
raw data 9-3
undifferentiated 9-3
files
delivery options 9-2
transfer connectivity 9-3
types 9-2
pullkey
DBRAW 9-3
UNDIF 9-3
V.I.P. and BASE II components 9-4
V.I.P. and DAS components 9-4
VisaNet connection method
access charges 1-29
requirement for POS—Visa and Visa Electron 3-1
VisaNet Integrated Payment (V.I.P.) System
Common Member Interface (CMI)
illustration 1-7
components
BASE I System 1-3
Common Member Interface (CMI) 1-7
Single Message System (SMS) 1-4
VisaNet Settlement Service (VSS) 1-5
VisaNet Interchange Center (VIC)
description of 1-2
VisaNet Settlement Service (VSS)
alternately routed transactions 8-6

1 June 2018 Visa Confidential V.I.P. System SMS ATM Processing Specifications IX-9