PCI Watch

Tracking changes across the Payment Card Industry

TTA Bulletin nº 242: Terminal Level 2 Test Cases EMV® v4.3i Update

v2.0 Type Approval Bulletins
ChipContact Acceptance Device

EMV<sup>®</sup> Terminal Type Approval Bulletin No. 242 Second Edition, January 2021 Terminal Level 2 Test Cases v4.3i Update

Applicability

This Bulletin applies to:

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

Related Documents

This Bulletin should be read in conjunction with:

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

Effective Date

  • January 31th 2021

Description

Based on EMVCo's continued review of the EMVCo Type Approval Terminal Level 2 Test Cases v4.3i, the following updates are necessary, and shall be applied to any type approval session beginning on, or after, the effective date cited above. Update to EMV<sup>®</sup> Terminal Type Approval - Level 2 Test Cases – version 4.3i Section 5.5 – Default Values Setting Updates

Introduction

A Bitmasks checking mechanism at the test tool level shall be implemented to verify that the TVR and the TSI bits, which are not used depending on the test cases conditions, stay at ‘0’ and are not wrongly set to ‘1’. As a result of this bitmasks checking, a new pass criteria is added in all test cases, to reflect it. Three levels of bitmask are defined to create the ‘Un-set TVR bits’ (and TSI) Pass Criteria:

  • Terminal configuration setting bitmask (example: if CDA is not supported, TVR bit CDA failed can never be set), named ICS-bitmask
  • LT (Card) setting bitmask (example if AIP of LT does not support DDA, TVR bit DDA failed can never be set), named LT-bitmask
  • Transaction bitmask (example if Transaction date is earlier then Expiration, TVR bit Expired can never be set), named Transaction-bitmask Note that even if the Transaction-bitmask is defined here, it will be not used for the time being. 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 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 B4b6 B4b5 B4b4 B4b3 B4b2 B4b1 B5b8 B5b7 B5b6 B5b5 B5b4 TVR Name Offline data authentication was not performed SDA failed ICC data missing Card appears on terminal exception file DDA failed CDA failed SDA Selected RFU 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 RFU Transaction exceeds floor limit Lower consecutive offline limit exceeded Upper consecutive offline limit exceeded Transaction selected randomly for online processing Merchant forced transaction online RFU or Biometric Try Limit not exceeded RFU or A selected Biometric Type not supported RFU Default TDOL used Issuer authentication failed Script processing failed before final GENERATE AC Script processing failed after final GENERATE AC RFU Related ICS question of the configuration SDA and DDA = NO Exception File = NO SDA and DDA = NO CDA = NO SDA and DDA = NO Always set Velocity Checking = NO Always set Biometric = No Biometric = No Offline Enciphered PIN AND Plaintext PIN = NO Offline Enciphered PIN AND Plaintext PIN AND Online Enciphered PIN = NO Offline Enciphered PIN AND Plaintext PIN AND Online Enciphered PIN = NO Online Enciphered PIN = NO Always set Always set Floor Limit Checking = NO Velocity Checking = NO Velocity Checking = NO Random Transaction Selection = NO Biometric = No Biometric = No Always set Default TDOL = NO Always set bitmask has the value: 0 1 0 1 1 1 1 1 0 0 0 0 1 1 1 1 0 0 1 1 1 1 1 1 1 1 1 1 0 1 1 1 1 0 0 0 1 countries. B5b3 B5b2 B5b1 RFU RFU RFU Always set 1 Always set 1 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 B1b8 B1b7 B1b6 B1b5 B1b4 B1b3 B1b2 B1b1 B2b8 B2b7 B2b6 B2b5 B2b4 B2b3 B2b2 B2b1 B3b8 B3b7 B3b6 TVR Name Offline data authentication was not performed SDA failed ICC data missing Card appears on terminal exception file DDA failed CDA failed SDA Selected RFU 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 LT Data setting AIP States SDA is not supported All Mandatory Data present in LT AIP States DDA is not supported AIP States CDA is not supported AIP States SDA is not supported ICC application version not present in LT Effective Data not present in LT (AUC not present in LT) OR (AUC value = ‘FFC0’) (ATC different from ‘0’) OR (LOATC # ‘0’) OR (LCOL AND UCOL not present) AIP states Cardholder Verification is not supported (AIP states Cardholder Verification is not supported) OR (CVM list uses only EMVCo recognized Code) (AIP states Cardholder Verification is not supported) OR (CVM list does not contain Offline Enciphered PIN AND Plaintext PIN) bitmask has the value: 0 1 1 0 1 1 1 0 1 0 1 1 1 0 0 0 1 1 1 countries. B3b5 PIN entry required and PIN pad not (AIP states Cardholder Verification is 1 present or not working not supported) OR (CVM list does not contain any PIN) B3b4 PIN entry required, PIN pad (AIP states Cardholder Verification is 1 present, but PIN was not entered not supported) OR (CVM list does not contain any PIN) B3b3 Online PIN entered (AIP states Cardholder Verification is 1 not supported) OR (CVM List does not contain Online PIN) B3b2 RFU 0 B3b1 RFU 0 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 for 0 online processing B4b4 Merchant forced transaction online 0 B4b3 RFU or Biometric Try Limit not 0 exceeded B4b2 RFU or A selected Biometric Type 0 not supported B4b1 RFU 0 B5b8 Default TDOL used TDOL present in LT 1 B5b7 Issuer authentication failed 0 B5b6 Script processing failed before final 0 GENERATE AC B5b5 Script processing failed after final 0 GENERATE AC 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 B1b8 B1b7 B1b6 B1b5 B1b4 B1b3 B1b2 B1b1 B2b8 B2b7 B2b6 B2b5 Offline data authentication was not performed SDA failed ICC data missing Card appears on terminal exception file DDA failed CDA failed SDA Selected RFU ICC and terminal have different application versions Expired application Application not yet effective Requested service not allowed for card product bitmask has the value: 0 0 0 0 0 0 0 0 0 0 0 0 countries. B2b4 New card 0 B2b3 RFU 0 B2b2 RFU or Biometric not performed or 0 not successful B2b1 RFU or Biometric template format 0 supported B3b8 Cardholder verification was not 0 successful B3b7 Unrecognised CVM 0 B3b6 PIN Try Limit exceeded 0 B3b5 PIN entry required and PIN pad not 0 present or not working B3b4 PIN entry required, PIN pad 0 present, but PIN was not entered B3b3 Online PIN entered 0 B3b2 RFU 0 B3b1 RFU 0 B4b8 Transaction exceeds floor limit 0 B4b7 Lower consecutive offline limit 0 exceeded B4b6 Upper consecutive offline limit 0 exceeded B4b5 Transaction selected randomly for 0 online processing B4b4 Merchant forced transaction online 0 B4b3 RFU or Biometric Try Limit not 0 exceeded B4b2 RFU or A selected Biometric Type 0 not supported B4b1 RFU 0 B5b8 Default TDOL used 0 B5b7 Issuer authentication failed 0 B5b6 Script processing failed before final 0 GENERATE AC B5b5 Script processing failed after final 0 GENERATE AC B5b4 RFU 0 B5b3 RFU 0 B5b2 RFU 0 B5b1 RFU 0 Bitmask Checking Mechanism The Tool shall implement, for each transaction run in all test cases, the following checking function (applicable for all TVR bits, one by one) based on the previous bitmasks: IF (TVR ByteXbitY is set to ‘1’) AND ((ICS-bitmask ByteXbitY = ‘1) OR (LT-bitmask ByteXbitY = ‘1) OR (Transaction-bitmask ByteXbitY = ‘1)) # ZERO THEN Pass Criteria = error on ByteXbitY ‘Un-set TVR bits’ Pass Criteria The following Pass Criteria apply to all test cases individually: TVR bits, where ICS-bitmask and/or the LT-bitmask equivalent bits are set to ‘1’, shall be set to '0' received at 1ST GENERATE AC. TSI-ICS-bitmask countries. 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 TSI bits and are depending on the related ICS question(s) other TSI bit shall have the value ‘0’ in the bitmask: TSI B1b8 B1b7 B1b6 B1b5 B1b4 B1b3 TSI Name Offline data authentication was performed Cardholder verification authentication was performed Card risk management was performed Issuer authentication was performed Terminal risk management was performed Script processing was performed Related ICS question of the configuration (SDA and DDA) AND CDA = NO Offline Only = YES (Velocity Checking) AND (Random Transaction Selection) AND (Floor Limit) = NO Offline Only = YES bitmask has the value: 1 0 0 1 1 1 B1b2 RFU 1 B1b1 RFU 1 B2b8 RFU 1 B2b7 RFU 1 B2b6 RFU 1 B2b5 RFU 1 B2b4 RFU 1 B2b3 RFU 1 B2b2 RFU 1 B2b1 RFU 1 Note: even if not related to ICS-bitmask, the un-setting of RFU TSI bits is checked here. countries. TSI-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 - … The LT-bitmask is limited to the following TSI bits (any other TSI bit shall have the value ‘0’ in this bitmask): TSI B1b8 B1b7 B1b6 B1b5 B1b4 B1b3 TSI Name Offline data authentication was performed Cardholder verification authentication was performed Card risk management was performed Issuer authentication was performed Terminal risk management was performed Script processing was performed LT Data setting AIP states SDA AND DDA AND CDA are not supported AIP states Cardholder Verification is not supported OR CVM List is not present in LT bitmask has the value: 1 1 0 0 0 0 B1b2 RFU 0 B1b1 RFU 0 B2b8 RFU 0 B2b7 RFU 0 B2b6 RFU 0 B2b5 RFU 0 B2b4 RFU 0 B2b3 RFU 0 B2b2 RFU 0 B2b1 RFU 0 countries. TSI-Transaction-bitmask All bits of the TSI-Transaction-bitmask shall be set to zero for the time being. TSI TSI Name LT Data setting B1b8 B1b7 B1b6 B1b5 B1b4 B1b3 Offline data authentication was performed Cardholder verification authentication was performed Card risk management was performed Issuer authentication was performed Terminal risk management was performed Script processing was performed B1b2 B1b1 B2b8 B2b7 B2b6 B2b5 B2b4 B2b3 B2b2 B2b1 RFU RFU RFU RFU RFU RFU RFU RFU RFU RFU bitmask has the value: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Bitmask Checking Mechanism The Tool shall implement, for each transaction run in all test cases, the following checking function (applicable for all TSI bits, one by one) based on the previous bitmasks: IF (TSI ByteXbitY is set to ‘1’) AND ((ICS-bitmask ByteXbitY = ‘1) OR (LT-bitmask ByteXbitY = ‘1) OR (Transaction-bitmask ByteXbitY = ‘1)) # ZERO THEN Pass Criteria = error on ByteXbitY ‘Un-set TSI bits’ Pass Criteria The following Pass Criteria apply to all test cases individually: TSI bits, where TSI-ICS-bitmask and/or the TSI-LT-bitmask equivalent bits are set to ‘1’, shall be set to '0' received at 1ST GENERATE AC. countries. Section 7 – Test Cases Updates New test cases include: 2CA.122.06 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 Revised test cases include: 2CA.015.00 2CA.015.01 2CA.015.02 2CA.015.03 2CA.124.00 2CA.124.01 2CA.124.02 2CA.124.03 2CA.130.00 2CB.024.00 2CB.031.00 2CB.031.09 2CC.071.00 2CI.021.00 2CJ.002.00 2CJ.002.01 2CJ.002.02 2CJ.002.03 2CJ.002.04 2CJ.002.05 2CJ.002.06 2CJ.002.07 2CJ.002.08 2CJ.002.09 Deleted test cases include: 2CA.054.01 2CA.122.20 2CA.122.21 2CA.122.22 2CA.122.23 2CA.122.24 2CJ.002.10 2CJ.002.11 2CJ.002.12 2CJ.002.13 2CJ.002.14 2CJ.035.00 2CJ.041.00 2CJ.042.00 2CJ.043.00 2CJ.044.00 2CJ.045.00 2CJ.046.00 2CA.122.25 2CB.031.10 2CC.146.00 2CM.083.01 2CM.083.02 2CJ.047.00 2CJ.048.00 2CJ.049.00 2CJ.050.00 2CJ.051.00 2CJ.052.00 2CJ.053.00 2CJ.054.00 2CJ.056.00 2CJ.057.00 2CJ.058.00 2CJ.059.00 2CM.083.03 2CJ.060.00 2CJ.062.00 2CK.005.01 2CM.063.00 2CM.064.00 2CM.067.00 2CM.083.00 countries. 2CA.015.00 Test No: Objective: Reference EMV 4.3: Terminal Configuration: Terminal Configuration (New format): Conditions: Processing DOLs: data absent from ICC 2CA.015.00 - Revision 43j - Number of sub cases: 6 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 Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) NA [NA]
  • 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 03: CDOL1 request the TC Hash value. The TDOL of LT contains (in this order) the Acquirer Identifier ‘9F01’ (with a nonzero value), an optional ICC static data that is absent from the LT (for example the Issuer Action Code – Default, tag ‘9F0D’) and the Merchant Identifier ‘9F16’ (with a non-zero value)
  • 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.
  • Case 06: CDOL1 request the TC Hash value. The TDOL of LT contains (in this order) the Acquirer Identifier ‘9F01’, the Merchant Identifier ‘9F16’ (both with a non-zero value) and an optional ICC static data that is absent from the LT (for example the Issuer Action Code – Default, tag ‘9F0D’). Action: Procedure: Pass Criteria: NA Application in LT is selected and transaction is performed with LT (in particular the DOL processing).
  • 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
  • Case 03 & 06: TC hash value received a First Generate AC shall be have the same value as the one computed (with ‘00’ value for the data absent) countries. 2CA.015.01 Test No: Objective: Reference EMV 4.3: Terminal Configuration: Terminal Configuration (New format): Conditions: Processing DOLs: data absent from ICC (2) 2CA.015.01 - Revision 43j - Number of sub cases: 2 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. By using Dynamic Data Authentication. Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) [DDA] supported [DDA]
  • Case 01: The DDOL of LT requests the Unpredictable Number ‘9F37’ and an optional ICC static data that is absent from the LT (for example the Issuer Action Code – Default, tag ‘9F0D’)
  • Case 02: The DDOL of LT requests an optional ICC static data that is absent from the LT (for example the Issuer Action Code – Default, tag ‘9F0D’) and the Unpredictable Number ‘9F37’ Action: Procedure: Pass Criteria: NA Application in LT is selected and transaction is performed with LT (in particular the DOL processing). The terminal shall return an INTERNAL AUTH command to the LT 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 Test No: Objective: Reference EMV 4.3: Terminal Configuration: Terminal Configuration (New format): Conditions: Processing DOLs: data absent from Terminal 2CA.015.02 - Revision 43j - Number of sub cases: 8 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 Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) [TRMDabsent]
  • 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 03: CDOL1 request the TC Hash value. The TDOL of LT contains (in this order) the Acquirer Identifier ‘9F01’ (with a nonzero value), an optional terminal data that is absent: Terminal Risk Management Data ‘9F1D’ and the Merchant Identifier ‘9F16’ (with a non-zero value)
  • 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 06: CDOL1 request the TC Hash value. The TDOL of LT contains (in this order) the Acquirer Identifier ‘9F01’, the Merchant Identifier ‘9F16’ (both with a non-zero value) and an optional terminal data that is absent: Terminal Risk Management Data ‘9F1D’.
  • 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 countries. 2CA.015.02 Procedure: Pass Criteria: Processing DOLs: data absent from Terminal Application in LT is selected and transaction is performed with LT (in particular the DOL processing).
  • 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).
  • Case 03 & 06: TC hash value received a First Generate AC shall have the same value as the one computed (with ‘00’ value for the data absent) countries. 2CA.015.03 Test No: Objective: Reference EMV 4.3: Terminal Configuration: Terminal Configuration (New format): Conditions: Processing DOLs: data absent from Terminal (2) 2CA.015.03 - Revision 43j - Number of sub cases: 2 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. By using Dynamic Data Authentication. Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) [DDA] AND [TRMDabsent]
  • Case 01: The DDOL of LT requests the Unpredictable Number ‘9F37’ and contain an optional terminal data that is absent: Terminal Risk Management Data ‘9F1D’,
  • Case 02: The DDOL of LT requests an optional terminal data that is absent: Terminal Risk Management Data ‘9F1D’ and the Unpredictable Number ‘9F37’. Action: Procedure: Pass Criteria: NA Application in LT is selected and transaction is performed with LT (in particular the DOL processing). The terminal shall return an INTERNAL AUTH command to the LT 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.122.06 EMV reserved Data objects processing (4) Test No: 2CA.122.06 - Revision 43j - Number of sub cases: 3 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.3: Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Terminal [Biometric] not supported AND [PSE] supported Configuration: Terminal NOT[Biometric] AND [PSE] Configuration (New format): Conditions:
  • LT AID value is B000001234
  • Terminal AID Value is B000001234
  • PSE contains a directory file with entries for ADF.
  • PDOL, CDOL1, CDOL2 and TDOL 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.11 EMV reserved Data objects processing (8) Test No: 2CA.122.11 – Revision 43j – 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.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Book Bulletins - Section SB 231 - Bulletin n°231, Issuer Identification Number Extended (IINE) (December 2020) Terminal Configuration: 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 the Specification Bulletin SB 185, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 197, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 231, Table 34 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 ‘9F0C’, ‘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 countries. 2CA.122.11 EMV reserved Data objects processing (8) 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 ‘9F0C’, ‘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 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)
  • TVR byte 1 - bit 1, byte 2 - bit 3, byte 4 - bit 1, byte 5 – bits 4 to 1 are set to ‘0’, received at 1st GENERATE AC. countries. 2CA.122.12 EMV reserved Data objects processing (9) Test No: 2CA.122.12 - Revision 43j - Number of sub cases: 3 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.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Book Bulletins - Section SB 231 - Bulletin n°231, Issuer Identification Number Extended (IINE) (December 2020) Terminal [PSE] supported Configuration: Terminal [PSE] Configuration (New format): Conditions:
  • LT AID value is A0000000031010
  • Terminal AID Value is 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 the Specification Bulletin SB 185, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 197, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 231, Table 34 are excluded from the below lists.
  • 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’' 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’ 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’ with values different from zero. Action: NA countries. 2CA.122.12 EMV reserved Data objects processing (9) 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 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.13 EMV reserved Data objects processing (10) Test No: 2CA.122.13 – Revision 43j – 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.3: Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Terminal [Biometric] not supported Configuration: Terminal NOT[Biometric] Configuration (New format): Conditions:
  • LT AID value is A0000000031010
  • Terminal AID Value is A0000000031010
  • PDOL, CDOL1, CDOL2 and TDOL 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
  • Case 03: Records contains the following EMV primitive tags reserved but not used in the EMV specification: ‘9F30’ and ‘9F31’ with values different from zero.
  • Case 04: 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
  • Case 05: 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 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.14 EMV reserved Data objects processing (11) Test No: 2CA.122.14 – Revision 43j – 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.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Book Bulletins - Section SB 231 - Bulletin n°231, Issuer Identification Number Extended (IINE) (December 2020) Terminal Configuration: 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 the Specification Bulletin SB 185, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 197, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 231, Table 34 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 countries. 2CA.122.14 EMV reserved Data objects processing (11) 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 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)
  • TVR byte 1 - bit 1, byte 2 - bit 3, byte 4 - bit 1, byte 5 – bits 4 to 1 are set to ‘0’, received at 1st GENERATE AC. countries. 2CA.122.15 EMV reserved Data objects processing (12) Test No: 2CA.122.15 - Revision 43j - Number of sub cases: 3 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.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Book Bulletins - Section SB 231 - Bulletin n°231, Issuer Identification Number Extended (IINE) (December 2020) Terminal [PSE] supported Configuration: Terminal [PSE] 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 the Specification Bulletin SB 185, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 197, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 231, Table 34 are excluded from the below lists.
  • 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’' 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’ 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’ with values different from zero. Action: NA countries. 2CA.122.15 EMV reserved Data objects processing (12) 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.
  • 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.16 EMV reserved Data objects processing (13) Test No: 2CA.122.16 – Revision 43j – 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.3: Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Terminal [Biometric] not supported Configuration: Terminal NOT[Biometric] Configuration (New format): Conditions:
  • LT AID value is A0000000041010
  • Terminal AID Value is A0000000041010
  • PDOL, CDOL1, CDOL2 and TDOL 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
  • Case 03: Records contains the following EMV primitive tags reserved but not used in the EMV specification: ‘9F30’ and ‘9F31’ with values different from zero.
  • Case 04: 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
  • Case 05: 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 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.17 EMV reserved Data objects processing (14) Test No: 2CA.122.17 – Revision 43j – 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.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Book Bulletins - Section SB 231 - Bulletin n°231, Issuer Identification Number Extended (IINE) (December 2020) Terminal Configuration: 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 the Specification Bulletin SB 185, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 197, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 231, Table 34 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 countries. 2CA.122.17 EMV reserved Data objects processing (14) 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 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)
  • TVR byte 1 - bit 1, byte 2 - bit 3, byte 4 - bit 1, byte 5 – bits 4 to 1 are set to ‘0’, received at 1st GENERATE AC. countries. 2CA.122.18 EMV reserved Data objects processing (15) Test No: 2CA.122.18 - Revision 43j - Number of sub cases: 3 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.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Book Bulletins - Section SB 231 - Bulletin n°231, Issuer Identification Number Extended (IINE) (December 2020) Terminal [PSE] supported Configuration: Terminal [PSE] 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 the Specification Bulletin SB 185, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 197, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 231, Table 34 are excluded from the below lists.
  • 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’' 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’ 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’ with values different from zero. Action: NA countries. 2CA.122.18 EMV reserved Data objects processing (15) 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.
  • 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.19 EMV reserved Data objects processing (16) Test No: 2CA.122.19 – Revision 43j – 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.3: Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Terminal [Biometric] not supported Configuration: Terminal NOT[Biometric] Configuration (New format): Conditions:
  • LT AID value is A0000000651010
  • Terminal AID Value is A0000000651010
  • PDOL, CDOL1, CDOL2 and TDOL 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
  • Case 03: Records contains the following EMV primitive tags reserved but not used in the EMV specification: ‘9F30’ and ‘9F31’ with values different from zero.
  • Case 04: 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
  • Case 05: 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 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.20 EMV reserved Data objects processing (17) Test No: 2CA.122.20 – Revision 43j – 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.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Book Bulletins - Section SB 231 - Bulletin n°231, Issuer Identification Number Extended (IINE) (December 2020) Terminal Configuration: 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 the Specification Bulletin SB 185, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 197, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 231, Table 34 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 countries. 2CA.122.20 EMV reserved Data objects processing (17) 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 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)
  • TVR byte 1 - bit 1, byte 2 - bit 3, byte 4 - bit 1, byte 5 – bits 4 to 1 are set to ‘0’, received at 1st GENERATE AC. countries. 2CA.122.21 EMV reserved Data objects processing (18) Test No: 2CA.122.21 - Revision 43j - Number of sub cases: 3 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.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Book Bulletins - Section SB 231 - Bulletin n°231, Issuer Identification Number Extended (IINE) (December 2020) Terminal [PSE] supported Configuration: Terminal [PSE] 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 the Specification Bulletin SB 185, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 197, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 231, Table 34 are excluded from the below lists.
  • 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’' 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’ 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’ with values different from zero. Action: NA countries. 2CA.122.21 EMV reserved Data objects processing (18) 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.
  • 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.22 EMV reserved Data objects processing (19) Test No: 2CA.122.22 – Revision 43j – 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.3: Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Terminal [Biometric] not supported Configuration: Terminal NOT[Biometric] Configuration (New format): Conditions:
  • LT AID value is A000000333010101
  • Terminal AID Value is A000000333010101
  • PDOL, CDOL1, CDOL2 and TDOL 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
  • Case 03: Records contains the following EMV primitive tags reserved but not used in the EMV specification: ‘9F30’ and ‘9F31’ with values different from zero.
  • Case 04: 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
  • Case 05: 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 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.23 EMV reserved Data objects processing (20) Test No: 2CA.122.23 – Revision 43j – 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.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Book Bulletins - Section SB 231 - Bulletin n°231, Issuer Identification Number Extended (IINE) (December 2020) Terminal Configuration: 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 the Specification Bulletin SB 185, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 197, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 231, Table 34 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 countries. 2CA.122.23 EMV reserved Data objects processing (20) 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 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)
  • TVR byte 1 - bit 1, byte 2 - bit 3, byte 4 - bit 1, byte 5 – bits 4 to 1 are set to ‘0’, received at 1st GENERATE AC. countries. 2CA.122.24 EMV reserved Data objects processing (21) Test No: 2CA.122.24 - Revision 43j - Number of sub cases: 3 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.3: Book Bulletins - Section SB 197 - Bulletin n°197, Tokenisation Data Objects – Token Requestor ID and Last 4 Digits of PAN (May 2017) Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Book Bulletins - Section SB 231 - Bulletin n°231, Issuer Identification Number Extended (IINE) (December 2020) Terminal [PSE] supported Configuration: Terminal [PSE] 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 the Specification Bulletin SB 185, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 197, Table 34 are excluded from the below lists.
  • All Data Elements listed in the Specification Bulletin SB 231, Table 34 are excluded from the below lists.
  • 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’' 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’ 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’ with values different from zero. Action: NA countries. 2CA.122.24 EMV reserved Data objects processing (21) 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.
  • 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.25 EMV reserved Data objects processing (22) Test No: 2CA.122.25 – Revision 43j – 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.3: Book Bulletins - Section SB 185 - Bulletin n°185, Biometric Terminal Specification (March 2017) Terminal [Biometric] not supported Configuration: Terminal NOT[Biometric] Configuration (New format): Conditions:
  • LT AID value is A0000001523010
  • Terminal AID Value is A0000001523010
  • PDOL, CDOL1, CDOL2 and TDOL of LT contains EMV primitive tags reserved but not use

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