Contactless Kernel C-4 Implementation Conformance Statement Version 2.10

v2.10 Type Approval Forms
Contactless Acceptance Device

Export Form Data Import Form Data Contactless Kernel C-4 Implementation Conformance Statement Version 22..1100 ICS Reference Number and Validity Period (for EMVCo administrative use only) ICS Reference Number: Valid from: Valid to: Notice: This ICS form must be completed for products implementing the Kernel C-4 submitted to receive EMVCo Contactless Product testing and compliance/approval. ICS form must be completed in its entirety and provided along with the corresponding “ICS

  • Contactless Product”. Part Ia
  • Administrative Product Provider Identification M Company Legal Name: (As listed on the Letter of Registration) M EMVCo Registration Number: Laboratory Identification M Company Legal Name: M EMVCo Registration Number: ICS Submission Type M Select submission type C For any submission except Initial, please provide the EMVCo letter of approval reference number of the previously approved product (if already granted) M Is this ICS a replacement of a previously accepted ICS? Yes No C If Yes. please provide the reference number of the previously accepted ICS C If Yes, please provide the reason for replacing the ICS C If Yes, please provide details of ICS replacement 14 Part 1b
  • Primary contact (for all C4 Contactless reader type approval communication) First name Last name Title Email Telephone Fax Company address Part 1c
  • EMVCo Level 1 Certification details EMV® Contactless Protocol Version Supported Level 1 Approval number Date EMV Contactless Protocol Certification Received Note: If device not yet submitted for EMV Contactless Protocol Certification, please provide date Certification will start on. EMV® is a registered trademark in the U.S. and other countries and an unregistered trademark elsewhere. The EMV trademark is owned by EMVCo. V230921 Copyright ©2023 EMVCo, LLC. All rights reserved. ICS Contactless Kernel C-4 – version 2.10 of 14 Part 2
  • Contactless reader product information Reader product type Terminal ID Device/terminal version Operating system/platform Note: PCD (proximity coupling device) details * PCD: The peripheral device of the terminal that uses inductive coupling to provide power to the PICC (and mobiles) and also to control the data exchange with the PICC. The PCD can be attached or integrated to a POS terminal. Provide unique identification number(s) assigned to identify the PCD embedded in the contactless product PCD ID PCD hardware/model PCD software name Software version [Enter the value] [Enter the value] Form factors supported If any other form factors supported, please specify C-4 kernel version Version number of any test application required for certification ID-1 card: [Enter the value] Micro-SD: [Enter the value] Mobile handset: 14 PIN entry device information PED (PIN Pad) details Is PIN entry supported? If yes, provide: PED Model name PED software version PED architecture Contactless reader details Reader serial number Version number Other information and comments 14 Part 3 – Implementation details Where the reader is hard-coded to support, or not support, particular functionality, please select ‘Yes’ or ‘No’ as appropriate in answer to the questions below. Where the reader can be configured (without modification to the C4 kernel or any referenced libraries) so as to support, or not support, particular functionality, please select ‘Configurable’. Readers which support such configuration are known as multiconfiguration kernel readers. The inclusion of any ‘Configurable’ answers will identify your reader as being able to be configured to support a variety of implementation requirements from your customers. Your reader will be tested using a variety of configurations to ensure that it is certified for implementation in any of the potential configurations that result from its capabilities. This provides the greatest flexibility for you and your clients whilst providing the necessary confidence in the product. Pre-Kernel processing Is zero amount allowed flag supported? Does the reader detect it will be unable to go online during Pre-PDOL processing? Note: Please choose ‘Configurable’ when the function can be disabled or enabled. 14 Contactless transaction types supported Are “Cash” transactions supported? (Application Usage Control) If the above answer is “Yes” or “Configurable”, then which type of “Cash” transactions are supported: Domestic International Are “Goods and Services” transactions supported? (Application Usage Control) If the above answer is “Yes” or “Configurable”, then which type of “Goods and Services” transactions are supported: Domestic International Are “ATM” transactions supported? (Application Usage Control) If the above answer is “Yes” or “Configurable”, then which type of “ATM” transactions are supported: Domestic International Note: Please choose ‘Configurable’ when the function can be disabled or enabled. 14 Terminal Type supported What type of operational control is supported by the Terminal? Operational Control: Financial Institution Merchant Cardholder Please specify the environment in which the Terminal will operate: Financial Institution Attended Unattended Is the Terminal type “Offline only”? Note: If the terminal type is “Offline with online capability”, then the only valid options are either “No” or “Configurable” Is the Terminal type “Online only”? Note: If the terminal type is “Offline with online capability”, then the only valid options are either “No” or “Configurable” Note: Please choose ‘Configurable’ when the function can be disabled or enabled. 14 Other Interfaces supported Is AEIPS contact interface supported? Note: Please choose ‘Configurable’ when the function can be disabled or enabled. Transaction Processing Capability The reader must be capable of processing transactions in EMV Partial online mode. Please confirm that this is the case by selecting ‘Yes’ from the drop-down list. Does the reader process transactions with Delayed authorisation? Which method does the reader use for generating the UN? Text (Please refer to the C-4 Kernel specification, Section 10.2.3.1 for details) Note: Please choose ‘Configurable’ when the function can be disabled or enabled. 14 Offline data authentication C4 requires that all Terminals must support SDA. The enablement of SDA support must be configurable for deployment. Please confirm that this is the case by selecting ‘Configurable’ from the dropdown list. C4 requires that all Terminals must support CDA. The enablement of CDA support must be configurable for deployment. Please confirm that this is the case by selecting ‘Configurable’ from the dropdown list. What is the maximum length of CA public 1948 bits key supported by the reader? Does the reader support revocation of an installed CA public key without the key’s removal? Does the reader detect CDA failure during Issuer or ICC public key recovery prior to the First Terminal Action Analysis? Note: Supporting offline data authentication is mandatory for ALL readers The enablement of offline data authentication must be configurable for deployment. Processing Restrictions Is exception list processing supported? 14 Cardholder verification The reader must be able to support Online PIN as a CV method. The enablement of Online PIN support must be configurable at deployment. Please confirm that this is the case by selecting ‘Configurable’ from the dropdown list. The reader must be able to support Signature as a CV method. The enablement of Signature support must be configurable at deployment. Please confirm that this is the case by selecting ‘Configurable’ from the dropdown list. The reader must be able to support Mobile CVM as a CV method. The enablement of Mobile CVM support must be configurable at deployment. Please confirm that this is the case by selecting ‘Configurable’ from the dropdown list. The reader must be able to support No CVM as a CV method. The enablement of No CVM support must be configurable at deployment. Please confirm that this is the case by selecting ‘Configurable’ from the dropdown list. The reader must be able to indicate that it is exempt from ‘No CVM control checks’. The enablement of ‘Exempt from no CVM checks’ must be configurable at deployment. Please confirm that this is the case by selecting ‘Configurable’ from the dropdown list. 14 The reader must support a configurable deactivation timer (1 to 3 seconds) for when restarting transactions due to Mobile CVM failure. The default value of this timer shall be 1.5 seconds. Please enter whether this is supported and the value set in seconds Timer length: 1.5 seconds 14 Printing receipts Is the reader connected to a terminal with Printing capability? Note: Integrated readers must have printing capability. Is the printing of Terminal Verification Results supported? Is the printing of Authorisation Response Codes supported? Does reader support Cardmember display messages? Membership-Related Data Processing Does the reader support membershiprelated data processing? Note: Please choose ‘Configurable’ when the function can be disabled or enabled. 14 Part 4
  • Declaration I confirm that all the information I have provided, in answer to the questions on this form, is correct and complete. Please confirm that the terminal does not support random transaction selection or velocity checking for contactless transactions. Please confirm that the terminal does not filter any data elements requested by the card. Name Title Signature Date Modular Architecture Declaration (To be completed if the reader employs a modular architecture) Please confirm that the terminal architecture identified above is structured using self-contained modules that can be updated independently. Please confirm that the terminal architecture identified above is capable of calculating a unique checksum value over the C4 kernel and any external libraries utilised in the processing of EMV transactions. Please confirm that the configuration of a terminal implementing the architecture identified above can be modified without the need for recompilation of the C4 kernel or any external libraries utilised in the processing of EMV transactions. Please confirm that you have supplied design documentation in accompaniment with this form which correctly and completely describes the structure and interfaces of the terminal architecture identified above. Please confirm that all products listed above implement the same terminal architecture as described in the accompanying design documentation. 14 Part 5
  • 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 unless noted as non-compliant on the attached sheets 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 14