PCI Watch

Tracking changes across the Payment Card Industry

Contactless Level 1 Reduced Range PCD – Implementation Conformance Statement (ICS)

v3.2a Type Approval Forms
Contactless Acceptance Device

Export Form Data Import Form Data Level 1 Reduced Range PCD – Implementation Conformance Statement Version 3.2a ICS Reference Number and Validity Period (for EMVCo administrative use only) ICS Reference Number: Valid from: Valid to: Notice: This ICS form shall be completed for PCDs submitted for Reduced Range PCD Type Approval. The form shall be completed in its entirety. All Yes and No questions shall be answered. If a feature/option is NOT supported, i.e. a question is answered “No”, the sub- questions for that feature/question shall be left blank. Part I - Administrative 1 - Product provider identification M I.1.1 – Company Legal Name: (As listed on the Letter of Registration) M I.1.2 – EMVCo Registration Number: 2 - Laboratory identification M I.2.1 – Company Legal Name: M I.2.2 – EMVCo Registration Number: 3 - ICS submission type M I.3.1 – Select submission type Inission M I.3.2 – Product submitted for M I.3.3 – Is this ICS a replacement Yes No of a previously accepted ICS? C I.3.3.1 – If Yes. please provide the reference number of the previously accepted ICS C I.3.3.2 – If Yes, please provide the reason for replacing the ICS C I.3.3.3 – If Yes, please provide details of ICS replacement

Number:

of 17

Part II – Product identification 1 - PCD identification (PCD Under Test) Name II.1.1 – PCD–ID1 II.1.2 – PCD hardware-ID2 II.1.3 – PCD firmware/SoftwareID3 II.1.4 – Contactless Controller (CLF) Hardware II.1.5 – Contactless Chip Firmware II.1.6 – Middleware/CLF driver software name II.1.7 – Please confirm that the provided identifications link unambiguously to one and only one PCD configuration definition, covering all functionalities required by EMV Contactless Interface Specification (including the antenna). II.1.8 – Please confirm that those mentioned identifications will serve as basis against which any further minor change will be tracked. II.1.9 – Is the product an OEM product? Version Yes Yes Yes No 2 - Device / Terminal within the Reduced Range PCD will be tested (As tested In) Commercial Name4 Technical Name (manufacturing code) Version II.2.1 – Device / Terminal Reader II.2.2 – Please confirm that the provided identification Yes links unambiguously to one and only one product configuration definition (including the antenna).

Number:

of 17

Part II – Product identification Sample 15 Sample 25 Sample 35 Serial number Serial number Serial number 3 - Samples selection method6 II.3.1 – Reference attached document 1 Provide the identification (name/identifier + version) you have assigned to uniquely identify the PCD for the concerned vendor. This identification shall define the combination of PCD hardware and firmware. 2 Provide the identification (name/identifier + version) you have assigned to uniquely identify the PCD hardware for the concerned vendor. This identification shall define the full set of hardware components implementing EMV Contactless Specifications (analogue + digital). The antenna shall be part of the PCD hardware. The combination of the "PCD Hardware-ID" and of the "PCD Firmware/Software-ID" shall also form a unique combination for the concerned Vendor. 3 Provide the identification (name/identifier + version) you have assigned to uniquely identify the PCD firmware for the concerned vendor. Identification shall define the full set of firmware components/modules implementing the EMV Contactless Specifications (analogue + digital). The combination of the "PCD Hardware-ID" and of the "PCD Firmware/Software-ID" shall also form a unique combination for the concerned Vendor. 4 Provide the “Commercial Name” of the Device / Terminal where the PCD is tested, as well as the Technical Name you have assigned to uniquely identify it. It is the so-called 'as tested in' reflecting the sample under test. 5 Provide identification of the specific Samples submitted for Type Approval. 6 Describe the method used to select the Samples submitted for Type Approval (e.g. from the production line).

Number:

of 17

Part III: Implementation information Yes No 1 - Digital characteristics Related to Requirements 9.2 – Polling. (9.2.1.1 to 9.2.1.7) III.1.1 – Does the PCD use proprietary commands other than EMV Contactless Specifications Type A and Type B commands during the polling loop? III.1.1.1 – If yes, please list all the other technologies supported by the PCD and describe how the different technologies work together. Please describe the full polling sequence(s) used to detect a cardholder device in the field included but not limited to the number of polling commands for each technology and intervals between the commands per polling cycle. Indicate the level of priority for the other technologies in comparison with Type A and Type B during a polling cycle. III.1.1.2 – If yes, for each other technology, is a reset required before or after the proprietary polling command? III.1.1.3 – If no, does the PCD suspend the Operating Field (as defined in section 3.2.10 of EMV Contactless Specifications) for a period of tSUSPEND after a polling cycle? Related to Section 9.1.1. Bullet 5 III.1.2 – When the PICC has been removed from the Operating Field at the end of a correct transaction, does the PCD reset the Operating Field (as defined in section 3.2.6 of EMV Contactless Specifications, wait the period of tPAUSE with unmodulated carrier and resume with the polling and collision detection. III.1.2.1 – If yes, please indicate the value of tPAUSE. III.1.2.2 – If no, please describe the behavior of the PCD when the PICC has been removed from the Operating Field at the end of correct transaction with details including timing values. Related to Requirements 10.14 – Exception Processing – PCD ( 10.3.5.9) III.1.3 – Please describe the behavior of the PCD when it has performed a reset of the Operating Field because no error recovery is possible during the half-duplex block transmission protocol. Value ms

Number: Comments

of 17

Part III: Implementation information Yes No Value Related to Requirement 9.5.0.1 – Transaction Completion III.1.4 – Does the PCD implement the removal procedure for transaction completion? Remark: The PCD shall implement at least one transaction completion procedure. Related to Requirement 9.5.0.1 – Transaction Completion III.1.5 – Does the PCD implement the PICC presence check procedure for transaction completion? Remark: The PCD shall implement at least one transaction completion procedure. Related to Requirement 10.1.5.1 –Legacy behavior support III.1.6 – Does the PCD implement a legacy behavior by accepting I-Blocks with b6 of PCB set to ‘1’? Related to Requirement 10.1.5.1 –Legacy behavior support III.1.7 – Does the PCD implement a legacy behavior by accepting R-Blocks with b2 of PCB set to ‘0’? Related to Requirement 10.1.5.1 –Legacy behavior support III.1.8 – Does the PCD implement legacy behavior by accepting S-Blocks with b1 of PCB set to ‘1’? Related to Requirement 10.3.2.2 – PCD chaining buffer size III.1.9 – What is the maximum FSC value supported by the PCD? Related to Requirement 4.7.3.3 – FSD value III.1.10 – What is the maximum frame size that the PCD can receive (FSD)? Bytes Bytes 2 - Support of Type A communication PICCs Related to Requirements 4.5 – Loaded State III.2.1 – Does the PCD resort to transmission error processing when it senses the carrier modulated for the first half of the bit duration and bit period does not start with the loaded state of the subcarrier? III.2.1.1 – If no, please describe the PCD behavior in this case. Comments

Number:

of 17

Part III: Implementation information Yes No Related to Requirements 4.20 – FDTA,PICC ( 4.8.1.1) III.2.2 – Does the PCD accept a Type A sequence received with a Frame Delay Time not aligned to the grid as defined in Figure 4.14, Table 4.2 and 4.3? III.2.2.1 – If yes, indicate after which commands or blocks is the FDT not aligned to the grid accepted. Related to Requirements 5.7 – Type A PICC Compliance with ISO/IEC 14443-4 ( 5.5.2.1) III.2.3 – Does the PCD support Type A PICCs not indicating conformity to ISO 14443-4 (i.e. SAK byte with b6 = (1)b)? Related to Requirements 5.12- Length Byte TL of the ATS ( 5.7.2.2) III.2.4 – Does the PCD support Type A PICCs returning an ATS of length greater than 20 bytes (i.e. ATS with the TL bytes having a value > ‘14’)? Related to Requirements 5.21 – Historical Bytes of the ATS ( 5.7.2.14) III.2.5 – Does the PCD support Type A PICCs returning an ATS with more than 15 Historical Bytes? Related to Requirements 5.16- Format Byte TA(1) of the ATS (5.7.2.8) III.2.6 – Does the PCD support Type A PICCs indicating support of other bit rates than 106 kbps in both directions (i.e. ATS with TA(1) different from ‘00’, ‘08’, ‘80’ or ‘88’)? III.2.6.1 – If yes, please indicate the supported bit rates (for each direction) and describe the behaviour of the PCD when a Type A PICC indicates support of other bit rates than 106 kbps. III.2.6.2 – If no, please confirm that the PCD initiates exception processing for Type A PICCs indicating support of other bit rates than 106 kbps in any direction. Related to Requirement 5.8.1.1 – PPS Command III.2.7 – May the PCD send a PPS command when the PICC indicates support of bit rates different from 106 kbit/s in the TA(1) of the ATS? III.2.7.1 – If yes, when does the PCD send a the PPS command? Value

Number: Comments

of 17

Part III: Implementation information Yes No 3 - Support of Type B communication PICCs Related to Requirements 4.15 – End of Sequence PICC->PCD – Type B (4.6.2.5) III.3.1 – Does the PCD resort to transmission error processing when the PICC maintains the subcarrier on for a time greater than tFSOFF after the EoS)? III.3.1.1 – If no, please describe the PCD behavior in this case. Related to Requirements 4.3 – Synchronization PICC->PCD – Type B (4.3.2.3) III.3.2 – Does the PCD accept a Type B sequence received with a synchronization time TR1 < TR1MIN (i.e. subcarrier with no phase transition, sent for a duration less than TR1MIN)? III.3.2.1 – If yes, please indicate the minimum TR1 accepted by the PCD. III.3.2.2 – If yes, does the PCD support the same minimum value of TR1 from one command to another and from one transaction to another? III.3.2.2.1 – If yes, what is the value ? III.3.2.2.2 – If no (the supported minimum TR1 changes between commands and/or transactions), what are the limits and variations? Related to Requirements 4.3 – Synchronization PICC->PCD – Type B (4.3.2.3) III.3.3 – Does the PCD accept a Type B sequence received with a synchronization time TR1 > TR1MAX (i.e. subcarrier with no phase transition, sent for a duration greater than TR1MAX)? III.3.3.1 – If yes, please indicate the maximum TR1 accepted by the PCD. Value 1/fc 1/fc 1/fc Comments

Number:

of 17

Part III: Implementation information Yes No Related to Requirements 6.8 –Byte Rates supported by the PICC (6.3.2.4) III.3.4 – Does the PCD support Type B PICCs indicating support of other bit rates than 106 kbps in both directions (i.e. ATQB with Bit_Rate_Capability different from ‘00’, ‘08’, ‘80’ or ‘88’)? III.3.4.1 – If yes, please indicate the supported bit rates (for each direction) and describe the behaviour of the PCD when a Type B PICC indicates support of other bit rates than 106kbps. III.3.4.2 – If no, please confirm that the PCD initiates exception processing for Type B PICCs indicating support of other bit rates than 106 kbps in any direction. Related to Requirements 6.22 – Setting the Bit Rate for Type B III.3.5 – Does the PCD establish bit rates higher than 106 kbps when working with Type B PICCs indicating support of bit rates higher than 106 kbps? III.3.5.1 – If yes, please describe the behavior of the PCD when a Type B PICC indicates support of other bit rates than 106 kbps. Related to Requirements 6.12 – Type B Protocol Type supported by the PICC ( 6.3.2.8) III.3.6 – Does the PCD support Type B PICCs not indicating conformity to ISO 14443-4 (i.e. ATQB with Protocol Type ≠ (0001)Bb)? Value 4 - Support of dual PICCs: Type A and Type B Related to Requirements 10.3 – Power Level Indication III.4.1 – Does the PCD support a power level indication different from (00)b in the received S(WTX) Request blocks (i.e. bits ‘b8b7’ of the INF field of the S(WTX) Request block different from (00)b? Related to Requirements 10.11 – Block Handling Rules for the PCD ( 10.3.4.3) III.4.2 – When an R(ACK) block with a block number not equal to the PCD’s current block number is received not in response to an R(NAK) block sent to notify a time out, does the PCD re-transmit the last I-block)? III.4.2.1 – If no, please describe the behavior.

Number: Comments

of 17

Part III: Implementation information Yes No Related to Requirements 10.8 – Block Sizes during Chaining III.4.3 – When the PCD sends a chain of Iblocks, can the INF field of the last block sent by the PCD (i.e. the block not indicating chaining) have a length equal to zero? Remark: An I-Block sent by a PCD cannot have an INF field length equal to zero if indicating chaining. III.4.3.1 – If yes, please describe the behavior. Value Comments

Number:

of 17

Part IV: Operational information Yes No 1 - Device Test Environment IV.1.1 – Describe the installation and operation of the Device Test Environment submitted with the Samples, including the location and version of the test applications (Loop-Back). 2 - Power supply Yes No IV.2.1 – Is it a batteryoperated Product? IV.2.1.1 – If yes, is the battery the only source of power to the Terminal or Card Reader? IV.2.1.2 – If battery operated, what type of batteries are required (Please specify an established standard type whenever possible)? IV.2.1.3 – Nominal voltage of batteries required? IV.2.2 – Is it a DC-operated Product? IV.2.2.1 – If yes, is the DC power the only source of power to the Terminal or Card Reader? IV.2.2.2 – What is the nominal voltage of the DC supply required? IV.2.2.3 – What is the nominal current of DC supply required? Value Value V V A Comments Comments

Number:

of 17

Part IV: Operational information Yes No IV.2.3 – Is it an ACoperated Product? IV.2.3.1 – If yes, is the AC power the only source of power to the Terminal or Card Reader? IV.2.3.2 – What is the nominal voltage of AC supply required? IV.2.3.3 – What is the nominal frequency of AC supply required? IV.2.4 – Is a combination of battery and DC or battery and AC possible? IV.2.4.1 – If yes, please describe precisely how the Product is powered and attach a diagram Value V Hz Comments IV.2.4.2 – Please describe what happens when the primary source of power is removed from the Product during operations (during a transaction with a PICC).

Number:

of 17

Part V - Background information 1 - Architecture V.1.1 – Please describe the architecture of antenna and PCD/Terminal/Card Reader. Yes No Value Comments

Number:

of 17

Part V - Background information 2 – Testing information V.2.1 – Please provide an unambiguous diagram providing the antenna size and location. Yes No Value Comments V.2.2 – Please provide an unambiguous diagram providing the Reference Mark position. V.2.3 – Please provide an unambiguous diagram defining Product Landing Plane. V.2.4 – Please provide an unambiguous diagram defining the φ=0 axis during testing.

Number:

of 17

Part V - Background information 3 - Landing plane shape V.3.1 – If the Product has an uneven convex surface, please provide clearly the Z axis with a picture Yes No Value Comments V.3.2 – If a Product is concave or if a Product is a type of concave device because it has a ridge in its perimeter that does not permit a flat Test PICC to fit properly against its actual level 0 surface, please indicates clearly the level 0 surface for the PICC with a picture

Number:

of 17

Part VI – Digital signatures 1 - Product provider I hereby declare that the referenced product information contained in this Implementation Conformance Statement for Reduced Range PCD Level 1 Type Approval is currently in conformity with the Reduced Range PCD Acceptance Criteria as defined in: Terminal Type Approval Bulletin No.276: Reduced Range Devices Acceptance Criteria. First Edition, April 2024. Comments Signature 2 - Laboratory I hereby declare that this ICS document has been reviewed, and that all product information is consistent throughout the ICS. Comments Signature 3 - EMVCo Approval Secretariat Signature

Number:

of 17

Part VII - Instructions The Implementation Conformance Statement – Level 1 (ICS-L1)

  • describes vendor implementation choices and how the Reduced Range product implements EMV Contactless Level 1 Specifications, including optional elements,
  • allows a vendor to record precise details of the PCD embedded in their Samples submitted to testing,
  • provides Test Laboratories with basic technical information to facilitate testing,
  • enables EMVCo to register product details for the PCD Type Approval. The description of the options selected by the vendor enables EMVCo and the Test Laboratory to identify and run the appropriate PCD Type Approval tests on the PCD. The ICS consists of the following parts, related to the different nature of the information requested: Identification information Information about the EMVCo registration of the vendor and Information about the Vendor representative for PCD Type Approval. Unambiguous identification information of the PCD, its hardware and firmware, as well as the samples submitted for testing. This information will be used on the EMVCo PCD LoA. Remark: Inconsistent identification information across different documents may delay the test report assessment process or may result in a decline of a LoA request. Implementation information Specific information on how the vendor has implemented the specifications into the PCD. Some relate to options taken in EMV Contactless Specifications and other relate to PCD behaviors, chosen by the Vendor, and which are considered as out of scope of EMV Contactless Specifications (e.g.: PCD behavior following removal or an excess of error). Operational information Specific information on how the device and the Device Test Environment provided by the Vendor shall be configured and operate to perform the appropriate tests. Background information Detailed information on the PCD and on the Terminal/Card Reader architecture. This information is helpful to the Test Laboratory as an input for a test session. The vendor shall complete the ICS form before sending it to the Test Laboratory. Additional information submitted as part of an ICS shall comply with the following rules:
  • All documents supplied shall be properly identified and controlled using footers on each page with the following information: - a document ID number generated by the vendor’s documentation numbering system, - a date referring to the design of the samples submitted for testing.
  • Additional pages (attachments with descriptions, drawings, and schematics) shall refer to the section of the ICS to which they correspond, and vice versa, and shall be included in the page count of the document,
  • Additional documents (e.g. data sheets) shall be attached if necessary, and a list of all attached documents shall be added to the ICS. Number: of 17 This ICS is only valid if it is signed by the vendor. By signing, the vendor confirms that the ICS form contains all the necessary information regarding the PCD, the Terminal or Card Reader in which it will be tested, and its conformance to the referenced specifications. IMPORTANT: An ICS is only valid for one specific Proximity Coupling Device implemented in one specific contactless product. Therefore: 1- if, for instance, a PCD can be used with two antennae, it shall be considered as two different PCDs and a separate ICS – L1 is required for each PCD. 2- if during testing, some tests fail and the vendor need to change the design of the PCD or of the Terminal or Card Reader in which it is submitted, the relevant product information declared in the ICS shall be updated to link unambiguously to the modified design. Number: of 17