PCI Watch

Tracking changes across the Payment Card Industry

SB nº 157: Changes to EMV® Book C-7, Version 2.4 (Spec Change)

v1.0 Specification Bulletins
Contactless

Draft Specification Bulletin No. 157 First Edition February 2015 Changes to EMV Book C-7, Version 2.4 This Specification Bulletin describes changes to the EMV Contactless Specifications, Book C-7, Version 2.4.

Applicability

This Specification Bulletin applies to: EMV Contactless Specifications for Payment Systems, Book C-7, Kernel 7 Specification, Version 2.4, February 2014

Related Documents

None

Summary

This Specification Bulletin correct the Data Object tag in EMV Book C-7, Version 2.4. This Specification Bulletin clarifies the use of Cryptogram Information Data (CID) ‘9F27’. This Specification Bulletin provides the possibility of switching interface accordingly if fDDA fails or not performed. This Specification Bulletin makes clarifications on data requirements for online message and clearing records defined in Annex C. This Specification Bulletin makes other various clarifications.

http://www.emvco.com.

Specification Change 1. In Table C-1, change the Tag of Terminal Country Code to ‘9F1A’. 2. Use of CID ‘9F27’: - 1) In Table 4-3 and Table 4-4, add new row: Mandatory (M) Tag Optional (O) Conditional (C) Data Element Name “9F27” M Cryptogram Information Data 2) Replace Requirement 4.1.4.4 with the following:

4.1.4.4 The Card’s transaction disposition is included in the Cryptogram Information Data (Tag “9F27”). If the card does not return CID, the Kernel shall:

  • Initialise CID to ‘00’
  • Set CID bits 8-7 to the value of Issuer Application Data(Tag “9F10”) Byte 5 bit 6-5 If the card returns an ARQC (CID bit8-7 = ‘10’), indicting an online transaction is requested. Then the Kernel continues with mandatory-data check for online request, see Error! Reference source not found.. If the card returns an AAC(CID bit8-7=’00’), indicting an offline decline. Then the Kernel continues with mandatory-data check for offline decline, see Error! Reference source not found.. If the card returns a TC (CID bit8-7=’01’), indicting an offline approval. Then the Kernel continues with mandatory-data check for offline approval, see Error! Reference source not found.. 3. Add CTQ Byte 1 bit 5 checking if fDDA fails or not performed. In Request 4.3.2.5, insert the following paragraph before the ‘Else’: Else if the Card Transaction Quality Byte 1 bit 5 =’1’ (Terminate Transaction and swith interface if full transaction flow in contact interface supported.) And the TTQ Byte 1 bit 5 = ‘1’ (Full transaction flow in contact interface Supported) Then the Kernel shall terminate the transaction by providing a Try Another Interface Outcome. http://www.emvco.com. 4. Update the C-1 Table by appending a column describing the requirements of the corresponding data object. The updated table will be: Data element Authorization Tag Source

Requirement

Mode Amount, Authorised (Numeric) ‘9F02’ Terminal Offline and online Mandatory Amount, (Numeric) Other ‘9F03’ Terminal Offline and online Mandatory Application Cryptogram (AC) ‘9F26’ Card Offline and online Mandatory Application Interchange (AIP) Profile ‘82’ Card Offline and online Mandatory Application PAN ‘5A’ Application PAN ‘5F34’ Sequence Number Application Transaction (ATC) Counter ‘9F36’ Card Card Card Offline and online Mandatory Offline and online Conditional, only if the card returns it back to kernel. Offline and online Mandatory Cryptogram ‘9F27’ Information Data (CID) Card Offline and online Mandatory Issuer Application Data ‘9F10’ (IAD) Card Offline and online Mandatory Terminal Capabilities ‘9F33’ Terminal Offline and online Mandatory Terminal Country Code ‘9F1A’ Terminal Offline and online Mandatory

http://www.emvco.com.

Data element Authorization Tag Source Requirement Mode Terminal Verification ‘95’ Results (TVR) Kernel Offline and online ‘00 00 00 00 00’ Track 2 Data Equivalent ‘57’ Card Online Mandatory Transaction Currency ‘5F2A’ Code Terminal Offline and online Mandatory Transaction Date ‘9A’ Terminal Offline and online Mandatory Transaction Type ‘9C’ Terminal Offline and online Mandatory Unpredictable Number ‘9F37’ (UN) Product Identification ‘9F63’ Information Application Version No. ‘9F09’ Track 1 Discretionary ‘9F1F’ Data Terminal Offline and online Mandatory Card Offline and online Conditional, only if the card returns it back to kernel. Terminal Offline and online Optional Card Online Conditional, only if the card returns it back to kernel. 5. Add step to remove Tearing Transaction record if the offline balance has not updated in the matched card. 1) Update Figure 4-4 TTR Processing Flow Chart via adding a box of ‘Remove the Tearing Transaction record if offline balance has not been updated. 2) 4.5.5.6 Attach the following words to ‘Else’ description: the kernel shall remove the Tearing Transaction record. 6. Update Figure 4-4 to be consistent with the request description in 4.5.5.7 on the circumstance under which the returned SW1 SW2 is not ‘9000’ when reading the last record from the card in tearing record recovery. Change the figure with End Application instead of going back to Application Selection in case that non 9000 is returned. 7. Delete original Table 4-6 Data to be Read in Read Application Data. 8. Delete EC Issuer Authentication Code(‘9F74’) from Table A-1 and Table C-1.

http://www.emvco.com.