PCI Watch

Tracking changes across the Payment Card Industry

TTA Bulletin n°268: Terminal Level 2 Test Cases 44a Update

v2.0 Type Approval Bulletins
Contact Acceptance Device

EMV® Terminal Type Approval Bulletin No. 268 Second Edition, December 2023 Terminal Level 2 Test Cases 4.4a Update

Applicability

This Bulletin applies to:

  • EMV® Terminal Type Approval - Level 2 Test Cases – version 4.4a

Related Documents

This Bulletin should be read in conjunction with:

  • EMV® Terminal Type Approval - Level 2 Test Cases – version 4.4a

Effective Date

  • January 1st, 2024

Description

Based on EMVCo's continued review of EMV® Terminal Type Approval Level 2 Test Cases v4.4a, 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® Terminal Type Approval - Level 2 Test Cases – version 4.4a Section 5 – Test Settings Updates Section 5.5 – TVR & TSI un-setting bits checking TVR ICS-bitmask The ICS-bitmask value is defined by the tool at the start of a kernel configuration test session. This bitmask is depending on the supported options of this kernel configuration (listed in the ICS) and stay at the same value during the whole kernel configuration testing. It must be recalculated based on the supported options for each kernel configuration under test. The ICS-bitmask is limited to some TVR bits and are depending on the related ICS question(s) other TVR bit shall have the value ‘0’ in the bitmask: TVR TVR Name Related ICS question of the configuration B1b8 B1b7 Offline data authentication was not performed SDA failed SDA and DDA = NO bitmask has the value: 0 1

countries.

B1b6 ICC data missing 0 B1b5 Card appears on terminal Exception File = NO 1 exception file B1b4 DDA failed SDA and DDA = NO 1 B1b3 CDA failed CDA = NO 1 B1b2 SDA Selected SDA and DDA = NO 1 B1b1 XDA Selected XDA = No 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 not 0 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 or Biometric required Biometric = No 1 but Biometric capture device not working B3b1 RFU or Biometric required, Biometric = No 1 Biometric capture device present, but Biometric Subtype entry was bypassed 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 not Biometric = No 1 exceeded B4b2 RFU or A selected Biometric Biometric = No 1 Type not supported B4b1 XDA not failed XDA = No 1 B5b8 Default TDOL used Default TDOL = NO 1

countries.

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 CA ECC key missing XDA AND ODE = No 1 B5b2 ECC key recovery failed XDA AND ODE = No 1 B5b1 RFU Always set 1 Note: even if not related to ICS-bitmask, the un-setting of RFU TVR bits is checked here. TVR LT-bitmask The LT-bitmask value is defined by the tool for a kernel configuration testing. This bitmask is depending on the LT setting used for a batch of test cases. LT-bitmask must be updated anytime the LT is changed: - AIP - AUC - TDOL presence - ATC value = 0 - Effective Date present - Last Online ATC absent - Lower Consecutive Limit and Upper Consecutive Limit absent - … The LT-bitmask is limited to the following TVR bits (any other TVR bit shall have the value ‘0’ in this bitmask): TVR TVR Name B1b8 B1b7 B1b6 B1b5 B1b4 B1b3 B1b2 B1b1 B2b8 B2b7 B2b6 B2b5 B2b4 Offline data authentication was not performed SDA failed ICC data missing Card appears on terminal exception file DDA failed CDA failed SDA Selected XDA Selected ICC and terminal have different application versions Expired application Application not yet effective Requested service not allowed for card product New card B2b3 RFU LT Data setting bitmask has the value: 0 AIP States SDA is not supported 1 All Mandatory Data present in LT 1 0 AIP States DDA is not supported 1 AIP States CDA is not supported 1 AIP States SDA is not supported 1 AIP States XDA is not supported 1 ICC application version not present 1 in LT 0 Effective Data not present in LT 1 (AUC not present in LT) OR (AUC 1 value = ‘FFC0’) (ATC different from ‘0’) OR 1 (LOATC # ‘0’) OR (LCOL AND UCOL not present) 0

countries.

B2b2 RFU or Biometric not performed 0 or not successful B2b1 RFU or Biometric template 0 format supported B3b8 Cardholder verification was not AIP states Cardholder Verification 1 successful is not supported B3b7 Unrecognised CVM (AIP states Cardholder Verification 1 is not supported) OR (CVM list uses only EMVCo recognized Code) B3b6 PIN Try Limit exceeded (AIP states Cardholder Verification 1 is not supported) OR (CVM list does not contain Offline Enciphered PIN AND Plaintext PIN) B3b5 PIN entry required and PIN pad (AIP states Cardholder Verification 1 not present or not working is not supported) OR (CVM list does not contain any PIN) B3b4 PIN entry required, PIN pad (AIP states Cardholder Verification 1 present, but PIN was not is not supported) OR (CVM list entered does not contain any PIN) B3b3 Online PIN entered (AIP states Cardholder Verification 1 is not supported) OR (CVM List does not contain Online PIN) B3b2 RFU or Biometric required but 0 Biometric capture device not working B3b1 RFU or Biometric required, 0 Biometric capture device present, but Biometric Subtype entry was bypassed B4b8 Transaction exceeds floor limit 0 B4b7 Lower consecutive offline limit Lower consecutive offline limit not 1 exceeded present in LT B4b6 Upper consecutive offline limit Upper consecutive offline limit not 1 exceeded present in LT B4b5 Transaction selected randomly 0 for online processing B4b4 Merchant forced transaction 0 online B4b3 RFU or Biometric Try Limit not 0 exceeded B4b2 RFU or A selected Biometric 0 Type not supported B4b1 XDA not Failed AIP States XDA is not supported 1 B5b8 Default TDOL used TDOL present in LT 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 0

countries.

B5b3 B5b2 B5b1 RFU RFU RFU TVR Transaction-bitmask All bits of the Transaction-bitmask shall be set to zero for the time being. TVR TVR Name LT Data setting B1b8 B1b7 B1b6 B1b5 B1b4 B1b3 B1b2 B1b1 B2b8 B2b7 B2b6 B2b5 B2b4 B2b3 B2b2 B2b1 B3b8 B3b7 B3b6 B3b5 B3b4 B3b3 B3b2 B3b1 B4b8 B4b7 Offline data authentication was not performed SDA failed ICC data missing Card appears on terminal exception file DDA failed CDA failed SDA Selected XDA Selected ICC and terminal have different application versions Expired application Application not yet effective Requested service not allowed for card product New card RFU RFU or Biometric not performed or not successful RFU or Biometric template format supported Cardholder verification was not successful Unrecognised CVM PIN Try Limit exceeded PIN entry required and PIN pad not present or not working PIN entry required, PIN pad present, but PIN was not entered Online PIN entered RFU or Biometric required but Biometric capture device not working RFU or Biometric required, Biometric capture device present, but Biometric Subtype entry was bypassed Transaction exceeds floor limit Lower consecutive offline limit exceeded 0 0 0 bitmask has the value: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

countries.

B4b6 Upper consecutive offline limit 0 exceeded B4b5 Transaction selected randomly 0 for online processing B4b4 Merchant forced transaction 0 online B4b3 RFU or Biometric Try Limit not 0 exceeded B4b2 RFU or A selected Biometric 0 Type not supported B4b1 RFU 0 B5b8 Default TDOL used 0 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 0 B5b3 CA ECC key missing 0 B5b2 ECC key recovery failed 0 B5b1 RFU 0

countries.

Terminal Settings Several test cases require the use of predefined Terminal data setting listed in this section in one Terminal Setting named Termsetting1. [Termsetting1] Data Transaction Date 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 TAC-Default TAC-Denial TAC-Online Tag (if any) 9A 9F06 9F09 9F06 9F06 9F06 9F06 9F06 9F06 9F06 - Value Current Date B000001234 3031 0000000000 0000000000 0000000000 B00000567800000000000000 000000FF 0000400000 0000000000 0000400000 B000001235 2000000000 0000000000 2000000000 B000001236 0080000000 0000000000 0080000000 B000001237 0000400000 0000000000 0000400000 B000001238 0040000000 0000000000 0040000000 B000001239 0020000000 0000000000 0020000000 B000001240 0040000000 0000000000 0040000000

countries.

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 9F06 - 9F06 - 9F06 - 9F06 - B000001241 0000000000 0000000000 0000000000 B000001242 0080000000 0000000000 0080000000 B000001243 0060000000 0000000000 0060000000 B000001244 0000000000 0000000000 0000000000 Note: If the Kernel support less than 12 AIDs (as per ICS response), the above list will be limited to the first (in the order) AID listed above to reach the number of AID supported. Note2: 6 is the minimum number of AID that the Kernel shall support.

countries.

LT Settings [LTSetting1] (updates only) Data Tag 8C CDOL1 8D CDOL2 Value 95059B029F241D9F1906 9F25029F34039F3704 9F40059F33039A039F2103 95059B029F241D9F1906 9F25029F34039F3704 9F40059F33039A039F21038A02 [LTSetting157] (differences with LTSetting1) Data Track 1 Discretionary Data Tag 9F1F [LTSetting158] (differences with LTSetting1) Data Track 1 Discretionary Data Tag 9F1F Value 9F1F04C3C6 Value 9F1F06CED7 [LTSetting159] (differences with LTSetting1) Data Tag CVM list 8E [LTSetting160] (differences with LTSetting1) Data Tag CVM list 8E [LTSetting161] (differences with LTSetting1) Data Tag CVM list 8E [LTSetting162] (differences with LTSetting1) Data Tag CVM list 8E [LTSetting163] (differences with LTSetting1) Data Tag CVM list 8E [LTSetting164] (differences with LTSetting1) Value 000005DC0000000000060000 Value 000005DC0000000000070000 Value 00000000000005DC00080000 Value 00000000000005DC00090000 Value 000000000000000000040000

countries.

Data Tag CVM list 8E [LTSetting165] (differences with LTSetting1) Data Tag CVM list 8E [LTSetting166] (differences with LTSetting1) Data Tag AIP 82 [LTSetting167] (differences with LTSetting1) Data Tag CVM list 8E [LTSetting168] (differences with LTSetting1) Data Tag CVM list 8E [LTSetting169] (differences with LTSetting1) Data Tag CVM list 8E [LTSetting170] (differences with LTSetting1) Data Tag CVM list 8E [LTSetting171] (differences with LTSetting1) Data Tag CVM list 8E [LTSetting172] (differences with LTSetting1) Data Tag CVM list 8E [LTSetting173] (differences with LTSetting1) Data Tag CVM list 8E Value 00000000000000000000 Value 00000000000000000002 Value 2100 Value 00000000000000000200 Value 000003E8000000000206 Value 00000000000003E80209 Value 000003E8000000000207 Value 00000000000003E80208 Value 00000000000000000201 Value 00000000000000000204

countries.

[LTSetting174] (differences with LTSetting1) Data Tag CVM list 8E [LTSetting175] (differences with LTSetting1) Data Tag CVM list 8E [LTSetting176] (differences with LTSetting1) Data Tag CVM list 8E [LTSetting177] (differences with LTSetting1) Data Tag CVM list 8E [LTSetting178] (differences with LTSetting1) Data Tag CVM list 8E [LTSetting179] (differences with LTSetting1): Data Expiration Date IAC-Default [LTSetting189] (differences with LTSetting1) Data IAC-Denial IAC-Online IAC-Default Tag 9F0E 9F0F 9F0D [LTSetting190] (differences with LTSetting1) Data Tag CVM list 8E Value 00000000000000000205 Value 00000000000000000202 Value 0000000000000000410344030200 Value 000000000000000041030200 Value 000000000000000044030200 Tag 5F24 9F0D Value 200101 0040000000 Value 00040000 00040000 00040000 Value 00000000000000000102

countries.

Section 7 – Test Cases Updates New test cases include: 2CE.003.15 2CJ.087.06 Revised test cases include: 2CA.041.00 2CA.041.04 2CA.122.00 2CA.122.02 2CA.122.04 2CA.122.08 2CA.122.11 2CA.122.14 2CA.122.17 2CA.122.20 2CA.122.23 2CB.031.00 2CC.058.07 2CC.014.00 2CC.014.01 2CC.014.02 2CC.014.08 2CC.014.09 2CC.122.01 2CC.123.02 2CC.134.06 2CC.134.10 2CC.134.12 2CE.003.00 2CJ.002.08 2CJ.018.00 2CJ.018.01 2CJ.018.02 2CJ.018.03 2CJ.018.04 2CJ.018.09 2CJ.018.10 2CJ.074.00 2CJ.084.01 2CJ.087.00 2CJ.088.01 2CJ.089.00 2CJ.089.02 2CJ.089.04 2CJ.089.06 2CJ.089.08 2CJ.089.10 2CJ.095.06 2CJ.095.07 2CJ.095.08 2CJ.095.09 Deleted test cases include: 2CA.025.03 2CA.067.00 2CA.068.00 2CA.069.00 2CJ.177.00 2CM.038.00 2CM.040.00 2CM.044.00 2CM.052.00 2CM.080.00 2CM.082.00 2CM.091.00 2CJ.023.02 2CJ.095.10 2CJ.095.11 2CJ.095.12 2CJ.100.05 2CJ.112.00 2CJ.158.00 2CJ.159.00 2CJ.159.01 2CJ.160.00 2CJ.160.01 2CJ.161.00 2CJ.162.00 2CJ.163.00 2CJ.164.00 2CJ.165.00 2CJ.166.00 2CJ.166.01 2CJ.167.00 2CJ.167.01 2CJ.168.00 2CJ.168.01 2CJ.169.00 2CJ.169.02 2CM.105.00 2CM.137.00 2CN.016.00 2CO.019.00 2CO.020.00 2CO.021.00 2CM.094.02 2CJ.178.00 2CJ.203.01 2CK.010.00 2CM.020.00 2CM.020.01 2CM.077.00 2CM.081.00 2CM.086.00 2CM.087.00 2CO.030.00 2CO.031.00 2CO.037.00 2CS.014.00 2CS.014.01 2CS.014.02 2CS.014.03 2CS.015.00 2CS.015.01 2CS.015.02 2CS.015.03 2CS.015.04 2CS.015.05 2CS.016.00 2CO.021.01 2CO.022.00 2CO.023.00 2CO.032.00 2CO.033.00 2CO.038.00 2CM.094.03 2CS.016.03 2CT.008.00 2CT.009.00 2CT.009.01 2CT.010.00 2CT.010.01 2CT.010.02 2CT.010.03 2CT.011.00 2CT.011.01 2CT.011.02 2CT.011.03 2CT.011.04 2CT.018.00 2CT.018.01 2CT.035.00 2CT.036.00 2CT.037.00 2CT.039.00 2CT.012.00 2CT.012.01 2CT.013.00 2CT.013.01

countries.

2CA.041.00 Coding of Bits and Bytes RFU Revision: 44b Objective: To ensure that the terminal sets to zeroes data (bits and bytes) indicated as RFU, unless otherwise stated. This applies particularly to TVR, TSI, Terminal capabilities, additional capabilities, GENERATE AC reference control parameter Reference Book 3 - Section 6.3.6 - Coding of RFU Data EMV 4.4: Book 3 - Section 6.5.5.2 - Command Message Book 4 - Section A2 - Terminal Capabilities Book 4 - Section A3 - Additional Terminal Capabilities Terminal [NA] ICS Options: Conditions TVR, TSI, Terminal Capabilities and Additional Terminal Capabilities are: requested in CDOL1 Procedure:

  • 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’)
  • Data received at first GENERATE AC: - RFU bits set to zero (TVR_B2b3=‘0’). - RFU bits set to zero (TSI_B1b1=‘0’). - RFU bits set to zero (TSI_B1b2=‘0’). - RFU bits set to zero (TSI_B2b1=‘0’). - RFU bits set to zero (TSI_B2b2=‘0’). - RFU bits set to zero (TSI_B2b3=‘0’). - RFU bits set to zero (TSI_B2b4=‘0’). - RFU bits set to zero (TSI_B2b5=‘0’). - RFU bits set to zero (TSI_B2b6=‘0’). - RFU bits set to zero (TSI_B2b7=‘0’). - RFU bits set to zero (TSI_B2b8=‘0’). - RFU bits set to zero (TermCap_B1b1=‘0’). - RFU bits set to zero (TermCap_B1b2=‘0’). - RFU bits set to zero (TermCap_B1b3=‘0’). - RFU bits set to zero (TermCap_B1b4=‘0’). - RFU bits set to zero (TermCap_B1b5=‘0’). - RFU bits set to zero (TermCap_B3b1=‘0’). - RFU bits set to zero (TermCap_B3b2=‘0’). countries. 2CA.041.00 Coding of Bits and Bytes RFU - RFU bits set to zero (TermCap_B3b5=‘0’). - RFU bits set to zero (AddTermCap_B2b1=‘0’). - RFU bits set to zero (AddTermCap_B2b2=‘0’). - RFU bits set to zero (AddTermCap_B2b3=‘0’). - RFU bits set to zero (AddTermCap_B2b4=‘0’). - RFU bits set to zero (AddTermCap_B2b5=‘0’). - RFU bits set to zero (AddTermCap_B2b6=‘0’). - RFU bits set to zero (AddTermCap_B2b7=‘0’). - RFU bits set to zero (AddTermCap_B3b1=‘0’). - RFU bits set to zero (AddTermCap_B3b2=‘0’). - RFU bits set to zero (AddTermCap_B3b3=‘0’). - RFU bits set to zero (AddTermCap_B3b4=‘0’). - RFU bits set to zero (AddTermCap_B4b3=‘0’). - RFU bits set to zero (AddTermCap_B4b4=‘0’).
  • Parameter received at first GENERATE AC: - Reference control parameter bits set to zero (P1_b1='0') - Reference control parameter bits set to zero (P1_b2='0') - Reference control parameter bits set to zero (P1_b3='0') - Reference control parameter bits set to zero (P1_b6='0') countries. 2CA.041.04 Coding of Bits and Bytes RFU (5) (Implied) Revision: 44b Objective: To ensure that the terminal does not use the RFU bits, even when set to '1'. This applies to IAC Reference Book 3 - Section 6.3.6 - Coding of RFU Data EMV 4.4: Terminal [NA] ICS Options: Conditions IACs RFU bits of LT are set to '1': Procedure:
  • Transaction is performed with TermSetting1 and LTsetting189 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. 2CA.122.00 Test No: Objective: Reference EMV 4.4: Terminal Configuration (New format): Conditions: Payment System reserved Data objects processing 2CA.122.00 - Revision 44b - Number of sub cases: 7 To ensure that the terminal ignores Payment System reserved Data Objects when the selected AID is not an Payment System AID. Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects [NA]
  • LT AID value is B000001234
  • Terminal AID Value is B000001234
  • PDOL, CDOL1, CDOL2 and TDOL of LT contains all reserved tags in the range '9F50' to '9F7F'.
  • Case 01: FCI (tag 6F) of ADF contains all reserved tags in the range '9F50' to '9F6A' with values different from zero
  • Case 02: FCI Issuer discretionary Data (tag BF0C) of ADF contains additionally all reserved tags in the range '9F50' to '9F6A' with values different from zero.
  • Case 03: Response to GENERATE AC commands contains all reserved tags in the range '9F50' to '9F7F' with values different from zero. and shall be encoded in Template 77.
  • Case 04: Records contains all reserved tags in the range '9F50' to '9F7F' with values different from zero. (splitted over SFI 1 to 10).
  • Case 05: Response to GET PROCESSING OPTIONS contains all reserved tags in the range '9F50' to '9F7F' with values different from zero. and shall be encoded in template 77
  • Case 06: FCI (tag 6F) of ADF contains all reserved tags in the range '9F6B' to '9F7F' with values different from zero Action: Procedure: Pass Criteria:
  • Case 07: FCI Issuer discretionary Data (tag BF0C) of ADF contains additionally all reserved tags in the range '9F6B' to '9F7F' with values different from zero. NA Application in LT is selected and transaction is processed with LT until approval.
  • The terminal shall process the transaction until completion, by requesting a TC at first or second GENERATE AC.
  • Values of the reserved tags in the range '9F50' to '9F7F' received by the LT via the DOLs are set to “00’ (Note: for CDOL2 this is applicable only if a 2nd GENERATE AC has been performed) countries. 2CA.122.02 EMV reserved Data objects processing (1) Test No: 2CA.122.02 – Revision 44b – Number of sub cases: 5 Objective: To ensure that the terminal ignores EMV reserved Data Objects (not used by EMV). Reference Book 3 – Section Annex B1 Coding of the Tag Field of BER-TLV Data EMV 4.4: Objects Book 3 - Section Annex A2 – Data Elements by tag Terminal [NA] Configuration (New format): Conditions:
  • LT AID value is B000001234
  • Terminal AID Value is B000001234
  • PDOL, CDOL1, CDOL2 and TDOL of LT contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’.
  • All Data Elements listed in Book 3, Table 38 are excluded from the below lists.
  • Case 01: FCI (tag 6F) of ADF contains additionally all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero within the FCI template
  • Case 02: FCI Issuer discretionary Data (tag BF0C) of ADF contains additionally all EMV primitive tags (reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero
  • Case 03: Response to GENERATE AC contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero and shall be encoded in template 77
  • Case 04: Records contains: all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero (splitted over SFI 1 to 10).
  • Case 05: Response to GET PROCESSING OPTIONS contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the countries. 2CA.122.02 EMV reserved Data objects processing (1) range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero and shall be encoded in template 77 Action: NA Procedure: Application in LT is selected and transaction is processed with LT until approval. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC either at First or Second GENERATE AC.
  • Values of the EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’received by the LT via the DOLs are set to “00’(Note: for CDOL2 this is applicable only if a 2nd GENERATE AC has been performed) countries. 2CA.122.04 Proprietary Data objects processing (1) Test No: 2CA.122.04 - Revision 44b - Number of sub cases: 7 Objective: To ensure that the terminal ignores Proprietary Data Objects. Reference Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects EMV 4.4: Book 3 - Section Annex A2 – Data Elements by tag Terminal [NA] Configuration (New format): Conditions:
  • All Data Elements listed in Book 3, Table 38 are excluded from the below lists.
  • Case 01: FCI (tag 6F) of ADF contains additionally 50 proprietary tags including Tag DF09, DF10, DF11 and DF21 within the FCI template
  • Case 02: FCI Issuer discretionary Data (tag BF0C) of ADF contains additionally 50 proprietary tags including Tag DF09, DF10, DF11 and DF21
  • Case 03: Response to GET PROCESSING OPTIONS contains additionally 50 proprietary tags including Tag DF09, DF10, DF11 and DF21and shall be encoded in template 77
  • Case 04: The PDOL of LT contains additionally 50 proprietary tags including Tag DF09, DF10, DF11 and DF21
  • Case 05: The CDOL1 of LT contains additionally 50 proprietary tags including Tag DF09, DF10, DF11 and DF21
  • Case 06: The CDOL2 of LT contains additionally 50 proprietary tags including Tag DF09, DF10, DF11 and DF21 and LT request ARQC on first Generate AC
  • Case 07: The TDOL of LT contains additionally 50 proprietary tags including Tag DF09, DF10, DF11 and DF21 Action: NA Procedure: Application in LT is selected and transaction is processed with LT until approval. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC at first or second GENERATE AC. countries. 2CA.122.08 EMV reserved Data objects processing (5) Test No: 2CA.122.08 – Revision 44b – Number of sub cases: 5 Objective: To ensure that the terminal ignores EMV reserved Data Objects (not used by EMV). Reference Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects EMV 4.4: Book 3 - Section Annex A2 – Data Elements by tag Terminal [NA] Configuration (New format): Conditions:
  • LT AID value is A000000025
  • Terminal AID Value is A000000025
  • PDOL, CDOL1, CDOL2 and TDOL of LT contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’.
  • All Data Elements listed in Book 3, Table 38 are excluded from the below lists.
  • Case 01: FCI (tag 6F) of ADF contains additionally all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero within the FCI template
  • Case 02: FCI Issuer discretionary Data (tag BF0C) of ADF contains additionally all EMV primitive tags (reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero
  • Case 03: Response to GENERATE AC contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero and shall be encoded in template 77
  • Case 04: Records contains: all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero (splitted over SFI 1 to 10).
  • Case 05: Response to GET PROCESSING OPTIONS contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero and shall be encoded in template 77 countries. 2CA.122.08 EMV reserved Data objects processing (5) Action: NA Procedure: Application in LT is selected and transaction is processed with LT until approval. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC either at First or Second GENERATE AC.
  • Values of the EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’received by the LT via the DOLs are set to “00’ (Note: for CDOL2 this is applicable only if a 2nd GENERATE AC has been performed) countries. 2CA.122.11 EMV reserved Data objects processing (8) Test No: 2CA.122.11 – Revision 44b – Number of sub cases: 5 Objective: To ensure that the terminal ignores EMV reserved Data Objects (not used by EMV). Reference Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects EMV 4.4: Book 3 - Section Annex A2 – Data Elements by tag Terminal [NA] Configuration (New format): Conditions:
  • LT AID value is A0000000031010
  • Terminal AID Value is VISA A0000000031010
  • PDOL, CDOL1, CDOL2 and TDOL of LT contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’.
  • All Data Elements listed in Book 3, Table 38 are excluded from the below lists.
  • Case 01: FCI (tag 6F) of ADF contains additionally all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero within the FCI template
  • Case 02: FCI Issuer discretionary Data (tag BF0C) of ADF contains additionally all EMV primitive tags (reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero
  • Case 03: Response to GENERATE AC contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero and shall be encoded in template 77
  • Case 04: Records contains: all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero (splitted over SFI 1 to 10).
  • Case 05: Response to GET PROCESSING OPTIONS contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero and shall be encoded in template 77 countries. 2CA.122.11 EMV reserved Data objects processing (8) Action: NA Procedure: Application in LT is selected and transaction is processed with LT until approval. Pass Criteria:
  • The terminal shall process the transaction until completion, by requesting a TC either at First or Second GENERATE AC.
  • Values of the EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’received by the LT via the DOLs are set to “00’ (Note: for CDOL2 this is applicable only if a 2nd GENERATE AC has been performed) countries. 2CA.122.14 EMV reserved Data objects processing (11) Test No: 2CA.122.14 – Revision 44b – Number of sub cases: 5 Objective: To ensure that the terminal ignores EMV reserved Data Objects (not used by EMV). Reference Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects EMV 4.4: Book 3 - Section Annex A2 – Data Elements by tag Terminal [NA] Configuration (New format): Conditions:
  • LT AID value is A0000000041010
  • Terminal AID Value is A0000000041010
  • PDOL, CDOL1, CDOL2 and TDOL of LT contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’.
  • All Data Elements listed in Book 3, Table 38 are excluded from the below lists.
  • Case 01: FCI (tag 6F) of ADF contains additionally all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero within the FCI template
  • Case 02: FCI Issuer discretionary Data (tag BF0C) of ADF contains additionally all EMV primitive tags (reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero
  • Case 03: Response to GENERATE AC contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero and shall be encoded in template 77
  • Case 04: Records contains: all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero (splitted over SFI 1 to 10).
  • Case 05: Response to GET PROCESSING OPTIONS contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero and shall be encoded in template 77 countries. 2CA.122.14 EMV reserved Data objects processing (11) Action: NA Procedure: Application in LT is selected and transaction is processed with LT until approval. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC either at First or Second GENERATE AC.
  • Values of the EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’received by the LT via the DOLs are set to “00’ (Note: for CDOL2 this is applicable only if a 2nd GENERATE AC has been performed) countries. 2CA.122.17 EMV reserved Data objects processing (14) Test No: 2CA.122.17 – Revision 44b – Number of sub cases: 5 Objective: To ensure that the terminal ignores EMV reserved Data Objects (not used by EMV). Reference Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects EMV 4.4: Book 3 - Section Annex A2 – Data Elements by tag Terminal [NA] Configuration (New format): Conditions:
  • LT AID value is A0000000651010
  • Terminal AID Value is A0000000651010
  • PDOL, CDOL1, CDOL2 and TDOL of LT contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’.
  • All Data Elements listed in Book 3, Table 38 are excluded from the below lists.
  • Case 01: FCI (tag 6F) of ADF contains additionally all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero within the FCI template
  • Case 02: FCI Issuer discretionary Data (tag BF0C) of ADF contains additionally all EMV primitive tags (reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero
  • Case 03: Response to GENERATE AC contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero and shall be encoded in template 77
  • Case 04: Records contains: all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero (splitted over SFI 1 to 10).
  • Case 05: Response to GET PROCESSING OPTIONS contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero and shall be encoded in template 77 countries. 2CA.122.17 EMV reserved Data objects processing (14) Action: NA Procedure: Application in LT is selected and transaction is processed with LT until approval. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC either at First or Second GENERATE AC.
  • Values of the EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’received by the LT via the DOLs are set to “00’ (Note: for CDOL2 this is applicable only if a 2nd GENERATE AC has been performed) countries. 2CA.122.20 EMV reserved Data objects processing (17) Test No: 2CA.122.20 – Revision 44b – Number of sub cases: 5 Objective: To ensure that the terminal ignores EMV reserved Data Objects (not used by EMV). Reference Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects EMV 4.4: Book 3 - Section Annex A2 – Data Elements by tag Terminal [NA] Configuration (New format): Conditions:
  • LT AID value is A000000333010101
  • Terminal AID Value is A000000333010101
  • PDOL, CDOL1, CDOL2 and TDOL of LT contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’.
  • All Data Elements listed in Book 3, Table 38 are excluded from the below lists.
  • Case 01: FCI (tag 6F) of ADF contains additionally all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero within the FCI template
  • Case 02: FCI Issuer discretionary Data (tag BF0C) of ADF contains additionally all EMV primitive tags (reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero
  • Case 03: Response to GENERATE AC contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero and shall be encoded in template 77
  • Case 04: Records contains: all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero (splitted over SFI 1 to 10).
  • Case 05: Response to GET PROCESSING OPTIONS contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero and shall be encoded in template 77 countries. 2CA.122.20 EMV reserved Data objects processing (17) Action: NA Procedure: Application in LT is selected and transaction is processed with LT until approval. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC either at First or Second GENERATE AC.
  • Values of the EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’received by the LT via the DOLs are set to “00’ (Note: for CDOL2 this is applicable only if a 2nd GENERATE AC has been performed) countries. 2CA.122.23 EMV reserved Data objects processing (20) Test No: 2CA.122.23 – Revision 44b – Number of sub cases: 5 Objective: To ensure that the terminal ignores EMV reserved Data Objects (not used by EMV). Reference Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects EMV 4.4: Book 3 - Section Annex A2 – Data Elements by tag Terminal [NA] Configuration (New format): Conditions:
  • LT AID value is A0000001523010
  • Terminal AID Value is A0000001523010
  • PDOL, CDOL1, CDOL2 and TDOL of LT contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’.
  • All Data Elements listed in Book 3, Table 38 are excluded from the below lists.
  • Case 01: FCI (tag 6F) of ADF contains additionally all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero within the FCI template
  • Case 02: FCI Issuer discretionary Data (tag BF0C) of ADF contains additionally all EMV primitive tags (reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero
  • Case 03: Response to GENERATE AC contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero and shall be encoded in template 77
  • Case 04: Records contains: all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero (splitted over SFI 1 to 10).
  • Case 05: Response to GET PROCESSING OPTIONS contains all EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’ with values different from zero and shall be encoded in template 77 countries. 2CA.122.23 EMV reserved Data objects processing (20) Action: NA Procedure: Application in LT is selected and transaction is processed with LT until approval. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC either at First or Second GENERATE AC.
  • Values of the EMV primitive tags reserved but not used in the EMV specification, (for example ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F01’ to ‘9F4F’received by the LT via the DOLs are set to “00’ (Note: for CDOL2 this is applicable only if a 2nd GENERATE AC has been performed) countries. 2CB.031.00 Permitted Revision: Objective: Reference EMV 4.4: Terminal Configuration (New format): Conditions: Application Selection Indicator: One Occurrence 44b To ensure that if the DFNAME in the ICC is longer than that of the AID in the terminal, but they are identical up to and including the last character in the terminal AID, the terminal shall check the Application Selection indicator. If the indicator says only one occurrence is allowed the terminal does not add the AID to the candidate list and issue another SELECT command using the next AID. Book 1 - Section 12.3.3 - Using a List of AIDs [NA]
  • LT does not contain PSE
  • DF Name 1 contained in FCI returned by the LT for first AID (AID1) selection is longer than that of terminal AID used for selection, but they are identical up to and including the last character in the terminal AID1.
  • Terminal Application Selection Indicator only allows one occurrence for selected AID.
  • LT shall contain another DF Name 2 exactly matching the terminal AID2. Action: Procedure: Pass Criteria: NA Application Selection using list of AIDs is performed.
  • The terminal shall process the transaction until completion, by requesting a TC.
  • LT shall receive SELECT Command with AID name that exactly matches the ADF name from the LT.
  • LT shall not receive SELECT Command with the longer DF Name 1
  • LT shall not receive SELECT AID1 command with P2 set to ‘Next occurrence
  • After SELECT AID1 command, the LT shall receive another SELECT 'AID' command but with the AID2 name.
  • . countries. 2CC.014.00 absent Test No: Objective: Reference EMV 4.4: Terminal Configuration (New format): Conditions: Retrieving CA Public Key used to Perform SDA: Key 2CC.014.00 - Revision 44b - Number of sub cases: 0 To ensure that if the terminal supports Static Data Authentication, if no Certification Authority Public Keys is available for a given RID and Certification Authority Public Key Index, the terminal fails Static Data Authentication. Book 2 - Section 5.2 - Retrieval of Certification Authority Public Key [SDA]
  • Terminal does not contain the Certification Authority Public Key referenced in LT.
  • AIP of LT indicates Static Data Authentication is supported (AIP byte 1 bit 7 = ‘1’). Action: Procedure: Pass Criteria: NA Application in LT is selected and transaction is processed with LT (in particular Static Data Authentication).
  • The terminal shall process the transaction until completion, by requesting a TC at first or second GENERATE AC.
  • TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication failed) received at 1st GENERATE AC.
  • TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not used) received at 1st GENERATE AC.
  • TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not used) received at 1st GENERATE AC.
  • TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) received at 1st GENERATE AC. countries. 2CC.014.01 absent Test No: Objective: Reference EMV 4.4: Terminal Configuration (New format): Conditions: Retrieving CA Public Key used to Perform DDA: Key 2CC.014.01 - Revision 44b - Number of sub cases: 0 To ensure that if the terminal supports Dynamic Data Authentication, and if no Certification Authority Public Keys is available for a given RID and Certification Authority Public Key Index, the terminal fails the Dynamic Data Authentication process. Book 2 - Section 6.2 - Retrieval of Certification Authority Public Key [DDA]
  • Terminal does not contain the Certification Authority Public Key referenced in LT.
  • AIP of LT indicates Dynamic Data Authentication is supported (AIP byte 1 bit 6 = ‘1’). Action: Procedure: Pass Criteria: NA Application in LT is selected and transaction is processed with LT.
  • The terminal shall process the transaction until completion, by requesting a TC at first or second GENERATE AC.
  • TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication failed) received at 1st GENERATE AC.
  • TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not used) received at 1st GENERATE AC.
  • TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used) received at 1st GENERATE AC.
  • TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) received at 1st GENERATE AC. countries. 2CC.014.02 Retrieving CA Public Key used to Perform Combined DDA/AC: Key absent Test No: 2CC.014.02 - Revision 44b - Number of sub cases: 0 Objective: To ensure that if the terminal supports Combined DDA/AC Data Authentication, and if no Certification Authority Public Keys is available for a given RID and Certification Authority Public Key Index, the terminal fails the Combined DDA/AC Data Authentication process. Reference Book 2 - Section 6.2 - Retrieval of Certification Authority Public Key EMV 4.4: Book 2 - Section 6.6 - Combined DDA/Application Cryptogram Generation (CDA) Terminal [CDA] AND ([Offline Only] OR [Offline/Online Capable]) Configuration (New format): Conditions:
  • Terminal does not contain the Certification Authority Public Key referenced in LT.
  • AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
  • IAC’s and TAC’s are set so that TC is requested at first Gen AC. Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:
  • The Terminal shall not request CDA for the GENERATE AC
  • The terminal shall process the transaction until completion, by requesting a TC according to TAC and IAC setting.
  • TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data Authentication failed) received at 1st GENERATE AC.
  • TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used) received at 1st GENERATE AC.
  • TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not used) received at 1st GENERATE AC.
  • TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) received at 1st GENERATE AC. countries. 2CC.014.08 Retrieving CA Public Key used to Perform Combined DDA/AC: Key absent (9) Test No: 2CC.014.08 - Revision 44b - Number of sub cases: 0 Objective: To ensure that if the terminal supports Combined DDA/AC Data Authentication, and if no Certification Authority Public Keys is available for a given RID and Certification Authority Public Key Index, the terminal fails the Combined DDA/AC Data Authentication process. Reference Book 2 - Section 6.2 - Retrieval of Certification Authority Public Key EMV 4.4: Book 2 - Section 6.6 - Combined DDA/Application Cryptogram Generation (CDA) Terminal [CDA] AND ([Online Only] OR [Offline/Online Capable]) Configuration (New format): Conditions:
  • Terminal does not contain the Certification Authority Public Key referenced in LT.
  • AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
  • IAC’s and TAC’s are set so that ARQC is requested at first Gen AC.
  • Transaction is online approved. Action: Procedure: Pass Criteria: NA Application in LT is selected and transaction is processed with LT.
  • The Terminal shall not request CDA for the 1st and 2nd GENERATE AC
  • The terminal shall process the transaction until completion, by requesting a TC at second GENERATE AC.
  • TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data Authentication failed) received at 1st GENERATE AC.
  • TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used) received at 1st GENERATE AC.
  • TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not used) received at 1st GENERATE AC.
  • TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) received at 1st GENERATE AC. countries. 2CC.014.09 Retrieving CA Public Key used to Perform Combined DDA/AC: Key absent (10) Test No: 2CC.014.09 - Revision 44b - Number of sub cases: 0 Objective: To ensure that if the terminal supports Combined DDA/AC Data Authentication, and if no Certification Authority Public Keys is available for a given RID and Certification Authority Public Key Index, the terminal fails the Combined DDA/AC Data Authentication process. Reference Book 2 - Section 6.2 - Retrieval of Certification Authority Public Key EMV 4.4: Book 2 - Section 6.6 - Combined DDA/Application Cryptogram Generation (CDA) Terminal [CDA] AND ([Online Only] OR [Offline/Online Capable]) Configuration (New format): Conditions:
  • Terminal does not contain the Certification Authority Public Key referenced in LT.
  • AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
  • IAC’s and TAC’s are set so that ARQC is requested at first Gen AC.
  • Transaction is online declined. Action: Procedure: Pass Criteria: NA Application in LT is selected and transaction is processed with LT.
  • The Terminal shall not request CDA for the 1st and 2nd GENERATE AC
  • The terminal shall process the transaction until completion, by requesting an AAC at second GENERATE AC.
  • TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data Authentication failed) received at 1st GENERATE AC.
  • TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used) received at 1st GENERATE AC.
  • TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not used) received at 1st GENERATE AC.
  • TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) received at 1st GENERATE AC. countries. 2CC.058.07 Certification Revocation List update, addition (3) Revision: 44b Objective: To ensure that the terminal is be able to update the Certification Revocation List by adding an entry. Reference Book 2 - Section 5.1.2 - Certification Revocation List EMV 4.4: Terminal [CDA] AND [Key Revocation] ICS Options: Conditions:
  • Pre-Conditions: Test 2CC.058.06 has to be run before
  • LTsetting143: - AIP of LT indicates CDA is supported but no other authentication methods Procedure:
  • Action: - CRL entry 'xx' is removed and replaced by CRL entry 'yy' from the CRL list before undertaking an EMV transaction. A valid CRL entry is loaded to the device, where the LT Issuer Public Key Certificate in LT is calculated with RID, CA Public Key Index and Certificate Serial Number to correspond to this valid entry. A default acquirer process as documented by the device vendor is performed to update the CRL
  • Transaction is performed with TermSetting1 and LTsetting143 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 in Kernel Data Output: - CDA failed (TVR_B1b3=‘1’). countries. 2CC.122.01 Response to GENERATE AC when responding AAC is in format 1 or 2 (2) Revision: 44b Objective: To ensure that the terminal can use the ICC response format 1 or 2 (as specified in book 3 part I) in Enhanced Combined DDA/AC, when LT responds AAC to GENERATE AC command. Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.4: Terminal [CDA] AND ([Offline Only] OR [Offline/Online Capable]) ICS Options: Conditions:
  • LTsetting1: - AIP indicates CDA is supported
  • LT_response at first GENERATE AC - Cryptogram Information Data ‘9F27’ responding an ARQC (‘80’) and command response is in format 2.
  • Case 01 - LT_response at second GENERATE AC § Cryptogram Information Data ‘9F27’ responding an AAC (‘00’) and command response is in format 1. Procedure:
  • Case 02 - LT_response at second GENERATE AC § Cryptogram Information Data ‘9F27’ responding an AAC (‘00’) and command response is in format 2.
  • Transaction is performed with TermSetting1 and LTsetting1 Pass Criteria:
  • 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: - SDA not used (TVR_B1b7=‘0’). - DDA not used (TVR_B1b4=‘0’).
  • Data received in Kernel Data Output: - Offline Data Authentication was performed (TSI_B1b8=‘1’). countries. 2CC.123.02 Signed Dynamic Application Data Length (3) Revision: 44b Objective: To ensure that the terminal compares the Signed Dynamic Application Data length with the ICC Public Key length for Combined DDA/AC Data Authentication. Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification EMV 4.4: Terminal [Online Only] AND [Normal Default Action Code processing] AND ([CDA ICS Mode1] OR [CDA Mode2]) Options: Conditions:
  • LTsetting1: - AIP indicates CDA is supported
  • LT_response at second GENERATE AC - Length of Signed Dynamic Application Data is different from the ICC Public Key length Procedure:
  • Issuer_response: - The issuer does not respond to online processing request. Terminal unable to go Online.
  • Transaction is performed with TermSetting1 and LTsetting1 Pass Criteria:
  • Data received at first GENERATE AC: - SDA not used (TVR_B1b7=‘0’). - DDA not used (TVR_B1b4=‘0’).
  • Terminal display: 'Declined' message
  • Data received in Kernel Data Output: - Offline Data Authentication was performed (TSI_B1b8=‘1’). - Combined Data Authentication failed (TVR_B1b3=‘1’). countries. 2CC.134.06 Response to GENERATE AC when responding TC or ARQC is not in format 1 (Implied) (2) Revision: 44b Objective: To ensure that the terminal does not use the ICC response format 1 in Enhanced Combined DDA/AC (as specified in book 3 part I) when responding TC or ARQC. Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.4: Terminal [Online Only] AND [CDA Mode1] ICS Options: Conditions:
  • LTsetting107: - AIP indicates CDA is supported
  • Case 01 - LT_response at first GENERATE AC § Cryptogram Information Data ‘9F27’ responding an ARQC (‘80’) in format 1 Procedure:
  • Case 02 - LT_response at first GENERATE AC § Cryptogram Information Data ‘9F27’ responding an ARQC (‘80’) in format 2 - LT_response at second GENERATE AC § Cryptogram Information Data ‘9F27’ responding an TC (‘40’) in format 1
  • Transaction is performed with TermSetting1 and LTsetting107 Pass Criteria:
  • Terminal display: ‘Declined’ OR 'Terminated' message countries. 2CC.134.10 Response to GENERATE AC when responding TC or ARQC is not in format 2 (Implied) (3) Revision: 44b Objective: To ensure that the terminal does not use the ICC response format 1 in Enhanced Combined DDA/AC (as specified in book 3 part I) when responding TC or ARQC. Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.4: Terminal [Online Only] AND [Normal Default Action Code processing] AND ([CDA ICS Mode1] OR [CDA Mode2]) Options: Conditions:
  • LTsetting107: - AIP indicates CDA is supported
  • Case 01 - LT_response at first GENERATE AC § Cryptogram Information Data ‘9F27’ responding an ARQC (‘80’) in format 1 Procedure:
  • Case 02 - LT_response at first GENERATE AC § Cryptogram Information Data ‘9F27’ responding an ARQC (‘80’) in format 2 - LT_response at second GENERATE AC § Cryptogram Information Data ‘9F27’ responding an TC (‘40’) in format 1 - Issuer_response: § The Issuer does not respond to online processing request. Terminal unable to go Online.
  • Transaction is performed with TermSetting1 and LTsetting107 Pass Criteria:
  • Terminal display: ‘Declined’ OR 'Terminated' message countries. 2CC.134.12 Response to GENERATE AC when responding TC or ARQC is not in format 1 (Implied) (3) Revision: 44b Objective: To ensure that the terminal does not use the ICC response format 1 in Enhanced Combined DDA/AC (as specified in book 3 part I) when responding TC or ARQC. Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.4: Terminal [Online Only] AND ([CDA Mode1] OR [CDA Mode4]) ICS Options: Conditions:
  • LTsetting107: - AIP indicates CDA is supported
  • LT_response at first GENERATE AC - Cryptogram Information Data ‘9F27’ responding an ARQC (‘80’) in format 2 Procedure:
  • LT_response at second GENERATE AC - Cryptogram Information Data ‘9F27’ responding an TC (‘40’) in format 1
  • Transaction is performed with TermSetting1 and LTsetting107 Pass Criteria:
  • Terminal display: ‘Declined’ OR 'Terminated' message countries. 2CE.003.00 Recognition of ‘Space’ characters in AN formatted Data Objects Test No: 2CE.003.00 - Revision 44b - Number of sub cases: 0 Objective: To ensure that terminal accepts data objects from the ICC with ‘space’ characters included in AN defined fields. Reference Book 3 - Section 43 - Data Element Format Conventions EMV 4.4: Terminal [Display] AND [Cardholder Confirmation] Configuration (New format): Conditions:
  • LT shall contain the following data objects with at least one ‘space’ character in each data object: - Application Preferred Name. - Application Label.
  • LT shall contain the Issuer Code Table Index. Action: Procedure: Pass Criteria: NA Application in LT is selected and transaction is processed with LT.
  • The terminal shall process the transaction until completion, by requesting a TC at first or second GENERATE AC.
  • The terminal shall display either the ‘Application Preferred Name’ or the ‘Application Label both with the ‘space’ character present countries. 2CE.003.15 Acceptance of format errors on data objects (2) Revision: 44b Objective: The terminal accepts specific data objects from the ICC with format errors, when processing the transaction Reference Book 3 - Section 7.5 – Erroneous or Missing Data in the ICC EMV 4.4: Terminal [NA] ICS Options: Conditions:
  • Case 01 - LTsetting157: § LT contains the Track 1 Discretionary Data with value: 9F1F04C3C6 Procedure:
  • Case 02 - LTsetting158: § LT contains the Track 1 Discretionary Data with value: 9F1F06CED7
  • Case 01: Transaction is performed with TermSetting1 and LTsetting157
  • Case 02: Transaction is performed with TermSetting1 and LTsetting158 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.08 All bits in TSI and TVR are set to 0b (9) Revision: 44b 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.4: Terminal [Offline/Online Capable] OR [Online Only] 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 8 to 7 (Cardholder verification not successful, Unrecognised CVM) and Byte 5 bit 7 to 5 (Issuer Authentication failed, Script processing failed before final GENERATE AC, Script processing failed after final GENERATE AC) and raising the TSI bits: Byte 1 bit 7 to 5, 3 (Cardholder verification was performed, Card risk management was performed, Issuer Authentication was performed, script processing 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 '3032' § Application Usage Control has the value '0000' § Issuer Country Code is returned § CVM List has the value '00000000000000003F00' § IAC-Online has the value '0040000000' - LT_response at All Script commands § SW1SW2: 6984 - LT_response at External Authenticate command § SW1SW2: 6300 - 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: countries. 2CJ.002.08 Procedure: All bits in TSI and TVR are set to 0b (9) § PDOL is present in LT and request the TVR and TSI
  • 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’) § 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') § Script processing failed before final GENERATE AC (TVR_B5b6=‘1’) § Script processing was performed (TSI_B1b3='1') § Issuer Authentication Failed (TVR_B5b7=‘1’) - Data received in Kernel Data Output: § Transaction is approved with a TC: (CID=’40’) § 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. 2

Shown in part. Read the original for the full text.