EMV® Contactless Terminal Level 1 Type Approval – Reduced Range Interoperability Test Application Requirements

EMV® Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements Version 1.0.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. Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements v1.0.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 non-infringement. All warranties, rights and remedies relating to products and services that have undergone evaluation by EMVCo are provided solely by the parties selling or otherwise providing such products or services, and not by EMVCo, and EMVCo will have no liability whatsoever in connection with such products and services. This document is provided "AS IS" without warranties of any kind, and EMVCo neither assumes nor accepts any liability for any errors or omissions contained in this document. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND 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. Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements v1.0.r Page ii / iv Revision Log – Version 1.0.r The following changes have been made to the document since the publication of version 1.0: Editorial updates © 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. Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements v1.0.r Contents Page iii / iv 1 Using this Manual....................................................................................................................... 1 1.1 Purpose ............................................................................................................................... 1 1.2 Audience.............................................................................................................................. 1 1.3 Reference Documents ......................................................................................................... 1 1.4 Definitions ............................................................................................................................ 1 2 Test Environment ....................................................................................................................... 3 3 Application Configuration files ................................................................................................. 4 3.1 AID List ................................................................................................................................ 4 3.1.1 File Name ........................................................................................................................ 4 3.1.2 File Format ...................................................................................................................... 4 3.2 PICC Configuration files....................................................................................................... 4 3.2.1 Name ............................................................................................................................... 5 3.2.2 Format ............................................................................................................................. 5 4 Test Application. ........................................................................................................................ 7 4.1 General Requirements......................................................................................................... 7 4.2 Test Preparation .................................................................................................................. 7 4.3 Test Application flow ............................................................................................................ 8 4.4 Application processing ......................................................................................................... 9 4.5 Application additional requirements ................................................................................... 11 A. Commands................................................................................................................................ 12 A.1. Select Command ............................................................................................................... 12 A.2. Select PPSE ...................................................................................................................... 13 © 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. Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements v1.0.r Page iv / iv Figures Figure 2-1—Test Environment .............................................................................................................. 3 Figure 3-1—AID List file format............................................................................................................. 4 Figure 3-2—PICC Configuration File Format ........................................................................................ 6 Figure 4-1—Loop mode Application flow .............................................................................................. 8 Figure 4-2—Single mode Application flow ............................................................................................ 9 Figure 4-3—Transaction Flow selection.............................................................................................. 10 © 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. Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements v1.0.r Page 1/14 1 Using this Manual 1.1 Purpose In addition to the PTP mobiles used in the PCD Interoperability Tests, PTP cards are added to the pool of PICCs to be used for Reduced Range Interoperability and Validation tests. The PTP cards used for Interoperability tests are loaded with real payment applications using specific transaction flows configured with test data. Consequently, a specific application shall be loaded on DUT to perform Interoperability tests with PTP cards. EMVCo provides Laboratories with a test application allowing Laboratories to perform the Interoperability and Validation tests with PTP mobiles and PTP cards (EMVCo COTS Interoperability Application). This application is currently compatible with the Android operating system (version 7.0 and later) only. EMVCo may consider additional operating systems in the future. If a Reduced Range product does not support the EMVCo COTS Interoperability Application provided by EMVCo, the Product Provider shall develop its own application implementing the requirements defined in this document. 1.2 Audience This manual is provided to: • Product Providers • Testing laboratories recognised to perform the Type Approval tests 1.3 Reference Documents EMV documents are available on the EMVCo web site: https://www.emvco.com/ Ref. [ConfigFiles] Document Title Version EMV Reduced Range Interoperability App Config Files Latest available 1.4 Definitions The following abbreviations and notations are used in this document: Term Definition Test Environment Environment needed to perform the Test. Product Provider Entity that submits the Reduced Range product for Reduced Range Type Approval. © 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. Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements v1.0.r Page 2/14 Term Proximity Coupling Device (PCD) Definition A hardware device that uses inductive coupling to provide power to the PICC and exchange data with the PICC. Proximity Integrated Circuit Card (PICC) A hardware device containing an integrated circuit and capable of inductive coupling in the proximity of a coupling device. PICC Test Pool (PTP) A cardholder device used for Interoperability tests. Device Testing Laboratory Transaction A facility recognised by EMVCo for performing EMV Contactless testing of the analogue interface for PICCs and PCDs. A sequence of logic interactions that the PICC and the Terminal shall execute as foreseen by the EMV Contactless application. The transaction starts with the first logic message from the PCD to the PICC. © 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. Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements v1.0.r 2 Test Environment Page 3/14 The Test environment is composed of three components: • AID List: A file listing all the AIDs used by the PTP Cards during the Interoperability tests. This file is defined by EMVCo and will be installed directly by the Laboratory during test session. In case the AIDList cannot be installed by the Laboratory, it can be installed by the Product Provider. Latest version of the file is available in [ConfigFiles] on EMVCo website. • PICC Configuration files: A file defining for each PTP card the specific sequence of C-APDUs to be sent by the Reduced Range product under test. The Configuration files are defined by EMVCo and will be installed directly by the Laboratory during test session. In case the PICC Configuration files cannot be installed by the Laboratory, they can be installed by the Product Provider. Latest version of these files are available in [ConfigFiles] on EMVCo website. • Interoperability Test Application. Figure 2-1—Test 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. Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements v1.0.r 3 Application Configuration files Page 4/14 These configuration files defined by EMVCo shall be used by the test application. EMVCo provides Product Providers with the configuration files used for Reduced Range Interoperability tests with PTP Cards. The configuration files are included in [ConfigFiles]. The Configuration files will be installed on the Reduced Range product under test by the Testing Laboratory prior to the test session. The Test Application shall be capable to use the configuration files as specified in this section. 3.1 AID List The AID List xml file contains a list of AIDs used by EMVCo for Reduced Range product Interoperability Tests. This file can be updated by EMVCo over the time. 3.1.1 File Name The name of the AID list xml file is “AIDList.xml” 3.1.2 File Format Figure 3-1—AID List file format The AID names listed in the AIDList file can be partial. The AID is expressed in Hexadecimal characters (with no space), the minimum length of the AIDs in AIDList is 10 characters (5 Bytes). 3.2 PICC Configuration files The PICC Configuration xml files specify the command APDUs that the test application shall send during a transaction performed with cards matching the PICC Configuration xml files. © 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. Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements v1.0.r Page 5/14 3.2.1 Name The name of the PICC Configuration file contains the AID of the concerned PICC application and optionally the PDOL returned by the PICC in response to SELECT command. File name format: ‘PICC_(AID).xml’ or ‘PICC_(AID)(PDOL).xml’: • The AID in the PICC Configuration filename is exactly the same as the DF Name returned by the card • The PDOL can be added in the file name to differentiate multiple PICC Configuration xml files for the same AID, the PDOL in the file name is exactly the same as the PDOL returned by the card in the Select AID response and should be: ‘9F38’+length of tag 9F38+value of tag 9F38 For example a file name could be “PICC_1122334455_9F3802AABB.xml”: • AID=1122334455 • PDOL: o Length= 02 o Value= AABB 3.2.2 Format The APDUs to be exchanged with PTP Cards are defined in an group. This application group is composed of: • An attribute AID with as value the DF Name as returned by the card in Select AID response. • 1 or multiple groups. The first group is the 1st command APDU the test application shall send after the Select AID response has been received. Each group contained: • The Attributes: o “Name”: Name of the command o “cmd”: 2 hexadecimal characters (1 Byte) for the Class byte of the command APDU o “ins”: 2 hexadecimal characters (1 Byte) for the Instruction byte of the command APDU. o “p1”: 2 hexadecimal (1 Byte) characters for the P1 byte of the command APDU. o “p2”: 2 hexadecimal characters (1 Byte) for the P2 byte of the command APDU. o “cmdData”: hexadecimal characters for the data to be sent in the command APDU. If a command does not need data to be sent the “cmdData” attribute is absent • node with “sw” attribute. The “sw” attribute is composed of 4 hexadecimal characters. It value shall be “9000” © 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. Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements v1.0.r Page 6/14 Figure 3-2—PICC Configuration File Format © 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. Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements v1.0.r 4 Test Application. Page 7/14 4.1 General Requirements The RF, Analogue and Digital parameters (for example VOV, t1, t2, t3, t4, mi, tR, tF, tP, tRESET, etc.) shall not vary from the ones defined in Device Test Environment functions, they shall remain identical to those implemented into the Product that will be deployed in the field. 4.2 Test Preparation The test application shall be installed on the Reduced Range product prior to the start of the Interoperability Test. PICC Configuration files and AIDList file will be installed by Testing Laboratory on the Reduced Range product under test before to start test session. The Product provider shall supply to Testing Laboratories clear instructions on how to install and operate the testing application. © 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. Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements v1.0.r Page 8/14 4.3 Test Application flow The test Application shall support 2 modes o Loop mode: ▪ Application start when operator push “Start” Button ▪ Application is in a loop mode until operator decide to stop the Application. Figure 4-1—Loop mode Application flow © 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. Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements v1.0.r o Single mode: Application automatically stop after 1 transaction (Pass or Fail) Page 9/14 Figure 4-2—Single mode Application flow The single mode can be used by Testing Laboratory to verify that the application can correctly operate with all the PTP cards defined by EMVCo. In Single mode the test application shall create a log file accessible to Testing Laboratory. 4.4 Application processing Following the “ACTIVATION” the test application shall process the Card: 1. Select PPSE Command. The contactless card has a PPSE that contains a list of products and applications selectable over the contactless interface. To recover the list applications (ADF Names), Test Application shall send a SELECT PPSE command (refer to section A.2). In case multiple ADF Names are present in Card response, the test application shall use the first ADF Name in the list returned by the card that is present in the AID List (refer to section 3.1). © 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. Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements v1.0.r Page 10/14 The Test Application shall compare consecutively the ADF Names returned by the card with the AIDs present in AIDList file: If the ADF Name returned by the card has the same length and value as an AID listed in the AIDList file(full match), or if the ADF Name returned by the card begins with an AID listed in the AIDList file (partial match), then the ADF Name returned by the card shall be selected by the Test Application. Otherwise the Test Application shall compare the next ADF Name returned by the card with the AIDs listed in the AIDList file. 2. Selection of the Transaction flow: The test application sends a SELECT AID command (refer to section A.1) using the AID selected above. The application will be able to select the PICC configuration file after receiving the response to SELECT Command. The test application shall select automatically the PICC Configuration file to be used depending on the ‘DF Name and the PDOL (if multiple configuration file are defined for the selected AID) returned to the SELECT command. PICC configuration file shall be selected using its name (refer to section 3.2.1). Figure 4-3—Transaction Flow selection © 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. Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements v1.0.r Page 11/14 3. Transaction processing. After the SELECT command the test application shall send consecutively all the CAPDUs defined in the selected PICC configuration file. For each R-APDU received from the PICC the application verifies that the Status Word is correct (’90 00’). No verification of the data received is requested. A transaction is PASS if a correct Status Word (’90 00’) is received for each R-APDU received. Note: The application will keep in memory a test flow until it receives a different DF Name or a different PDOL in the answer to SELECT Command. No need to reopen or reload the PICC configuration file if no change. 4.5 Application additional requirements The test application shall follow the following requirements: • Application shall support both Type A and Type B • Screen shall remain ON during the tests. Reduced Range product shall not enter in sleep mode. • The Application shall provide 2 result indicators: o Message on the screen o Sound Indicator: 2 different sound indicators are necessary ▪ BIP 1: PASS ▪ BIP 2: FAIL The two different sound indicators shall be easily distinguishable. The sound indicator should be defined by “.wav” files or equivalent to allow customization. Product Provider may discuss with Testing laboratory. The delay between the reception of last R-APDU from the PTP Card and the generation of the result sound indicator shall be as short as possible and shall not exceed 500ms. • The test application shall complete the transaction in a reasonable timeframe. • Test application shall record the log of the last transaction in .txt format in “single mode”. © 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. Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements v1.0.r A. Commands A.1.Select Command The Select command shall be coded as described in following Table: Code CLA INS P1 P2 Lc Data Value ‘00’ ‘A4’ ‘04’ ‘00’ '05'–'10' File name – AID to select Le Any value (disregarded) E.g. Maximum Length of data to be returned (‘00’ by default) The Response from the PICC to SELECT AID command is coded as followed Page 12/14 © 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. Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements v1.0.r Page 13/14 A.2.Select PPSE The contactless card has a PPSE that contains a list of products and applications selectable over the contactless interface. To recover the list of products and applications, Test application shall send a SELECT (PPSE) command. The SELECT command is defined in section A.1. The SELECT PPSE command shall be coded as Followed: Code Value CLA ‘00’ INS ‘A4’ P1 ‘04’ P2 ‘00’ Lc Data '0E’ ‘32 50 41 59 2E 53 59 53 2E 44 44 46 30 31 (2PAY.SYS.DDF01) ‘ Le Any value (disregarded) E.g. Maximum Length of data to be returned (‘00’ by default) The response to the to the SELECT PPSE contains a FCI defined as follows: © 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. Contactless Terminal Level 1 Type Approval Reduced Range Interoperability Test Application Requirements v1.0.r Page 14/14 *** 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.