EMVCo ICC Level 1 Implementation Conformance Statement

v4.3c Type Approval Forms
ChipContact Card

EMV Co ICC Level 1 Implementation Conformance Statement ICS Reference Number ICS Reference Number: Notice: This ICS form shall be co mpleted for ICC s submitted f o r EMV Contact Level 1 evaluation. T he 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. A

  • Administrative Product Provider Identification A. seq A1 1. seq A2 r 1 1
  • Company Name: FORMTEXT           A. seq A1 c 1. seq A2 2 – EMVCo Registration Number: FORMTEXT           ICS Version N umber A. seq A1 2. seq A2 r 1 1
  • Is this ICS an update to a previously accepted ICS? FORMCHECKBOX Yes FORMCHECKBOX No A. seq A1 c 2. seq A2 2
  • If y es, p lease provide the reference number of the previously accepted ICS FORMTEXT           A. seq A1 c 2. seq A2 3
  • If y es, p lease provide the reason for updating the ICS FORMTEXT           Product Specification & Test Cases

References

Name Version Number Release Date A. seq A1 3. seq A2 r 1 1

  • EMV Contact Specification FORMTEXT           FORMTEXT           FORMTEXT           A. seq A1 c 3. seq A2 2
  • EMV Contact Bulletins (list all applicable) FORMTEXT           FORMTEXT           FORMTEXT           Product and Chip Description s A. seq A1 4. seq A2 r 1 1
  • Product Name: FORMTEXT           A. seq A1 c 4. seq A2 2 – Who is the ICC Manufacturer who will be producing the test ICC s being submitted for testing ? FORMTEXT           A. seq A1 c 4. seq A2 3
  • Is this ICC based off of a previously approved ICC ? A. seq A1 c 4. seq A2 4 If yes, please provide the EMVCo reference number of the previously approved ICC FORMCHECKBOX Yes FORMCHECKBOX No FORMTEXT           A. seq A1 c 4. seq A2 5
  • Chip Provider: FORMTEXT           A. seq A1 c 4. seq A2 6
  • Chip Type or Iden ti fier: FORMTEXT           A. seq A1 c 4. seq A2 7
  • EMVCo IC C ompliance C ertificate reference number: D ate: FORMTEXT           FORMTEXT           A. seq A1 c 4. seq A2 8
  • Operating System Name: FORMTEXT           A. seq A1 c 4. seq A2 9
  • Operati ng System Version N umber: FORMTEXT           Chip Feature

Description

A. seq A1 c 4. seq A2 10

  • RAM size ( kB) FORMTEXT           A. seq A1 c 4. seq A2 11
  • ROM size ( kB) FORMTEXT           A. seq A1 c 4. seq A2 12 – Total EEPROM or Flash size ( kB) FORMTEXT           A. seq A1 c 4. seq A2 13 – Total EEPROM or Flash size ( kB)* FORMTEXT           A. seq A1 c 4. seq A2 14
  • CPU (8, 16 or 32 bit s etc) FORMTEXT           A. seq A1 c 4. seq A2 15
  • Crypto coprocessor present ? FORMCHECKBOX Yes FORMCHECKBOX No * Free EEPROM or Flash size available for initialization and personalization of the application (s) listed in " ref Application_on_the_PICC h * MERGEFORMAT Applications on the ICC " (excluding any memory utilized for the PICC operating system). Applications on the ICC Application Name Version Developer Reference specification with version AID or File ID Application Functional Options / Comments Payment applications ( please indicate the Payment System Application s and Issuer Product when available) FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           Other applications FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           Applications Interaction with the payment application (s) A. seq A1 5. seq A2 r 1 1
  • Do any other application ( s) interact with the payment application (s) ? FORMCHECKBOX Yes FORMCHECKBOX No A. seq A1 c 5. seq A2 2
  • If yes, describe how the other application ( s) interact (s) with the payment application (s) (Data shared, functions shared). P lease p rovide details below. FORMTEXT           Level 1 Electrical Characteristics L1 E. seq A1 r 1 1 – Sample information L1 E. seq A1 c 1. seq A2 r 1 1 – EMV Contact protocol type(s) supported? FORMCHECKBOX T=0 FORMCHECKBOX T=1 L1E. seq A1 2 – Card Class L1 E. seq A1 c 2. seq A2 2
  • Class A Supported? FORMCHECKBOX Yes FORMCHECKBOX No L1 E. seq A1 c 2. seq A2 3
  • Class B Supported? FORMCHECKBOX Yes FORMCHECKBOX No L1 E. seq A1 c 2. seq A2 4
  • Class C Supported? FORMCHECKBOX Yes FORMCHECKBOX No Level 1 Protocol Characteristics L1 P. seq A1 r 1 1 – ATR L1 P. seq A1 c 1. seq A2 r 1 1
  • Hex values returned by the ICC in response to cold reset: (Provide the longest historical byte string the card can support) FORMTEXT           L1P. seq A1 c 1. seq A2 c 1. seq A3 r 1 1 – Is TA2 retu rned with b5 = 0 ( specific mode, parameters defined by the interface bytes) in the Cold ATR ? FORMCHECKBOX Yes FORMCHECKBOX No L1P. seq A1 c 1. seq A2 c 1. seq A3 2 – Is the Cold ATR EMV Compatible ? An ATR is EMV compatible when it shall be accepted by at least one generation of EMV terminals. FORMCHECKBOX Yes FORMCHECKBOX No L1 P. seq A1 c 1. seq A2 c 1. seq A3 3 – Is the Cold ATR EMV Compliant ? FORMCHECKBOX Yes FORMCHECKBOX No L1 P. seq A1 c 1. seq A2 2
  • Hex values returned by the ICC in response to warm reset: (Provide the longest historical byte string the card can support) FORMTEXT           Transport Protocol L1 P. seq A1 2 – T = 0 supported? FORMCHECKBOX Yes FORMCHECKBOX No L1 P. seq A1 c 2. seq A2 r 1 1
  • Can the card issue procedure byte ‘60’ to request a Work Waiting Time extension? FORMCHECKBOX Yes FORMCHECKBOX No L1 P. seq A1 c 2. seq A2 c 1. seq A3 r 1 1
  • If yes, c an the card issue procedure byte ‘60’ to request a Work Waiting Time extension, during any command & response exchange of the payment application? FORMCHECKBOX Yes FORMCHECKBOX No L1 P. seq A1 c 2. seq A2 c 1. seq A3 c 1. seq A4 r 1 1
  • If y es, describe how and where in the transaction this will occur. Please provide details below: FORMTEXT           L1 P. seq A1 c 2. seq A2 c 1. seq A3 2
  • If y es, does the card issue procedure byte ‘60’ to request a Work Waiting Time extension, during ICC L1 testing ? FORMCHECKBOX Yes FORMCHECKBOX No L1 P. seq A1 3 – T = 1 supported? FORMCHECKBOX Yes FORMCHECKBOX No L1 P. seq A1 c 3. seq A2 r 1 1
  • Can the card issue a waiting time extension request, S (WTX request) block? FORMCHECKBOX Yes FORMCHECKBOX No L1 P. seq A1 c 3. seq A2 c 1. seq A3 r 1 1 – If yes, c an the card issue a waiting time extension request, S (WTX request) block, during any command & response exchange of the payment application? FORMCHECKBOX Yes FORMCHECKBOX No L1 P. seq A1 c 3. seq A2 c 1. seq A3 c 1. seq A4 r 1 1
  • If y es, describe how and where in the transaction this will occur. Please provide details below. FORMTEXT           L1 P. seq A1 c 3. seq A2 c 1. seq A3 2
  • If y es, does the card issue a waiting time extension request, S (WTX request) block, during ICC L1 testing ? FORMCHECKBOX Yes FORMCHECKBOX No L1 P. seq A1 c 3. seq A2 2
  • Value of IFSC FORMTEXT           L1 P. seq A1 c 3. seq A2 3
  • Can the ICC initiate chaining? FORMCHECKBOX Yes FORMCHECKBOX No L1P. seq A1 c 3. seq A2 c 3. seq A3 r 1 1
  • If yes, c an the card initiate chaining, during any command & response exchange of the payment application? FORMCHECKBOX Yes FORMCHECKBOX No L1P. seq A1 c 3. seq A2 c 3. seq A3 c 1. seq A4 r 1 1
  • If yes, describe how and where in the transaction this is initiated? Please provide details below: FORMTEXT           L1P. seq A1 c 3. seq A2 c 3. seq A3 2
  • If yes, does the card initiate chaining, during ICC L1 testing? FORMCHECKBOX Yes FORMCHECKBOX No L1 P. seq A1 c 3. seq A2 4
  • Can the ICC by means of chaining receive a command of length > IFSC ? FORMCHECKBOX Yes FORMCHECKBOX No L1 P. seq A1 c 3. seq A2 c 4. seq A3 r 1 1 – If yes, c an the ICC by means of chaining receive a command of length > IFSC, during any command & response exchange of the payment application? FORMCHECKBOX Yes FORMCHECKBOX No L1 P. seq A1 c 3. seq A2 c 4. seq A3 c 1. seq A4 r 1 1
  • If y es, specify such command and its response. Please provide details below: FORMTEXT           L1 P. seq A1 c 3. seq A2 c 4. seq A3 2
  • If y es, does the ICC by means of chaining receive a command of length > IFSC, during ICC L1 testing ? FORMCHECKBOX Yes FORMCHECKBOX No L1 P. seq A1 4
  • Dynamic Calculations FORMCHECKBOX Yes FORMCHECKBOX No L1 P. seq A1 c 4. seq A2 r 1 1
  • Can the ATR timings be impacted by any dynamic computation during the card reset? If Yes, please submit card(s) which display different timings. FORMCHECKBOX Yes FORMCHECKBOX No L1 P. seq A1 c 4. seq A2 c 1. seq A 3 r 1 1
  • If y es, please provide details below FORMTEXT           Level 2 Additional Information for preparation of Level 1 test tool L1 L2. seq A1 r 1 1 – PSE supported? FORMCHECKBOX Yes FORMCHECKBOX No L1 L2. seq A1 c 1. seq A2 r 1 1
  • FCI Data: returned by card FORMTEXT           L1 L2. seq A1 c 1. seq A2 2 – List of READ RECORD Commands and Responses: Command Response FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           FORMTEXT           L1 L2. seq A1 c 1. seq A2 3
  • SFI of Directory File and Record Number FORMTEXT           L1L2. seq A1 2 – Direct Select supported? FORMCHECKBOX Yes FORMCHECKBOX No L1 L2. seq A1 c 2. seq A2 r 1 1
  • EMV Application Name: FORMTEXT           L1 L2. seq A1 c 2. seq A2 2 – Is there any dynamic computations or internal check that could make variable the d u ration of the S E L E CT command? FORMCHECKBOX Yes FORMCHECKBOX No L1 L2. seq A1 c 2. seq A2 c 2. seq A3 r 1 1
  • If y es, describe the worst case FORMTEXT           L1 L2. seq A1 c 2. seq A2 3 – Is this EMV application implicitly selected by Cold Reset ? FORMCHECKBOX Yes FORMCHECKBOX No L1 L2. seq A1 c 2. seq A2 c 3. seq A3 r 1 1
  • If n o, please state ADF or Name of the application implicitly selected by Cold Reset, if any: FORMTEXT           L1 L2. seq A1 c 2. seq A2 4 – Is this EMV application implicitly selected by Warm Reset ? FORMCHECKBOX Yes FORMCHECKBOX No L1 L2. seq A1 c 2. seq A2 c 4. seq A3 r 1 1
  • If n o, please state ADF or Name of the application implicitly selected by Warm Reset, if any: FORMTEXT           L1L2. seq A1 3 – DYNAMIC DATA AUTHENTICATION supported? FORMCHECKBOX Yes FORMCHECKBOX No L1L2. seq A1 4
  • Enciphered PIN supported? FORMCHECKBOX Yes FORMCHECKBOX No L1 L2. seq A1 c 4. seq A2 r 1 1. - if y es, what is the max length of the private key? FORMTEXT           L1L2. seq A1 5 – 1st GENERATE AC L1 L2. seq A1 c 5. seq A2 r 1 1 - 1st GAC Command FORMTEXT           L1 L2. seq A1 c 5. seq A2 2
  • Maximum Response size (depending if CDA is supported) FORMTEXT           L1L2. seq A1 6 – 2nd GENERATE AC L1 L2. seq A1 c 6. seq A2 r 1 1 - 2nd GAC Command FORMTEXT           L1 L2. seq A1 c 6. seq A2 2
  • Maximum Response size (depending if CDA is supported) FORMTEXT           Level 1 Laboratory Identification ( Section t o be completed by the Lab) Company Name: FORMTEXT           EMVCo Registration Number: ( f or EMVCo Accredited Lab) FORMTEXT           ICS Reviewer’s Name: FORMTEXT           Title: FORMTEXT           Telephone Number: FORMTEXT           Fax Number: FORMTEXT           Email Address: FORMTEXT           Signature: FORMTEXT           Date: FORMTEXT           Comments FORMTEXT           Product Provider’s Officer Identification 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. Product Provider ’s Officer Name: FORMTEXT           Title: FORMTEXT           Signature: FORMTEXT           Date: FORMTEXT