CDA CVC3 Instrukcja Użytkownika

MasterCard® PayPass™M/Chip, Acquirer Implementation Requirements v.1-A4 6/06

2. INTRODUCTION 2.3 Implementation Summary Implementing PayPass—M/Chip acceptance is an extension to an acquirer’s existing infrastructure. The follo

. ACQUIRER IMPACTS 3.1 Overview For a general overview of PayPass requirements, services, and products refer to the MasterCard PayPass Product Gu

3. ACQUIRER IMPACTS NOTE Acquirers should note the scope of a vendor’s letter of approval. It may apply only to the reader and not necessarily the re

EMBEDDED READER EXTERNAL READER Figure 2, PayPass Readers 3.3.3 Supporting Other Payment Ac

3. ACQUIRER IMPACTS Required transaction timings may vary significantly depending upon the type of deployment and factors external to the terminal, e

Offline Static Card Authentication Method (CAM) Offline Dynamic CAM SDA DDA* CDA POS with offline capability Mandatory Not Allowed Mandatory PO

3. ACQUIRER IMPACTS The following are required to support this PayPass functionality: • The terminal must maintain a PayPass—M/Chip CVM and receipt l

3.4.6 Fallback for PayPass Transactions The following defines the PayPass requirements for fallback at PayPass terminals. Definition A PayPass fallba

3. ACQUIRER IMPACTS 3.4.8 “Referrals”/”Call Me” Issuer Responses “Referrals”/”Call Me” Issuer responses are not required to be supported by Acquirer

3.5.3 Accepting PayPass—Mag Stripe and Cardholder Devices Acquirers should note that their PayPass—M/Chip terminals will also support PayPass—Mag Str

TABLE OF CONTENTS 1 USING THESE REQUIREMENTS ...

. TERMINAL CONFIGURATION 4.1 PayPass Specific Terminal Data The following sections provide configuration requirements for PayPass—M/Chip terminal

PRODUCT RID PIX PIX EXTENSION APPLICATION LABEL MasterCard A000000004 1010 — “MasterCard” MasterCard with domestic functions A000000004 1010 DC

4. TERMINAL CONFIGURATION NOTE These TACs are specific to PayPass—M/Chip terminals performing PayPass—M/Chip transactions. If the terminal supports c

BYTE BIT MEANING DENIAL ONLINE DEFAULT 4 7 Lower consecutive offline limit exceeded 0 0 0 6 Upper consecutive offline limit exceeded 0

4. TERMINAL CONFIGURATION BYTE BIT MEANING DENIAL ONLINE DEFAULT 2 5 Requested service not allowed for card product 1 0 0 4 New card 0

4.6 Terminal Capabilities The terminal capability (or profile) must be specific to PayPass—M/Chip use. The Terminal Capabilities field is coded accor

4. TERMINAL CONFIGURATION b8 b7 b6 b5 b4 b3 b2 b1 MEANING 0 x x x x x x x Plain-text PIN for ICC verification x 0 x x x x x x Enciphered PI

. NETWORK INTERFACES AND HOST SYSTEMS 5.1 Summary of Changes PayPass transactions at PayPass—M/Chip terminals are indicated by new values in exis

5. NETWORK INTERFACES AND HOST SYSTEMS 5.2 Authorization Requests PayPass authorizations must be processed with the new values defined in Table 9 belo

NOTE The TVR sent to the issuer in clearing messages from offline only terminals may differ from the TVR used in Terminal Action Analysis. This is

Copyright The information contained in this manual is proprietary and confidential to MasterCard International Incorporated (MasterCard) and its Memb

. TESTING 6.1 Testing Overview The MasterCard test process for PayPass—M/Chip is a series of test stages. This chapter summarizes how PayPass—M/Ch

6.4 Test Stages The acquirer test stages for a PayPass—M/Chip implementation are summarized in Table 13. The following sections provide a summary of

6. TESTING 6.6 TIP Acquirers run the tests and then submit log files from the simulators for validation by MasterCard. The TIP is designed to validate

Conditional Offline Clearing Testing Currently, acquirers may choose if they wish to send chip data in clearing messages or not. Acquirers that do de

6. TESTING 6.10 Further Information and Contact Details Queries and further assistance can be obtained from the acquirer’s regional representative or

APPENDICES Appendix A: PayPass Transaction Flows Overview The PayPass—M/Chip terminal transaction flow is based on the EMV 2000 specifications with so

APPENDICES Appendix A, PayPass Transaction Flows, continued Online-Capable Terminal Transaction Flow Figure A-1 shows the transaction flow for a PayP

Offline-Only Terminal Transaction Flow Figure A-2 shows the transaction flow for a PayPass—M/Chip card at an offline-only PayPass—M/Chip terminal. Mo

APPENDICES Appendix A, PayPass Transaction Flows, continued PayPass—Mag Stripe Transaction Flow Figure A-3 shows the transaction flow for a mag strip

Appendix B, Glossary MASTERCARD PAYPASS—M/CHIP, ACQUIRER IMPLEMENTATION REQUIREMENTS v.1-A4 6/06 39 Term Description M/Chip 4 Application The

. USING THESE REQUIREMENTS 1.1 Purpose This document provides guidelines for acquirers implementing the MasterCard PayPass—M/Chip product. These imp

APPENDICES Appendix B, Glossary, continued Term Description PayPass Transaction A payment transaction using PayPass technology for the data exchang

MASTERCARD PAYPASS—M/CHIP, ACQUIRER IMPLEMENTATION REQUIREMENTS v.1-A4 6/06 41

© 2006 MasterCard International Incorporated PayPass-23 v.1-A4 6/06

1.3 Audience This document is intended for use by acquirers implementing MasterCard PayPass acceptance. It is assumed that the audience is already fa

1. USING THESE REQUIREMENTS 1.6 Related Publications The following publications contain material directly related to the contents of this book: 1.

1.8 Abbreviations The following abbreviations are used in these requirements: MASTERCARD PAYPASS—M/CHIP, ACQUIRER IMPLEMENTATION REQUIREMENTS v

1. USING THESE REQUIREMENTS 1.9 Further Information Further information on the above and the overall PayPass program is available in the MasterCard Pa

. INTRODUCTION 2.1 Overview of MasterCard PayPass MasterCard has initiated the development of a program allowing consumers to make MasterCard pa