PCI Watch

Tracking changes across the Payment Card Industry

TTA Bulletin n°286: Terminal Level 2 Test Cases 4.4c Update

v1.0 Type Approval Bulletins
Contact Acceptance Device

countries. EMV® Terminal Type Approval Bulletin No. 286 First Edition, July 2026 Terminal Level 2 Test Cases 4.4c Update

Applicability

This Bulletin applies to:

  • EMV® Terminal Type Approval - Level 2 Test Cases – version 4.4c.r

Related Documents

This Bulletin should be read in conjunction with:

  • EMV® Terminal Type Approval - Level 2 Test Cases – version 4.4c
  • Specification Bulletin 308 - EMV® Contact Chip Features Sunsetting – Phase 1, 2nd Edition

Effective Date

  • July 1st, 2026

Description

Based on EMVCo's continued review of EMV® Terminal Type Approval Level 2 Test Cases v4.4c, 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.4c Section 5 – LT settings [LTSetting195] (differences with LTSetting1) Data Tag Value AEF 01: - Record 02: '70’ ‘9F0E’ (IAC-Denial) ‘0000000000’ ‘9F0F’ (IAC-Online) ‘0000000000’ ‘9F0D’ (IAC-Default) ‘0000000000’ ‘8C’ (CDOL1) ‘95059B029F241D 9F19069F25029F34039F3704 9F40059F33039A039F2103970C9814’ ‘8D’ (CDOL2) ‘95059B029F241D 9F19069F25029F34039F3704 9F40059F33039A039F21038A02970C9814’ ‘9F08’ (Version) ‘3031’

countries.

‘8E’ (CVM List) ‘Any value’ ‘9F07’ (AUC) ‘FFC0’ ‘5F28’ (Issuer Country Code) ‘XXX’ ‘5F20’ (Cardholder Name) ‘4E414D453132333435’ '97' (RFU tag, previously TDOL) '5F24069F280209F30029F3102' [LTSetting196] (differences with LTSetting1) Data Tag Value CDOL1 8C 95059B029F241D9F1906 9F25029F34039F04049F3A04 9F3B029F430181049F3704 CDOL2 8D 95059B029F241D9F1906 9F25029F34039F04049F3A04 9F3B029F430181049F3704 PDOL 9F38 95059B029F33039F04049F3A04 9F3B029F43018104 FCI Template (Select AID): ‘6F’ ‘84’ (DF Name) ‘B000001234’ ‘A5’ ‘50’ (Label) ‘454D56436F25465737’ ‘9F38’ (PDOL) ‘95059B029F3309F0404 9F3A049F3B029F43018104’ '9F04' (Reserved Tag) '00000200' '9F3A' (Reserved Tag) '00001000' '9F3B' (Reserved Tag) '0901' '9F43' (Reserved Tag) '02' '81' (Reserved Tag) '00000100' [LTSetting197] (differences with LTSetting1) Data Tag Value CDOL1 8C 95059B029F241D9F1906 9F25029F34039F04049F3A04 9F3B029F430181049F3704 CDOL2 8D 95059B029F241D9F1906 9F25029F34039F04049F3A04 9F3B029F430181049F3704 PDOL 9F38 95059B029F33039F04049F3A04 9F3B029F43018104 FCI Template (Select AID): ‘6F’

countries.

‘84’ (DF Name) ‘B000001234’ ‘A5’ ‘50’ (Label) ‘454D56436F25465737’ ‘9F38’ (PDOL) ‘95059B029F3309F0404 9F3A049F3B029F43018104’ 'BF0C' (FCI Issuer Discretionary Data) '9F04' (Reserved Tag) '00000200' '9F3A' (Reserved Tag) '00001000' '9F3B' (Reserved Tag) '0901' '9F43' (Reserved Tag) '02' '81' (Reserved Tag) '00000100' [LTSetting198] (differences with LTSetting1) Data Tag Value CDOL1 8C 95059B029F241D9F1906 9F25029F34039F04049F3A04 9F3B029F430181049F3704 CDOL2 8D 95059B029F241D9F1906 9F25029F34039F04049F3A04 9F3B029F430181049F3704 PDOL 9F38 95059B029F33039F04049F3A04 9F3B029F43018104 [LTSetting199] (differences with LTSetting1) Data Tag Value PDOL 9F38 95059B029F33039F04049F3A04 9F3B029F43018104 AEF 01: - Record 02: '70’ ‘9F0E’ (IAC-Denial) ‘0000000000’ ‘9F0F’ (IAC-Online) ‘0000000000’ ‘9F0D’ (IAC-Default) ‘0000000000’ ‘8C’ (CDOL1) ‘95059B029F241D9F1906 9F25029F34039F04049F3A04 9F3B029F430181049F37048D’ (CDOL2) ‘95059B029F241D9F1906 9F25029F34039F04049F3A04 9F3B029F430181049F3704 ‘9F08’ (Version) ‘3031’ ‘8E’ (CVM List) ‘Any value’ ‘9F07’ (AUC) ‘FFC0’ ‘5F28’ (Issuer Country Code) ‘XXX’ ‘5F20’ (Cardholder Name) ‘4E414D453132333435’

countries.

'97' (RFU tag, previously TDOL) '5F24069F280209F30029F3102' '9F04' (Reserved Tag) '00000200' '9F3A' (Reserved Tag) '00001000' '9F3B' (Reserved Tag) '0901' '9F43' (Reserved Tag) '02' '81' (Reserved Tag) '00000100' [LTSetting200] (differences with LTSetting1) Data Tag Value CDOL1 8C 95059B029F241D9F1906 9F25029F34039F04049F3A04 9F3B029F430181049F3704 CDOL2 8D 95059B029F241D9F1906 9F25029F34039F04049F3A04 9F3B029F430181049F3704 PDOL 9F38 95059B029F33039F04049F3A04 9F3B029F43018104 FCI Template (Select PSE): ‘6F’ ‘84’ (DF Name) ‘1PAY.SYS.DDF01’ ‘A5’ ‘88’ (SFI) ‘01’ '9F04' (Reserved Tag) '00000200' '9F3A' (Reserved Tag) '00001000' '9F3B' (Reserved Tag) '0901' '9F43' (Reserved Tag) '02' '81' (Reserved Tag) '00000100' PSE Directory '70' '61' '4F' (ADF Name) ‘B000001234’ ‘50’ (Label) ‘454D56436F25465737’ [LTSetting201] (differences with LTSetting1) Data Tag Value CDOL1 8C 95059B029F241D9F1906 9F25029F34039F04049F3A04 9F3B029F430181049F3704 CDOL2 8D 95059B029F241D9F1906 9F25029F34039F04049F3A04

countries.

9F3B029F430181049F3704 PDOL 9F38 95059B029F33039F04049F3A04 9F3B029F43018104 FCI Template (Select PSE): ‘6F’ ‘84’ (DF Name) ‘1PAY.SYS.DDF01’ ‘A5’ ‘88’ (SFI) ‘01’ PSE Directory '70' '61' '4F' (ADF Name) ‘B000001234’ ‘50’ (Label) ‘454D56436F25465737’ '73' (Directory Discretionary Template) '9F04' (Reserved Tag) '00000200' '9F3A' (Reserved Tag) '00001000' '9F3B' (Reserved Tag) '0901' '9F43' (Reserved Tag) '02' '81' (Reserved Tag) '00000100' [LTSetting202] (differences with LTSetting1): Data Tag Value CVM List 8E 00000000000000000300 [LTSetting203] (differences with LTSetting1): Data Tag Value CVM List 8E 00000000000000000500 [LTSetting204] (differences with LTSetting1): Data Tag Value CVM List 8E 00000000000000000303 [LTSetting205] (differences with LTSetting1): Data Tag Value CVM List 8E 00000000000000000503 [LTSetting206] (differences with LTSetting1): Data Tag Value CVM List 8E 00000000000000000307 [LTSetting207] (differences with LTSetting1):

countries.

Data Tag Value CVM List 8E 00000000000000000508 [LTSetting208] (differences with LTSetting1): Data Tag Value CVM List 8E 00000000000000000306 [LTSetting209] (differences with LTSetting1): Data Tag Value CVM List 8E 00000000000000000509 [LTSetting210] (differences with LTSetting1): Data Tag Value CVM List 8E 00000000000000000304 [LTSetting211] (differences with LTSetting1): Data Tag Value CVM List 8E 00000000000000000504 [LTSetting212] (differences with LTSetting1): Data Tag Value CVM List 8E 00000000000000000301 [LTSetting213] (differences with LTSetting1): Data Tag Value CVM List 8E 00000000000000000501 [LTSetting214] (differences with LTSetting1): Data Tag Value CVM List 8E 00000000000000000305 [LTSetting215] (differences with LTSetting1): Data Tag Value CVM List 8E 00000000000000000505 [LTSetting216] (differences with LTSetting1): Data Tag Value

countries.

CVM List 8E 00000000000000000302 [LTSetting217] (differences with LTSetting1): Data Tag Value CVM List 8E 00000000000000000502 [LTSetting218] (differences with LTSetting1): Data Tag Value CVM List 8E 000000000000000003030000 [LTSetting219] (differences with LTSetting1): Data Tag Value CVM List 8E 000000000000000005030000 [LTSetting220] (differences with LTSetting1) Data Tag Value AIP 82 ‘7C00’ [LTSetting221] (differences with LTSetting1) Data Tag Value AIP 82 ‘7C00’ Expiration Date 5F24 200101 IAC-Online 9F0F 0040000000 [LTSetting222] (differences with LTSetting1) Data Tag Value AID B000001234 CVM List 8E 0000000000000000010304030000 CDOL1 8C 95059B029F241D 9F19069F25029F34039F3704 9F40059F33039A039F21039F3501 [LTSetting223] (differences with LTSetting1) Data Tag Value AID B000001235 CVM List 8E 0000000000000000010304030000 CDOL1 8C 95059B029F241D 9F19069F25029F34039F3704 9F40059F33039A039F21039F3501

countries.

[LTSetting224] (differences with LTSetting1) Data Tag Value FCI Template (Select AID): ‘6F’ ‘84’ (DF Name) ‘B000001234’ ‘A5’ ‘50’ (Label) ‘454D56436F25465737’ ‘9F38’ (PDOL) ‘95059B029F33039F0404 9F3A049F3B029F43018104’ 'BF10' (Payment System Reserved Constructed Tag) '9F500200009F2804AABBCCDD' 'BF0D' (Issuer Specific Constructed Tag) '9F5104000012349F2902CCDD' 'BF20' (EMV Reserved Constructed Tag) '9F4F01019E02CCDD' 'BF0E' (Issuer Specific Constructed Tag) 'BF2108BF11059F52020000' [LTSetting225] (differences with LTSetting1) Data Tag Value FCI Template (Select AID): ‘6F’ ‘84’ (DF Name) ‘B000001234’ ‘A5’ ‘50’ (Label) ‘454D56436F25465737’ ‘9F38’ (PDOL) ‘95059B029F33039F0404 9F3A049F3B029F43018104’ 'BF0C' (FCI Issuer Discretionary Data) 'BF10' (Payment System Reserved Constructed Tag) '9F500200009F2804AABBCCDD' 'BF0D' (Issuer Specific Constructed Tag) '9F5104000012349F2902CCDD' 'BF20' (EMV Reserved Constructed Tag) '9F4F01019E02CCDD' 'BF0E' (Issuer Specific Constructed Tag) 'BF2108BF11059F52020000'

countries.

Section 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 bitmask has the value: B1b8 Offline data authentication was not performed 0 B1b7 SDA failed SDA and DDA = NO 1 B1b6 ICC data missing 0 B1b5 Card appears on terminal exception file Exception File = NO 1 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 different application versions 0 B2b7 Expired application 0 B2b6 Application not yet effective 0 B2b5 Requested service not allowed for card product 0 B2b4 New card Velocity Checking = NO 1 B2b3 RFU Always set 1 B2b2 RFU or Biometric not performed or not successful Biometric = No 1 B2b1 RFU or Biometric template format supported Biometric = No 1 B3b8 Cardholder verification was not successful 0 B3b7 Unrecognised CVM 0 B3b6 PIN Try Limit exceeded Offline Enciphered PIN AND Plaintext PIN = NO 1 B3b5 PIN entry required and PIN pad not present or not working 0 B3b4 PIN entry required, PIN pad present, but PIN was not entered Offline Enciphered PIN AND Plaintext PIN AND Online Enciphered PIN = NO 1 B3b3 Online PIN entered Online Enciphered PIN = NO 1 B3b2 RFU or Biometric required but Biometric capture device not working Biometric = No 1

countries.

B3b1 RFU or Biometric required, Biometric capture device present, but Biometric Subtype entry was bypassed Biometric = No 1 B4b8 Transaction exceeds floor limit Floor Limit Checking = NO 1 B4b7 Lower consecutive offline limit exceeded Velocity Checking = NO 1 B4b6 Upper consecutive offline limit exceeded Velocity Checking = NO 1 B4b5 Transaction selected randomly for online processing Random Transaction Selection = NO 1 B4b4 Merchant forced transaction online 0 B4b3 RFU or Biometric Try Limit not exceeded Biometric = No 1 B4b2 RFU or A selected Biometric Type not supported Biometric = No 1 B4b1 XDA not failed XDA = No 1 B5b8 RFU Always set 0 B5b7 Issuer authentication failed 0 B5b6 Script processing failed before final GENERATE AC 0 B5b5 Script processing failed after final GENERATE AC 0 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 - 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 LT Data setting bitmask has the value:

countries.

B1b8 Offline data authentication was not performed 0 B1b7 SDA failed AIP States SDA is not supported 1 B1b6 ICC data missing All Mandatory Data present in LT 1 B1b5 Card appears on terminal exception file 0 B1b4 DDA failed AIP States DDA is not supported 1 B1b3 CDA failed AIP States CDA is not supported 1 B1b2 SDA Selected AIP States SDA is not supported 1 B1b1 XDA Selected AIP States XDA is not supported 1 B2b8 ICC and terminal have different application versions ICC application version not present in LT 1 B2b7 Expired application 0 B2b6 Application not yet effective Effective Data not present in LT 1 B2b5 Requested service not allowed for card product (AUC not present in LT) OR (AUC value = ‘FFC0’) 1 B2b4 New card (ATC different from ‘0’) OR (LOATC # ‘0’) OR (LCOL AND UCOL not present) 1 B2b3 RFU 0 B2b2 RFU or Biometric not performed or not successful 0 B2b1 RFU or Biometric template format supported 0 B3b8 Cardholder verification was not successful AIP states Cardholder Verification is not supported 1 B3b7 Unrecognised CVM (AIP states Cardholder Verification is not supported) OR (CVM list uses only EMVCo recognized Code) 1 B3b6 PIN Try Limit exceeded (AIP states Cardholder Verification is not supported) OR (CVM list does not contain Offline Enciphered PIN AND Plaintext PIN) 1 B3b5 PIN entry required and PIN pad not present or not working (AIP states Cardholder Verification is not supported) OR (CVM list does not contain any PIN) 1 B3b4 PIN entry required, PIN pad present, but PIN was not entered (AIP states Cardholder Verification is not supported) OR (CVM list does not contain any PIN) 1 B3b3 Online PIN entered (AIP states Cardholder Verification is not supported) OR (CVM List does not contain Online PIN) 1 B3b2 RFU or Biometric required but Biometric capture device not working 0 B3b1 RFU or Biometric required, Biometric capture device present, but Biometric Subtype 0

countries.

entry was bypassed B4b8 Transaction exceeds floor limit 0 B4b7 Lower consecutive offline limit exceeded Lower consecutive offline limit not present in LT 1 B4b6 Upper consecutive offline limit exceeded Upper consecutive offline limit not present in LT 1 B4b5 Transaction selected randomly for online processing 0 B4b4 Merchant forced transaction online 0 B4b3 RFU or Biometric Try Limit not exceeded 0 B4b2 RFU or A selected Biometric Type not supported 0 B4b1 XDA not Failed AIP States XDA is not supported 1 B5b8 RFU 0 B5b7 Issuer authentication failed 0 B5b6 Script processing failed before final GENERATE AC 0 B5b5 Script processing failed after final GENERATE AC 0 B5b4 RFU 0 B5b3 RFU 0 B5b2 RFU 0 B5b1 RFU 0 TVR Transaction-bitmask All bits of the Transaction-bitmask shall be set to zero for the time being. TVR TVR Name LT Data setting bitmask has the value: B1b8 Offline data authentication was not performed 0 B1b7 SDA failed 0 B1b6 ICC data missing 0 B1b5 Card appears on terminal exception file 0 B1b4 DDA failed 0 B1b3 CDA failed 0 B1b2 SDA Selected 0 B1b1 XDA Selected 0 B2b8 ICC and terminal have different application versions 0 B2b7 Expired application 0 B2b6 Application not yet effective 0 B2b5 Requested service not allowed for card product 0 B2b4 New card 0 B2b3 RFU 0

countries.

B2b2 RFU or Biometric not performed or not successful 0 B2b1 RFU or Biometric template format supported 0 B3b8 Cardholder verification was not successful 0 B3b7 Unrecognised CVM 0 B3b6 PIN Try Limit exceeded 0 B3b5 PIN entry required and PIN pad not present or not working 0 B3b4 PIN entry required, PIN pad present, but PIN was not entered 0 B3b3 Online PIN entered 0 B3b2 RFU or Biometric required but Biometric capture device not working 0 B3b1 RFU or Biometric required, Biometric capture device present, but Biometric Subtype entry was bypassed 0 B4b8 Transaction exceeds floor limit 0 B4b7 Lower consecutive offline limit exceeded 0 B4b6 Upper consecutive offline limit exceeded 0 B4b5 Transaction selected randomly for online processing 0 B4b4 Merchant forced transaction online 0 B4b3 RFU or Biometric Try Limit not exceeded 0 B4b2 RFU or A selected Biometric Type not supported 0 B4b1 RFU 0 B5b8 RFU 0 B5b7 Issuer authentication failed 0 B5b6 Script processing failed before final GENERATE AC 0 B5b5 Script processing failed after final GENERATE AC 0 B5b4 RFU 0 B5b3 CA ECC key missing 0 B5b2 ECC key recovery failed 0 B5b1 RFU 0

countries.

Section 7 – Test Cases Updates New test cases include: 2CA.041.07 2CA.119.09 2CA.119.10 2CA.119.11 2CA.119.12 2CA.119.13 2CA.122.26 2CA.122.27 2CA.122.28 2CJ.095.24 2CJ.095.25 2CJ.095.26 2CJ.095.27 2CJ.095.28 2CJ.095.29 2CM.020.02 2CA.122.29 2CA.124.04 2CA.124.05 Revised test cases include: 2CA.013.00 2CA.014.00 2CA.015.00 2CA.015.02 2CA.016.00 2CA.017.00 2CA.018.00 2CA.020.00 2CA.021.00 2CA.119.03 2CA.119.04 2CA.119.05 2CA.119.06 2CA.119.08 2CA.122.00 2CA.122.01 2CA.122.02 2CA.122.03 2CA.122.04 2CA.122.05 2CA.122.06 2CA.122.07 2CA.122.08 2CA.122.09 2CA.122.10 2CA.122.11 2CA.122.12 2CA.122.13 2CA.122.14 2CA.122.15 2CA.122.16 2CA.122.17 2CA.122.18 2CA.122.19 2CA.122.20 2CA.122.21 2CA.122.22 2CA.122.23 2CA.122.24 2CA.122.25 2CA.123.00 2CA.123.01 2CB.031.11 2CJ.085.00 2CJ.087.02 2CM.020.01 2CM.024.02 2CM.024.03 Deleted test cases include: 2CC.097.00 2CJ.002.14 2CJ.083.05 2CJ.083.06 2CJ.090.00 2CJ.090.01 2CJ.090.02 2CJ.090.03 2CJ.090.04 2CJ.090.05 2CJ.090.06 2CJ.090.07 2CJ.090.08 2CJ.090.09 2CJ.090.10 2CJ.090.11 2CJ.092.00 2CJ.092.01 2CJ.092.02 2CJ.092.03 2CJ.092.04 2CJ.092.05 2CJ.092.06 2CJ.092.07 2CJ.092.08 2CJ.092.09 2CJ.092.10 2CJ.092.11 2CJ.114.00 2CJ.114.01 2CJ.115.00 2CJ.115.02 2CJ.115.03 2CJ.115.04 2CK.003.00 2CK.004.00 2CK.004.01 2CK.004.02 2CK.004.03 2CK.005.00 2CK.005.01 2CK.005.02 2CK.006.00 2CM.130.00 2CM.130.01 2CM.130.02

countries.

2CA.013.00 Processing DOLs: unknown tag Test No: 2CA.013.00 - Revision 44d - Number of sub cases: 3 Objective: To verify that whenever the tag of any data object identified in the DOL is unknown to the terminal, the IUT provides a data element with the length specified and a value of all hexadecimal zeroes. Reference EMV 4.4: Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) Terminal Configuration (New format): [NA] Conditions:

  • Case 01: The PDOL of LT contains a Data Object with an unknown tag to the terminal
  • Case 02: The CDOL1 of LT contains a Data Object with an unknown tag to the terminal
  • Case 03: The CDOL2 of LT contains a Data Object with an unknown tag to the terminal and LT request ARQC on first Generate AC Action: NA Procedure: Application in LT is selected and transaction is performed with LT (in particular the DOL processing). Pass Criteria: The LT shall receive the DOL with portion of the DOL field representing the Data Object filled with hexadecimal zeroes (portion has the same length as the Data Object in DOL). countries. 2CA.014.00 Processing DOLs: constructed tag Test No: 2CA.014.00 - Revision 44d - Number of sub cases: 3 Objective: To verify that whenever the tag of any data object identified in the DOL represents a constructed data object, the IUT provides a data element with the length specified and a value of all hexadecimal zeroes. Reference EMV 4.4: Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) Terminal Configuration (New format): [NA] Conditions:
  • Case 01: The PDOL of LT contains a constructed Data Object
  • Case 02: The CDOL1 of LT contains a constructed Data Object
  • Case 03: The CDOL2 of LT contains a constructed Data Object and LT request ARQC on first Generate AC Action: NA Procedure: Application in LT is selected and transaction is performed with LT (in particular the DOL processing). Pass Criteria: The LT shall receive the DOL with portion of the DOL field representing the Data Object filled with hexadecimal zeroes (portion has the same length as the Data Object in DOL). countries. 2CA.015.00 Processing DOLs: data absent from ICC Test No: 2CA.015.00 - Revision 44d - Number of sub cases: 4 Objective: To verify that whenever a data object is in the list and is meaningful to the IUT but represents optional static data absent from the ICC, the portion of the command field corresponding is filled with hexadecimal zeroes Reference EMV 4.4: Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) Terminal Configuration (New format): [NA] Conditions:
  • Case 01: In addition to the default values the CDOL1 of LT contains an optional ICC static data that is absent from the LT (for example the Issuer Action Code – Default, tag ‘9F0D’), this data is located in the middle of the CDOL1.
  • Case 02: In addition to the default values the CDOL2 of LT contains an optional ICC static data that is absent from the LT and LT request ARQC on first GENERATE AC (for example the Issuer Action Code – Default, tag ‘9F0D’), this data is located in the middle of the CDOL2.
  • Case 04: In addition to the default values the CDOL1 of LT contains an optional ICC static data that is absent from the LT (for example the Issuer Action Code – Default, tag ‘9F0D’), this data is the last in the CDOL.
  • Case 05: In addition to the default values the CDOL2 of LT contains an optional ICC static data that is absent from the LT and LT request ARQC on first GENERATE AC (for example the Issuer Action Code – Default, tag ‘9F0D’), this data is the last in the CDOL.
  • Action: NA Procedure: Application in LT is selected and transaction is performed with LT (in particular the DOL processing). Pass Criteria:
  • The LT shall receive the DOL with portion of the DOL field representing the Data Object filled with hexadecimal zeroes (portion has the same length as the Data Object in DOL). countries. 2CA.015.02 Processing DOLs: data absent from Terminal Test No: 2CA.015.02 - Revision 44d - Number of sub cases: 6 Objective: To verify that whenever a data object is in the list and is meaningful to the IUT but represents optional static data absent from the terminal, the portion of the command field corresponding is filled with hexadecimal zeroes Reference EMV 4.4: Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) Terminal Configuration (New format): [TRMDabsent] Conditions:
  • Case 01: In addition to the default values the CDOL1 of LT contains an optional terminal data that is absent: Terminal Risk Management Data ‘9F1D’, this data is located in the middle of the CDOL1.
  • Case 02: In addition to the default values the CDOL2 of LT contains an optional terminal data that is absent: Terminal Risk Management Data ‘9F1D’, this data is located in the middle of the CDOL2.
  • Case 04: In addition to the default values the CDOL1 of LT contains an optional terminal data that is absent: Terminal Risk Management Data ‘9F1D’, this data is the last in the CDOL.
  • Case 05: In addition to the default values the CDOL2 of LT contains an optional terminal data that is absent: Terminal Risk Management Data ‘9F1D’, this data is the last in the CDOL.
  • Case 07: The PDOL of LT contains the same data as the default values of CDOL2 and an optional terminal data that is absent and located in the middle of the PDOL: Terminal Risk Management Data ‘9F1D’.
  • Case 08: The PDOL of LT contains the same data as the default values of CDOL2 and an optional terminal data that is absent and located at the end of the PDOL: Terminal Risk Management Data ‘9F1D’. Action: NA Procedure: Application in LT is selected and transaction is performed with LT (in particular the DOL processing). Pass Criteria:
  • The LT shall receive the DOL with portion of the DOL field representing the Data Object filled with hexadecimal zeroes (portion has the same length as the Data Object in DOL). countries. 2CA.016.00 Processing DOLs: shorter data object length, numeric format Test No: 2CA.016.00 - Revision 44d - Number of sub cases: 3 Objective: To verify that whenever the length specified in the DOL entry is less than the length of the actual data object, leftmost bytes of the data element are truncated if the data object has numeric format. Reference EMV 4.4: Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) Terminal Configuration (New format): [NA] Conditions:
  • Case 01: The PDOL of LT contains a data object which has numeric format and a length shorter than actual Data Object Length
  • Case 02: The CDOL1 of LT contains a data object which has numeric format and a length shorter than actual Data Object Length
  • Case 03: The CDOL2 of LT contains a data object which has numeric format and a length shorter than actual Data Object Length. LT request an ARQC on First GENERATE AC Action: NA Procedure: Application in LT is selected and transaction is performed with LT (in particular the DOL processing). Pass Criteria: The LT shall receive the DOL with portion of the DOL field representing the Data Object correctly truncated (portion has the same length as the Data Object in DOL). countries. 2CA.017.00 Processing DOLs: shorter data object length, other format Test No: 2CA.017.00 - Revision 44d - Number of sub cases: 3 Objective: To verify that whenever the length specified in the DOL entry is less than the length of the actual data object, rightmost bytes of the data element are truncated if the data object has any other format (including compressed numeric) than numeric. Reference EMV 4.4: Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) Terminal Configuration (New format): [NA] Conditions:
  • Case 01: The PDOL of LT contains data objects which has format an, ans and b and lengths shorter than actual Data Objects Length
  • Case 02: The CDOL1 of LT contains data objects which has format an, ans, cn and b and lengths shorter than actual Data Objects Length
  • Case 03: The CDOL2 of LT contains data objects which has format an, ans, cn and b and lengths shorter than actual Data Objects Length. LT request an ARQC on first GENERATE AC Action: NA Procedure: Application in LT is selected and transaction is performed with LT (in particular the DOL processing). Pass Criteria: The LT shall receive the DOL with portion of the DOL field representing the Data Object correctly truncated (portion has the same length as the Data Object in DOL). countries. 2CA.018.00 Processing DOLs: longer data object length, numeric format Test No: 2CA.018.00 - Revision 44d - Number of sub cases: 3 Objective: To verify that whenever the length specified in the DOL entry is greater than the length of the actual data object, the actual data is padded with leading hexadecimal zeroes if the data object has numeric format. Reference EMV 4.4: Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) Terminal Configuration (New format): [NA] Conditions:
  • Case 01: The PDOL of LT contains a data object which has numeric format and a length longer than actual Data Object Length
  • Case 02: The CDOL1 of LT contains a data object which has numeric format and a length longer than actual Data Object Length
  • Case 03: The CDOL2 of LT contains a data object which has numeric format and a length longer than actual Data Object Length. LT request an ARQC on first GENERATE AC Action: NA Procedure: Application in LT is selected and transaction is performed with LT (in particular the DOL processing). Pass Criteria: The LT shall receive the DOL with portion of the DOL field representing the Data Object correctly padded with leading hexadecimal zeroes (portion has the same length as the Data Object in DOL) countries. 2CA.020.00 Processing DOLs: longer data object length, other format Test No: 2CA.020.00 - Revision 44d - Number of sub cases: 4 Objective: To verify that whenever the length specified in the DOL entry is greater than the length of the actual data object, the actual data is padded with trailing hexadecimal zeroes for any other format than numeric or compressed numeric. Reference EMV 4.4: Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) Terminal Configuration (New format): [NA] Conditions:
  • Case 01: The PDOL of LT contains data objects which has format an (IFD Serial Number, ‘9F1E’), ans (Merchant Identifier, ‘9F16’) and b (Additional Terminal Capabilities, ‘9F40’) and lengths longer than actual Data Objects Length.
  • Case 02: The CDOL1 of LT data objects which has format an (IFD Serial Number, ‘9F1E’), ans (Merchant Identifier, ‘9F16’) and b (Transaction Status Information, ‘9B’).
  • Case 03: The CDOL2 of LT contains data objects which has format an (IFD Serial Number, ‘9F1E’), ans (Merchant Identifier, ‘9F16’) and b (Transaction Status Information, ‘9B’).
  • Case 05: The CDOL2 of LT contains Issuer Authentication Data Object with a length longer than actual Data Object Length (for example: Issuer Authentication Data has a length of 12 bytes and length declared in CDOL2 is 14). Action: NA Procedure: Application in LT is selected and transaction is performed with LT (in particular the DOL processing). Pass Criteria: The LT shall receive the DOL with portion of the DOL field representing the Data Object correctly padded with trailing hexadecimal zeroes (portion has the same length as the Data Object in DOL). countries. 2CA.021.00 Processing DOLs: data not applicable Test No: 2CA.021.00 - Revision 44d - Number of sub cases: 3 Objective: To verify that whenever a data object is in the list and is meaningful to the Terminal but is not applicable to the current transaction, the portion of the command field corresponding is filled with hexadecimal zeroes Reference EMV 4.4: Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) Terminal Configuration (New format): [NA] Conditions:
  • LCOLL and UCOLL are not present in LT
  • Case 01: The PDOL of LT requests the LATC
  • Case 02: The CDOL1 of LT requests the LATC
  • Case 03: The CDOL2 of LT requests the LATC Action: NA Procedure: Application in LT is selected and transaction is performed with LT (in particular the DOL processing). Pass Criteria: The LT shall receive the DOL with portion of the DOL field representing the Data Object filled with hexadecimal zeroes (portion has the same length as the Data Object in DOL). countries. 2CA.041.07 Coding of Bits and Bytes RFU (8) Revision: 44d Objective: To ensure that the terminal sets to zeroes data (bits and bytes) indicated as RFU, unless otherwise stated. This applies to TVR B5b8, Reference EMV 4.4: Book Bulletins - Section SB 308 - Bulletin n°308; 2nd Ed, Contact Chip Features Sunsetting - Phase 1 Terminal ICS Options: [SB308] Conditions: TVR is 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_B5b8=‘0’). countries. 2CA.119.03 Data order in template for First GENERATE AC Command (format 2) without CDA Revision: 44d Objective: To ensure that the terminal accepts a response to GENERATE AC command in an order different from example given in EMV Specifications. Reference EMV 4.4: Book 3 - Section 6.5.5.4 - Data Field Sent in the Command Message Terminal ICS Options: [NA] Conditions:
  • LT_response at first GENERATE AC (data in this order in format 2) - Issuer Application Data ‘9F10’. - Application Cryptogram ‘9F26’ - Cryptogram Information Data ‘9F27’ - Application transaction Counter ‘9F36’,
  • LTsetting220: - AIP indicates CDA is not supported Procedure:
  • Transaction is performed with TermSetting1 and LTsetting220 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: - Issuer Application Data ‘9F10’ shall have the same value as the one in the LTsetting220, - Offline data authentication was performed (TVR_B1b8=‘0’) - Cryptogram Information Data ‘9F27’ = TC (‘40’),
  • Terminal display: ‘Approved' message countries. 2CA.119.04 Data order in template for First GENERATE AC Command (format 2) without CDA Revision: 44d Objective: To ensure that the terminal accepts a response to GENERATE AC command in an order different from example given in EMV Specifications. Reference EMV 4.4: Book 3 - Section 6.5.5.4 - Data Field Sent in the Command Message Terminal ICS Options: [Online Only] OR [Offline/Online Capable] Conditions:
  • LT_response at second GENERATE AC (data in this order in format 2) - Issuer Application Data ‘9F10’. - Application Cryptogram ‘9F26’ - Cryptogram Information Data ‘9F27’ responding a TC (‘40’), - Application transaction Counter ‘9F36’,
  • LTsetting221: - AIP indicates CDA is not supported - Expiration Date has the value '200101', - IAC-Online has the value '0040000000'. Procedure:
  • Transaction is performed with TermSetting1 and LTsetting221 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 Kernel Data Output: - Issuer Application Data ‘9F10’ shall have the same value as the one in the LTsetting221, - Offline data authentication was performed (TVR_B1b8=‘0’) - Cryptogram Information Data ‘9F27’ = TC (‘40’),
  • Terminal display: ‘Approved' message countries. 2CA.119.05 Data order in template for First GENERATE AC Command (format 2) with CDA Revision: 44d Objective: To ensure that the terminal accepts a response to GENERATE AC command in an order different from example given in EMV Specifications. Reference EMV 4.4: Book 2 - Section 6.6.1 Dynamic Signature Generation Book 3 - Section 6.5.5.4 - Data Field Sent in the Command Message Terminal ICS Options: [CDA] AND ([Offline Only] OR [Offline/Online Capable] Conditions:
  • LT_response at first GENERATE AC (data in this order in format 2) - Issuer Application Data ‘9F10’. - Signed Dynamic Application data ‘9F4B’ - Cryptogram Information Data ‘9F27’ responding a TC (‘40’), - Application transaction Counter ‘9F36’,
  • LTsetting1: - AIP indicates CDA is supported Procedure:
  • 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 with CDA (P1_b8='0' AND P1_b7=‘1’ AND P1_b5='1' AND P1_b4='0'),
  • Data received in Kernel Data Output: - Issuer Application Data ‘9F10’ shall have the same value as the one in the LTsetting1, - Offline Data Authentication was performed (TSI_B1b8=‘1’), - Offline data authentication was performed (TVR_B1b8=‘0’) - CDA not failed (TVR_B1b3=‘0’) - Cryptogram Information Data ‘9F27’ = TC (‘40’),
  • Terminal display: ‘Approved' message countries. 2CA.119.06 Data order in template for Second GENERATE AC Command (format 2) with CDA Revision: 44d Objective: To ensure that the terminal accepts a response to GENERATE AC command in an order different from example given in EMV Specifications. Reference EMV 4.4: Book 2 - Section 6.6.1 Dynamic Signature Generation Book 3 - Section 6.5.5.4 - Data Field Sent in the Command Message Terminal ICS Options: ([CDA Mode1] OR [CDA Mode4]) AND ([Online Only] OR [Offline/Online Capable]) Conditions:
  • LT_response at second GENERATE AC (data in this order in format 2) - Signed Dynamic Application data ‘9F4B’, - Application transaction Counter ‘9F36’, - Cryptogram Information Data ‘9F27’ responding a TC (‘40’), - Issuer Application Data ‘9F10’.
  • LTsetting107: - AIP indicates CDA is supported, - Expiration Date has the value '200101', - IAC-Online has the value '0040000000'. Procedure:
  • Transaction is performed with TermSetting1 and LTsetting107 Pass Criteria:
  • Parameter received at second GENERATE AC: - The terminal shall process the transaction until completion, by requesting a TC with CDA (P1_b8='0' AND P1_b7=‘1’ AND P1_b5='1' AND P1_b4='0')
  • Data received in Kernel Data Output: - Issuer Application Data ‘9F10’ shall have the same value as the one in the LTsetting107, - Offline Data Authentication was performed (TSI_B1b8=‘1’), - CDA not failed (TVR_B1b3=‘0’) - Cryptogram Information Data ‘9F27’ = TC (‘40’),
  • Terminal display: ‘Approved' message countries. 2CA.119.08 Data order in template for First GENERATE AC Command (format 2) with CDA (2) Revision: 44d Objective: To ensure that the terminal accepts a response to GENERATE AC command in an order different from example given in EMV Specifications. Reference EMV 4.4: Book 2 - Section 6.6.1 Dynamic Signature Generation Book 3 - Section 6.5.5.4 - Data Field Sent in the Command Message Terminal ICS Options: ([CDA Mode1] OR [CDA Mode2]) AND [Online Only] Conditions:
  • LT_response at first GENERATE AC (data in this order in format 2) - Issuer Application Data ‘9F10’. - Signed Dynamic Application data ‘9F4B’, - Cryptogram Information Data ‘9F27’ responding an ARQC (‘80’), - Application transaction Counter ‘9F36’,
  • LTsetting107: - AIP indicates CDA is supported, - Expiration Date has the value '200101', - IAC-Online has the value '0040000000'. Procedure:
  • Transaction is performed with TermSetting1 and LTsetting107 Pass Criteria:
  • Parameter received at first GENERATE AC: - The terminal shall process the transaction until completion, by requesting an ARQC with CDA (P1_b8='1' AND P1_b7=‘0’ AND P1_b5='1' AND P1_b4='0')
  • 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 Kernel Data Output: - Issuer Application Data ‘9F10’ shall have the same value as the one in the LTsetting107, - Offline Data Authentication was performed (TSI_B1b8=‘1’), - Offline data authentication was performed (TVR_B1b8=‘0’) - CDA not failed (TVR_B1b3=‘0’) - Cryptogram Information Data ‘9F27’ = TC (‘40’),
  • Terminal display: ‘Approved' message countries. 2CA.119.09 Data order in template for First GENERATE AC Command (format 2) without CDA (2) Revision: 44d Objective: To ensure that the terminal accepts a response to GENERATE AC command in an order different from example given in EMV Specifications. Reference EMV 4.4: Book 3 - Section 6.5.5.4 - Data Field Sent in the Command Message Terminal ICS Options: [NA] Conditions:
  • LT_response at first GENERATE AC (data in this order in format 2) - Application transaction Counter ‘9F36’, - Application Cryptogram ‘9F26’ - Issuer Application Data ‘9F10’. - Cryptogram Information Data ‘9F27’,
  • LTsetting220: - AIP indicates CDA is not supported Procedure:
  • Transaction is performed with TermSetting1 and LTsetting220 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: - Issuer Application Data ‘9F10’ shall have the same value as the one in the LTsetting220, - Offline data authentication was performed (TVR_B1b8=‘0’) - Cryptogram Information Data ‘9F27’ = TC (‘40’),
  • Terminal display: ‘Approved' message countries. 2CA.119.10 Data order in template for First GENERATE AC Command (format 2) without CDA (2) Revision: 44d Objective: To ensure that the terminal accepts a response to GENERATE AC command in an order different from example given in EMV Specifications. Reference EMV 4.4: Book 3 - Section 6.5.5.4 - Data Field Sent in the Command Message Terminal ICS Options: [Online Only] OR [Offline/Online Capable] Conditions:
  • LT_response at second GENERATE AC (data in this order in format 2) - Application transaction Counter ‘9F36’, - Issuer Application Data ‘9F10’. - Application Cryptogram ‘9F26’ - Cryptogram Information Data ‘9F27’ responding a TC (‘40’),
  • LTsetting221: - AIP indicates CDA is not supported - Expiration Date has the value '200101', - IAC-Online has the value '0040000000'. Procedure:
  • Transaction is performed with TermSetting1 and LTsetting221 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 Kernel Data Output: - Issuer Application Data ‘9F10’ shall have the same value as the one in the LTsetting221, - Offline data authentication was performed (TVR_B1b8=‘0’) - Cryptogram Information Data ‘9F27’ = TC (‘40’),
  • Terminal display: ‘Approved' message countries. 2CA.119.11 Data order in template for First GENERATE AC Command (format 2) with CDA (2) Revision: 44d Objective: To ensure that the terminal accepts a response to GENERATE AC command in an order different from example given in EMV Specifications. Reference EMV 4.4: Book 2 - Section 6.6.1 Dynamic Signature Generation Book 3 - Section 6.5.5.4 - Data Field Sent in the Command Message Terminal ICS Options: [CDA] AND ([Offline Only] OR [Offline/Online Capable] Conditions:
  • LT_response at first GENERATE AC (data in this order in format 2) - Application transaction Counter ‘9F36’, - Signed Dynamic Application data ‘9F4B’ - Issuer Application Data ‘9F10’. - Cryptogram Information Data ‘9F27’ responding a TC (‘40’),
  • LTsetting1: - AIP indicates CDA is supported Procedure:
  • 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 with CDA (P1_b8='0' AND P1_b7=‘1’ AND P1_b5='1' AND P1_b4='0'),
  • Data received in Kernel Data Output: - Issuer Application Data ‘9F10’ shall have the same value as the one in the LTsetting1, - Offline Data Authentication was performed (TSI_B1b8=‘1’), - Offline data authentication was performed (TVR_B1b8=‘0’) - CDA not failed (TVR_B1b3=‘0’) - Cryptogram Information Data ‘9F27’ = TC (‘40’),
  • Terminal display: ‘Approved' message countries. 2CA.119.12 Data order in template for Second GENERATE AC Command (format 2) with CDA (3) Revision: 44d Objective: To ensure that the terminal accepts a response to GENERATE AC command in an order different from example given in EMV Specifications. Reference EMV 4.4: Book 2 - Section 6.6.1 Dynamic Signature Generation Book 3 - Section 6.5.5.4 - Data Field Sent in the Command Message Terminal ICS Options: ([CDA Mode1] OR [CDA Mode4]) AND ([Online Only] OR [Offline/Online Capable]) Conditions:
  • LT_response at second GENERATE AC (data in this order in format 2) - Application transaction Counter ‘9F36’, - Issuer Application Data ‘9F10’, - Signed Dynamic Application data ‘9F4B’, - Cryptogram Information Data ‘9F27’ responding a TC (‘40’).
  • LTsetting107: - AIP indicates CDA is supported, - Expiration Date has the value '200101', - IAC-Online has the value '0040000000'. Procedure:
  • Transaction is performed with TermSetting1 and LTsetting107 Pass Criteria:
  • Parameter received at second GENERATE AC: - The terminal shall process the transaction until completion, by requesting a TC with CDA (P1_b8='0' AND P1_b7=‘1’ AND P1_b5='1' AND P1_b4='0')
  • Data received in Kernel Data Output: - Issuer Application Data ‘9F10’ shall have the same value as the one in the LTsetting107, - Offline Data Authentication was performed (TSI_B1b8=‘1’), - Offline data authentication was performed (TVR_B1b8=‘0’) - CDA not failed (TVR_B1b3=‘0’) - Cryptogram Information Data ‘9F27’ = TC (‘40’),
  • Terminal display: ‘Approved' message countries. 2CA.119.13 Data order in template for First GENERATE AC Command (format 2) with CDA (4) Revision: 44d Objective: To ensure that the terminal accepts a response to GENERATE AC command in an order different from example given in EMV Specifications. Reference EMV 4.4: Book 2 - Section 6.6.1 Dynamic Signature Generation Book 3 - Section 6.5.5.4 - Data Field Sent in the Command Message Terminal ICS Options: ([CDA Mode1] OR [CDA Mode2]) AND [Online Only] Conditions:
  • LT_response at first GENERATE AC (data in this order in format 2) - Signed Dynamic Application data ‘9F4B’, - Application transaction Counter ‘9F36’, - Issuer Application Data ‘9F10’. - Cryptogram Information Data ‘9F27’ responding an ARQC (‘80’),
  • LTsetting107: - AIP indicates CDA is supported, - Expiration Date has the value '200101', - IAC-Online has the value '0040000000'. Procedure:
  • Transaction is performed with TermSetting1 and LTsetting107 Pass Criteria:
  • Parameter received at first GENERATE AC: - The terminal shall process the transaction until completion, by requesting an ARQC with CDA (P1_b8='1' AND P1_b7=‘0’ AND P1_b5='1' AND P1_b4='0')
  • 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 Kernel Data Output: - Issuer Application Data ‘9F10’ shall have the same value as the one in the LTsetting107, - Offline Data Authentication was performed (TSI_B1b8=‘1’), - Offline data authentication was performed (TVR_B1b8=‘0’) - CDA not failed (TVR_B1b3=‘0’) - Cryptogram Information Data ‘9F27’ = TC (‘40’),
  • Terminal display: ‘Approved' message countries. 2CA.122.00 Payment System reserved Data objects processing Test No: 2CA.122.00 - Revision 44d - Number of sub cases: 7 Objective: To ensure that the terminal ignores Payment System reserved Data Objects when the selected AID is not an Payment System AID. Reference EMV 4.4: Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects Terminal Configuration (New format): [NA] Conditions:
  • LT AID value is B000001234
  • Terminal AID Value is B000001234
  • PDOL, CDOL1 and CDOL2 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
  • 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. 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 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.01 Payment System reserved Data objects processing (2) Test No: 2CA.122.01 - Revision 44d - Number of sub cases: 5 Objective: To ensure that the terminal ignores Payment System reserved Data Objects when the selected AID is not an Payment System AID. Reference EMV 4.4: Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects Terminal Configuration (New format): [PSE] Conditions:
  • LT AID value is B000001234
  • Terminal AID Value is B000001234
  • PDOL, CDOL1 and CDOL2 of LT contains all reserved tags in the range '9F50' to '9F7F'.
  • PSE contains a directory file with entries for ADF.
  • Case 01: FCI Issuer discretionary Data (tag BF0C) of PSE contains additionally all reserved tags in the range '9F50' to '9F6A’ with values different from zero.
  • Case 02: FCI (tag 6F) of PSE contains additionally all reserved tags in the range '9F50' to '9F6A’ with values different from zero.
  • Case 03: Template '73' of ADF Directory Entry contains additionally all reserved tags in the range '9F50' to '9F7F’ with values different from zero.
  • Case 04: FCI Issuer discretionary Data (tag BF0C) of PSE contains additionally all reserved tags in the range '9F6B' to '9F7F’ with values different from zero.
  • Case 05: FCI (tag 6F) of PSE contains additionally all reserved tags in the range '9F50' to '9F6B’ with values different from zero. 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.
  • Values of the reserved tags in the range '9F50' to '9F7F' received by the LT via the DOLs are set to “00’ (Note: for countries. 2CA.122.01 Payment System reserved Data objects processing (2) CDOL2 this is applicable only if a 2nd GENERATE AC has been performed) countries. 2CA.122.02 EMV reserved Data objects processing (3) Test No: 2CA.122.02 – Revision 44d – Number of sub cases: 5 Objective: To ensure that the terminal ignores EMV reserved Data Objects (not used by EMV). Reference EMV 4.4: Book 3 – Section Annex B1 Coding of the Tag Field of BER-TLV Data Objects Book 3 - Section Annex A2 – Data Elements by tag Terminal Configuration (New format): [NA] Conditions:
  • LT AID value is B000001234
  • Terminal AID Value is B000001234
  • PDOL, CDOL1 and CDOL2 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' (excluding '9F04', '9F3A', 9F3B', '9F43', '81', ‘97’ and ‘98’).
  • 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’ (excluding ‘9F04’, ‘9F3A’, 9F3B’, ‘9F43’, ‘81’, ‘97’ and ‘98’) 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 ’(excluding ‘9F04’, ‘9F3A’, 9F3B’, ‘9F43’, ‘81’, ‘97’ and ‘98’) 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’ (excluding ‘9F04’, ‘9F3A’, 9F3B’, ‘9F43’, ‘81’, ‘97’ and ‘98’) 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’ countries. 2CA.122.02 EMV reserved Data objects processing (3) excluding ‘9F04’, ‘9F3A’, 9F3B’, ‘9F43’, ‘81’, ‘97’ and ‘98’) 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’ (excluding ‘9F04’, ‘9F3A’, 9F3B’, ‘9F43’, ‘81’, ‘97’ and ‘98’) 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.03 EMV reserved Data objects processing (4) Test No: 2CA.122.03 - Revision 44d - Number of sub cases: 3 Objective: To ensure that the terminal ignores EMV reserved Data Objects (not used by EMV). Reference EMV 4.4: Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects Book 3 - Section Annex A2 – Data Elements by tag Terminal Configuration (New format): [PSE] Conditions:
  • LT AID value is B000001234
  • Terminal AID Value is B000001234
  • All Data Elements listed in Book 3, Table 38 are excluded from the below lists.
  • PDOL, CDOL1 and CDOL2 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’ (excluding ‘9F04’, ‘9F3A’, 9F3B’, ‘9F43’, ‘81’, ‘97’ and ‘98’).
  • PSE contains a directory file with entries for ADF.
  • Case 01: FCI Issuer discretionary Data (tag BF0C) of PSE 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’' (excluding ‘9F04’, ‘9F3A’, 9F3B’, ‘9F43’, ‘81’, ‘97’ and ‘98’) with values different from zero.
  • Case 02: FCI (tag 6F) of PSE 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’ (excluding ‘9F04’, ‘9F3A’, 9F3B’, ‘9F43’, ‘81’, ‘97’ and ‘98’) with values different from zero.
  • Case 03: Template '73' of ADF Directory Entry 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’ (excluding ‘9F04’, ‘9F3A’, 9F3B’, ‘9F43’, ‘81’, ‘97’ and ‘98’) with values different from zero. Action: NA Procedure: Application in LT is selected and transaction is processed with LT until approval. countries. 2CA.122.03 EMV reserved Data objects processing (4) Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC.
  • 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 (5) Test No: 2CA.122.04 - Revision 44d - Number of sub cases: 6 Objective: To ensure that the terminal ignores Proprietary Data Objects. Reference EMV 4.4: Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects Book 3 - Section Annex A2 – Data Elements by tag Terminal Configuration (New format): [NA] 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 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. 2CA.122.05 EMV reserved Data objects processing (6) Test No: 2CA.122.05 – Revision 44d – Number of sub cases: 5 countries. 2CA.122.05 EMV reserved Data objects processing (6) Objective: To ensure that the terminal ignores EMV reserved Data Objects (not used by EMV). Reference EMV 4.4: Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects Book 3 - Section Annex A2 – Data Elements by tag Terminal Configuration (New format): NOT[Biometric] Conditions:
  • LT AID value is B000001234
  • Terminal AID Value is B000001234
  • PDOL, CDOL1 and CDOL2 of LT contains EMV primitive tags reserved but not used in the EMV specification: ‘9F30’ and ‘9F31’
  • Case 01: FCI (tag 6F) of ADF contains the following EMV primitive tags reserved but not used in the EMV specification: ‘9F30’ and ‘9F31’ with values different from zero within the FCI template
  • Case 02: FCI Issuer discretionary Data (tag BF0C) of ADF contains the following EMV primitive tags reserved but not used in the EMV specification: ‘9F30’ and ‘9F31’ with values different from zero encoded in template 77
  • Case 03: Response to GENERATE AC contains the following EMV primitive tags reserved but not used in the EMV specification: ‘9F30’ and ‘9F31’ with values different from zero encoded in template 77
  • Case 04: Records contains the following EMV primitive tags reserved but not used in the EMV specification: ‘9F30’ and ‘9F31’ with values different from zero.
  • Case 05: Response to GET PROCESSING OPTIONS contains the following EMV primitive tags reserved but not used in the EMV specification: ‘9F30’ and ‘9F31’ with values different from zero 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 process the transaction until completion, by requesting a TC.
  • Values of the reserved tags '9F30' and '9F31' 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. countries. 2CA.122.06 EMV reserved Data objects processing (7) Test No: 2CA.122.06 - Revision 44d - Number of sub cases: 3 Objective: To ensure that the terminal ignores EMV reserved Data Objects (not used by EMV). Reference EMV 4.4: Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects Book 3 - Section Annex A2 – Data Elements by tag Terminal Configuration (New format): NOT[Biometric] AND [PSE] Conditions:
  • LT AID value is B000001234
  • Terminal AID Value is B000001234
  • PSE contains a directory file with entries for ADF.
  • PDOL, CDOL1 and CDOL2 of LT contains EMV primitive tags reserved but not used in the EMV specification: ‘9F30’ and ‘9F31’
  • Case 01: FCI Issuer discretionary Data (tag BF0C) of PSE contains the following EMV primitive tags reserved but not used in the EMV specification: ‘9F30’ and ‘9F31 with values different from zero.
  • Case 02: FCI (tag 6F) of PSE contains the following EMV primitive tags reserved but not used in the EMV specification: ‘9F30’ and ‘9F31’ with values different from zero.
  • Case 03: Template '73' of ADF Directory Entry contains the following EMV primitive tags reserved but not used in the EMV specification: ‘9F30’ and ‘9F31’ with values different from zero. 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.
  • Values of the reserved tags '9F30' and '9F31' 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.07 Proprietary Data objects processing (8) Test No: 2CA.122.07 - Revision 44d - Number of sub cases: 6 Objective: To ensure that the terminal ignores Proprietary Data Objects. Reference EMV 4.4: Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects Book 3 - Section Annex A2 – Data Elements by tag Terminal Configuration (New format): NOT[Biometric] Conditions:
  • Case 01: FCI (tag 6F) of ADF contains additionally Tags DF50 to DF54 within the FCI template
  • Case 02: FCI Issuer discretionary Data (tag BF0C) of ADF contains additionally Tags DF50 to DF54
  • Case 03: Response to GET PROCESSING OPTIONS contains Tags DF50 to DF54 and shall be encoded in template 77
  • Case 04: The PDOL of LT contains additionally Tags DF50 to DF54
  • Case 05: The CDOL1 of LT contains additionally Tags DF50 to DF54
  • Case 06: The CDOL2 of LT contains additionally Tags DF50 to DF54 and LT request ARQC on first Generate AC 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. countries. 2CA.122.08 EMV reserved Data objects processing (9) Test No: 2CA.122.08 – Revision 44d – Number of sub cases: 5 Objective: To ensure that the terminal ignores EMV reserved Data Objects (not used by EMV). Reference EMV 4.4: Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects Book 3 - Section Annex A2 – Data Elements by tag Terminal Configuration (New format): [NA] Conditions:
  • LT AID value is A000000025
  • Terminal AID Value is A000000025
  • PDOL, CDOL1 and CDOL2 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’ (excluding ‘9F04’, ‘9F3A

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