EMV® Mobile Product Level 1 Type Approval – Administrative Process

EMV® Mobile Product Level 1 Type Approval Administrative Process Version 2.9 September 2025 © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page i / vii 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. © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page ii / vii Revision Log – Version 2.9 The following changes have been made to the document since the publication of Version 2.8. 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. Incorporated changes described in the following Specification Updates: • Section 4.1: LOA or TAS are sent to both primary and secondary contacts • Appendix A: Clarification that new specification bulletins updating the EMV Contactless Interface Specification are considered as a specification update. Change or Derivative process is not applicable in this case. Other editorial changes: • Editorial updates © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page iii / vii Contents 1 Introduction .................................................................................................................. 1 1.1 Audience ................................................................................................................. 1 1.2 Normative References............................................................................................. 2 1.2.1 EMV Specifications...................................................................................... 2 1.2.2 Mobile Product Level 1 Type Approval Documents...................................... 3 1.2.3 Mobile Product Level 1 Type Approval Forms.............................................. 4 1.2.4 External References .................................................................................... 4 1.3 Definitions ............................................................................................................... 5 1.4 Notational Conventions ........................................................................................ 9 1.4.1 Abbreviations............................................................................................. 9 1.4.2 Terminology and Conventions ................................................................. 9 2 Scope of Mobile Product Level 1 Type Approval ..................................................... 10 2.1 Mobile Product Definition ...................................................................................... 10 2.2 Mobile Product Architecture in Scope of EMV Type Approval ............................... 11 2.2.1 Eligible Devices ......................................................................................... 11 2.2.2 Execution Environments ............................................................................ 12 2.2.3 Supported Protocols .................................................................................. 12 2.3 Scope of Mobile Product Level 1 Type Approval ................................................... 12 2.4 Scope of Mobile Product Level 1 Test Assessment ............................................... 14 2.5 Debug Sessions .................................................................................................... 14 3 Mobile Product Level 1 Type Approval Overview .................................................... 15 3.1 Mobile Product Level 1 Type Approval Flow.......................................................... 15 3.2 Reporting Results to EMVCo................................................................................. 16 3.2.1 Reporting Evaluation Results..................................................................... 16 3.2.2 All Test Reports ......................................................................................... 16 3.2.3 Request for Approval or for TAS ................................................................ 16 3.3 General Rules for a Test Session.......................................................................... 16 3.4 Submitting Request for Approval Form or TAS...................................................... 17 3.5 Fee Structure ........................................................................................................ 17 3.6 EMVCo Service Levels.......................................................................................... 18 3.7 Multiple Laboratories ............................................................................................. 19 4 Mobile Product Level 1 Type Approval Procedures ................................................ 20 4.1 Product Provider Registration................................................................................ 20 4.2 Testing Phase ....................................................................................................... 22 © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page iv / vii 4.3 Product Provider Decision to Submit ..................................................................... 26 4.4 Approval Phase..................................................................................................... 26 4.5 Request for Approval or Test Assessment Summary ............................................ 29 4.6 Functional Test Reports ........................................................................................ 30 4.7 Test Assessment Summary................................................................................... 31 4.8 Letter of Approval.................................................................................................. 31 4.8.1 Minor/Major Change and Letter of Approval .............................................. 31 4.8.2 Publication on EMVCo Website ................................................................. 32 4.8.3 Restrictions/Comments in the Letter of Approval ....................................... 32 4.9 Letter of Rejection – Appeals ................................................................................ 33 4.10 Renewal of a Letter of Approval or Test Assessment Summary ............................ 33 4.11 Changed and Derivative Mobile Products.............................................................. 34 4.11.1 Derivative Product Definition...................................................................... 34 4.11.2 Changed Product Definition ....................................................................... 34 4.11.3 Family of Product Definition ....................................................................... 35 4.11.4 Minor, Major and New product ................................................................... 35 4.11.5 Testing Requirements................................................................................ 36 4.11.5.1 Testing Scenarios........................................................................ 36 4.11.5.2 Differential Testing ...................................................................... 36 4.11.6 Iteration of Minor or Major Change/Derivative Requests ............................ 37 4.11.6.1 Iteration of Minor Changes .......................................................... 37 4.11.6.2 Iteration of Major Changes .......................................................... 38 4.11.6.3 Examples .................................................................................... 39 4.11.7 Change or Derivative Request Process Flow............................................. 40 4.11.8 Identified Changes or Derivatives not Requiring Testing – Process Flow... 42 4.11.9 Family of Product Change Request Process Flow ..................................... 43 4.11.9.1 General Process.......................................................................... 43 4.11.9.2 NFC controller firmware change .................................................. 46 4.11.9.3 Software or OS change ............................................................... 48 4.12 Multiple Requests for Approval submitted at the Same Time ................................ 50 4.13 Submission of a Product with a Test Assessment Summary ................................. 51 5 Test Version and Specification Change ................................................................... 52 5.1 Test Cases Change Without EMV Specification Change....................................... 52 5.2 Test Cases Change Due to New EMV Specifications or Bulletins ......................... 53 5.3 Migration Period for Changes and Derivatives ...................................................... 54 6 Conformance.............................................................................................................. 55 © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page v / vii 6.1 Non-Conformance Investigation ............................................................................ 55 6.2 Revocation of Test Assessment Summary or Letter of Approval ........................... 55 6.3 Corrective Action................................................................................................... 56 7 Roles & Responsibilities ........................................................................................... 57 7.1 EMVCo ................................................................................................................. 57 7.1.1 EMVCo Card Type Approval Secretariat.................................................... 58 7.2 Product Provider ................................................................................................... 59 7.3 EMVCo Recognised Laboratories ......................................................................... 60 7.4 EMVCo Qualified Auditors..................................................................................... 61 7.4.1 Laboratory Recognition Audit..................................................................... 61 7.5 Relationships between Laboratories and Product Providers.................................. 62 7.6 Relationships between Auditors and Product Providers ........................................ 63 7.7 Relationships between Auditors and Laboratories................................................. 63 7.8 Change in Corporate Identity or Contact Information............................................. 64 8 Termination of Mobile Product Level 1 Type Approval ........................................... 65 8.1 Termination Right.................................................................................................. 65 8.2 Submissions after Notice of Termination ............................................................... 65 Appendix A - Changes and Derivatives of Mobile Products .......................................... 66 Appendix B – Test Requirements for New Products ...................................................... 70 Analogue, Validation and Interoperability Testing ............................................................ 70 Digital Testing.................................................................................................................. 71 Appendix C - Test Applications ....................................................................................... 72 Analogue and Digital ....................................................................................................... 72 Validation and Interoperability ......................................................................................... 73 UICC .................................................................................................................. 73 eSE, eUICC and HCE ............................................................................................. 73 Appendix D - Product Samples ........................................................................................ 75 Appendix E - UICC Kits..................................................................................................... 78 Obtaining UICC Kits ........................................................................................................ 78 © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page vi / vii Figures Figure 2-1: Mobile Product Physical Architecture......................................................................... 10 Figure 3-1: Mobile Product Level 1 Type Approval Flow.............................................................. 15 Figure 4-1: Product Provider Registration .................................................................................... 21 Figure 4-2: Testing Phase............................................................................................................. 25 Figure 4-3: Approval Phase ........................................................................................................... 28 Figure 4-4: Family of Product Change Request Process Flow .................................................... 43 Figure 4-5: Example of Schedule for Multiple RFA submission ................................................... 50 Figure 5-1: Release of New Test Cases without EMV Specification Change.............................. 52 Figure 5-2: Release of New Test Cases with EMV Specification or Bulletin Change.................. 54 © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page vii / vii Tables Table 1.1: EMV Specifications ........................................................................................................ 2 Table 1-2: Mobile Product Level 1 Type Approval Documents ...................................................... 3 Table 1-3: Mobile Product Level 1 Type Approval Forms .............................................................. 4 Table 1-4: External References ...................................................................................................... 4 Table 1.5: Abbreviations ................................................................................................................. 9 Table 2-1: Evaluations for Mobile Product Level 1 Type Approval .............................................. 12 Table 2-2: Evaluations for Mobile Product Level 1 Test Assessment .......................................... 14 Table A-1: Major Changes or Derivations .................................................................................... 66 Table A-2: Minor Changes or Derivations requiring Declaration.................................................. 69 Table B-1: Evaluation Matrix......................................................................................................... 70 © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 1 / 79 1 Introduction EMVCo, LLC (“EMVCo”) is the owner of the EMV® Integrated Circuit Card Specifications, including the EMV Contactless Interface Specification. All readers of this document are advised that 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 review the legal notice on page i of this document for important limitations on the scope of Type Approval. The EMV Mobile Product Level 1 Type Approval is the verification by EMVCo that a specific mobile product has demonstrated sufficient conformance to the EMV specifications. The process supports two types of evaluation: • Approval of commercial product with issuance of a Letter of Approval; • Assessment of non-commercial product (prototype) with issuance of a Test Assessment Summary (TAS). A Test Assessment Summary does not represent any type approval for the mobile product’s contactless functionality. It is delivered by EMVCo as a first and partial step if EMVCo has found reasonable evidence that the submitted samples passed EMV applicable analogue and digital tests covering EMV Contactless Interface Specification. 1.1 Audience This document is intended for all interested stakeholders in the Mobile Product system, including but not limited to: • Mobile handset suppliers • Wearable Product suppliers • NFC controller suppliers • Laboratories intending to offer testing services • EMVCo Qualified Auditors • Any other entity interested in developing to the EMV Specification The document may also be of use to other industry bodies focused on standardising different parts of mobile products. © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 2 / 79 1.2 Normative References The version numbers identified in the references below are valid at the time of release of this document. Nevertheless, the latest version available from EMVCo should apply. 1.2.1 EMV Specifications EMVCo, LLC (EMVCo) manages and maintains the EMV Integrated Circuit Card (ICC) Specifications for Payment Systems, hereinafter called the EMV specifications. EMV specifications are publicly available on the EMVCo website: www.emvco.com. Table 1.1: EMV Specifications Reference [CIS] Publication Name EMV Level 1 Specifications for Payment Systems ― EMV Contactless Interface Specification All Specification Update Bulletins as published on the EMVCo website Version 3.1 – Dec 2020 or higher Latest available © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 3 / 79 1.2.2 Mobile Product Level 1 Type Approval Documents Table 1-2: Mobile Product Level 1 Type Approval Documents Reference Publication Name Version [Lab Reco Req] EMV Laboratory Recognition Requirements Latest Available [MPL1 Analog TC] EMV Contactless Card Level1 Type Approval – PICC Analogue Test Bench and Test Case Requirements 3.2a or higher [MPL1 Digital TC] EMV Contactless Card Level 1 Type Approval – PICC Digital Test Cases 3.2a or higher [MPL1 TG] EMV Mobile Product Level 1 Type Approval – Mobile Level 1 Test Guidelines 3.2a or higher [MPL1 ITR] EMV Mobile Product Level 1 Type Approval – Validation and Interoperability Testing Requirements 1.6 or higher [IT LAB GUID] EMV Mobile Product Level 1 Type Approval - Laboratory Guidelines for Mobile Validation and Interoperability Testing Latest available [MPL1TAR] EMV Mobile Product Level 1 Type Approval - Level 1 Test Application Requirements 2.0.2 or higher Distribution EMVCo Website EMVCo Website EMVCo Website EMVCo Website EMVCo Website Restricted to EMVCo Qualified Test Tool Suppliers, EMVCo Recognised Laboratories, and EMVCo Qualified Auditors EMVCo Website © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 1.2.3 Mobile Product Level 1 Type Approval Forms Table 1-3: Mobile Product Level 1 Type Approval Forms Page 4 / 79 Publication Name Request for Registration for Product Providers Business Review Form EMV Mobile Product Level 1 Implementation Conformance Statement Request for Test Assessment Request for Approval (and for Publication) Product Change or Derivative Request Minor Change Declaration Form Version Latest available Latest available Latest available Distribution EMVCo Website EMVCo Website EMVCo Website Latest available Latest available Latest available Latest available EMVCo Website EMVCo Website EMVCo Website EMVCo Website 1.2.4 External References Table 1-4: External References Reference [7816] [14443] [18092] Publication Name ISO/IEC 7816 Identification cards — Integrated circuit cards ISO/IEC 14443 Identification cards — Contactless integrated circuit(s) cards — Proximity cards ISO/IEC 18092 Information technology — Telecommunications and information exchange between systems — Near Field Communication — Interface and Protocol (NFCIP-1) © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 5 / 79 1.3 Definitions The following terms are used in this specification: Term Definition Audit report Auditor Card Type Approval Secretariat Conformance Contactless Mobile Payment (CMP) Delta Testing Differential Testing EMV® EMV Specifications EMVCo EMVCo Recognised Laboratory EMVCo Qualified Auditor EMVCo Qualified Test Tool Execution Environment A report written by an EMVCo qualified auditor assessing, for example, type approval test results or laboratory test processes. See “EMVCo Qualified Auditor”. The EMVCo entity that manages the card and mobile type approval processes. Meeting all EMV requirements defined for Mobile Product Level 1 Type Approval including requirements for implemented optional functions. Integration of EMV-based contactless payment technology in mobile devices. Testing that covers the difference between the test plan versions the product was approved against versus the current version of the test plan when the product is changed or derived. Testing that covers the difference between the original product and the derivative product independently of the test plan being updated or not. Note: Testing will be determined on a case by case basis depending on the change A trademark owned by EMVCo, referring to the technical specifications published by EMVCo. Specifications managed, maintained, and enhanced by EMVCo, including those listed in Table 1.1. The organization that manages the EMV Specifications and their related testing processes. An independent, impartial entity that has received a Letter of Recognition from EMVCo, entitling it to perform testing for specified type approval; in the context of this document, to perform testing for mobile level1 type approval. An independent, impartial entity that has received a Letter of Qualification from EMVCo, entitling it to verify conformance to EMVCo-defined type approval procedures. A test tool qualified by EMVCo for use in type approval testing (by EMVCo Recognised Laboratories) or debug testing (by Product Providers). The environment where the payment application is executed, e.g. SWP UICC, eUICC, eSE, HCE. © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 6 / 79 Execution Environment under Test (EEUT) Handset Implementation Conformance Statement (ICS) Initial Execution Environment (Initial EE) International Organization for Standardization (ISO) Laboratory Letter of Recognition Letter of Approval Letter of Qualification Letter of Rejection Level 1 Level 1 evaluation Mobile Product Level 1 Type Approval Mobile Product Level 1 Type Approval process The execution environment that is evaluated and in which the test application shall reside A type of mobile device; specifically a mobile phone handset. A form completed by a Product Provider identifying the product, the EMV mandatory functions, the EMV optional functions supported, and (if any) the non-EMV proprietary functions. The Execution Environment selected by the Product Provider on which Analogue, Validation, Interoperability are fully performed. An international body that provides standards for financial transactions and telecommunication messages. ISO works in conjunction with the International Telecommunication Union (ITU) for standards that affect telecommunications. ISO supports specific technical committees and work groups to promulgate and maintain financial service industry standards. A facility that performs testing for Type Approval. Written statement that documents the decision of EMVCo that a laboratory is an EMVCo Recognised Laboratory and performs testing for type approval in conformance with the rules defined by EMVCo. Written statement that documents the decision of EMVCo that a specified mobile product has demonstrated sufficient conformance to the EMV Specifications and other testing requirements as of its test date. Written statement that documents the decision of EMVCo that an auditor is an EMVCo qualified auditor and performs audits for type approval in conformance with the rules defined by EMVCo. A statement that documents the decision of EMVCo that a specified product has NOT demonstrated sufficient conformance to the EMV Specifications and/or meets the requirements for the issuance of a Letter of Approval as of its test date. One of the two levels of EMV testing: Testing the proximity contactless interface of a mobile product according to [CIS]. Execution and reporting on the results of a defined set of functional tests supporting the EMV Specifications. Verification by EMVCo that a specific mobile product has demonstrated sufficient conformance to the EMV Specifications and other required testing. The steps necessary for a mobile product to obtain an EMVCo Letter of Approval. © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 7 / 79 Mobile Product (or Mobile Device) Multiple Execution Environment Near Field Communications (NFC) NFC Controller Non-card L1 form factor Passive Device Payment System Product Provider Prototype Product Recognition Registration Letter Registration Number Regression Testing A portable electronic device with contactless and optional wide area communication capabilities. Mobile devices include mobile phones and other consumer electronic devices such as a suitably equipped PDA, as defined in section 2.1. Capability for a mobile product to support several Execution Environments. For example one secure element in the UICC and HCE. A short range contactless proximity technology based on ISO/IEC 18092, which provides for ISO/IEC 14443 compatible communications A module within a mobile device providing a contactless interface compatible with EMV Contactless Communication Protocol Specification. Products that are not a card and not a mobile handset or a Wearable Product and that support mobile payment application(s). Mobile device powered by the PCD field (the NFC chip is not powered by a battery). For the purpose of this document, a payment system is defined as a payment system that participates in EMVCo’s Mobile Product Level 1 Type Approval Process. The entity that submits a mobile product to EMVCo for Mobile Product Level 1 Type Approval. Non-commercial mobile product. For example a product from an NFC chipset vendor that wishes to get an evidence that their chipset and firmware are compliant with EMV requirements Formal recognition by EMVCo that a test laboratory is competent to perform one or more categories of testing defined by EMV type approval procedures. Written statement provided by the Card Type Approval Secretariat including the Registration Number of the Product Provider, EMVCo Qualified Auditor, or EMVCo Recognised Laboratory. Unique identification number that EMVCo assigns to the Product Provider, EMVCo Qualified Auditor, or EMVCo Recognised Laboratory. A predefined subset of functional test cases executed to determine whether undeclared changes have been made to the originally approved product or to detect unforeseen consequences from declared changes. © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 8 / 79 Request for Approval Request for Approval Form Request for Test Assessment Request for Test Assessment Form Test Test Assessment Summary Test case Test report Type Approval Type Approval documentation Type Approval process Validation and Interoperability Testing Wearable Product The formal request by the Product Provider for EMVCo to evaluate the test report with the objective to receive a Letter of Approval. The request includes test reports, forms and any other information required for evaluation and may be submitted by the Product Provider or by a laboratory acting on behalf of the Product Provider. The form used to enact a Request for Approval. The formal request by the Product Provider for EMVCo to evaluate the test report with the objective to receive a Test Assessment. The request includes test reports, forms and any other information required for evaluation and may be submitted by the Product Provider or by a laboratory acting on behalf of the Product Provider. The form used to enact a Request for Test Assessment. Any activity that aims at verifying the conformance of a selected product or process to a given requirement under a given set of conditions. A written statement that documents the decision of EMVCo that has found reasonable evidence that the submitted samples passed EMV applicable level 1 tests as of its test date and it may be used by other certification authorities as part of their own Type Approval processes. A description of the actions required to achieve a specific test objective. Document provided by a laboratory containing the test results for a Product. As used in this document, the term is interchangeable with Mobile Product Level 1 Type Approval. Full set of documents and procedures issued by EMVCo to enable the Type Approval process. As used in this document, the term is interchangeable with Mobile Product Level 1 Type Approval Process. A set of tests to assess the capability of the mobile product to perform a transaction when presented to a number of different terminals. Any chip or host card emulation based product that is incorporated into an item of clothing or accessory which supports proximity payment © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 1.4 Notational Conventions 1.4.1 Abbreviations The abbreviations listed in Table 1.5 are used in this specification. Abbreviation CMP eSE eUICC ETSI ETSI SCP GSM GSMA HCE ICS IEC IMEI PICC RF TAC UICC Table 1.5: Abbreviations Description Contactless Mobile Payment Embedded Secure Element Embedded UICC European Telecommunication Standards Institute ETSI Smart Card Platform Global System for Mobile Communications GSM Association – an association of GSM operators Host-based Card Emulation Implementation Conformance Statement International Electrotechnical Commission International Mobile Equipment Identity Proximity Integrated Circuit Chip Radio Frequency Type Allocation Code Universal Integrated Circuit Card Page 9 / 79 1.4.2 Terminology and 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. © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 10 / 79 2 Scope of Mobile Product Level 1 Type Approval 2.1 Mobile Product Definition A mobile product is a portable electronic device with contactless and optional wide area communication capabilities. The primary focus for the Type Approval is the NFC Controller, antenna and card emulation mode. A Wearable Product is considered a mobile product for the purposes of this document whether powered by a battery and/or contains an NFC Controller. Figure 2-1 shows a possible architecture of a mobile product. Figure 2-1: Mobile Product Physical Architecture ISO 7816 interface with the baseband processor Connection to Secure Element (e.g. SWP, ISO 7816, S2C) Mobile Product UICC Card NFC SE Controller Communication link between the UICC and NFC Controller (e.g. SWP, HCI) Baseband and Application Processor HCE Mobile product processor to run applications interfacing with the user Contactless antenna Communication link between the Application processor and the NFC Controller, (e.g. NCI) © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 A mobile product shall identify at least the following elements: • Product name and version (Note: may not be the commercial name) • Product operating system name and version • NFC Controller (or Contactless Front End) name and version • NFC Controller firmware name and version • Antenna Identifier Name and version • NFC environment: o Battery Identification (if applicable) o Handset case/housing Identification o Position of the antenna in the handset • HCE support • eSE support • eUICC support • SWP UICC support • Form factor Page 11 / 79 2.2 Mobile Product Architecture in Scope of EMV Type Approval 2.2.1 Eligible Devices The main target of the Mobile Product Level 1 Type Approval process is the mobile handset providers, but other devices may also be eligible to this approval process as long as they support the mobile payment application(s) of the Payment Systems. The other eligible devices are listed below: • Wearable Products. Note that if Wearable Products support multiple sizes or straps (in case of watch for instance) EMVCo shall be contacted to determine the test requirements. • Other products that are not a card and not a mobile handset or a Wearable may also be eligible (product called non-card L1 form factor in this Mobile Product Level 1 Type Approval process). The above eligible devices can be either active devices (powered by a battery) or Passive Devices (powered by the PCD field). © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 12 / 79 2.2.2 Execution Environments Mobile Product architecture may support one or more execution environments where the payment applications are executed. Execution environment can consist of secure elements in different form factors, such as UICC, removable SD card, or non-removable device such as an embedded secure element (eSE) or eUICC. Execution Environment can also be Hostbased Card Emulation (HCE). EMVCo supports Mobile Products with removable secure element (SWP UICC), embedded secure element (eSE or eUICC) or HCE hosting the payment application. Other execution environments are currently out of scope of the EMV Mobile Product Level1 Type Approval 2.2.3 Supported Protocols By Default, any mobile product shall support both Type A and Type B contactless protocols. This applies to mobile handsets or tablets. It is at the discretion of EMVCo to accept that a mobile product only supports Type A or Type B. If it is not possible to support Type A and Type B, the Product Provider shall contact EMVCo and explain the reasons why only one protocol type is supported. Agreement of EMVCo is a prerequisite before submission of an ICS for a mobile handsets or a non-card L1 form factor product that only supports one protocol type. Wearable Products may support both Type A and Type B contactless protocols or only one contactless protocol. ICS has to be filled accordingly at the discretion of the Product Provider. For non-card L1 form factor Products, the Product Provider shall contact EMVCo on the applicable requirement before submission of the ICS form. 2.3 Scope of Mobile Product Level 1 Type Approval EMVCo issues a Letter of Approval for a Mobile Product when the Mobile Product has successfully completed the evaluations listed in Table 2-1. Table 2-1: Evaluations for Mobile Product Level 1 Type Approval Contactless Analogue and Digital Mobile Product Validation Mobile Product Interoperability The scope of EMVCo’s Mobile Product Level 1 testing is: • Testing the minimum functionality that the NFC Controller and Proximity Payment Antenna of the Mobile Product should support to comply with [CIS]; • Testing the communication behaviour of the Mobile Product with a pool of reference terminals: o Validation at a single position with a subset of terminals; o Interoperability at numerous positions within the operating volume on all terminals of the pool using a robot. © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 13 / 79 Refer to [MPL1 ITR] for a description of the validation and interoperability test requirements. If a Product Provider applies for a Letter of Approval for a Mobile Product supporting multiple execution environments, the Type Approval shall include the evaluations which are described in Appendix B – Test Requirements for New Products. All evaluations for each Execution Environment shall be successful in order to get a Letter of Approval for the product. Note 1: if the operating system of a mobile product supports HCE, it is mandatory that HCE execution environment is listed in the ICS and tested during the Mobile Product Level 1 Type Approval. Note 2: Product Provider may decide not to have UICC, eSE or eUICC execution environment tested even if the product supports it. However, some Payment Systems may not recognize the EMVCo LOA if the Product Provider wishes to use the untested EE. Note 3: The procedure applicable to eSE testing described in this document also applies to eUICC testing. © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 14 / 79 2.4 Scope of Mobile Product Level 1 Test Assessment EMVCo issues a Test Assessment Summary for a Mobile Product when the Mobile Product has successfully completed the evaluations listed in Table 2-2 for the selected execution environments. Test Assessment Summary only applies to prototype products. The Product Provider can choose the execution environments to be tested. Table 2-2: Evaluations for Mobile Product Level 1 Test Assessment Contactless Analogue and Digital The scope of EMV Mobile Product Level 1 testing is testing the minimum functionality that the NFC Controller and Proximity Payment Antenna of the Mobile Product should support to comply with [CIS]. If a Product Provider applies for a Test Assessment Summary for a Mobile Product supporting multiple execution environments, the Test Assessment shall include the evaluations which are described in Appendix B – Test Requirements for New Products. All evaluations for each execution environment shall be successful in order to get a Test Assessment Summary for the product 2.5 Debug Sessions Debug sessions may occur between the laboratory and the Product Provider at any time and are beyond the scope of EMVCo. © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 15 / 79 3 Mobile Product Level 1 Type Approval Overview 3.1 Mobile Product Level 1 Type Approval Flow The L1 Type approval flow follows the generic steps applicable to any EMV Type Approval Figure 3-1: Mobile Product Level 1 Type Approval Flow © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 3.2 Reporting Results to EMVCo Page 16 / 79 3.2.1 Reporting Evaluation Results The Product Provider shall ask the EMVCo Recognised Laboratory to send the reports directly to EMVCo. 3.2.2 All Test Reports Each test report shall include the ICS reference number on the cover page. 3.2.3 Request for Approval or for TAS Upon receipt of a Request for Approval or a request for TAS, the Card Type Approval Secretariat will invoice the Product Provider. After confirmation from the Financial Secretariat that all the required fees have been paid, it will assemble all the reports into one Request for Approval package. It is the Product Provider’s responsibility to ensure that all required items are received by EMVCo. The Request for Approval or request for TAS will not be reviewed until payment of all required fees and all required items have been received. 3.3 General Rules for a Test Session The following rules shall be followed by the laboratory performing the Level 1 evaluation: • The Product Provider shall not be present during the testing of the Mobile Product. • Mobile Products shall be tested against the currently supported Test Cases version(s), and with an EMVCo qualified Test Tool. • No modifications are allowed to the Mobile Product. If any modifications are made to the Mobile Product during the test session, the session shall end and the Product Provider shall initiate a new submission including a new ICS. • If any modification is made to the ICS during the test session (without any modification to the Mobile Product or to the functional description of the Mobile Product), the modified ICS shall be sent to EMVCo. The modified ICS is reviewed by EMVCo and if acceptable retains the validity period of the original EMVCo-accepted ICS. Note: Modification of the ICS is subject to a fee (See Section 3.5). • The terminals used for the validation and interoperability evaluations are restricted to the laboratory. The laboratory shall not disclose the list of terminals to the Product Providers. A number will be allocated to each terminal to identify them in the report. © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 17 / 79 3.4 Submitting Request for Approval Form or TAS A Request for Approval form or Request for TAS form, completed in its entirety, shall be submitted after testing is complete, as discussed in section 4.5. Product Providers may submit a preliminary Request for Approval form or Request for TAS form during the Testing Phase, at any point after EMVCo notifies the laboratory that the ICS is acceptable (as discussed in section 4.2). If the form is submitted early, EMVCo will invoice the Product Provider and the Product Provider can pay the administrative fees before test reports are available. Given that test reports are not reviewed until EMVCo has received payment of all fees, early payment avoids delays during the Approval Phase. 3.5 Fee Structure EMVCo will charge fees to cover the administrative expenses incurred by EMVCo in managing the Mobile Product Level 1 Type Approval process. This process includes, but is not limited to: • review of test reports; • updates to the Mobile Product Level 1 Type Approval documentation, specifications, and Test Cases; • maintenance of the EMVCo website, including lists of approved Mobile Products, EMVCo Recognised Laboratories, and EMVCo Qualified Auditors. The following fee shall be paid to EMVCo by the Product Provider per mobile product: • Initial parent submission: o Mobile L1 Request for Approval fee for a review of a request for approval for a new product or for a review of a request for TAS for a prototype. o Combined Mobile L1 Derivative Request fee for each review of a derivative request submitted with the initial parent submission. • Subsequent derivative submission: o Mobile L1 Derivative Request fee for a review of a derivative request submitted after the initial parent submission. o Combined Mobile L1 Derivative Request fee for each review of a derivative request submitted at the same time as another derivative submission from the same parent. • Mobile L1 Change Request fee for a change request. • Publication of a Minor Product fee for the publication on the EMVCo website of a minor product. • Mobile L1 Family of Product fee for a family change or derivative request. A fee shall be paid for each product included into the family. Note that a specific fee applies if the change/derivation is a Handset Software/OS change or an NFC Controller Firmware change affecting card emulation. © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 18 / 79 • Letter of Approval Re-issuance fee for a Letter of Approval or Test Assessment Summary re-issuance requested by the Product Provider. • ICS Replacement fee. One free ICS replacement is allowed during the ICS life cycle. Any subsequent ICS replacement requested is charged to the Product Provider. o Same submission process applies as for initial ICS submission (Laboratory submits the changed ICS). o This applies to any change in the ICS after the official approval of the ICS by EMVCo. o 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 ICS replacement is not allowed after Test Report submission to EMVCo. The following fee shall be paid to EMVCo by the laboratory: • ICS decline fee if an incomplete and/or inconsistent ICS is submitted to EMVCo for review (as Laboratory is responsible of reviewing the ICS provided by the Product Provider). ICS decline process applies to the initial ICS submission and also to any other ICS replacement (charged or not charged to the Product Provider). • Test report decline fee if an incomplete and/or inconsistent test report is submitted to EMVCo for review. Note 1: The amount of each fee is published in the Mobile Type Approval bulletin 22 available on EMVCo Website. Please check the EMVCo website for the latest fee amounts. Note 2: The fee table in bulletin 22 assumes no deductions will be made on payments to EMVCo for tax withholdings, bank fees, or other amounts (“Deductions”). If any Deductions are to be made, then the fee payable will be increased by such amount as necessary to ensure that the amounts that EMVCo actually receives, excluding taxes that EMVCo is required to collect, reflects the amounts in Bulletin 22. The Request for Approval or Request for TAS will not be reviewed until complete payment has been received. Note 3: The testing fees charged by the EMVCo Recognised Laboratory to execute test cases are the responsibility of the Product Provider. Note 4: In case of multiple submissions, all requests for Approval shall be received at the same time to benefit from the reduced fee. 3.6 EMVCo Service Levels The service level for the issuance of a Letter of Approval or a Test Assessment Summary for a report showing 100% compliance shall be 5 business days from the receipt of all required documentation and payment of any applicable fees. The service level for ICS review shall be 3 business days. The service level for a Change or Derivative request review shall be 8 business days. © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 19 / 79 EMVCo strives to provide the optimum service levels for all activities, but it cannot commit to service levels for matters that require investigational work, such as reviewing reports not showing 100% compliance. 3.7 Multiple Laboratories Level 1 testing can be split between different laboratories. When this is the case, the following rules shall apply: • A single laboratory is responsible for the Level 1 functional testing (primary laboratory). o The primary laboratory may subcontract some testing to other laboratories (subcontracted laboratories). o The primary laboratory and the subcontracted laboratory shall be recognised for full Mobile Level 1. o Agreement shall be in place between the laboratories to support the subcontracting work. o The Product Provider shall be informed and shall agree that some or full testing will be sub-contracted to another Recognised Laboratory. o The primary laboratory submits the ICS to EMVCo. o The primary laboratory shall create, sign and submit to EMVCo all test reports. o All samples shall be sent to the primary laboratory that will dispatch some of them to the subcontracted laboratory. o All samples used during the test sessions shall be returned to the primary laboratory and shall be kept by the primary laboratory after the testing. o All session results and logs shall be made available to the Primary Laboratory, responsible for their archive. o The subcontracted laboratories shall follow EMV rules. o The primary laboratory will be responsible for subcontracted laboratories defects and may require additional audit. o In case of ICS issue, fees will only be applied to the primary laboratory. o The primary laboratory shall document the subcontracted work into the test report. • When testing is conducted at multiple laboratories, all test reports received shall contain the same version number of the EMV application(s), operating system, and environment. • All rules regarding the samples shall be maintained. All sets of mobile product samples at all laboratories are for the same version of the ICS. The reports shall clearly indicate which samples were tested at each laboratory. © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 20 / 79 4 Mobile Product Level 1 Type Approval Procedures The following sections describe the Type Approval process: Note: This document frequently requests one entity to send a form or a test report to EMVCo. Unless otherwise specified, all such materials shall be sent to the Card Type Approval Secretariat (card_approval@emvco.com). 4.1 Product Provider Registration1 As illustrated in Figure 4-1, the Product Provider Registration process is as follows: • The Product Provider enters registration information on the EMVCo Registration Web page. • EMVCo reviews the registration. o If at least one Payment System knows the Product Provider and agrees for them to be a vendor, no business review is required. o If the Product Provider is unknown to all Payment System or if any Payment System objects, then the Product Provider is informed that a business review is required. The Product Provider shall submit a Business Review form (including a Dun & Bradstreet report or equivalent in English) to the Card Approval Secretariat (card_approval@emvco.com). • EMVCo reviews the submitted materials and, if acceptable, sends a confirmation email to the Product Provider with the following additional information: o Link to the EMVCo Type Approval Contract (DocuSign) o Appropriate contact information • The Product Provider shall digitally sign the EMVCo Type Approval Contract with DocuSign. • When the EMVCo Type Approval Contract is countersigned by EMVCo, the EMVCo Type Approval Contract is sent back to the Product Provider by DocuSign. Note 1: The EMVCo Type Approval contract shall be executed before the testing phase described in section 4.2 begins. • The Card Type Approval Secretariat provides the Product Provider with a Registration Letter which will include the Product Provider’s unique Registration Number. Note 2: The registration process is completed only once per Product Provider. Note 3: An EMVCo Letter of Approval or Test Assessment Summary is addressed to the primary and secondary contacts identified on the Request for Registration. 1 Product Provider registration can be performed concurrently with, or after, selecting a laboratory. © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Figure 4-1: Product Provider Registration Start Product Provider enters registration information on the EMVCo Registration Web page If required, Product Provider Provides a Business Review form to EMVCo Page 21 / 79 Registration Information and Form complete? Y EMVCo enters Product Provider’s information into EMVCo database and sends Product Provider contracts for signature EMVCo informs Product Provider of incomplete information Product Provider submits completed contracts to EMVCo Contracts complete? N Y EMVCo sends Product Provider a copy of signed contracts EMVCo informs Product Provider of incomplete contract information EMVCo provides Registration Letter including Registration Number to Product Provider End © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 22 / 79 4.2 Testing Phase The Product Provider: • Selects one test laboratory from the list of EMVCo Recognised Laboratories published on the EMVCo website and executes bilateral required agreements and contracts. Note 1: The Product Provider shall ensure that the laboratory chosen is independent of the Product Provider. • For each mobile product that it submits, sends: o A fully completed and digitally signed Implementation Conformance Statement (ICS) to the selected laboratory. Note 2: The ICS format and content are defined by EMVCo. The latest version of the ICS available on the EMVCo website shall be used. o Product samples: • with battery, charger, tools necessary to insert/change UICC (if required); • with a Reference Mark representing the reference testing point (the Reference Mark shall be positioned on the mobile product surface); • configured: ✓ with WiFi, GPS and Bluetooth disabled (or with indication to disable these technologies). Note: Bluetooth shall be disabled unless it is required for mobile payment operations; ✓ with all applicable contactless functionalities such as P2P and Mifare enabled (or with indication to enable these functionalities); ✓ to keep the screen ON as long as possible (in order to facilitate the testing and to be representative of normal conditions of usage). Refer to the specific screen requirements defined in the different testing documents ([MPL1 TG], [MPL1 ITR]); ✓ to show the battery level (i.e. to indicate clearly the battery level) when testing (the display of the battery level can be made on the device screen or using command line provided by Product Provider). The laboratory shall ensure that mobile product is tested when battery level is above 50% during analogue and digital testing (refer to [MPL1 ITR] for battery requirements during validation and interoperability testing). Note 3: The Product Samples shall be provided from the same manufacturing batch, using the same Hardware components and loaded with the same firmware/software/OS version. Note 4: The Product Provider shall refer to Appendix D - Product Samples to determine the exact number of product samples to provide as well as the required configurations and test profiles depending on the supported execution environment(s). © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 23 / 79 Note 5: The same sample shall be used for analogue testing, validation and interoperability testing. If testing is split between multiple laboratories, all labs shall use the same samples. The first laboratory shall manage the shipment to the next laboratory. Different samples are allowed on digital tests. Note 6: All provided samples shall have the same TAC. Note 7: The TAC of the mobile product samples is checked and compared to the TAC documented into the ICS as part of the laboratory verification. The TAC is also documented into the LOA to ensure that the LOA is associated to the tested product reference. It is possible for the Product Provider to document production TACs in addition to the TAC of the product samples in case the samples used for testing have specific TAC range. The production TACs for the tested product will also be listed into the LOA with a note that only the TAC value of the testing samples has been checked by EMVCo. Note 8: If the TAC is not available for the product, a Product Reference Number shall be used instead. A Product Reference Number is a unique identification or model number that has an equivalent meaning as a TAC for a mobile phone. Note 9: Usage of Airplane mode is possible when there is no other possible way to disable other technologies (Wifi , Bluetooth and GPS) individually. A The laboratory: • Validates that the ICS is complete and all sections and fields are consistent. • Digitally signs the ICS. • Submits a copy of the complete ICS to EMVCo (card_approval@emvco.com) for acceptance prior to the start of the type approval testing process. EMVCo: • Reviews the ICS. • If the ICS is acceptable to EMVCo, then: o States the ICS expiration date. An approved ICS is valid for 6 months. Note 10: EMV Functional Testing shall be completed and reports submitted prior to expiration of the ICS. 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 longer valid (ICS, RFA, report) and a new process shall be restarted. Note that in this case the invoice will not be reimbursed. o Assigns the ICS reference number. o Notifies the laboratory of acceptance by providing back the ICS digitally signed by EMVCo including the ICS reference Number. o Archives the ICS for later comparison to the ICS submitted within the Request for Approval or Request for TAS. © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 24 / 79 o Optionally at this stage, the Product Provider may submit a Request for Approval Form to the Card Type Approval Secretariat (card_approval@emvco.com) in order to receive and pay EMVCo’s invoice prior to complete testing (See section 3.4). • If the ICS is not acceptable to EMVCo, then: o Notifies the laboratory that the ICS is not acceptable and issues an invoice to the laboratory for the decline ICS fee as defined in section 3.5. o The laboratory notifies the Product Provider that the ICS is not acceptable. o The Product Provider submits a new ICS to the laboratory. o Processing continues with Step A of section 4.2. The laboratory: • Validates that the samples received are consistent with the ICS. • Identifies the list of applicable EMVCo-defined Test Cases according to the ICS and Appendix B – Test Requirements for New Products. • Tests the Mobile Product and provides a signed and non-modifiable test report(s) to the Product Provider. o Test results shall be based upon the current valid Test Cases versions. o Tests shall be executed with EMVCo qualified Test Tool(s). Note 11: The laboratory is required to archive all test tool versions for a minimum of three years after the version deactivation date. Note 12: The laboratory should maintain all test result logs for all Test Cases and make those available for EMVCo review as requested. Note 13: Once started, the test session shall not be interrupted by debug sessions. A type approval test session is either aborted or run until completion. If it is aborted, the next session will have to restart from the beginning. © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Figure 4-2: Testing Phase Start Product Provider selects EMVCo Recognised Laboratory (s) Page 25 / 79 Product Provider provides ICS and Product samples to Laboratory(s) Laboratory(s) validates ICS ICS acceptable? N Y Laboratory(s) submits ICS to EMVCo Laboratory(s) informs Product Provider of non-acceptance ICS acceptable? N Y EMVCo informs Laboratory(s) of acceptance EMVCo informs Laboratory(s) of non-acceptance Laboratory(s) validates that the Sample Products are consistent with ICS Laboratory(s) performs testing Laboratory(s) provides test results to Product Provider End © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 26 / 79 4.3 Product Provider Decision to Submit The Product Provider determines whether test results resulting from 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 Mobile Product performance. Test results may be submitted to EMVCo for evaluation up to 90 days from the date the Mobile Product was tested. If the test results and the related Request for Approval are not submitted within that 90 day period, all documents related to this approval request are no longer valid (ICS, RFA, report) and a new type approval shall be restarted. Note that in this case, the approval fee will not be reimbursed. • The Product Provider shall 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. 4.4 Approval Phase The Product Provider: • Submits a Request for Approval or a Request for TAS to the Card Type Approval Secretariat at card_approval@emvco.com (See section 4.5 for a detailed description of the materials to be submitted.) • Upon reception of EMVCo’s invoice, pays required Type Approval administrative fees to EMVCo. Note 1: Product Providers may submit the Request for Approval Form before submitting test reports in order to receive and pay EMVCo’s invoice prior to complete testing (See section 3.4). • Requests the EMVCo Recognised Laboratory to send the functional test report directly to EMVCo. Note 2: If any functional test report shows less than 100% successful test results, the Product Provider shall include an impact analysis of the non-conformance(s). Upon reception of a Request for Approval, EMVCo: • B Determines whether the test report has expired. o If so, EMVCo notifies the Product Provider that the test report has expired. The Product Provider shall begin the process again. • Determines whether this is the first Request for Approval submitted with this ICS reference number. o If so, issues an invoice to the Product Provider for the applicable fees. o If not and if the previously issued invoice has been paid, EMVCo continue with step C. o EMVCo waits for payment before proceeding. © 2015-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® Mobile Product Level 1 Type Approval Administrative Process v2.9 Page 27 / 79 • C Determines whether all materials described in section 4.5 have been received. o If not: - EMVCo notifies the Product Provider that the Request for Approval or Request for TAS is incomplete. - EMVCo takes no further action until a new Request for Approval or Request for TAS is received. - When an additional Request for Approval or Request for TAS is received, EMVCo processes it as usual, beginning with Step B. • Evaluates the submitted functional test report and each ICS submitted with the report. o EMVCo will consider “acceptable for an approval or TAS” a functional test report showing 100% successful test results. o If a functional test report shows less than 100% successful test results, EMV