TTA Bulletin nº 243: Contactless Product – Book A & B Test Cases v2.8a Support of SB249 – EMV® Contactless Book A Update

v1.0 Type Approval Bulletins
Contactless Acceptance Device

EMV<sup>®</sup> Terminal Type Approval Bulletin No. 243 First Edition, September 2020 Terminal Contactless Product – Book A & B Test Cases v2.8a Support of SB249 - EMV Contactless Book A Update

Applicability

This Bulletin applies to:

  • EMV Contactless Specifications for Payment Systems, Book A Architecture and General Requirements, Version 2.8, April 2019

Related Documents

  • N/A

Effective Date

  • October 15, 2020

Description

EMVCo introduced the Specification Bulletin 249 - EMV Contactless Book A Update. Related to this bulletin, a new test case is introduced and some are updated in the EMVCo Type Approval Book A & B Test Cases – version 2.8a Update to EMVCo Type Approval Book A & B Test Cases –version 2.8a Revised test cases: 2EA.014.03 (subcase 1, 2 and 3) New test cases: 2EA.014.03 (subcase4) Deleted test cases: None

countries.

2EA.014.03 PIN’ Test No: Objective: Restart in D and second Outcome ‘Request Online - Revision 2.9a - Number of sub cases: 4 To ensure that the reader shall support a first Outcome ‘Online Requested’ followed by a restart in D with the second Outcome ’Request Online PIN’ with online response ‘Any’, or the value of the Outcome Parameter online response is ‘EMV Data’ and at least one of the following Data is present: - Issuer Authentication Data (Tag ‘91’) - Issuer Script Template (tag’71’, tag ‘72’) Reference BOOK A/B: Terminal Configuration: Conditions: and a third Outcome ‘Approved’, ‘Declined’, or ‘End Application’, with the corresponding message displayed at 2nd outcome and 3rd restart and a receipt at end of transaction. [Book A] - Requirement 6.3, 8.1.1.19, 8.1.1.20, 8.1.1.21, 8.1.1.22 EMV Draft Specification Bulletion N° 249 september 20 8.1.1.24 NA

  • Case01: Entry Point transaction is performed with [LTsetting1.137] (1st Outcome Start = ’D’, ‘Online Request’, online response data = ‘EMV Data’, Issuer Authentication Data (tag 91) is received; 2nd Outcome Start = ’D’, ‘Request Online PIN’, online response data = ‘EMV Data’, UI Request on Outcome = Yes, UI Request on restart = No; 3rd Outcome ‘Approved, Receipt=yes’)
  • Case02: Entry Point transaction is performed with [LTsetting1.138] (1st Outcome Start = ’D’, ‘Online Request’, online response data = ‘EMV Data’, Issuer Script Template (tag 71) is received; 2nd Outcome Start = ’D’, ‘Request Online PIN’, online response data = ‘EMV Data’, UI Request on Outcome = Yes, UI Request on restart = No; 3rd Outcome ‘Declined’)
  • Case03: Entry Point transaction is performed with [LTsetting1.139] (1st Outcome Start = ’D’, ‘Online Request’, online response data = ‘EMV Data’, Issuer Script Template (tag 72) are received; 2nd Outcome Start = ’D’, ‘Request Online PIN’, online response data = ‘EMV Data’, UI Request on Outcome = Yes, UI Request on restart = No; 3rd Outcome ‘End Application)
  • Case04: Entry Point transaction is performed with [LTsetting1.153] (1st Outcome Start = ’D’, ‘Online Request’, online response = Any; 2nd Outcome Start = ’D’, ‘Request Online PIN’, online response = Any, UI Request on Outcome = Yes, UI Request on restart = No; 3rd Outcome ‘Approved, Receipt=yes’) Action: Procedure: Pass Criteria: NA Entry Point transaction is performed for [Termsetting1] with different LT settings.
  • Case01: The LT shall not receive the SELECT command with PPSE at 2nd restart
  • Case01: The LT shall not receive the SELECT AID ‘A0000000040004’ (corresponding to the APP4 AID) at 2nd restart countries. 2EA.014.03 PIN’ Restart in D and second Outcome ‘Request Online
  • Case01: The UI Request on Outcome: MSG ID ‘09’ ("Please Enter Your PIN") is correctly displayed at 2nd Outcome.
  • Case01: The LT shall receive in the 3rd GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 1 (Restart Flag set).
  • Case01: The LT shall receive in the 3rd GET PROCESSING OPTIONS data field: Start is set to ‘0D’
  • Case01: The LT shall receive in the 3rd GET PROCESSING OPTIONS data field: Issuer Authentication Data are set with the value transmitted
  • Case01: The UI Request on Outcome: MSG ID ‘03’ ("Approved") is correctly displayed at end of the transaction
  • Case01: a receipt is provided at end of transaction
  • Case02: The LT shall not receive the SELECT command with PPSE at 2nd restart
  • Case02: The LT shall not receive the SELECT AID ‘A0000000040004’ (corresponding to the APP4 AID) at 2nd restart
  • Case02: The UI Request on Outcome: MSG ID 09‘’ ("Please Enter Your PIN") is correctly displayed at 2nd Outcome.
  • Case02: The LT shall receive in the 3rd GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 1 (Restart Flag set).
  • Case02: The LT shall receive in the 3rd GET PROCESSING OPTIONS data field: Start is set to ‘0D’
  • Case02: The LT shall receive in the 3rd GET PROCESSING OPTIONS data field: Issuer script template (tag 71) are set with the value transmitted
  • Case02: The UI Request on Outcome: MSG ID ‘07’ ("Not Authorised") is correctly displayed at end of the transaction
  • Case03: The LT shall not receive the SELECT command with PPSE at 2nd restart
  • Case03: The LT shall not receive the SELECT AID ‘A0000000040004’ (corresponding to the APP4 AID) at 2nd restart
  • Case03: The UI Request on Outcome: MSG ID 09‘’ ("Please Enter Your PIN") is correctly displayed at 2nd Outcome.
  • Case03: The LT shall receive in the 3rd GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 1 (Restart Flag set). countries. 2EA.014.03 PIN’ Restart in D and second Outcome ‘Request Online
  • Case03: The LT shall receive in the 3rd GET PROCESSING OPTIONS data field: Start is set to ‘0D’
  • Case03: The LT shall receive in the 3rd GET PROCESSING OPTIONS data field: Issuer script Template (tag 72) are set with the value transmitted
  • Case03: The UI Request on Outcome: MSG ID ‘1C’ ("Insert, Swipe or Try Another Card") is correctly displayed at end of the transaction
  • Case04: The LT shall not receive the SELECT command with PPSE at 2nd restart
  • Case04: The LT shall not receive the SELECT AID ‘A0000000040004’ (corresponding to the APP4 AID) at 2nd restart
  • Case04: The UI Request on Outcome: MSG ID ‘09’ ("Please Enter Your PIN") is correctly displayed at 2nd Outcome.
  • Case04: The LT shall receive in the 3rd GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 1 (Restart Flag set).
  • Case04: The LT shall receive in the 3rd GET PROCESSING OPTIONS data field: Start is set to ‘0D’
  • Case04: The UI Request on Outcome: MSG ID ‘03’ ("Approved") is correctly displayed at end of the transaction
  • Case04: a receipt is provided at end of transaction countries. Updated LTSetting: [Ltsetting1.137] characteristics:
  • Single AID APP4 (with associated Kernel ID = 24)
  • PDOL with Pre-Processing indicator, restart, start, Issuer Authentication Data
  • When Restart = 0, GPO Response indicates o the 1st Outcome ‘online request’ o start D
  • Online Response Data: EMV data
  • CVM:NA
  • UI Request on Outcome Present: No
  • UI Request on Restart Present: No
  • Data Record Present: No
  • Discretionary Data Present: No
  • Alternate Interface Preference: NA
  • Receipt: No
  • Field Off Request: NA
  • Removal Timeout: 10s
  • When Restart = 1 (1st restart), GPO Response indicates o the 2nd Outcome ‘Request Online PIN’ o start D
  • Online Response Data: EMV data ( tag ‘91’)
  • CVM:online PIN
  • UI Request on Outcome Present: Yes
  • UI Request on Restart Present: No
  • Data Record Present: Yes
  • Discretionary Data Present: Yes
  • Alternate Interface Preference: NA
  • Receipt: No
  • Field Off Request: NA
  • Removal Timeout: 10s
  • UI Request on 2nd Outcome: MSG ID 09 ‘Please Enter Your PIN’
  • When Restart = 1 (2nd Restart), GPO Response indicates the Final Outcome ‘Approved’ countries.
  • CVM: N/A
  • Receipt: yes Data PPSE Directory Entry 1 Value
  • AID = ‘A0000000040004’
  • Label = ‘APP4’
  • Kernel Identifier = 24
  • API = ‘01’ AID FCI 1
  • AID = ‘A0000000040004’
  • Label = ‘APP4’
  • API = ‘01’
  • PDOL = ‘D102D2019110’ Outcome 1 GPO response
  • Outcome Value = ’05’
  • Start value = ‘0D’
  • Online Response Data = ‘01’
  • CVM value = ‘00’
  • Alternate Interface Preference value = ‘00’
  • Receipt value = ‘00’
  • Field Off Request value = ‘FFFF’
  • Removal Timeout value = ‘0064’ Online Response 1 GPO response Outcome 2 GPO response
  • Tag 91 = ’0102030405060708090A0B0C0D0E0F10’
  • Outcome Value = ’06’
  • Start value = ‘0D’
  • Online Response Data = ‘01’
  • CVM value = ‘01’
  • Alternate Interface Preference value = ‘00’
  • Receipt value = ‘00’
  • Field Off Request value = ‘FFFF’
  • Removal Timeout value = ‘0064’ UI Request on Outcome o
  • Message ID value = ’09’ countries. 2 GPO response Online Response 2 GPO response Outcome 3 GPO response UI Request on Outcome 3 GPO response
  • Status value = ‘05’
  • Hold Time value = ‘0032’
  • Language Preference value = ‘0000’
  • Value Qualifier value = ‘00’
  • Value = ‘000000000000’
  • Currency Code = ‘0000’
  • Tag 91 = ‘1112131415161718191A1B1C1D1E1F20’
  • Outcome Value = ’03’
  • Start value = ‘00’
  • Online Response Data = ‘00’
  • CVM value = ‘00’
  • Alternate Interface Preference value = ‘00’
  • Receipt value = ‘01’
  • Field Off Request value = ‘FFFF’
  • Removal Timeout value = ‘0000’
  • Message ID value = ’03’
  • Status value = ‘05’
  • Hold Time value = ‘0032’
  • Language Preference value = ‘0000’
  • Value Qualifier value = ‘00’
  • Value = ‘000000000000’
  • Currency Code = ‘0000’ Table C.96: [Ltsetting1.137] [Ltsetting1.138] characteristics:
  • Single AID APP4 (with associated Kernel ID = 24)
  • PDOL with Pre-Processing indicator, restart, start,Issuer script data
  • When Restart = 0, GPO Response indicates o the 1st Outcome ‘online request’ o start D
  • Online Response Data: EMV data countries.
  • CVM:NA
  • UI Request on Outcome Present: No
  • UI Request on Restart Present: No
  • Data Record Present: No
  • Discretionary Data Present: No
  • Alternate Interface Preference: NA
  • Receipt: No
  • Field Off Request: NA
  • Removal Timeout: 10s
  • When Restart = 1 (1st restart), GPO Response indicates o the 2nd Outcome ‘Request Online PIN’ o start D
  • Online Response Data: EMV data ( tag ‘71’)
  • CVM:online PIN
  • UI Request on Outcome Present: Yes
  • UI Request on Restart Present: No
  • Data Record Present: No
  • Discretionary Data Present: No
  • Alternate Interface Preference: NA
  • Receipt: No
  • Field Off Request: NA
  • Removal Timeout: 10s
  • UI Request on 2nd Outcome: MSG ID 09 ‘Please Enter Your PIN’
  • When Restart = 1 (2nd Restart), GPO Response indicates the Final Outcome ‘Declined’
  • CVM: N/A
  • Receipt: no Data PPSE Directory Entry 1 Value
  • AID = ‘A0000000040004’
  • Label = ‘APP4’
  • Kernel Identifier = 24
  • API = ‘01’ countries. AID FCI 1 Outcome 1 GPO response Online Response 1 GPO response Outcome 2 GPO response UI Request on Outcome 2 GPO response Online Response 2 GPO response
  • AID = ‘A0000000040004’
  • Label = ‘APP4’
  • API = ‘01’
  • PDOL = ‘D102D2017110’
  • Outcome Value = ’05’
  • Start value = ‘0D’
  • Online Response Data = ‘01’
  • CVM value = ‘00’
  • Alternate Interface Preference value = ‘00’
  • Receipt value = ‘00’
  • Field Off Request value = ‘FFFF’
  • Removal Timeout value = ‘0064’
  • Tag 71 = ’0102030405060708090A0B0C0D0E0F10’
  • Outcome Value = ’06’
  • Start value = ‘0D’
  • Online Response Data = ‘01’
  • CVM value = ‘01’
  • Alternate Interface Preference value = ‘00’
  • Receipt value = ‘00’
  • Field Off Request value = ‘FFFF’
  • Removal Timeout value = ‘0064’
  • Message ID value = ’09’
  • Status value = ‘05’
  • Hold Time value = ‘0032’
  • Language Preference value = ‘0000’
  • Value Qualifier value = ‘00’
  • Value = ‘000000000000’
  • Currency Code = ‘0000’
  • Tag 71 = ‘1112131415161718191A1B1C1D1E1F20’ countries. Outcome 3 GPO response UI Request on Outcome 3 GPO response
  • Outcome Value = ’04’
  • Start value = ‘00’
  • Online Response Data = ‘00’
  • CVM value = ‘00’
  • Alternate Interface Preference value = ‘00’
  • Receipt value = ‘00’
  • Field Off Request value = ‘FFFF’
  • Removal Timeout value = ‘0000’
  • Message ID value = ’07’
  • Status value = ‘05’
  • Hold Time value = ‘0032’
  • Language Preference value = ‘0000’
  • Value Qualifier value = ‘00’
  • Value = ‘000000000000’
  • Currency Code = ‘0000’ Table C.97: [Ltsetting1.138] [Ltsetting1.139] characteristics:
  • Single AID APP4 (with associated Kernel ID = 24)
  • PDOL with Pre-Processing indicator, restart, start, Issuer script data
  • When Restart = 0, GPO Response indicates o the 1st Outcome ‘online request’ o start D
  • Online Response Data: EMV data
  • CVM:NA
  • UI Request on Outcome Present: No
  • UI Request on Restart Present: No
  • Data Record Present: No
  • Discretionary Data Present: No
  • Alternate Interface Preference: NA
  • Receipt: No countries.
  • Field Off Request: NA
  • Removal Timeout: 10s
  • When Restart = 1 (1st restart), GPO Response indicates o the 2nd Outcome ‘Request Online PIN’ o start D
  • Online Response Data: EMV data ( tag ‘72’)
  • CVM:online PIN
  • UI Request on Outcome Present: Yes
  • UI Request on Restart Present: No
  • Data Record Present: Yes
  • Discretionary Data Present: No
  • Alternate Interface Preference: NA
  • Receipt: No
  • Field Off Request: NA
  • Removal Timeout: 10s
  • UI Request on 2nd Outcome: MSG ID 09 ‘Please Enter Your PIN’
  • When Restart = 1 (2nd Restart), GPO Response indicates the Final Outcome ‘End Application’
  • CVM: N/A
  • Receipt: no Data PPSE Directory Entry 1 Value
  • AID = ‘A0000000040004’
  • Label = ‘APP4’
  • Kernel Identifier = 24
  • API = ‘01’ AID FCI 1
  • AID = ‘A0000000040004’
  • Label = ‘APP4’
  • API = ‘01’
  • PDOL = ‘D102D2017210’ Outcome 1 GPO response
  • Outcome Value = ’05’
  • Start value = ‘0D’
  • Online Response Data = ‘01’ countries. Online Response 1 GPO response Outcome 2 GPO response Online Response 2 GPO response Outcome 3 GPO response UI Request on Outcome 3 GPO response
  • CVM value = ‘00’
  • Alternate Interface Preference value = ‘00’
  • Receipt value = ‘00’
  • Field Off Request value = ‘FFFF’
  • Removal Timeout value = ‘0064’
  • Tag 72 = ’0102030405060708090A0B0C0D0E0F10’
  • Outcome Value = ’06’
  • Start value = ‘0D’
  • Online Response Data = ‘01’
  • CVM value = ‘01’
  • Alternate Interface Preference value = ‘00’
  • Receipt value = ‘00’
  • Field Off Request value = ‘FFFF’
  • Removal Timeout value = ‘0064’ o
  • Tag 72 = ‘1112131415161718191A1B1C1D1E1F20’
  • Outcome Value = ’07’
  • Start value = ‘00’
  • Online Response Data = ‘00’
  • CVM value = ‘00’
  • Alternate Interface Preference value = ‘00’
  • Receipt value = ‘00’
  • Field Off Request value = ‘FFFF’
  • Removal Timeout value = ‘0000’
  • Message ID value = ’1C’
  • Status value = ‘05’
  • Hold Time value = ‘0032’
  • Language Preference value = ‘0000’
  • Value Qualifier value = ‘00’ countries.
  • Value = ‘000000000000’
  • Currency Code = ‘0000’ Table C.98: [Ltsetting1.139] New LTSetting: [Ltsetting1.153] characteristics:
  • Single AID APP4 (with associated Kernel ID = 24)
  • PDOL with Pre-Processing indicator, restart, start,
  • When Restart = 0, GPO Response indicates o the 1st Outcome ‘online request’ o start D
  • Online Response:Any
  • CVM:NA
  • UI Request on Outcome Present: No
  • UI Request on Restart Present: No
  • Data Record Present: No
  • Discretionary Data Present: No
  • Alternate Interface Preference: NA
  • Receipt: No
  • Field Off Request: NA
  • Removal Timeout: 10s
  • When Restart = 1 (1st restart), GPO Response indicates o the 2nd Outcome ‘Request Online PIN’ o start D
  • Online Response: Any
  • CVM:online PIN
  • UI Request on Outcome Present: Yes
  • UI Request on Restart Present: No
  • Data Record Present: Yes
  • Discretionary Data Present: Yes countries.
  • Alternate Interface Preference: NA
  • Receipt: No
  • Field Off Request: NA
  • Removal Timeout: 10s
  • UI Request on 2nd Outcome: MSG ID 09 ‘Please Enter Your PIN’
  • When Restart = 1 (2nd Restart), GPO Response indicates the Final Outcome ‘Approved’
  • CVM: N/A
  • Receipt: yes Data PPSE Directory Entry 1 Value
  • AID = ‘A0000000040004’
  • Label = ‘APP4’
  • Kernel Identifier = 24
  • API = ‘01’ AID FCI 1
  • AID = ‘A0000000040004’
  • Label = ‘APP4’
  • API = ‘01’
  • PDOL = ‘D102D201’ Outcome 1 GPO response
  • Outcome Value = ’05’
  • Start value = ‘0D’
  • Online Response Data = ‘02’
  • CVM value = ‘00’
  • Alternate Interface Preference value = ‘00’
  • Receipt value = ‘00’
  • Field Off Request value = ‘FFFF’
  • Removal Timeout value = ‘0064’ Outcome 2 GPO response
  • Outcome Value = ’06’
  • Start value = ‘0D’
  • Online Response Data = ‘02’
  • CVM value = ‘01’
  • Alternate Interface Preference value = ‘00’
  • Receipt value = ‘00’ countries. UI Request on Outcome 2 GPO response Outcome 3 GPO response UI Request on Outcome 3 GPO response
  • Field Off Request value = ‘FFFF’
  • Removal Timeout value = ‘0064’
  • Message ID value = ’09’
  • Status value = ‘05’
  • Hold Time value = ‘0032’
  • Language Preference value = ‘0000’
  • Value Qualifier value = ‘00’
  • Value = ‘000000000000’
  • Currency Code = ‘0000’
  • Outcome Value = ’03’
  • Start value = ‘00’
  • Online Response Data = ‘00’
  • CVM value = ‘00’
  • Alternate Interface Preference value = ‘00’
  • Receipt value = ‘01’
  • Field Off Request value = ‘FFFF’
  • Removal Timeout value = ‘0000’
  • Message ID value = ’03’
  • Status value = ‘05’
  • Hold Time value = ‘0032’
  • Language Preference value = ‘0000’
  • Value Qualifier value = ‘00’
  • Value = ‘000000000000’
  • Currency Code = ‘0000’ Table C.112: [Ltsetting1.153] 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 NON-INFRINGEMENT, 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.