PayPass M/Chip. Reader Card Application Interface Specification

Transcription

1 PayPass /Chip Reader Card Application Interface Specification Version 2.0 September 2008

2 Proprietary Rights The information contained in this document is proprietary and confidential to astercard International Incorporated, one or more of its affiliated entities (collectively "astercard"), or both. This material may not be duplicated, published, or disclosed, in whole or in part, without the prior written permission of astercard. Trademarks Trademark notices and symbols used in this manual reflect the registration status of astercard trademarks in the United States. Please consult with the Customer Operations Services team or the astercard Law Department for the registration status of particular product, program, or service names outside the United States. All third-party product and service names are trademarks or registered trademarks of their respective owners. edia This document is available in both electronic and printed format. Address astercard Worldwide 2200 astercard Boulevard O'Fallon O USA Version 2.0 September 2008 ii 2008 astercard PayPass /Chip Reader Card Application Interface Specification

3 Table of Contents Table of Contents Using this anual... vii Purpose... vii Scope... vii Audience... vii Related Documentation... viii Reference aterials... ix Abbreviations...x Notational Conventions... xii Transition Flow Diagrams... xiii Document Word Usage... xiii Requirement Numbering... xiv Guidance on Terminology... xiv Document Overview...xv 1 Introduction astercard Proximity Payment /Chip Profile and ag Stripe Profile Architecture Transaction Processing Summary Commands Introduction COPUTE CRYPTOGRAPHIC CHECKSU Definition and Scope Command essage Data Field Returned in the Response essage Status Bytes GENERATE AC Definition and Scope Command essage Data Field Returned in the Response essage Status Bytes GET PROCESSING OPTIONS Definition and Scope Command essage Data Field Returned in the Response essage astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification iii

4 Table of Contents Status Bytes READ RECORD Definition and Scope Command essage Data Field Returned in the Response essage Status Bytes SELECT Definition and Scope Command essage Data Field Returned in the Response essage Status Bytes Application Activation Overview Pre-Processing Protocol Activation Application Selection Building the Candidate List Final Selection PayPass /Chip Transaction Processing Transaction Flow Exception Processing Processing Data Objects Status Bytes COPUTE CRYPTOGRAPHIC CHECKSU Functions Used in Transaction Processing FCI and SW1-SW2 Processing GET PROCESSING OPTIONS Processing Read ag Stripe Application Data ag Stripe Application Version Number Checking COPUTE CRYPTOGRAPHIC CHECKSU Processing Offline Data Authentication ethod Selection Read /Chip Application Data Processing Restrictions Terminal Risk anagement /Chip CV Selection Terminal Action Analysis GENERATE AC Processing Retrieve ICC Key and Verify SDAD (CDA) Static Data Authentication...40 Version 2.0 September 2008 iv 2008 astercard PayPass /Chip Reader Card Application Interface Specification

5 Table of Contents Completion Data Object Handling Data Object Format DOL Handling Bitmaps Used in Discretionary Data Data Object anagement...45 Annex A Data Objects Dictionary astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification v

6

7 Using this anual Purpose Using this anual Purpose astercard PayPass technology enables fast, easy and globally accepted payments through the use of contactless chip technology on the traditional astercard card platform. PayPass /Chip is designed specifically for authorization networks that currently support chip card authorizations for credit or debit applications. This document defines the behavior of the contactless reader used in PayPass /Chip and PayPass ag Stripe transactions. This definition replaces the interface specification given in Part II of the PayPass /Chip Technical Specifications, v1.3. Scope This document provides the specifications necessary to achieve interoperability between PayPass cards and PayPass /Chip readers. It contains the following definitions as applied to both PayPass /Chip and PayPass ag Stripe purchase transactions: The definition of commands, responses and data objects exchanged between the card and PayPass reader The definition of the command sequence in order to support the purchase transaction flow The definition of the internal processing of the PayPass reader Other transaction types (e.g. refunds) may be supported by the PayPass reader however they are not discussed in this document. Audience This document is intended for use by vendors that want to implement the PayPass /Chip application on an acceptance device. This document is also intended for type approval services that test the actual implementations against this specification astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification vii

8 Using this anual Related Documentation Related Documentation For the purposes of developing PayPass readers this specification should be read in conjunction with the following astercard documents: Document astercard PayPass Terminal Implementation Requirements PayPass /Chip Acquirer Implementation Requirements PayPass Performance easurement astercard PayPass Application Note #2, 30 January 2008 Content Lists requirements for reader development and for reader integration in retail systems. Describes the user interface. Lists requirements for acquirers implementing the PayPass /Chip program, including reader/terminal functionality and configuration. Defines the method by which transaction time is measured during the testing of PayPass cards and readers. Lists the minimum performance, in terms of transaction time, required of PayPass cards and readers. The content of this specification overlaps with that of the EV Entry Point Specification. For the purposes of developing PayPass readers, the developer has the option of either Implementing all of the requirements in this document, or Implementing the requirements of the EV Entry Point Specification in place of those given in Chapter 3 of this document. The requirements in the remaining chapters of this document have still to be implemented. The different documents specifying PayPass reader behavior are summarized in the following figure: Version 2.0 September 2008 viii 2008 astercard PayPass /Chip Reader Card Application Interface Specification

9 Using this anual Reference aterials Reference aterials The following references are used in this document. The latest version applies unless a publication date is explicitly stated. [ISO 639-1] Codes for the representation of names and languages Part 1: Alpha-2 Code [ISO ] [ISO 4217] [ISO/IEC 7813] [ISO/IEC ] Codes for the representation of names of countries and their subdivisions Part 1: Country codes Codes for the representation of currencies and funds Identification cards Financial transaction cards Information technology Identification cards Integrated circuit(s) cards with contacts - Part 4: Interindustry commands for interchange [ISO/IEC ] Identification cards Integrated circuit(s) cards with contacts Part 5: Numbering system and registration procedure for application identifiers. [ISO 8583:1987] [ISO 8583:1993] [ISO/IEC 8859] [EV BOOK 1] [EV BOOK 2] [EV BOOK 3] [EV BOOK 4] [EVCLPRO] [EVEPS] [PPTIR] Bank card originated messages Interchange message specifications Content for financial transactions Financial transaction card originated messages Interchange message specifications Information processing 8-bit single-byte coded graphic character sets Integrated Circuit Card Specification for Payment Systems: Application Independent ICC to Terminal Interface Requirements, Version 4.2, June 2008 Integrated Circuit Card Specification for Payment Systems: Security and Key anagement, Version 4.2, June 2008 Integrated Circuit Card Specification for Payment Systems: Application Specification, Version 4.2, June 2008 Integrated Circuit Card Specification for Payment Systems: Cardholder, Attendant and Acquirer Interface Requirements, Version 4.2, June 2008 EV Contactless Specifications for Payment Systems - EV Contactless Communication Protocol Specification, v2.0 EV Contactless Specifications for Payment Systems EV Entry Point Specification, ay 2008 astercard PayPass Terminal Implementation Requirements, Nov astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification ix

10 Using this anual Abbreviations Abbreviations The following abbreviations are used in this specification: Abbreviation AAC AC AFL AID AIP an ans ARQC ATC b BCD C C-APDU CA CDA CDOL CID CLA cn CVC CV CVR DD DDA DF DOL EV FCI IAD ICC INS ISO Lc Le LRC Description Application Authentication Cryptogram Application Cryptogram Application File Locator Application Identifier Application Interchange Profile Alphanumeric Alphanumeric Special Authorization Request Cryptogram Application Transaction Counter Binary Binary Coded Decimal Conditional Command Application Protocol Data Unit Certification Authority Combined DDA/AC Generation Card Risk anagement Data Object List Cryptogram Information Data Class byte of command message Compressed Numeric Card Validation Code Cardholder Verification ethod Cardholder Verification Rule Discretionary Data Dynamic Data Authentication Dedicated File Data Object List Europay astercard Visa File Control Information Issuer Application Data Integrated Circuit Card Instruction byte of command message International Organization for Standardization Number of bytes present in the data field of the C-APDU aximum length of bytes expected in the data field of the R-APDU Longitudinal Redundancy Check Version 2.0 September 2008 x 2008 astercard PayPass /Chip Reader Card Application Interface Specification

11 Using this anual Abbreviations Abbreviation Description andatory n Numeric NATC TRACK1 NATC TRACK2 N CA N I N IC O PAN PCVC3 TRACK1 PCVC3 TRACK2 PDOL PIN PPSE PUNATC TRACK1 PUNATC TRACK2 Track 1 Number of ATC Digits Track 2 Number of ATC Digits Length of the Certification Authority Public Key odulus Length of the Issuer Public Key odulus Length of the ICC Public Key odulus Optional Primary Account Number Track 1 Bitmap for CVC3 Track 2 Bitmap for CVC3 Processing Options Data Object List Personal Identification Number Proximity Payment System Environment Track 1 Bitmap for UN and ATC Track 2 Bitmap for UN and ATC P1 Parameter 1 P2 Parameter 2 R-APDU Response Application Protocol Data Unit RFU Reserved for Future Use RID Registered Application Provider Identifier SDA Static Data Authentication SDAD Signed Dynamic Application Data SSAD Signed Static Application Data SFI Short File Identifier SW1 Status Byte One SW2 Status Byte Two TC Transaction Certificate TLV Tag Length Value TVR Terminal Verification Results UDOL Unpredictable Number Data Object List UN Unpredictable Number var. Variable length 2008 astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification xi

12 Using this anual Notational Conventions Notational Conventions The following notations apply in this document: Notation Description '0' to '9' and 'A' to 'F' Hexadecimal notation. Values expressed in hexadecimal form are enclosed in single quotes (i.e. '_'). 1001b Binary notation. Values expressed in binary form are followed by a lower case "b". digit Any of the ten Arabic numerals from 0 to 9 "/Chip profile is supported" Track 1 Data GENERATE AC Labels for flags, decision outcomes, or individual bits of a data object are enclosed in double quotes. Data object names are written in italics to distinguish them from the text. C-APDUs are written in SALL CAPITALS to distinguish them from the text. The following table lists symbols that are used throughout this document: Symbol k TRACK1 k TRACK2 t TRACK1 t TRACK2 n UN m TRACK1 m TRACK2 q TRACK1 q TRACK2 eaning Number of non-zero bits in the Track 1 Bitmap for UN (Numeric) and ATC (PUNATC TRACK1 ) Number of non-zero bits in the Track 2 Bitmap for UN (Numeric) and ATC (PUNATC TRACK2 ) The symbol t TRACK1 represents the value of NATC TRACK1 and indicates the number of digits of the ATC to be included in the discretionary data field of the Track 1 Data. The symbol t TRACK2 represents the value of NATC TRACK2 and indicates the number of digits of the ATC to be included in the discretionary data field of the Track 2 Data. The symbol n UN represents the number of positions available in the discretionary data fields of the Track 1 Data and Track 2 Data for transporting UN (Numeric) to the issuer. The symbol m TRACK1 indicates the number of characters present in the discretionary data field of the Track 1 Data. The symbol m TRACK2 indicates the number of digits present in the discretionary data field of the Track 2 Data. Number of non-zero bits in the Track 1 Bitmap for CVC3 (PCVC3 TRACK1 ). The symbol q TRACK1 represents the number of CVC3 digits included in the discretionary data field of the Track 1 Data. Number of non-zero bits in the Track 2 Bitmap for CVC3 (PCVC3 TRACK2 ). The symbol q TRACK2 represents the number of CVC3 digits included in the discretionary data field of the Track 2 Data. Version 2.0 September 2008 xii 2008 astercard PayPass /Chip Reader Card Application Interface Specification

13 Using this anual Transition Flow Diagrams Transition Flow Diagrams The following symbols are used in the flow diagrams in this document: The symbols are identified with a number. Paragraphs in the textual description starting with Symbol n correspond to the symbol bearing the same number in the transition flow diagram. The following example illustrates how it works. The decision symbol is used in a flow diagram, identified with number 2. OK TEST 2 NOK An explanation of the check done in symbol 2 is given: Symbol 2 An explanation of how the application checks that the condition is satisfied. Document Word Usage The following words are used often in this manual and have a specific meaning: must Defines a product or system capability that is mandatory. should Defines a product or system capability that is recommended. may Defines a product or system capability that is optional astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification xiii

14 Using this anual Requirement Numbering Requirement Numbering Requirements in this document are uniquely numbered with the number appearing next to each requirement: For example: If the PDOL is not present, the PayPass reader must use a command data field of '8300'. Guidance on Terminology PayPass Card Due to the legacy of the plastic card industry and the fact that the most common PayPass compliant form factor is card based, the term "card" is used frequently throughout this document. However, the contactless nature of PayPass permits noncard form factors. The functionality of PayPass cards and devices is driven by the chip inside and is independent of the form factor in which the chip resides. Therefore the default reference for the consumer token in this document is "PayPass card" or "card", as appropriate. PayPass Reader The term "PayPass reader" is used to refer to the device supporting the PayPass /Chip application and providing the contactless interface used by the PayPass card. Although this can be an integral part of the terminal, it is considered in this specification as a separate logical entity. Terminal The term "terminal" is used in this document to mean the POS device, as distinct from the PayPass reader that provides the contactless interface. The terminal and the PayPass reader may exist in a single integrated device, but are considered separately in this document. astercard In this document, the term "astercard" is used to refer to astercard International Incorporated and/or its affiliated entities. It does not refer to the astercard payment brand. Version 2.0 September 2008 xiv 2008 astercard PayPass /Chip Reader Card Application Interface Specification

15 Using this anual Document Overview Document Overview This document is organized as follows: Section Description 1 Introduction This chapter provides a high-level summary of PayPass /Chip. 2 Commands This chapter defines the commands and responses supported by PayPass /Chip. 3 Application Activation This chapter describes the procedure for identifying and activating the PayPass application on the card, and other transaction pre-processing. 4 PayPass /Chip Transaction Processing This chapter describes the transaction processing of the PayPass reader after it has been enabled by the terminal and the PayPass application has been selected on the card. It specifies how the PayPass reader implements the transaction flow, and lists requirements to ensure interoperability. While other transaction types may be supported, this chapter focuses on the interaction between the PayPass card and the PayPass reader during a purchase transaction. 5 Data Object Handling This chapter defines the data object handling for the PayPass reader. Annex A Data Objects Dictionary This annex lists the data objects supported by the PayPass reader astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification xv

16

17 Introduction astercard Proximity Payment 1 Introduction This chapter provides a high-level summary of PayPass /Chip. 1.1 astercard Proximity Payment astercard has developed a program intended to allow consumers to make payment transactions at point of sale using contactless technology. The generic term "contactless technology" is used when the point of interaction is between 1 mm and 10 m. Although the proximity payment program covers multiple technologies and ranges, this document deals only with the technical specifications of the astercard PayPass product built with a contactless chip with a range from 1 mm to 4 cm. 1.2 /Chip Profile and ag Stripe Profile Within PayPass transactions we distinguish two different profiles: /Chip and ag Stripe. The PayPass ag Stripe profile is designed for contactless payments using authorization networks that currently support only magnetic stripe authorization for credit or debit applications. The PayPass ag Stripe card stores Track 1 Data and Track 2 Data. The PayPass reader fills the discretionary data field with a dynamic CVC3 during each transaction. The dynamic CVC3 is generated by the PayPass ag Stripe card using a secret key and a unique transaction counter provided by the PayPass card, and an unpredictable number generated by the PayPass reader. The PayPass ag Stripe card provides better security than magnetic stripe technology because the dynamic CVC3 is used by the issuer to authenticate the PayPass ag Stripe card during online authorization processing. The PayPass /Chip profile is designed for contactless payments in markets that are oriented towards offline acceptance. To manage the offline risk the PayPass reader performs terminal risk management and offline authentication of the PayPass card. The PayPass /Chip card performs its own card risk management and accepts or declines the transaction offline. To ensure global acceptance of PayPass, unless agreed by astercard: All PayPass /Chip readers support and process PayPass cards that only support the PayPass ag Stripe profile. All PayPass /Chip cards support the PayPass ag Stripe profile when presented at a PayPass ag Stripe only reader astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification 1

18 Introduction Architecture 1.3 Architecture This specification considers the PayPass reader to be a peripheral device of the terminal. The PayPass reader performs the interaction with the PayPass card and the cardholder. The architecture is summarized in Figure 1.1. Figure 1.1 PayPass Terminal-Reader Architecture Note There is no requirement to create devices following the architecture described here. This logical architecture is only used to specify an externally observable behavior. A terminal and PayPass reader integrated in one physical device can also meet the requirements listed in this specification. 1.4 Transaction Processing Summary The processing carried out by the PayPass reader during a PayPass transaction, including the interaction with the PayPass card and with the terminal may be summarized as follows: The terminal enables the PayPass reader and provides the necessary transaction data (e.g. transaction amount). The PayPass reader: o o o Initializes its internal data base and, depending on the transaction amount, sets any internal flags for which the corresponding transaction limit has been exceeded. Creates a list of applications that are supported by both the card and PayPass reader. Picks the highest priority application from the list of mutually supported applications, and selects it on the card. These steps may be done according to [EVEPS] or according to the application activation described in Chapter 3 of this document. The PayPass reader initiates the transaction on the PayPass card. Based on the response from the PayPass card, the PayPass reader continues with either a PayPass ag Stripe or PayPass /Chip transaction. Version 2.0 September astercard 2 PayPass /Chip Reader Card Application Interface Specification

19 Introduction Transaction Processing Summary For a PayPass /Chip transaction, the PayPass reader continues with the following steps: o The PayPass reader determines which form of ODA to perform. o The PayPass reader reads the data records of the PayPass card. o The PayPass reader performs Terminal Risk anagement and Terminal Action Analysis, and selects a cardholder verification method for the transaction. o The PayPass reader requests an application cryptogram from the PayPass card. o The PayPass reader performs offline data authentication as appropriate. For a PayPass ag Stripe transaction, the PayPass reader continues with the following steps: o The PayPass reader reads the data records from the PayPass card. o The PayPass reader issues the COPUTE CRYPTOGRAPHIC CHECKSU command to the PayPass card. o The PayPass reader stores the CVC3-related data in the discretionary data fields of the Track 1 Data and Track 2 Data. If the outcome of the above processing was successful, the reader provides a visible and audible indication of a successful PayPass interaction to the cardholder. The PayPass reader completes the transaction by preparing the necessary Data Record and Transaction Outcome information and returning it to the terminal. If the outcome of the above processing was not successful, the reader, if appropriate, provides an indication of the failure to the cardholder. The PayPass reader either: o o Retries the above processing, or Prepares the necessary Transaction Outcome information and returns it to the terminal. The PayPass reader then hands control back to the terminal. The decision to provide failure indication and either retry or return control to the terminal is implementation dependent. The different stages of the transaction are summarized in Figure astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification 3

20 Introduction Transaction Processing Summary Figure 1.2 Transaction Processing Overview Version 2.0 September astercard 4 PayPass /Chip Reader Card Application Interface Specification

21 Commands Introduction 2 Commands This chapter defines the commands and responses supported by PayPass /Chip. 2.1 Introduction The INS byte of the C-APDU is structured according to [EV BOOK 1]. The coding of INS and its relationship to CLA are shown in Table 2.1. Table 2.1 Coding of the Instruction Byte CLA INS eaning '80' '2A' COPUTE CRYPTOGRAPHIC CHECKSU '80' 'AE' GENERATE AC '80' 'A8' GET PROCESSING OPTIONS '00' 'B2' READ RECORD '00' 'A4' SELECT The status bytes returned by the PayPass card are coded as specified in Section of [EV BOOK 3]. In addition to the status bytes specific for every command, the PayPass card may return the status bytes shown in Table 2.2. Table 2.2 Generic Status Bytes SW1 SW2 eaning '6D' '00' Instruction code not supported or invalid '6E' '00' Class not supported '6F' '00' No precise diagnosis 2008 astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification 5

22 Commands Compute Cryptographic Checksum 2.2 COPUTE CRYPTOGRAPHIC CHECKSU Definition and Scope The COPUTE CRYPTOGRAPHIC CHECKSU command initiates the computation of the dynamic CVC3 on the card. The computation is based on the UN (Numeric) sent by the PayPass reader, the ATC of the PayPass card and the relevant secret key stored in the card. The response of the PayPass card consists of returning the CVC3 TRACK2, the CVC3 TRACK1 (optional) and the ATC to the PayPass reader Command essage The COPUTE CRYPTOGRAPHIC CHECKSU command message is coded according to Table 2.3. Table 2.3 COPUTE CRYPTOGRAPHIC CHECKSU Command essage Code CLA INS P1 P2 Lc Data Le Value '80' '2A' '8E' '80' var. UDOL related data '00' The data field of the command message is coded according to the UDOL following the rules as defined in Section 5.2. If the PayPass card does not have a UDOL, the PayPass reader uses the Default UDOL Data Field Returned in the Response essage The data field of the response message is a constructed data object with tag '77' (Response essage Template). The value field may include several TLV coded data objects, but always includes the CVC3 TRACK2 (tag '9F61') and the ATC (tag '9F36'). The value field may also include the CVC3 TRACK1 (tag '9F60'). Version 2.0 September astercard 6 PayPass /Chip Reader Card Application Interface Specification

23 Commands Generate AC Status Bytes The status bytes that may be sent in response to the COPUTE CRYPTOGRAPHIC CHECKSU command are listed in Table 2.4. Table 2.4 Status Bytes for COPUTE CRYPTOGRAPHIC CHECKSU Command SW1 SW2 eaning '67' '00' Wrong length '69' '85' Conditions of use not satisfied '6A' '86' Incorrect parameters P1-P2 '90' '00' Normal processing 2.3 GENERATE AC Definition and Scope The GENERATE AC command sends transaction-related data to the card, which then computes and returns an Application Cryptogram. Depending on the risk management in the card, the cryptogram returned by the PayPass card may differ from that requested in the command message. The PayPass card may return an AAC (transaction declined), an ARQC (online authorization request) or a TC (transaction approved) Command essage The GENERATE AC command message is coded according to Table 2.5. Table 2.5 GENERATE AC Command essage Code Value CLA '80' INS 'AE' P1 Reference Control Parameter (see Table 2.6) P2 '00' Lc var. Data CDOL related data Le '00' 2008 astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification 7

24 Commands Generate AC Table 2.6 GENERATE AC Reference Control Parameter b8 b7 b6 b5 b4 b3 b2 b1 eaning 0 0 AAC 0 1 TC 1 0 ARQC 1 1 RFU x RFU 0 Other values RFU 0 CDA not requested 1 CDA requested x x x x RFU Other values RFU The data field of the command message is coded according to CDOL1 following the rules as defined in Section Data Field Returned in the Response essage The data field in the response message to the GENERATE AC command is coded according to either format 1 or format 2, as follows. Format 1 In the case of format 1, the data object returned in the response message is a primitive data object with tag equal to '80'. The value field consists of the concatenation without delimiters (tag and length) of the value fields of the data objects specified in Table 2.7. Format 1 is only used if CDA is not performed. Table 2.7 GENERATE AC Response essage Data Field (Format 1) Value CID ATC AC IAD Presence O Version 2.0 September astercard 8 PayPass /Chip Reader Card Application Interface Specification

25 Commands Generate AC Format 2 In the case of format 2, the data object returned in the response message will vary depending on whether CDA was performed or not. CDA Not Performed If CDA is not performed, the data object returned in the response message for an AAC, ARQC or TC is a constructed data object with tag equal to '77', as specified in Table 2.8. Table 2.8 GENERATE AC Response essage Data Field (Format 2) No CDA Tag Value Presence '77' Response essage Template '9F27' CID '9F36' ATC '9F26' AC '9F10' IAD O CDA Performed If CDA is performed, the data object returned in the response message for an ARQC or TC is a constructed data object with tag equal to '77'. It contains at least the three mandatory data objects specified in Table 2.9, and optionally the IAD. Table 2.9 GENERATE AC Response essage Data Field (Format 2) CDA Tag Value Presence '77' Response essage Template '9F27' CID '9F36' ATC '9F4B' SDAD '9F10' IAD O Status Bytes The status bytes that may be sent in response to the GENERATE AC command are listed in Table Table 2.10 Status Bytes for GENERATE AC Command SW1 SW2 eaning '67' '00' Wrong length '69' '85' Conditions of use not satisfied '6A' '86' Incorrect parameters P1-P2 '90' '00' Normal processing 2008 astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification 9

26 Commands Get Processing Options 2.4 GET PROCESSING OPTIONS Definition and Scope The GET PROCESSING OPTIONS command initiates the transaction within the card Command essage The GET PROCESSING OPTIONS command message is coded according to Table Table 2.11 GET PROCESSING OPTIONS Command essage Code CLA INS P1 P2 Lc Data Le Value '80' 'A8' '00' '00' var. PDOL related data '00' The data field of the command message is the Command Template with tag '83' and with a value field coded according to the PDOL provided by the PayPass card in the response to the SELECT command. If the PDOL is not provided by the PayPass card, the length field of the template is set to zero. Otherwise the length field is the total length of the value fields of the data objects transmitted to the card. The value fields are concatenated according to the rules defined in Section Data Field Returned in the Response essage The data field in the response message to the GET PROCESSING OPTIONS command is coded according to either format 1 or format 2, as follows. Format 1 In the case of format 1, the data object returned in the response message is a primitive data object with tag equal to '80'. The value field consists of the concatenation without delimiters (tag and length) of the value fields of the AIP and the AFL, as shown in Table Version 2.0 September astercard 10 PayPass /Chip Reader Card Application Interface Specification

27 Commands Get Processing Options Table 2.12 GET PROCESSING OPTIONS Response essage Data Field (Format 1) Value AIP AFL Presence Format 2 In the case of format 2, the data object returned in the response message is a constructed data object with tag '77' (Response essage Template). The value field may include several TLV coded objects, but always includes the AIP (tag '82') and AFL (tag '94'), as shown in Table Table 2.13 GET PROCESSING OPTIONS Response essage Data Field (Format 2) Tag Value Presence '77' Response essage Template '82' AIP '94' AFL Status Bytes The status bytes that may be sent in response to the GET PROCESSING OPTIONS command are listed in Table Table 2.14 Status Bytes for GET PROCESSING OPTIONS Command SW1 SW2 eaning '67' '00' Wrong length '69' '85' Conditions of use not satisfied '6A' '86' Incorrect parameters P1-P2 '90' '00' Normal processing 2008 astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification 11

28 Commands Read Record 2.5 READ RECORD Definition and Scope The READ RECORD command reads a file record in a linear file. The response of the PayPass card consists of returning the record Command essage The READ RECORD command message is coded according to Table Table 2.15 READ RECORD Command essage Code Value CLA '00' INS 'B2' P1 Record Number P2 See Table 2.16 Lc Not present Data Not present Le '00' Table 2.16 specifies the coding of P2 of the READ RECORD command. Table 2.16 P2 of READ RECORD Command b8 b7 b6 b5 b4 b3 b2 b1 eaning x x x x x SFI P1 is a record number Data Field Returned in the Response essage The data field in the PayPass card response contains the record requested by the command. For SFIs in the range 1-10, the record is a TLV constructed data object with tag '70' as shown in Table Table 2.17 READ RECORD Response essage Data Field '70' Length Record Template Version 2.0 September astercard 12 PayPass /Chip Reader Card Application Interface Specification

29 Commands Select Status Bytes The status bytes that may be sent in response to the READ RECORD command are listed in Table Table 2.18 Status Bytes for READ RECORD Command SW1 SW2 eaning '6A' '82' Incorrect parameters P1 P2; file not found '6A' '83' Incorrect parameters P1 P2; record not found '6A' '86' Incorrect parameters P1 P2 '90' '00' Normal processing 2.6 SELECT Definition and Scope The SELECT command is used to select the PPSE directory and the PayPass application. The response from the PayPass card consists of returning the FCI Command essage The SELECT command message is coded according to Table Table 2.19 SELECT Command essage Code CLA INS P1 P2 Lc Data Le Value '00' 'A4' '04' '00' Length of data field File Name '00' The data field of the command message contains the PPSE directory name ("2PAY.SYS.DDF01") or the ADF Name (or AID) of the application in the PayPass card 1. 1 Depending on the value of the File Name, the SELECT command is referred to as SELECT PPSE or SELECT AID command astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification 13

30 Commands Select Data Field Returned in the Response essage The data field of the response message contains the FCI of the PPSE or PayPass application selected by the command. Select PPSE Table 2.20 defines the FCI returned by a successful selection of the PPSE directory. The FCI contains the list of PayPass applications (ADF Names) supported by the card. Table 2.20 SELECT Response essage Data Field (FCI) of the PPSE Tag Value Presence '6F' FCI Template '84' DF Name 'A5' FCI Proprietary Template 'BF0C' FCI Issuer Discretionary Data The FCI Issuer Discretionary Data is a constructed data object of which the value field is comprised of one or more Application Templates (tag '61') as described in Table Table 2.21 FCI Issuer Discretionary Data 'BF0C' Length '61' Length of directory entry 1 Directory entry 1 '61' Length of directory entry n Directory entry n Each directory entry is the value field of an Application Template and contains the information according to Table 2.22 and Table Table 2.22 Directory Entry Format Tag Value Presence '4F' ADF Name (AID) '87' Application Priority Indicator (see Table 2.23). '50' Application Label O Table 2.23 Application Priority Indicator Format b8 b7-b5 b4-b1 Definition 0 Application may be selected without confirmation of cardholder xxx RFU 000 Other values RFU 0000 No priority assigned xxxx Order in which the application is to be listed or selected, ranging from 1-15, with 1 being the highest priority. Version 2.0 September astercard 14 PayPass /Chip Reader Card Application Interface Specification

31 Commands Select Select PayPass Application Table 2.24 defines the FCI returned in response to a successful selection of a PayPass application. Table 2.24 SELECT Response essage Data Field (FCI) of a PayPass Application Tag Value Presence '6F' FCI Template '84' DF Name (AID) 'A5' FCI Proprietary Template 2 '50' Application Label O '87' Application Priority Indicator O '5F2D' Language Preference O '9F38' PDOL O '9F11' Issuer Code Table Index O '9F12' Application Preferred Name O 'BF0C' FCI Issuer Discretionary Data O 'XXXX' 1 or more additional data objects from application provider, Issuer or ICC supplier O Status Bytes The status bytes returned by the PPSE or PayPass application for the SELECT command are listed in Table Table 2.25 Status Bytes for SELECT Command SW1 SW2 eaning '62' '83' Selected file invalidated 3 '67' '00' Wrong length '6A' '81' Function not supported '6A' '82' File not found '6A' '86' Incorrect parameters P1-P2 '90' '00' Normal processing 2 The FCI Proprietary Template may be empty. In this case the length must be set to zero. 3 These specifications do not specify how to block the PPSE or PayPass application. For a dual-interface card (contact and contactless), this may be done by using the contact interface astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification 15

32

33 Application Activation Overview 3 Application Activation This chapter describes the procedure for identifying and activating the PayPass application on the card, and other transaction pre-processing. 3.1 Overview Application activation begins when the terminal enables the PayPass reader to perform a contactless transaction. Application activation can be divided into the following areas: 1. Pre-processing, in which the transaction amount is checked against defined limits for each supported application 2. Protocol activation, in which contactless protocol of the PayPass reader is activated and prepared for card discovery 3. Application selection, in which first the PPSE and then the PayPass application are selected on the card 3.2 Pre-Processing When the PayPass reader has been enabled by the terminal and the values of the transaction related data objects listed in are defined, then the following steps are performed The PayPass reader must set Transaction CV to "No CV" The PayPass reader must set the Transaction Outcome to "Declined". The following steps are completed for each AID supported by the PayPass reader The PayPass reader must clear the following flags: Terminal Contactless Transaction Limit Exceeded Flag Terminal Contactless Floor Limit Exceeded Flag Terminal CV Required Limit Exceeded Flag If the Amount, Authorized is greater than or equal to the Terminal Contactless Transaction Limit for that AID, then the Terminal Contactless Transaction Limit Exceeded Flag must be set for that AID If the Amount, Authorized is greater than the Terminal Contactless Floor Limit for that AID, then the Terminal Contactless Floor Limit Exceeded Flag must be set for that AID astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification 17

34 Application Activation Protocol Activation If the Amount, Authorized is greater than or equal to the Terminal CV Required Limit for that AID, then the Terminal CV Required Limit Exceeded Flag must be set for that AID. 3.3 Protocol Activation If the PayPass reader has completed pre-processing, and if the Terminal Contactless Transaction Limit Exceeded Flag has not been set for at least one AID supported by the PayPass reader, then the PayPass reader must: Power up the contactless interface and start the polling and collision detection mechanisms as defined in [EVCLPRO]. Provide a visible indication to the cardholder that the reader is active and that the card can be presented. Otherwise, the PayPass reader must not proceed with the rest of application activation. It must instead continue with the Completion function as described in Section Application Selection The application selection process is described in detail in the following sections from the standpoint of both the card and the PayPass reader. The application selection mechanism minimizes the number of commands between the card and PayPass reader. If no errors are encountered, only two SELECT commands (see Section 2.6) are necessary. The process is described in two steps, and is summarized in Figure The PayPass reader selects the PPSE and creates a list of applications that are supported by both the card and the PayPass reader. This list is referred to as the "candidate list" (see Section 3.4.1). 2. From the candidate list, the application to be run is chosen and selected on the card (see Section 3.4.2). Figure 3.1 Application Selection PayPass Card PayPass Reader 1. SELECT PPSE 2. List of AIDs 3. SELECT AID 4. FCI Version 2.0 September astercard 18 PayPass /Chip Reader Card Application Interface Specification

35 Application Activation Application Selection As an alternative to the application selection method described here, the PayPass reader may also support a proprietary application selection method that is outside the scope of this specification. If so, then the proprietary method may be performed either: Immediately prior to step , or Immediately prior to step if the candidate list is empty Building the Candidate List The steps taken by the PayPass reader to establish the candidate list are given in this section The PayPass reader must initialize an empty candidate list The PayPass reader must select the PPSE on the card using the SELECT command as described in Section 2.6. If the card returns status bytes other than '9000', then the PayPass reader must continue with step Otherwise, the PayPass reader must continue with step The PayPass reader must retrieve all the directory entries from the FCI Issuer Discretionary Data (tag 'BF0C') in the FCI returned by the card. Additional tags returned in the FCI that are not listed in Table 2.20 must be discarded by the PayPass reader. The PayPass reader must process each directory entry by comparing the ADF Name in the directory entry with the AIDs supported by the PayPass reader. If the directory entry is not coded according to Table 2.22 then the PayPass reader must ignore the directory entry. If the ADF Name matches the AID of one of the applications supported by the PayPass reader, then the directory entry is added to the candidate list. The ADF Name in the directory entry matches an AID in the PayPass reader if the ADF Name has the same length and value as the AID, or the ADF Name begins with the entire AID The PayPass reader must remove from the candidate list all applications that require cardholder confirmation (b8 = '1' in the Application Priority Indicator (see Table 2.23)) The PayPass reader must remove from the candidate list all applications for which the Terminal Contactless Transaction Limit Exceeded Flag has been set in the preprocessing phase The PayPass reader must order the candidate list according to the following rules: The applications must be listed in order of priority, as indicated by the Application Priority Indicator (see Table 2.23), where the application with the highest priority is listed first. Applications that have the same priority are listed in the order in which they were listed in the PPSE directory entries in the FCI Issuer Discretionary Data (see Table 2.21) astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification 19

36 Application Activation Application Selection Applications with no priority must come last and in the order in which they were listed in the PPSE directory entries in the FCI Issuer Discretionary Data (see Table 2.21) Final Selection If the candidate list is empty, the PayPass reader must set the Transaction Outcome to "End Application" and continue with the Completion function as specified in Section in order to terminate the transaction. Otherwise, the PayPass reader must continue with step The PayPass reader must pick the first application from the candidate list and select this application with a SELECT command coded according to Section using the ADF Name found in the directory entry of the application. If the SELECT command fails (i.e. SW1-SW2 '9000'), then the PayPass reader must remove the application from the candidate list and resume processing at step Having completed application selection, the PayPass reader can begin the main PayPass /Chip Transaction Processing, as described in Chapter 4. Version 2.0 September astercard 20 PayPass /Chip Reader Card Application Interface Specification

37 PayPass /Chip Transaction Processing Transaction Flow 4 PayPass /Chip Transaction Processing This chapter describes the transaction processing of the PayPass reader after it has been enabled by the terminal and the PayPass application has been selected on the card. It specifies how the PayPass reader implements the transaction flow, and lists requirements to ensure interoperability. While other transaction types may be supported, this chapter focuses on the interaction between the PayPass card and the PayPass reader during a purchase transaction. 4.1 Transaction Flow The PayPass reader must execute the transaction flow as described in Figure 4.1 and Figure 4.2, and in the corresponding text below. Note The transaction flow described in Figure 4.1 and Figure 4.2 assumes normal processing without exceptions. Exception processing is described in Section 4.2. Symbol 1 FCI and SW1-SW2 Processing The PayPass reader performs certain checks on the data received in reply to the SELECT AID command as described in Section Symbol 2 GET PROCESSING OPTIONS Command Processing The PayPass reader initiates the transaction by issuing the GET PROCESSING OPTIONS command as described in Section The PayPass card returns the AIP and the AFL. Symbol 3 /Chip profile? The PayPass reader verifies if the "/Chip profile is supported" bit in the AIP is set. If the bit is set, the PayPass reader continues by selecting the method of offline data authentication to be used (see Symbol 7). If the bit is not set, then it continues by reading from the PayPass card the PayPass ag Stripe application data (see Symbol 4). Symbol 4 Read ag Stripe Application Data Based on the AFL previously received from the card, the PayPass reader reads the necessary data using the READ RECORD command as specified in Section Symbol 5 ag Stripe Application Version Number Checking The PayPass reader verifies the compatibility of its application with the PayPass ag Stripe application in the PayPass card as specified in Section astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification 21

38 PayPass /Chip Transaction Processing Transaction Flow Symbol 6 COPUTE CRYPTOGRAPHIC CHECKSU Processing The PayPass reader continues with the COPUTE CRYPTOGRAPHIC CHECKSU command as specified in Section The PayPass reader then sets the Transaction Outcome to "Online Request". Note After the completion of the COPUTE CRYPTOGRAPHIC CHECKSU response, the PayPass card can be removed from the PayPass reader. Symbol 7 Offline Data Authentication ethod Selection The PayPass reader selects the offline data authentication method to be used in the transaction. As described in Section 4.3.6, it compares the functionality available on the card, as indicated in the AIP, with its own capabilities. The result of this process is a decision to perform CDA, SDA or not to perform any offline data authentication. Symbol 8 Read /Chip Application Data The PayPass reader reads the necessary data using READ RECORD commands as specified in Section Symbol 9 Processing Restrictions The PayPass reader performs the Processing Restrictions function as specified in Section This includes application version number checking, application usage control checking and application effective/expiry dates checking. Symbol 10 Terminal Risk anagement The PayPass reader performs Terminal Risk anagement as specified in Section Symbol 11 /Chip CV Selection The PayPass reader selects a cardholder verification method as specified in Section The result of this function is stored as the Transaction CV. Symbol 12 Terminal Action Analysis The PayPass reader performs Terminal Action Analysis in order to decide whether the transaction should be approved offline, declined offline, or transmitted online. The PayPass reader makes this decision based on the content of the TVR, the Issuer Action Codes and Terminal Action Codes as specified in Section Symbol 13 GENERATE AC The PayPass reader issues a GENERATE AC command, as described in Section , requesting a TC, ARQC or an AAC based on the results of Terminal Action Analysis. The PayPass card performs its card risk management when it receives the GENERATE AC command, and may decide to complete the transaction online (ARQC), offline (TC) or decline the transaction (AAC). Note After the completion of the GENERATE AC response, the PayPass card may be removed from the PayPass reader. Version 2.0 September astercard 22 PayPass /Chip Reader Card Application Interface Specification

39 PayPass /Chip Transaction Processing Transaction Flow Symbol 14 Card Generated AAC? If the PayPass reader requested an ARQC or TC, and if the PayPass card has generated an AAC, the PayPass reader sets the Transaction Outcome to "Try Another Interface" and continues with the Completion function. If the PayPass reader requested an AAC, and if the PayPass card has generated an AAC, the PayPass reader sets the Transaction Outcome to "Declined" and continues with the Completion function. Otherwise, the PayPass reader continues by checking if CDA was used in the PayPass card response. Symbol 15 Combined DDA/AC Generation? If CDA is being performed, the PayPass reader continues by retrieving the ICC Public Key from the data read from the PayPass card and by verifying the SDAD. If CDA has not been performed, the PayPass reader continues by verifying that the PayPass card generated an ARQC. Symbol 16 Retrieve ICC Public Key and Verify SDAD (CDA) The PayPass reader retrieves the ICC Public Key and verifies the SDAD generated by the PayPass card as specified in Section Symbol 17 Card Generated ARQC (CDA)? The PayPass reader checks if the card generated an ARQC. If this is the case, the PayPass reader sets the Transaction Outcome to "Online Request" for online capable terminals, and to "Declined" for offline-only terminals. If the PayPass card generated a TC, the PayPass reader sets the Transaction Outcome to "Approved". The PayPass reader continues with the Completion function. Symbol 18 Card Generated ARQC (No CDA)? The PayPass reader checks if the PayPass card generated an ARQC. If this is the case, the PayPass reader sets the Transaction Outcome to "Online Request" for online capable terminals, and to "Declined" for offline-only terminals. The PayPass reader then continues with the Completion function. If the PayPass card generated a TC, the PayPass reader continues by performing SDA. Symbol 19 Static Data Authentication The PayPass reader performs SDA as specified in Section The PayPass reader sets the Transaction Outcome to "Approved". Symbol 20 Completion The PayPass reader executes the Completion function as specified in Section , and hands control back to the terminal astercard Version 2.0 September 2008 PayPass /Chip Reader Card Application Interface Specification 23