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

EMV® Terminal Type Approval Reduced Range PCD Level 1 Administrative Process Version 3.2a.r September 2025 © 2024-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. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page i / iv 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. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page ii / iv Revision Log – Version 3.2a.r The following changes have been made to the document since the publication of version 3.2a: Editorial updates. 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. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page iii / iv Contents 1 Introduction 1 1.1 Audience 1 1.2 Normative references 2 1.2.1 EMV Specifications 2 1.2.2 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 Reduced Range PCD Type Approval Overview 7 3 Reduced Range PCD Type Approval Procedure 8 3.1 Registration 9 3.1.1 EMVCo Registration 9 3.1.2 EMVCo Contract 9 3.2 Reduced Range PCD Type Approval Test 10 3.2.1 Product Provider / Test Laboratory contract 10 3.2.2 Samples and ICS submission rules 11 3.2.2.1 ICS Submission 12 3.2.2.2 ICS replacement 12 3.2.3 Test Procedures 13 3.2.3.1 Analogue Test 13 3.2.3.2 Digital Test 13 3.2.3.3 Interoperability Test 13 3.2.4 Type Approval Test Report 13 3.2.5 json Test Report 14 3.3 Product Provider Preparation for Approval Request 15 3.3.1 Product Provider decision on submission to EMVCo for review 15 3.3.2 Submission to Review 15 3.4 Product Provider Dossier 16 3.5 EMVCo Review and Approval 17 3.5.1 Reduced Range PCD Letter of Approval Types. 17 3.5.2 Reduced Range Letter of Approval information 17 3.5.3 Publication on EMVCo Website 18 3.6 EMVCo Type Approval fee structure 19 4 Change Management 20 4.1 PCD changes 21 4.1.1 Minor and major changes 21 © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page iv / iv 4.1.2 PCD change and Reduced Range PCD Type Approval Level 1 need 21 4.2 Change of Name and Address 22 4.3 Re-Issuance of LoA 22 5 Roles and responsibilities 23 5.1 EMVCo 23 5.2 EMVCo CATA Secretariat 23 5.3 Test Laboratory 24 5.3.1 Multiple Test Laboratories 24 5.4 Auditor Team 25 5.5 Product Provider 25 6 Test Version and Specification Change 26 6.1 Test Changes without EMV Specifications change 26 6.2 Test Changes Due to EMV Specifications change 27 7 Appendix 28 © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 1 / 28 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 mechanism for testing Reduced Range PCD devices 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 on page 2 of this document for important limitations on the scope of type approval. This document describes the overall Contactless Terminal Reduced Range PCD 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 © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r 1.2 Normative references Page 2 / 28 1.2.1 EMV Specifications Table 1-1: EMV Specifications Reference Publication Name Version [L1 SPEC] EMV Level 1 Specifications for Payment Systems ― EMV Contactless Interface Specification Version 3.2, 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 Level 1 Type Approval Documents Table 1-2: PCD Level 1 Type Approval Documents Reference Publication Name Version [PCDL1 ITR] EMV Terminal Type Approval – Interoperability Latest version Testing Requirement available [L1 GDL] EMV Contactless Terminal Level 1 Type Approval – Latest version Reduced Range PCD Level 1 Guidelines available [INTAppReq EMV Contactless Terminal Level 1 Type Approval – Latest version ] Reduced Range Interoperability Test Application available Requirements [L1 DTE] EMV Contactless Terminal Level 1 Type Approval – Latest version Device Test Environment available [TTAB276] EMV Terminal Type Approval Bulletin 276: Reduced Latest version Range Acceptance Criteria available [TTAB185] EMV Terminal Type Approval Bulletin 185: Terminal Latest version Type Approval Fees available © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 3 / 28 1.3 Definitions The following terms are used in this specification: Table 1-3: Definitions Term Definition Analogue Test Set of tests that checks the Radio Frequency characteristics of the hardware and software/firmware of the PCD against the EMV Specifications. Device Test Environment 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. Device Under Test (DUT) Sample within which the PCD submitted for Type Approval is actually tested. Digital Test Defined set of tests that checks the software responsible for the data exchange between PICC and PCD against the EMV Specifications. EMV Specifications 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). EMVCo Organization that manages the EMV specifications and their related testing processes. Environment 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. Implementation Conformance Statement (ICS) Form completed by the Product Provider identifying the PCD implementation and to be submitted to the Test Laboratory along with the Samples. Interoperability Testing A set of tests to assess the capability of the PCD product to perform a transaction when presented to a number of different PICCs. Landing Plane The identified area where a cardholder must ‘tap’ their contactless card or device to achieve a successful read. Loop-Back Application Test application that the Product Provider needs to develop and implement in the Device Test Environment. Major Modification Technical change to a characteristic of the PCD – or of the product embedding it – which can potentially change its Conformance. Minor Modification Technical change to a characteristic of the PCD – or of the product embedding it – which cannot potentially change its Conformance. Operating System Set of software components allowing the PCD software/firmware (OS) Operating Volume 3-dimensional space in which the PCD can communicate with a PICC by means of a magnetic field. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 4 / 28 Reduced Range PCD Letter of Approval (LoA) Reduced Range PCD Type Approval Reduced Range PCD Type Approval Documentation Reduced Range PCD Type Approval Process PCD Under Test Product Provider Proximity Coupling Device (PCD) Proximity IC Card (PICC) PICC Test Pool (PTP) devices Registration Number Request for approval Sample Terminal Test Test Bench Written statement that documents the decision of EMVCo that a specified PCD implemented within a specified Contactless Product has demonstrated sufficient compliance EMVCo requirements 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 Reduced Range PCD Type Approval Process. Steps necessary for a PCD to obtain a Reduced Range PCD Letter Of Approval. PCD embedded in the Sample that is actually tested during Type Approval Test. Entity that submits the PCD for Reduced Range 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. 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. Pool of PICCs used to perform Interoperability tests. This pool is composed of Mobile and ID-1 Cards selected by EMVCo. Unique identification number assigned by EMVCo to a Product Provider. Form that accompanies the PCD submission to EMVCo for Reduced Range PCD Type Approval. 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...). 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. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 5 / 28 Test Case Test Environment Test Laboratory (or Testing Laboratory or Laboratory) Test Report 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 RR Type Approval Test. Facility recognised by EMVCo to perform RR Type Approval Test. Document provided by the Test Laboratory containing the Test results. © 2024-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 Reduced Range 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 DUT Device Under Test ICS Implementation Conformance Statement LoA Letter of Approval OS Operating System PCD Proximity Coupling Devices RR Reduced Range RFA Request For Approval Page 6 / 28 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. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 7 / 28 2 Reduced Range PCD Type Approval Overview The following sections identify the scope of Reduced Range PCD Type Approval, the Type Approval Procedure as well as Roles and Responsibilities. EMVCo Reduced Range PCD Type Approval establishes an increased level of confidence that Product Providers have understood and can sufficiently comply with the EMV Specifications. The component(s) supporting the functionality required by the EMV Specifications (as defined in the scope section 1) is called 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 Reduced Range PCD Level 1 testing is: • Testing the minimum functionality that the PCD product should support to demonstrate sufficient compliance 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 (PTP Devices): Interoperability at numerous positions within the operating volume on all PTP Devices of the pool using a robot. Refer to [L1 GDL] for a description of the Level 1 testing procedures. Product Providers submit their DUT with the necessary Device Test Environment and appropriate documentation, including the Implementation Conformance Statement (ICS), to a 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 product that requires retesting and approval before EMV compliance can be claimed. • Common industry practice requires Product Providers to accommodate local acquirer requirements in their DUT. These acquirer requirements are outside of scope for EMVCo Type Approval. EMVCo limits Type Approval to the EMV PCD as tested in the submitted DUT, 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. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 8 / 28 3 Reduced Range PCD Type Approval Procedure This section describes the Reduced Range PCD Type Approval procedure to be followed by Product Providers, laboratories, and EMVCo. Figure below shows the diagram of Reduced Range PCD Type Approval procedure. Figure 3-1: Reduced Range PCD Type Approval Procedure © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 9 / 28 3.1 Registration 3.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. Product Providers that are already registered for another EMVCo approval process must complete this registration process. The registration process is composed of the following steps: • The Product Provider submits a registration request to the EMVCo Type Approval Secretariat through the EMVCo website. • The Product Provider will receive a confirmation email from EMVCo Type Approval Secretariat with the following additional information: o Link to the EMVCo Test Contracts (DocuSign) o Appropriate contact information • The Product Provider shall sign the EMVCo Test Contracts with DocuSign. • When the EMVCo Test Contracts are countersigned by the EMVCo, the EMVCo Test Contracts are sent back to the Product Provider by DocuSign. • A unique Registration Number is assigned and shared with the Product Provider. Note: If the Product Provider had previously registered for Terminal Type Approval Level 1 (Contact and Contactless), the company Registration Number initially assigned will not change when requesting registration for Reduced Range PCD Type Approval. 3.1.2 EMVCo Contract The Product Provider must complete and sign the EMVCo defined Reduced Range PCD contract. The contract has to be signed with EMVCo prior to submission of product test report. This contract stipulates, amongst other provisions, the Product Provider’s acceptance of all specifications, procedures, terms and conditions governing EMVCo Reduced Range 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. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 10 / 28 3.2 Reduced Range 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 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 product that it submits. Through this ICS the Product Provider selects the compliance level it applies for, either Reduced Range 1 or Reduced Range 2. The format and content requirements of the ICS are determined by 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 Product software requirements in order for the Test Laboratory to execute the EMVCo Type Approval test. • The Test Laboratory shall test the Product 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. 3.2.1 Product Provider / Test Laboratory contract The Product Provider selects and contacts a Test Laboratory. The Product Provider is free to select any Test Laboratory for the purpose of achieving EMVCo Reduced Range 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. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 11 / 28 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 Product 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 Product is EMV approved. 3.2.2 Samples and ICS submission rules The Product Provider shall send to the chosen Test Laboratory: • A signed Implementation Conformance Statement (ICS) for the Product 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 EMVCo (minimum three). • Samples presented must: o Have Reference Mark (as defined in [L1 GDL]) that will be used to define the origin of the Operating Volume as specified in the EMV Specifications. Note: In case the Product is submitted with a Contactless Symbol: o The Contactless Symbol shall be compliant with the EMVCo Contactless Symbol Reproduction Requirements available on EMVCo website. o The Reference Mark is defined as the centre of the Contactless Symbol. o Have unique and specific identification of the PCD hardware and PCD firmware. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 12 / 28 o Be submitted along with a Device Testing Environment compliant with requirements described in [L1 DTE]and in [L1 GDL], 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 Be submitted along with a Reduced Range Interoperability Test Application compliant with requirements defined in [INTAppReq] if the Product does not support the application provided by EMVCo to Testing Laboratories. o Provide identification of the Landing Plane including the position of the origin of the Operating Volume. 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. 3.2.2.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. 3.2.2.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. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 13 / 28 • 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. o Product Provider may decide to change the Type of Product he wants to submit, from RR1 to RR2 or vice versa. This implies an ICS replacement and this change is considered as an administrative information change. • 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): 3.2.3 Test Procedures The Test Laboratory performs the following tests on the Samples in accordance with EMVCo procedures. These tests respectively confirm the compliance with the requirements defined by EMVCo for Reduced Range Products regarding the Analogue and Digital characteristics of data exchange between a PICC and a PCD: 3.2.3.1 Analogue Test [L1 GDL] details the tests that a Test Laboratory must perform based on EMV established requirements (intended for all participants in the Reduced Range Type Approval Process). 3.2.3.2 Digital Test [L1 GDL] details the tests that a Test Laboratory must perform based on EMV established requirements (intended for all participants in the Reduced Range Type Approval Process). 3.2.3.3 Interoperability Test [L1 GDL] details the tests that a Test Laboratory must perform based on EMV established requirements (intended for all participants in the Reduced Range Type Approval Process). Note 1: The PTP Devices used for the Interoperability tests are restricted to the Test Laboratory. The Test Laboratory shall not disclose the list of PTP Devices to the Product Providers. An identification number will be allocated to each PICC to identify them in the report. Note 2: The same sample shall be used for Analogue testing and Interoperability testing. Different samples are allowed on Digital. 3.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 includes, at a minimum, the following items: © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 14 / 28 • 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 • Test method information: o EMVCo specification/each Test Case version used for all tests o Interoperability Test Requirement version o [L1 GDL] 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 Product 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. 3.2.5 json Test Report In addition to Type Approval report the Test Laboratory shall provide EMVCo with an Analogue and an Interoperability json Test Reports compliant with the requirements defined by EMVCo. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 15 / 28 3.3 Product Provider Preparation for Approval Request 3.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 and the type of Letter of Approval requested. Submitting test results to EMVCo for evaluation indicates Product Provider acceptance that the test results are a true representation of Product performance. Test results may be submitted to EMVCo for evaluation up to 90 days from the date of the completion of the product’s Type Approval testing. Test results that exceed the 90-days validity period have expired and cannot be submitted. Product 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. In case of the Request for Approval is accepted, the samples will be detained as stated in section 3.2.1. The Product Provider must ensure that Test Report is ready to be submitted to EMVCo. 3.3.2 Submission to Review To complete the Request For Approval previously sent, the Test Laboratory shall submit to EMVCo a digitally signed 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. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 16 / 28 3.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. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 17 / 28 3.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. Depending on the decision, EMVCo will: • Issue Reduced Range Letter of Approval, if appropriate (Letter of Approval will only be issued electronically and sent by email). • Provide notification of Reduced Range Type Approval. A Reduced Range PCD LoA is valid for 3 years. Note: No renewal is possible for Reduced Range Products. 3.5.1 Reduced Range PCD Letter of Approval Types. EMVCo proposes two types of Reduced Range PCD LoA depending on the performance of the Product: • Reduced Range 1 PCD LoA. • Reduced Range 2 PCD LoA. The type of Reduced Range PCD LoA a Product Provider can apply for depends on the Operating Volume in which its product complies with EMV requirements for Reduced Range Products. The testing procedures to be applied to request Reduced Range PCD LoAs are defined in [L1 GDL]. The criteria to receive a Reduced Range PCD LoA are defined in [TTAB276]. Product Providers can perform pre-testing with Testing Laboratories to define the level of compliance they want to apply for. 3.5.2 Reduced Range Letter of Approval information EMV Product LoA identifies: • The approved PCD name and its two sub-sets: o PCD hardware name, o firmware/software name, • the Contactless Product name in which it was tested, • the EMV Specifications version against which it was tested, • the TTA Bulletin “Reduced Range Devices Acceptance Criteria” [TTAB276] used for the results evaluation, • the Interoperability deck version against which it was tested, © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r • the LoA expiration date. Reduced Range LoA number coding is the following: Figure 3-2: Reduced Range LoA number coding Page 18 / 28 Limitations of the current LoA, e.g.: If the product performs a RESET before or after a proprietary polling command, 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 Reduced Range PCD Requirements may be found during Contactless Product testing. In that case, EMVCo will decide whether the PCD LoA must be removed from the list of approved products posted on EMVCo website. Product Provider may need to come back to Reduced Range PCD Type Approval. 3.5.3 Publication on EMVCo Website Letter of Approval is made available on the EMVCo website. However, if the Product Provider indicated on the Request for Approval Form that the approval should not be made public (for a period of time): • The Letter of Approval issued will be a provisional letter. A provisional letter is valid for six months. • At the end of the six months period, a final Letter of Approval will be issued (with only the name updated) and sent to the Product Provider. The Product will be listed on the EMVCo website. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r 3.6 EMVCo Type Approval fee structure The following fee structure is applicable: • Initial Submission • ICS Replacement (starting at 2nd Replacement) • Declined ICS/Report (Test Laboratory fee) • LoA reissuance Note: The amount of each fee is published in [TTAB185]. Page 19 / 28 © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 20 / 28 4 Change Management During the Reduced Range Product life cycle, Product Provider may need to make changes to the tested product, including: • engineering changes to the approved PCD, • engineering changes to the product in which the PCD has been tested and approved, • re-use of the approved PCD in another product than the one in which it has been tested and approved. A PCD is a combination of hardware and software components, each of them having determined functionalities and specific characteristics. The way those components are organized, their interactions, and the resulting functionality of the PCD define the PCD that is approved. A modification of any of these components or of their relationships could change the resulting functionality and create another PCD than the approved one. This new PCD may potentially not comply with the EMV Reduced Range PCD Requirements. Moreover, a PCD is developed to work in a specific environment (the Contactless Product and its architecture). The PCD communicates in an adapted way with its environment, while the environment provides the PCD with all needed resources for a correct behavior (power supply, absence of disturbing electromagnetic interference, etc.). Therefore, the environment in which the PCD is embedded is relevant for EMV Reduced Range PCD Requirements compliance: a PCD working in the product in which it has been tested could potentially not work in another –or modified- product. Note: The PCD functionality is to be understood as the set of functionalities the Product Provider wants to implement in the PCD. One of these functionalities is the implementation of the EMV Specifications, but the PCD functionality is not limited to it. The PCD also implements other functions responsible for the interface between the PCD and the rest of the product (e.g. communication with the Entry Point, communication with EMV Kernel(s) ...) The full set of functionalities is relevant for the PCD definition. The first sub-section deals with PCD changes, and the potential need on EMVCo re-approval of the PCD. The second sub-section deals with PCD’s environment changes, and the potential need on EMVCo re-approval of the PCD. In both situations, PCD changes can be qualified major or minor in nature. As Product Providers are intimately familiar with their PCD and products, it is ultimately the Product Provider’s responsibility to make the determination whether a change is major or minor (except for some cases specified below). However, if the Product Provider is unsure of the severity of the change, they may submit details of the change to EMVCo via email to request EMVCo's opinion. This request should include a full description of the change being made by the Product Provider in order for EMVCo to make a timely assessment. It is the responsibility of the Product Provider to maintain all evidentiary documentation describing why the modification made is minor i.e. cannot modify or impact the functionality of PCD and demonstrating the PCD is still compliant to the EMV Reduced Range PCD Requirements (design documents, test logs, etc.). © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 21 / 28 4.1 PCD changes 4.1.1 Minor and major changes Any change that can modify the functionality of the PCD is to be considered a major change, as the modified PCD is no longer representative of the originally approved PCD. Most changes to a PCD are potential major changes. The list below provides some examples of PCD changes; please note this list is not meant to be exhaustive. Examples of major changes Those changes are to be always considered as major changes. • Change in the way the Contactless EMV specification is implemented (see ICSimplementation information) • Change of Proximity Payment Antenna location or design • Change to an equivalent or different processor (in the situation where the processor is dedicated to the PCD, otherwise this change has to be considered a change of the environment) • Contactless Controller Firmware changes impacting L1 performances. • PCD Software or firmware changes impacting L1 performance • Contactless Controller Hardware Change • Contactless Controller parameter changes • PCD Landing Plane change • Contactless Symbol position change (if present during Type Approval), or addition of a Contactless Symbol at a position other that what was used during Type Approval. • Casing Changes involving metallic characteristics • Component or PCB changes impacting L1 performance Examples of changes that are generally considered as minor • Change of passive or active components for another with same physical and electrical characteristics. • Change of the color or marking of the PCD enclosure • Change of an external connector • Different providers implementing the same antenna design and material (antenna design is exactly the same – shape, thickness, material etc. ) 4.1.2 PCD change and Reduced Range PCD Type Approval Level 1 need • When the change is major, the PCD is considered a new PCD. The PCD must be renamed and submitted for Type Approval Test to receive a new EMVCo approval. • When the change is minor, there is no new Reduced Range PCD Type Approval Level 1 required by EMVCo. The PCD hardware and software version shall be updated as appropriate, as well as the PCD version. The PCD is considered a derivative PCD. However, it should be noted that: © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 22 / 28 ✓ EMVCo Contactless Product Approval will only be issued to products embedding an EMVCo-approved PCD version. ✓ It is the Product Provider’s responsibility to manage all linkage, documentation or test results to the modified PCD to show this is a derivative of the original approved one and is still compliant with EMV Reduced Range PCD Requirements. EMVCo does not issue approval letters for these derivative PCDs, without Type Approval Test and re-submission to Type Approval Process. 4.2 Change of Name and Address The Product Provider shall inform the EMVCo Type Approval Secretariat if the company name, address or contact information, as previously provided in the Product Provider registration process, changes. Changes impacting company names will require the Product Provider to sign a new contract with EMVCo. Generally, approval letters are not reissued for name changes in the event of the Product Provider’s assignment of the Letter of Approval if assignment is permitted under the provider’s contract with EMVCo and terms and conditions of the Letter of Approval (for example, in the event of provider’s merger, reorganization, or sale of substantially all its assets). Modifications to company addresses and contact information will be applied to the EMVCo web site and subsequent communication (e.g. approval notification) with the Product Provider. Some organizations specify different contact information for various products. 4.3 Re-Issuance of LoA If as a result of a company name change, address change or contact change, EMVCo needs to re-issue an existing LoA on explicit request from the Product Provider, EMVCo will request an administrative fee per LoA re-issuance. Please note that LoA are only issued electronically. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 23 / 28 5 Roles and responsibilities The following sections define the roles and responsibilities for the various participants in the Type Approval Process. 5.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 PTP Devices 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 Reduced Range 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 Product that have received EMVCo Type Approval notification. • EMVCo Terminal Type Approval Secretariat. 5.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. • Test Laboratory list. • Type Approval test requirements. • Issue Letter of Approvals. • Approved Product list. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 24 / 28 5.3 Test Laboratory The Test Laboratory is an entity recognised by EMVCo to conduct testing of Reduced Range Products 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 Reduced Range 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 product 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 Reduced Range PCD Level 1 evaluations. • Maintain the pool of PTP devices 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 4.2. 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 Laboratories is the responsibility of the Product Provider requesting EMVCo’s approval. EMVCo is not responsible for Test Laboratory testing fees. 5.3.1 Multiple Test Laboratories Level 1 testing can be split between different 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. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 25 / 28 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 EMVCo 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 any 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). 5.4 Auditor Team The auditor team comprises the person(s) in charge of conducting audits on behalf of EMVCo. 5.5 Product Provider The Product Provider is the entity responsible for submitting Contactless Product embedding PCD for Type Approval in compliance with Reduced Range PCD Type Approval procedures. © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 26 / 28 6 Test Version and Specification Change The following sections identify the process managing Reduced Range Type Approval Test changes due to EMV Specifications or Test Cases change. 6.1 Test Changes without EMV Specifications change EMVCo reserves the right to change Type Approval Test at any time in order to increase the accuracy and integrity of the tests versus the EMV Specifications, or for any other reasons. Figure 6-1: Example of the timing for test changes EMVCo will inform all participants of the new tests and fix the date(s) for activation of the new tests and deactivation of the old. By default, a migration period of 2 months between the activation date and the deactivation date, will apply for all submissions. Note: Example of migration period: • Version n+1 Test plan is activated Jan 1st, • Product can be registered with Version n ICS version until February 28th • Testing in Version n shall start before February 28th. • The report in Version n shall be submitted at the latest by May 30th • Related RFA must also be received before May 30th • Product can be registered with Version n+1 ICS version as from January 1st © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 27 / 28 6.2 Test Changes Due to EMV Specifications change After a change in the EMV Specification, EMVCo will decide: • If and when the Type Approval tests must be changed to accommodate the new specifications • When to introduce the new Type Approval test version • When to stop testing with the previous Type Approval test version EMVCo will announce on its website the new Test Cases version and the date(s) of the activation of the new version and deactivation of the previous versions and inform Laboratories and Tool Providers. By default, a migration period of 2 months between the activation date and the deactivation date, will apply for all submissions. Note: Example of migration period: • Version n+1 Test plan is activated Jan 1st, • Product can be registered with Version n ICS version until February 28th • Testing in Version n shall start before February 28th. • The report in Version n shall be submitted at the latest by May 30th • Related RFA must also be received before May 30th • Product can be registered with Version n+1 ICS version as from January 1st Figure 5.2 identifies the impact of specification changes on the Type Approval Process. Figure 5.2: Timeline for test changes following changes in EMV Specification © 2024-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 Reduced Range PCD Level 1 Administrative Process v3.2a.r Page 28 / 28 7 Appendix This appendix describes the enhancement of the present Administrative Process to support the EMVCo requirements related to the Contactless Marks Trademark License Agreement that Product Providers shall comply to, if the Contactless Symbol is present on the Product submitted for Approval. The support of this Contactless Marks Trademark License Agreement implies the following requirement in the administrative Process: • Product Provider must sign the ‘Contactless Marks Trademark License Agreement’, before any further product submission with the Contactless Symbol. • Test Laboratory must check the compliance of the EMVCo symbol on the Product if present, when performing the Reduced Range PCD Type Approval Tests • At the time of reviewing the Request for Approval of any product with Contactless Symbol, EMVCo will check that: o Product Provider has previously signed the Contactless Marks Trademark License Agreement. o The ‘presence of the EMVCo Symbol’ result in the Test Laboratory Test report submitted. &lt;&lt;< End of Document >>> © 2024-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.