EMV® Terminal Type Approval - Contactless Product - Administrative Process

© 2011-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 __________________________________________________ Administrative Process Version 2.11d July 2026 EMV® Type Approval Terminal Contactless Product Administrative Process Legal Notice Page i / v © 2011-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 rel iance. 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 LIMITATI ON IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON - INFRINGEMENT, AS TO THIS DOCUMENT. EMVCo makes no representations or warranties with respect to intellectual property rights of any third parties in or in relation to this document. EMVCo undertakes no responsibility to determine whether any implementation of this document may violate, infringe, or otherwise exercise the patent, copyright, trademark, trade secret, know-how, or other intellectual property rights of third parties, and thus any person who implements any part of this document should consult an intellectual property attorney before any such implementation. Without limiting the foregoing, this document may provide for the use of public key encryption and other technology, which may be the subject matter of patents in several countries. Any party seeking to implement this document is solely responsible for determining whether its activities require a license to any such technology, including for patents on public key encryption technology. EMVCo shall not be liable under any theory for any party's infringement of any intellectual property rights in connection with this document. EMV® Type Approval Terminal Contactless Product Administrative Process Revision Log – Version 2.11d Page ii / v © 2011-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. Revision Log – Version 2.11d The following changes have been made to the document since the publication of Version 2.11c. Some of the numbering and cross references in this version have been updated to reflect changes introduced by the published bulletins. The numbering of existing requirements did not change, unless explicitly stated otherwise. Reason for change Introduction of Type Approval for Entry Point Module in standalone EMV® Type Approval Terminal Contactless Product Administrative Process Contents Page iii / v © 2011-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. Contents TERMINAL TYPE APPROVAL CONTACTLESS PRODUCT ............................................................ 0 LEGAL NOTICE ......................................................................................................................................... 1 REVISION LOG – VERSION 2.11D .......................................................................................................... 2 CONTENTS .................................................................................................................................................. 3 1 INTRODUCTION ................................................................................................................................. 7 1.1 AUDIENCE .............................................................................................................................................. 7 1.2 NORMATIVE REFERENCES ...................................................................................................................... 7 1.3 DEFINITIONS .......................................................................................................................................... 9 1.4 NOTATIONAL CONVENTIONS ............................................................................................................... 12 1.4.1 Abbreviations ............................................................................................................................. 12 1.5 TERMINOLOGY & CONVENTIONS ......................................................................................................... 12 2 TYPE APPROVAL OVERVIEW ...................................................................................................... 13 2.1 SCOPE OF CONTACTLESS TYPE APPROVAL .......................................................................................... 13 2.1.1 EMVCo Contactless Terminal Type Approval Process Goal ..................................................... 13 2.1.2 Contactless Terminal Architecture: the Product ........................................................................ 13 2.1.3 Multi-Kernel Environment .......................................................................................................... 14 2.1.4 Modular Approach Principles .................................................................................................... 14 2.1.5 Contactless Product Identification and Family of Product ........................................................ 15 2.2 EMVCO CONTACTLESS TYPE APPROVAL DESCRIPTION ...................................................................... 17 2.2.1 Initial Product Submission ......................................................................................................... 17 2.2.2 Derivative Product Submission .................................................................................................. 17 2.2.3 Request of Approval ................................................................................................................... 19 2.2.4 Derivative Request of Approval .................................................................................................. 19 2.2.5 Renewal Request for Approval ................................................................................................... 19 2.2.6 Laboratories testing procedures ................................................................................................. 20 2.3 CONTACTLESS TYPE APPROVAL LIFE CYCLE CONCEPT ....................................................................... 21 2.3.1 Contactless Product Life Cycle and Type Approval Milestones ................................................. 21 2.3.2 Product Design Phase ................................................................................................................ 21 2.3.3 Product Debugging Phase .......................................................................................................... 21 2.3.4 Product Approval Phase............................................................................................................. 21 2.3.5 Product Approval Renewal Phase .............................................................................................. 22 2.4 ICS SUBMISSION RULES ....................................................................................................................... 23 2.4.1 ICS Submission ........................................................................................................................... 23 2.4.2 ICS replacement ......................................................................................................................... 23 2.5 EMVCO TYPE APPROVAL FEE STRUCTURE .......................................................................................... 24 3 ROLES & RESPONSIBILITIES ....................................................................................................... 25 3.1 EMVCO ............................................................................................................................................... 25 EMV® Type Approval Terminal Contactless Product Administrative Process Contents Page iv / v © 2011-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.2 EMVCO TYPE APPROVAL SECRETARIAT (CATA) .............................................................................. 26 3.3 AUDITORS ............................................................................................................................................ 26 3.4 EMVCO RECOGNISED LABORATORIES ................................................................................................ 26 3.5 PRODUCT PROVIDER ............................................................................................................................ 27 3.5.1 Type Approval Request ............................................................................................................... 27 4 TYPE APPROVAL PROCEDURE ................................................................................................... 28 4.1 REGISTRATION ..................................................................................................................................... 31 4.2 CONTRACT WITH EMVCO ................................................................................................................... 31 4.3 INITIAL AND DERIVATIVE TYPE APPROVAL PROCESS .......................................................................... 32 4.3.1 Product Provider and Laboratory Operations ........................................................................... 32 4.3.2 Product Provider Preparation for Approval Request................................................................. 36 4.3.3 Product Provider Request for Approval ..................................................................................... 36 4.3.4 EMVCo Approval ....................................................................................................................... 37 4.3.5 Derivative Submission: Laboratory Testing Procedure ............................................................. 40 4.3.6 Administrative LOA request Submission .................................................................................... 46 4.4 TYPE APPROVAL RENEWAL PROCESS .................................................................................................. 49 4.4.1 Basic Policy ................................................................................................................................ 49 4.4.2 Laboratories for renewal testing ................................................................................................ 51 4.4.3 Samples Submission ................................................................................................................... 51 4.4.4 ICS Submission ........................................................................................................................... 51 5 TEST VERSION AND SPECIFICATION CHANGE ..................................................................... 52 5.1 TEST CHANGES WITHOUT SPECIFICATION UPDATE .............................................................................. 52 5.2 TEST CHANGES DUE TO SPECIFICATION UPDATE ................................................................................. 52 5.3 TESTING APPLICABILITY ...................................................................................................................... 53 6 PRODUCT CHANGES ....................................................................................................................... 54 7 CHANGE IN CONTACT DETAILS ................................................................................................. 55 8 APPENDIX A: TEMPLATES AND FORMS ................................................................................... 56 9 APPENDIX B: CHECKSUM IMPLEMENTATION RULES ........................................................ 57 10 APPENDIX D: CONTACTLESS KERNEL C -REGX PROCEDURE (OPTIONAL) .................. 60 10.1 DEFINITION OF A CONTACTLESS KERNEL C-REGX ............................................................................. 60 10.2 TYPE APPROVAL PROCEDURES ............................................................................................................ 60 10.2.1 Contactless Product submitted for the initial Approval contains a Contactless Kernel C-REGx 60 10.2.2 LoA issuance .............................................................................................................................. 61 11 APPENDIX E: AUTORUN PARAMETER TESTING ................................................................... 62 12 APPENDIX F: TYPE APPROVAL OF CONTACTLESS KERNEL C -8 IN STANDALONE ... 63 12.1 TYPE APPROVAL PROCEDURES ............................................................................................................ 63 13 APPENDIX G: TYPE APPROVAL OF ENTRY POINT MODULE IN STANDALONE ........... 65 13.1 TYPE APPROVAL PROCEDURES ............................................................................................................ 65 EMV® Type Approval Terminal Contactless Product Administrative Process Contents Page v / v © 2011-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. 14 APPENDIX H: OVERVIEW OF PRODUCT QUALIFICATION PROCESS .............................. 67 EMV® Type Approval Terminal Contactless Product Administrative Process Introduction Page 7 / 68 © 2011-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 Introduction EMVCo, LLC (“EMVCo”) is the manager of the EMV Contactless Specifications for Payment Systems hereinafter called the EMV Contactless Specifications. The objective of this document is to provide a Type Approval process for Contactless Products implementing the following specifications: • EMV Contactless Specifications for Payment Systems – Book A • EMV Contactless Specifications for Payment Systems – Book B • EMV Contactless Specifications for Payment Systems – Books C-n Note: EMV Level 1 Contactless Specifications for Payment Systems is addressed in a separate process document dedicated to Level 1. Common industry practice requires Product Providers to accommodate local Acquirer requirements in their Product. These Acquirer requirements are out of the EMVCo Type Approval scope. The Product Software Architecture plays a significant role in determining whether complying with non-EMV acquirer requirements are likely to impact the approved EMV Contactless Product. EMVCo limits Type Approval to the EMV Contactless Product, leaving the responsibility to the appropriate local acquiring entity (also referred to as the owner of the environment of use) to validate continued compliance with the EMV Contactless Specifications functionality in the integrated acquiring environment. All readers of this document are advised that Type Approval, when granted by EMVCo, shall not be construed as a warranty or representation of any sort, nor may it be relied upon by any party as an assurance of quality or functionality of any product or service. Please note the legal notice stated above at page 2 of this document for important limitations on the scope of Type Approval. 1.1 Audience The target audience of this document includes: • Product Providers • Laboratories recognised to perform the Type Approval tests • Auditors acting on behalf of EMVCo 1.2 Normative References Table 1: Reference Documents Reference Publication name Bookmark [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 – Version 4.4 – October 2022 EMV® Type Approval Terminal Contactless Product Administrative Process Introduction Page 8 / 68 © 2011-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. Security and Key Management [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 Latest version available [Book D] EMV Level 1 Contactless Specifications for Payment Systems – EMV Contactless Interface Specification Latest version available [ICS] EMVCo Type Approval Contactless Product - Implementation Conformance Statement Latest version available [TA EP] EMVCo Type Approval Contactless Product - Entry Point Test Plan Latest version available [TA S] EMVCo Type Approval Contactless Product - EMVCo System Test Plan This includes: • 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 [CL TE] Test Environment Requirements Latest version available [TA ADMIN L1] EMVCo Type Approval Contactless Product – Level 1 Administrative Process Latest version available [TA C-n] C-n Kernel Test Plans - Functional Test Plan Latest version available [TA INT C-n] C-n Specific Tests required by Payment Systems. Latest version available [TB1] EMV Terminal Type Approval Bulletin 185 Latest version available EMV® Type Approval Terminal Contactless Product Administrative Process Introduction Page 9 / 68 © 2011-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.3 Definitions The following terms are used in this specification: Card - A payment card as defined by a payment system. CATA – EMVCo Type Approval secretariat. Checksum - A Product Provider-generated value (minimum 4 bytes) for each module. This Checksum must be a unique value for each module. The method or algorithm used for generating the Checksum is left to the discretion of the Product Provider. For example, a Product Provider may choose to implement SHA-1 or CRC. These values shall be easily retrievable for each Kernel Module, Software Module, External Libraries or Entry Point Module when loaded in the Product and this for comparative purposes. Refer to Appendix B: Checksum Implementation Rules for more details on Checksum defined rules. Compliance - Meeting all the requirements including any implemented optional requirement(s). Contactless Kernel C-REGX – The proprietary Kernel software located in the Contactless Product where x is a registered Kernel ID using the EMVCo Kernel ID registration process. C- REGX does not refer to EMVCo Kernel C-n. EMVCo Software – The part of the software present in the Product which follows EMVCo requirements (i.e. Books A, B and C-n). Entry Point Module – The software module managing application (AID) and Kernel selection according to [Book B]. Family of Product - A Family of Products means multiple Contactless Products having the same Hardware and Communication Configuration: • CPU • Operating System • RAM (same or higher) • Communication Interface and API with the PCD Function – A process accomplished by one or more commands and resultant actions that are used to perform all or part of a transaction. Implementation Conformance Statement (ICS) - A form completed by the Product Provider. The written statement lists all optional functions as specified in the EMV Contactless Specifications. EMV® Type Approval Terminal Contactless Product Administrative Process Introduction Page 10 / 68 © 2011-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. Integrated circuit(s) - Electronic component(s) designed to perform processing and/or memory functions. International Organization for Standardization (ISO) - An international body that provides standards for financial transactions and telecommunication messages. ISO works in conjunction with the International Telecommunication Union (ITU) for standards that affect telecommunications. ISO supports specific technical committees and work groups to promulgate and maintain financial service industry standards. Interface - Technical requirements for exchanging data and functions between two software modules. Kernel C-n - Is a software Module compliant to one of the [Book C-n] specifications. Laboratory - A facility recognised by EMVCo to perform Type Approval testing. Letter of Approval - Written statement that documents the decision of EMVCo that a specified Product has demonstrated sufficient compliance to the EMV Contactless Specifications on the date of testing. Main Laboratory – For Contactless Product Type Approval only, it is the Laboratory performing: - Entry Point Module [TA EP] (if not previously approved in standalone), - Book A General Requirements Testing [TA BAGR], - Module Integration Testing [TA MIT], - and one Contactless Kernel C-n at minimum. Major modification - Technical change to the EMV application or addition to the application that implies the Product Provider cannot guarantee continued compliance of the modified application with the requirements of EMV Contactless Specifications, as defined by EMVCo. Minor modification - Technical change to the EMV application that does not affect the functionality of the application with respect to the requirements of EMV Contactless Specifications, as defined by EMVCo. PCD - Proximity Coupling Device. A device of the Product that uses inductive coupling to provide power to the PICC and also controls the data exchange with the PICC. Procedure - Specified way to perform a set of tasks. Product - According to the definition in sections 2.1.2 which defines the Product to be type approved during the Type Approval process. It must be the Product with the final software EMV® Type Approval Terminal Contactless Product Administrative Process Introduction Page 11 / 68 © 2011-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. module versions (Entry Point and/or C-n Kernel(s)). Product Hardware and Communication Configuration - Identify the set of resources of the Product: • CPU • Operating System • RAM • Communication Interface and API with the PCD Protocol - Method of communication between the ICC and the PCD, represented in this specification by Type A and Type B. Reference specification (EMV Contactless Specifications) - A set of documents defining the requirements the Product shall comply with. The reference specification consists of the current EMV Contactless Specifications (Books A, B, C-n, D) for Payment Systems and any additional documentation required when performing Type Approval. Registration number - A unique identification number assigned by EMVCo to a Product Provider. Request for Approval - A form that goes with a Product submitted to EMVCo for Type Approval and marks the launch of its invoice. Sample - A Product taken out of the production line for testing. Software Module - A self-contained program that carries out a clearly defined task and is intended to operate within a larger program suite. Mainly a module represents a Kernel C-n or Entry Point. Test - Any activity that aims at verifying the compliance of a selected Product or process to a given requirement under a given set of conditions. Test case - A description of the actions required to achieve a specific test objective. Test Kernel – Software simulating a Contactless Kernel that must be present in the Product under test for testing reason. Type Approval – The acknowledgment by EMVCo that the specified Product has demonstrated sufficient compliance to the EMV Contactless Specifications for its stated purpose. EMV® Type Approval Terminal Contactless Product Administrative Process Introduction Page 12 / 68 © 2011-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. Type Approval documentation - Full set of documents and procedures issued by EMVCo to enable the Type Approval process. Type Approval process - The processes that test a Product for compliance with specification. 1.4 Notational Conventions 1.4.1 Abbreviations FIT Fully Integrated Terminal ICC Integrated Circuit Card ICR Integrated Card Reader ICS Implementation Conformance Statement ISO International Organization for Standardization Lab Laboratory LoA Letter of Approval PCD Proximity Coupling Devices PICC Proximity Integrated Circuit Card RFA Request for Approval RRP Relay Resistance Protocol TTA Terminal Type Approval 1.5 Terminology & conventions The following words are often used in this specification and have a specific meaning: May Defines a Product or system capability, which is optional or a statement which is informative only and is out of scope for this specification. Should Defines a Product or system capability, which is recommended. EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Overview Page 13 / 68 © 2011-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 Type Approval Overview 2.1 Scope of Contactless Type Approval 2.1.1 EMVCo Contactless Terminal Type Approval Process Goal EMVCo Contactless Terminal Type Approval ascertains the level of confidence that Product Providers have correctly implemented the EMV Contactless Specifications. Product Providers submit their Product with the software and appropriate documentation, including the Implementation Conformance Statement (ICS), to an EMVCo recognised Laboratory for testing. The Laboratory executes a set of EMVCo-defined test cases and prepares a test report document for the Product Provider that may then be submitted to EMVCo for evaluation. EMVCo’s evaluation of the test report concludes with the issuance of a Letter of Approval or decline notification. Obtaining an EMV Product Approval from EMVCo has the following advantages: • Acquirers have access to terminal implementations in respect of which compliance to the EMV Contactless Specifications has already been tested - yielding a likely reduction in testing costs as well as improved time to market for final implementations. • Product Providers can sell the approved EMVCo compliant Product on a worldwide basis and differentiate themselves from the competition. 2.1.2 Contactless Terminal Architecture: the Product There are three possible options for the Product under test, called the 'Product' in the rest of the document: 1 / The Contactless Product: it is the general case defining the Contactless Product that is submitted in this process. The Product includes: • Communication with contactless cards • Application selection and Kernel activation • Kernel(s) • The hardware Note: The Product could be any of the following: - a Fully Integrated Terminal, - an Intelligent card reader - a Combination of terminal and transparent card reader. 2/ The Contactless Kernel C-8 in standalone Appendix F: Type Approval of Contactless Kernel C-8 in standalone of the present document describes the EMVCo administrative procedure when the Product Provider wants to submit a Contactless Kernel C-8 as a standalone Kernel. EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Overview Page 14 / 68 © 2011-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/ The Entry Point Module in standalone Appendix G: Type Approval of Entry Point Module in standalone of present document describes the EMVCo administrative procedure when the Product Provider wants to submit an Entry Point Module in standalone. 2.1.3 Multi-Kernel Environment The Contactless Product submitted for approval works in a multi-Kernel environment. This means that one or several Kernels C-n (C-2 to C-8) are present at the time of testing and will be tested independently. The number of Kernels (C-2 to C-8) present in the Product for approval depends on the Product Provider’s decision. He may decide to submit a Product containing one Kernel (as a minimum) or up to 7 EMV Kernels for approval. Approval will be granted to the corresponding Product and is valid only for that configuration reflecting the specific Kernel(s) present during approval. A Product Provider can decide at any time to enhance the Product by adding/deleting/changing a Kernel (or Entry Point Module). However, this shall result in a new approval if required to that Product, reflecting the new Product. When the Product contains any software or Kernel not described by EMVCo and changes occur to such software, it is considered as a change to the Product, hence, section 6 ‘changes’ applies. 2.1.4 Modular Approach Principles EMVCo assumes that the Contactless Products implement a modular software architecture. By submitting a Product, the Product Provider confirms compliance with the Modular Architecture. EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Overview Page 15 / 68 © 2011-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.1.5 Contactless Product Identification and Family of Product 1/ Contactless Product Identification A Contactless Product submitted for approval is identified by: 1. Its Product Hardware and Communication Configuration: the Hardware managing the EMVCo Software and communicating with the PCD: • CPU • Operating System • RAM • Communication Interface and API with the PCD 2. Its EMVCo software that covers: • Book A • Book B (Entry Point) • All C-n Kernels 3. Its Level 1 approved PCD Changing any of the above part of the Contactless Product shall follow the rules defined in the present document. 2/ Family of Products A Family of Products means multiple Contactless Products having the same Hardware and Communication Configuration: • CPU • Operating System • RAM (same or higher) • Communication Interface and API with the PCD EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Overview Page 16 / 68 © 2011-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. Below is an example of 4 Members of the same Family, with different EMVCo Software and different PCDs: EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Overview Page 17 / 68 © 2011-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.2 EMVCo Contactless Type Approval Description 2.2.1 Initial Product Submission The following rules shall be applied to Products initially submitted to EMVCo for formal approval when the Product implements a Modular Architecture. These rules do not apply to debug testing that may be conducted directly between the Laboratory and Product Provider. • All functional options, Hardware and Communication Configuration, L1 Approved PCD, Entry Point Module and Kernel(s) present must be identified on the ICS. This reflects the Product configuration submitted for approval. • The Laboratory must validate and submit a copy of the completed ICS to EMVCo prior to performing Type Approval testing. EMVCo will review the statement for accuracy, archive the form for later comparison, and send an acknowledgement that the ICS is acceptable for testing. • Samples are retained by the Laboratory for a period of the LoA validity + 1 year as of the date of approval. The Product Provider is responsible for providing support as necessary to maintain the Product in an operational state to accommodate any Derivative testing or analysis that may be deemed necessary by EMVCo. Note: If the EMV Contact is present in the Product, it shall be listed in the ICS for testing purposes. 2.2.2 Derivative Product Submission The following rules shall be applied to Products submitted to EMVCo for Derivative formal approval: • Derivative Submission shall be based on the Initial Product or on a Products part of the same Family (so having the same Hardware and Communication Configuration as the Product submitted during the Initial Submission). • New PCD must be identified on the ICS (if applicable). • Any added Kernel(s), modified Entry Point Module or modified Kernel(s) must be identified on the ICS (if applicable). • The Laboratory must validate and submit a copy of the completed ICS to EMVCo prior to performing Type Approval testing. EMVCo will review the statement for accuracy, archive the form for later comparison, and send an acknowledgement that the ICS is acceptable for testing • Samples are retained by the Laboratory for a period of the LoA validity + 1 year as of the date of approval. The Product Provider is responsible for providing support as necessary to maintain the Product in an operational state to accommodate any Derivative testing or analysis that may be deemed necessary by EMVCo. • The Product ending date validity remains the same as the Initial Product. EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Overview Page 18 / 68 © 2011-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.2.2.1 Family of Product vs Derivative Submission Changes to have a new Family Product Member (with the same Hardware and Communication Configuration): • EMVCo Software covers : o Book A o Book B (Entry Point) o C-n Kernels • PCD replacement by another PCD already tested once in a Contactless Product of the same family. Note1: EMVCo Software changes require testing as described in the Derivative Submission process. Note2: Changing a PCD which is not previously Level 1 and Contactless Product approved require testing as described in the Derivative Submission process Below is an example of creating a new Product in the same Family by updating the Kernel C- 2 to a new version. 2.2.2.2 Allowed changes in a Product Changes allowed during Derivative Submission: • EMVCo Software covers: • Book A & Book B (Entry Point) • C-n Kernels (changes or added) Any of the above changes, if tested once, can be used in any member of the Family without retesting. • PCD EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Overview Page 19 / 68 © 2011-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. A PCD change may require, on Payment System request, additional testing such as Performance testing or C-n Specific testing. Note: An EMVCo Software (package of Entry Point and Kernel(s) C-n) tested once in a Product can be used in any other Member of the same Family without any testing and so without Derivative Submission. Other Minor Changes: Changes defined as minors in Bulletin 11 – Contactless Product are allowed, without any testing, to create a new Family Product Member. Note: Minors changes are not tested, it is the responsibility of the Product Provider to ensure the new Product comply with the Family. 2.2.3 Request of Approval To determine compliance, reference implementations of the Product must undergo predefined tests in a specified test environment (Laboratory). The Product submitted to Laboratory shall be submitted with a Contactless Level 1 (PCD) complete with a valid LoA and must be representative of final deployment. The Letter of Approval will be granted for Entry Point Module in standalone or Contactless Kernel C-8 in standalone or per Kernel in the Contactless Product (For Contactless Product, the LOA includes also the hardware and the Entry Point Module). After the Letter of Approval has been granted, it is valid as long as the following applies: • The approval is not revoked by EMVCo. • The LoA is valid for the period of approval duration. 2.2.4 Derivative Request of Approval Some changes are allowed in the Product as per section 2.2.2.2. The updated Product submitted to Laboratory shall be submitted with a Contactless Level 1 (PCD) complete with a valid LoA and must be representative of final deployment. The Letter of Approval(s) will be granted to the submitted changes only. After the Letter of Approval has been granted, it is valid as long as the following applies: • The approval is not revoked by EMVCo. • The LoA is valid for the period of approval duration. 2.2.5 Renewal Request for Approval A Product Approval is valid for 4 years. The starting date is the date of the initial approval or the date of the Derivative approval. Every 4 years, EMVCo evaluates whether the Product demonstrates sufficient compliance to the current EMV Contactless Specifications. If the evaluation results are positive then EMVCo grants an extension to the Product Letter of Approval. The following rules will apply to Renewal Request: EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Overview Page 20 / 68 © 2011-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 Entry Point Module in standalone • The Entry Point Module in standalone ongoing LoA is still valid at the time of renewal. • EMV Contactless Specifications for Payment Systems – Book B is still valid. For Contactless Kernel C-8 in standalone • The Contactless Kernel C-8 in standalone ongoing LoA is still valid at the time of renewal. • EMV Contactless Kernel C-8 specifications are still valid. For Contactless Product • The Kernels(s) ongoing LoA is still valid at the time of renewal. • The Level 1 LoA of all PCD(s) listed in the Product must be valid at the time of renewal. In case some PCD(s) LoAs are no longer valid, these concerned PCD(s) will be removed from the renewed Contactless Product LoA. • All EMV Contactless Specifications are still valid (Books A, B and C-n) • Renewal per Kernel LOA may be requested (to address different Kernel expiration dates) After the renewal date, Products not passing renewal testing nor applying for renewal testing will be removed from the approved list and their Letter of Approval will be considered revoked. 2.2.6 Laboratories testing procedures The Laboratories must perform the following testing procedure depending on the type of submission: • For Initial submission, the testing procedure is described in section 4.3.1.1. • For Derivative submission, the testing procedure is described in section 4.3.5. • For Renewal submission, the testing procedure is described in section 4.4.1.1. Transaction Type Testing: Section IV of the Contactless Product ICS requests the transaction type(s) ‘supported and activated’ for each Kernel present in the Contactless Product. When a transaction type is supported and activated at a Kernel level then it is considered supported and activated at the Product level and the related tests shall be executed. Note: ‘Support and Activation’ of the transaction type implementation depends on each Kernel. For example for C-3, if the transaction type is supported, it is automatically activated. EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Overview Page 21 / 68 © 2011-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.3 Contactless Type Approval Life Cycle Concept The following sections identify the Type Approval life cycle which is a logical concept regarding the design and key approval milestones of a Contactless Product. 2.3.1 Contactless Product Life Cycle and Type Approval Milestones Type Approval shall be done on a sample that is representative of future production. Therefore, the Type Approval milestone shall occur at a particular moment in the Product Life cycle: Figure 1 - Life cycle of Contactless Product 2.3.2 Product Design Phase The Product is developed by the Product Provider or an entity directly related to the Product Provider. Most importantly, Product design and development must be in accordance with the EMV Contactless Specifications, as well as any other applicable specifications (e.g. government standards). 2.3.3 Product Debugging Phase The Product design is checked and tested against all related specifications. EMVCo recommends that compliance testing against the EMV Contactless Specifications is conducted on the representative sample before proceeding to Type Approval, preferably with tools equivalent to those used for Type Approval tests. The Product Provider must identify which options its Product design has incorporated from the EMV Contactless Specifications and gather the information to be submitted in the Type Approval process. 2.3.4 Product Approval Phase EMVCo assesses compliance (see section 4.30) of the Product design against the EMV Contactless Specifications. To determine compliance, reference implementations of the Product must undergo predefined tests in a specified test environment (EMVCo Recognised Laboratory). EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Overview Page 22 / 68 © 2011-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. The Product submitted for approval shall be complete with a valid EMVCo Level 1 Letter of Approval and must be representative of final deployment. After the Letter of Approval has been granted, it is valid as long as the following applies: • The approval is not revoked by EMVCo. • The LoA is valid for the period of approval duration. Any change to the Product creates a new Product, whether it occurs before, during, or after deployment. Type Approval of that new Product is not presumed. Derivative Submission Approval At any time after initial approval, the Product Provider may decide to update the Product or to create a new Family Member. This will result in an additional approval called Derivative Submission. 2.3.5 Product Approval Renewal Phase Prior to the renewal date, Product Providers may request a renewal by submitting the original approved Product to EMVCo for Renewal testing (see section 4.4). The purpose of this renewal testing is to ensure that Products pass the most current EMVCo testing. At the time of submission, the Product submitted for approval shall be complete with valid EMVCo Level 1 Letter of Approval. EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Overview Page 23 / 68 © 2011-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.4 ICS Submission rules 2.4.1 ICS Submission • The initial ICS submission to the EMVCo is free of charge. • The Laboratory is responsible of reviewing the ICS provided by the Product Provider. • The ICS submitted must be the ICS in pdf format, capable of importing/exporting XML format and shall be digitally signed by the Product Provider and the Laboratory at the time of submission to EMVCo. • The Laboratory supplies the signed copy of the vendor-supplied ICS to EMVCo for review prior to the start of the Type Approval testing process. • EMVCo will review and approve the ICS by returning the ICS in pdf digitally signed and with the official ICS number. • In case the ICS is incorrectly filled, decline fee applies to Laboratory. • ICS submission shall be done using the latest version of the ICS available at the time of the submission on EMVCo website. During the migration period, former version of the ICS available on the website may be used. 2.4.2 ICS replacement • One free ICS replacement is allowed during the ICS life cycle. Any Derivative ICS replacement requested will be charged to the Product Provider. • Same submission process applies as for initial ICS submission (Laboratory submits the changed ICS). • This applies to any change in the ICS after the official approval of the ICS by EMVCo. • After the start of the test session of the Product, ICS replacements (following the rules of the previous bullet) are only allowed for administrative information update (such as name of Product) but not are not allowed for technical information update. • Laboratory shall ensure that any ICS change requested is not made to hide a bug in the Product (such as deactivation a function because this function is not working properly). • ICS replacement is no more allowed after Test Report submission to EMVCo. Note: ICS decline process remains and any error reported by EMVCo will be charged to the Laboratory (as Laboratory is responsible of reviewing the ICS provided by the Product Provider). ICS decline process applies to the initial ICS submission and also to any other ICS replacement (charged or not charged to the Product Provider). EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Overview Page 24 / 68 © 2011-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.5 EMVCo Type Approval fee structure The following fee structures apply: • Initial submission • Derivative submission for a software change • Derivative submission for a new/change PCD • Administrative LoA request submission • ICS Replacement (starting at 2 nd Replacement) • Product renewal • Declined ICS/Report • LoA reissuance Note: The amount of fees for each are published in Terminal Type Approval Bulletin 185. EMV® Type Approval Terminal Contactless Product Administrative Process Roles & Responsibilities Page 25 / 68 © 2011-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 Roles & Responsibilities The following sections define the roles and responsibilities of the various participants in the Type Approval process. 3.1 EMVCo EMVCo defines Type Approval contactless requirements and evaluates operational results. EMVCo provides the following services: • Defines the Administrative Process. • Operates the Approval Process. • Defines mandatory auditor qualification requirements. • Qualifies companies that perform audits to establish Laboratory recognition. • Defines Laboratory recognition requirements. • Evaluates Laboratory audit results and determines if the EMVCo recognition should be granted to a Laboratory. • Defines Tool Qualification Process. • Qualifies Test Tool and maintains a list of Qualified Test Tools on the EMVCo web site. • Coordinates with the Payment Systems for the Kernels C-n testing. • Manages Laboratory appeals process and resolves recognition disputes. • Defines appropriate test cases to test compliance with EMVCo Contactless Specifications. • Defines procedures used to perform testing, submits test results for evaluation, and communicates evaluation results. • Defines the test tools and evaluation criteria thereof. • Evaluates Product Approval test results to determine whether approval should be granted. • Evaluates Product renewal tests results to determine whether a renewal should be granted. • Notifies appropriate EMVCo working group of warranted specification corrections, clarifications, and enhancements where appropriate. • Evaluates Product and card failure complaints to determine if Type Approval revocation for a particular Product is appropriate. • Provides result response to Product Provider’s Type Approval test result evaluation request. • Maintains and publishes (via EMVCo website) a list of Products that have received EMVCo Type Approval notification. • Issue the Letter of Approval. EMV® Type Approval Terminal Contactless Product Administrative Process Roles & Responsibilities Page 26 / 68 © 2011-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.2 EMVCo Type Approval Secretariat (CATA) The EMVCo Terminal Type Approval Secretariat (CATA) is responsible for managing the EMVCo Type Approval contactless process. This includes the administrative functions associated with Product Provider’s registration, completion of contracts, processing approval requests and fees, issuing Letter of Approval letters of compliance or decline, etc. The role also includes communicating Type Approval status to third parties and the maintenance of a database that provides the following: • Coordinate with the Payment Systems. • Qualified Auditors. • Recognised Laboratories. • Qualified EMVCo Tools. • Type Approval and compliance requirements and test cases. • Approved EMV contact & contactless Products. 3.3 Auditors One type of auditors is required for contactless process: • Laboratory Auditor: The Laboratory Auditor is in charge of auditing the Laboratory for recognition purpose. 3.4 EMVCo Recognised Laboratories The Laboratory is a test facility recognised by EMVCo to conduct testing of the Product or part of the Product in accordance with the EMVCo Type Approval requirements and test cases. It shall also: • Verify the Implementation Conformance Statement provided by the Product Provider • Extract the set of test case depending on: o The version of Entry Point, o The version of each Kernel, o If it is an initial or derivative submission, o If it is a renewal approval. • Perform the test session • Checksum values of each module and sub modules; as well as untested modules shall be retrieved for the Contactless Product submitted and checked by the Laboratory against value declared by the Product Provider. • Analyse the test results. • Communicate the results to the Product Provider. • Send to EMVCo the result of the test session(s) after Product Provider approval. • Eventually send the Request for Approval on behalf of the Product Provider. EMV® Type Approval Terminal Contactless Product Administrative Process Roles & Responsibilities Page 27 / 68 © 2011-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.5 Product Provider 3.5.1 Type Approval Request The Product Provider shall provide the Product to be tested by the Laboratory: • Sign appropriate contracts. • Fill out the Request for Approval and Implementation Conformance Statement Forms. • Select one or several Laboratories to run the tests session(s). • Submit to Laboratory(ies) the ICS for review. • Submit to EMVCo the Request for Approval form (or the Laboratory can submit on behalf of the Product Provider). • Submits the final Product to the Laboratory(ies) for testing. • Send the identical samples to the Main Laboratory. • Verify and approve the test results provided by the Laboratory(ies). • Manage the Family of Product. EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Procedure Page 28 / 68 © 2011-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 Type Approval Procedure The Type Approval procedure applied by Product Providers, Laboratories, auditors and EMVCo includes the following: • Product Provider obtains registration information from the EMVCo web site or from an EMVCo recognised Laboratory • Product Provider submits a completed registration template to the EMVCo Type Approval Secretariat • Product Provider obtains the Level 2 EMVCo/vendor contract from EMVCo, the EMVCo web site or from an EMVCo recognised Laboratory • Product Providers conclude the contract with EMVCo. This contract covers Product Approval. A contract between EMVCo and the Product Providers must be signed before test results are submitted to EMVCo for evaluation and potential Type Approval. • Product Providers select one or several recognised Laboratories from the list of recognised Laboratories published on the EMVCo web site: o For Entry Point Module in standalone testing [TA EP] or Contactless Kernel C- 8 in standalone testing [TA C-8], the selected Laboratory is referenced as the Main Laboratory. o For Contactless Product, the Laboratory performing Book A General Requirements testing [TA BAGR], Entry Point Module testing [TA EP] (if not already approved), one Contactless Kernel C-n testing using [TA C-n] and [TA INT C-n] at minimum and Module Integration Testing [TA MIT] is referenced as the Main Laboratory. • Product Providers conclude a contract with the selected Laboratory(ies) in respect of the Product to be tested. • Product Providers and selected Laboratory(ies) shall fill out the ICS: o For Contactless Product, one ICS for the overall Product (called Contactless Product ICS) and one ICS for each Kernel C-n present. The Contactless Product ICS is managed by the Main Laboratory and it is the responsibility to share this ICS (after EMVCo Approval of the ICS) with the other selected Laboratories (if any). o For Entry Point Module in standalone, one ICS for Entry Point Module only o For Contactless Kernel C-8 in standalone, one ICS for Kernel C-8 • Each Laboratory reviews for accuracy the ICS received from the Product Provider and then archived for later comparison. Each Laboratory submits a validated copy of the completed ICS to EMVCo prior performing testing. This ICS must be in pdf format, capable of importing/exporting XML format and shall be digitally signed by the Application Provider and by the Laboratory (both signatures on the same ICS submitted) as paper copy or scanned copy are no more accepted. • The EMVCo CATA Secretariat will respond with a confirmation that all the submitted ICSs are acceptable for testing to the Main Laboratory. o If the submitted ICS is acceptable the Secretariat responds back to the Laboratory and return at the same time the approved ICS in .pdf format digitally signed o If the submitted ICS is unacceptable the Secretariat inform the Laboratory and apply the “Decline fees” (see Bulletin) EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Procedure Page 29 / 68 © 2011-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. • All Laboratories perform appropriate testing of the submitted Product against the published test requirements and test cases. • On Product Provider’s request, the Laboratories submit the ICSs and test results (with Checksum of the modules tested) to the EMVCo CATA Secretariat. • Product Providers submit a completed Request for Approval form to EMVCo. Based on the RFA form, EMVCo will provide Product Provider with an invoice. • Based on the received invoice, the Product Provider shall settle the administrative fees with EMVCo. • If the fee payment is confirmed by EMVCo Financial Secretariat, analysis of the ICS and test report by EMVCo will start and, if appropriate, approval notified. Note that payment cannot be refunded after the RFA form is received. • Type approved Contactless Products are posted on the EMVCo web site after approval notification. • Approved Products are retained by the Laboratory for a period of the LoA validity + 1 year as of the date of approval. The Product Provider is responsible for providing support as necessary to maintain the Product in an operational state to accommodate any testing or analysis that may be deemed necessary by EMVCo. Note: An Approved Contactless Product ICS is valid 6 months. If the related Request for Approval and the associated report is not submitted and the invoice is not paid within that period, all related documents to this approval request are no more valid (ICS, RFA, report) and a new process shall be restarted. Note that, in this case, the invoice is not reimbursed. Figures 8 below shows the diagram of Type Approval Process EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Procedure Page 30 / 68 © 2011-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. Figure 2 - Contactless Product Type Approval Procedure EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Procedure Page 31 / 68 © 2011-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.1 Registration Registration provides the Product Provider with entry to the EMVCo approval process in order to make the Product Provider aware of all formalities that need to be finalized prior to submitting their final test report to EMVCo for approval. The registration process is composed of the following steps: • The Product Provider enters registration information on the EMVCo Registration Web page. • The Product Provider will receive a confirmation email from EMVCo Type Approval Secretariat with the following additional information: o Link to the EMVCo Test Contract (DocuSign) o Appropriate contact information • The Product Provider shall sign the EMVCo Test Contract with DocuSign. • When the EMVCo Test Contract is countersigned by the EMVCo, the EMVCo Test Contract is sent back to the Product Provider by DocuSign. • A unique Registration Number is assigned and shared with the Product Provider. 4.2 Contract with EMVCo The Product Provider must complete and sign the EMVCo defined contract before final test results are submitted to EMVCo for evaluation and possible approval. This contract governs the relationship between EMVCo and the Product Provider and includes the Product Provider’s acceptance of all specifications, procedures, terms and conditions governing EMVCo Contactless Product Type Approval. The contract is standard for all Product Providers to ensure consistent requirements for all participants. Contract customization for individual Product Providers is not possible. The Product Provider must also complete and sign the: ‘Contactless Marks Trademark License Agreement - Vendor and Brand versions EMVCo’ available at EMVCo website. The agreement has to be signed with EMVCo prior to submission of a Product. EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Procedure Page 32 / 68 © 2011-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.3 Initial and Derivative Type Approval Process 4.3.1 Product Provider and Laboratory Operations The following operations are performed by the Product Provider and the Laboratory as they relate to the Type Approval procedure: • The Product Provider is free to select any EMVCo recognised Laboratories on purpose of achieving EMVCo Contactless Type Approval. A list of recognised Laboratories is published on the EMVCo web site. Once Laboratories have been selected, the Product Provider and Laboratories sign a contract defining the rights and obligations of the contracting parties. The provisions of Product Provider/Laboratory contract are up to the contracting entities and entirely out of EMVCo’s scope. Any fees payable to the Laboratory in respect of the tests to be performed are solely at the discretion of the Laboratory. • Product Provider sends the appropriate Implementation Conformance Statement (ICS) to the chosen Laboratory(ies) for each Product that it submits for testing. The ICS format and content requirements are determined by EMVCo. • Each Laboratory validates the Product Provider’s-supplied ICSs and supplies a copy to the EMVCo CATA Secretariat for approval prior to the start of the Type Approval testing process. • Product Provider sends to the Main Laboratory all needed samples. If multiple Laboratories are selected, the Main Laboratory dispatch the samples to Other Laboratories. • The Laboratory(ies) tests the Products in accordance with EMVCo test procedures. • The Product Provider prepares the Request for Approval form and submits it to the EMVCo CATA Secretariat. EMVCo then issues the invoice to the Product Provider. • Product Provider submits payment to EMVCo based on the received invoice. • The Laboratory(ies) sends the final test reports to the Product Provider being the owner of the test results. The Laboratory(ies) must advise EMVCo of any failures that have been encountered during testing. • The Laboratory(ies) submits an original copy of the test results report to the EMVCo CATA Secretariat and ensures that the Product Provider has already submitted his completed Request For Approval form. EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Procedure Page 33 / 68 © 2011-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.3.1.1 Laboratory test procedure for Initial Submission The Laboratories must perform the following testing procedure when the test session is performed for an Initial Product Submission: For the Main Laboratory: Before the Test Session: • Request the Other Laboratory(ies) (if any) to provide the Kernels C-2 to C-8 ICSs they are in charge of. The ICSs provided by the Other Laboratory(ies) to the Main Laboratory shall have been previously approved by EMVCo. • When all ICSs of the submitted Contactless Product have been received by the Main Laboratory, the Main Laboratory sends Contactless Product ICS to each Other Laboratory(ies) involved in this submission. Note : The Main Laboratory is responsible for the management of the samples. This includes reception from the Product Provider of all samples (including the ones for the Other Laboratory(ies)) and sending them to Other Laboratory(ies). During the Test Session: For the Entry Point in standalone: • Entry Point Module testing using [TA EP] test plan. For the Contactless Kernel C-8 in standalone: • Kernel C-8 testing using the [TA C-8] and [TA INT C-8] test plans. For the Contactless Product: • Book A General Requirements testing using [TA BAGR] test plan. • Entry Point Module testing using [TA EP] test plan. • Module Integration Testing using [TA MIT] test plan, for all C-n Kernel(s) present in Product. • Kernels C-2 to C-8 testing using the [TA C-n] functional test plans, [TA INT C-n] C-n specific tests plans, [TA P] Performance test plan and [TA RRP] RRP Accuracy test plan (for Kernel C-8 and C-2 only). The Main Laboratory shall test one or several Kernels declared in the ICS and present in the Product submitted (Main Lab shall test at least test one of Kernel present). Note1: All steps above must be run on the final software module versions. If any failures occur in a Module (Kernel or Entry Point), then the whole set of tests of the concerned Module (Kernel or Entry Point) must be re-run until a successful completion is achieved. If the successful completion of a Kernel testing cannot be achieved, but the Book A General Requirements, Entry Point Module and the other Kernel successfully pass the testing (included Module Integration Testing and Performance) without any change in the final software module versions, then the LoA can be issued without the concerned Kernel. Note2: Checksum values of each module and sub modules, external libraries; as well as untested Kernels or modules, shall be retrieved from the Contactless Product submitted and EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Procedure Page 34 / 68 © 2011-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. checked by the Laboratory against value declared by the Product Provider. It is not allowed to change any Checksum value during the Type Approval, as the Product submitted shall be the final Product Note3: If the Entry Point Module has been already approved in standalone and has a valid LoA in standalone on the same Operating System, Entry Point Module testing with [TA EP] test plan is not required. Note4: If the Contactless Kernel C-8 has been already approved in standalone and has a valid LOA with the same Operating System, Contactless Kernel C-8 testing with [TA C-8] and [TA INT C-8] test plan are not required. For the Other Laboratory (if any for Contactless Product Submission only): Before the Test Session: • On request from the Main Laboratory, provide the Kernels C-2 to C-8 ICSs it is in charge of. The ICSs provided to the Main Laboratory shall have been previously approved by EMVCo. • Receive back from the Main Laboratory, the Contactless Product ICS of Main Laboratory and the samples. During the Test Session: • Kernels C-2 to C-8 testing using the [TA C-n] functional test plans, [TA INT C-n] C-n Specific tests [TA P] Performance test plan and [TA RRP] RRP Accuracy test plan (for Kernel C-8 and/or C-2 only): Other Lab(s) shall test one or several Kernels declared in the ICS and present in the Product submitted but not tested by the Main Laboratory. • Testing must be done with final module versions of the Product. This means Laboratories must verify the Checksum of each module (Entry Point, Kernels C-n present in the Product), even for the module(s) not tested. Checksum values of each module and software module shall be retrieved from the Contactless Product submitted and checked by the Laboratory against value provided by the Product Provider in the ICS. It is not allowed to change any Checksum value during the Type Approval, as the Product submitted shall include final software module versions of the Product. Note1: A Laboratory running a test session for a Kernel C-n using related [TA C-n] and [TA INT C-n] test plans must run in the same session the C-n related [TA-P] Performance test plan and [TA RRP] RRP Accuracy test plan (for Kernel C-8 and/or C-2 only). Note2: If the Contactless Kernel C-8 has been already approved in standalone and has a valid LOA with the same Operating System, [TA C-8] testing and [TA INT C-8] testing are not required. 4.3.1.2 Contracts between Laboratories and Product Provider The provisions of the contract entered between Laboratories and Product Providers are entirely outside of EMVCo’s scope. However, the likely areas for inclusion are mentioned below for information purposes only: EMV® Type Approval Terminal Contactless Product Administrative Process Type Approval Procedure Page 35 / 68 © 2011-2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only p