PCI Watch

Tracking changes across the Payment Card Industry

TTA Bulletin n°278: Terminal Level 2 Test Cases 4.4b Update

v1.0 Type Approval Bulletins
Contact Acceptance Device

EMV® Terminal Type Approval Bulletin No. 278 First Edition, October 2024 Terminal Level 2 Test Cases 4.4b Update

Applicability

This Bulletin applies to:

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

Related Documents

This Bulletin should be read in conjunction with:

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

Effective Date

  • January 1st, 2025

Description

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

countries.

B1b6 ICC data missing 0 B1b5 Card appears on terminal Exception File = NO 1 exception file B1b4 DDA failed SDA and DDA = NO 1 B1b3 CDA failed CDA = NO 1 B1b2 SDA Selected SDA and DDA = NO 1 B1b1 XDA Selected XDA = No 1 B2b8 ICC and terminal have 0 different application versions B2b7 Expired application 0 B2b6 Application not yet effective 0 B2b5 Requested service not allowed 0 for card product B2b4 New card Velocity Checking = NO 1 B2b3 RFU Always set 1 B2b2 RFU or Biometric not Biometric = No 1 performed or not successful B2b1 RFU or Biometric template Biometric = No 1 format supported B3b8 Cardholder verification was not 0 successful B3b7 Unrecognised CVM 0 B3b6 PIN Try Limit exceeded Offline Enciphered PIN AND 1 Plaintext PIN = NO B3b5 PIN entry required and PIN 0 pad not present or not working B3b4 PIN entry required, PIN pad Offline Enciphered PIN AND 1 present, but PIN was not Plaintext PIN AND Online entered Enciphered PIN = NO B3b3 Online PIN entered Online Enciphered PIN = NO 1 B3b2 RFU or Biometric required Biometric = No 1 but Biometric capture device not working B3b1 RFU or Biometric required, Biometric = No 1 Biometric capture device present, but Biometric Subtype entry was bypassed B4b8 Transaction exceeds floor limit Floor Limit Checking = NO 1 B4b7 Lower consecutive offline limit Velocity Checking = NO 1 exceeded B4b6 Upper consecutive offline limit Velocity Checking = NO 1 exceeded B4b5 Transaction selected randomly Random Transaction Selection = 1 for online processing NO B4b4 Merchant forced transaction 0 online B4b3 RFU or Biometric Try Limit not Biometric = No 1 exceeded B4b2 RFU or A selected Biometric Biometric = No 1 Type not supported B4b1 XDA not failed XDA = No 1 B5b8 Default TDOL used Default TDOL = NO 1

countries.

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

countries.

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

countries.

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

countries.

B4b6 Upper consecutive offline limit 0 exceeded B4b5 Transaction selected randomly 0 for online processing B4b4 Merchant forced transaction 0 online B4b3 RFU or Biometric Try Limit not 0 exceeded B4b2 RFU or A selected Biometric 0 Type not supported B4b1 RFU 0 B5b8 Default TDOL used 0 B5b7 Issuer authentication failed 0 B5b6 Script processing failed before 0 final GENERATE AC B5b5 Script processing failed after 0 final GENERATE AC B5b4 RFU 0 B5b3 CA ECC key missing 0 B5b2 ECC key recovery failed 0 B5b1 RFU 0

countries.

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

countries.

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

countries.

LT Settings [LTSetting107] (differences with LTSetting1): Data Expiration Date Effective Date Application Version Number Application Usage Control CVM List IAC-Online [LTSetting108] (differences with LTSetting1): Data Expiration Date Effective Date Application Version Number Application Usage Control CVM List IAC-Online [LTSetting113] (differences with LTSetting1): Data CVM List [LTSetting149] (differences with LTSetting1) Data Application Interchange Profile Issuer Public Key Certificate ICC Public Key Certificate ICC PIN Encipherment Public Key Certificate CVM list Tag 82 90 9F46 9F2B 8E [LTSetting150] (differences with LTSetting1) Data Tag Application Interchange Profile 82 90 Issuer Public Key Certificate Tag 5F24 5F25 9F08 9F07 8E 9F0F Value 200101 480101 3032 0000 00000000000000000203 0040000000 Tag 5F24 5F25 9F08 9F07 8E 9F0F Value 200101 480101 3032 0000 00000000000000003F00 0040000000 Tag Value 8E 000000000000000000010000 Value 5000 Computed with Certificate Expiration Date 0170 Computed with Certificate Expiration Date 0170 not present in LT 00000000000000000403 Value 3000 Computed with Certificate Expiration Date 0172

countries.

ICC Public Key Certificate ICC PIN Encipherment Public Key Certificate CVM list 9F46 9F2B 8E [LTSetting151] (differences with LTSetting1) Data Application Interchange Profile ICC Public Key Certificate Issuer Public Key Certificate Tag 82 9F46 90 [LTSetting152] (differences with LTSetting1) Data CVM list Issuer Public Key Certificate ICC PIN Encipherment Public Key Certificate Tag 8E 90 9F2B [LTSetting154] (differences with LTSetting1) Data CVM list Issuer Public Key Certificate ICC PIN Encipherment Public Key Certificate Tag 8E 90 9F2B [LTSetting155] (differences with LTSetting1) Data CVM list Issuer Public Key Certificate ICC PIN Encipherment Public Key Certificate Tag 8E 90 9F2B [LTSetting180] (differences with LTSetting1) Data Tag Application Interchange Profile 82 90 Issuer Public Key Certificate [LTSetting181] (differences with LTSetting1) Computed with Certificate Expiration Date 0172 not present in LT 00000000000000000403 Value 2000 Computed with Certificate Expiration Date 0148 Computed with Certificate Expiration Date 0148 Value 00000000000000000403 Computed with Certificate Expiration Date 0148 Computed with Certificate Expiration Date 0178 Value 00000000000000000403 Computed with Certificate Expiration Date 0170 Computed with Certificate Expiration Date 0170 Value 00000000000000000403 Computed with Certificate Expiration Date 0190 Computed with Certificate Expiration Date 1238 Value 4000 Computed with Certificate Expiration Date 0348

countries.

Data Tag Application Interchange Profile 82 90 Issuer Public Key Certificate [LTSetting182] (differences with LTSetting1) Data Application Interchange Profile ICC Public Key Certificate Issuer Public Key Certificate Tag 82 9F46 90 [LTSetting183] (differences with LTSetting1) Data Application Interchange Profile ICC Public Key Certificate Issuer Public Key Certificate Tag 82 9F46 90 [LTSetting184] (differences with LTSetting1) Data Application Interchange Profile ICC Public Key Certificate Issuer Public Key Certificate ICC PIN Encipherment Public Key Certificate CVM list Tag 82 9F46 90 9F2B 8E [LTSetting185] (differences with LTSetting1) Data Application Interchange Profile ICC Public Key Certificate Issuer Public Key Certificate Tag 82 9F46 90 [LTSetting186] (differences with LTSetting1) Data Application Interchange Profile ICC Public Key Certificate Tag 82 9F46 Value 4000 Computed with Certificate Expiration Date 1235 Value 2000 Computed with Certificate Expiration Date 0135 Computed with Certificate Expiration Date 0188 Value 2000 Computed with Certificate Expiration Date 0190 Computed with Certificate Expiration Date 0144 Value 1100 Computed with Certificate Expiration Date 0170 Computed with Certificate Expiration Date 0170 not present in LT 00000000000000000403 Value 0100 Computed with Certificate Expiration Date 0148 Computed with Certificate Expiration Date 0148 Value 0100 Computed with Certificate Expiration Date 0135

countries.

90 Issuer Public Key Certificate [LTSetting187] (differences with LTSetting1) Data Application Interchange Profile ICC Public Key Certificate Issuer Public Key Certificate Tag 82 9F46 90 [LTSetting191] (differences with LTSetting1) Data Tag CVM List 8E [LTSetting192] (differences with LTSetting1) Data Tag CVM List 8E [LTSetting193] (differences with LTSetting1): Data Expiration Date IAC-Denial [LTSetting194] (differences with LTSetting1) Data Tag CVM List 8E Computed with Certificate Expiration Date 0188 Value 0100 Computed with Certificate Expiration Date 0190 Computed with Certificate Expiration Date 0144 Value ‘00000000000000004100’ Value ‘00000000000000004000’ Tag 5F24 9F0E Value 200101 0040000000 Value ‘00000000000000001E00’

countries.

Section 7 – Test Cases Updates New test cases include: 2CB.031.11 2CJ.098.01 Revised test cases include: 2CB.031.09 2CC.138.00 2CC.141.03 2CC.147.00 2CC.148.00 2CC.149.00 2CC.150.00 2CC.151.00 2CC.152.00 2CC.153.00 Deleted test cases include: 2CM.060.02 2CM.092.00 2CC.154.00 2CC.155.00 2CC.156.00 2CC.157.00 2CJ.098.00 2CM.109.00 2CJ.112.00 2CK.010.00 2CM.025.00 2CM.094.00 2CM.094.01

countries.

2CB.031.09 DF name longer than AID & multiple occurrence Revision: 44c Objective: To ensure that if the DF name in the ICC is longer than that of the AID in the terminal but are identical up to and including the last character in the terminal AID, the terminal shall check the Application Selection indicator. If the Application Selection Indicator indicates that multiple occurrence are permitted and if the application is not blocked, the terminal adds the AID to the candidate list and repeats the SELECT command using the same command data as before, but changes P2 in the command to '02'. Reference Book 1 - Section 12.3.3 - Using a List of AIDs EMV 4.4: Terminal NOT[Cardholder Confirmation] Configuration (New format): Conditions:

  • Terminal Application Selection Indicator allows multiple occurrences for selected AID.
  • LT does not contain PSE
  • LT contain the ADF’s corresponding to the AID’s supported by the Terminal
  • LT returns 20 extended AIDs related to the AID ‘A0000000031010’. For each occurrence: - The DF Name returned in FCI by the LT are longer than terminal AID A0000000031010 used for selection, but they are identical up to and including the last character in the terminal AID (So A00000000310100001, A00000000310100002, etc). - For each ADF, FCI of ADF contains all optional data objects: Application Priority Indicator (‘87’), PDOL (‘9F38’), Language Preference (‘5F 2D’), Issuer Code Table Index (‘9F 11’), Application Preferred Name (‘9F 12’) and FCI issuer Discretionary Data (‘BF 0C’) containing: ‘9F 4D’ '5F54' Bank Identifier Code (BIC), '5F53' International Bank Account Number (IBAN), '5F55' Issuer Country Code (alpha 2), '5F56' Issuer Country Code (alpha 3), '42' Issuer Identifier Number and the EMV reserved tag ‘9F30’ with a length such that FCI template reach its maximum length.
  • Application Priority Indicator of the ADFs are different and in such a way that the ADF with highest priority is the one returned on the last SELECT NEXT command (so on DF with value A00000000310100020).
  • Case 01: Terminal supports three AID’s: - A0000000031010 countries. 2CB.031.09 DF name longer than AID & multiple occurrence - A0000000041010 - A0000000250000
  • Case 02: Terminal supports only one AID’s: - A0000000031010 Action: Procedure: Pass Criteria: NA Application Selection using list of AIDs is performed.
  • The terminal shall process the transaction until completion, by requesting a TC
  • LT shall receive twenty (20) SELECT 'AIDs' with P2 option set to 'next'.
  • The terminal shall select the AID (A00000000310100020) and process the transaction using that AID. countries. 2CB.031.11 DF name longer than AID & multiple occurrence Revision: 44c Objective: To ensure that if the DF name in the ICC is longer than that of the AID in the terminal but are identical up to and including the last character in the terminal AID, the terminal shall check the Application Selection indicator. If the Application Selection Indicator indicates that multiple occurrence are permitted and if the application is not blocked, the terminal adds the AID to the candidate list and repeats the SELECT command using the same command data as before, but changes P2 in the command to '02'. Reference Book 1 - Section 12.3.3 - Using a List of AIDs EMV 4.4: Terminal [Cardholder Confirmation] Configuration (New format): Conditions:
  • Terminal Application Selection Indicator allows multiple occurrences for selected AID.
  • LT does not contain PSE
  • LT contain the ADF’s corresponding to the AID’s supported by the Terminal
  • LT returns 20 extended AIDs related to the AID ‘A0000000031010’. For each occurrence: - The DF Name returned in FCI by the LT are longer than terminal AID A0000000031010 used for selection, but they are identical up to and including the last character in the terminal AID (So A00000000310100001, A00000000310100002, etc). - For each ADF, FCI of ADF contains all optional data objects: Application Priority Indicator (‘87’), PDOL (‘9F38’), Language Preference (‘5F 2D’), Issuer Code Table Index (‘9F 11’), Application Preferred Name (‘9F 12’) and FCI issuer Discretionary Data (‘BF 0C’) containing: ‘9F 4D’ '5F54' Bank Identifier Code (BIC), '5F53' International Bank Account Number (IBAN), '5F55' Issuer Country Code (alpha 2), '5F56' Issuer Country Code (alpha 3), '42' Issuer Identifier Number and the EMV reserved tag ‘9F30’ with a length such that FCI template reach its maximum length.
  • Application Priority Indicator of the ADFs are different and in such a way that the ADF with highest priority is the one returned on the last SELECT NEXT command (so on DF with value A00000000310100020).
  • Action: - Cardholder select the AID A00000000310100020 countries. 2CB.031.11 DF name longer than AID & multiple occurrence
  • Case 01: Terminal supports three AID’s: - A0000000031010 - A0000000041010 - A0000000250000
  • Case 02: Terminal supports only one AID’s: - A0000000031010 Action: Procedure: Pass Criteria: NA Application Selection using list of AIDs is performed.
  • The terminal shall process the transaction until completion, by requesting a TC
  • LT shall receive twenty (20) SELECT 'AIDs' with P2 option set to 'next'.
  • The terminal shall display the 20 application and request confirmation/selection from the cardholder
  • The terminal shall generate a final SELECT AID command on the selected AID. countries. 2CC.138.00 First Combined DDA/AC generation AAC request Revision: 44c Objective: To ensure that Enhanced Combined DDA/AC generation is not requested when the device generates an AAC in the 1st GENERATE AC. Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.4: Terminal [CDA] ICS Options: Conditions:
  • LTsetting193: - AIP of LT indicates CDA is supported - Expiration Date has the value '200101' - IAC-Denial has the value '0040000000' Procedure:
  • Transaction is performed with TermSetting1 and LTsetting193 Pass Criteria:
  • Parameter received at first GENERATE AC: - The terminal shall process the transaction until completion, by requesting an AAC (P1_b8='0' AND P1_b7=‘0’)
  • Data received at first GENERATE AC: - Offline Data Authentication was not performed (TVR_B1b8=‘1’). countries. 2CC.141.03 GENERATE AC for Combined DDA/AC generation, case unable to go online, AAC (2) Revision: 44c Objective: To ensure that, when unable to go online and an AAC is requested, the terminal perform the 2nd GENERATE AC without Enhanced Combined DDA/AC. Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.4: Terminal ([Offline/Online Capable] OR ([Online Only] AND [Normal Default Action Code ICS processing])) AND ([CDA Mode1] OR [CDA Mode2]) Options: Conditions:
  • LTsetting145: - AIP indicates CDA is supported Procedure:
  • Issuer_response: - The Issuer does not respond to online processing request. Terminal unable to go Online.
  • Transaction is performed with TermSetting1 and LTsetting145 Pass Criteria:
  • Parameter received at second GENERATE AC: - The terminal shall process the transaction until completion, by requesting an AAC (P1_b8='0' AND P1_b7=‘0’) - The command is requested by the terminal without CDA
  • Data received in Kernel Data Output: - Offline Data Authentication was performed (TVR_B1b8=‘0’). countries. 2CC.147.00 Certificate Expiration Date (1) Revision: 44c Objective: To ensure that the terminal manage the Certificate Expiration Date as per SB272 bulletin. Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.4: Book Bulletins - Section SB 272 - Bulletin n°272, Update of Date Management Requirement (January 2023) Terminal ICS Options: Conditions: [SDA]
  • Case 01: - LTsetting149:
  • Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0170.
  • AIP of LT indicates Static Data Authentication only is supported (AIP byte 1 bit 7 = ‘1’).
  • Case 02: - LTsetting180:
  • Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0348.
  • AIP of LT indicates Static Data Authentication only is supported (AIP byte 1 bit 7 = ‘1’).
  • Case 03: - LTsetting181:
  • Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 1235.
  • AIP of LT indicates Static Data Authentication only is supported (AIP byte 1 bit 7 = ‘1’). Procedure: Pass Criteria:
  • Case 01: Transaction is performed with TermSetting1 and LTsetting149
  • Case 02: Transaction is performed with TermSetting1 and LTsetting180
  • Case 03: Transaction is performed with TermSetting1 and LTsetting181
  • 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: - Transaction Date set to current date of test - SDA not failed (TVR_B1b7=‘0’) countries. 2CC.147.00 Certificate Expiration Date (1) - SDA selected (TVR_B1b2=‘1’) - DDA not used (TVR_B1b4=‘0’) - CDA not used (TVR_B1b3=‘0’) - XDA not used (TVR_B4b1=‘0’) - XDA not selected (TVR_B1b1=‘0’) - Offline Data Authentication was performed (TSI_B1b8=‘1’) countries. 2CC.148.00 Certificate Expiration Date (2) Revision: 44c Objective: To ensure that the terminal manage the Certifcate Expiration Date as per SB272 bulletin. Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.4: Book Bulletins - Section SB 272 - Bulletin n°272, Update of Date Management Requirement (January 2023) Terminal ICS Options: Conditions: [DDA]
  • Case 01 - LTsetting150:  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0172  ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0172.  AIP of LT indicates Dynamic Data Authentication only is supported (AIP byte 1 bit 6 = ‘1’).
  • Case 02 - LTsetting151:  ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0148  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0148  AIP of LT indicates Dynamic Data Authentication only is supported (AIP byte 1 bit 6 = ‘1’).
  • Case 03 - LTsetting182:  ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0135.  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0188  AIP of LT indicates Dynamic Data Authentication only is supported (AIP byte 1 bit 6 = ‘1’).
  • Case 04 - LTsetting183:  ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0190.  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0144 countries. 2CC.148.00 Certificate Expiration Date (2)  AIP of LT indicates Dynamic Data Authentication only is supported (AIP byte 1 bit 6 = ‘1’). Procedure:
  • Case 01: Transaction is performed with TermSetting1 and LTsetting150
  • Case 02: Transaction is performed with TermSetting1 and LTsetting151
  • Case 03: Transaction is performed with TermSetting1 and LTsetting182
  • Case 04: Transaction is performed with TermSetting1 and LTsetting183 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: - Transaction Date set to current date of test - SDA not used (TVR_B1b7=‘0’) - SDA not selected (TVR_B1b2=‘0’) - DDA not failed (TVR_B1b4=‘0’) - CDA not used (TVR_B1b3=‘0’) - XDA not used (TVR_B4b1=‘0’) - XDA not selected (TVR_B1b1=‘0’) - Offline Data Authentication was performed (TSI_B1b8=‘1’) countries. 2CC.149.00 Certificate Expiration Date (3) Revision: 44c Objective: To ensure that the terminal manage the Certifcate Expiration Date as per SB272 bulletin. Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.4: Book Bulletins - Section SB 272 - Bulletin n°272, Update of Date Management Requirement (January 2023) Terminal ICS Options: Conditions: [CDA] AND ([Offline Only] OR [Offline/Online Capable])
  • Case 01 - LTsetting184:  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0170  ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0170.  AIP of LT indicates Combined Data Authentication is supported (AIP byte 1 bit 1 = ‘1’).
  • Case 02 - LTsetting185:  ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0148  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0148  AIP of LT indicates Combined Data Authentication is supported (AIP byte 1 bit 1 = ‘1’).
  • Case 03 - LTsetting182:  ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0135.  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0188  AIP of LT indicates Combined Data Authentication is supported (AIP byte 1 bit 1 = ‘1’).
  • Case 04 - LTsetting183:  ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0190.  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0144 countries. 2CC.149.00 Certificate Expiration Date (3)  AIP of LT indicates Combined Data Authentication is supported (AIP byte 1 bit 1 = ‘1’). Procedure:
  • Case 01: Transaction is performed with TermSetting1 and LTsetting184
  • Case 02: Transaction is performed with TermSetting1 and LTsetting185
  • Case 03: Transaction is performed with TermSetting1 and LTsetting186
  • Case 04: Transaction is performed with TermSetting1 and LTsetting187 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 at first GENERATE AC: - Transaction Date set to current date of test - SDA not used (TVR_B1b7=‘0’) - SDA not selected (TVR_B1b2=‘0’) - DDA not used (TVR_B1b4=‘0’) - CDA not failed (TVR_B1b3=‘0’) - XDA not used (TVR_B4b1=‘0’) - XDA not selected (TVR_B1b1=‘0’)
  • Data received in Kernel Data Output: - Offline Data Authentication was performed (TSI_B1b8=‘1’) countries. 2CC.150.00 Certificate Expiration Date (4) Revision: 44c Objective: To ensure that the terminal manage the Certifcate Expiration Date as per SB272 bulletin. Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.4: Book Bulletins - Section SB 272 - Bulletin n°272, Update of Date Management Requirement (January 2023) Terminal ICS Options: Conditions: ([CDA Mode1] OR [CDA Mode2]) AND ([Online Only] OR [Offline/Online Capable])
  • LT_response at first GENERATE AC - Cryptogram Information Data ‘9F27’ responding an ARQC (‘80’) with CDA.
  • Case 01 - LTsetting184:  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0170  ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0170.  AIP of LT indicates Combined Data Authentication is supported (AIP byte 1 bit 1 = ‘1’).
  • Case 02 - LTsetting185:  ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0148  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0148  AIP of LT indicates Combined Data Authentication is supported (AIP byte 1 bit 1 = ‘1’).
  • Case 03 - LTsetting182:  ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0135.  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0188  AIP of LT indicates Combined Data Authentication is supported (AIP byte 1 bit 1 = ‘1’).
  • Case 04 - LTsetting183: countries. 2CC.150.00 Certificate Expiration Date (4)  ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0190.  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0144  AIP of LT indicates Combined Data Authentication is supported (AIP byte 1 bit 1 = ‘1’). Procedure:
  • Case 01: Transaction is performed with TermSetting1 and LTsetting184
  • Case 02: Transaction is performed with TermSetting1 and LTsetting185
  • Case 03: Transaction is performed with TermSetting1 and LTsetting186
  • Case 04: Transaction is performed with TermSetting1 and LTsetting187 Pass Criteria:
  • Parameter received at second GENERATE AC: - The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’)
  • Data received at first GENERATE AC: - Transaction Date set to current date of test - SDA not used (TVR_B1b7=‘0’) - SDA not selected (TVR_B1b2=‘0’) - DDA not used (TVR_B1b4=‘0’) - CDA not failed (TVR_B1b3=‘0’) - XDA not used (TVR_B4b1=‘0’) - XDA not selected (TVR_B1b1=‘0’)
  • Data received in Kernel Data Output: - Offline Data Authentication was performed (TSI_B1b8=‘1’) countries. 2CC.151.00 Certificate Expiration Date (4) Revision: 44c Objective: To ensure that the terminal manage the Certifcate Expiration Date as per SB272 bulletin. Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.4: Book Bulletins - Section SB 272 - Bulletin n°272, Update of Date Management Requirement (January 2023) Terminal ICS Options: Conditions: [CDA Mode4] AND ([Online Only] OR [Offline/Online Capable])
  • LT_response at first GENERATE AC - Cryptogram Information Data ‘9F27’ responding an ARQC (‘80’).
  • LT_response at second GENERATE AC - with CDA
  • Case 01 - LTsetting184:  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0170  ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0170.  AIP of LT indicates Combined Data Authentication is supported (AIP byte 1 bit 1 = ‘1’).
  • Case 02 - LTsetting185:  ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0148  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0148  AIP of LT indicates Combined Data Authentication is supported (AIP byte 1 bit 1 = ‘1’).
  • Case 03 - LTsetting182:  ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 013(.  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0188  AIP of LT indicates Combined Data Authentication is supported (AIP byte 1 bit 1 = ‘1’).
  • Case 04 countries. 2CC.151.00 Certificate Expiration Date (4) - LTsetting183:  ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0190.  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0144  AIP of LT indicates Combined Data Authentication is supported (AIP byte 1 bit 1 = ‘1’). Procedure:
  • Case 01: Transaction is performed with TermSetting1 and LTsetting184
  • Case 02: Transaction is performed with TermSetting1 and LTsetting185
  • Case 03: Transaction is performed with TermSetting1 and LTsetting186
  • Case 04: Transaction is performed with TermSetting1 and LTsetting187 Pass Criteria:
  • Parameter received at second GENERATE AC: - The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’)
  • Data received at second GENERATE AC: - Transaction Date set to current date of test - SDA not used (TVR_B1b7=‘0’) - SDA not selected (TVR_B1b2=‘0’) - DDA not used (TVR_B1b4=‘0’) - CDA not failed (TVR_B1b3=‘0’) - XDA not used (TVR_B4b1=‘0’) - XDA not selected (TVR_B1b1=‘0’)
  • Data received in Kernel Data Output: - Offline Data Authentication was performed (TSI_B1b8=‘1’) countries. 2CC.152.00 Certificate Expiration Date (5) Revision: 44c Objective: To ensure that the terminal manage the Certifcate Expiration Date as per SB272 bulletin. Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.4: Book Bulletins - Section SB 272 - Bulletin n°272, Update of Date Management Requirement (January 2023) Terminal ICS Options: Conditions: [Offline Enciphered PIN]
  • Case 01 - LTsetting154:  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0170.  ICC PIN Encipherement Public Key Certificate in LT is calculated with Certificate Expiration Date 0170.  CVM List is 'Enciphered PIN, if terminal supports' (04 03)  AIP of LT indicates Cardholder verification is supported (AIP byte 1 bit 5 = ‘1’).
  • Case 02 - LTsetting155:  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0190.  ICC PIN Encipherement Public Key Certificate in LT is calculated with Certificate Expiration Date 1238.  CVM List is 'Enciphered PIN, if terminal supports' (04 03)  AIP of LT indicates Cardholder verification is supported (AIP byte 1 bit 5 = ‘1’).
  • Case 03 - LTsetting152:  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0148.  ICC PIN Encipherement Public Key Certificate in LT is calculated with Certificate Expiration Date 0178.  CVM List is 'Enciphered PIN, if terminal supports' (04 03)  AIP of LT indicates Cardholder verification is supported (AIP byte 1 bit 5 = ‘1’).
  • Case 04 - LTsetting149: countries. 2CC.152.00 Certificate Expiration Date (5)  Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0170.  ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0170.  ICC PIN Encipherement Public Key Certificate not present.  CVM List is 'Enciphered PIN, if terminal supports' (04 03)  AIP of LT indicates Cardholder verification is supported (AIP byte 1 bit 5 = ‘1’). Procedure:
  • Transaction is performed with TermSetting1 and LTsetting154
  • Transaction is performed with TermSetting1 and LTsetting155
  • Transaction is performed with TermSetting1 and LTsetting154
  • Transaction is performed with TermSetting1 and LTsetting149 Pass Criteria:
  • Terminal display: 'Enter PIN' Message
  • 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: - Transaction Date set to current date of test - Cardholder verification successful (TVR_B3b8=‘0’) - Cardholder verification was performed (TSI_B1b7='1') - CVM Results = '04 03 02' countries. 2CC.153.00 Certificate Expiration Date (6) Revision: 44c Objective: To ensure that the terminal manage the Certifcate Expiration Date as per SB272 bulletin. Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.4: Book Bulletins - Section SB 272 - Bulletin n°272, Update of Date Management Requirement (January 2023) Terminal ICS Options: Conditions: Procedure: [Offline Enciphered PIN] AND [SDA]
  • LTsetting149: - Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0170. - ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0170. - ICC PIN Encipherement Public Key Certificate not present. - CVM List is 'Enciphered PIN, if terminal supports' (04 03) - AIP of LT indicates Cardholder verification and SDA only are supported (AIP byte 1 bit 5 = ‘1’ and byte 1 bit 7 = '1').
  • Transaction is performed with TermSetting1 and LTsetting149 Pass Criteria:
  • Terminal display: 'Enter PIN' Message
  • 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: - Transaction Date set to current date of test - SDA not failed (TVR_B1b7=‘0’) - SDA selected (TVR_B1b2=‘1’) - DDA not used (TVR_B1b4=‘0’) - CDA not used (TVR_B1b3=‘0’) - XDA not used (TVR_B4b1=‘0’) - XDA not selected (TVR_B1b1=‘0’) - Offline Data Authentication was performed (TSI_B1b8=‘1’) - Cardholder verification successful (TVR_B3b8=‘0’) - Cardholder verification was performed (TSI_B1b7='1') countries. 2CC.154.00 Certificate Expiration Date (7) Revision: 44c Objective: To ensure that the terminal manage the Certifcate Expiration Date as per SB272 bulletin. Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.4: Book Bulletins - Section SB 272 - Bulletin n°272, Update of Date Management Requirement (January 2023) Terminal ICS Options: Conditions: Procedure: [Offline Enciphered PIN] AND [DDA]
  • LTsetting150: - ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0172 - Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0172 - ICC PIN Encipherement Public Key Certificate not present. - CVM List is 'Enciphered PIN, if terminal supports' (04 03) - AIP of LT indicates Cardholder verification and DDA only are supported (AIP byte 1 bit 5 = ‘1’ and byte 1 bit 6 = '1').
  • Transaction is performed with TermSetting1 and LTsetting150 Pass Criteria:
  • Terminal display: 'Enter PIN' Message
  • 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: - Transaction Date set to current date of test - SDA not used (TVR_B1b7=‘0’) - SDA not selected (TVR_B1b2=‘0’) - DDA not failed (TVR_B1b4=‘0’) - CDA not used (TVR_B1b3=‘0’) - XDA not used (TVR_B4b1=‘0’) - XDA not selected (TVR_B1b1=‘0’) - Offline Data Authentication was performed (TSI_B1b8=‘1’) - Cardholder verification successful (TVR_B3b8=‘0’) - Cardholder verification was performed (TSI_B1b7='1') - CVM Results = '04 03 02' countries. 2CC.155.00 Certificate Expiration Date (8) Revision: 44c Objective: To ensure that the terminal manage the Certifcate Expiration Date as per SB272 bulletin. Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.4: Book Bulletins - Section SB 272 - Bulletin n°272, Update of Date Management Requirement (January 2023) Terminal ICS Options: Conditions: Procedure: Pass Criteria: [Offline Enciphered PIN] AND [CDA] AND ([Offline Only] OR [Offline/Online Capable])
  • LTsetting184: - Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0170 - ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0170. - ICC PIN Encipherement Public Key Certificate not present. - CVM List is 'Enciphered PIN, if terminal supports' (04 03) - AIP of LT indicates Cardholder verification and Combined Data Authentication is supported (AIP byte 1 bit 5 = ‘1’ and byte 1 bit 1 = ‘1’).
  • Transaction is performed with TermSetting1 and LTsetting184
  • 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 at first GENERATE AC: - Transaction Date set to current date of test - SDA not used (TVR_B1b7=‘0’) - SDA not selected (TVR_B1b2=‘0’) - DDA not used (TVR_B1b4=‘0’) - CDA not failed (TVR_B1b3=‘0’) - XDA not used (TVR_B4b1=‘0’) - XDA not selected (TVR_B1b1=‘0’) - Cardholder verification successful (TVR_B3b8=‘0’) - Cardholder verification was performed (TSI_B1b7='1')
  • Data received in Kernel Data Output: - Offline Data Authentication was performed (TSI_B1b8=‘1’) countries. 2CC.156.00 Certificate Expiration Date (9) Revision: 44c Objective: To ensure that the terminal manage the Certifcate Expiration Date as per SB272 bulletin. Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.4: Book Bulletins - Section SB 272 - Bulletin n°272, Update of Date Management Requirement (January 2023) Terminal ICS Options: Conditions: Procedure: Pass Criteria: [Offline Enciphered PIN] AND ([CDA Mode1] OR [CDA Mode2]) AND ([Online Only] OR [Offline/Online Capable])
  • LT_response at first GENERATE AC - Cryptogram Information Data ‘9F27’ responding an ARQC (‘80’) with CDA.
  • LTsetting184: - Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0170 - ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0170. - ICC PIN Encipherement Public Key Certificate not present. - CVM List is 'Enciphered PIN, if terminal supports' (04 03) - AIP of LT indicates Cardholder verification and Combined Data Authentication is supported (AIP byte 1 bit 5 = ‘1’ and byte 1 bit 1 = ‘1’).
  • Transaction is performed with TermSetting1 and LTsetting184
  • Parameter received at second GENERATE AC: - The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’)
  • Data received at first GENERATE AC: - Transaction Date set to current date of test - SDA not used (TVR_B1b7=‘0’) - SDA not selected (TVR_B1b2=‘0’) - DDA not used (TVR_B1b4=‘0’) - CDA not failed (TVR_B1b3=‘0’) - XDA not used (TVR_B4b1=‘0’) - XDA not selected (TVR_B1b1=‘0’) - Cardholder verification successful (TVR_B3b8=‘0’) - Cardholder verification was performed (TSI_B1b7='1')
  • Data received in Kernel Data Output: countries. 2CC.156.00 Certificate Expiration Date (9) - Offline Data Authentication was performed (TSI_B1b8=‘1’) countries. 2CC.157.00 Certificate Expiration Date (10) Revision: 44c Objective: To ensure that the terminal manage the Certifcate Expiration Date as per SB272 bulletin. Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.4: Book Bulletins - Section SB 272 - Bulletin n°272, Update of Date Management Requirement (January 2023) Terminal ICS Options: Conditions: Procedure: Pass Criteria: [Offline Enciphered PIN] AND [CDA Mode4] AND ([Online Only] OR [Offline/Online Capable])
  • LT_response at first GENERATE AC - Cryptogram Information Data ‘9F27’ responding an ARQC (‘80’).
  • LT_response at second GENERATE AC - with CDA
  • LTsetting184: - Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date 0170 - ICC Public Key Certificate in LT is calculated with Certificate Expiration Date 0170. - ICC PIN Encipherement Public Key Certificate not present. - CVM List is 'Enciphered PIN, if terminal supports' (04 03) - AIP of LT indicates Cardholder verification and Combined Data Authentication is supported (AIP byte 1 bit 5 = ‘1’ and byte 1 bit 1 = ‘1’).
  • Transaction is performed with TermSetting1 and LTsetting184
  • Parameter received at second GENERATE AC: - The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’)
  • Data received at second GENERATE AC: - Transaction Date set to current date of test - SDA not used (TVR_B1b7=‘0’) - SDA not selected (TVR_B1b2=‘0’) - DDA not used (TVR_B1b4=‘0’) - CDA not failed (TVR_B1b3=‘0’) - XDA not used (TVR_B4b1=‘0’) - XDA not selected (TVR_B1b1=‘0’) - Cardholder verification successful (TVR_B3b8=‘0’) countries. 2CC.157.00 Certificate Expiration Date (10) - Cardholder verification was performed (TSI_B1b7='1')
  • Data received in Kernel Data Output: - Offline Data Authentication was performed (TSI_B1b8=‘1’) countries. 2CJ.098.00 CVM processing fails and no more CVRs in the CVM List Revision: 44c Objective: To ensure that the terminal fails the Cardholder verification and sets the 'Cardholder verification was not successful' bit in the TVR to 1b, if a CVM processing fails, the 'Apply succeeding Cardholder Verification Rule if this CVM is unsuccessful' bit is set to 1b, and there are no more Cardholder Verification Rules in the CVM List. Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.4: Terminal [Offline Plaintext PIN] ICS Options: Conditions:
  • Case 01 - LTsetting191:  AIP of LT indicates Cardholder Verification is supported  CVM List has the value '00000000000000004100' (Plaintext PIN verified by ICC, always). - Action:  Cardholder enters a wrong PIN.
  • Case 02 - LTsetting192:  AIP of LT indicates Cardholder Verification is supported  CVM List has the value '00000000000000004000' (Fail CVM, always) Procedure:
  • Case 01: Transaction is performed with TermSetting1 and LTsetting191
  • Case 02: Transaction is performed with TermSetting1 and LTsetting192 Pass Criteria:
  • Parameter received at first or second GENERATE AC: - The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’)
  • Data received at first GENERATE AC: - Cardholder verification failed (TVR_B3b8=‘1’) - Cardholder verification was performed (TSI_B1b7='1')
  • Case 01: CVM Result = 41 00 01
  • Case 02: CVM Result = 40 00 01 countries. 2CJ.098.01 CVM processing fails and no more CVRs in the CVM List Revision: 44c Objective: To ensure that the terminal fails the Cardholder verification and sets the 'Cardholder verification was not successful' bit in the TVR to 1b, if a CVM processing fails, the 'Apply succeeding Cardholder Verification Rule if this CVM is unsuccessful' bit is set to 1b, and there are no more Cardholder Verification Rules in the CVM List. Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.4: Terminal NOT[Offline Plaintext PIN] ICS Options: Conditions:
  • Case 01 - LTsetting191:  AIP of LT indicates Cardholder Verification is supported  CVM List has the value '00000000000000004100' (Plaintext PIN verified by ICC, always). Procedure:
  • Case 02 - LTsetting192:  AIP of LT indicates Cardholder Verification is supported  CVM List has the value '00000000000000004000' (Fail CVM, always)
  • Case 01: Transaction is performed with TermSetting1 and LTsetting191
  • Case 02: Transaction is performed with TermSetting1 and LTsetting192 Pass Criteria:
  • Parameter received at first or second GENERATE AC: - The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’)
  • Data received at first GENERATE AC: - Cardholder verification failed (TVR_B3b8=‘1’) - Cardholder verification was performed (TSI_B1b7='1')
  • Case 01: CVM Result = 3F 00 01
  • Case 02: CVM Result = 40 00 01 countries. 2CJ.112.00 Online PIN is the selected CVM and the online PIN processing is successful Revision: 44c Objective: To ensure that the terminal considers the CVM as successful, if enciphered PIN verified online is the selected CVM and Issuer answered that PIN presented is good. To ensure that the PIN Pad enciphers the PIN upon entry for transmission in the authorization or financial transaction, if CVM is online PIN verification. To ensure that the terminal sets the CVM Results byte 3 to 'unknown' when PIN is entered for online verification. Reference Book 3 - Section 10.5.2 - Online PIN Processin EMV 4.4: Book 4 - Section 6.3.4.5 - CVM Results Terminal [Online Enciphered PIN] ICS Options: Conditions:
  • LTsetting167: - AIP of LT indicates Cardholder Verification is supported (AIP byte 1 bit 5 = ‘1’). - CVM List has the value '00000000000000000200', 'Enciphered Online PIN verification, Always' (02 00)
  • Issuer_response: - Issuer response indicates approval. Procedure: Pass Criteria: Transaction is performed with TermSetting1 and LTsetting167
  • Parameter received at second GENERATE AC: - The terminal shall process the transaction until completion, by requesting a TC (P1_b8='0' AND P1_b7=‘1’)
  • Data received at first GENERATE AC: - Cardholder verification successful (TVR_B3b8=‘0’) - Online PIN entered (TVR_B3b3=‘1’) - Cardholder verification was performed (TSI_B1b7='1') - CVM Results = '02 00 00' countries. 2CK.010.00 Card responds with an ARQC on first GENERATE AC Revision: 44c Objective: To ensure that if the card responds with an ARQC to first GENERATE AC and is permitted to do so and if terminal has online capability, the Kernel prepares a Kernel Data Output for an authorization or financial request message Reference Book 3 - Section 9.3.1 - GENERATE AC (First Issuance) EMV 4.4: Terminal [Online Only] OR [Offline/Online Capable] ICS Options: Conditions:
  • LT_response at first GENERATE AC - Cryptogram Information Data ‘9F27’ responding an ARQC with Advice (‘08’) Procedure:
  • Transaction is performed with TermSetting1 and LTsetting1 Pass Criteria:
  • A Kernel Data Output shall be send after first Generate AC and before second Generate AC containing at least Cryptogram Information Data ‘9F27’ responding an ARQC (‘88’). countries. 2CM.025.00 Terminal Prints Receipt With Line for Cardholder Signature Revision: 44c Objective: To ensure that the terminal prints a receipt with line for Cardholder signature when signature is the applicable CVM Reference Book 4 - Section 6.3.4.4 - Signature EMV 4.4: Terminal [Signature] ICS Options: Conditions:
  • LTsetting194: - AIP of LT indicates Cardholder Verification is supported (AIP byte 1 bit 5 = ‘1’). - CVM is Signature, always (1E 00) Procedure:
  • Transaction is performed with TermSetting1 and LTsetting194 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’)
  • Terminal shall print a line for Cardholder signature either on merchant receipt OR by using an electronic panel countries. 2CM.094.00 Calculation, Storage, and Display Date-Dependant Fields For Year 2000 + Revision: 44c Objective: To ensure that the terminal is able to accurately calculate and store date dependent fields representing the year 2000 Reference Book 4 - Section 6.7.3 - Date Management EMV 4.4: Terminal [Internal Date Management] ICS Options: Conditions:
  • LTsetting1: - CDOL1 requests Transaction Date and Transaction Time
  • Case 01: - TermSetting1:
  • Terminal Date is set to 31/12/2032 23h59min
  • Case 02: - TermSetting1:
  • Terminal Date set to 28/02/2027 23h59min
  • Case 03: - TermSetting1: Procedure:
  • Terminal Date is set to 28/02/2040 23h59min
  • Wait a minute before performing Transaction
  • 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’)
  • Case 01 - Data received at first GENERATE AC:
  • Transaction Date set to 01/01/2033
  • Case 02 - Data received at first GENERATE AC:
  • Transaction Date set to 01/03/2027
  • Case 02 - Data received at first GENERATE AC:
  • Transaction Date set to 29/02/2040 countries. 2CM.094.01 Calculation, Storage, and Display Date-Dependant Fields For Year 2000 + Revision: 44c Objective: To ensure that the terminal is able to accurately calculate and store date dependent fields representing the year 2000 Reference Book 4 - Section 6.7.3 - Date Management EMV 4.4: Terminal [Online Only] AND NOT[Internal Date Management] ICS Options: Conditions:
  • LTsetting1: - CDOL1 requests Transaction Date and Transaction Time
  • Case 01: - TermSetting1:
  • Terminal Date is set to 31/12/2032 23h59min
  • Case 02: - TermSetting1:
  • Terminal Date set to 28/02/2027 23h59min
  • Case 03: - TermSetting1: Procedure:
  • Terminal Date is set to 28/02/2040 23h59min
  • Wait a minute before performing Transaction
  • 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’)
  • Case 01 - Data received at first GENERATE AC:
  • Transaction Date set to 01/01/2033
  • Case 02 - Data received at first GENERATE AC:
  • Transaction Date set to 01/03/2027
  • Case 02 - Data received at first GENERATE AC:
  • Transaction Date set to 29/02/2040 countries. countries. countries.

Legal Notice

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

countries.