EMV® Terminal Type Approval – PCD Level 1 – Administrative Process

EMV® Terminal Type Approval PCD Level 1 Administrative Process Version 3.2a.r September 2025 © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page i / v Legal Notice This document summarizes EMVCo’s present plans for evaluation services and related policies and is subject to change by EMVCo at any time. This document does not create any binding obligations upon EMVCo or any third party regarding the subject matter of this document, which obligations will exist, if at all, only to the extent set forth in separate written agreements executed by EMVCo or such third parties. In the absence of such a written agreement, no product provider, test laboratory or any other third party should rely on this document, and EMVCo shall not be liable for any such reliance. No product provider, test laboratory or other third party may refer to a product, service or facility as EMVCo approved, in form or in substance, nor otherwise state or imply that EMVCo (or any agent of EMVCo) has in whole or part approved a product provider, test laboratory or other third party or its products, services, or facilities, except to the extent and subject to the terms, conditions and restrictions expressly set forth in a written agreement with EMVCo, or in an approval letter, compliance certificate or similar document issued by EMVCo. All other references to EMVCo approval are strictly prohibited by EMVCo. Under no circumstances should EMVCo approvals, when granted, be construed to imply any endorsement or warranty regarding the security, functionality, quality, or performance of any particular product or service, and no party shall state or imply anything to the contrary. EMVCo specifically disclaims any and all representations and warranties with respect to products that have received evaluations or approvals, and to the evaluation process generally, including, without limitation, any implied warranties of merchantability, fitness for purpose or noninfringement. All warranties, rights and remedies relating to products and services that have undergone evaluation by EMVCo are provided solely by the parties selling or otherwise providing such products or services, and not by EMVCo, and EMVCo will have no liability whatsoever in connection with such products and services. This document is provided "AS IS" without warranties of any kind, and EMVCo neither assumes nor accepts any liability for any errors or omissions contained in this document. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT, AS TO THIS DOCUMENT. EMVCo makes no representations or warranties with respect to intellectual property rights of any third parties in or in relation to this document. EMVCo undertakes no responsibility to determine whether any implementation of this document may violate, infringe, or otherwise exercise the patent, copyright, trademark, trade secret, know-how, or other intellectual property rights of third parties, and thus any person who implements any part of this document should consult an intellectual property attorney before any such implementation. Without limiting the foregoing, this document may provide for the use of public key encryption and other technology, which may be the subject matter of patents in several countries. Any party seeking to implement this document is solely responsible for determining whether its activities require a license to any such technology, including for patents on public key encryption technology. EMVCo shall not be liable under any theory for any party's infringement of any intellectual property rights in connection with this document. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page ii / v Revision Log – Version 3.2a.r The following changes have been made to the document since the publication of version 3.2a (March 2023). 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. • Editorial updates © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page iii / v Contents 1 Introduction 1 1.1 Audience 1 1.2 Normative references 2 1.2.1 EMV Specifications 2 1.2.2 PCD Level 1 Type Approval Documents 2 1.3 Definitions 3 1.4 Notational conventions 6 1.4.1 Abbreviations 6 1.4.2 Terminology & conventions 6 2 PCD Type Approval Overview 7 2.1 Scope of PCD Type Approval 7 2.2 PCD Type Approval Life Cycle Concept 8 2.2.1 PCD Life Cycle and Type Approval Milestones 8 2.2.1.1 Design Phase 8 2.2.1.2 Debugging Phase 8 2.2.1.3 PCD Type Approval Phase 8 2.2.1.4 PCD approval Renewal Phase 9 2.2.1.5 Restricted Renewal Phase. 9 2.2.1.6 End of Design Life 9 2.3 EMVCo Contactless Approach 10 2.4 EMVCo Contactless Terminal Type Approvals Description 10 2.4.1 Contactless Product Definition 10 2.4.2 EMVCo Contactless Product Type Approval Processes Overview 16 2.4.2.1 General: Registration and Contract 17 2.4.2.2 PCD Type Approval 17 2.4.2.3 IFM Contact Type Approval 17 2.4.2.4 L2 kernel Contact Approval 17 2.4.2.5 Contactless Product Approval 17 2.5 ICS Submission rules 18 2.5.1 ICS Submission 18 2.5.2 ICS replacement 18 2.6 EMVCo Type Approval fee structure 19 3 Roles and responsibilities 20 3.1 EMVCo 20 3.2 EMVCo CATA Secretariat 21 3.3 Test Laboratory 21 3.3.1 Multiple Test Laboratories 22 © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r 3.4 Auditor Team 3.5 Product Provider 4 PCD Type Approval Procedure 4.1 Registration 4.1.1 EMVCo Registration 4.1.2 EMVCo Contract 4.2 PCD Type Approval Test 4.2.1 Product Provider / Test Laboratory contract 4.2.2 Samples and ICS submission 4.2.3 Analogue and Digital Tests 4.2.3.1 Analogue Test 4.2.3.2 Digital Test 4.2.3.3 Interoperability Test 4.2.4 Type Approval Test Report 4.3 Product Provider Preparation for Approval Request 4.3.1 Product Provider decision on submission to EMVCo for review 4.3.2 Submission to Review 4.4 Product Provider Dossier 4.5 EMVCo Review and Approval 4.6 Type Approval Renewal Process 4.6.1 Renewal Test Plan 4.6.2 PCD Late Renewal. 4.6.3 Anticipated Renewal. 4.6.4 Restricted Renewal 4.6.5 Test Laboratory for renewal testing 4.6.6 ICS Submission 5 Test Version and Specification Change 5.1 Test Changes without EMV Specifications change 5.2 Test Changes Due to EMV Specifications change 6 PCD Change Management 6.1 PCD changes 6.1.1 Minor and major PCD changes 6.1.2 PCD change and PCD Type Approval Level 1 need 6.2 Change of Name and Address 6.3 Re-Issuance of LoA 7 Appendix Page iv / v 22 22 23 24 24 24 25 25 26 27 27 27 27 28 29 29 29 30 31 33 33 33 34 34 34 34 36 36 37 39 40 40 40 41 41 42 © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page v / v © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 1 / 42 1 Introduction EMVCo, LLC (“EMVCo”) is the owner of the EMV Level 1 Specifications for Payment Systems ― EMV Contactless Interface Specification, hereinafter called the EMV Specifications. EMVCo’s objective in establishing the Type Approval Process described in this document is to create a limited mechanism for testing Proximity Coupling Devices (PCDs) used in proximity integrated circuit chip card terminals for sufficient conformance with the EMV Specifications for their stated purpose as of the date of such testing, subject to all of the limitations and restrictions of the Type Approval Process set forth herein. 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. This document describes the overall contactless Terminal Level 1 Type Approval Process and the templates and forms to be completed by the participants in the process. 1.1 Audience The target audience of this document includes: • Product Provider • Testing laboratories recognised to perform the type approval tests • Auditors qualified by EMVCo to evaluate testing laboratories for EMVCo recognition © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r 1.2 Normative references Page 2 / 42 1.2.1 EMV Specifications Table 1-1: EMV Specifications Reference Publication Name Version [L1 SPEC] EMV Level 1 Specifications for Payment Systems ― Version 3.2, EMV Contactless Interface Specification July 2022 EMV Specification Bulletin No 282: PPS0 and PPS1 First Edition, RFU Value Handling March 2023 EMV Specification Bulletin No 283: PCD Carrier Phase Drift First Edition, March 2023 EMV Specification Bulletin No. 300 – PICC Presence First Edition, Check Procedure June 2024 EMV Specification Bulletin No. 303 Adding an Optional Suspend and a Mandatory Suspend in the Polling Loop Second Edition, May 2024 1.2.2 PCD Level 1 Type Approval Documents Table 1-2: PCD Level 1 Type Approval Documents Reference Publication Name Version EMV Contactless Terminal Level 1 Type Approval – Version 3.2a, PCD Analogue Test Bench and Test Case January 2025 Requirements EMV Contactless Terminal Level 1 Type Approval – Version 3.2a, PCD Digital Test Cases January 2025 EMV Contactless Terminal Level 1 Type Approval – Version 3.2a, Device Test Environment January 2025 EMV Terminal Type Approval Bulletin 185: Terminal Latest version Type Approval Fees available [PCDL1 ITR] EMV Terminal Type Approval – Interoperability Latest version Testing Requirement available © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 3 / 42 1.3 Definitions The following terms are used in this specification: Table 1-3: Definitions Term Analogue Test Card Reader Fully Integrated Terminal Intelligent Card Reader Contactless Product Transparent Card Reader Device Test Environment Device Under Test (DUT) Digital Test EMV Kernel EMV Specifications EMVCo Entry Point Definition Set of tests that checks the Radio Frequency characteristics of the hardware and software/firmware of the PCD against the EMV Specifications. Reader, to be connected to a Terminal, to allow the Terminal to perform a financial transaction, when the Terminal does not embed the implementation(s) needed for its intended use. Terminal embedding a PCD, Entry Point and POS System Architecture according to Book A & B, and EMV Kernel(s) according to Book C-1 to C-4. Card Reader, embedding a PCD, Entry Point and POS System Architecture according to Book A & B and EMV Kernel(s) according to Book C-1 to C-4. Components can be either all in the reader (Single Component ICR) or only part of component can be present (Multiple Component ICR). The final product according to definition of section 4.2.2 for Product Approval. This Contactless Product contains the PCD concerned by the present Level 1 Approval Process. Card Reader, embedding a PCD, but no Entry Point and no EMV Kernel(s). Part of the Test Environment needed to perform the Type Approval Test, which the Product Provider needs to develop and submit to the Test Laboratory at the same time as the Samples. Sample within which the PCD submitted for Type Approval is actually tested. Defined set of tests that checks the software responsible for the data exchange between PICC and PCD against the EMV Specifications. Software module that is developed for exclusive support of the EMV contactless debit/credit functions requirements according to EMV Book C-1 to C-4. Set of documents defining the requirements, which the PCD shall comply with for PCD Type Approval (and listed in the “Normative References” section of the PCD Type Approval Administrative Process document). The organization that manages the EMV Specifications and their related testing processes. Software module according to Book A, that is developed for protocol activation and deactivation as well as for selection of an EMV Kernel. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 4 / 42 Environment Implementation Conformance Statement (ICS) Interoperability Testing Landing Plane Loop-Back Application Major Modification Minor Modification Operating System (OS) Operating Volume PCD Letter of Approval (LoA) PCD Type Approval PCD Type Approval Documentation PCD Type Approval Process PCD Under Test Product Provider Proximity Coupling Device (PCD) Part(s) of the product constituted of components that are not part of the PCD - as they are not involved in PCD functionality - but interface with the PCD (for example used by, connected to,..) or have a direct impact on the behavior of the PCD. Form completed by the Product Provider identifying the PCD implementation and to be submitted to the Test Laboratory along with the Samples. A set of tests to assess the capability of the PCD product to perform a transaction when presented to a number of different PICCs. The identified area where a cardholder must ‘tap’ their contactless card or device to achieve a successful read. Test application that the Product Provider needs to develop and implement in the Device Test Environment. Technical change to a characteristic of the PCD – or of the product embedding it – which can potentially change its Conformance. Technical change to a characteristic of the PCD – or of the product embedding it – which cannot potentially change its Conformance. Set of software components allowing the PCD software/firmware 3-dimensional space in which the PCD can communicate with a PICC by means of a magnetic field. Written statement that documents the decision of EMVCo that a specified PCD implemented within a specified Contactless Product has demonstrated sufficient conformance to the EMV Specifications on the date of testing. Acknowledgment by EMVCo that a specified PCD within a specified Contactless Product has demonstrated sufficient conformance to the EMV Specification. Set of documents and procedures issued by EMVCo to enable the PCD Type Approval Process. Steps necessary for a PCD to obtain an EMVCo Letter Of Approval. PCD embedded in the Sample that is actually tested during Type Approval Test. Entity that submits the PCD for PCD Type Approval. Peripheral device of the terminal, that uses inductive coupling to provide power to the PICC and also to control the data exchange with the PICC, up to the transport layer (included), as specified in the EMV Specifications. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 5 / 42 Proximity IC Card (PICC) Registration Number Renewal Request for approval Restricted Renewal Sample Terminal Terminal Main Loop Test Test Bench Test Case Test Environment Test Laboratory (or Testing Laboratory or Laboratory) Test Report Card of the ID-1 form factor (as defined in ISO/IEC 7810) or other form factor into which integrated circuit(s) and coupling means have been placed and in which communication to such integrated circuit(s) is done by inductive coupling in proximity of a coupling device. Unique identification number assigned by EMVCo to a Product Provider. Extension given to the PCD Approval at the end of its validity date after evaluation that the specified product has demonstrated sufficient conformance to the current EMV specification at the time of the renewal. Form that accompanies the PCD submission to EMVCo for PCD Type Approval. Extension given to the PCD Approval at the end of its validity date, after failing Renewal testing. The specified product has demonstrated sufficient conformance to current critical EMV functionality at the time of the Renewal. Contactless Product, including the PCD to be submitted to Type Approval, picked out of production for testing. Device used at the point of transaction to perform a financial transaction and incorporating the host communication. It may also include other components and interfaces (e.g. PCD, Entry Point, Application kernel...). Highest control flow of the terminal which waits for and dispatches events during an EMV Contactless transaction using the functionality located in the PCD. Any activity that aims at verifying the conformance of a selected product or process to a given requirement under a given set of conditions. Defined combination of a set of test methods and test equipment used when performing a Test and owned by the Test Laboratory. Description of the actions required to achieve a specific Test objective. Environment needed to perform the Test. It is constituted of a Test Bench in combination with a Device Test Environment for PCD Type Approval Test. Facility recognised by EMVCo to perform PCD Type Approval Test. Document provided by the Test Laboratory containing the Test results. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r 1.4 Notational conventions 1.4.1 Abbreviations The abbreviations listed in Table 1-4 are used in this specification. Table 1-4: Abbreviations Abbreviation Description ICS Implementation Conformance Statement DUT Device Under Test LoA Letter of Approval OS Operating System PCD Proximity Coupling Devices Page 6 / 42 1.4.2 Terminology & conventions The following words are used often in this specification and have a specific meaning: Shall Defines a product or system capability which is mandatory. 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. The following conventions apply: Requirement Numbering Requirements in this specification are uniquely numbered with the number appearing next to each requirement: For example: 5.4.2.1Example The PCD shall verify the BCC included in the UID CLn. The PCD shall consider an incorrect BCC as a transmission error. A requirement may have different numbers in different versions of the specifications. Hence, all references to a requirement should include the version of the specification as well as the requirement’s number. Requirements may include informative statements. In this case the statement is written in the italic font and the verb ‘may’ instead of ‘shall’ is used © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 7 / 42 2 PCD Type Approval Overview The following sections identify the scope of PCD Type Approval, the PCD Type Approval Procedure as well as Roles and Responsibilities. 2.1 Scope of PCD Type Approval EMVCo PCD Type Approval establishes an increased level of confidence that Product Providers have understood and can successfully implement the EMV Specifications. The component(s) supporting the functionality required by the EMV Specifications (as defined in the scope section 1) is called the Proximity Coupling Device (PCD). The Product Provider is required to identify the PCD and assign it a unique label according to the Product Provider’s naming conventions. Note: Contactless Product architecture, identification and version control (naming) is outside the scope of the EMV Specifications. The scope of EMVCo’s PCD Level 1 testing is: • Testing the minimum functionality that the PCD should support to comply with EMV Level 1 Specifications for Payment Systems ― EMV Contactless Interface Specification. • Testing the communication behaviour of the PCD with a pool of reference PICCs: o Validation at a single position with the PICCs o Interoperability at numerous positions within the operating volume on all PICCs of the pool using a robot. Refer to [PCDL1 ITR] for a description of the Interoperability test requirements. Product Providers submit their card acceptance device (Terminal or Card Reader with embedded PCD) with the necessary Device Test Environment and appropriate documentation, including the Implementation Conformance Statement (ICS), to an EMVCo recognised Test Laboratory for testing. The Test Laboratory executes a set of EMVCo defined Test Cases and prepares a test result document for the Product Providers that may then be submitted to EMVCo for evaluation. EMVCo’s evaluation of the test results concludes with the issuance of Letter of Approval or decline notification. Approval, when granted, applies to the Product Provider–supplied EMV PCD identification. • Major changes or additions to the PCD create a new unapproved PCD that requires retesting and approval before EMV compliance can be claimed. • Common industry practice requires Product Providers to accommodate local acquirer requirements in their card acceptance devices. These acquirer requirements are outside of scope for EMVCo Type Approval. EMVCo limits Type Approval to the EMV PCD as tested in the submitted card acceptance device, 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 Specifications functionality in the integrated acquiring environment. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 8 / 42 2.2 PCD Type Approval Life Cycle Concept The following sections identify the PCD Type Approval life cycle which is a logical concept regarding the design and key approval milestones of a PCD. 2.2.1 PCD 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 PCD Life cycle. Product/PCD design Debugging Figure 2-1: Life cycle of a PCD EMVCo PCD Approval *with representative Sample Approval duration EMVCo PCD Approval Renewal Renewal duration EMVCo PCD Approval Renewal Start of design phase End of debugging phase : Out of scope of EMVCo PCD Approval Start of production phase End of first approval Start of renewed approval 2.2.1.1 Design Phase The PCD is developed by an entity directly related to the PCD or terminal provider and/or the manufacturer of the PCD(s). Most importantly, PCD design and development must be in accordance with the EMV Specifications, as well as any other applicable specifications (e.g. government standards). 2.2.1.2 Debugging Phase The PCD design is checked and tested against all related specifications. EMVCo recommends that conformance testing against the EMV Specifications is conducted on the representative Sample before proceeding to Type Approval, preferably with tools equivalent to those used for Type Approval tests. Before starting production, implementations of the PCD type must be submitted for Type Approval tests to demonstrate conformance with the required specifications. The Product Provider must identify which options its PCD design has incorporated from the EMV Specifications and gather the information to be submitted in the PCD Type Approval Process. 2.2.1.3 PCD Type Approval Phase EMVCo assesses conformance of the PCD design against the EMV Specifications. To determine conformance, identified implementations of the PCD type must undergo predefined tests in a specified test environment (Test Laboratory). The Samples submitted to Test Laboratory must be representative of final product. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 9 / 42 After the PCD Letter of Approval has been granted, it is valid as long as the following applies: • The design and implementation of the PCD within the Contactless Product embedding it is the same in production as it was within the Samples, which was tested and approved. • The approval is not revoked by EMVCo. • The renewal date is not past. • No non-conformance is found at the Contactless Product testing which impacts the PCD conformance. Any change in the Contactless Product design or any re-use of the PCD in another Contactless Product, as specified in the section titled “PCD change management” of this document, may also impact the PCD compliance. PCD approval in this new or modified product is not presumed. 2.2.1.4 PCD approval Renewal Phase Prior to the Renewal date, Product Providers may request a Renewal by submitting the originally approved product to EMVCo for Renewal testing. The purpose of this Renewal testing is to assure that these products pass the most current EMVCo testing. By passing the Renewal test, the product will receive an extension to the Letter of Approval. Products not passing Renewal testing can apply for a Restricted Renewal. Alternatively, after the Renewal date, they will be removed from the approved products list, and their Letter of Approval will be considered revoked. Should there be a case where a product reaches its Renewal date without any applicable test plan updates, such products will be issued an extension to their Letter of Approval. Note: See also section 4.6.2 for Late Renewal requests. 2.2.1.5 Restricted Renewal Phase. Products which fail Renewal testing are eligible to apply for a one-time Restricted Renewal. The failed test case results from the product’s Renewal test session can be submitted for a Restricted Renewal approval. A product which demonstrates sufficient conformance to critical EMV functionality will be assigned a Restricted Renewal and listed as such on the EMVCo website on a dedicated list. Products not passing Restricted Renewal testing will be removed from the approved products list, and their Letter of Approval will be considered revoked, after the Renewal date. Only products which have previously failed Renewal testing will be considered for a Restricted Renewal. A product having already been approved for a 4-year extension as a Restricted Renewal will not be eligible to apply for a further Restricted Renewal. 2.2.1.6 End of Design Life The end of the design life of an approved PCD type is reached when production of that type is finally stopped. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 10 / 42 2.3 EMVCo Contactless Approach EMVCo Contactless 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 Test Laboratory for testing. The Test 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. Note: The integration of an OEM product into a final Product may impact its analogue performances. As a result, EMVCo does not approve OEM products, each final implementation of an OEM product shall be separately submitted to EMVCo Type Approval. 2.4 EMVCo Contactless Terminal Type Approvals Description 2.4.1 Contactless Product Definition This section defines the Contactless Product definitions that Product Provider can implement, based on the POS System defined in Book A. A POS System 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 basic functions of the POS System include: • communication with contactless cards. • application selection and kernel activation. • displaying messages to the cardholder. • displaying messages to the merchant. • accepting merchant data entry of the transaction amount. • cardholder verification (e.g. signature). • provision of online connections. • provision of data capture for clearing and settlement. • Additionally, Entry Point and Kernels C-1 to C-4 shall be located in the POS System. The physical architecture of the POS System can be any of the following, according to Book A definition: • Fully integrated terminal ‘FIT’: All elements included in a single device. • Intelligent card reader ‘ICR’: 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, while kernels and other processes are in the terminal. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 11 / 42 1/ Fully Integrated Terminal (FIT): All elements of POS System included in a single device. Figure 2-2: Fully Integrated Terminal The FIT includes: • Level 1 Contactless PCD according to [L1 SPEC]. • Entry Point and POS System Architecture according to Book A and B • EMV Kernels according to Book C-1 to C-7 including: • Kernel transactions flow, o Kernel functions o EMV data management, o Cryptography, o …. • Consumer & merchant interface(s). • If present, the contact and mag stripe part of the FIT: o IFM (L1), o EMV contact Kernel (L2), • Acquiring Network interface. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 12 / 42 2/ Intelligent Card Reader (ICR), the reader handles most of the contactless transaction processing, transmitting the results for completion to the terminal, where two implementations are possible: 2.1/ Single Component ICR (S-ICR), where all EMV components (EMV requirements defined in Book A, B, C and [L1 SPEC]) are in the reader. Figure 2-3: Single Component ICR (example 1) Figure 2-4: Single Component ICR (example 2) The ICR includes: • Level 1 Contactless PCD according to [L1 SPEC]. • Entry Point and POS System Architecture according to Book A and B. • EMV Kernels according to Book C-1 to C-7 including: o Kernel transactions flow, o Kernel functions © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 13 / 42 o EMV data management, o Cryptography, o …. • If present, the contact part of the ICR: o IFM (L1), o EMV contact Kernel (L2), 2.2/ Multi Component ICR (M-ICR): In this second case, The M-ICR contains most of the EMV components (EMV requirements defined in Book A, B, C and [L1 SPEC]) are in the reader. Figure 2-5: Multiple Component ICR (example 1) Figure 2-6: Multiple Component ICR (example 2) © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 14 / 42 The ICR include: • A valid Level 1 Contactless PCD with an EMVCo Letter of Approval according to [L1 SPEC]. • Part of Entry Point and POS System Architecture according to Book A and B • Part of EMV Kernels according to Book C-1 to C-7 • If present, the contact part of the ICR: o IFM (L1) o EMV Contact Kernel (L2) 3/ Combination of terminal and transparent card reader: The reader provides communication with the card, while kernels and other processes are in the terminal: Figure 2-7: Transparent Reader Combination (example 1) © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Figure 2-8: Transparent Reader Combination (example 2) Page 15 / 42 Note: In case the reader contains the PCD L1 Hardware and analogue, and if the PCD L1 Digital software is not present in the reader but in the terminal, then the Product is considered as a Fully Integrated Terminal (FIT). © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 16 / 42 2.4.2 EMVCo Contactless Product Type Approval Processes Overview The present document focuses on the PCD Level 1 Type Approval only. This section is for information on the overall Contactless Product Type Approval. EMVCo Contactless Product Type Approval is a process that tests a Contactless Product for compliance with the full set of EMV specifications (Book A, Book B, Book C & [L1 SPEC]). This section and Figure 2-9 overview the EMVCo Contactless Product Type Approval Processes. Figure 2-9: Process overview © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 17 / 42 2.4.2.1 General: Registration and Contract Product Provider registration and contract(s) are required to start Type Approval. Registration Number and contract(s) document will be sent by EMVCo Type Approval Secretariat upon receiving the registration request form. The registration is valid for all EMVCo Type Approval processes. 2.4.2.2 PCD Type Approval PCD testing is designed to test the acceptance functionality, Analogue and digital interfaces of the PCD. 1. Analogue Test: to check the Radio Frequency of hardware and firmware 2. Digital Test: to check data exchange between PICC and PCD 3. Interoperability Test: To test PCD using PICCs that are sufficiently representative of the ones deployed in the field The PCD Letter of Approval (PCD LoA) is provisional. Indeed today, some PCD requirements can only be tested once EMV Kernel(s) are present. Therefore, EMVCo retains the right to revoke a PCD LoA if problems relating to the PCD are found during Contactless Product Approval. Further information for PCD Type Approval will be described in the following sections of this document. 2.4.2.3 IFM Contact Type Approval In case that the Contactless Product contains a contact IFM, the IFM shall follow the Contact L1 Type Approval as detailed in the EMVCo Terminal Type Approval – IFM Level 1 Administrative Process document, latest version. 2.4.2.4 L2 kernel Contact Approval In case that the Contactless Product contains a contact Level 2 kernel, the kernel shall follow the L2 Contact Type Approval as detailed in the EMVCo Type Approval – Terminal Level 2 Administrative Process document, latest version. 2.4.2.5 Contactless Product Approval The overall Contactless Product Approval is detailed in the EMVCo Type Approval – Contactless Product Administrative Process document, latest version. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 18 / 42 2.5 ICS Submission rules 2.5.1 ICS Submission • The initial ICS submission to the EMVCo is free of charge. • 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 Test Laboratory at the time of submission to EMVCo. • The Test Laboratory supplies the signed copy of the Product Provider-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 Test Laboratory. • ICS submission shall be always 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.5.2 ICS replacement • One free ICS replacement is allowed during the ICS life cycle. Any subsequent ICS replacement requested will be charged to the Product Provider. • Same submission process applies as for initial ICS submission (Test 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 are not allowed for technical information update. • Test Laboratory shall ensure that any ICS change requested is not made to hide a bug in the product (such as deactivation of 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 Test Laboratory (as Test 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): © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r 2.6 EMVCo Type Approval fee structure The following fee structure is applicable: • Initial Submission • ICS Replacement (starting at 2nd Replacement) • Renewal • Declined ICS/Report (Test Laboratory fee) • LoA reissuance Page 19 / 42 Note: The amount of each fees is published in Terminal Type Approval Bulletin 185. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 20 / 42 3 Roles and responsibilities The following sections define the roles and responsibilities for the various participants in the Type Approval Process. 3.1 EMVCo EMVCo defines Type Approval requirements and evaluates operational results. EMVCo provides the following services: • Defines mandatory auditor qualification requirements. • Qualifies organizations that perform audits to establish Test Laboratory recognition. • Defines mandatory Test Laboratory recognition requirements. • Sets Test Laboratory audit time frame. • Defines PICCs to the Test Laboratories for the Interoperability tests. • Manages Test Laboratory appeals process and resolves recognition disputes based on the statement of L1 contract. • Determines the applicability of the EMV Specification and associated test requirements. • Evaluates PCD Type Approval summary results to determine if approval requests should be granted or not. • Notifies appropriate EMVCo working group of warranted specification corrections, clarifications, and enhancements that result from the conditional approval process. • Evaluates terminal and card failure complaints to determine if Type Approval revocation is appropriate. • Maintain and publishes (via EMVCo website) a list of PCD that have received EMVCo Type Approval notification. • EMVCo Terminal Type Approval Secretariat. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 21 / 42 3.2 EMVCo CATA Secretariat The EMVCo CATA secretariat is responsible for communicating Type Approval status to third parties and for the administration and maintenance of a database that provides the following: • Qualified auditor list • Recognised Test Laboratory list • Type Approval test requirements • Issue PCD approval letters • Approved PCD list 3.3 Test Laboratory The Test Laboratory is an entity recognised by EMVCo to conduct testing of PCD(s) in accordance with the Type Approval test requirements and Test Cases. The Test Laboratory must: • Apply to EMVCo for recognition. • Conduct testing in accordance with EMVCo’s PCD Level 1 Type Approval requirements and with EMVCo qualified Test Tools. • Validate that the Implementation Conformance Statement (ICS) is complete and all sections and fields are consistent. • Send the ICS to EMVCo • Begin testing a product only after receiving EMVCo’s acceptance of the Product’s ICS • Ensure that, if any modification is made to the PCD during the test session, a new test session is initiated with a new ICS accepted by EMVCo. • Ensure that any ICS change requested is not made to hide a bug in the product (such as deactivation of a function because this function is not working properly). • Identify in the test report the reason for any modification made to the ICS during the test session (without any modification to the product). • Identify in the test report any discrepancy found during the test session, either failure of a test or non-conformance to the specification. • Issue test reports in an electronic format as defined by EMVCo. • Be able to conduct testing for all Test Cases defined by EMVCo for the Level 1 evaluations. • Maintain the pool of PICCs used for Interoperability testing. • Provide a quarterly report of testing activities and performance to EMVCo. • Maintain EMVCo recognition. • Apply for Renewal of recognition before the expiration of their Letter of Recognition. • Notify EMVCo of any change in contact information, as described in section 6.2. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 22 / 42 It is the responsibility of the Test Laboratory to ensure that its staff members are properly trained on Test Tools, EMV Specifications and other testing requirements. It is not the responsibility of EMVCo to provide training. Payment of fees for testing tasks undertaken by EMVCo recognised Laboratories is the responsibility of the Product Provider requesting EMVCo’s approval. EMVCo is not responsible for Test Laboratory testing fees. 3.3.1 Multiple Test Laboratories Level 1 testing can be split between different EMVCo recognised Test Laboratories. When this is the case the following rules shall apply: • A single Test Laboratory is responsible for the Level 1 testing (primary laboratory). o The primary Test Laboratory may subcontract some testing to other laboratories (subcontracted laboratories) o The primary Test Laboratory submits the ICS to EMVCo. o In case of ICS issue, fees will only be applied to the primary Test Laboratory o The primary Test Laboratory shall sign and submit to EMVCo all test reports o The subcontracted Test Laboratories shall follow EMV rules. o The primary Test Laboratory will be responsible for subcontracted Test Laboratories defects and may require additional audit. o The primary Test Laboratory shall document the subcontracted work into the test report • When testing is conducted at multiple Test Laboratories, all test reports received must contain the same version number of the EMV application(s), operating system, and environment. • All rules regarding the samples shall be maintained. All samples at all Test Laboratories are for the same version of the ICS. The reports shall clearly indicate which samples were tested at each Test Laboratory. Note: EMVCo’s expectation is that an EMVCo recognised Test Laboratory has to provide all services required to fully test a product. By opening to multi-lab model, EMVCo intends to provide with some flexibility to address specific and temporary situations (exceptional workload, test tool breakdown, new facility). 3.4 Auditor Team The auditor team comprises the person(s) in charge of conducting audits on behalf of EMVCo. 3.5 Product Provider The Product Provider is the entity responsible for submitting Contactless Product embedding PCD for Type Approval in compliance with PCD Type Approval procedures. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 23 / 42 4 PCD Type Approval Procedure This section describes the PCD Type Approval procedure to be followed by Product Providers, laboratories, and EMVCo. Figure below shows the diagram of PCD Type Approval procedure. Figure 4-1: PCD Type Approval Procedure © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 24 / 42 4.1 Registration 4.1.1 EMVCo Registration Registration provides the Product Provider with entry into the approval process for when the Product Provider wants to submit their final Type Approval Test Report to EMVCo for approval. This registration is valid for all other EMVCo Type Approval Processes including Contactless Product Type Approval, Contact Level 1 Type Approval and Contact Level 2 Type Approval. The registration process is composed of the following steps: • The Product Provider submits a registration request to the EMVCo Type Approval Secretariat. • Registration request document shall be sent to the EMVCo Type Approval Secretariat in pdf format (unlocked to ensure that copy and paste of information are possible) electronically signed. Scanned copies are not allowed. • 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.1.2 EMVCo Contract The Product Provider must complete and sign the EMVCo defined contract. The contract has to be signed with EMVCo prior to submission of product test report. Product Provider must submit the contract, if not already signed. This contract stipulates, amongst other provisions, the Product Provider’s acceptance of all specifications, procedures, terms and conditions governing EMVCo PCD Type Approval. The contract is standard for all Product Providers to help ensure consistent requirements for all participants. Contract customization for individual Product Providers is not acceptable. Please visit EMVCo website to download the documents you need. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 25 / 42 4.2 PCD Type Approval Test The following operations shall be performed by the Product Provider and by the Test Laboratory in the Type Approval procedure: • The Product Provider is free to select any EMVCo recognised Test Laboratory for the purpose of achieving EMVCo Type Approval. The Product Provider and Test Laboratory shall execute a contract defining appropriate rights and obligations. At a minimum, the contract shall contain the requirements listed in the following section. • Product Provider sends an Implementation Conformance Statement (ICS) to the chosen Test Laboratory for each implementation under test (IUT) that it submits. The ICS format and content requirements are determined by EMVCo. The ICS submitted must be the ICS in pdf format, and shall be digitally signed by the Product Provider at the time of submission to EMVCo. • The Test Laboratory supplies a copy of the Product Provider-supplied ICS to EMVCo for review prior to the start of the Type Approval testing process, digitally signed by the Product Provider and by the Test Laboratory: o As result EMVCo provides a unique ICS Reference Number Product Provider and the Test Laboratory must discuss PCD software requirements in order for the Test Laboratory to execute the EMVCo Type Approval test. • The Test Laboratory shall test the terminal in accordance with EMVCo test procedures. • Testing shall be performed in Test Laboratory premises with the complete solution samples located in these premises. • The Product Provider prepares the Request For Approval form and submits it to EMVCo. EMVCo can then issue the invoice for the Product Provider. RFA can be sent only after the ICS has been approved by EMVCo. • Product Provider submits payment to EMVCo based on the received invoice. • The Test Laboratory shall send the final test report to the Product Provider for approval before official submission to EMVCo. • When agreed by the Product Provider, the Test Laboratory shall submit the Type Approval Test Report to EMVCo, and ensures Product Provider has already submitted his completed Request For Approval form. Note: An Approved ICS is valid 6 months. If the related Request For Approval 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 will not be reimbursed. Note: If the test session has not started yet and the ICS already been approved, when a new EMVCo release of the ICS published (I.e. after the migration period when applicable), then the ICS shall be resubmitted with new latest ICS version before Test Laboratory can submit the report. 4.2.1 Product Provider / Test Laboratory contract The Product Provider selects and contacts an EMVCo- recognised Test Laboratory. The Product Provider is free to select any EMVCo- recognised Test Laboratory for the purpose of © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 26 / 42 achieving EMVCo PCD Type Approval. A list of recognised laboratories is published on the EMVCo website. Once a Test Laboratory is selected, the Product Provider and Testing Laboratory shall execute a contract defining individual rights and obligations of the contracting parties. The provisions of Product Provider/Test Laboratory contract are up to the contracting entities and entirely out of scope of EMVCo. Any fees payable to the Test Laboratory in respect of the tests to be conducted are solely at the discretion of the Test Laboratory. Note: Topics likely to be included in the contract between Testing Laboratories and Product Providers are mentioned below for information purposes only. • Any Test Laboratory requirements needed for testing including any software application required interfacing with the Test Laboratory test equipment. Within the EMVCo documents this is referred to as an Upper Tester. • Reference to the contract between the Product Provider and EMVCo • Agreement of mutual cooperation in providing needed information and assistance • Lead time for the execution of the Type Approval tests • The number of Samples for testing (minimum three) • Arrangement for the preparation and delivery of Samples • Right to keep all Samples for the duration of the test procedure • Right to keep all approved samples for a period of the LoA validity + 1 year. Note: samples are retained for subsequent testing purposes and the Product Provider must provide the necessary support to the Test Laboratory to ensure the PCD remains fully functional. • Recognition that no infringement on the independence or impartiality of the Test Laboratory will be allowed during or after testing • Agreement on the boundaries of use of the test report • Provisions for conflict resolution • Maintaining the Samples at the Test Laboratory during EMVCo evaluation of test results. • Maintaining the Samples while the PCD is EMV approved. 4.2.2 Samples and ICS submission The Product Provider shall send to the chosen Test Laboratory: • A signed Implementation Conformance Statement (ICS) for the PCD type that it submits. • The ICS format and content requirements are determined by EMVCo. The latest ICS template at the time of testing must be used. Please visit EMVCo website to download the documents you need. • The agreed number of Samples as defined by the Test Laboratory (minimum three). • Samples presented must: o Have Contactless Symbol at the center of the landing plane as specified in the specifications. o Have a unique check sum for PCD firmware, and unique and specific identification of the PCD hardware. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 27 / 42 o Be submitted along with a Device Testing Environment compliant with requirements described in EMVCo PCD Type Approval Device Test Environment document, i.e. that: ✓ For Analogue Test, allows a number of PCD functions to be accessible in a step-by-step mode. ✓ For Digital Test and part of Analogue Test, implements a Loop Back Application. ✓ For Interoperability Test, implements the Interoperability Loop Back. ✓ Provides a means for the different command/responses to be displayed. (e.g. on the display of a PC). ✓ Includes manual, cables and any necessary PC software (where required). ✓ Includes other components that allow the operation of the PCD if the Contactless Product in which it is embedded does not constitute an operable device alone. o Provide identification of the Landing Plane including the final position of the Contactless Symbol. o Be identical, i.e. there shall be no hardware, firmware or software difference between the samples presented. o Be representative of the final product. 4.2.3 Analogue and Digital Tests The Test Laboratory performs the following tests on the Samples in accordance with EMVCo procedures. These tests respectively confirm the compliance of the electrical characteristics of the power and data exchange between PICC and PCD and the compliance of the digital data exchange between PICC and PCD: 4.2.3.1 Analogue Test Related document “Contactless Terminal Level 1 Type Approval — PCD Analogue Test Bench and Test Cases Requirements” details the tests that a Test Laboratory must perform based on EMV-established requirements (intended for all participants in the PCD Type Approval Process). 4.2.3.2 Digital Test Related document “Contactless Terminal Level 1 Type Approval – PCD Digital Test Cases” details the tests that a Test Laboratory must perform based on EMV-established requirements (intended for all participants in the PCD Type Approval Process). 4.2.3.3 Interoperability Test Related document “Terminal Type Approval PCD Level 1 — Interoperability Testing Requirements” details the tests that a Test Laboratory must perform based on EMVestablished requirements (intended for all participants in the PCD Type Approval Process). Note 1: The PICCs used for the Interoperability tests are restricted to the Test Laboratory. The Test Laboratory shall not disclose the list of PICCs to the Product Providers. An identification number will be allocated to each PICC to identify them in the report. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 28 / 42 Note 2: The same PCD Sample shall be used for Analogue testing and Interoperability testing. Different samples are allowed on digital. 4.2.4 Type Approval Test Report The Test Laboratory provides the Product Provider (owner of the test results) with a signed Test Report in a non-modifiable and electronically signed format. The Test Report, called Test Report for PCD Type Approval includes, at a minimum, the following items: • The unique identification of the Test Report • Test Laboratory information • Tested Product Information o Implementation Conformance Statement Reference Number o Identification of Product Provider o Identification of the Samples o Identification of any other Product Provider equipment or components (e.g. terminal model) submitted to allow testing o Picture of the Sample under test taken by the Test Laboratory • Test method information o EMVCo specification/each Test Case version used for all tests o Interoperability Test Requirement version o Identification of all Test Laboratory testing equipment and software versions used during the tests o Description of the Test Laboratory environmental conditions during testing • Test results information o Dates when tests were performed o The results of Analogue Test o The results of Digital Test o A summary test report for each test including: ✓ Test Case numbers that were executed with a pass or fail indication ✓ A detailed description from the Test Laboratory of failed tests including logs of the test results for each reported discrepancy in the failed test. ✓ A detailed description of any exceptional test(s) performed, equipment utilized and a description of related test results ✓ A detailed description of the PCD modifications that may be required for the purpose of executing the EMVCo Test Cases Note: The Test Laboratory should maintain all test result logs for all Test Cases and make those available for EMVCo review as requested. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 29 / 42 4.3 Product Provider Preparation for Approval Request 4.3.1 Product Provider decision on submission to EMVCo for review The Product Provider determines whether test results resulting from Test Laboratory testing will be submitted to EMVCo for evaluation. • Submitting test results to EMVCo for evaluation indicates Product Provider acceptance that the test results are a true representation of PCD performance. Test results may be submitted to EMVCo for evaluation up to 90 days from the date the PCD was tested. Test results that exceed the 90-days validity period have expired and cannot be submitted. PCD re-testing is required to create a current test report if the validity period is exceeded and EMVCo evaluation is desired. • The Product Provider must ensure that the Samples associated with test results submitted to EMVCo for evaluation remain unaltered and accessible in a timely manner during the evaluation process. It is required that the Samples remain in the possession of the Test Laboratory when test results are submitted to EMVCo until EMVCo has approved or declined the Request For Approval. The Product Provider must ensure that Test Report is ready to be submitted to EMVCo. 4.3.2 Submission to Review To complete the Request For Approval previously sent, the Test Laboratory shall submit to EMVCo an original signed copy or electronic copy digitally signed of the Test Report. Note 1: Product Provider must give consent for the Test Laboratory to submit the Test Report to EMVCo directly. Note 2: This step can be done at the same time as or after the EMVCo fee payment. However, Product Provider shall be aware that EMVCo review will only start once the fee paid. The request for review is considered completed once EMVCo has received: • The Request For Approval form filled-in, including the official name of the Product Provider requesting the approval as well as their registration number. • The complete Test Report received from the Test Laboratory, including the signed copy of the Implementation Conformance Statement (ICS), as submitted by the Product Provider to the Test Laboratory. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 30 / 42 4.4 Product Provider Dossier The dossier submitted to EMVCo will comprise: • A signed copy of the Implementation Conformance Statement (ICS), received from the Test Laboratory • Letter requesting approval (Request For Approval form) received from Product Provider • Product Provider payment • The complete and unchanged Test Report received from the Test Laboratory • Any additional supporting documentation the Product Provider believes is appropriate © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 31 / 42 4.5 EMVCo Review and Approval Upon receiving the dossier and internal validation of the fee payment, EMVCo will: Review the submitted test report (report must be valid at the time of review) and determine if Type Approval should be granted.The PCD Letter of Approval is provisional until Product Approval is granted, meaning Level 1 approval stands by itself, but can be revoked based upon a Level 2 product test. Depending on the decision, EMVCo will: • Issue PCD Letter of Approval, if appropriate (Letter of Approval will only be issued electronically and sent by email) • Provide notification of PCD Type Approval EMV PCD LoA identifies: • The approved PCD name and its two sub-sets: o PCD hardware name, o PCD firmware/software name, • the Contactless Product name in which it was tested, • the EMV Specifications version against which it was tested, • the Interoperability version against which it was tested, • the Renewal date. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r PCD LoA number coding is the following: Figure 4-2: PCD LoA number coding Page 32 / 42 Limitations of the current LoA, e.g.: If the PCD performs a RESET before or after a proprietary polling command of the PCD, the LoA will contain the sentence “EMVCo cannot guarantee interoperability because this PCD provides additional proprietary functionality and features such as polling for other technologies, that are beyond the scope of EMVCo” Note: As described earlier, non-conformance of EMV Specifications requirement may be found during Contactless Product testing. In that case, EMVCo will decide whether the PCD LoA must be removed from the approved PCDs list posted on EMVCo website. Product Provider may need to come back to PCD Type Approval. © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 33 / 42 4.6 Type Approval Renewal Process A PCD approval is valid for 4 years. Every 4 years, EMVCo evaluates whether the product demonstrates sufficient conformance to the current EMV specification. If the evaluation result is positive then EMVCo gives an extension to the PCD Letter of Approval. After the Renewal date, PCDs not passing Renewal testing or Restricted Renewal evaluation will be removed from the approved PCDs list and their Letter of Approval will be considered revoked. Six months before the Renewal date of their Product, EMVCo will send a notification letter to the Product Providers. Upon receipt of this letter, and prior to the Renewal date, Product Providers may request their Renewal by submitting the originally approved product to EMVCo for Renewal testing. Note: Product Providers are not allowed to apply for Renewal testing before receiving the notification letter (except in case of anticipated renewal see section 4.6.3 for more details) . 4.6.1 Renewal Test Plan The set of the Renewal test will be generated based on the newly added and/or modified Test Cases including the new Interoperability PICCs since the older test plan and the Interoperability test requirements the PCD was tested against and the most current test plan and Interoperability test requirements at the time of testing, plus regression testing. The most current test plan reference is the version available at the time of the Type Approval test session. 6 months before the Renewal date, Product Providers may submit the original sample to a Test Laboratory for Renewal Testing. Note: Renewal test session shall be performed using the same sample that was tested during initial Approval. In case of multiple samples used during initial Approval: • The sample used to perform Analogue and Interoperability tests during initial Approval shall be used to perform Analogue and Interoperability Renewal tests. • The sample used to perform Digital tests during initial Approval shall be used to perform Digital Renewal tests. The objective of Renewal testing is to ensure these products pass the most current EMVCo testing. By passing the Renewal testing, the product will receive an extension to the Letter of Approval. . 4.6.2 PCD Late Renewal. Even after the Product expiration, Product Provider may decide to apply for a Late Renewal. All rules of renewal listed in the section 4.6 apply with the following changes: • Late renewal can be requested during the year following the product expiration, • Test Plan version at the date of the ICS submission applies, © 2010-2025 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 PCD Level 1 Administrative Process v3.2a.r Page 34 / 42 • If Late Renewal is granted, LoA will be extended for a duration date of 4 years starting from initial Renewal date (for example in case of Late Renewal started 1 year after expiration of the LoA, the LoA will be valid only 3 years after Late Renewal). Note: As a reminder, Expired Product are removed from the approved products list and their LoA are revoked until Renewal is granted. 4.6.3 PCD Anticipated Renewal. Even before the Product Renewal period, Product Provider may decide to apply for an Anticipated Renewal. All rules of renewal listed in the section 4.6 apply with the following changes: • Anticipated renewal can be requested anytime before the product expiration, up t