EMVCo Common Payment Application Level 1 & Level 2 ... - Implementer Options L2.0.1 - Is EMV CPS...

V251116_1 Copyright ©2017 EMVCo, LLC. All rights reserved. of 18 ICS CPA – version 1.0l

EMVCo Common Payment Application

Level 1 & Level 2 Implementation Conformance Statement

Version 1.0l

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 card products submitted for CPA Level 1 & Level 2

Functional evaluations. 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.

A - Administrative

Product Provider Identification A.1.1 - Company Legal Name: (As listed on the Letter of Registration)

A.1.2 – EMVCo Registration Number:

Level 1 Protocol Laboratory Identification A.1.3 - Company Legal Name:


Level 2 Laboratory Identification A.1.5 - Company Legal Name:


ICS Submission Type A.2.1 - Select submission type <Select>

A.2.2 - For any submission except Initial, please provide the EMVCo letter of approval reference number of the previously approved product (if already granted)

A.2.3 - Is this ICS a replacement of a previously accepted ICS?

Yes No

A.2.4 - If Yes. please provide the reference number of the previously accepted ICS

A.2.5 - If Yes, please provide the reason for replacing the ICS

<Select>

A.2.6 - If Yes, please provide details of ICS replacement


Product Specification References

Name Version Number

Release Date

Released by

Audit Report Tracking Number

A.3.1 - EMV Specification

EMV Integrated Circuit Card Specifications for Payment Systems

A.3.2 – EMV Bulletins (list all applicable)

A.3.5 - Other Specification(s) for Operating System

A.3.6 - Other Specification(s) for non CPA application(s)

A.3.7 - CPA Specification

EMV Integrated Circuit Card Specifications for Payment Systems: Common Payment Application Specification


A.3.8 - CPA Bulletins (list all applicable)

A.3.9 - EMV Card Personalization Specification (if applicable)

A.3.10 - CPS Bulletins (list all applicable)


Product and Chip Descriptions A.5.1 – Product Name:

Product Version:

(This is the name that will appear on the Approved Products List)

A.5.2 – Who is the Card Manufacturer who will be producing the test cards being submitted for testing:

A.5.3 - Chip Provider:

A.5.4 - Chip Type or Identifier:

A.5.5 - EMVCo IC Compliance Certificate reference number:

Date:

A.5.6 - Which method was chosen for electrical testing?

Chip Provider

EMVCo Accredited Lab

A.5.7 - If electrical testing was done by the Chip Provider, please provide the Reference Number of the IC Electrical Compliance Label

A.5.8 - Operating System Type:

A.5.9 - Operating System Name and Version Number:

Name:

Version Number:

Chip Feature Description

A.5.10 – RAM size (Kbytes)

A.5.11 – ROM size (Kbytes)

A.5.12 – Total EEPROM or Flash size (Kbytes)

A.5.13 – Available EEPROM or Flash size (Kbytes)*

A.5.14 – CPU (8, 16 or 32 bit etc.)

A.5.15 – Crypto coprocessor present? Yes No

A.5.16 – RSA implementation supported by the card

<Select>

* Free EEPROM or Flash size available for initialization and personalization of the application(s) listed in Section A.6.1 (excluding any memory utilized for the card operating system).


Applications on the Card A.6.1 – CPA Application(s) and CCD Application(s) if applicable*

Name Version Developer Functional Description

AID(s) of all card images submitted for testing except

for B7(A1a), B9(A1b), B10(A1c),

B51a, and A11.x

Code Loaded

A.6.2 – Other Application(s) if applicable

Name Version Developer Functional Description

AID(s) or File ID(s) of the actual application

Code Loaded

* Note: For testing purposes multiple application is defined by several instances of the same ordifferent CCD (resp CPA) application code with each instance having its own independent application life cycle – please list the AIDs for all instances of the application under the AID column. Multiple AIDs that share the same instance are not considered as multiple applications – in such a case please list only one AID for each instance of the application under the AID column.

Please also specify the number of AIDs listed here in L2.3.1.


Applications Interaction with the CPA application A.7.1 - Do any other applications interact with the CPA application? Yes No

A.7.2 - If yes, describe how each of the other applications interact with the CPA application (Data shared, functions shared). Please provide details below.

Limitation on simultaneous personalization and activation of all applications listed in section A.6

A.7.3 - Is there any limitation that precludes submitting card image B1 for testing with all applications personalized and activated simultaneously? (e.g. restriction on EEPROM size, other application selected by default, etc.) Yes No

A.7.4 - If yes, please describe the limitation below. Please also list in A.7.5 and A.7.6 the original and additional multi-application configurations that will be submitted for testing.

A.7.5 - Original multi-application configuration (submitted on all card images for testing):

A.7.6 - Additional multi-application configurations (submitted on card image B1 for non-regression testing):

Additional Functionality included in the CPA application A.8.1a - Does the CPA application include any additional functionality? (e.g. additional functionality in EMV and CPA defined commands, or other examples of additional functionality in Section 19 of the CPA specification) Yes No

A.8.1b - If the answer to A.8.1a is ‘Yes’ is this additional functionality activated for testing? Yes No

A.8.2 - If A.8.1.a is “Yes”, please describe the additional functionality included in the CPA application. Please provide details below.


L1 - EMV Level 1 Electrical Characteristics L1.1 – Card Class

L1.1.1 - Class A Supported? Yes No

L1.1.2 - Class B Supported? Yes No

L1.1.3 - Class C Supported? Yes No

L1.1.4 - Operating Voltage: (normal) V

L1.1.5 - Maximum Current: mA

Transport ProtocolL1.2 – T = 0 supported? Yes No

L1.2.1 - Does the card issue procedure byte ‘60’ to request a Work Waiting Time extension during any command & response exchange of the CPA application?

Yes No

L1.2.2 - If Yes, describe how and where in the transaction this will occur. Please provide details below.

L1.3 – T = 1 supported? Yes No

L1.3.1 - Does the card issue a waiting time extension request, S (WTX request) block, during any command & response exchange of the CPA application?

Yes No

L1.3.2 - If Yes, describe how and where in the transaction this will occur. Please provide details below:

L1.3.3 - Value of IFSC

L1.3.4 - Can the ICC initiate chaining? Yes No

L1.3.5 - If Yes, describe how and where in the transaction this is initiated? Please provide details below:

L1.3.6 - Can the ICC by means of chaining receive a command of length > IFSC (for cases IFSC=’FE’ the “NO” box shall be checked)?

Yes No

L1.3.7 - If yes, specify such command and its response. Please provide details below:

L1.4 – Dynamic Calculations

L1.4.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.

Yes No

L1.4.2 - If Yes, please provide details below:


Answer to Reset (ATR) L1.5 - ATR

L1.5.1 - Hex values returned by the ICC in response to cold reset: (Provide the longest historical byte string the card can support) L1.5.2 - EMV Compliant Cold ATR: Yes No L1.5.3 - Hex values returned by the ICC in response to warm reset: (Provide the longest historical byte string the card can support) L1.5.4 - EMV Compliant Warm ATR: Yes No

Level 2 Additional Information for preparation of Level 1 test tool L1.6 – PSE supported? Yes No

L1.6.1 - FCI Data: returned by card

L1.6.2 - Read Record Data for Directory File: L1.6.3 - SFI of Directory File and Number of Records

SFI: Number of Records:

L1.7 – Direct Select supported? Yes No

L1.7.1 - EMV Application Name:

L1.8 – DYNAMIC DATA AUTHENTICATION supported?

Yes No

L1.9 – Enciphered PIN supported? Yes No

L1.10 – 1st GENERATE AC L1.10.1 - 1st GAC Command

L1.10.2 - Maximum Response size (depending if CDA is supported)

L1.11 – 2nd GENERATE AC L1.11.1 - 2nd GAC Command

L1.11.2 - Maximum Response size (depending if CDA is supported)


L2 - EMV Level 2 L2.0 - Implementer Options

L2.0.1 - Is EMV CPS Personalization supported?

Yes No

L2.0.2 - Is Dynamic RSA supported? Yes No L2.0.3 - Is VLP supported? Yes No L2.0.4 - Is Profile Selection Using Card Data supported?

Yes No

L2.0.5 - If Yes, provide a list of AIDs and specify which AID is linked to which GPO Parameter for card image B51a. (What is the value of x for DF0x in template BF3E that is associated with each AID?)

Note: Please define the AIDs as specified in Card Image B51a.

AID x in DF0x

L2.0.6 - Are Application Security Counters supported?

Yes No

L2.0.7 - Application Control ‘Allow Retrieval of Offline Values and Limits’ bit is significant (see note of CPA req. 12.7)

Yes No

L2.0.8 – Cryptogram Version supported

Version & Cryptogram Confirmation L2.1 - MAC longer than 4 supported? Yes No

L2.1.1 - Is MAC with length equal to 5 supported?

Yes No


Yes No


Yes No


Yes No


Application Selection L2.2 – PSE supported? Yes No

SELECT Command L2.2.1 - FCI Maximum Length

READ RECORD Command

L2.2.2 - SFI value(s) for the Directory Elementary File L2.2.3 - Number of Records supported L2.2.4 - Maximum Record size (bytes per record) L2.2.5 - Minimum Record size (bytes per record) L2.2.6 - How many template ‘61’ can be loaded in Records?

L2.3 – ADF L2.3.1 – How many AIDs are supported per CPA application?

SELECT Command

L2.3.2 – FCI Maximum Length

Read Application Data L2.5 – READ RECORD COMMAND

L2.5.1 - [SFI 11 to 20] range supported Yes No

L2.5.2 - [SFI 21 to 30] range supported Yes No

L2.5.3 -List the SFI value(s) supported (all ranges) L2.5.4 - Number of Records supported

L2.5.5 - Maximum Record size (bytes per record) L2.5.6 - Minimum Record size (bytes per record)


Keys (to be completed when answer to question L2.0.2 is ‘Yes’)L2.6 – Public Keys

L2.6.1 - Maximum CA Public Key length L2.6.2 - Maximum Issuer Public Key length

L2.6.3 - If Maximum CA key size is different from the pre-determined EMVCo test keys please provide CA public key value for testing L2.6.4 - If Maximum Issuer key size is different from the pre-determined EMVCo test keys please provide Issuer public key value for testing

L2.8 – DDA L2.8.1 - Maximum ICC Public Key Length

L2.8.2 - If Maximum key size is different from the pre-determined EMVCo test keys please provide ICC public key value for testing

Modulus:

Exponent:

L2.8.3 - Odd Key Length supported? Yes No

L2.9 – CDA L2.9.1 - Maximum ICC Public Key length


Modulus:

Exponent:


L2.11 – Enciphered PIN Yes No

L2.11.1 - Can the ICC Public key be different for Enciphered PIN and DDA/CDA?

Yes No

L2.11.2 - Can the ICC Public key be the same for Enciphered PIN and DDA/CDA?

Yes No

L2.11.3 - Maximum ICC Public Key length


Modulus:

Exponent:



Issuer Scripts EMV defined script commands supported by the application but not specified by CPA

L2.14 – Application Block L2.14.1 - Supported before 2nd GEN AC? Yes No L2.14.2 - Supported after 2nd GEN AC? Yes No L2.14.3 - Second nibble range of the CLA byte (with first

nibble is ‘8’) supported (different from ‘C’) L2.16 – Card Block

L2.16.1 - Supported before 2nd GEN AC? Yes No L2.16.2 - Supported after 2nd GEN AC? Yes No L2.16.3 - Second nibble range of the CLA byte (with first

nibble is ‘8’) supported (different from ‘C’)

L2.18 – Additional SCRIPT Command without Secure Messaging for Confidentiality (without tag ‘87’)

If the additional Issuer Script commands supported are different from those defined in CPA specification, you are required to fill in L2.18 as well as A8.2. To be CPA compliant, UPDATE RECORD and PUT DATA should not be listed.

L2.18.1 – List of script commands supported by the application as additional functionality

L2.18.2 - Supported before 2nd GEN AC?

L2.18.3 - Supported after 2nd GEN AC?

L2.18.4 - Second nibble range of the CLA byte (with first nibble is ‘8’) supported (different from ‘C’)

L2.18.5 - Additional SCRIPT Command with tag ‘81’ supported?

L2.18.6 Can a tag that is part of a previously personalized template be deleted later?

Yes No

Yes No

Yes No

Yes No

Yes No

Yes No

Yes No

Yes No

Yes No

Yes No

Yes No

Yes No

Note: If there are more than 3 Additional SCRIPT Command without Secure Messaging for Confidentiality (without tag ‘87’), list them here and provide the information appropriate for L2.18.2, L2.18.3, L2.18.4, L2.18.5, and L2.18.6.


L2.19 – Additional SCRIPT Command with Secure Messaging for Confidentiality (with tag ‘87’) L2.19.1 – List of script commands supported by the application as additional functionality

L2.19.2 - Supported before 2nd GEN AC?

L2.19.3 - Supported after 2nd GEN AC?

L2.19.4 - Second nibble range of the CLA byte (with first nibble is ‘8’) supported (different from ‘C’)

L2.19.5 Can a tag that is part of a previously personalized template be deleted later?

Yes No

Yes No

Yes No

Yes No

Yes No

Yes No

Yes No

Yes No

Yes No

Note: If there are more than 3 Additional SCRIPT Command with Secure Messaging for Confidentiality (with tag ‘87’), list them here and provide the information appropriate for L2.19.2, L2.19.3, L2.19.4 and L2.19.5.

Log L2.22 – LOG File

L2.22.1a - SFI value(s) supported for the Log File (in the range 21 to 30)

21 22 23 24 25 26 27 28 29 30

L2.22.1b - SFI value used in personalized cards

L2.22.2a - Maximum number of records supported for each SFI indicated in L2.22.1a.

(A value should be specified for each SFI supported)

SFI value(s) Maximum number of records supported

L2.22.2b - Maximum number of records in total supported for the Log File

L2.22.3 - List the different Log Entry(s) supported and respective card image(s) other than those defined for card image A1 and B1.

Log Entry(s) Card Image(s)

L2.22.4 - List the different Log Format(s) supported and respective card image(s) other than those defined for card image A1 and B1.

Log Format(s) Card Image(s)


Specific Data L2.23 – Currency Code X

L2.23.1 - What is the Currency Code X whose transactions are counted in Counter 1 for the relevant CCD card images?

L2.24 – Currency Code Y L2.24.1 - What is the Currency Code Y whose amounts are cumulated in Accumulator 1 for the relevant CCD card images?

L2.25 – Reference Day 0 L2.25.1 – What is the reference day 0 used (only if different from December 31, 1999)?

L2.26 – SFI value for Profile Selection File L2.26.1 –SFI value(s) supported for the Profile Selection File in the range (21 to 30)?

21 22 23 24 25 26 27 28 29 30

L2.26.2 – SFI value used in personalized cards

L2.27 – Issuer Country Code L2.27.1 – What is the Country Code that is personalized on the cards submitted for testing?

L2.28 – Currency Code for Accumulator 2 L2.28.1 – What is the Currency Code whose amounts are accumulated in Accumulator 2?

Other CCD compliant related functionsL2.29 – Proprietary Authentication Data (longer then

zero) supported Yes No

L2.29.1 - What is (are) the length(s) supported?

L2.29.2 - Can it be included in the ARPC calculation (CSU Byte 1 bit 8 supported)?

Yes No

L2.29.3 - What is (are) the Proprietary Authentication Data Value(s), or how it is calculated?

L2.30 – Non EMV Commands L2.30.1 - Does the CPA Application support Non EMV Commands? (other than Proprietary Script Commands)

Yes No

L2.30.2 - Please list all supported pairs of CLA/INS

L2.31 – VERIFY Command L2.31.1 - NON CPA P2 byte value(s) supported (different from ‘80’ and ‘88’)


Maximum Number of Profiles supportedL2.40 – PROFILES

L2.40.1 - How many Profiles can be supported (Maximum number of Profile Control entries in template BF3F)?

L2.40.2 – How many Profiles can be supported when each profile is configured according to the rules for the default card image configuration B1, each N = minimum number/length required to be supported in the CCD/CPA Specifications, and all the data is shared between instances if multiple instances are supported?

Maximum Allocated Size (higher than the Minimum defined in the CPA specification)L2.41 – Maximum Allocated Size

L2.41.1 - Single Additional Check Table

L2.41.1a - Single Additional Check Table length in bytes bytes

L2.41.1b – Additional Check Table Comparison Data Length in bytes

bytes

L2.41.1c – Number of Comparison Blocks for an Additional Check Table (with Comparison Data Length equal to ‘01’)

Blocks

L2.41.2 - Single Currency Conversion Table in number of currencies currencies

L2.41.3 - Number of AIP/AFL Entries entries

L2.41.4 - GPO Input Data Length in bytes bytes

L2.41.5 - Profile Selection Entry Comparison

L2.41.5a - Profile Selection Entry Comparison Block Length in bytes

bytes

L2.41.5b – Maximum number of comparison blocks for one Profile Selection Entry (Number of blocks without Bit Mask)

Blocks

L2.41.6 - Profile Selection File record number with each (Profile Selection Entry) record length greater than 30 bytes

records

L2.41.7 - First GENERATE AC Extension Data length in bytes bytes

L2.41.8 - First GEN AC Unchanging Log Data Table number of Data Entries

entries

L2.41.9 – Length of data extracted from First GEN AC command data for Transaction Logging using First GEN AC Unchanging Log Data Table (byte 2 of a Data Entry)

bytes

L2.41.10 - First GEN AC Log Data Table number of Data Entries entries

L2.41.11 - Length of data extracted from First GEN AC command data for Transaction Logging using First GEN AC Log Data Table (byte 2 of a Data Entry)

bytes


L2.41.12 - Second GEN AC Log Data Table number of Data Entries entries

L2.41.13 - Length of data extracted from Second GEN AC command data for Transaction Logging using Second GEN AC Log Data Table (byte 2 of a Data Entry)

bytes

L2.41.14 - Second GENERATE AC Extension Data in bytes bytes

L2.41.15 - Total size in bytes of all EMV Records bytes

L2.41.16 - Number of EMV Records records

L2.41.17 - Number of Log Records records

L2.41.18 - Number of AIDs supported for a single CPA application AIDs

Specific Data ElementsL2.42 – Can These Data be not personalized?

L2.42.1 - Accumulator 2 and Counter 2/3, Cyclic Accumulator 2, Additional Check Table 2 (CPA req. 21.12)

Yes (personalization may omit one or more of these data)

No (personalization must include all of these data, even if the condition in Table 21-9 is not met)

L2.43 – Does the card Application allow personalization without these data?

L2.43.1 - GPO Parameter 1 Yes No

L2.43.2 - Profile Control template Yes No

L2.43.3 - Application Control Yes No

L2.43.4 - CIACs Entries template Yes No

L2.43.5 - Accumulator Controls template Yes No

L2.43.6 - Accumulator 1 Control Yes No

L2.43.7 - Accumulator Profile Controls template Yes No

L2.43.8 - Counter Controls template Yes No

L2.43.9 - Counter Profile Controls template Yes No

L2.43.10 - Cyclic Accumulator Controls template Yes No

L2.43.11 - Cyclic Accumulator 1 Control Yes No

L2.43.12 - Cyclic Accumulator Profile Controls template Yes No

L2.43.13 - Issuer Country Code Yes No


L2.43.14 - Application Currency Code Yes No

L2.43.15 - Additional Check Table template Yes No

L2.43.16 - Number of Days Offline Limit Yes No

L2.43.17 - AIP/AFL Entries template Yes No

L2.43.18 - Issuer Options Profile Controls template Yes No

L2.43.19 - MTA Profile Controls template Yes No

L2.43.20 - Accumulator 1 Limit Set 1 Yes No

L2.43.21 - Counter 1 Limit Set 1 Yes No

L2.43.22 - Limit Entries template Yes No

L2.43.23 - Currency Conversion Tables template Yes No

L2.43.24 - Currency Conversion Table entry 1 Yes No

L2.43.25 – Counter 1 Control Yes No

L2.43.26 – Additional Check Table 1 Yes No

EMV CPS personalization (to be completed when answer to question L2.0.1 is ‘Yes’)L2.44 – KMC keys

L2.44.1 - Can the Card support multiple KMC keys? Yes No

L2.45 – DGIs L2.45.1 - CPA recommended DGI supported? Yes No

L2.45.2 - Can the DGIs be loaded in any order? Yes No

L2.45.3 - If not please define for each DGI that can not be loaded in any order: • the DGI• any DGI’s that must be loaded prior• any DGI’s that must be loaded later

L2.46 - Does the CPA Application support Non CPS Commands (before personalization)?

Yes No

L2.46.1 - Please list all supported pairs of CLA/INS (when CLA byte has one of the following values: ‘00’, ’04, ‘08’, ‘0C’, ‘80’, ‘84’ ‘88’, ‘8C’, ‘9x’ or ‘Ex’)

Issuer Options L2.47 – Proprietary format of IAD byte 19-32

supported Yes No


Digital Signatures

Product Provider I agree and understand that the cards submitted for Functional Level 1, Functional Level 2 and Security Evaluation testing are exactly the same. Also if an issue requires a change to the code of the card or the addition of a patch or new executable code to the card, EMVCo must be notified. In case of such change, new cards must be submitted for Functional Level 1 and Functional Level 2 and Security Evaluation testing.

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

Level 1 Laboratory I hereby declare that this ICS document has been reviewed, and that all product information is consistent throughout the ICS.

Comments

Signature

Level 2 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

EMVCo Common Payment Application Level 1 & Level 2 ... - Implementer Options L2.0.1 - Is EMV CPS...

Documents

Transcript of EMVCo Common Payment Application Level 1 & Level 2 ... - Implementer Options L2.0.1 - Is EMV CPS...