PCI Watch

Tracking changes across the Payment Card Industry

EMV® Terminal Type Approval - Entry Point - Test Cases

v2.11d Test Cases & Test Environments
Contactless Acceptance Device

EMV® Terminal Type Approval Entry Point Test Cases Version 2.11d June 2026 EMV® Terminal Type Approval Entry Point Test Cases v2.11d

Legal Notice

This document 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 EMV® Terminal Type Approval Entry Point Test Cases v2.11d

for any party's infringement of any intellectual property rights in connection with this document. EMV® Terminal Type Approval Entry Point Test Cases v2.11d

Version History Version Date Revision Description 2.11d

  • Rename document as Entry Point
  • System testing and related LT settings are moved to the System Test Plan
  • Moved Termsetting to the Product Testing Environment document
  • Corrected Test Cases: 2EA.004.00, 2EA.004.01, 2EC.001.00, 2EC.001.10, 2EC.001.11, 2EC.001.12, 2EC.001.13, 2EC.001.14, 2EC.001.16, 2EE.009.00
  • New Test Cases: 2EC.001.17, 2EC.001.18, 2ED.009.33, 2ED.009.34, 2ED.009.35, 2ED.009.36, 2ED.036.00
  • Versioning policy of the present document: This current version 2.11d follows the current Entry Point Specification revision number, where.d is incremented (a, b, c, …) for each new revision of the present document issued to correct any issues, or to incorporate Type Approval Bulletins. EMV® Terminal Type Approval Entry Point Test Cases v2.11d 1. 2. 3. 4. 5. 6. 7. 7.1. 7.3. 8. 8.1. 8.2. 8.3. 9. 9.1. 2EA.004. 2EA.004. 2EA.005. 2EA.006. 2EA.006. 2EA.007. 2EA.007. 2EA.011. 2EA.012. 2EA.013. 2EA.013. 2EA.014. 2EA.014. 2EA.014. 2EA.014. 2EA.014. 2EA.016. 2EA.017. 2EA.017. 2EA.017. 2EA.018. 2EA.019. 2EA.019. 2EA.020. 2EA.021. EMV® Terminal Type Approval Entry Point Test Cases v2.11d 9.2. 2EB.001. 2EB.001. 2EB.002. 2EB.003. 2EB.003. 2EB.003. 2EB.004. 2EB.004. 2EB.004. 2EB.005. 2EB.005. 2EB.006. 2EB.006.01 Status Check present and set, Amount different from 1 with Transaction Type ‘Purchase’. 88 2EB.007. 2EB.007. 2EB.008. 2EB.008. 2EB.008. 2EB.008. 2EB.008. 2EB.009. 2EB.009. 2EB.009. 2EB.010. 2EB.010. 2EB.011. 2EB.011. 2EB.011. 2EB.012. 2EB.012. 2EB.013. 2EB.013. 2EB.013. 2EB.014. 2EB.014. 2EB.014. 2EB.015. 2EB.015. 2EB.015. 2EB.016. 2EB.016. EMV® Terminal Type Approval Entry Point Test Cases v2.11d 2EB.016. 2EB.017. 2EB.017. 2EB.017. 2EB.018. 2EB.018. 2EB.018. 2EB.019. 2EB.019. 2EB.019. 2EB.020. 2EB.020. 2EB.021. 2EB.022. 9.3. 2EC.001. 2EC.001. 2EC.001. 2EC.001. 2EC.001. 2EC.001. 2EC.001. 2EC.001. 2EC.001. 2EC.001. 2EC.001. 2EC.001. 2EC.001. 2EC.001. 2EC.001. 2EC.002. 2EC.003. 2EC.004. 2EC.004. 2EC.005. 2EC.005. 2EC.006. 2EC.006. EMV® Terminal Type Approval Entry Point Test Cases v2.11d 2EC.007. 2EC.007. 9.4. 2ED.001. 2ED.001. 2ED.001. 2ED.001. 2ED.003. 2ED.003. 2ED.003. 2ED.003. 2ED.003. 2ED.004. 2ED.004. 2ED.005. 2ED.005. 2ED.007. 2ED.007. 2ED.007. 2ED.007. 2ED.008. 2ED.008. 2ED.009. 2ED.009. 2ED.009. 2ED.009. 2ED.009. 2ED.009. 2ED.009. 2ED.009. 2ED.009. 2ED.009. 2ED.009. EMV® Terminal Type Approval Entry Point Test Cases v2.11d 2ED.009. 2ED.009. 2ED.009. 2ED.009. 2ED.009.31 PPSE select response having a Directory Entry with Kernel AID not Present or = 0 (1). 218 2ED.009.32 PPSE select response having a Directory Entry with Kernel AID not Present or = 0 (2). 219 2ED.009.33 PPSE select response having a Directory Entry with Kernel AID not Present or = 0 (3). 220 2ED.009.34 PPSE select response having a Directory Entry with Kernel AID not Present or = 0 (4). 221 2ED.009.35 PPSE select response having a Directory Entry with Kernel AID not Present or = 0 (5). 222 2ED.009.36 PPSE select response having a Directory Entry with Kernel AID not Present or = 0 (6). 223 2ED.010. 2ED.010. 2ED.011. 2ED.011. 2ED.012. 2ED.012. 2ED.012. 2ED.012. 2ED.012. 2ED.012. 2ED.012. 2ED.012. 2ED.012. 2ED.012. 2ED.013. 2ED.013. 2ED.014. 2ED.014. 2ED.015. 2ED.015. 2ED.015. 2ED.016. 2ED.017. EMV® Terminal Type Approval Entry Point Test Cases v2.11d 2ED.017. 2ED.017. 2ED.017. 2ED.018. 2ED.018. 2ED.018. 2ED.018. 2ED.019. 2ED.019. 2ED.019. 2ED.019. 2ED.021. 2ED.021. 2ED.022. 2ED.023. 2ED.023. 2ED.024. 2ED.024. 2ED.024. 2ED.025. 2ED.026. 2ED.026. 2ED.027. 2ED.028. 2ED.029. 2ED.030. 2ED.031. 2ED.032. 2ED.033. 2ED.034. 2ED.035. 2ED.036. 9.5. 2EE.001. 2EE.001. 2EE.002. 2EE.002. 2EE.003. 2EE.003.01 Kernel Activation of the Selected Combination after a SPI command (Autorun= ‘Yes’)... 301 2EE.004. 2EE.005. EMV® Terminal Type Approval Entry Point Test Cases v2.11d 2EE.006. 2EE.007. 2EE.008. 2EE.009. 9.6. 2EF.001. 2EF.001. 2EF.001. 2EF.002. 2EF.003. 2EF.003. 9.7. [LTSETTING1. [LTSETTING2. [LTSETTING3. [LTSETTING4. [LTSETTING5. [LTSETTING6. [LTSETTING7. [LTSETTING8. EMV® Terminal Type Approval Entry Point Test Cases v2.11d 1.

Scope

EMV Contactless Specifications for Payment Systems – Book A and Book B, define the terminal requirements necessary to select an EMV Contactless Application in an international interchange environment and provides for backward compatibility with already existing Contactless Applications. The present document, 'EMVCo Type Approval – Entry Point - Test Cases’, includes 2 main sections:

  • LT (Card) Test Environment: defines the requirements for the test card in order to perform the tests defined in this document
  • Test Cases: A set of test cases which when applied to the Entry Point Module, are designed to determine whether the Entry Point Module meets the requirements stated in [Book A] and [Book B]. Test cases are defined for unitary tests and functional tests. If any special conditions are required for a specific test case, these conditions are described in the test case. The intended audiences for this document are EMVCo recognised laboratories, Entry Point and Contactless application providers, acquiring members or merchants. Although acquiring members and merchants may reference this document, type approval testing oriented toward Entry Point and Contactless application providers. EMV® Terminal Type Approval Entry Point Test Cases v2.11d 2. Reference documents [N1] EMV Integrated Circuit Card Specification for Payment Systems – Book 1 – Application Independent ICC to Terminal Interface Requirements Version 4.4 – October 2022 [N2] EMV Integrated Circuit Card Application Specification for Payment Systems – Book 2 – Security and Key Management Version 4.4 – October 2022 [N3] EMV Integrated Circuit Card Terminal Specification for Payment Systems – Book 3 – Application Specification Version 4.4 – October 2022 [N4] EMV Integrated Circuit Card Terminal Specification for Payment Systems – Book 4 – Cardholder, Attendant, and Acquirer Interface Requirements Version 4.4 – October 2022 [Book A] EMV Contactless Specifications for Payment Systems – Book A – Architecture and General Requirements Latest version available [Book B] EMV Contactless Specifications for Payment Systems – Book B – Entry Point Specification Latest version available [Book C-n] EMV Contactless Specifications for Payment Systems – Book C-n – kernel Specification, where n refers to Kernel 2 to 8 Latest version available [CL TE] Product Testing Environment Latest version available [ICS] EMVCo Type Approval Contactless Product - Implementation Conformance Statement Latest version available [Symb] Contactless Symbol Reproduction Guidelines Latest version available [TA Admin] EMVCo Type Approval Contactless Product – Administrative Process Latest version available EMVCo Type Approval Contactless Product - EMVCo System Test Plan this includes all additional testing required by each Payment System, such as:
  • Performance Testing ([TA P])
  • Relay Resistance Protocol Accuracy Testing Latest version available EMV® Terminal Type Approval Entry Point Test Cases v2.11d ([TA RRP])
  • Module Integration Testing ([TA MIT])
  • Book A General Requirements Testing ([TA BAGR]) (Book A testing) [MAPP] EMV Terminal Type Approval – Book C-8 – Mobile Test Application Guidelines Latest available EMV® Terminal Type Approval Entry Point Test Cases v2.11d 3. Abbreviations and Notations ADF Application Definition File AID Application Identifier CVM Cardholder verification Method EP Entry Point (refers to Book B Specifications) FCI File Control Information GPO GET PROCESSING OPTIONS ICC Integrated Circuit Card ID Identifier LT Lower tester (Card Simulator) MSG Message NA Not Applicable (or specific value assigned) PDOL Processing Options Data Object List PPSE Proximity Payment System Environment POS Point Of Sale RFU Reserved for Future Use SFI Short File Identifier TLV Tag Length Value TTQ Terminal Transaction Qualifier UI User Interface EMV® Terminal Type Approval Entry Point Test Cases v2.11d 4. Global Glossary Entry Point Module - the Software Module used to select the Kernel according to [Book A] & [Book B]. This Entry Point Module is the Product tested with the present test plan. Implementation conformance statement (ICS) - A form completed by the product provider. The written statement lists all optional functions as specified in the reference specification implemented [Book A] & [Book B]. Kernel: A software Module that may refer to
  • a (Payment System) Kernel: the kernel complies with one of the [Book C-n] specifications (so EMVCo C-n Kernel only). By default a ‘kernel’ refers to a ‘Payment System Kernel’.
  • a Test Kernel: a software module simulating a Kernel C-n that must be present in the product under test for testing reason. The Test Kernel shall be in accordance with the section ‘6.1. Test Kernel definition’.
  • a Kernel C-REGX: a proprietary kernel software present in the Contactless Product where x is a Kernel ID which has been registered following EMVCo kernel ID registration process. C-REGX does not refer to the Payment System Kernels. Laboratory - A facility that performs type approval testing. Lower Tester – Card simulator of the test tool that communicates with the product under test. The LT shall be in accordance with section 7 of the present document. POS System - a POS System is the physical architecture of the Product under test. It is the device that communicates with contactless cards, processes contactless transactions, and may support other payment functionalities such as magnetic stripe or contact chip transactions. The physical architecture can be any of the following:
  • Fully integrated terminal: all elements included in a single device.
  • Intelligent card reader: The reader handles most of the contactless transaction processing, passing the results for completion by the terminal.
  • Combination of terminal and transparent card reader: The reader provides communication with the card, whilst kernels and other processes are in the terminal. Test Kernel – see ‘Kernel’ definition above. Test Payment Application – Software simulating a Payment Application that must be present in the product under test for testing reason. The test payment application shall be in accordance with the section 7 of the present document. EMV® Terminal Type Approval Entry Point Test Cases v2.11d 5. Document Overview The document is organized in several chapters, completed by annexes:
  • Section 7 specifies the LT (Card) Test Environment; it includes the LT Test kernel and a high level of the LT Data Configuration, which is detailed in Annex A
  • Section 8 specifies the Test Structure and the Test Categories.
  • Section 9 contains all the Test Cases definition. This section is divided into 6 subsections to cover all Entry Point requirements of [Book A] & [Book B]. 1. General Requirements 2. Pre-Processing 3. Protocol Activation 4. AID and Kernel Selection 5. Kernel Activation 6. Outcome Processing EMV® Terminal Type Approval Entry Point Test Cases v2.11d 6. Terminal Test Environment Please refer to Product Testing Environment [CL TE] Document for the detail of the Termsettings and related Environment. EMV® Terminal Type Approval Entry Point Test Cases v2.11d 7. LT (Card) Test Environment 7.1. LT (Card)

Requirement

This section describes the functional requirement of the Lower Tester called LT (Card) to perform Entry Point Type Approval, in order to communicate with the Test Kernels. The below commands shall be supported:

  • Select PPSE
  • Send POI Information (SPI)
  • Select AID
  • Get Processing Options 7.1.1 Select PPSE Format For the Select PPSE command, several responses shall be supported:
  • A correctly formatted FCI coded accorded EMV (including one or several template 61, with or without optional data elements). A response length until 252 bytes shall be supported.
  • A wrongly formatted FCI
  • An Error Status Word
  • No response to the Select PPSE command
  • For each LT (Card) data configuration (called LTSetting), a single Select PPSE response is specified.

7.1.2 Send POI Information Format For the Send POI Information command, several responses shall be supported:

  • A correctly formatted FCI coded accorded EMV (including one or several template 61, with or without optional data elements). A response length until 252 bytes shall be supported.
  • A wrongly formatted FCI
  • An Error Status Word
  • No response to the Send POI Information command
  • For each LT (Card) data configuration, at most a single Send POI Information response is specified. EMV® Terminal Type Approval Entry Point Test Cases v2.11d

7.1.3 Select AID format For the Select AID command, several responses shall be supported:

  • A correctly formatted FCI coded accorded EMV (with partial or full AID, with or without PDOL, with or without optional data element). A response length until 252 bytes shall be supported.
  • An Error Status Word
  • No response to the Select AID command
  • For each LT (Card) data configuration, a single Select AID response is specified per AID present in the card. LT (Card) with a single to 4 AIDs shall be supported. The default PDOL content is defined in Annex B.

7.1.4 Get Processing Options format For the Get Processing Options command, several responses shall be supported:

7.1.4.1 Template response (except kernels C-2 and C-8): The Template response is a TLV (Tag ‘77’) constructed data element formatted as follow:

  • Outcome data: A TLV coded data element (tag ‘D4’), which contains the Kernel Outcome that the LT requests. The test kernel will then pass this Outcome to Entry Point. This TLV data contains the following data element (values only):
  • Outcome Value (1 byte), coded in Hex: reflecting the various Outcome value of [Book A] Table 6-1: ‘01’ (Select Next), ‘02’ (Try Again), ‘03’ (Approved), ’04’ (Declined), ‘05’ (online Request), ‘06’ (Try Another Interface), ‘07’ (End Application), ‘08’ (Request Online PIN’) The below data element are the parameters related to the above Outcome:
  • Start value (1 byte): reflecting line 1 (Start) of [Book A] Table 6-2: value ‘0A’, 0B’, ‘0C’ ‘0D’ for A, B, C and D restart, and value’00’ for N/A.
  • Online Response Data (1 byte): reflecting line 2 (Online Response Data) of [Book A] Table 6-2: value ‘01’ for EMV Data, value ‘02’ for Any and value’00’ for N/A
  • CVM value (1 byte): reflecting line 3 (CVM) of [Book A] Table 6-2: value ‘01’, 02’, ‘03’ ‘04’ for Online PIN, Conf Code Verified, Obtain Signature, No CVM, and value’00’ for N/A. EMV® Terminal Type Approval Entry Point Test Cases v2.11d
  • Alternate Interface Preference value (1 byte): reflecting line 8 (Alternate Interface) of [Book A] Table 6-2: value ‘01’, 02’, ‘03’ for Contact Chip, Mag- Stripe and both, and value’00’ for N/A.
  • Receipt value (1 byte): reflecting line 9 (Receipt) of [Book A] Table 6-2: value ‘01’ for provide a receipt, and value’00’ for N/A.
  • Field Off Request value (2 bytes): reflecting line 10 (Field Off request) of [Book A] Table 6-2: hold time unit coded in Hexadecimal (‘FFFF’ for N/A).
  • Removal Timeout value (2 bytes): reflecting line 11 (Removal Timeout) of [Book A] Table 6-2: time out unit coded in Hexadecimal.
  • Online Response Data 1: A TLV coded data element (tag ‘91’), which contain the EMV tag 91 data element which might be present in case of restart
  • Online Response Data 2: A TLV coded data element (tag ‘71’), which contain the EMV tag 71 data element which might be present in case of restart
  • Online Response Data 3: A TLV coded data element (tag ‘72’), which contain the EMV tag 72 data element which might be present in case of restart
  • UI Request on Outcome: A TLV coded data element (tag ‘D5’), which contain the UI request on Outcome that the LT request (TLV coded). This TLV data contains the following data element (values only) of Table 7-1:
  • Message ID value (1 byte): reflecting [Book A] Table 9-5.
  • Status value (1 byte): coded in Hex: reflecting the various status value of [Book A] Table 9-1. First line of the Table has the value ‘01’, second the value ‘02’,...
  • Hold Time value (2 bytes): reflecting line 3 (Hold Time) of [Book A] Table 7-1: hold time unit coded in Hexadecimal.
  • Value Qualifier value (1 byte): reflecting line 5) of [Book A] Table 7-1: value ‘01’ is for Amount and value ‘02’ is for Balance. ‘00’ means Value Qualifier is not present.
  • Value (6 bytes): reflecting line 6 (Value) of [Book A] Table 7-1: follow description of table 7-1. When Value Qualifier is not present (set to ‘00’), this must be filled with zeroes.
  • Currency Code (2 bytes): reflecting line 7 (Currency Code) of [Book A] Table 7-1: follow description of table 7-1. When Value Qualifier is not present (set to ‘00’), this must be filled with zeroes.
  • Language Preference value (2 to 8 bytes): reflecting line 4 of [Book A] Table 7-1: value of EMV tag ‘5F2D’. When no language preference is supported then the value is ‘0000’
  • UI Request on Restart A TLV coded data element (tag ‘D6’), which contain the UI request on Outcome that the LT request (TLV coded). Same coding as above. EMV® Terminal Type Approval Entry Point Test Cases v2.11d
  • Data Record Present A TLV coded constructed data element (tag ‘E1’), which contain the transaction record for clearing that the LT request (TLV coded). This field contain any TLV EMV data element.
  • Discretionary Data Present A TLV coded constructed data element (tag ‘E2’). This field contains any TLV EMV data element. Note about outcome parameters:
  • UI Request on Outcome Present: when ‘UI Request on Outcome’ (tag ‘D5’) is present, ‘UI Request on Outcome Present’ is considered set
  • UI Request on Restart Present: when ‘UI Request on Restart’ (tag ‘D6’) is present,’ UI Request on Restart Present’ is considered set
  • Data Record Present: when ‘Data Record’ (tag ‘E1’) is present,’ Data Record Present ’ is considered set
  • Discretionary Data Present: when ‘Data Record’ (tag ‘E2’) is present,’ Discretionary Data Present ’ is considered set 7.1.4.2 Template response (C-2 kernel) When the test kernel emulates C-2 (i.e. Kernel ID=’02’), the Get Processing Options response follows the rules below. Tag Value Presence ‘77’ Response Message Template Format 2 Mandatory ‘DF8116’ User Interface Request Data (corresponds to the MSG signal) Optional ‘E4’ OUT Mandatory ‘DF8129’ Outcome Parameter Set Mandatory ‘DF8116’ User Interface Request Data Optional ‘FF8105’ Data Record Optional ‘FF8106’ Discretionary Data Optional Table 7.1.4.2: GPO response format for Test Kernel emulating C-2 The Template response is a TLV (Tag ‘77’) constructed data element formatted as follow. The test kernel may then pass the listed data elements to the Entry Point. EMV® Terminal Type Approval Entry Point Test Cases v2.11d
  • UI Request Data: A TLV coded data element (tag ‘DF8116’), which contains the UI Request Data. This data item corresponds to the tag ‘User Interface Request Data’ (13 bytes long) defined in [Book C-2] and must follow the same format. It can either be returned:
  • Out of the ‘E4’ template tag, in which case it corresponds to the MSG signal
  • Within the ‘E4’ template tag
  • In both positions, in which case the ‘MSG’ signal must be treated before the ‘OUT’ one UI Request Data includes the following parameters:
  • Message Identifier
  • Status
  • Hold Time
  • Language Preference
  • OUT: A TLV coded constructed data element (tag ‘E4’), which contains:
  • The Kernel Outcome. This data item corresponds to the tag ‘Outcome Parameter Set’ (8 bytes long) defined in [Book C-2] and must follow the same format. It includes the following parameters: § Outcome Status (i.e. ‘3’ for ONLINE REQUEST) § Start value (i.e. ‘1’ for B) § Online Response Data (i.e. ‘F’ for N/A) § CVM value (i.e. ‘0’ for NO CVM) § UI Request on Outcome Present (i.e. 0b for not present) § UI Request on Restart Present (i.e. 1b for present) § Data Record Present (i.e. 0b for not present) § Discretionary Data Present (i.e. 0b for not present) § Receipt value (i.e. 0b for N/A) § Alternate Interface Preference value (i.e. ‘F’ for N/A) § Field Off Request value (i.e. ‘FF’ for N/A) § Removal Timeout value (i.e. ‘64’ for 20 seconds) EMV® Terminal Type Approval Entry Point Test Cases v2.11d
  • User Interface Request Data: see further details above.
  • Data Record. A TLV coded constructed data element (tag ‘FF8105’), which contains the transaction record for clearing. This field contains part or all of the data record elements defined in [Book C-2].
  • Discretionary Data: A TLV coded constructed data element (tag ‘FF8106’), which contains Kernel-specific data objects. This field contains part or all of the Discretionary Data elements defined in [Book C-2].

7.1.4.3 Template response (C-8 kernel) When the test kernel emulates C-8 (i.e. Kernel ID=‘08’), the Get Processing Options response follows the rules below. Tag Value Presence ‘77’ Response Message Template Format 2 Mandatory ‘9F8205 User Interface Request Data (corresponds to the MSG signal) Optional ‘E4’ OUT Mandatory ‘9F8210 Outcome Parameter Set Mandatory ‘9F8205 User Interface Request Data Optional ‘BF8102 Data Record Optional ‘BF8103 Discretionary Data Optional Table 7.1.4.2: GPO response format for Test Kernel emulating C-8 The Template response is a TLV (Tag ‘77’) constructed data element formatted as follow. The test kernel may then pass the listed data elements to the Entry Point.

  • UI Request Data: A TLV coded data element (tag ‘9F8105’), which contains the UI Request Data. This data item corresponds to the tag ‘User Interface Request Data’ (13 bytes long) defined in [Book C-8] and must follow the same format. It can either be returned:
  • Out of the ‘E4’ template tag, in which case it corresponds to the MSG signal
  • Within the ‘E4’ template tag EMV® Terminal Type Approval Entry Point Test Cases v2.11d
  • In both positions, in which case the ‘MSG’ signal must be treated before the ‘OUT’ one UI Request Data includes the following parameters:
  • Message Identifier
  • Status
  • Hold Time
  • Language Preference
  • Value Qualifier
  • Value
  • Currency Code
  • OUT: A TLV coded constructed data element (tag ‘E4’), which contains:
  • The Kernel Outcome. This data item corresponds to the tag ‘Outcome Parameter Set’ (8 bytes long) defined in [Book C-8] and must follow the same format. It includes the following parameters: § Outcome Status (i.e. ‘3’ for ONLINE REQUEST) § Start value (i.e. ‘1’ for B) § Online Response Data (i.e. ‘F’ for N/A) § CVM value (i.e. ‘0’ for NO CVM) § UI Request on Outcome Present (i.e. 0b for not present) § UI Request on Restart Present (i.e. 1b for present) § Data Record Present (i.e. 0b for not present) § Discretionary Data Present (i.e. 0b for not present) § Receipt value (i.e. 0b for N/A) § Alternate Interface Preference value (i.e. ‘F’ for N/A) § Field Off Request value (i.e. ‘FF’ for N/A) § Removal Timeout value (i.e. ‘64’ for 20 seconds)
  • User Interface Request Data: see further details above.
  • Data Record. A TLV coded constructed data element (tag ‘BF8102’), which contains the transaction record for clearing. This field contains part or all of the data record elements defined in [Book C-8]. EMV® Terminal Type Approval Entry Point Test Cases v2.11d
  • Discretionary Data: A TLV coded constructed data element (tag ‘BF8103’), which contains Kernel-specific data objects. This field contains part or all of the Discretionary Data elements defined in or [Book C-8].

7.1.4.4 No response to the GPO command The GPO response from LT may be empty (for time out testing purpose). Also For each LT (Card) data configuration, two GPO responses may be specified per AID present in the card.

  • A response when Restart = 0
  • A response when Restart = 1 EMV® Terminal Type Approval Entry Point Test Cases v2.11d 7.3. Reference LT (Card) test setti

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