PCI Watch

Tracking changes across the Payment Card Industry

Contact Terminal Level 1 Implementation Conformance Statement 1.0a

v1.0a Type Approval Forms
Contact Acceptance Device

Export Form Data Import Form Data Level 1 IFM – Implementation Conformance Statement Version 41..30da 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 products submitted to receive EMVCo Contact Level 1 testing and approval. The form shall be completed in its entirety, even for items that are indicated as outside the scope of the EMV® specification. 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. If more than one IFM design is identified in the IUT, a separate ICS is required for each IFM and separate type approval for each design applies.

/ 13

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 C I.3.2 – For any submission except Initial, please provide the EMVCo letter of approval reference number of the previously approved product (if already granted) M I.3.3 – Is this ICS a replacement of a previously accepted ICS? Yes No 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 4 – IFM Identification This part must be completed with the information to be used within the EMVCo approval letter, if the IFM is approved. Designation Name Version I.4.1 – Name assigned by Vendor to uniquely identify the IFM (Mandatory – must be completed) I.4.2 – Name assigned by Vendor to uniquely identify this IFM hardware (Mandatory – must be completed) I.4.3 – Name assigned by Vendor to uniquely identify IFM software (Mandatory - must be completed) The field “Name assigned by Vendor to uniquely identify the IFM” shall be unique for the concerned Vendor. The combination of the two fields “Name assigned by Vendor to uniquely identify the IFM hardware” and ““Name assigned by Vendor to uniquely identify the IFM software” shall also form a unique combination for the concerned Vendor. / 13 5 – Terminal Identification If EMVCo approval is issued, the IFM identification information provided in this section will be used on the EMVCo letter of approval and posted on the EMVCo website. This identification information must agree with the information provided on the approval request letter and the test report submitted for EMVCo evaluation. Inconsistent identification information in these three documents may delay the approval process or may result in a decline for the approval request.

Description

Name Identifier Version (manufacturing code) I.5.1 – This is the device/terminal “Marketing name” within which the IFM was tested. This terminal name will appear on the letter of approval, in addition to the IFM name. 6 - Test Sample Identification of Each (serial number, production batch, date, etc., for each IFM submitted to testing. 1. 2. 3. 7 - Selection Method of the Test Samples I.7.1 – Describe the method you utilized to select the samples provided to the laboratory for type approval testing (e.g. production ready, or from the production line). Attachment Reference:

/ 13

Part II - IFM Implementation (General) 1 - IFM(s) II.1.1 – How many IFMs are in the IUT? II.1.2 – How many of these IFMs are accessible to a cardholder? II.1.3 – How many of these IFMs can be identified as an IFM in the IUT? II.1.4 – How many different IFM types (IFM name and version combinations) are present in the terminal? II.1.5 – For each of the above-mentioned IFM types, is the IFM type designed in conformity with the EMV Specification? (each IFM type needs its own ICS) II.1.6 – For each of the above-mentioned IFM types, what class does the IFM support, A or B? (an IFM shall support class A or B, but not both) II.1.7 – What is the minimum IFM ambient operating temperature allowed? °C (IFM should operate in a range of 5˚C to 40˚C) II.1.8 – What is the maximum IFM ambient operating temperature allowed? °C (IFM should operate in a range of 5˚C to 40˚C) II.1.9 – What is the max. Temperature inside the IFM(s) around the inserted ICC? °C (Tambient = maximum allowed; PICC = 250 mW) 2 - Identifying the IFM within the IUT II.2.1 – Please attach a description of how the IFM can be identified within the IUT (if the IUT is not the IFM itself): Attachment Reference: 3 - IFM Interface to the Rest of Terminal II.3.1 – Please describe the interface between the IFM and the rest of terminal: Attachment Reference: 4 - Test Software II.4.1 – Any laboratory requirements needed for testing including any software application required interfacing with the laboratory test equipment. Within the EMVCo documents this is referred to as an Upper Tester. Please explain and describe where the appropriate test software is located in the IUT, how it operates, and indicate its version: Attachment Reference:

/ 13

Part III – IFM 1 - Terminal Characteristics (Mechanical) III.1.1 – Please describe the contact footprint(s), the characteristics of the contacts (e.g., gliding contacts), location guides and clamps (if used), etc. (see EMV specifications, Book I, §5.2.2, “Dimensions and location of contacts”): Attachment Reference: 2 - Class III.2.1 – What class does the IFM support, A or B? (an IFM shall support class A or B, but not both) 3 - Frequency Characteristics of C3 III.3.1 – Clock operating Frequency of C3? (Please provide the value in MHz with 4 significant digits, i.e. 1 kHz precision) 4 - Electrical Characteristics of contact C6 III.4.1 – Is the contact C6 connected to the IFM or isolated? (Select only one box below) C6 is electrically isolated from the IFM C6 is connected to the IFM (For existing class A terminals only) III.4.2 – When C6 is connected, please describe its implemented electrical contact characteristics (see EMV, Book I and EMV Specification Bulletin 216, Third Edition, March 2020, §5.2.3, “Contact Assignment” and §5.3.3 “Contact C6”): Attachment Reference: 5 - Collision Detection III.5.1 – If a collision detection function is implemented, please describe the behaviour of the IFM when a collision occurs (ICC and terminal are transmitting at the same time) (see EMV specifications, Book I, §5.5.2, “input/output”): Attachment Reference: 6 - Recovery Behaviour on Short Circuit III.6.1 – Please describe the behaviour of the IFM or terminal if a short circuit occurs on the ICC contacts (includes long-term short circuit and the recovery behaviour after removal of the short circuit, as well as time parameters): Attachment Reference:

/ 13

7 - ICC Insertion/Withdrawal Functionality III.7.1 – Please indicate the ICC insertion/withdrawal functionality of the IFM in the IFM that shall be tested and approved: III.7.1.1 – Manual ICC insertion/withdrawal(ICC directly accessible and removable at all times) III.7.1.2 – Manual ICC insertion/withdrawal(ICC directly accessible at all times but mechanically locked when electrically activated) III.7.1.3 – Combination of manual and automatic ICC insertion/withdrawal(ICC directly accessible at all times but mechanically locked when electrically activated) III.7.1.4 – Combination of manual and automatic ICC insertion/withdrawal (ICC not directly accessible [completely inside the IFM]) III.7.2 – If you cannot check one of the insertion/withdrawal functionality above, please describe it in an attachment: Attachment Reference: III.7.3 – If the ICC is mechanically locked or completely located inside the IFM (while it is electrically activated), please describe how it is accessible to the cardholder at any time (see EMV specifications, Book I, §5.2, “Mechanical Characteristics of the ICC”). Attachment Reference: III.7.4 – When applicable, please describe how the lock mechanism for an inserted ICC can be overridden for test purposes (during the testing, a test probe must be inserted and withdrawn several times without manual intervention): Attachment Reference: III.7.5 – With drawings and directions, please describe exactly how an ICC must be inserted and withdrawn from the IFM of the IUT during type approval tests: Attachment Reference:

/ 13

8 - Power Supply III.8.1 – Please indicate the IUT power supply requirements: III.8.1.1 – Battery-operated IUT (The battery is a source of power to the IUT) III.8.1.1.1 – Type of batteries required (Please specify an established standard type whenever possible) III.8.1.1.2 – Nominal voltage of batteries required V III.8.1.1.3 – Minimum voltage of battery for correct operation V III.8.1.1.4 – Maximum voltage of battery for correct operation V III.8.1.1.5 – If the IFM is powered only by batteries, are these batteries located in a sealed compartment, that cannot be accessed without risking to damage the IFM casing ? (Note: Examples of compartments that are not sealed: those that may be opened using a screwdriver or similar simple hand-held tool, by sliding the battery out of the casing, by unlocking a lever, latch or lock, by pressing a release button, etc. Examples of compartments that are sealed: those permanently glued to the housing, molded in one piece, or soldered in place). III.8.1.2 – DC-operated IUT (The DC power supply is a source of power to the IUT) III.8.1.2.1 – Nominal voltage of DC supply required V III.8.1.2.2 – Minimum voltage of DC supply for correct operation V III.8.1.2.3 – Maximum voltage of DC supply for correct operation V III.8.1.2.4 – Maximum current of DC supply required A III.8.1.3 – Mains-operated IUT (The main AC power supply is a source of power to the IUT) III.8.1.3.1 – Nominal voltage of AC supply required V III.8.1.3.2 – Minimum voltage of AC supply for correct operation V III.8.1.3.3 – Maximum voltage of AC supply for correct operation V III.8.1.3.4 – Nominal frequency of AC supply Hz III.8.1.4 – Combination of battery and DC or mains III.8.1.4.1 – If yes, please describe precisely how the IUT is powered and attach a diagram: III.8.1.4.2 – If yes, Please describe what happens when the primary source of power is removed from the IUT during operation (with an ICC inserted):

/ 13

Part IV – Implemented Protocol Types Protocol type IV 1 - ATR IV 2 - Character protocol T=0 IV 3 - Block protocol T=1 IV 4 - Transport of APDUs by T=0 IV 5 - Transport of APDUs by T=1 Reference EMV, §8 EMV, §9.2.2 EMV, §9.2.4 EMV, §9.3.1 EMV, §9.3.2 Status m m m m m Support (Y/N) Part V – General Protocol Information Parameter V 1 - Does the terminal reject an ICC returning TCK in a T=0 only ATR? V 2 - Does the terminal continue the card session as soon as all characters indicated in T0 and/or TDi have been received (i.e. does it ignore any character sent by an ICC after all characters indicated in T0 and/or TDi have been received)? V 3 - Does the IFM support the Implicit negotiable mode (without m PPS) V 4 - Does the IFM support explicit negotiable mode (with PPS) o* Note: Referred to as V-7 in IFM Prot TC v4.3c-20180425 V.4.1 – If explicit negotiable mode is supported, indicate TA1 c* bit 8 to 5 values (Fi) that may cause the terminal to initiate proprietary negotiations when TA2 is absent (negotiable mode) Reference EMV, §8.3.4 EMV, §8.3.4 Supported EMV, §8.3.3.1 EMV, §8.3.3.1 EMV, §8.3.3.1 0 (372) 2 (558) 3 (744) 4 (1116) 5 (1488) 6 (1860) 9 (512) A (768) B (1024) C (1536) D (2048) V.4.2 – If explicit negotiable mode is supported, indicate TA1 bit 4 to 1 values (Di) that may cause the terminal to initiate proprietary negotiations when TA2 is absent (negotiable mode) Note: Referred to as V-7.2 in IFM Prot TC v4.3c-20180425 c* EMV, §8.3.3.1 2 (2) 3 (4) 4 (8) 5 (16) 6 (32) 7 (64) 8 (12) 9 (20) V.4.3 – If explicit negotiable mode is supported, indicate TA1 bit 8 to 5 and bit 4 to 1 COMBINATIONs in hexadecimal that cause the terminal to initiate proprietary negotiations when TA2 is absent (negotiable mode) *: outside the scope of the EMV specification c* EMV, §8.3.3.1 V240117 Copyright ©2007-2024 EMVCo, LLC. All rights reserved. ICS IFM L1 - version 1.0a

/ 13 ICS Reference Number:

Part VI – Answer to Reset 1 - Parameter Values for ATR Parameter Reference Status Values VI.1.1 – When TA2 is returned with b5=0 (specific mode, parameters defined by the interface bytes), is the IFM able to support TA1 values that are not in the range ‘11’ to ‘13’? VI.1.1.1 – If yes, what values of TA1 (different from ‘11’, ‘12’, ‘13’) are supported? VI.1.1.2 – If yes, is ‘D6’ a value of TA1 supported? VI.1.2 – Is the IFM able to support TC2 values different from ‘0A’? VI.1.2.1 – If yes, what values of TC2 (different from ‘0A’) are supported? VI.1.2.2 – If yes, are ‘01’, ‘09’ and/or ‘0B’ values of TC2 supported? EMV, §8.3.3.1 EMV, §8.3.3.1 EMV, §8.3.3.1 EMV, §8.3.3.7 EMV, §8.3.3.7 EMV, §8.3.3.7 Allowed o ‘Yes’ or ‘No’ Supported c1 “00” … “10” and “14” … “FF” c1 ‘Yes’ or ‘No’ o ‘Yes’ or ‘No’ c2 “01” … ”09” and “0B” … ”FF” c2 “01”, “09”, “0B” 01 09 0B c1: depends on response to VI.1.1. c2: depends on response to VI.1.2. * Provided the values are consistent with characters actually returned. ** Shaded boxes indicate a prohibited capability.

/ 13

Part VII – Protocol T=1 1 - Implemented Features Function Reference Status Supported VII.1.1 – Does the IFM accept Blocks with Node addressing: NAD ≠ EMV, §9.2.4.1.1 ’00’

  • VII.1.2 – Behaviour on BWT excess (when IFM receives no response to an I Block, R-Block or S(Response)) EMV, §9.2.5.1 m VII.1.3 – Behaviour on BWT excess (when IFM receives no response to an S(request)) EMV, §9.2.5.1 m VII.1.4 – Behaviour on WTX excess (when IFM receives no response to an I-Block, R-Block or S(Response)) EMV, §9.2.5.1 m VII.1.5 – Behaviour on CWT excess (when IFM receives no response to an I-Block, R-Block or S(Response)) EMV, §9.2.5.1 m VII.1.6 – Behaviour on CWT excess (when IFM receives no response to an S(request)) EMV, §9.2.5.1 m VII.1.7 – Behaviour on I-Block with LEN = ‘FF’ but actual length of the INF part of the block is inferior to 255 EMV, §9.2.5.1 m 2 - Block Types Block Reference Status Supported VII.2.1 – Can the IFM send an S(RESYNCH request)? VII.2.1.1 – If yes, is the S(RESYNC request) ISO compliant or proprietary? VII.2.1.2 – If yes, can the IFM receive a S(RESYNCH response)? VII.2.2 – Does the IFM support a transaction abortion mechanism for proprietary reasons? c1: depends on response to VII.2.1. EMV, §9.2.5.1 / 8. AND NOTE EMV, §9.2.5.1 / 8. AND NOTE EMV, §9.2.5.1 / 8. NOTE EMV, §9.2.5.1 / 9. AND NOTE o c1 c1 o* 3 - Parameter Values for T=1 Parameter Reference Status VII.3.1 – Does the IFM support EMV, §9.2.4.1.1 LEN of INF in the range [‘0’, REFERENCE SPECIFICATION …, ‘254’] Allowed m ‘Yes’ or ‘No’ Values Supported / 13 VIII - Digital Signatures Product Provider I hereby declare that the above referenced product currently is and will remain in compliance with the above referenced EMV specification for all mandatory and supported optional requirements. Comments Signature Laboratory I hereby declare that this ICS document has been reviewed, and that all product information is consistent throughout the ICS. Comments Signature EMVCo Approval Secretariat Signature / 13 IX Instructions The ICS is designed as a fill-in-the-blanks questionnaire wherever possible. It must be filled out by the IFM provider. Some implemented features and specifications must be briefly described (text and schematics). For other features, especially the implemented protocols, values or a range of allowed values must be given. Beside questions on technical aspects of the implementation relating to the EMV Specification and the testing itself, the ICS also contains information regarding the IFM for the purpose of accurately identifying the IFM on an approval letter.
  • Administrative Information of shall be filled:
  • Company Name and registration Number
  • Laboratory Name and Registration Number
  • IFM and Terminal Information of shall be filled Additional pages (attachments with descriptions, drawings, and schematics) shall refer to the section to which they correspond, and vice versa. Additional documents (e.g., data sheets) shall be attached if necessary, and a list of all attached documents shall be added to the ICS. / 13 X Notation The following legend applies to all subsequent tables:
  • Optional m Mandatory p Prohibited na Not applicable c Conditional the capability may be implemented as an option the capability is required in all implementations the capability must not be used no requirement can be expressed about this capability requirement depends on the selection of other optional or conditional items / 13