EMV® Terminal Type Approval - Contactless Product - Testing Environment Requirements

© 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV ® Terminal Type Approval Contactless Product Testing Environment Requirements Version 2.11d June 2026 EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 2 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. 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 Testing Environment Requirements v2.11d Page 3 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. for any party's infringement of any intellectual property rights in connection with this document. EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 4 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Version History Version Date Revision Description 2.11d • First Version Versioning policy of the present document: The document version is based on the current Entry Point Specification revision number (e.g. 2.11) to which an additional letter is appended and incremented to track any revision of the document issued to correct any issues or to incorporate Type Approval Bulletins. EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 5 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Table of Contents 1. SCOPE ......................................................................................................................................................... 7 2. REFERENCE DOCUMENTS ................................................................................................................... 8 3. ABBREVIATIONS AND NOTATIONS ................................................................................................ 10 4. GLOBAL GLOSSARY ............................................................................................................................ 11 5. DOCUMENT OVERVIEW ..................................................................................................................... 12 6. TEST KERNEL REQUIREMENTS ...................................................................................................... 13 6.1. GENERAL REQUIREMENTS ........................................................................................................................ 13 6.2 EP DATA RECORDING ................................................................................................................................. 15 6.3 TEST DATA REPORTING .............................................................................................................................. 17 6.4 TEST KERNEL PROCESS .............................................................................................................................. 20 6.5 TEST KERNEL ID DEFINITION .................................................................................................................... 22 7. TEST PAYMENT APPLICATION ........................................................................................................ 23 8. TERMINAL DATA CONFIGURATIONS (‘TERMSETTING’) ........................................................ 24 8.1 TERMINAL DATA CONFIGURATIONS WITH KERNEL C-X NOT PRESENT ..................................................... 25 Terminal setting 1 [Termsetting1] ............................................................................................................. 26 Terminal setting 2 [Termsetting2] ............................................................................................................. 28 Terminal setting 3 [Termsetting3] ............................................................................................................. 31 Terminal setting 4 [Termsetting4] ............................................................................................................. 35 Terminal setting 5.x [Termsetting5.x] ........................................................................................................ 37 Terminal setting 6 [Termsetting6] ............................................................................................................. 41 Terminal setting 7 [Termsetting7] ............................................................................................................. 44 Terminal setting 8 [Termsetting8] ............................................................................................................. 45 Terminal setting 13 [Termsetting13] ......................................................................................................... 47 Terminal setting 14 [Termsetting14] ......................................................................................................... 49 Terminal setting 15 [Termsetting15] ......................................................................................................... 50 Terminal setting 16 [Termsetting16] ......................................................................................................... 51 Terminal setting 17 [Termsetting17] ......................................................................................................... 52 Terminal setting 18 [Termsetting18] ......................................................................................................... 54 Terminal setting 19.x [Termsetting19.x] .................................................................................................... 55 Terminal setting 20 [Termsetting20] ......................................................................................................... 57 Terminal setting 21 [Termsetting21] ......................................................................................................... 59 Terminal setting 22 [Termsetting22] ......................................................................................................... 60 Terminal setting 23 [Termsetting23] ......................................................................................................... 61 Terminal setting 24 [Termsetting24] ......................................................................................................... 62 Terminal setting 25 [Termsetting25] ......................................................................................................... 63 Terminal setting 27 [Termsetting27] ......................................................................................................... 64 Terminal setting 29 [Termsetting29] ......................................................................................................... 65 Terminal setting 30 [Termsetting30] ......................................................................................................... 66 9.2. CONFIGURATIONS WHEN KERNEL(S) C-N SHALL BE PRESENT .................................................................. 67 TERMINAL SETTING 9 [TERMSETTING9] .......................................................................................................... 67 Terminal setting 10 [Termsetting10] ......................................................................................................... 68 Terminal setting 11 [Termsetting11] ......................................................................................................... 75 Terminal setting 31 [Termsetting31] ......................................................................................................... 76 Terminal setting 32 [Termsetting32] ......................................................................................................... 79 EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 6 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Terminal setting 33 [Termsetting33] ......................................................................................................... 80 9.3 CONFIGURATIONS FOR C-8 IN STANDALONE ............................................................................................. 81 Terminal setting 26 [Termsetting26] ......................................................................................................... 82 EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 7 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. 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 – Testing Environment Requirements’ describes the requirements for the terminal to be submitted to Type Approval testing: • Entry Point Testing • System Testing The intended audiences for this document are EMVCo recognised laboratories, Entry Point and Contactless application Providers, acquirersor merchants. Although acquirers and merchants may reference this document, type approval testing oriented toward Entry Point and Contactless application providers. EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 8 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. 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 [ICS] EMVCo Type Approval Contactless Product - Implementation Conformance Statement 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 ([TA RRP]) • Module Integration Testing ([TA MIT]) • Book A General Requirements Testing ([TA BAGR]) Latest version available [TA Admin] EMVCo Type Approval Contactless Product – Administrative Process Latest version available EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 9 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. [TA EP] EMVCo Type Approval Contactless Product - Entry Point Test Plan Latest version available EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 10 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. 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 Testing Environment Requirements v2.11d Page 11 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. 4. Global Glossary Entry Point Module - the Software Module used to select the Kernel according to [Book A] & [Book B]. 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 Kernel C-n: the kernel complies with one of the [Book C-n] specifications (so EMVCo Kernel C-n only). By default a ‘kernel’ refers to a ‘Payment System Kernel’. • a Test Kernel: a software module acting as a kernel 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. 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 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 Testing Environment Requirements v2.11d Page 12 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. 5. Document Overview The document is organized in the following sections: o Section 6 specifies the Test Kernel requirements, o Section 7 specifies the Test Payment Application requirements, o Section 8 specifies the Terminal Data Configuration depending on the presence of the Kernel(s) C-2 to C-8 and used for Entry Point or System testing. EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 13 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. 6. Test Kernel Requirements This section describes the functional requirements of the Test Kernels ‘TK’ to be loaded in a device in order to perform the Entry Point testing or the System testing. 6.1. General requirements These Test Kernels must be provided by the device vendors and must be capable of meeting the minimum functionality described below: ¨ A Minimum of 7 Test Kernels must be present in the Product under Test. ¨ Each of these Test Kernel shall be able to have different Kernel ID ¨ Kernel ID of each Test Kernel must be configurable according to the Termsetting defined in the present document ¨ The Test Kernel shall be able to record and present all flags and data elements listed in the [Book A] and [Book B] specifications. ¨ The Test Kernel shall be use the PDOL and build a GPO command accordingly using Test Kernel or Entry Point data to report those data to the LT. ¨ The Test Kernel shall be restart after online processing ¨ The Test Kernel shall be able to provide the outcome to Entry Point including: l The Outcome parameter l The Associated Data form the Kernel: ² The User Interface Request Data (if any in LTsetting) ² The Data Record (if any in LT setting), ² The Discretionary Data (if any in LTsetting) The below figure shows the Test Kernel in the POS System environment: EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 14 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Prepare Outcome and UI request LT GPO Test Kernel: - Send GPO to LT according to PDOL - Receive data for Outcome and UI Response Data EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 15 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. 6.2 EP data recording The Test Kernel must be capable of reflecting the result of the pre-processing and kernel activation process by the Entry Point application. This means that the activated Test Kernel shall record and output when requested, the following data: • Entry Point Pre-Processing Indicators, • Amount Authorised, • Unpredictable Number • Restart flag For the purpose of verifying data listed above, the Test Kernel shall support a proprietary Tag ‘D1’, called ‘Test flags’ in the test environment and capable of mapping above listed data onto Tag ‘D1’ according to the bit setting in Table 1. The Test Flags data element has the following format: b8 B7 b6 b5 b4 b3 b2 b1 Meaning 0 Reader Contactless Floor Limit Not Exceeded 1 Reader Contactless Floor Limit Exceeded RFU 0 Reader CVM Required Limit Not Exceeded 1 Reader CVM Required Limit Exceeded 0 Status Check Not Requested 1 Status Check Requested 0 Not Zero Amount 1 Zero Amount 0 Contactless Application Allowed 1 Contactless Application Not Allowed RFU Table 1: Tag ’D1’, Test Flags data format – Byte 1 EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 16 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. b8 B7 b6 b5 b4 B3 b2 b1 Meaning 0 Restart Flag is 0 1 Restart Flag is 1 RFU Table 2: Tag ‘D1’, Test Flags data format – Byte 2 Where: • Terminal Contactless Floor Limit exceeded or not: the bit 8 reflects the setting of the Entry Point Pre-Processing Indicator ‘Reader Contactless Floor Limit Exceeded’ of the Entry Point Software as described in [Book B]. • Terminal CVM Required Limit exceeded or not: the bit 6 reflects the setting of the Entry Point Pre-Processing Indicator ‘Reader CVM Required Limit Exceeded’ of the Entry Point Software as described in [Book B]. • Status Check requested or not: the bit 5 reflects the setting of the Entry Point Pre- Processing Indicator ‘Status Check Requested’ of the Entry Point Software as described in [Book B]. • Zero Amount or not Zero Amount: the bit 4 reflects the setting of the Entry Point Pre-Processing Indicator ‘Zero Amount’ of the Entry Point Software as described in [Book B]. • Contactless Application not Allowed the bit 3 reflects the setting of the Entry Point Pre-Processing Indicator ‘Contactless Application Not Allowed’ of the Entry Point Software as described in [Book B]. • Restart Flag reflects the setting of the ‘restart flag’ EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 17 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. 6.3 Test data reporting Upon Test Kernel activation by Entry Point, the selected Test Kernel must be able to provide all Entry Point and Test Kernel data required for testing purpose in the data field of the Get Processing Option Command. The Get Processing Option Command of the Test Kernels shall be coded as follows Code Value CLA ‘80’ INS ‘A8’ P1 ‘00’ P2 ‘00’ Lc Var. Data PDOL Related Data Le ‘00’ Table 3: Get Processing Command Format for the Test Kernels EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 18 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Data field in the command message: The data field of the command message is a data object coded according to the PDOL provided by the LT (Card), as defined in EMV section 5.4, and is introduced by the tag '83'. The minimum data to be supported in PDOL are the following: Data Object Tag Length Source Comment Test flags D1 2 Test Kernel Includes Pre-Processing flags and Restart flag TTQ 9F66 4 Entry Point When data not present, to be filled with zeroes Kernel Identifier_Termi nal 96 var Entry Point Kernel ID is of variable size and may be one, three, or more bytes (until 8) in length Amount Authorised 9F02 6 POS System Amount Other 9F03 6 POS System Transaction Type 9C 1 POS System UN 9F37 4 POS System Start Point D2 1 Entry Point 1st Outcome where Entry Point Started (‘0A’, ‘0B’, ‘0C’ or ‘0D’) FCI 6F var Entry Point FCI of the selected AID Select Response Status Word D3 2 Entry Point SW of the Select Response command of the selected AID Issuer Authentication Data 91 Var POS System present if previous transaction required a restart Issuer Script 71 71 var POS System present if previous transaction required a restart Issuer Script 72 72 var POS System present if previous transaction required a restart EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 19 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Data field in the response message: See Entry Point Test Plan Section 7.1.4. EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 20 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. 6.4 Test Kernel process This section specifies the Terminal Test Kernel process. 1. The Test Kernel is activated according to [Book B], section kernel activation. 2. The Test Kernel shall get the FCI Select Response, the Status Word, and also all Entry Point data at activation, and shall record these data. 3. The Test Kernel shall generate a GPO command using the PDOL retrieved in FCI (if present) and send the command to the LT according to the PDOL setting. The data objects supported in PDOL are defined in section 6.3. 4. The Test Kernel waits for the LT (card) response which can answer one of the following responses: o Case 1: the card response specifies an Outcome without any User Interface Request o Case 2: the card response specifies an Outcome with a User Interface Request (on Outcome) o Case 3: the card response specifies an Outcome with a User Interface Request (on Restart) o Case 4: the card response specifies an Outcome with a User Interface Request on Outcome and a User Interface Request on Restart o Case 5: no card response, or no outcome or wrong response format 4.1. When a User Interface Request on Outcome is present, the following parameters specific to User Interface Request on Outcome are present: o Message Identifier o Status o Hold Time (integer multiple of 100ms) o Language Preference (as per EMV tag '5F2D' according to ISO 639) o Value Qualifier o Value o Currency Code (numeric value as per ISO 4217). 4.2. When a User Interface Request on Restart is present, the same parameters as for User Interface Request on Outcome are present: 4.3. When an Outcome is present, the following parameters specific to Outcome are present: o Start EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 21 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. o Online Response Data o CVM o UI Request on Outcome o UI Request on Restart o Data Record Present o Discretionary Data Present o Alternate Interface Preference o Receipt o Field Off Request o Removal Timeout The Test Kernel shall send this Outcome with User Interface Request on Restart (if present) to Entry Point. 4.4. When the Test Kernel emulates a C-2 or C-8 Kernel, the LT provides the constructed tag ‘E4’ that includes the Outcome Parameter Set, User Interface Request Data (if any), Data Record (if any) and Discretionary Data (if any) in the correct TLV format compliant with the respective kernel specification (see further details about the GPO response in [TA EP]). The test kernel must pass those items to the Entry Point without any format modification. 4.5. When no card response, or no outcome or wrong response format, the Terminal Test kernel closes the session. 5. If ‘Start’ Parameter is set to ‘NA’, the Test Kernel stops it process. If ‘Start’ Parameter is set to ‘A’, ‘B’, ‘C’, the Test Kernel shall wait for a new activation from the Entry Point (with the Select AID response) and go to Step 2 If ‘Start’ Parameter is set to ‘D’, the Test Kernel shall wait for a new activation from the Entry Point (start ‘D’) with online response and shall generate a GPO command using the PDOL retrieved in FCI (if present) and send the command to the card and go to Step 4. Note: The Test Kernel software receives from Entry Point Module, all EP data. The way these data are transmitted from Entry Point Module to the selected Contactless Kernel is not defined in the Book A & B Specifications. However for testing purpose these data transmitted to the selected Test Kernel, must be transmitted by the Entry Point Module in the same way and using the same format as for a Kernel C-n. EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 22 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. 6.5 Test Kernel ID definition The Test Kernel uses the Kernel ID values ‘02’, ‘03’, ‘04’, ‘05’, ‘06’, ‘07’ or ‘08’ with the following correspondences: o TK2 = ‘02’ o TK3 = ‘03’ o TK4 = ‘04’ o TK5 = ‘05’ o TK6 = ‘06’ o TK7 = ‘07’ o TK8 = ‘08’ EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 23 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. 7. Test Payment Application For testing purpose, the Test (or real) payment application loaded in the POS system at the time of testing shall: • Perform functionality of the Test Kernels present in the Product under Test with the associated kernel ID and AIDs. • Output the Final Outcome with: ² The Outcome parameter ² The Associated Data from the Kernel: l The User Interface Request Data (if any in LTsetting) l The Data Record (if any in LTsetting), l The Discretionary Data (if any in LTsetting) ² The ADF Name selected ² The Kernel Identifier - Terminal • Output the various message occuring during the transaction like for instance Message Identifier ‘14’ (Welcome). This output could be done via display, file output, etc. • Provide the Output of the Entry Point Module to the Test Tool. EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 24 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. 8. Terminal Data Configurations (‘Termsetting’) Several terminal data configurations are needed to test Entry Point or the System. These data configurations are used in the Test Cases for Entry Point Module testing, for Contactless System testing which includes Module Integration testing, Performance, System testing and RRP testing. These Terminal data configurations are referenced as [TermsettingX], where X reflects one of the Terminal Setting below. EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 25 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. 8.1 Terminal Data Configurations with Kernel C-x not present The below Termsettings are used for Entry Point Module testing. Whatever the Contactless Product submitted supports Kernel C-n, the below Termsettings require that the Kernels C-n are not present in those configurations during testing. • Terminal setting 1 [Termsetting1] • Terminal setting 2 [Termsetting2] • Terminal setting 3 [Termsetting3] (needed only if Autorun is supported) • Terminal setting 4 [Termsetting4] • Terminal setting 5.x [Termsetting5.x] (needed only if Autorun is supported) • Terminal setting 6 [Termsetting6] • Terminal setting 7 [Termsetting7] (needed only if Autorun is supported) • Terminal setting 8 [Termsetting8] • Terminal setting 13 [Termsetting13] (needed only if Autorun is supported) • Terminal setting 14 [Termsetting14] (needed only if POI Info is supported) • Terminal setting 15 [Termsetting15] (needed only if POI Info is supported) • Terminal setting 16 [Termsetting16] (needed only if Autorun is supported) • Terminal setting 17 [Termsetting17] • Terminal setting 18 [Termsetting18] (needed only if Autorun is supported) • Terminal setting 19.x [Termsetting19.x] (needed only if Autorun is supported) • Terminal setting 20 [Termsetting20] (needed only if Autorun is supported) • Terminal setting 21 [Termsetting21] • Terminal setting 22 [Termsetting22] • Terminal setting 23 [Termsetting 23] (needed only if POI Info is supported) • Terminal setting 24 [Termsetting24] (needed only if POI Info AND Autorun are supported) • Terminal setting 25 [Termsetting25] (needed only if POI Info AND Autorun are supported) • Terminal setting 27 [Termsetting27] EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 26 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Terminal setting 1 [Termsetting1] o Covers the Kernel ID coding (international/domestic kernel). o International and Domestic AID. o All Pre-Processing features activated (pre-processing parameter with the same value for all combinations not depending on the Transaction Type). o If the Terminal Configuration 'Contact' is supported, a 'contact software' must be provided in order to start a transaction (such as Application Selection Process) or to run a full EMV transaction with an EMV Contact Application Kernel (approved or not). Details on [Termsetting1] • Kernel ID o International kernel ID: TK2, TK3, TK4, TK5, TK6, TK7, TK8, 21, 22, 23, 24, 25, 32 associated to 10 Test Kernel instances. o Domestic kernel ID (EMVCo format): 810978, BF0840 associated to 2 Test Kernel instances o Domestic kernel ID (proprietary format): C11111, FF2222 associated to 2 Test Kernel instances • The following AID (A000000010001, A000000020002, A000000030003, A000000040004, A0000001523010, A0000000031010, A0000000041010, A0000000043060, A0000000046000, A0000000651010, A0000000251010, B0000000010101) are combined to each above Test Kernel instances and all type of transaction supported • All preprocessing feature activated (including same values) in all Test Kernel instances. • Autorun Parameter: ‘No’ (when Autorun is supported) Kernel ID AID TK2 TK3 TK4 TK5 TK 6 TK 7 TK 8 21 22 23 24 25 32 8109 78 BF08 40 C111 11 FF22 22 A0000000010001 x x x x x x x x A0000000020002 x x x x x x x x x x A0000000030003 x x x x x x x x x x x A0000000040004 x x x x x x x x x x EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 27 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. A0000000031010 x x A0000000041010 x x x x A0000000043060 x x x x A0000000046000 x x x x A0000000651010 x x x x x A0000000251010 x x x x A0000001523010 x x A0000003330101 x x A0000003241010 x x B0000000010101 x x x x x x x x x x Table 4: Kernel ID/AID combination for [Termsetting1] Status Check Support flag 1 Zero Amount Allowed flag 1 Zero Amount for Offline Allowed flag - Reader Contactless Transaction Limit 120 Reader Contactless Floor Limit 12 Terminal Floor Limit - Reader CVM Required Limit 15 TTQ ‘B6208000’ Extended Selection Support flag 1 Table 5: Entry Point data for [Termsetting1] ‘-‘ means that the data object is not present. TTQ: Mag-stripe mode supported, EMV mode supported, EMV contact chip supported, Online capable reader, Online PIN supported, Signature supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN supported, Issuer Update Processing supported. EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 28 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Terminal setting 2 [Termsetting2] o 13 kernel IDs and 29 combinations available independent from the Transaction Type. o Pre-Processing parameters specific to each combination. Details on [Termsetting2] • Autorun Parameter: ‘No’ (when Autorun is supported) • Kernel ID/AID Kernel ID AID TK2 TK3 TK4 TK5 TK6 TK7 21 22 23 24 25 2B A0000000010001 x x x x A0000000020002 x x x A0000000030003 x x x A0000000040004 x x x x A0000000031010 x x A0000000041010 x x x A0000000651010 x x A0000000251010 x x x x A0000001523010 x A0000003330101 X A0000003241010 x Table 6: Kernel ID/AID combinations for [Termsetting2] EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 29 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. • Entry Point Configuration (not depending on the Transaction Type) Combination AID/kernel A00000000 30003/21 A00000000 41010/TK2 A00000000 20002/22 A00000000 41010/2B A00000000 20002/2B A000000 0031010/ TK3 A000000 0010001/ 23 A000000 0031010/ 2B A000000 0010001/ 2B A00000002 51010/TK4 A00000006 51010/TK5 A00000000 40004/24 A00000000 30003/25 A000000 0041010/ TK4 A000000 0020002/ 24 A00000000 10001/21 A00000006 51010/TK2 A00000002 51010/TK5 A00000000 30003/22 A00000000 40004/25 A000000 0251010/ TK3 A000000 0040004/ 23 A000000 0251010/ 2B A000000 0040004/ 2B A000000 1523010/ TK6 A000000 3330101/ TK7 A000000 3241010/ TK6 A000000 0010001/ 25 Status Check Support flag - 0 1 - - 0 1 1 0 - Zero Amount Allowed flag 1 - 0 0 1 - 1 1 - 0 Zero Amount for Offline Allowed flag 0 - 0 - 1 1 0 0 0 1 Reader Contactless Transaction Limit 120 - 200 - - - 200 - 120 - Reader Contactless Floor Limit 20 - - 50 20 - - 50 - 20 Terminal Floor Limit - - 25 - - - 25 - - - Reader CVM Required Limit - 10 - 20 - 10 - 20 10 - TTQ ‘840080FF’ (1) - ‘28000F0 0’(2) ‘C4008000’ (3) ‘8400800 0’ (1) - ‘28000000’( 2) - - ‘8400800 0’ (1) Extended Selection Support flag 1 - 0 1 1 0 - 1 0 1 Table 7: Entry Point data for [Termsetting2] ‘-‘ means that the data object is not present. EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 30 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. (1) TTQ value ‘840080FF’: Mag-stripe mode supported, EMV mode not supported, EMV contact chip not supported, Online capable reader, Online PIN supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing supported. Byte 4 RFU Bits set to 1 (2) TTQ value ‘28000F00’: Mag-stripe mode not supported, EMV mode supported, EMV contact chip not supported, Offline-only reader, Online PIN not supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing not supported, Byte 3 RFU Bits set to 1, (3)TTQ value ‘C4008000’: Mag-stripe mode supported, EMV mode not supported, EMV contact chip not supported, Online capable reader, Online PIN supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing supported, Byte 1 RFU Bits set to 1. EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 31 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Terminal setting 3 [Termsetting3] o This Terminal setting is requested only when Autorun Parameter is supported. o Pre-Processing data not present o Pre-Processing Indicators have no fixed values. o TTQ is present with fixed values. o If the Terminal Configuration 'Contact' is supported, a 'contact software' must be provided in order to start a transaction (such as Application Selection Process) or to run a full EMV transaction with an EMV Contact Application Kernel (approved or not). Details on [Termsetting3] • Autorun Parameter: ‘Yes’ • Defined Autorun Amount Authorised = 10 • Defined Autorun Amount, Other = 20 • Autorun parameters according to ICS: o Transaction Type • Kernel ID/AID Kernel ID AID TK2 TK3 TK4 TK5 TK6 TK7 TK8 21 22 23 24 25 2B A0000000010001 x x x x A0000000020002 x x x x A0000000030003 x x x x A0000000040004 x x x x x A0000000031010 x x x A0000000041010 x x x x A0000000651010 x x x A0000000251010 x x x x x A0000001532010 X x X A0000003330101 x x X EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 32 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Table 8: Kernel ID/AID combination for [Termsetting3] EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 33 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. • Entry Point Configuration data Combination AID/kernel A0000000 030003/21 A000000 0041010/ TK2 A000000 0020002/ 22 A000000 0041010/ 2BA0000 0000200 02/2B A00000000 31010/TK3 A00000000 10001/23 A00000000 31010/2B A00000000 10001/2B A00000002 51010/TK4 A00000006 51010/TK5 A00000000 40004/24 A00000000 30003/25 A00000000 41010/TK4 A00000000 20002/24 A00000000 10001/21 A00000006 51010/TK2 A00000002 51010/TK5 A00000000 30003/22 A00000000 40004/25 A00000002 51010/TK3 A00000000 40004/23 A00000002 51010/2B A00000000 40004/2B A00000015 32010/TK6 A00000033 30101/TK7 Status Check Support flag - - - - - - - - - Zero Amount Allowed flag - - - - - - - - - Zero Amount for Offline Allowed flag - - - - - - - - - Reader Contactless Transaction Limit - - - - - - - - - Reader Contactless Floor Limit - - - - - - - - - Terminal Floor Limit - - - - - - - - - Reader CVM Required Limit - - - - - - - - - TTQ ‘84008000’ (1) - ‘28000000’( 2) ‘84008000’ (1) ‘84008000’ (1) - ‘28000000’( 2) - - Extended Selection Support flag 1 - 0 1 1 0 - 1 0 Table 9: Entry Point data for [Termsetting3] ‘-‘ means that the data object is not present. (1) TTQ value ‘84008000’: Mag-stripe mode supported, EMV mode not supported, EMV contact chip not supported, Online capable reader, Online PIN supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing supported EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 34 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. (2) TTQ value ‘28000000’: Mag-stripe mode not supported, EMV mode supported, EMV contact chip not supported, Offline-only reader, Online PIN not supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing not supported EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 35 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Terminal setting 4 [Termsetting4] o 5 kernels ID and international AIDs and 11 combinations available depending on the Transaction Type. o Pre-Processing parameters specific to each combination. Details on [Termsetting4] • Autorun Parameter: ‘No’ (when Autorun is supported) • 5 kernels with different AID configurations depending on transaction type supported: o Purchase o Purchase with Cashback o Cash Advance o Refund Kernel ID Type of Transaction 21 22 23 24 25 Purchase A0000000030003 A0000000020002 A0000000010001 A0000000040004 A0000000030003 Purchase with Cashback A0000000030003 Cash Advance A0000000010001 A0000000030003 Refund A0000000030003 A0000000020002 A0000000040004 Table 10: Combinations for [Termsetting4] EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 36 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. • Entry Point Configuration Combination AID/kernel/ type of transaction A0000000 030003/21 Purchase A000000 0020002/ 22 A000000 0030003/ 25 Purchas e A000000 0010001/ 23 Purchas e A000000 0040004/ 24 Purchas e A000000 0020002/ 22 Refund A00000000 10001/23 A00000000 30003/25 Cash Advance A000000 0030003/ 21 Purchas e with Cashbac k A000000 0040004/ 24 Refund A000000 0030003/ 21 Refund Status Check Support flag - 0 1 0 - 0 1 1 - Zero Amount Allowed flag 1 - 0 0 1 - 1 1 - Zero Amount for Offline Allowed flag 0 - 0 - 0 0 1 - - Reader Contactless Transaction Limit - - 200 120 120 - 200 - - Reader Contactless Floor Limit 20 - - - 20 - - 50 50 Terminal Floor Limit - - 25 - - - 25 - - Reader CVM Required Limit - 10 - 20 - 10 - 20 - TTQ ‘84008000’ (1) - ‘2800000 0’(2) ‘8400800 0’ (1) ‘8400800 0’ (1) - ‘2800000 0’(2) - ‘8400800 0’ (1) Extended Selection Support flag 1 - 0 1 1 0 - 1 1 Table 11: Entry Point data for [Termsetting4] ‘-‘ means that the data object is not present. (1) TTQ value ‘84008000’: Mag-stripe mode supported, EMV mode not supported, EMV contact chip not supported, Online capable reader, Online PIN supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing supported (2) TTQ value ‘28000000’: Mag-stripe mode not supported, EMV mode supported, EMV contact chip not supported, Offline-only reader, Online PIN not supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing not supported. EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 37 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Terminal setting 5.x [Termsetting5.x] o This Terminal setting is requested only when Autorun Parameter is supported. o Same combination Kernel ID/AID as [Termsetting4]. o Pre-Processing not activated. o Pre-Processing Indicators have no fixed values. o Copy of TTQ has the same value as TTQ in TermSetting4. Details on [Termsetting5.x] • Autorun Parameter: ‘Yes’ • Defined Autorun Amount Authorised = 10 • Defined Autorun Amount, Other = 20 • Autorun parameters according to ICS: o Transaction Type: § Purchase: [Termsetting5.1] § Purchase with Cashback: [Termsetting5.2] § Cash Advance: [Termsetting5.3] § Refund: [Termsetting5.4] • 5 kernels with different AID configurations depending on transaction type supported: Kernel ID Type of Transaction 21 22 23 24 25 Purchase A0000000030003 A0000000020002 A0000000010001 A0000000040004 A0000000030003 Purchase with Cashback A0000000030003 Cash Advance A0000000010001 A0000000030003 Refund A0000000030003 A0000000020002 A0000000040004 Table 12: Combinations for [Termsetting5.x] EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 38 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 39 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. • Entry Point Configuration Combination AID/kernel/ type of transaction A0000000 030003/21 Purchase A000000 0020002/ 22 A000000 0030003/ 25 Purchas e A000000 0010001/ 23 Purchas e A000000 0040004/ 24 Purchas e A000000 0020002/ 22 Refund A00000000 10001/23 A00000000 30003/25 Cash Advance A000000 0030003/ 21 Purchas e with Cashbac k A000000 0040004/ 24 Refund A000000 0030003/ 21 Refund Status Check Support flag - - - - - - - - - Zero Amount Allowed flag - - - - - - - - - Zero Amount for Offline Allowed flag - - - - - - - - - Reader Contactless Transaction Limit - - - - - - - - - Reader Contactless Floor Limit - - - - - - - - - Terminal Floor Limit - - - - - - - - - Reader CVM Required Limit - - - - - - - - - TTQ ‘84008000’ (1) - ‘2800000 0’(2) ‘8400800 0’ (1) ‘8400800 0’ (1) - ‘2800000 0’(2) - ‘8400800 0’ (1) Extended Selection Support flag 1 - 0 1 1 0 - 1 1 Table 13: Entry Point data for [Termsetting5.x] ‘-‘ means that the data object is not present. (1) TTQ value ‘84008000’: Mag-stripe mode supported, EMV mode not supported, EMV contact chip not supported, Online capable reader, Online PIN supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing supported EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 40 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. (2) TTQ value ‘28000000’: Mag-stripe mode not supported, EMV mode supported, EMV contact chip not supported, Offline-only reader, Online PIN not supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing not supported EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 41 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Terminal setting 6 [Termsetting6] o Same as [Termsetting2] but Test Kernel ID 1 is not supported and less AIDs. Details on [Termsetting6] • Autorun Parameter: ‘No’ (if supported). • Kernel ID/AID Kernel ID AID TK2 TK3 TK4 TK5 2B A0000000031010 x x A0000000041010 x x x A0000000651010 x x A0000000251010 x x x x Table 14: Kernel ID/AID combinations for [Termsetting6] EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 42 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. • Entry Point Configuration (not depending on the Transaction Type) Combination AID/kernel A000000 0041010/ TK2 A000000 0041010/ 2B A00000000 31010/TK3 A00000000 31010/2B A00000002 51010/TK4 A00000006 51010/TK5 A00000000 41010/TK4 A00000006 51010/TK2 A00000002 51010/TK5 A00000002 51010/TK3 A00000002 51010/2B Status Check Support flag 0 1 - - 1 1 0 Zero Amount Allowed flag - 0 0 1 1 1 - Zero Amount for Offline Allowed flag - 0 - 1 0 0 0 Reader Contactless Transaction Limit - 200 - 120 200 - - Reader Contactless Floor Limit - - 50 20 - 50 100 Terminal Floor Limit - 25 - - 25 - - Reader CVM Required Limit 10 - 20 - - 20 10 TTQ - ‘28000000’( 2) ‘84008000’ (1) ‘84008000’ (1) ‘28000000’( 2) - - Extended Selection Support flag - 0 1 1 - 1 0 Table 15: Entry Point data for [Termsetting6] ‘-‘ means that the data object is not present. (1) TTQ value ‘84008000’: Mag-stripe mode supported, EMV mode not supported, EMV contact chip not supported, Online capable reader, Online PIN supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing supported (2) TTQ value ‘28000000’: Mag-stripe mode not supported, EMV mode supported, EMV contact chip not supported, Offline-only reader, Online PIN not supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing not supported EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 43 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 44 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Terminal setting 7 [Termsetting7] o This Terminal setting is requested only when Autorun Parameter is supported. o Same as [Termsetting3] but Test Kernel ID 1 is not supported and less AIDs. Details on [Termsetting7] • Autorun Parameter: ‘Yes’ • Defined Autorun Amount Authorised = 10 • Defined Autorun Amount, Other = 20 • Autorun parameters according to ICS: o Transaction Type • Kernel ID/AID Kernel ID AID TK2 TK3 TK4 TK5 2B A0000000031010 x x A0000000041010 x x x A0000000651010 x x A0000000251010 x x x x Table 16: Kernel ID/AID combination for [Termsetting7] Note that Pre-Processing is not activated, so the Pre-Processing parameters are not required. EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 45 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Terminal setting 8 [Termsetting8] o Same as [Termsetting1] but several TTQ RFU bits are set to 1. Details on [Termsetting8] • Autorun Parameter: ‘No’ (if supported) • Kernel ID o International kernel ID: 21, 22, 23, 24, 25, 32 associated to 6 Test Kernel instances. o Domestic kernel ID (EMVCo format): 810978, BF0840 associated to 2 Test Kernel instances o Domestic kernel ID (proprietary format): 811111, BF2222 associated to 2 Test Kernel instances. • The following AIDs (A0000000010001, A0000000020002, A0000000030003, A0000000040004, B0000000010101) are combined for each above Test Kernel instance and all type of transaction supported • All pre-processing feature activated (including same values) not depending on the Transaction Type. Kernel ID AID 21 22 23 24 25 32 810978 BF0840 811111 BF2222 A0000000010001 x x x x x x x A0000000020002 x x x x x x x x x A0000000030003 x x x x x x x x x x A0000000040004 x x x x x x x x X B0000000010101 x x x x x x x x x Table 17: Kernel ID/AID combination for [Termsetting8] EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 46 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Status Check Support flag 1 Zero Amount Allowed flag 1 Zero Amount for Offline Allowed flag 0 Reader Contactless Transaction Limit 120 Reader Contactless Floor Limit 12 Terminal Floor Limit - Reader CVM Required Limit 15 TTQ ‘F72A8A55’ (several RFU bits set) Extended Selection Support flag 1 Table 18: Entry Point data for [Termsetting8] ‘-‘ means that the data object is not present. TTQ: Mag-stripe mode supported, EMV mode supported, EMV contact chip supported, Online capable reader, Online PIN supported, Signature supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN supported, Issuer Update Processing supported EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 47 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Terminal setting 13 [Termsetting13] o This Terminal setting is requested only when Autorun Parameter is supported. o Same kernel IDs as [Termsetting1] but preprocessing is not supported (Autorun Parameter: ‘Yes’, if Autorun Option is supported), and each AID is associated to a single Kernel ID. Details on [Termsetting13] • Autorun Parameter: ‘Yes’ • Defined Autorun Amount Authorised = 10 • Defined Autorun Amount, Other = 20 • Kernel ID o International kernel ID: 21, 22, 23, 24, 25, 32 associated to 6 Test Kernel instances. o Domestic kernel ID (EMVCo format): 810978, BF0840 associated to 2 Test Kernel instances o Domestic kernel ID (proprietary format): C11111, FF2222 associated to 2 Test Kernel instances • The following AIDs (A0000000010001, A0000000020002, A0000000030003, A0000000040004, B0000000010101, B0000000010102, B0000000010103, B0000000010104, B0000000010105) are combined to one or two Test Kernel instances and all transaction types supported • No preprocessing feature activated in all Test Kernel instances. Kernel ID AID 21 22 23 24 25 32 TK8 810978 BF0840 C11111 F2222 A0000000010001 x x A0000000020002 x A0000000030003 x x A0000000040004 x B0000000010101 x EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 48 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. B0000000010102 x B0000000010103 x B0000000010104 x B0000000010105 x Table 19: Kernel ID/AID combinations for [Termsetting13] EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 49 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Terminal setting 14 [Termsetting14] o This Terminal setting is requested only when POI Information is supported. o Same kernel IDs as [Termsetting2] with POI Information added Details on [Termsetting14] Terminal Data used for Selection Data Object List (SDOL) are specified in the table below: Data object Tag Value Amount Authorised 9F02 Set by the test POI Information 8B see below Terminal Country Code 9F1A ‘0250’ Transaction Currency Code 5F2A ICS parameter Table 20: Terminal data used in SDOL for [Termsetting14] The POI Information Identifier are specified in the table below: ID Name Value Description ‘0001’ Terminal Category ‘0001’ Transit Gate ‘xxxx’ Other IDs shall be present if supported Table 21: POI Information [Termsetting14] EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 50 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Terminal setting 15 [Termsetting15] o This Terminal setting is requested only when POI Information is supported. o Same kernel IDs as [Termsetting2] with POI Information added. Details on [Termsetting15] Terminal Data used for Selection Data Object List (SDOL) are specified in the table below: Data object Tag Value Amount Authorised 9F02 Set by the test POI Information 8B See below Terminal Country Code 9F1A ‘0250’ Transaction Currency Code 5F2A ICS parameter Table 22: Terminal data used in SDOL for [Termsetting15] The POI Information Identifier are specified in the table below: ID Name Value Description ‘0001’ Terminal Category ‘0002’ Loyalty ‘xxxx’ Other IDs shall be present if supported Table 23: POI Information [Termsetting15] EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 51 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Terminal setting 16 [Termsetting16] o This Terminal setting is requested only when Autorun Parameter is supported. o Same settings as [Termsetting2]. o Autorun Parameter: ‘Yes’. o Defined Autorun Amount Authorised = 10 o Defined Autorun Amount, Other = 20 EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 52 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Terminal setting 17 [Termsetting17] o Same settings as [Termsetting3]. Details on [Termsetting17] • Autorun Parameter: ‘No’ (if supported). • Entry Point Configuration data: Combination AID/kernel A0000000 030003/21 Any AID/TK8 A000000 0041010/ TK2 A000000 0020002/ 22 A000000 0041010/ 2BA0000 0000200 02/2B A00000000 31010/TK3 A00000000 10001/23 A00000000 31010/2B A00000000 10001/2B A00000002 51010/TK4 A00000006 51010/TK5 A00000000 40004/24 A00000000 30003/25 A00000000 41010/TK4 A00000000 20002/24 A00000000 10001/21 A00000006 51010/TK2 A00000002 51010/TK5 A00000000 30003/22 A00000000 40004/25 A00000002 51010/TK3 A00000000 40004/23 A00000002 51010/2B A00000000 40004/2B A00000015 32010/TK6 A00000033 30101/TK7 Status Check Support flag - - - - - - - - - Zero Amount Allowed flag - - - - - - - - - Zero Amount for Offline Allowed flag - - - - - - - - - Reader Contactless Transaction Limit - - - - - - - - - Reader Contactless Floor Limit - - - - - - - - - Terminal Floor Limit - - - - - - - - - Reader CVM Required Limit - - - - - - - - - TTQ ‘84008000’ (1) - ‘28000000’( 2) ‘84008000’ (1) ‘84008000’ (1) - ‘28000000’( 2) - - Extended Selection Support flag 1 - 0 1 1 0 - 1 0 Table 24: Entry Point data for [Termsetting17] EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 53 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. ‘-‘ means that the data object is not present. (1) TTQ value ‘84008000’: Mag-stripe mode supported, EMV mode not supported, EMV contact chip not supported, Online capable reader, Online PIN supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing supported (2) TTQ value ‘28000000’: Mag-stripe mode not supported, EMV mode supported, EMV contact chip not supported, Offline-only reader, Online PIN not supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing not supported EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 54 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Terminal setting 18 [Termsetting18] o This Terminal setting is requested only when Autorun Parameter is supported. o Same settings as [Termsetting3]. o Pre-Processing indicators set to fixed- values o (TTQ value are the same as [Termsetting3]) excepted that TTQ byte 2 bit 8 (online required) is set to be synchronised with the Status Check requested indicator defined below). Details on [Termsetting18] o Autorun Parameter: ‘Yes’. o fixed values of Pre-Pprocessing Indicators: Status Check requested 1 Contactless Application Not Allowed 0 Zero Amount 0 Reader CVM Required Limit Exceeded 0 Reader Contactless Floor Limit Exceeded 0 Table 25: Fixed values of Pre-processing indicators for [Termsetting18] EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 55 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Terminal setting 19.x [Termsetting19.x] o This Terminal setting is requested only when Autorun Parameter is supported. o Same combination Kernel ID/AID as [Termsetting5.x]. o (TTQ value are the same as [Termsetting5.x]) except that TTQ byte 2 bit 8 (online required) is set to be synchronised with the Status Check requested indicator defined below). o Autorun Parameter: ‘Yes’. o Predefined Autorun Amount Authorised = 10 o Predefined Autorun Amount, Other = 20 Details on [Termsetting19.1] o Fixed values of Pre-Processing Indicators: Status Check requested 1 Contactless Application Not Allowed 0 Zero Amount 0 Reader CVM Required Limit Exceeded 0 Reader Contactless Floor Limit Exceeded 0 Table 26: Fixed values of Pre-Processing Indicatorsfor [Termsetting19.1] Details on [Termsetting19.2] o Fixed values of Pre-Processing Indicators: Status Check requested 1 Contactless Application Not Allowed 1 Zero Amount 0 Reader CVM Required Limit Exceeded 0 Reader Contactless Floor Limit Exceeded 0 Table 27: Fixed values of Pre-Processing Indicatorsfor [Termsetting19.2] EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 56 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Details on [Termsetting19.3] o Fixed values of Pre-Processing Indicators: Status Check requested 0 Contactless Application Not Allowed 0 Zero Amount 1 Reader CVM Required Limit Exceeded 0 Reader Contactless Floor Limit Exceeded 0 Table 28: Fixed values of Pre-Processing Indicatorsfor [Termsetting19.3] Details on [Termsetting19.4] o Fixed values of Pre-Processing Indicators: Status Check requested 0 Contactless Application Not Allowed 0 Zero Amount 0 Reader CVM Required Limit Exceeded 1 Reader Contactless Floor Limit Exceeded 0 Table 29: Fixed values of Pre-Processing Indicatorsfor [Termsetting19.4] EMV ® Terminal Type Approval Testing Environment Requirements v2.11d Page 57 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV ® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Terminal setting 20 [Termsetting20] o This Terminal setting is requested only when Autorun Parameter is supported. o Pre-Processing Indicators have fixed values. Details on [Termsetting20] o Autorun Parameter: ‘Yes’. o Predefined Autorun Amount Authorised = 10 o Predefined Autorun Amount, Other = 20 o Fixed values of Pre-Processing Indicators: Status Check requested 1 Contactless Application Not Allowed 0 Zero Amount 0 Reader CVM Required Limit Exceeded 0 Reader Cont