PCI Watch

Tracking changes across the Payment Card Industry

TTA Bulletin nº 251: Terminal Contact Level 2 Test Cases – 43j Update

v2.0 Type Approval Bulletins
ChipContact Acceptance Device

EMV<sup>®</sup> Terminal Type Approval Bulletin No. 251 Second Edition, November 2021 Terminal Level 2 Test Cases 43j Update

Applicability

This Bulletin applies to:

  • EMV<sup>®</sup> Terminal Type Approval - Level 2 Test Cases – version 4.3j

Related Documents

This Bulletin should be read in conjunction with:

  • EMV<sup>®</sup> Terminal Type Approval - Level 2 Test Cases – version 4.3j

Effective Date

  • 1st January 2022

Description

Based on EMVCo's continued review of the EMVCo Type Approval Terminal Level 2 Test Cases v4.3j, the following updates are necessary, and shall be applied to any type approval session beginning on, or after, the effective date cited above. Update to EMV<sup>®</sup> Terminal Type Approval - Level 2 Test Cases – version 4.3j Section 5.5 - TVR & TSI un setting bits checking Updates TVR TVR Name Related ICS question of the configuration B1b8 B1b7 B1b6 B1b5 B1b4 B1b3 B1b2 B1b1 Offline data authentication was not performed SDA failed ICC data missing Card appears on terminal exception file DDA failed CDA failed SDA Selected RFU SDA and DDA = NO Exception File = NO SDA and DDA = NO CDA = NO SDA and DDA = NO Always set bitmask has the value: 0 1 0 1 1 1 1 1

B2b8 ICC and terminal have 0 different application versions B2b7 Expired application 0 B2b6 Application not yet effective 0 B2b5 Requested service not allowed 0 for card product B2b4 New card Velocity Checking = NO 1 B2b3 RFU Always set 1 B2b2 RFU or Biometric not Biometric = No 1 performed or not successful B2b1 RFU or Biometric template Biometric = No 1 format supported B3b8 Cardholder verification was 0 not successful B3b7 Unrecognised CVM 0 B3b6 PIN Try Limit exceeded Offline Enciphered PIN AND 1 Plaintext PIN = NO B3b5 PIN entry required and PIN 0 pad not present or not working B3b4 PIN entry required, PIN pad Offline Enciphered PIN AND 1 present, but PIN was not Plaintext PIN AND Online entered Enciphered PIN = NO B3b3 Online PIN entered Online Enciphered PIN = NO 1 B3b2 RFU Always set 1 B3b1 RFU Always set 1 B4b8 Transaction exceeds floor limit Floor Limit Checking = NO 1 B4b7 Lower consecutive offline limit Velocity Checking = NO 1 exceeded B4b6 Upper consecutive offline limit Velocity Checking = NO 1 exceeded B4b5 Transaction selected randomly Random Transaction Selection = 1 for online processing NO B4b4 Merchant forced transaction 0 online B4b3 RFU or Biometric Try Limit Biometric = No 1 not exceeded B4b2 RFU or A selected Biometric Biometric = No 1 Type not supported B4b1 RFU Always set 1 B5b8 Default TDOL used Default TDOL = NO 1 B5b7 Issuer authentication failed 0 B5b6 Script processing failed before 0 final GENERATE AC B5b5 Script processing failed after 0 final GENERATE AC B5b4 RFU Always set 1 B5b3 RFU Always set 1 B5b2 RFU Always set 1 B5b1 RFU Always set 1

countries.

Section 7 – Test Cases Updates New test cases include: 2CA.144.00 2CE.003.14 Revised test cases include: 2CA.124.03 2CA.129.00 2CA.129.01 2CA.130.00 Deleted test cases include: None 2CJ.002.12 2CJ.002.13 2CJ.086.05 2CO.034.02 2CO.034.03 2CA.124.03 Application Version Number assigned by the payment system Revision: 43k Objective: To ensure that the terminal maintains the Application Dependent Data for each supported AID(s) assigned by the payment system Reference Book 4 - Section 10.2 - Application Dependent Data EMV 4.3: Terminal ([Online Only AND Normal Default Action processing]) OR [Offline/Online ICS Capable] Options: Conditions:

  • Termsetting1: Terminal is configured at the same time with ‘NbAIDsForTest’ different AIDs and each of them have a set of different data according to table 7 (excluding the following data elements managed at the Terminal Level: Transaction Currency Code, Transaction Currency Exponent, Transaction Reference Currency Code and Transaction Reference Currency Exponent) of section 10.2, Book 4 and for each AID the data values are different. The number of AIDs ‘NbAIDsForTest’ configured in the Terminal depends on the response of the ICS question: ‘How Many AIDs can be supported’= NbMaxAIDs, where NbAIDsForTest=MIN(11, NbMaxAIDs) - Terminal supports AID = B000001234  TAC-Default = 0000000000  TAC-Denial = 0000000000  TAC-Online = 0000000000 - Terminal supports AID = B000001235  TAC-Default = 2000000000  TAC-Denial = 0000000000  TAC-Online = 2000000000 countries. 2CA.124.03 system Application Version Number assigned by the payment - Terminal supports AID = B000001236  TAC-Default = 0080000000  TAC-Denial = 0000000000  TAC-Online = 0080000000 - Terminal supports AID = B000001237  TAC-Default = 0000400000  TAC-Denial = 0000000000  TAC-Online = 0000400000 - Terminal supports AID = B000001238  TAC-Default = 0040000000  TAC-Denial = 0000000000  TAC-Online = 0040000000 - Terminal supports AID = B000001239  TAC-Default = 0020000000  TAC-Denial = 0000000000  TAC-Online = 0020000000 - Terminal supports AID = B000001240  TAC-Default = 0040000000  TAC-Denial = 0000000000  TAC-Online = 0040000000 - Terminal supports AID = B000001241  TAC-Default = 0000000000  TAC-Denial = 0000000000  TAC-Online = 0000000000 - Terminal supports AID = B000001242  TAC-Default = 0080000000  TAC-Denial = 0000000000  TAC-Online = 0080000000 - Terminal supports AID = B000001243  TAC-Default = 0060000000  TAC-Denial = 0000000000  TAC-Online = 0060000000 - Terminal supports AID = B000001244 countries. 2CA.124.03 system Application Version Number assigned by the payment  TAC-Default = 0000000000  TAC-Denial = 0000000000  TAC-Online = 0000000000
  • LT_response at first GENERATE AC - Cryptogram Information Data ‘9F27’ responding an ARQC (‘80’).
  • Issuer_response: - The Issuer does not respond to online processing request. Terminal unable to go Online.
  • Case 01 - LTsetting1:  DF Name = B000001234
  • Case 02 - LTsetting125:  DF Name = B000001235  CVM List is not present in LT
  • Case 03 - LTsetting126:  DF Name = B000001236  ICC Application Version Number does not match Terminal Application Version Number
  • Case 04 - LTsetting127:  DF Name = B000001237  CVM list contain only one rules which is an ‘Unrecognised CVM' = '00000000000000003F00'
  • Case 05 - LTsetting128:  DF Name = B000001238  Application is expired in LT
  • Case 06 - LTsetting129:  DF Name = B000001239  Application is not yet effective in LT
  • Case 07 countries. 2CA.124.03 system Application Version Number assigned by the payment - LTsetting130:  DF Name = B000001240  Application is expired in LT
  • Case 08 - LTsetting131:  DF Name = B000001241
  • Case 09 - LTsetting132:  DF Name = B000001242  ICC Application Version Number does not match Terminal Application Version Number
  • Case 10 - LTsetting133:  DF Name = B000001243  Application is not yet effective in LT Procedure:
  • Case 11 - LTsetting134:  DF Name = B000001244
  • Case 01: Transaction is performed with Termsetting1 and LTsetting1
  • Case 02: Transaction is performed with Termsetting1 and LTsetting125
  • Case 03: Transaction is performed with Termsetting1 and LTsetting126
  • Case 04: Transaction is performed with Termsetting1 and LTsetting127
  • Case 05: Transaction is performed with Termsetting1 and LTsetting128
  • Case 06: Transaction is performed with Termsetting1 and LTsetting129
  • Case 07: Transaction is performed with Termsetting1 and LTsetting130
  • Case 08: Transaction is performed with Termsetting1 and LTsetting131
  • Case 09: Transaction is performed with Termsetting1 and LTsetting132
  • Case 10: Transaction is performed with Termsetting1 and LTsetting133
  • Case 11: Transaction is performed with Termsetting1 and LTsetting134 Pass Criteria:
  • Case 01: - Parameter received at second GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’)
  • Case 02: - Parameter received at second GENERATE AC: countries. 2CA.124.03 system Application Version Number assigned by the payment  The terminal shall process the transaction until completion, by requesting an AAC (P1_b8='0' AND P1_b7=‘0’)
  • Case 03: - Parameter received at second GENERATE AC:  The terminal shall process the transaction until completion, by requesting an AAC (P1_b8='0' AND P1_b7=‘0’)
  • Case 04: - Parameter received at second GENERATE AC:  The terminal shall process the transaction until completion, by requesting an AAC (P1_b8='0' AND P1_b7=‘0’)
  • Case 05: - Parameter received at second GENERATE AC:  The terminal shall process the transaction until completion, by requesting an AAC (P1_b8='0' AND P1_b7=‘0’)
  • Case 06: - Parameter received at second GENERATE AC:  The terminal shall process the transaction until completion, by requesting an AAC (P1_b8='0' AND P1_b7=‘0’)
  • Case 07: - Parameter received at second GENERATE AC:  The terminal shall process the transaction until completion, by requesting an AAC (P1_b8='0' AND P1_b7=‘0’)
  • Case 08: - Parameter received at second GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’)
  • Case 09: - Parameter received at second GENERATE AC:  The terminal shall process the transaction until completion, by requesting an AAC (P1_b8='0' AND P1_b7=‘0’)
  • Case 10: - Parameter received at second GENERATE AC:  The terminal shall process the transaction until completion, by requesting an AAC (P1_b8='0' AND P1_b7=‘0’)
  • Case 11: - Parameter received at second GENERATE AC: countries. 2CA.124.03 system Application Version Number assigned by the payment  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) 2CA.129.00 Tokenisation Data – Data Output Revision: 43k Objective: To ensure that the Kernel outputs the Tokenisation Data Objects returned by LT Reference Book Bulletins - Section SB 178 - Bulletin n 178 - Tokenisation Data Objects – EMV 4.3: Payment Account Reference (PAR) (April 2016), Book Bulletins - Section SB 197 - Bulletin n 197 - Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Terminal [Online Only] OR [Offline/Online Capable] ICS Options: Conditions:
  • LT_response at first GENERATE AC - Cryptogram Information Data ‘9F27’ responding an ARQC (‘80’).
  • Case 01 - LTsetting119:  CDOL2 request the PAR Data Object ('9F24'), the Token Requestor ID Data Object ('9F19') and the Last 4 Digits of PAN Data Object ('9F25').  PAR Data Object ('9F24') has the value = '31303030303030303030303030303030303030303030303030 30303030' and is returned in GPO response
  • Case 02 - LTsetting1:  CDOL2 request the PAR Data Object ('9F24'), the Token Requestor ID Data Object ('9F19') and the Last 4 Digits of PAN Data Object ('9F25'). - LT_response at first GENERATE AC  Response contain tag '9F24' with value '32303030303030303030303030303030303030303030303030 30303030'
  • Case 03 - LTsetting109:  CDOL2 request the PAR Data Object ('9F24'), the Token Requestor ID Data Object ('9F19') and the Last 4 Digits of PAN Data Object ('9F25'). countries. 2CA.129.00 Tokenisation Data – Data Output  An EMV Record (in the SFI range 1 to 10) contains PAR Data Object with the value = '32303030303030303030303030303030303030303030303030 30303030'
  • Case 04 - LTsetting120:  CDOL2 request the PAR Data Object ('9F24'), the Token Requestor ID Data Object ('9F19') and the Last 4 Digits of PAN Data Object ('9F25').  Token Requestor ID Data Object ('9F19') has the value = '000000012345' and is returned in GPO response
  • Case 05 - LTsetting1:  CDOL2 request the PAR Data Object ('9F24'), the Token Requestor ID Data Object ('9F19') and the Last 4 Digits of PAN Data Object ('9F25'). - LT_response at first GENERATE AC  Response contain tag '9F19' with value '000000123456'
  • Case 06 - LTsetting110:  CDOL2 request the PAR Data Object ('9F24'), the Token Requestor ID Data Object ('9F19') and the Last 4 Digits of PAN Data Object ('9F25').  An EMV Record (in the SFI range 1 to 10) contains Token Requestor ID Data Object with the value = '000001234578'
  • Case 07 - LTsetting121:  CDOL2 request the PAR Data Object ('9F24'), the Token Requestor ID Data Object ('9F19') and the Last 4 Digits of PAN Data Object ('9F25').  PAR Data Object ('9F24') has the value = '31303030303030303030303030303030303030303030303030 30303030' and is returned in GPO response  Token Requestor ID Data Object ('9F19') has the value = '000000012345' and is returned in GPO response  Last 4 Digits of PAN Data Object ('9F25') has the value = '1234' and is returned in GPO response
  • Case 08 - LTsetting1: countries. 2CA.129.00 Tokenisation Data – Data Output  CDOL2 request the PAR Data Object ('9F24'), the Token Requestor ID Data Object ('9F19') and the Last 4 Digits of PAN Data Object ('9F25'). - LT_response at first GENERATE AC  Response contain tag '9F24' with value '31303030303030303030303030303030303030303030303030 30303030'  Response contain tag '9F19' with value '000000012345'  Response contain tag '9F25' with value '1234'
  • Case 09 - LTsetting111:  CDOL2 request the PAR Data Object ('9F24'), the Token Requestor ID Data Object ('9F19') and the Last 4 Digits of PAN Data Object ('9F25').  An EMV Record (in the SFI range 1 to 10) contains PAR Data Object with the value = '32303030303030303030303030303030303030303030303030 30303030'  An EMV Record (in the SFI range 1 to 10) contains Token Requestor ID Data Object with the value = '000001234578'  An EMV Record (in the SFI range 1 to 10) contains Last 4 Digits of PAN Data Object with the value = '1234' Procedure:
  • Case 01: Transaction is performed with Termsetting1 and LTsetting119
  • Case 02: Transaction is performed with Termsetting1 and LTsetting1
  • Case 03: Transaction is performed with Termsetting1 and LTsetting109
  • Case 04: Transaction is performed with Termsetting1 and LTsetting120
  • Case 05: Transaction is performed with Termsetting1 and LTsetting1
  • Case 06: Transaction is performed with Termsetting1 and LTsetting110
  • Case 07: Transaction is performed with Termsetting1 and LTsetting121
  • Case 08: Transaction is performed with Termsetting1 and LTsetting1
  • Case 09: Transaction is performed with Termsetting1 and LTsetting111 Pass Criteria:
  • Case 01: - Parameter received at second GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) - Data received at second GENERATE AC:  PAR Data Object (tag 9F24) shall have same value as at Get PROCESSING Option response  Token Requestor ID Data Object (tag 9F19) shall be set to zero  Last 4 Digits of PAN Data Object (tag 9F25) shall be set to zero countries. 2CA.129.00 Tokenisation Data – Data Output - Data received in BDC or ODC message:  PAR Data Object (tag 9F24) shall have same value as at Get PROCESSING Option response
  • Case 02: - Parameter received at second GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) - Data received at second GENERATE AC:  PAR Data Object (tag 9F24) shall have same value as at GENERATE AC 1 response  Token Requestor ID Data Object (tag 9F19) shall be set to zero  Last 4 Digits of PAN Data Object (tag 9F25) shall be set to zero - Data received in BDC or ODC message:  PAR Data Object (tag 9F24) shall have same value as at GENERATE AC 1 response
  • Case 03: - Parameter received at second GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) - Data received at second GENERATE AC:  PAR Data Object (tag 9F24) shall have same value as contained in LT  Token Requestor ID Data Object (tag 9F19) shall be set to zero  Last 4 Digits of PAN Data Object (tag 9F25) shall be set to zero - Data received in BDC or ODC message:  PAR Data Object (tag 9F24) shall have same value as contained in LT
  • Case 04: - Parameter received at second GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) - Data received at second GENERATE AC:  PAR Data Object (tag 9F24) shall be set to zero  Token Requestor ID Data Object (tag 9F19) shall have same value as at Get PROCESSING Option response  Last 4 Digits of PAN Data Object (tag 9F25) shall be set to zero - Data received in BDC or ODC message: countries. 2CA.129.00 Tokenisation Data – Data Output  Token Requestor ID Data Object (tag 9F19) shall have same value as at Get PROCESSING Option response
  • Case 05: - Parameter received at first or second GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) - Data received at second GENERATE AC:  PAR Data Object (tag 9F24) shall be set to zero  Token Requestor ID Data Object (tag 9F19) shall have same value as at GENERATE AC 1 response  Last 4 Digits of PAN Data Object (tag 9F25) shall be set to zero - Data received in BDC or ODC message:  Token Requestor ID Data Object (tag 9F19) shall have same value as at GENERATE AC 1 response
  • Case 06: - Parameter received at second GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) - Data received at second GENERATE AC:  PAR Data Object (tag 9F24) shall be set to zero  Token Requestor ID Data Object (tag 9F19) shall have same value as contained in LT  Last 4 Digits of PAN Data Object (tag 9F25) shall be set to zero - Data received in BDC or ODC message:  Token Requestor ID Data Object (tag 9F19) shall have same value as contained in LT
  • Case 07: - Parameter received at second GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) - Data received at second GENERATE AC:  PAR Data Object (tag 9F24) shall have same value as at Get PROCESSING Option response  Token Requestor ID Data Object (tag 9F19) shall have same value as at Get PROCESSING Option response  Last 4 Digits of PAN Data Object (tag 9F25) shall have same value as at Get PROCESSING Option response countries. 2CA.129.00 Tokenisation Data – Data Output - Data received in BDC or ODC message:  PAR Data Object (tag 9F24) shall have same value as at Get PROCESSING Option response  Token Requestor ID Data Object (tag 9F19) shall have same value as at Get PROCESSING Option response
  • Case 08: - Parameter received at first or second GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) - Data received at second GENERATE AC:  PAR Data Object (tag 9F24) shall have same value as at GENERATE AC 1 response  Token Requestor ID Data Object (tag 9F19) shall have same value as at GENERATE AC 1 response  Last 4 Digits of PAN Data Object (tag 9F25) shall have same value as at GENERATE AC 1 response - Data received in BDC or ODC message:  PAR Data Object (tag 9F24) shall have same value as at GENERATE AC 1 response  Token Requestor ID Data Object (tag 9F19) shall have same value as at GENERATE AC 1 response
  • Case 09: - Parameter received at second GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) - Data received at second GENERATE AC:  PAR Data Object (tag 9F24) shall have same value as contained in LT  Token Requestor ID Data Object (tag 9F19) shall have same value as contained in LT  Last 4 Digits of PAN Data Object (tag 9F25) shall have same value as contained in LT - Data received in BDC or ODC message:  PAR Data Object (tag 9F24) shall have same value as contained in LT  Token Requestor ID Data Object (tag 9F19) shall have same value as contained in LT countries. 2CA.129.01 Tokenisation Data – Data Output (2) Revision: 43k Objective: To ensure that the Kernel outputs the Tokenisation Data Objects returned by LT Reference Book Bulletins - Section SB 178 - Bulletin n 178 - Tokenisation Data Objects – EMV 4.3: Payment Account Reference (PAR) (April 2016), Book Bulletins - Section SB 197 - Bulletin n 197 - Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Terminal [Offline Only] ICS Options: Conditions:
  • Case 01 - LTsetting119:  CDOL1 request the PAR Data Object ('9F24'), the Token Requestor ID Data Object ('9F19') and the Last 4 Digits of PAN Data Object ('9F25').  PAR Data Object ('9F24') has the value = '31303030303030303030303030303030303030303030303030 30303030' and is returned in GPO response
  • Case 02 - LTsetting109:  CDOL1 request the PAR Data Object ('9F24'), the Token Requestor ID Data Object ('9F19') and the Last 4 Digits of PAN Data Object ('9F25').  An EMV Record (in the SFI range 1 to 10) contains PAR Data Object with the value = '32303030303030303030303030303030303030303030303030 30303030'
  • Case 03 - LTsetting120:  CDOL1 request the PAR Data Object ('9F24'), the Token Requestor ID Data Object ('9F19') and the Last 4 Digits of PAN Data Object ('9F25').  Token Requestor ID Data Object ('9F19') has the value = '000000012345' and is returned in GPO response
  • Case 04 - LTsetting110:  CDOL1 request the PAR Data Object ('9F24'), the Token Requestor ID Data Object ('9F19') and the Last 4 Digits of PAN Data Object ('9F25').  An EMV Record (in the SFI range 1 to 10) contains Token Requestor ID Data Object with the value = '000001234578' countries. 2CA.129.01 Tokenisation Data – Data Output (2)
  • Case 05 - LTsetting121:  CDOL1 request the PAR Data Object ('9F24'), the Token Requestor ID Data Object ('9F19') and the Last 4 Digits of PAN Data Object ('9F25').  PAR Data Object ('9F24') has the value = '31303030303030303030303030303030303030303030303030 30303030' and is returned in GPO response  Token Requestor ID Data Object ('9F19') has the value = '000000012345' and is returned in GPO response  Last 4 Digits of PAN Data Object ('9F25') has the value = '1234' and is returned in GPO response
  • Case 06 - LTsetting111:  CDOL1 request the PAR Data Object ('9F24'), the Token Requestor ID Data Object ('9F19') and the Last 4 Digits of PAN Data Object ('9F25').  An EMV Record (in the SFI range 1 to 10) contains PAR Data Object with the value = '32303030303030303030303030303030303030303030303030 30303030'  An EMV Record (in the SFI range 1 to 10) contains Token Requestor ID Data Object with the value = '000001234578'  An EMV Record (in the SFI range 1 to 10) contains Last 4 Digits of PAN Data Object with the value = '1234' Procedure:
  • Case 01: Transaction is performed with Termsetting1 and LTsetting119
  • Case 02: Transaction is performed with Termsetting1 and LTsetting109
  • Case 03: Transaction is performed with Termsetting1 and LTsetting120
  • Case 04: Transaction is performed with Termsetting1 and LTsetting110
  • Case 05: Transaction is performed with Termsetting1 and LTsetting121
  • Case 06: Transaction is performed with Termsetting1 and LTsetting111 Pass Criteria:
  • Case 01: - Parameter received at first GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) - Data received at first GENERATE AC:  PAR Data Object (tag 9F24) shall have same value as at Get PROCESSING Option response  Token Requestor ID Data Object (tag 9F19) shall be set to zero countries. 2CA.129.01 Tokenisation Data – Data Output (2)  Last 4 Digits of PAN Data Object (tag 9F25) shall be set to zero - Data received in BDC or ODC message:  Transaction is approved with a TC: (CID=’40’)  PAR Data Object (tag 9F24) shall have same value as at Get PROCESSING Option response
  • Case 02: - Parameter received at first GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) - Data received at first GENERATE AC:  PAR Data Object (tag 9F24) shall have same value as contained in LT  Token Requestor ID Data Object (tag 9F19) shall be set to zero  Last 4 Digits of PAN Data Object (tag 9F25) shall be set to zero - Data received in BDC or ODC message:  Transaction is approved with a TC: (CID=’40’)  PAR Data Object (tag 9F24) shall have same value as contained in LT
  • Case 03: - Parameter received at first GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) - Data received at first GENERATE AC:  PAR Data Object (tag 9F24) shall be set to zero  Token Requestor ID Data Object (tag 9F19) shall have same value as at Get PROCESSING Option response  Last 4 Digits of PAN Data Object (tag 9F25) shall be set to zero - Data received in BDC or ODC message:  Transaction is approved with a TC: (CID=’40’)  Token Requestor ID Data Object (tag 9F19) shall have same value as at Get PROCESSING Option response
  • Case 04: - Parameter received at first GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) - Data received at first GENERATE AC: countries. 2CA.129.01 Tokenisation Data – Data Output (2)  PAR Data Object (tag 9F24) shall be set to zero  Token Requestor ID Data Object (tag 9F19) shall have same value as contained in LT  Last 4 Digits of PAN Data Object (tag 9F25) shall be set to zero - Data received in BDC or ODC message:  Transaction is approved with a TC: (CID=’40’)  Token Requestor ID Data Object (tag 9F19) shall have same value as contained in LT
  • Case 05: - Parameter received at first GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) - Data received at first GENERATE AC:  PAR Data Object (tag 9F24) shall have same value as at Get PROCESSING Option response  Token Requestor ID Data Object (tag 9F19) shall have same value as at Get PROCESSING Option response  Last 4 Digits of PAN Data Object (tag 9F25) shall have same value as at Get PROCESSING Option response - Data received in BDC or ODC message:  Transaction is approved with a TC: (CID=’40’)  PAR Data Object (tag 9F24) shall have same value as at Get PROCESSING Option response  Token Requestor ID Data Object (tag 9F19) shall have same value as at Get PROCESSING Option response
  • Case 06: - Parameter received at first GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) - Data received at first GENERATE AC:  PAR Data Object (tag 9F24) shall have same value as contained in LT  Token Requestor ID Data Object (tag 9F19) shall have same value as contained in LT  Last 4 Digits of PAN Data Object (tag 9F25) shall have same value as contained in LT - Data received in BDC or ODC message:  Transaction is approved with a TC: (CID=’40’) countries. 2CA.129.01 Tokenisation Data – Data Output (2)  PAR Data Object (tag 9F24) shall have same value as contained in LT  Token Requestor ID Data Object (tag 9F19) shall have same value as contained in LT countries. 2CA.130.00 Tokenisation Data in INTERNAL AUTHENTICATE Revision: 43k Objective: To ensure that the Kernel outputs the Tokenisation Data Objects returned by LT Reference Book Bulletins - Section SB 178 - Bulletin n 178 - Tokenisation Data Objects – EMV 4.3: Payment Account Reference (PAR) (April 2016), Book Bulletins - Section SB 197 - Bulletin n 197 - Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Terminal [DDA] ICS Options: Conditions:
  • LTsetting112: - AIP indicates DDA only is supported - CDOL1 request the PAR Data Object ('9F24'), the Token Requestor ID Data Object ('9F19') and the Last 4 Digits of PAN Data Object ('9F25').
  • Case 01 - LT_response at INTERNAL AUTHENTICATE  Response contain tag '9F24' with value '31303030303030303030303030303030303030303030303030 30303030'
  • Case 02 - LT_response at INTERNAL AUTHENTICATE  Response contain tag '9F19' with value '000000012345' Procedure:
  • Case 03 - LT_response at INTERNAL AUTHENTICATE  GET Processing Response contain tag '9F24' with value '31303030303030303030303030303030303030303030303030 30303030'  Response contain tag '9F19' with value '000000012345'  Response contain tag '9F25' with value '1234'
  • Case 01: Transaction is performed with Termsetting1 and LTsetting112
  • Case 02: Transaction is performed with Termsetting1 and LTsetting112
  • Case 03: Transaction is performed with Termsetting1 and LTsetting112 Pass Criteria:
  • Case 01: - Parameter received at first or second GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) - Data received at first GENERATE AC: countries. 2CA.130.00 Tokenisation Data in INTERNAL AUTHENTICATE  PAR Data Object (tag 9F24) shall have same value as at INTERNAL AUTHENTICATE response  Token Requestor ID Data Object (tag 9F19) shall be set to zero  Last 4 Digits of PAN Data Object (tag 9F25) shall be set to zero - Data received in BDC or ODC message:  PAR Data Object (tag 9F24) shall have same value as at INTERNAL AUTHENTICATE response
  • Case 02: - Parameter received at first or second GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) - Data received at first GENERATE AC:  PAR Data Object (tag 9F24) shall be set to zero  Token Requestor ID Data Object (tag 9F19) shall have same value as at INTERNAL AUTHENTICATE response  Last 4 Digits of PAN Data Object (tag 9F25) shall be set to zero - Data received in BDC or ODC message:  Token Requestor ID Data Object (tag 9F19) shall have same value as at INTERNAL AUTHENTICATE response
  • Case 03: - Parameter received at first or second GENERATE AC:  The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) - Data received at first GENERATE AC:  PAR Data Object (tag 9F24) shall have same value as at INTERNAL AUTHENTICATE response  Token Requestor ID Data Object (tag 9F19) shall have same value as at INTERNAL AUTHENTICATE response  Last 4 Digits of PAN Data Object (tag 9F25) shall have same value as at INTERNAL AUTHENTICATE response - Data received in BDC or ODC message:  PAR Data Object (tag 9F24) shall have same value as at INTERNAL AUTHENTICATE response  Token Requestor ID Data Object (tag 9F19) shall have same value as at INTERNAL AUTHENTICATE response countries. 2CA.144.00 Cardholder Name Data Element Revision: 43k Objective: To ensure that the terminal accepts the Cardholder name with value 202F. Reference Book 3 - Section 5.2 - Data Objects EMV 4.3: Terminal [NA] ICS Options: Conditions:
  • Case 01 - LTsetting100:  Cardholder Name has the value = '202F'
  • Case 02 - LTsetting101:  Cardholder Name has the value = '4E414D202F'
  • Case 03 - LTsetting102:  Cardholder Name has the value = '4E414D453132333435202F'
  • Case 04 - LTsetting103:  Cardholder Name has the value = '4E414D45313233343537383930202F'
  • Case 05 - LTsetting104:  Cardholder Name has the value = '4E414D45313233343537383930204E414D45202F'
  • Case 06 - LTsetting105:  Cardholder Name has the value = '202F' and is returned in GPO response  Cardholder Name is not present in AEF record
  • Case 07 - LTsetting114:  Cardholder Name has the value = '4E414D202F' and is returned in GPO response  Cardholder Name is not present in AEF record
  • Case 08 - LTsetting115: countries. 2CA.144.00 Cardholder Name Data Element  Cardholder Name has the value = '4E414D453132333435202F' and is returned in GPO response  Cardholder Name is not present in AEF record
  • Case 09 - LTsetting116:  Cardholder Name has the value = '4E414D45313233343537383930202F' and is returned in GPO response  Cardholder Name is not present in AEF record Procedure:
  • Case 10 - LTsetting117:  Cardholder Name has the value = '4E414D45313233343537383930204E414D45202F' and is returned in GPO response  Cardholder Name is not present in AEF record
  • Case 01: Transaction is performed with Termsetting1 and LTsetting100
  • Case 02: Transaction is performed with Termsetting1 and LTsetting101
  • Case 03: Transaction is performed with Termsetting1 and LTsetting102
  • Case 04: Transaction is performed with Termsetting1 and LTsetting103
  • Case 05: Transaction is performed with Termsetting1 and LTsetting104
  • Case 06: Transaction is performed with Termsetting1 and LTsetting105
  • Case 07: Transaction is performed with Termsetting1 and LTsetting114
  • Case 08: Transaction is performed with Termsetting1 and LTsetting115
  • Case 09: Transaction is performed with Termsetting1 and LTsetting116
  • Case 10: Transaction is performed with Termsetting1 and LTsetting117 Pass Criteria:
  • Parameter received at first or second GENERATE AC: - The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’)
  • Case 01: - Data received in BDC or ODC message:  Cardholder Name has the value = '202F'
  • Case 02: - Data received in BDC or ODC message:  Cardholder Name has the value = '4E414D202F'
  • Case 03: - Data received in BDC or ODC message:  Cardholder Name has the value = '4E414D453132333435202F' countries. 2CA.144.00 Cardholder Name Data Element
  • Case 04: - Data received in BDC or ODC message:  Cardholder Name has the value = '4E414D45313233343537383930202F'
  • Case 05: - Data received in BDC or ODC message:  Cardholder Name has the value = '4E414D45313233343537383930204E414D45202F'
  • Case 06: - Data received in BDC or ODC message:  Cardholder Name has the value = '202F'
  • Case 07: - Data received in BDC or ODC message:  Cardholder Name has the value = '4E414D202F'
  • Case 08: - Data received in BDC or ODC message:  Cardholder Name has the value = '4E414D453132333435202F'
  • Case 09: - Data received in BDC or ODC message:  Cardholder Name has the value = '4E414D45313233343537383930202F'
  • Case 10: - Data received in BDC or ODC message:  Cardholder Name has the value = '4E414D45313233343537383930204E414D45202F' countries. 2CC.014.03 Retrieving CA Public Key used to Perform PIN Encryption: Key absent Revision: 43k Objective: To ensure that if the terminal supports Offline PIN Encryption, and if no Certification Authority Public Keys is available for a given RID and Certification Authority Public Key Index, the terminal fails the PIN Encryption process. Reference Book 2 - Section 6.2 - Retrieval of Certification Authority Public Key EMV 4.3: Terminal [Offline Enciphered PIN] ICS Options: Conditions:
  • LTsetting118: - AIP of LT indicates Cardholder Verification is supported - CDOL1 request the CVM Result ('9F34'). - CVM List has the value '00000000000000000400', Enciphered PIN verification Offline, Always - CA Public Key Index in ICC is not supported by the Terminal Procedure:
  • Transaction is performed with Termsetting1 and LTsetting118 Pass Criteria:
  • Parameter received at first or second GENERATE AC: - The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’)
  • Data received at first GENERATE AC: - Cardholder verification was not successful (TVR_B3b8=‘1’) - PIN entry required, PIN pad present, but PIN was not entered is not used (TVR_B3b4=‘0’) - PIN entry required and PIN pad present or working (TVR_B3b5=‘0’) - PIN Try Limit not exceeded (TVR_B3b6=‘0’) - Cardholder verification was performed (TSI_B1b7='1') - CVM Result = 04 00 01 countries. 2CE.003.14 Acceptance of format errors for Selection - List of AIDs Revision: 43k Objective: The terminal accepts application selection data objects from the ICC with data wrongly located, when processing List of AIDs Reference Book 1 - Section 12.2.4 - Error Handling for FCI Response Data, Book 1 - EMV 4.3: Section 12.3.3 - Using a List of AIDs, Book 3 - Section 7.5 – Erroneous or Missing Data in the ICC Terminal [NA] ICS Options: Conditions:
  • Case 01 - LTsetting106:  FCI Issuer Discretionary Template contains the Application Label '50' with value '454D56436F2546573746'
  • Case 02 - LTsetting106:  FCI Issuer Discretionary Template contains the Application Label '50' with value '454D56436F2546573746' - LT_response at FINAL SELECT  FCI Template is correctly formatted with Application Label located under FCI Proprietary Template Procedure:
  • Case 03 - LT_response at FINAL SELECT  FCI Template is incorrectly formatted with Application Label located under FCI Issuer Discretionary Template
  • Case 01: Transaction is performed with Termsetting1 and LTsetting106
  • Case 02: Transaction is performed with Termsetting1 and LTsetting106
  • Case 03: Transaction is performed with Termsetting1 and LTsetting1 Pass Criteria:
  • Parameter received at first or second GENERATE AC: - The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’) countries. 2CJ.002.12 All bits in TSI and TVR are set to 0b (13) Revision: 43k Objective: To ensure that all TVR and TSI bits are set to 0b when the terminal starts the transaction. Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.3: Terminal [Attended] AND [Forced Online] AND ([Offline/Online Capable] OR [Online ICS Only]) Options: Conditions:
  • Transaction 01: A first transaction is performed raising the TVR bits: Byte 2 bit 8 to 5 (ICC have different application version, Expired Application, Application not yet effective, Requested service not allowed for card product), Byte 3 bit 8 to 7 (Cardholder verification not successful, Unrecognised CVM) Byte 4 bit 4 (Merchant forced transaction online) and raising the TSI bits: Byte 1 bit 7, 6 (Cardholder verification was performed, Card risk management was performed) - Termsetting1: - Transaction Date set between 200101 and 480101 (current local date of testing) - LTsetting108:  Expiration Date has the value '200101'  Effective Date has the value '480101'  Application Version Number has the value '02'  Application Usage Control has the value '0000'  CVM List has the value '00000000000000003F00'  IAC-Online has the value '0040000000' - Action:  Transaction forced online
  • Transaction 02: A second transaction is performed correctly and the PDOL request the TVR and TSI - LTsetting1:  PDOL is present in LT and request the TVR and TSI Procedure:
  • Transaction 01: Transaction is performed with Termsetting1 and LTsetting108
  • Transaction 02: Transaction is performed with Termsetting1 and LTsetting1 Pass Criteria:
  • Transaction 01: - Data received at first GENERATE AC:  ICC and terminal have different application versions (TVR_B2b8=‘1’) countries. 2CJ.002.12 All bits in TSI and TVR are set to 0b (13)  Expired application (TVR_B2b7=‘1’)  Application not yet effective (TVR_B2b6=‘1’)  Requested service not allowed for card product (TVR_B2b5=‘1’)  Cardholder verification was not successful (TVR_B3b8=‘1’)  Unrecognised CVM (TVR_B3b7=‘1’)  Cardholder verification was performed (TSI_B1b7='1') - Data received at second GENERATE AC:  Card risk management was performed (TSI_B1b6='1') - Data received in BDC or ODC message:  Transaction is approved with a TC: (CID=’40’)
  • Transaction 02: - Data received at Get Processing Options:  All TVR bits are set to zero  All TSI bits are set to zero countries. 2CJ.002.13 All bits in TSI and TVR are set to 0b (14) Revision: 43k Objective: To ensure that all TVR and TSI bits are set to 0b when the terminal starts the transaction. Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.3: Terminal [Online Enciphered PIN] ICS Options: Conditions:
  • Transaction 01: A first transaction is performed raising the TVR bits: Byte 2 bit 8 to 5 (ICC have different application version, Expired Application, Application not yet effective, Requested service not allowed for card product), Byte 3 bit 3 (Online PIN entered) and Byte 5 bit 6 to 5 (Script processing failed before final GENERATE AC, Script processing failed after final GENERATE AC) and raising the TSI bits: Byte 1 bit 7 to 6, 3 (Cardholder verification was performed, script processing was performed) - LTsetting107:  Expiration Date has the value '200101'  Effective Date has the value '480101'  Application Version Number has the value '02'  Application Usage Control has the value '0000'  CVM List has the value '00000000000000000203'  IAC-Online has the value '0040000000' - Action:  Enter correct PIN = 1234 - LT_response at All Script commands  SW1SW2: 6281 - Issuer_response:  Issuer Script '71' contain one Issuer Script Command  Issuer Script '72' contain one Issuer Script Command
  • Transaction 02: A second transaction is performed correctly and the PDOL request the TVR and TSI - LTsetting1:  PDOL is present in LT and request the TVR and TSI Procedure:
  • Transaction 01: Transaction is performed with Termsetting1 and LTsetting107
  • Transaction 02: Transaction is performed with Termsetting1 and LTsetting1 countries. 2CJ.002.13 Pass Criteria: All bits in TSI and TVR are set to 0b (14)
  • Transaction 01: - Data received at first GENERATE AC:  ICC and terminal have different application versions (TVR_B2b8=‘1’)  Expired application (TVR_B2b7=‘1’)  Application not yet effective (TVR_B2b6=‘1’)  Requested service not allowed for card product (TVR_B2b5=‘1’)  Online PIN entered (TVR_B3b3=‘1’)  Cardholder verification was performed (TSI_B1b7='1') - Data received at second GENERATE AC:  Script processing failed before final GENERATE AC (TVR_B5b6=‘1’)  Script processing was performed (TSI_B1b3='1') - Data received in BDC or ODC message:  Script processing failed after final GENERATE AC (TVR_B5b5=‘1’)
  • Transaction 02: - Data received at Get Processing Options:  All TVR bits are set to zero  All TSI bits are set to zero countries. 2CJ.086.05 Cardholder Verification Rule for cash transactions not satisfied, transaction type (05) Revision: 43k Objective: When a cash cardholder verification rule is not satisfied based on transaction type, the terminal bypasses the rule and proceeded to the next rule. Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.3: Terminal [Unattended] AND [ATM] AND ([Cashback] OR [Goods] OR [Services] OR ICS [Inquiry] OR [Transfer] OR [Payment] OR [Administrative] OR [CashDeposit]) Options: Conditions:
  • LTsetting113: - CVM List has the value '000000000000000000010000' (Fail CVM, if unattended cash, followed by Fail CVM, always). Procedure:
  • Action: - Set Transaction Type to Not Cash
  • Transaction is performed with Termsetting1 and LTsetting113 Pass Criteria:
  • Parameter received at first or second GENERATE AC: - The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’)
  • Data received at first GENERATE AC: - Cardholder verification failed (TVR_B3b8=‘1’) - Cardholder verification was performed (TSI_B1b7='1') - CVM Results = '00 00 01' or ’00 01 01’ countries. 2CO.034.02 Terminal Terminates Processing of Issuer Script exceeding device limit (1) Revision: 43k Objective: To ensure that the terminal terminates the processing of an issuer script when exceeding the device limit. Reference Book 4 - Section 6.3.9 - Issuer-to-Card Script Processing, Book 4 - Section EMV 4.3: 12.2.4 - Script Incidents Terminal ([Online Only] OR [Offline/Online Capable]) AND [Device Script Limit not ICS unlimited] Options: Conditions:
  • LT_response at first GENERATE AC - Cryptogram Information Data ‘9F27’ responding an ARQC (‘80’). Procedure:
  • Issuer_response: - Issuer Script Response contains a minimum of two '71' scripts where the sum length exceeds the device limit during the last script (typically 128 bytes or value provided in the ICS)
  • Transaction is performed with Termsetting1 and LTsetting1 Pass Criteria:
  • Parameter received at second GENERATE AC: - The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’)
  • Data received at second GENERATE AC: - Script processing failed before final GENERATE AC (TVR_B5b6=‘1’) - Script processing was performed (TSI_B1b3='1')
  • Data received in BDC or ODC message: - No Script processing failed after GENERATE AC (TVR_B5b5=‘0’) - First Issuer Script Results = 20 yy yy yy yy - Last Issuer Script Results = 00 xx xx xx xx countries. 2CO.034.03 Terminal Terminates Processing of Issuer Script exceeding device limit (2) Revision: 43k Objective: To ensure that the terminal terminates the processing of an issuer script when exceeding the device limit. Reference Book 4 - Section 6.3.9 - Issuer-to-Card Script Processing, Book 4 - Section EMV 4.3: 12.2.4 - Script Incidents Terminal ([Online Only] OR [Offline/Online Capable]) AND [Device Script Limit not ICS unlimited] Options: Conditions:
  • LT_response at first GENERATE AC - Cryptogram Information Data ‘9F27’ responding an ARQC (‘80’). Procedure:
  • Issuer_response: - Issuer Script Response contains a minimum of two '72' scripts where the sum length exceeds the device limit during the last script (typically 128 bytes or value provided in the ICS)
  • Transaction is performed with Termsetting1 and LTsetting1 Pass Criteria:
  • Parameter received at second GENERATE AC: - The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’)
  • Data received in BDC or ODC message: - No Script processing failed before final GENERATE AC (TVR_B5b6=‘0’) - Script processing failed before after GENERATE AC (TVR_B5b5=‘1’) - Script processing was performed (TSI_B1b3='1') - First Issuer Script Results = 20 yy yy yy yy - Last Issuer Script Results = 00 xx xx xx xx countries. Annex B – Terminal Settings [Termsetting1] Data Transaction Date AID Application Version Number TAC-Default TAC-Denial TAC-Online AID Application Version Number TAC-Default TAC-Denial TAC-Online AID TAC-Default TAC-Denial TAC-Online AID TAC-Default TAC-Denial TAC-Online AID TAC-Default TAC-Denial TAC-Online AID TAC-Default TAC-Denial TAC-Online AID TAC-Default TAC-Denial TAC-Online AID TAC-Default TAC-Denial TAC-Online AID Tag (if any) 9A 9F06 9F09 9F06 9F09 9F06 9F06 9F06 9F06 9F06 9F06 9F06 Value Current Date B000001234 0001 0000000000 0000000000 0000000000 B000005678 0001 0000000000 0000000000 0000000000 B000001235 2000000000 0000000000 2000000000 B000001236 0080000000 0000000000 0080000000 B000001237 0000400000 0000000000 0000400000 B000001238 0040000000 0000000000 0040000000 B000001239 0020000000 0000000000 0020000000 B000001240 0040000000 0000000000 0040000000 B000001241 countries. TAC-Default TAC-Denial TAC-Online AID TAC-Default TAC-Denial TAC-Online AID TAC-Default TAC-Denial TAC-Online AID TAC-Default TAC-Denial TAC-Online 9F06 9F06 9F06 - 0000000000 0000000000 0000000000 B000001242 0080000000 0000000000 0080000000 B000001243 0060000000 0000000000 0060000000 B000001244 0000000000 0000000000 0000000000 countries. Annex C – LT Settings LT functional default behaviour: Excepted if otherwise stated in test cases, all LTsettings shall react as follow (simulating NO CRM functions): - GPO Command: LT response is correctly formatted in template 77, without additional data, - Verify Command: LT response is correctly formatted (with the internal check PIN according to LTsetting value) - Read Record: LT response are correctly formatted with the records according to the concerned LTsetting. - GENERATE AC: LT response is correctly formatted in template 77, without additional data
  • With CDA signature if required in command message)
  • With the AC Cryptogram requested in the command message (same CID as the one requested in the command message) Also, Issuer Simulator must responds ‘online accepted’ by default except if otherwise stated in the test cases [LTSetting1] Data Application Interchange Profile Application File Locator IAC-Denial IAC-Online IAC-Default CA Public Key Index FCI Template (Select AID): ‘6F’ ‘84’ (DF Name) ‘B000001234’ ‘A5’ ‘50’ (Label) ‘E454D56436F254657374’ ‘9F38’ (PDOL) ‘95059B029F3303’ AEF 01: - Record 01: '70’ ‘5F24’ (Expiration Date) ‘480101’ ‘5A’ (PAN) ‘xxxxxx1234x’ - Record 02: '70’ Tag 82 94 9F0F 9F0D 9F0E 8F Value 7D00 080102011001010 0 0000000000 0000000000 0000000000 01 countries. ‘9F0E’ (IAC-Denial) ‘0000000000’ ‘9F0F’ (IAC-Online) ‘0000000000’ ‘9F0D’ (IAC-Default) ‘0000000000’ ‘8C’ (CDOL1) ‘95059B029F241D9F19069F25029F34039F3704’ ‘8D’ (CDOL2) ‘95059B029F241D9F19069F25029F34039F3704’ ‘9F08’ (Version) ‘01’ ‘8E’ (CVM List) ‘TBD’ ‘9F07’ (AUC) ‘ FFC0’ ‘5F20’ (Cardholder Name) ‘4E414D453132333435’ Xxxx (ALL data will be defined) AEF 02: - Record 01: '70’ ‘8F’ (CA Public Key Index in ICC) ‘01’ ‘90’ (Issuer Public Key Certificate) ‘TBD01’ ‘9F46’ (ICC Public Key Certificate) ‘TBD01’ ‘92’ (Issuer Public Key Remainder’) ‘TBD01’ ‘9F48’ (ICC Public Key Remainder’) ‘TBD01’ ‘9F32’ (Issuer Public Key Exponent’) ‘TBD01’ ‘9F47’ (ICC Public Key Exponent’) ‘TBD01’ ‘93’ (Signed Static Application Data) ‘TBD01’ ‘9F49’ (DDOL)’ ‘9F3704’ ICC Private Key PIN TBD01 ‘1234’ [LTSetting100] (differences with LTSetting1) Data Cardholder Name [LTSetting101] (differences with LTSetting1) Data Cardholder Name [LTSetting102] (differences with LTSetting1) Data Cardholder Name [LTSetting103] (differences with LTSetting1) Tag 5F20 Tag 5F20 Value 202F Tag 5F20 Value 43414D202F Value 4E414D453132333435202F countries. Data Cardholder Name [LTSetting104] (differences with LTSetting1) Data Cardholder Name Tag 5F20 [LTSetting105] (differences with LTSetting1) Data Cardholder Name Cardholder Name in GPO response Tag 5F20 5F20 [LTSetting106] (differences with LTSetting1) Data FCI Template (Select AID): ‘6F’ ‘84’ (DF Name) ‘B000001234’ ‘A5’ ‘9F38’ (PDOL) ‘95059B02’ ‘BF0C’ ‘50’ (Label) ‘’EMVCo Test’ Tag 5F20 Value 4E414D45313233343537383930202F Value 4E414D45313233343537383930204E414D45202F Value TLV not present in record 202F Tag Value 4 [LTSetting107] (differences with LTSetting1): Data Expiration Date Effective Date Application Version Number Application Usage Control CVM List IAC-Online [LTSetting108] (differences with LTSetting1): Data Expiration Date Effective Date Application Version Number Tag 5F24 5F25 9F09 9F07 8E 9F0F Value 200101 480101 02 0000 000000000203 0040000000 Tag 5F24 5F25 9F09 Value 200101 480101 02 countries. Application Usage Control CVM List IAC-Online 9F07 8E 9F0F 0000 000000003F00 0040000000 [LTSetting109] (differences with LTSetting1): Data AEF 01: Record 02: Tag Value '70’ ‘9F0E’ (IAC-Denial) ‘0000000000’ ‘9F0F’ (IAC-Online) ‘0000000000’ ‘9F0D’ (IAC-Default) ‘0000000000’ ‘8C’ (CDOL1) ‘95059B029F241D9F19069F25029F3403’ ‘8D’ (CDOL2) ‘95059B029F241D9F19069F25029F3403’ ‘9F08’ (Version) ‘01’ ‘8E’ (CVM List) ‘TBD’ ‘9F07’ (AUC) ‘ FFC0’ ‘5F20’ (Cardholder Name) ‘4E414D453132333435’ Xxxx (ALL data will be defined) ‘9F24’ (PAR) ‘3230303030303030303030303030303030303030303030303030303030’ [LTSetting110] (differences with LTSetting1): Data AEF 01: Record 02: '70’ ‘9F0E’ (IAC-Denial) ‘0000000000’ ‘9F0F’ (IAC-Online) ‘0000000000’ ‘9F0D’ (IAC-Default) ‘0000000000’ ‘8C’ (CDOL1) ‘95059B029F241D9F19069F25029F3403’ ‘8D’ (CDOL2) ‘95059B029F241D9F19069F25029F3403’ ‘9F08’ (Version) ‘01’ ‘8E’ (CVM List) ‘TBD’ ‘9F07’ (AUC) ‘ FFC0’ ‘5F20’ (Cardholder Name) ‘4E414D453132333435’ Xxxx (ALL data will be defined) ‘9F19’ (Token Requestor ID) ‘00000123457’ Tag Value countries. [LTSetting111] (differences with LTSetting1): Data AEF 01: Record 02: Tag Value '70’ ‘9F0E’ (IAC-Denial) ‘0000000000’ ‘9F0F’ (IAC-Online) ‘0000000000’ ‘9F0D’ (IAC-Default) ‘0000000000’ ‘8C’ (CDOL1) ‘95059B029F241D9F19069F25029F3403’ ‘8D’ (CDOL2) ‘95059B029F241D9F19069F25029F3403’ ‘9F08’ (Version) ‘01’ ‘8E’ (CVM List) ‘TBD’ ‘9F07’ (AUC) ‘ FFC0’ ‘5F20’ (Cardholder Name) ‘4E414D453132333435’ Xxxx (ALL data will be defined) ‘9F24’ (PAR) ‘3230303030303030303030303030303030303030303030303030303030’ ‘9F19’ (Token Requestor ID) ‘00000123457’ ‘9F25’ (Last 4 digits of PAN) ‘1234’ [LTSetting112] (differences with LTSetting1) Data AIP Tag 82 Value ‘2000’ [LTSetting113] (differences with LTSetting1): Data CVM List [LTSetting114] (differences with LTSetting1) Data Cardholder Name Cardholder Name in GPO response Tag 5F20 5F20 [LTSetting115] (differences with LTSetting1) Data Cardholder Name Cardholder Name in GPO response Tag 5F20 5F20 [LTSetting116] (differences with LTSetting1) Tag 8E Value TLV not present in record 4E414D202F Value TLV not present in record 4E414D453132333435202F Value 0000000000010000 countries. Data Cardholder Name Cardholder Name in GPO response Tag 5F20 5F20 Value TLV not present in record 4E414D45313233343537383930202F [LTSetting117] (differences with LTSetting1) Data Cardholder Name Cardholder Name in GPO response Tag 5F20 5F20 Value TLV not present in record 4E414D45313233343537383930204E414D45202F [LTSetting118] (differences with LTSetting1): Data AEF 01: Record 02: '70’ ‘9F0E’ (IAC-Denial) ‘0000000000’ ‘9F0F’ (IAC-Online) ‘0000000000’ ‘9F0D’ (IAC-Default) ‘0000000000’ ‘8C’ (CDOL1) ‘95059B029F241D9F19069F25029F3403’ ‘8D’ (CDOL2) ‘95059B029F241D9F19069F25029F3403’ ‘9F08’ (Version) ‘01’ ‘8E’ (CVM List) ‘00000000000000000400’ ‘9F07’ (AUC) ‘ FFC0’ ‘5F20’ (Cardholder Name) ‘4E414D453132333435’ Xxxx (ALL data will be defined) Tag Value AEF 02: - Record 01: '70’ ‘8F’ (CA Public Key Index in ICC) ‘02’ ‘90’ (Issuer Public Key Certificate) ‘TBD02’ ‘9F46’ (ICC Public Key Certificate) ‘TBD01’ ‘92’ (Issuer Public Key Remainder’) ‘TBD02’ ‘9F48’ (ICC Public Key Remainder’) ‘TBD01’ ‘9F32’ (Issuer Public Key Exponent’) ‘TBD02’ ‘9F47’ (ICC Public Key Exponent’) ‘TBD01’ ‘93’ (Signed Static Application Data) ‘TBD02’ ‘9F49’ (DDOL)’ ‘9F3704’ [LTSetting119] (differences with LTSetting1) Data Tag Value countries. PAR in GPO response 9F24 [LTSetting120] (differences with LTSetting1) Data Token Requestor ID in GPO response Tag 9F19 [LTSetting121] (differences with LTSetting1) Data PAR in GPO response Token Requestor ID in GPO response Last 4 digits of PAN in GPO response Tag 9F24 9F19 9F25 [LTSetting125] (differences with LTSetting1) Data Tag DF Name 84 CVM List 8E [LTSetting126] (differences with LTSetting1) Data DF Name Application Version Number Tag 84 9F09 [LTSetting127] (differences with LTSetting1) Data Tag DF Name 84 CVM List 8E [LTSetting128] (differences with LTSetting1) Data DF Name Expiration Date Tag 84 5F24 [LTSetting129] (differences with LTSetting1) Data DF Name Effective Date Tag 84 5F25 31303030303030303030303030303030303030303030303 Value 000000012345 Value 31303030303030303030303030303030303030303030303 000000012345 1234 Value B000001235 Not present Value B000001236 02 Value B000001237 00000000000000003F00 Value B000001238 200101 Value B000001239 480101 countries. [LTSetting130] (differences with LTSetting1) Data DF Name Expiration Date Tag 84 5F24 [LTSetting131] (differences with LTSetting1) Data Tag DF Name 84 [LTSetting132] (differences with LTSetting1) Data DF Name Application Version Number Tag 84 9F09 [LTSetting133] (differences with LTSetting1) Data DF Name Effective Date Tag 84 5F25 [LTSetting134] (differences with LTSetting1) Data Tag DF Name 84 Value B000001240 200101 Value B000001241 Value B000001242 02 Value B000001243 480101 Value B000001244 countries.

Legal Notice

This document summarizes EMVCo’s present plans for evaluation services and related policies and is subject to change by EMVCo at any time. This document does not create any binding obligations upon EMVCo or any third party regarding the subject matter of this document, which obligations will exist, if at all, only to the extent set forth in separate written agreements executed by EMVCo or such third parties. In the absence of such a written agreement, no product provider, test laboratory or any other third party should rely on this document, and EMVCo shall not be liable for any such reliance. No product provider, test laboratory or other third party may refer to a product, service or facility as EMVCo approved, in form or in substance, nor otherwise state or imply that EMVCo (or any agent of EMVCo) has in whole or part approved a product provider, test laboratory or other third party or its products, services, or facilities, except to the extent and subject to the terms, conditions and restrictions expressly set forth in a written agreement with EMVCo, or in an approval letter, compliance certificate or similar document issued by EMVCo. All other references to EMVCo approval are strictly prohibited by EMVCo. Under no circumstances should EMVCo approvals, when granted, be construed to imply any endorsement or warranty regarding the security, functionality, quality, or performance of any particular product or service, and no party shall state or imply anything to the contrary. EMVCo specifically disclaims any and all representations and warranties with respect to products that have received evaluations or approvals, and to the evaluation process generally, including, without limitation, any implied warranties of merchantability, fitness for purpose or non-infringement. All warranties, rights and remedies relating to products and services that have undergone evaluation by EMVCo are provided solely by the parties selling or otherwise providing such products or services, and not by EMVCo, and EMVCo will have no liability whatsoever in connection with such products and services. This document is provided "AS IS" without warranties of any kind, and EMVCo neither assumes nor accepts any liability for any errors or omissions contained in this document. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT, AS TO THIS DOCUMENT. EMVCo makes no representations or warranties with respect to intellectual property rights of any third parties in or in relation to this document. EMVCo undertakes no responsibility to determine whether any implementation of this document may violate, infringe, or otherwise exercise the patent, copyright, trademark, trade secret, know-how, or other intellectual property rights of third parties, and thus any person who implements any part of this document should consult an intellectual property attorney before any such implementation. Without limiting the foregoing, this document may provide for the use of public key encryption and other technology, which may be the subject matter of patents in several countries. Any party seeking to implement this document is solely responsible for determining whether its activities require a license to any such technology, including for

countries.

patents on public key encryption technology. EMVCo shall not be liable under any theory for any party's infringement of any intellectual property rights in connection with this document.

countries.