ic card specification 20 eng

JCB IC Card Specification

Version 2.0 April, 2008

2008 JCB Co., Ltd. All rights reserved. All rights regarding this documentation are reserved by JCB Co., Ltd. (JCB). This documentation contains confidential and exclusive information, patents, copyrights, trademarks, trade secrets, know-how or other intellectual property rights, or any other rights of JCB and/or JCB International Co., Ltd. (JCBI). You shall accept and agree to all of the terms and conditions herein before viewing, downloading or otherwise using all or any part of this documentation (written, graphics or otherwise) appearing whether in whole or in part, regardless of form. JCBI is authorized to conduct JCBs business outside Japan, and the word of JCB in this documentation can be construed JCB and/or JCBI in each context. You are prohibited from copying for any third party, distributing, assigning, lending, displaying, publishing or disclosing or modifying (including but not limited to translating), all or any part of this documentation (written, graphics or otherwise) appearing whether in whole or in part, regardless of form, without the prior written permission of JCB. Certain parts of this documentation are produced by referring to documentations of EMVCo, LLC (EMVCo) and this documentation may contain any information regarding patents, copyrights, trademarks, trade secrets, know-how or other intellectual property rights, or any other rights of any third party including EMVCo. Regardless of such reference, JCB makes no representation, warranty or guarantee expressly nor impliedly whether all or any part of this documentation (written, graphics or otherwise) appearing whether in whole or in part, regardless of form, does or does not violate, infringe or otherwise use the information, patents, copyrights, trademarks, trade secrets, know-how or other intellectual property rights, or any other rights of third parties including EMVCo. You shall be solely responsible for determining whether your activities require license or permission from third parties including EMVCo. JCB shall not be liable for your or any third partys infringement of any intellectual property rights or any other rights of any third parties including EMVCo. While JCB uses reasonable efforts to include accurate and up-to-date information in this documentation, JCB makes no representation, warranty or guarantee expressly nor impliedly regarding the accuracy or finality of this documentation (written, graphics or otherwise) appearing whether in whole or in part, regardless of form and JCB shall not be liable for any product or service developed or produced in compliance with this documentation. JCB shall assume no liability for any typographical or other errors or omissions in the content of this documentation (written, graphics or otherwise) appearing whether in whole or in part, regardless of form. This documentation may contain links to other sites. JCB is not responsible for the content or practices of such sites. To the extent permitted by applicable law, in no event JCB, its officers, employees, affiliates, agents, or contractors, shall be liable to you or any third parties for any damages direct or indirect consequential, incidental, or punitive damages arising from the use of or inability to use this documentation, including without limitation, damages for loss of profit, business interruption, loss of information, damages arising from third partys claim, even if JCB has been advised of the possibility of such damages.

JCB IC Card Specification Revision History The revision histories to the version in April 2002 are as follows.Item number 1 2 3 Date of revision Chapter Contents of revision

Apr, 2008 Apr, 2008 Apr, 2008 Apr, 2008

All All 1.4.3(1) 1.5 Table1-1 1.6 4.1.3 5.9.3.1.2 4.2.6.2 4.2.7.2 5.5.2 5.6.2 Table 5-18 5.9.2 Table 5-27 5.12.2 Table 5-44 5.9.3.1.1 Table 5-37 5.12.3.2.1 Table 5-49 5.10.1 Table 5-41 Annex A Annex B

Updated JCB specification change information (Release version in June, 2006). Changed the reference specifications to EMV4.1. part of EMV

Changed JCB Terminal Specification Version 2.0 to JCB Terminal Requirements Version 1.0. Deleted the Application Authorisation Referral (AAR). Added the Recommended requirement for the PUT DATA/UPDATE RECORD command. Fixed Application Version Number value. Changed the Application Default Action (ADA) data to Mandatory.

4

5 6

Apr, 2008 Apr, 2008 Apr, 2008

7

Apr, 20088

Clarified the requirement for PIN Verification Not Performed Checking.

Apr, 20089

Added JCB specification Annex (Release version in March, 2004).

10 11


Contents

Table of Contents1 Introduction .................................................................................................................1-1 1.1 Objective .....................................................................................................1-1 1.2 Target Audience and Scope ........................................................................1-1 1.3 Structure......................................................................................................1-1 1.4 Related Materials ........................................................................................1-2 1.4.1 ISO Materials ..............................................................................................1-2 1.4.2 EMV Materials............................................................................................1-2 1.4.3 JCB Materials..............................................................................................1-3 1.5 Definition of Terms.....................................................................................1-3 1.6 Abbreviations............................................................................................1-12 Basic Requirements .......................................................................................................2-1 2.1 IC Card Requirements.................................................................................2-1 2.1.1 Magnetic Stripe Encoding and Embossing .................................................2-1 2.1.2 Electromechanical Characteristics, Logical Interface and Transmission Protocols .....................................................................................................2-1 2.2 Application Status.......................................................................................2-2 2.3 Application ID and Version Number..........................................................2-2 File Structure and Data Requirements ...........................................................................3-1 3.1 File Structure...............................................................................................3-1 3.2 Data .............................................................................................................3-2 3.2.1 Data Retrievable with GET DATA Command ............................................3-2 3.2.2 Data Retrievable with GET PROCESSING OPTIONS Command............3-2 3.2.3 Data Updatable with Issuer Script Commands ...........................................3-2 Command Requirements................................................................................................4-1 4.1 Transaction Commands ..............................................................................4-1 4.1.1 Supporting Conditions ................................................................................4-1 4.1.2 EXTERNAL AUTHENTICATE Command ...............................................4-2 4.1.3 GENERATE APPLICATION CRYPTOGRAM Command .......................4-2 4.1.4 GET CHALLENGE Command ..................................................................4-3 4.1.5 GET DATA Command ................................................................................4-3 4.1.6 GET PROCESSING OPTIONS Command................................................4-3 4.1.7 INTERNAL AUTHENTICATE Command ................................................4-3 4.1.8 READ RECORD Command.......................................................................4-3 4.1.9 SELECT Command ....................................................................................4-3 4.1.10 VERIFY Command.................................................................................4-3 4.2 Issuer Script Commands .............................................................................4-4 4.2.1 Supporting Conditions ................................................................................4-4 4.2.2 APPLICATION BLOCK Command...........................................................4-4 4.2.3 APPLICATION UNBLOCK Command.....................................................4-5 4.2.4 PIN CHANGE/UNBLOCK Command ......................................................4-5 4.2.5 CARD BLOCK Command .........................................................................4-5

2

3

4

JCB Confidential

i

April 2008


Contents

5

4.2.6 PUT DATA Command ................................................................................4-5 4.2.7 UPDATE RECORD Command ..................................................................4-6 Functional Requirements ...............................................................................................5-1 5.1 Application Selection..................................................................................5-1 5.1.1 Definition and Conditions of Execution .....................................................5-1 5.1.2 Processing Data...........................................................................................5-1 5.1.3 Processing ...................................................................................................5-3 5.2 Initiate Application Processing ...................................................................5-4 5.2.1 Definition and Conditions of Execution .....................................................5-4 5.2.2 Processing Data...........................................................................................5-4 5.2.3 Processing ...................................................................................................5-4 5.3 Read Application Data................................................................................5-5 5.3.1 Definition and Conditions of Execution .....................................................5-5 5.3.2 Processing Data...........................................................................................5-5 5.3.3 Processing ...................................................................................................5-5 5.4 Offline Data Authentication........................................................................5-6 5.4.1 Definition and Conditions of Execution .....................................................5-6 5.4.2 Processing Data...........................................................................................5-7 5.4.3 Processing .................................................................................................5-10 5.5 Processing Restrictions .............................................................................5-11 5.5.1 Definition and Conditions of Execution ................................................... 5-11 5.5.2 Processing Data......................................................................................... 5-11 5.5.3 Processing .................................................................................................5-12 5.6 Cardholder Verification ............................................................................5-13 5.6.1 Definition and Conditions of Execution ...................................................5-13 5.6.2 Processing Data.........................................................................................5-14 5.6.3 Processing .................................................................................................5-15 5.7 Terminal Risk Management......................................................................5-17 5.7.1 Definition and Conditions of Execution ...................................................5-17 5.7.2 Processing Data.........................................................................................5-17 5.7.3 Processing .................................................................................................5-18 5.8 Terminal Action Analysis .........................................................................5-19 5.8.1 Definition and Conditions of Execution ...................................................5-19 5.8.2 Processing Data.........................................................................................5-19 5.8.3 Processing .................................................................................................5-19 5.9 Card Action Analysis................................................................................5-20 5.9.1 Definition and Conditions of Execution ...................................................5-20 5.9.2 Processing Data.........................................................................................5-24 5.9.3 Processing .................................................................................................5-29 5.10 Online Processing .....................................................................................5-42 5.10.1 Definition and Conditions of Execution ...............................................5-42 5.10.2 Processing Data.....................................................................................5-42 5.10.3 Processing .............................................................................................5-43

JCB Confidential

ii

April 2008


Contents

Issuer Script ..............................................................................................5-44 5.11.1 Definition and Conditions of Execution ...............................................5-44 5.11.2 Processing Data.....................................................................................5-44 5.11.3 Processing .............................................................................................5-44 5.12 Completion................................................................................................5-45 5.12.1 Definition and Conditions of Execution ...............................................5-45 5.12.2 Processing Data.....................................................................................5-46 5.12.3 Processing .............................................................................................5-47 6 Security Requirements...................................................................................................6-1 6.1 Security Requirements Using Asymmetric Algorithm ...............................6-1 6.1.1 Certification Authority Service ...................................................................6-1 6.1.2 Processing ...................................................................................................6-1 6.2 Security Requirements Using Symmetric Algorithm .................................6-2 6.2.1 Types of Algorithm .....................................................................................6-2 6.2.2 Definition of Encryption Keys....................................................................6-2 6.2.3 Definition of Cryptogram Version Number ................................................6-3 6.2.4 Key Derivation............................................................................................6-4 6.2.5 AC Generation ............................................................................................6-7 6.2.6 ARPC Generation .......................................................................................6-8 6.2.7 Secure Messaging .......................................................................................6-9 Annex A. JCB Proprietary Data List.......................................................................... A-1 Annex B. Transaction Flow........................................................................................ B-1

5.11

JCB Confidential

iii

April 2008


1. Introduction

1

IntroductionThis chapter describes the objective, target audience, scope and structure of this specification, related materials, definitions of terms and abbreviations.

1.1

ObjectiveThis specification contains the requirements for IC Cards. The purpose of this specification is: (1) To define the JCB proprietary requirements for developing the IC Cards conforming to EMV4.1. (2) To describe the requirements for IC Cards that ensure proper and mutually secure operation of Terminals and IC Cards.

1.2

Target Audience and ScopeThe target audience of this specification is the JCB partners and parties involved in the issuance of IC Cards. It is presumed that IC Cards conforming to this specification shall conform to all applicable areas of EMV4.1. The scope of this specification is limited to the minimum additions and restrictions that have been made relative to EMV4.1 in order to define JCB proprietary requirements regarding new items that emerge with the migration of current magnetic stripe cards to IC Cards.

1.3

StructureChapter 1 Introduction This chapter describes the objective, target audience, scope and structure of this specification, related materials, definitions of terms and abbreviations. Chapter 2 Basic Requirements This chapter defines hardware requirements such as magnetic stripe encoding, embossing, and electromechanical characteristics. Software requirements such as the implementation requirements of the IC Card are defined as well. Chapter 3 File Structure and Data Requirements This chapter defines the file structure of the IC Card. Data supported and the corresponding update methods are defined, as well.

JCB Confidential

1-1

April 2008


1. Introduction

Chapter 4

Command Requirements

This chapter defines transaction commands and Issuer Script commands supported by cards. Chapter 5 Functional Requirements This chapter shows definitions, conditions of execution, processing data and processing regarding functions supported by IC Cards. Chapter 6 Security Requirements This chapter defines security requirements for asymmetrical and symmetrical algorithms. Annex A Annex B JCB Proprietary Data List Transaction Flow This Annex shows JCB Proprietary Data List. This Annex shows sample functional processing prescribed by the credit application requirements.

1.41.4.1

Related MaterialsISO Materials ISO materials relating to this specification are as follows: (1) ISO/IEC 7813:1995, Identification cards - Financial transaction cards (2) ISO/IEC 7816-4:1995, Identification cards, Integrated circuit(s) cards with contacts, Part 4, inter-industry commands for interchange

1.4.2

EMV Materials EMV materials relating to this specification are as follows. The term EMV4.1 refers to the following four documents: (1) EMV4.1 Book1: EMV Integrated Circuit Card Specification for Payment Systems Book1 - Application Independent ICC to Terminal Interface Requirements Version 4.1 May, 2004 (2) EMV4.1 Book2: EMV Integrated Circuit Card Specification for Payment Systems Book2 - Security and Key Management Version 4.1 May, 2004 (3) EMV4.1 Book3: EMV Integrated Circuit Card Specification for Payment

JCB Confidential

1-2

April 2008


1. Introduction

Systems Book3 - Application Specification Version 4.1 May, 2004 (4) EMV4.1 Book4: EMV Integrated Circuit Card Specification for Payment Systems Book4 - Cardholder, Attendant, and Acquirer Interface Requirements Version 4.1 May, 2004

1.4.3

JCB Materials JCB materials relating to this specification are as follows: (1) JCB Terminal Requirements Version 1.0

1.5

Definition of TermsThe terms and notations relating to this specification are defined in the Table 1-1. Alphanumeric characters (0 to 9, A to F) enclosed in single quotation marks () represent hexadecimal numbers.

JCB Confidential

1-3

April 2008


1. Introduction

Table 1-1A

Terms and Abbreviations

AAC Application Authentication Cryptogram AC Application Cryptogram ADA Application Default Action AFL Application File Locator AID Application Identifier AIP Application Interchange Profile Application Application Block Application Effective Dates Checking

An Application Cryptogram declining offline / online transactions, generated by the IC Card in response to a GENERATE AC command.

An enciphered value, generated using transaction related data, such as TC, AAC, and ARQC. It is generated by an IC Card after receiving a GENERATE AC command from an IC Terminal. Parameters set by an Issuer, used for judgment in the CAA and Completion, and showing optional functions to be performed. Data stored in an IC Card, which indicates the storage location of card data to be used in a Transaction. A code that specifies the application provider and the production type of application. Data stored in an IC Card, which indicates whether the specific functions are supported by the IC Card. The combination of a program and set of data that functions on an IC Card or an IC Terminal. An Issuer Script command which blocks a specific Application on an IC Card. One of the compatibility checks of Processing Restrictions, which confirm whether the transaction date is the same as or past the effective date of the application.

JCB Confidential

1-4

April 2008


1. Introduction

Application Expiration Dates Checking Application PAN Application Primary Account Number Application Selection Application Version Number ARPC Authorisation ResPonse Cryptogram ARQC Authorisation ReQuest Cryptogram ATC Application Transaction Counter AUC Application Usage Control

One of the compatibility checks of Processing Restrictions, which confirm whether the transaction date is prior to the expiration date of the application. An account number primarily stored in an IC Card Application. When it is padded to the right with F, the padding is ignored. A process to select the application for an IC Transaction. A version number respectively assigned to an Application of both an IC Card and an IC Terminal. A cryptogram generated by an Issuer host and passed to an IC Card through the Authorisation Response message. The IC Card verifies authenticity of ARPC by executing Issuer Authentication processing. An Application Cryptogram generated by an IC Card for Transactions requesting Online Authorisation in response to a GENERATE AC Command. A counter of Transactions maintained in an IC Card.

Data stored in an IC Card which specifies the restrictions designated by an Issuer on the IC Card Application usage.

C

CA Certification Authority CAA Card Action Analysis

A trusted central administration, operated by JCB, which operates and maintains JCB/CA Public Key Pairs. A function of an IC Card to determine whether to approve a Transaction, decline a Transaction, or issue an Online Authorisation request, based on verification results from a Terminal and within the IC Card itself.

JCB Confidential

1-5

April 2008


1. Introduction

CAAI Card Action Analysis Indicators CAASI Card Action Analysis Support Information CAC Card Action Code CAV Card Authentication Value Card Block Card Floor Limit Cardholder Cardholder Verification CDA "Combined Dynamic Data Authentication/ Application Cryptogram Generation" CID Cryptogram Information Data Completion

Data in an IC Card that records the results of the previous Transactions.

Data set in an IC Card, which specifies the supporting conditions of check items for CAA. Data set in an IC Card to determine whether to respond ARQC regardless of the CAA result, when the Terminal requests the IC Card to generate ARQC. A 3-digit security code encoded in track 1 and track 2 of the magnetic stripe of JCB Card and in Track 1 Discretionary Data and Track 2 Equivalent Data stored in J/Smart loaded onto the IC chip of JCB Card. An Issuer Script command, which blocks all Applications on an IC Card. One of the parameters set in an IC Card to indicate the maximum sum that can be processed offline in a single Transaction. An individual who presents an IC Card at the point of Transaction. The function performed to ensure that the person presenting the IC Card is the person to whom the application in the card was issued. An Offline Data Authentication in which a Terminal verifies the authenticity of an IC Card by using static application data stored in the IC Card and a random number specific to each transaction. GENERATE AC command is used to obtain dynamic signature data from the card. Data stored in an IC Card which indicates the type of Application Cryptogram returned by an IC Card in response to a GENERATE AC Command. A function of an IC Card to make the final judgment of whether to approve or decline a Transaction as a result of all the preceding processes. This function completes the Transaction.

JCB Confidential

1-6

April 2008


1. Introduction

CVM Cardholder Verification Method CVM List CVR Card Verification Results

A method of Cardholder Verification, such as Offline Enciphered PIN, Offline Plaintext PIN, Online Enciphered PIN, and Signature. A list set in an IC Card, which specifies CVM supported by the card. Temporarily saved data of the card-check results for a particular transaction.

D

DDA Standard Dynamic Data Authentication

Offline Data Authentication, in which a Terminal verifies the authenticity of an IC Card by using static application data stored in the IC Card and a random the card. number specific to each Transaction. The INTERNAL AUTHENTICATE command is used to obtain dynamic signature data from

DES Algorithm DKI Derivation Key Index

One of the algorithms in which a symmetric key is used for encryption and decryption. An index that indicates which master key is used in AC and ARPC generation.

F

First GENERATE AC command

A GENERATE AC command issued by an IC Terminal to an IC Card after TAA.

G

GENERATE AC command

A command issued by an IC Terminal to an IC Card, which requests the IC Card to generate TC, ARQC, or AAC.

JCB Confidential

1-7

April 2008


1. Introduction

I

IAC Issuer Action Code IC Card Integrated Circuit Card IC Card application IC Chip Integrated Circuit Chip Issuer Authentication Issuer Script

Parameters set in an IC Card by an Issuer, used for judgment in TAA. A card with an IC Chip embedded in it.

The application that functions on an IC card. an application issuer.

The application is issued by

An electronic component designed to perform processing and memory functions. A function in which an IC Card verifies whether an Authorisation Response is from a genuine Issuer or not. A function initiated by an Issuer through Online Processing for updating contents stored in Applications, and for blocking or unblocking Applications.

J

J/SmartTM

The JCB IC Card credit application developed according to the JCB IC Card Specification or the JCB Terminal credit application developed according to the JCB Terminal Requirements. It is also used as a general term for referring to both.

N

Nibble

Upper or lower 4 bits within a byte.

M

Master Key

A DES Key, which is managed by an Issuer, used to derive Unique Keys to generate AC, ARPC, and MAC or to encrypt command messages.

JCB Confidential

1-8

April 2008


1. Introduction

O

Offline Data Authentication Offline Enciphered PIN Verification Offline Plaintext PIN Verification Online Enciphered PIN Verification

A function in which the authenticity of an IC Card is verified offline to protect against counterfeit fraud. One of the CVMs, in which the PIN entered by a Cardholder is enciphered at the PIN Pad and then sent to the IC Card for verification. One of the CVMs, in which the PIN entered by a Cardholder is sent unencrypted, in plaintext form, from the PIN Pad to the IC Card for verification. One of the CVMs, in which the PIN entered by a Cardholder onto the PIN Pad is enciphered and then sent to an Issuer for verification.

P

PIN Personal Identification Number PIN Pad Private Key Processing Restrictions

A numeric code that is used for Cardholder Verification.

A device equipped with numeric and command keys used for PIN entry. The key in an asymmetric algorithm, that is kept secret and known only to the owner. A process in which the compatibility between an IC Card and an IC Terminal Application is verified by checking the Application Version Number, Application Expiration Date, Application Effective Date, and Application Usage Control.

PSE Payment System Environment Public Key

A list of all applications stored in an IC Card, which is used in Application Selection. The key in an asymmetric algorithm that may be known by all parties.

R

Read Application Data

A process to retrieve data from an IC Card, which is used for the Transaction.

JCB Confidential

1-9

April 2008


1. Introduction

RID Registered application provider Identifier RSA Algorithm

A code that specifies the application provider.

One of the algorithms in which an asymmetric key pair is used for encryption and decryption.

S

SDA Static Data Authentication Second GENERATE AC command Session Key

A type of Offline Data Authentication, in which an IC Terminal verifies the authenticity of an IC Card by using static application data stored in the IC Card. A cryptographic value stored in an IC Card. A GENERATE AC command issued by an IC Terminal to an IC Card, based on the result of online Authorisation. A DES Key, unique to a Transaction, which is derived from Unique Keys, and is used to generate AC, ARPC, and MAC or used to encrypt command messages.

T

TAA Terminal Action Analysis TAC Terminal Action Code TC Transaction Certificate Terminal Terminal Floor Limit

A function of an IC Terminal to determine whether to approve the Transaction, decline the Transaction, or issue an Online Authorisation request, based on the verification results in the Terminal. Parameters set in an IC Terminal, used for judgment in TAA.

An Application Cryptogram generated in response to a GENERATE AC Command by an IC Card as a result of offline or online approved Transactions. The device used to perform a financial transaction with an IC Card. One of the parameters set in an IC Terminal to indicate the maximum sum that can be processed offline in a single Transaction.

JCB Confidential

1-10

April 2008


1. Introduction

Terminal Risk Management TSI Transaction Information TVR Terminal Results Verification Status

A series of checks performed by a Terminal for the purpose of risk management, including Terminal Floor Limit Checking, Random Transaction Selection, Terminal Velocity Checking, and Exception File Checking. Data stored in an IC Terminal that indicates whether or not the Terminal performed the specific processing functions or not. Data which records the result of Offline Data Authentication, Processing Restrictions, Cardholder Verification, and Terminal Risk Management performed by a Terminal.

U

Unique Key

A DES Key, unique to each card, which is derived from the Master Keys, and is used to generate AC, ARPC, and MAC or used to encrypt command messages.

JCB Confidential

1-11

April 2008


1. Introduction

1.6

AbbreviationsAAC AC ADA ADF AFL AID AIP APDU ARC ARPC ARQC ATC AUC CA CAAI CAASI CAC CAV CDA CDOL1 CDOL2 CID CLA CVM CVR DDA DDF DDOL DES DF DKI FCI IAC IC ICC IEC INS ISO Application Authentication Cryptogram Application Cryptogram Application Default Action Application Definition File Application File Locator Application Identifier Application Interchange Profile Application Protocol Data Unit Authorisation Response Code Authorisation Response Cryptogram Authorisation Request Cryptogram Application Transaction Counter Application Usage Control Certification Authority Card Action Analysis Indicators Card Action Analysis Support Information Card Action Code Card Authentication Value Combined Dynamic Data Authentication / Application Cryptogram Generation Card Risk Management Data Object List 1 Card Risk Management Data Object List 2 Cryptogram Information Data Class Byte of the Command Message Cardholder Verification Method Card Verification Results Standard Dynamic Data Authentication Directory Definition File Dynamic Data Authentication Data Object List Data Encryption Standard Dedicated File Derivation Key Index File Control Information Issuer Action Code Integrated Circuit Integrated Circuit Card International Electrotechnical Commission Instruction Byte of the Command Message International Organisation for Standardisation

JCB Confidential

1-12

April 2008


1. Introduction

Lc Le LRC MAC P1 P2 PAN PDOL PIN PSE PIX POS RFU RID RSA SDA SFI SW1 SW2 TAC TC TLV TSI TVR XOR

Exact Length of Data Sent by the Terminal Application Layer in a Case 3 or 4 Command Maximum Length of Data Expected by the Terminal Application Layer in Response to a Case2 or 4 Command Longitudinal Redundancy Check Message Authentication Code Parameter 1 Parameter 2 Primary Account Number Processing Options Data Object List Personal Identification Number Payment System Environment Proprietary Application Identifier Extension Point-of-Service Reserved for Future Use Registered Application Provider Identifier Rivest, Shamir, Adleman Algorithm Static Data Authentication Short File Identifier Status Word 1 Status Word 2 Terminal Action Code Transaction Certificate Tag Length Value Transaction Status Information Terminal Verification Results Exclusive Or

JCB Confidential

1-13

April 2008


2. Basic Requirements

2

Basic RequirementsThis chapter defines hardware requirements such as magnetic stripe encoding, embossing, and electromechanical characteristics. Software requirements such as the implementation requirements of the IC Card are defined as well.

2.1

IC Card RequirementsAn IC Card shall be equipped with a magnetic stripe and a contact IC chip conforming to EMV4.1. The hardware requirements are defined as follows:

2.1.1

Magnetic Stripe Encoding and Embossing Magnetic stripe encoding and embossing of the IC Card are defined as follows: (1) Data structures and operation methods of magnetic stripe encoding and embossing on the IC Card shall follow the rules defined separately. (2) Data encoded on the magnetic stripe shall match Track 2 Equivalent Data, Cardholder Name, and Track 1 Discretionary Data in the IC Card credit application. The Track 1 Discretionary Data is the Discretionary area of Track 1 as defined in ISO/IEC 7813. (3) Track 2 Equivalent Data and Track 1 Discretionary Data mentioned in (2) shall contain all corresponding data on the magnetic stripe, except for the start sentinel, end sentinel and LRC. However, the data in CAV in Track 1 Discretionary Data and it in Track 2 Equivalent Data may differ from the data in CAV in Track 1 and Track 2 of the magnetic stripe. (4) If an IC Card credit application resides on the card, the service code of Track 2 data shall begin with either a 2 or 6.

2.1.2

Electromechanical Characteristics, Logical Interface and Transmission Protocols The electromechanical characteristics, logical interface and transmission protocols shall conform to the definitions in Part II of EMV4.1 Book1.

JCB Confidential

2-1

April 2008


2. Basic Requirements

2.2

Application StatusTwo levels of status exist for an application: the normal status, in which transactions can be performed, and the blocked status, in which no transaction can be performed. Application is blocked in one of the following cases: (1) The number of failed PIN tries has exceeded the PIN Try Limit with an IC Card and the If PIN Try Limit exceeded on current transaction, block application in the ADA(2,8) is set to 1. (2) An application block has been instructed through Issuer Script. (3) An application block has been instructed by a proprietary command set by the Issuer.NOTE: As for case (2), after successful completion of the APPLICATION BLOCK command, the IC Card must not be blocked during the current transaction. As for case (3), the Issuer is responsible for determining the processing. When an application is blocked, an IC Card shall always respond to a GENERATE AC Command with an AAC.

Application is unblocked in one of the following cases: (1) An application unblock has been instructed through Issuer Script. (2) An application unblock has been instructed by a proprietary command set by the Issuer. In order to prevent fraudulent use of the IC Card, the CARD BLOCK command defined in Part II, Section 6.5.3 of EMV4.1 Book3 may be implemented to forcibly restrict access on all IC Card applications. However, the IC Card must not be blocked during the current transaction after a successful completion of the CARD BLOCK command.

2.3

Application ID and Version NumberApplication ID (AID) for Terminals conforming to this specification shall be A0000000651010. The version number for Terminals conforming to this specification shall be 2.0.

JCB Confidential

2-2

April 2008


3 File Structure and Data Requirements

3

File Structure and Data RequirementsThis chapter defines the file structure, supported data and corresponding update methods of the IC Card.

3.1

File StructureThe file structure of the IC Card shall conform to Part III, Chapter 10 of EMV4.1 Book1 and Part II, Chapter 5 of EMV4.1 Book3. As additional requirements, Table 3-1 lists the data that shall be stored in IC Cards, in the first record of the file with an SFI value of 1.Table 3-1Item No. 1 2 3

Data to be Stored in the First Record of the File with an SFI Value of 1Tag 57 5F20 9F1F Data name Track 2 Equivalent Data Cardholder Name Track 1 Discretionary Data Presence Mandatory Optional Optional

Refer to Section 2.1.1 for additional requirements for data of items 1 and 3.

JCB Confidential

3-1

April 2008



3.2

DataThe data object format and data object list (DOL) structure of the IC Card shall conform to Part III, Chapter 10 of EMV4.1 Book1 and Part II, Chapter 5 of EMV4.1 Book3. Data supported by the IC Card consist of two types: data defined in Part IV, Annex A of EMV4.1 Book3 and JCB proprietary data. JCB proprietary data is listed in Annex A. The data used by each function of the IC Card are defined in Chapter 5.

3.2.1

Data Retrievable with GET DATA Command Table 3-2 defines the data defined in Part IV, Annex A of EMV4.1 Book3 that can be retrieved with the GET DATA command, when the data exists in the IC Card. JCB proprietary data that can be retrieved with the GET DATA command is listed in Annex A.Table 3-2Item No. 1 2 3

Data Retrievable with GET DATA CommandTag 9F36 9F13 9F17 Data name

ATC Last Online ATC Register PIN Try Counter

3.2.2

Data Retrievable with GET PROCESSING OPTIONS Command Table 3-3 defines the data that can be retrieved with the GET PROCESSING OPTIONS command, when the data exists in the IC Card.Table 3-3Item No. 1 2

Data Retrievable with GET PROCESSING OPTIONS CommandTag 82 94 Data name

AIP AFL

3.2.3

Data Updatable with Issuer Script Commands Issuer Script commands that can update the data in the IC Card are defined as follows.Refer to Section 4.2 for Issuer Script commands.

(1) PUT DATA (2) UPDATE RECORD

JCB Confidential

3-2

April 2008



3.2.3.1

Data Updatable with PUT DATA Command

Table 3-4 defines the data that can be updated with the PUT DATA command, when the data exists in the IC Card. Data other than those shown in Table 3-4 shall not be updated.Table 3-4Item No. 1 2 3 4 5 6 7 8 9

Data Updatable with PUT DATA CommandTag 9F57 9F58 9F59 9F5A 9F56 9F5B 9F65 9F64 9F66 Data name Upper Consecutive Domestic Offline Limit Lower Consecutive Domestic Offline Limit Upper Consecutive International Offline Limit Lower Consecutive International Offline Limit Cumulative Total Transaction Amount Limit Maximum Domestic Offline Transaction Amount Transaction Currency Conversion Table Cumulative Total Transaction Amount Upper Limit CAC

3.2.3.2

Data Updatable with UPDATE RECORD Command

Table 3-5 defines the data that can be updated with the UPDATE RECORD command, when the data exists in the IC Card. Data other than those shown in Table 3-5 shall not be updated.Table 3-5Item No. 1 2

Data Updatable with UPDATE RECORD CommandTag 9F23 9F14 Data name Upper Consecutive Offline Limit Lower Consecutive Offline Limit

JCB Confidential

3-3

April 2008


4. Command Requirements

44.1

Command RequirementsThis chapter defines the requirements for commands supported by IC Cards.

Transaction CommandsTable 4-1 lists the transaction commands and the supporting conditions of these commands. If the IC Card supports the transaction commands listed in Table 4-1, they shall conform to Part III, Chapter 11 of EMV4.1 Book1 and Part II, Chapter 6 of EMV4.1 Book3. To support transaction commands other than those shown in Table 4-1, approval by JCB is required. This section defines the supporting conditions of these commands and the additional requirements not specified in Part III, Chapter 11 of EMV4.1 Book1 and Part II, Chapter 6 of EMV4.1 Book3.

4.1.1

Supporting ConditionsTable 4-1Item No. 1 2 3 4 5 6 7 8 9

Transaction Commands and Supporting ConditionsCommand name EXTERNAL AUTHENTICATE GENERATE APPLICATION CRYPTOGRAM GET CHALLENGE GET DATA GET PROCESSING OPTIONS INTERNAL AUTHENTICATE READ RECORD SELECT VERIFY Support Optional Mandatory Optional Mandatory Mandatory Optional Mandatory Mandatory Optional

If the following conditions apply, the IC Card shall support the optional commands in Table 4-1. EXTERNAL AUTHENTICATE: When Issuer Authentication is supported GET CHALLENGE: When Offline Enciphered PIN Verification is supported INTERNAL AUTHENTICATE: When DDA is supported VERIFY: When Offline PIN Verification is supported

JCB Confidential

4-1

April 2008


4. Command Requirements 4.1.2 EXTERNAL AUTHENTICATE Command ARPC shall be used as the 8-byte encrypted data in the Issuer Authentication Data contained in the EXTERNAL AUTHENTICATE command message. Additionally, a 2-byte ARC shall be stored at the leftmost of the 1-8 byte area following the encrypted data.Refer to Section 6.2.6 for the verification of ARPC.

4.1.3

GENERATE APPLICATION CRYPTOGRAM Command The IC Card can generate three types of application cryptogram: ARQC, TC and AAC.Refer to Section 6.2.5 for AC (ARQC, TC, and AAC) generation.

Issuer Application Data included in the response message to the GENERATE AC command consists of the following mandatory data. These data shall be concatenated in the following order. (1) Length Indicator (2) DKI (3) Cryptogram Version Number (4) CVR The Length Indicator is a 1-byte data indicating the length of the data formed by concatenating (2), (3) and (4). The DKI is a 1-byte data that specifies the master key defined in Section 6.2.2. When the Issuer uses multiple master keys, this data is used to specify a master key. If this data is not used, the default value of 00 shall be used. The Cryptogram Version Number is a 1-byte data that specifies the session key generation method, AC generation method, ARPC generation method, and secure messaging method. CVR is the data that records the results of processing within the IC Card, such as Card Action Analysis and Completion. When the card responds to a GENERATE AC command that does not request CDA, these data shall be stored according to Format 1 (tag 80) defined in Part II, Section 6.5.5 of EMV4.1 Book 3. When the card responds to a GENERATE AC command that requests CDA, these data shall be stored according to Format defined in Part II, Section 6.6.1 of EMV4.1 Book2. For CDOL1 and CDOL2, which define the content of the data included in the GENERATE AC command message, refer to Sections 5.8 and 5.10, respectively.

JCB Confidential

4-2

April 2008


4. Command Requirements 4.1.4 4.1.5 GET CHALLENGE Command There are no additional requirements for the GET CHALLENGE command. GET DATA Command For data that can be retrieved with the GET DATA command, refer to Section 3.2.1. 4.1.6 GET PROCESSING OPTIONS Command The data format of the response message to the GET PROCESSING OPTIONS command shall conform to Format 1 defined in Part II, Section 6.5.8 of EMV4.1 Book3. For data that can be retrieved with the GET PROCESSING OPTIONS command, refer to Section 3.2.2. For PDOL in the command message, refer to Section 5.2. 4.1.7 INTERNAL AUTHENTICATE Command The data format of the response message to the INTERNAL AUTHENTICATE command shall conform to Format 1 defined in Part II, Section 6.5.9 of EMV4.1 Book3. For DDOL, which defines the content of the data in the INTERNAL AUTHENTICATE command message, refer to Section 5.4. 4.1.8 4.1.9 4.1.10 READ RECORD Command There are no additional requirements for the READ RECORD command. SELECT Command Both 00 and 02 shall be supported as the P2 value for the APDU. VERIFY Command There are no additional requirements for the VERIFY command.

JCB Confidential

4-3

April 2008



4.2

Issuer Script CommandsTable 4-2 lists the supporting conditions for the Issuer Script commands. All commands except the PUT DATA command and UPDATE RECORD command shall conform to Part II, Chapter 6 of EMV4.1 Book3. This chapter defines the supporting conditions for all commands. For all commands except the PUT DATA command and UPDATE RECORD command, additional requirements are defined. For the PUT DATA command and UPDATE RECORD command, their command messages and response messages are defined. All commands in Table 4-2 shall include a MAC (ref: Section 6.2.7) in the command data field.

4.2.1

Supporting ConditionsTable 4-2Item No. 1 2 3 4 5 6

Issuer Script Commands and Supporting ConditionsCommand name APPLICATION BLOCK APPLICATION UNBLOCK PIN CHANGE / UNBLOCK CARD BLOCK PUT DATA UPDATE RECORD Support Optional Optional Optional Optional Optional Optional

When the Issuer has the following Issuer Script requirements, the IC Card shall support the optional commands. APPLICATION BLOCK: When blocking an application APPLICATION UNBLOCK: When unblocking an application PIN CHANGE/UNBLOCK: When changing the PIN and/or unblocking the PIN CARD BLOCK: When blocking all applications residing on the IC Card PUT DATA: When updating data defined in Section 3.2.3.1 UPDATE RECORD: When updating data defined in Section 3.2.3.2 4.2.2 APPLICATION BLOCK Command There are no additional requirements for the APPLICATION BLOCK command.

JCB Confidential

4-4

April 2008


4. Command Requirements 4.2.3 APPLICATION UNBLOCK Command There are no additional requirements for the APPLICATION UNBLOCK command. 4.2.4 PIN CHANGE/UNBLOCK Command The value of P2 in the command message is defined as follows: (1) P2 = 00: Unblocks the PIN and does not change the PIN. (2) P2 = 02: Unblocks the PIN and changes the PIN.NOTE: If P2 = 02, PIN enciphered in the method defined in Section 6.2.7 shall be included in the data field.

4.2.5 4.2.64.2.6.1

CARD BLOCK Command There are no additional requirements for the CARD BLOCK command. PUT DATA CommandDefinition

The PUT DATA command shall conform to ISO/IEC7816-4. requirements for the PUT DATA command are defined below.

Additional

For data that can be updated with the PUT DATA command, refer to Section 3.2.3.1.4.2.6.2 Command Message

Table 4-3 defines the command message for the PUT DATA command. The Command Data should not be encrypted.Table 4-3Code

PUT DATA Command MessageValue

CLA INS P1, P2 Lc Data Le

04 DA Tag of data to be updated Length of data field New value of data object and MAC None

4.2.6.3

Status Word Included in Response Message

If the command is successfully executed, the status word 9000 shall be returned in the response message.

JCB Confidential

4-5

April 2008



If the command is not executed successfully, the status word shown in Table 4-4 shall be returned in the response message.Table 4-4Status

Status Word for Unsuccessful Execution of PUT DATA CommandSW1 62 62 64 65 69 69 69 69 69 67 6A 6A 6A 6A SW2 00 81 00 81 82 85 86 87 88 00 80 81 84 85 Description Information not provided Part of returned data may be corrupted State of nonvolatile memory not changed Memory failure Security status not satisfied Conditions of use not satisfied Command not allowed Secure messaging data object missing Secure messaging data object invalid Wrong length of data field Incorrect parameters in data field Function not supported Insufficient memory space Lc incompatible with TLV structure

Warning

Error

4.2.74.2.7.1

UPDATE RECORD CommandDefinition

The UPDATE RECORD command shall conform to ISO/IEC7816-4. Additional requirements for the UPDATE RECORD command are defined below. For data that can be updated with the UPDATE RECORD command, refer to Section 3.2.3.2.4.2.7.2 Command Message

Table 4-5 defines the command message for the UPDATE RECORD command. The Command Data should not be encrypted.Table 4-5Code CLA INS P1 P2 Lc Data Le

UPDATE RECORD Command MessageValue

04 DC Record number to be updated Reference Control Parameter (see Table 4-6) Length of data field New value of data object and MAC None

JCB Confidential

4-6

April 2008



The structure for the reference control parameter of P2 is defined in Table 4-6.Table 4-6b8 X b7 X

Reference Control Parameterb6 X b5 X b4 X b3 b2 b1 Description

1

0

0

SFI P1 indicates record number

4.2.7.3

Status Word Included in Response Message

If the command is successfully executed, the status word 9000 shall be returned in the response message. If the command is not executed successfully, the status word shown in Table 4-7 shall be returned in the response message.Table 4-7Status Status Word for Unsuccessful Execution of UPDATE RECORD Command SW1 62 62 64 65 69 69 69 69 69 67 6A 6A 6A 6A 6A SW2 00 81 00 81 81 82 86 87 88 00 81 82 83 84 85 Description Information not provided Part of returned data may be corrupted State of nonvolatile memory not changed Memory failure Command incompatible with file organization Security status not satisfied Command not allowed Secure messaging data object missing Secure messaging data object invalid Wrong length of data field Function not supported File not found Record not found Insufficient memory space Lc incompatible with TLV structure

Warning

Error

JCB Confidential

4-7

April 2008


5. Functional Requirements

5

Functional RequirementsRegarding functions supported by the IC Card, this chapter defines additional requirements not specified in EMV4.1. To support functions other than those defined in this chapter, approval by JCB shall be obtained. For the functions defined in this chapter, the data used and the transaction flow are described in Annexes A and B. As functional requirements, this chapter describes the definitions, conditions of execution, processing data and processing: (1) Definitions and Conditions of Execution The definitions, supporting conditions and conditions of execution for each function are described. (2) Processing Data Data used in each function is executed is described. In the Initial Storage column, T indicates data stored in the Terminal, C indicates data stored in the IC Card, and I indicates data included in the response message from the Issuer. Data listed as mandatory in the Presence column is data that must be present in order for the processing to be performed. Data listed as optional need not be present when performing the processing. This specification does not define a specific tag for data whose tag is listed as -. (3) Processing The processing of each function is described.

5.15.1.1

Application SelectionDefinition and Conditions of Execution Application Selection shall conform to Part III, Chapter 12 of EMV4.1 Book1. Support of Application Selection by the IC Card is mandatory. In addition, support of Partial Name Selection specified in Part III, Chapter 12 of EMV4.1 Book1 is mandatory.

5.1.2

Processing Data Tables 5-1 to 5-5 list IC Card data used in Application Selection. FCI included in the ADF, as shown in Table 5-3, is mandatory, while PSE, DDF, DDF Directory Entry and ADF Directory Entry are optional.

JCB Confidential

5-1

April 2008



Table 5-1Item No.

FCI Data Included in PSETag Data name Initial Storage C C C C C C C Presence

1 2 3 4 5 6 7 Table 5-2Item No.

6F 84 A5 88 5F2D 9F11 BF0C

FCI Template DF Name FCI Proprietary Template SFI of the directory elementary file Language Preference Issuer Code Table Index FCI Issuer Discretionary Data

Mandatory Mandatory Mandatory Mandatory Optional Optional Optional

FCI Data Included in DDFTag Data name Initial Storage C C C C C Presence

1 2 3 4 5 Table 5-3Item No.

6F 84 A5 88 BF0C

FCI Template DF Name FCI Proprietary Template SFI of the directory elementary file FCI Issuer Discretionary Data

Mandatory Mandatory Mandatory Mandatory Optional

FCI Data Included in ADFTag Data name Initial Storage C C C C C C C C C C Presence

1 2 3 4 5 6 7 8 9 10

6F 84 A5 50 87 9F38 5F2D 9F11 9F12 BF0C

FCI Template DF Name (AID) FCI Proprietary Template Application Label Application Priority Indicator PDOL Language Preference Issuer Code Table Index Application Preferred Name FCI Issuer Discretionary Data

Mandatory Mandatory Mandatory Optional Optional Optional Optional Optional Optional Optional

JCB Confidential

5-2

April 2008



Table 5-4Item No.

DDF Directory Entry DataTag Data name Initial Storage C C Presence

1 2 Table 5-5Item No.

9D 73

DDF Name Directory Discretionary Template

Mandatory Optional

ADF Directory Entry DataTag Data name Initial Storage C C C C C Presence

1 2 3 4 5

4F 50 9F12 87 73

ADF Name (AID) Application Label Application Preferred Name Application Priority Indicator Directory Discretionary Template

Mandatory Mandatory Optional Optional Optional

5.1.3

Processing The processing of Application Selection shall conform to Part III, Chapter 12 of EMV4.1 Book1. Application Selection shall always be the first processing performed immediately after resetting the IC Card.

JCB Confidential

5-3

April 2008



5.25.2.1

Initiate Application ProcessingDefinition and Conditions of Execution Initiate Application Processing shall conform to Part III, Section 10.1 of EMV4.1 Book3. Support of Initiate Application Processing by IC Cards is mandatory.

5.2.2

Processing Data Table 5-6 lists the data used in Initiate Application Processing.Table 5-6Item No.

Data Used in Initiate Application ProcessingTag Data name Initial Storage C C C C C C Presence

1 2 3 4 5 6

82 94 9F38 9F36 9F27 -

AIP AFL PDOL ATC CID CVR

Mandatory Mandatory Optional Mandatory Mandatory Mandatory

5.2.3

Processing The processing of Initiate Application Processing shall conform to Part III, Section 10.1 of EMV4.1 Book3. Additional requirements are defined below. An IC Card shall perform the following processing when it receives the GET PROCESSING OPTIONS command. (1) Increment the ATC by 1. (2) Set all bits of the CID to 0. (3) Set all bits of CVR, except the Length Indicator, to 0. Though the IC Card is allowed to change the AFL in the response according to the value in the PDOL, the AIP shall not be changed. Data necessary to change the AFL dynamically shall be specified in the PDOL.

JCB Confidential

5-4

April 2008



5.35.3.1

Read Application DataDefinition and Conditions of Execution Read Application Data shall conform to Part III, Section 10.2 of EMV4.1 Book3. Support of Read Application Data by the IC Card is mandatory.

5.3.2

Processing Data In Read Application Data, data is read from the record specified in the AFL, which is returned to the Terminal in the response to Initiate Application Processing.

5.3.3

Processing The processing of Read Application Data shall conform to Part III, Section 10.2 of EMV4.1 Book3.

JCB Confidential

5-5

April 2008



5.45.4.1

Offline Data AuthenticationDefinition and Conditions of Execution Offline Data Authentication consists of the following functions defined in Part II, Chapters 5 and 6 of EMV4.1 Book2 and Part III, Section 10.3 of EMV4.1 Book3. (1) SDA (Static Data Authentication) (2) DDA (Standard Dynamic Data Authentication) (3) CDA (Combined Dynamic Data Authentication/Application Cryptogram Generation) The supporting conditions of the IC Card are listed in Table 5-7.Table 5-7 Supporting Conditions of Offline Data AuthenticationSupport Mandatory Note When the IC Card supports SDA, the following bit of AIP shall be set to 1.

Item No. 1

Functionality SDA

AIP(1,7)SDA supported2 DDA Optional1 When the IC Card supports DDA, the following bits of AIP shall be set to 1.

AIP(1,7)SDA supported AIP(1,6)DDA supported3 CDA Optional When the IC Card supports CDA, the following bits of AIP shall be set to 1.

AIP(1,7)SDA supported AIP(1,6)DDA supported AIP(1,1)CDA supported1

Mandatory if the card supports CDA NOTE: Of the supporting conditions in Table 5-7, since items listed as Optional may be required under certain conditions, JCB must be consulted regarding the necessity of their implementation.

JCB Confidential

5-6

April 2008



5.4.2

Processing Data Table 5-8 lists the data used in SDA.Table 5-8Item No.

Data Used in SDATag Data name Initial Storage C C C C C C C C C C Presence

1 2 3 4 5 6 7 8 9 10

82 8F 5A 93 90 9F32 92 94 9F4A -

AIP CA Public Key Index Application PAN Signed Static Application Data Issuer Public Key Certificate Issuer Public Key Exponent Issuer Public Key Remainder AFL SDA Tag List Static Data to be Authenticated

Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Optional Mandatory Optional Mandatory

NOTE: All data for items 1 through 10 are passed to the Terminal during Initiate Application Processing and Read Application Data described in Sections 5.2 and 5.3. Item 10 consists of the data specified by items 8 and 9. The item 9 shall only contain the tag 82 for the AIP. Refer to Part II, Chapters 5 and 6 of EMV4.1 Book2 for the conditions regarding the existence of item 7.

Table 5-9 shows the recommended input data for Static Data to be Authenticated.Table 5-9Item No. 1 2 3 4 5 6 7 8 9 10

Recommended Input Data for Static Data to be AuthenticatedTag 5F25 5F24 82 5A 5F34 9F07 8E 9F0D 9F0E 9F0F Data name Application Effective Date Application Expiration Date AIP Application PAN Application PAN Sequence Number AUC CVM List IAC - Default IAC - Denial IAC - Online

Table 5-10 lists the data used in DDA.

JCB Confidential

5-7

April 2008



Table 5-10Item No.

Data Used in DDATag Data name Initial Storage C C C C C C C C C C C C C C C C C T C Presence

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

82 8F 5A 9F49 9F46 9F47 9F48 90 9F32 92 94 9F4A 9F4B 9F4C -

AIP CA Public Key Index Application PAN DDOL ICC Public Key Certificate ICC Public Key Exponent ICC Public Key Remainder Issuer Public Key Certificate Issuer Public Key Exponent Issuer Public Key Remainder AFL SDA Tag List ICC Public Key (Modulus) Signed Dynamic Application Data Static Data to be Authenticated ICC Dynamic Number ICC Private Key Exponent Terminal Dynamic Data CVR

Mandatory Mandatory Mandatory Optional Mandatory Mandatory Optional Mandatory Mandatory Optional Mandatory Optional Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory

NOTE: Items 1 through 12 are data passed to the Terminal during Initiate Application Processing and Read Application Data described in Sections 5.2 and 5.3. The DDOL value in item 4 shall include the tag 9F37 for the Unpredictable Number. For others, the Issuer may add on its own values as long as they conform to the definitions in Part III, Section 10.3 of EMV4.1 Book3. If the DDOL does not exist, the Default DDOL, mandatory at the Terminal, shall be used in DDA. Data specified in the DDOL is passed from the Terminal to the IC Card as item 18. As for the input to item 15, the data shown in Table 5-9 is recommended. The first 2 bytes of item 16 shall contain the ATC and optionally other data.

Table 5-11 lists the data used in CDA.

JCB Confidential

5-8

April 2008



Table 5-11Item No.

Data Used in CDATag Data name Initial Storage C C C C C C C C C C C C C C C C C C C C C T C Presence

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

82 8F 5A 9F38 8C 8D 9F46 9F47 9F48 90 9F32 92 94 9F4A 9F4B 9F4C 9F27 9F26 9F37 -

AIP CA Public Key Index Application PAN PDOL CDOL1 CDOL2 ICC Public Key Certificate ICC Public Key Exponent ICC Public Key Remainder Issuer Public Key Certificate Issuer Public Key Exponent Issuer Public Key Remainder AFL SDA Tag List ICC Public Key (Modulus) Signed Dynamic Application Data Static Data to be Authenticated ICC Dynamic Number CID AC (TC or ARQC) ICC Private Key Exponent Unpredictable Number CVR

Mandatory Mandatory Mandatory Optional Optional Optional Mandatory Mandatory Optional Mandatory Mandatory Optional Mandatory Optional Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory

NOTE: Items 1 through 14 are data passed to the Terminal through Application Selection, Initiate Application Processing, and Read Application Data in Sections 5.1, 5.2, and 5.3. Item 5 is used when CDA is executed in the first GENERATE AC command. In such cases, the value of CDOL1 shall include the tag 9F37 for the Unpredictable Number. Item 6 is used when CDA is executed in the second GENERATE AC command. In such cases, the value of CDOL2 shall include the tag 9F37 for the Unpredictable Number. As for the input to item 17, data shown in Table 5-9 is recommended. The first 2 bytes of item 18 shall contain the ATC and optionally other data.

JCB Confidential

5-9

April 2008



5.4.3

Processing The IC Card does not take part in SDA. The processing of DDA and CDA shall conform to Part II, Chapters 5 and 6 of EMV4.1 Book2 and Part III, Section 10.3 of EMV4.1 Book3. Additional requirements for DDA and CDA are defined below. When an IC Card receives the INTERNAL AUTHENTICATE command issued by a terminal, it shall set the Offline Dynamic Data Authentication Performed bit in CVR(4,2) to 1. When an IC Card receives the GENERATE AC command that requests CDA issued by a terminal and responds with either TC or ARQC, it shall set the Combined DDA/AC Generation performed bit in CVR(4,1) to 1.

JCB Confidential

5-10

April 2008



5.55.5.1

Processing RestrictionsDefinition and Conditions of Execution Processing Restrictions consists of the following compatibility checks defined in Part III, Section 10.4 of EMV4.1 Book3. (1) Application Version Number (2) Application Usage Control (3) Application Effective/Expiration Dates Checking Support of Application Version Number and Application Expiration Dates Checking by the IC Card are mandatory, while support of Application Usage Control and Application Effective Dates Checking are optional.

5.5.2

Processing Data If Processing Restrictions functions are supported, the following processing data shall be stored in the IC Card. These data are passed to the Terminal during Read Application Data described in Section 5.3. Table 5-12 lists the data used when checking the Application Version Number.Table 5-12Item No.

Data Used when Checking the Application Version NumberTag Data name Initial Storage C Presence

1

9F08

Application Version Number

Mandatory

NOTE: The version number of the IC Card conforming to this version of the specification is 2.0, and item 1 shall store '0200'.

Table 5-13 lists the data used in Application Usage Control.Table 5-13Item No.

Data Used in Application Usage ControlTag Data name Initial Storage C C Presence

1 2

9F07 5F28

AUC Issuer Country Code

Mandatory Optional

Table 5-14 lists the data used in Application Effective Dates Checking.

JCB Confidential

5-11

April 2008



Table 5-14Item No.

Data Used in Application Effective Dates CheckingTag Data name Initial Storage C Presence

1

5F25

Application Effective Date

Mandatory

Table 5-15 lists the data used in Application Expiration Dates Checking.Table 5-15Item No.

Data Used in Application Expiration Dates CheckingTag Data name Initial Storage C Presence

1

5F24

Application Expiration Date

Mandatory

5.5.3

Processing The IC Card does not take part in Processing Restrictions.

JCB Confidential

5-12

April 2008



5.65.6.1

Cardholder VerificationDefinition and Conditions of Execution Cardholder Verification consists of the following cardholder verification methods defined in Part II, Chapter 7 of EMV4.1 Book2 and Part III, Section 10.5 of EMV4.1 Book3. However, the Issuer can add on other methods defined in EMV such as combinations, or other methods undefined in EMV such as fingerprint verification or digital signature, with the approval of JCB. (1) Offline Plaintext PIN (2) Offline Enciphered PIN (3) Online Enciphered PIN (4) Signature (5) No CVM Supporting conditions of the functions are listed in Table 5-16. Table 5-16 lists the CVM code defined in Part IV, Annex C3 of EMV4.1 Book 3.Table 5-16 CVM CodeByte1 b8 b7 B6 b5 b4 b3 b2 B1 Support

Function

Offline Enciphered PIN Offline Plaintext PIN Online Enciphered PIN Signature No CVM

0 0 0 0 0

1/0 1/0 1/0 1/0 1/0

0 0 0 0 0

0 0 0 1 1

0 0 0 1 1

1 0 0 1 1

0 0 1 1 1

0 1 0 0 1

Optional Optional Mandatory Mandatory Mandatory

NOTE: Of the supporting conditions in Table 5-16, since items listed as Optional may be required under certain conditions, JCB must be consulted regarding the necessity of their implementation.

The CVM code for other methods of verification such as fingerprint verification or digital signature shall be defined by JCB as necessary. In order to support Cardholder Verification functions, the Cardholder verification is supported bit in the AIP(1,5) shall be set to 1.

JCB Confidential

5-13

April 2008


5. Functional Requirements 5.6.2 Processing Data Table 5-17 lists the data used in Cardholder Verification.Table 5-17Item No.

Data Used in Cardholder VerificationTag Data name Initial Storage C C Presence

1 2

82 8E

AIP CVM List

Mandatory Mandatory

NOTE: All data for items 1 and 2 are passed to the Terminal during Initiate Application Processing and Read Application Data described in Sections 5.2 and 5.3, respectively.

Table 5-18 lists the common data used for both plaintext PIN and enciphered PIN in Offline PIN Verification.Table 5-18Item No.

Data Used in Offline PIN VerificationTag Data name Initial Storage T C C C C C Presence

1 2 3 4 5 6

99 9F17 9F61

Transaction PIN Data CVR PIN Try Counter PIN Try Limit Reference PIN Data ADA

Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory

NOTE: Data for item 3 is passed to the Terminal with the GET DATA command described in Section 3.2.1.

Table 5-19 lists the data used in Offline Enciphered PIN Verification.

JCB Confidential

5-14

April 2008



Table 5-19Item No.

Data Used in Offline Enciphered PIN VerificationTag Data name Initial Storage C C C C C Presence

1 2 3 4 5 6 7 8 9

8F 90 9F32 92 9F2D 9F2E 9F2F -

CA Public Key Index Issuer Public Key Certificate Issuer Public Key Exponent Issuer Public Key Remainder ICC PIN Encipherment Public Key Certificate ICC PIN Encipherment Public Key Exponent ICC PIN Encipherment Public Key Remainder ICC PIN Encipherment Public Key (Modulus) ICC PIN Encipherment Private Key Exponent

Mandatory Mandatory Mandatory Optional Mandatory Mandatory Optional Mandatory Mandatory

C C C C

NOTE: All data except items 8 and 9 are passed to the Terminal during Read Application Data described in Section 5.3. The items 5,6,7,8 and 9 may not be used in some cases that are specified in Part II, Section 7 of EMV4.1 Book2.

5.6.3

Processing The IC Card does not take part in Online Enciphered PIN Verification, signature and No CVM. The processing of each Cardholder Verification function shall conform to Part II, Chapter 7 of EMV4.1 Book2 and Part III, Section 10.5 of EMV4.1 Book3. Additional requirements regarding Offline Plaintext/Enciphered PIN Verification are defined below. If the IC Card receives the GET DATA command requesting the PIN Try Counter, it shall check the PIN Try Counter value before returning a response. If the PIN Try Counter is 0, the PIN Try Limit exceeded bit in the CVR(3,7) shall be set to 1. If the PIN Try Counter is 0, that shall indicate that the PIN is blocked. If the IC Card receives the VERIFY command, the following processing shall be performed. (1) If the PIN Try Counter is not 0, the PIN Try Counter value shall be decremented by one, and the following processing shall be performed. (a) Compare the Transaction PIN in the VERIFY command with the Reference PIN.

JCB Confidential

5-15

April 2008



(b) If the Transaction PIN and Reference PIN match, the following processing shall be performed: [1] Set the PIN Try Limit value in the PIN Try Counter. [2] Set the Offline PIN verification failed bit in the CVR(2,2) to 0. [3] Set the Offline PIN verification performed bit in the CVR(2,3) to 1. [4] Return 9000 to the Terminal as the response to the VERIFY command. (c) If the Transaction PIN and the Reference PIN do not match, the following processing shall be performed: [1] Set the Offline PIN verification failed bit in the CVR(2,2) to 1. [2] Set the Offline PIN verification performed bit in the CVR(2,3) to 1. [3] Check the PIN Try Counter value. (I) If the value is 0, the following processing shall be performed. (i) Set the PIN Try Limit exceeded bit in the CVR(3,7) to 1. (ii) The If PIN Try Limit exceeded on current transaction, block application bit in the ADA(2,8) is 1, set the Application blocked by IC Card because PIN Try Limit exceeded bit in the CVR(3,2) to 1 and block the application. (iii) Return 63C0 to the Terminal as the response to the VERIFY command. (II) If the value is not 0, the following processing shall be performed. (i) Return 63CX (X indicates the remaining number of PIN tries) to the Terminal as the response to the VERIFY command. If the remaining number of PIN tries is equal to or more than 15, return 63CF to the Terminal. (2) If the PIN Try Counter is 0, the following processing shall be performed: (a) Set the PIN Try Limit exceeded bit in the CVR(3,7) to 1. (b) Set the Offline PIN verification performed bit in the CVR(2,3) to 1. (c) Return 6983 to the Terminal as the response to the VERIFY command.

JCB Confidential

5-16

April 2008



5.75.7.1

Terminal Risk ManagementDefinition and Conditions of Execution Terminal Risk Management consists of the following functions defined in Part III, Section 10.6 of EMV4.1 Book3. (1) Terminal Floor Limit Checking (2) Random Transaction Selection (3) Terminal Velocity Checking (4) Exception File Checking Terminal Floor Limit Checking, Random Transaction Selection, and Exception File Checking are procedures within the Terminal, and their support depends on the Terminal. Support of Terminal Velocity Checking by the IC Card is optional. Support of Terminal Risk Management by the IC Card is mandatory, and Terminal risk management is to be performed bit in the AIP(1,4) shall be set to 1.

5.7.2

Processing Data Table 5-20 lists the data used in Terminal Risk Management.Table 5-20Item No.

Data Used in Terminal Risk ManagementTag Data name Initial Storage C Presence

1

82

AIP

Mandatory

NOTE: Data for item 1 is passed to the Terminal during Initiate Application Processing described in Section 5.2.

Table 5-21 lists the data used in Terminal Floor Limit Checking.Table 5-21Item No.

Data Used in Terminal Floor Limit CheckingTag Data name Initial Storage C C Presence

1 2

5A 5F34

Application PAN Application PAN Sequence Number

Optional Optional

NOTE: Data for items 1 and 2 are passed to the Terminal during Read Application Data described in Section 5.3.

Table 5-22 lists the data used in Terminal Velocity Checking.

JCB Confidential

5-17

April 2008



Table 5-22Item No.

Data Used in Terminal Velocity CheckingTag Data name Initial Storage C C C C Presence

1 2 3 4

9F14 9F23 9F36 9F13

Lower Consecutive Offline Limit Upper Consecutive Offline Limit ATC Last Online ATC Register

Mandatory Mandatory Mandatory Mandatory

NOTE: Data for items 1 and 2 are passed to the Terminal during Read Application Data described in Section 5.3. The data for items 3 and 4 are passed to the Terminal with the GET DATA command described in Section 3.2.1.

5.7.3

Processing The IC Card does not take part in Terminal Floor Limit Checking, Random Transaction Selection and Exception File Checking. The processing of Terminal Velocity Checking shall conform to Part III, Section 10.6 of EMV4.1 Book3.

JCB Confidential

5-18

April 2008



5.85.8.1

Terminal Action AnalysisDefinition and Conditions of Execution Terminal Action Analysis shall conform to Part III, Section 10.7 of EMV4.1 Book3. Support of Terminal Action Analysis by the IC Card is mandatory.

5.8.2

Processing Data Table 5-23 lists the data used in Terminal Action Analysis.Table 5-23Item No.

Data Used in Terminal Action AnalysisTag Data name Initial Storage C C C Presence

1 2 3

9F0E 9F0F 9F0D

IAC Denial IAC Online IAC Default

Optional Optional Optional

NOTE: Data for items 1 to 3 are passed to the Terminal during Read Application Data described in Section 5.3. The tags of the data that shall be retrieved from the Terminal in order to perform Card Action Analysis defined in Section 5.9, and the tags of the data defined in Section 6.2.5 AC Generation, shall be included in CDOL1. If CDA is performed for data authentication defined in Section 5.4, the tag 9F37for the Unpredictable Number, must be included.

5.8.3

Processing The IC Card does not take part in Terminal Action Analysis.

JCB Confidential

5-19

April 2008



5.95.9.1

Card Action AnalysisDefinition and Conditions of Execution Card Action Analysis shall conform to Part III, Section 10.8 of EMV4.1 Book3. As additional requirements, the following functions listed in Table 5-24 are defined as check items.

JCB Confidential

5-20

April 2008



Table 5-24Item No.

Definitions of Check Items for Card Action AnalysisCheck Results Check Item DescriptionDetermines whether online processing was incomplete in the last online transaction. Determines whether Issuer Authentication failed or not performed although mandatory in the last online transaction. Determines whether SDA failed and the transaction was declined offline in previous transactions. Determines whether DDA or CDA failed and the transaction was declined offline in previous transactions. Determines whether the processing of the Issuer Script command failed in the last online transaction. Determines whether the cumulative number of consecutive offline transactions has exceeded the limit. The Issuer sets separate upper and lower limits for domestic and international use. Determines whether the cumulative amount of consecutive offline transactions has exceeded the limit set by the Issuer. As for the limits, the Issuer shall set to the upper and lower limits. Determines whether the transaction is with a IC Card that has never performed online processing. Determines whether the number of PIN Tries has been decreased to 0 in the previous transaction when Offline Plaintext/Enciphered PIN Verification is not to be performed for this transaction. Determines whether the domestic transaction amount exceeds the limit set by the Issuer with this transaction.Online capable Terminal OfflineOnly Terminal

1

2

Last Online Transaction Not Completed Issuer Authentication Failure On Last Online Transaction SDA Failure on Last Transaction DDA Failure on Last Transaction Issuer Script Processing Failure on Last Online Transaction Card Velocity Checking

ARQC

AAC/ TC

ARQC

TC

3 4

TC

TC

TC

TC

5

ARQC

AAC

6

ARQC

AAC

7

Cumulative Offline Transaction Amount Checking New Card Checking Offline PIN Verification Not Performed Card Floor Limit Checking

ARQC

AAC

8

ARQC /TC ARQC/ AAC/ TC

AAC/ TC

9

AAC /TC

10

ARQC

AAC

Support of Card Action Analysis by the IC Card is mandatory. However, the supporting conditions for individual check items are listed in Table 5-25.

JCB Confidential

5-21

April 2008



Table 5-25Item No. 1 2 3 4 5 6 7 8 9 101

Supporting Conditions of Card Action AnalysisCheck Item Last Online Transaction Not Completed Issuer Authentication Failure On Last Online Transaction SDA Failure on Last Transaction DDA Failure on Last Transaction Issuer Script Processing Failure on Last Online Transaction Card Velocity Checking Cumulative Offline Transaction Amount Checking New Card Checking Offline PIN Verification Not Performed Card Floor Limit Checking Support Optional Optional1 2 Mandatory Optional1 Optional1 Optional2 Optional2 Optional2 Optional2 Optional

2

Support of items 2, 4, or 5 is mandatory if the IC Card supports Issuer Authentication, DDA, CDA, or Issuer Script, respectively. Items 2, 6, 7, 8, and 9 are functions also defined in Completion in Section 5.12, and if they are supported in Completion, their support in Card Action Analysis is mandatory.

When the IC Card receives the first GENERATE AC command, Card Action Analysis shall always be performed. As for the individual check items included in Card Action Analysis, if the IC Card supports them, they shall always be performed. The Card Action Analysis Support Information (CAASI) defines which check items are supported by the IC Card. CAASI data structure is illustrated in Table 5-26. However, the order in which the individual check items are performed is not defined. Regardless of the results of any check items, the IC Card shall perform all check items it supports. If data necessary for processing does not exist, the processing shall continue with the next check item.

JCB Confidential

5-22

April 2008



Table 5-26

Data Structure of CAASI

CAASI Byte1 b8 b7 b6 b5 b4 b3 b2 b1 Meaning Last Online Transaction Not Completed Checking Issuer Authentication Failure on Last Online Transaction checking SDA Failure on Last Transaction checking DDA Failure on Last Transaction checking Issuer Script Processing Failure on Last Online Transaction checking Card Velocity Checking Cumulative Offline Transaction Amount Checking New Card Checking

1 1 1 1 1 1 1 1

CAASI Byte2 b8 b7 b6 b5 b4 b3 b2 b1 Meaning Offline PIN Verification Not Performed checking Card Floor Limit Checking RFU 2nd Issuer Authentication Failure On Last Online Transaction Checking 2nd Card Velocity Checking (upper limit) 2nd New Card Checking 2nd Offline PIN Verification Not Performed checking

1 1 0 0 1 1 1 1

CAASI Byte3 b8 b7 b6 b5 b4 b3 b2 b1 Meaning 2 Cumulative Offline Transaction Amount Checking (upper limit) RFUnd

1 0 0 0 0 0 0 0

JCB Confidential

5-23

April 2008



5.9.2

Processing Data Table 5-27 lists the data used in Card Action Analysis. Presence of data is independent of the supporting conditions of the check items.Table 5-27Item No.

Data Used in Card Action AnalysisTag Data name Initial Storage C C C C T C T Presence

1 2 3 4 5 6 7

9F61 9F63 9F35 9F27 95

ADA CVR CAAI CAASI Terminal Type CID TVR

Mandatory Mandatory Mandatory Mandatory Optional Mandatory Mandatory

Tables 5-28 to 5-30 show the data structures of items 1 through 3.Table 5-28ADA Byte1 b8 0 b7 b6 b5 b4 b3 b2 b1 Meaning RFU If issuer authentication performed and failed, decline transaction If issuer authentication is mandatory and no ARPC received, decline transaction If transaction declined offline, create advice If PIN Try Limit exceeded on current transaction and transaction is declined, create advice If transaction declined because issuer authentication failed or not performed, create advice If new card, transmit transaction online If new card, decline if unable to transmit transaction online

Data Structure of ADA

1 1 1 1

1 1 1

JCB Confidential

5-24

April 2008



ADA Byte2 b8 b7 b6 b5 b4 b3 b2 b1 Meaning If PIN Try Limit exceeded on current transaction, block application If PIN Try Limit exceeded on previous transaction, decline transaction If PIN Try Limit exceeded on previous transaction, transmit transaction online If PIN Try Limit exceeded on previous transaction, decline if unable to transmit transaction online RFU If online authorisation not completed on previous transaction, decline if unable to transmit transaction online

1 1 1 1 0 0 0 1

Table 5-29CVR Byte1 b8 0 b7 0

Data Structure of CVR

b6 0

b5 0

b4 0

b3 1

b2 0

b1 0

Meaning

Length Indicator

CVR Byte2 b8 0 0 1 1 b7 0 1 0 1 b6 b5 b4 b3 b2 b1 Meaning AAC returned in second GENERATE AC TC returned in second GENERATE AC Second GENERATE AC not requested RFU AAC returned in first GENERATE AC TC returned in first GENERATE AC ARQC returned in first GENERATE AC RFU Issuer authentication performed and failed Offline PIN verification performed Offline PIN verification failed Unable to go online

0 0 1 1

0 1 0 1 1 1 1 1

JCB Confidential

5-25

April 2008



CVR Byte3 b8 1 b7 b6 b5 b4 b3 b2 b1 Meaning Last online transaction not completed PIN Try Limit exceeded RFU New card Issuer authentication failure on last online transaction Issuer authentication not performed after online authorisation Application blocked by card because PIN Try Limit exceeded Offline static data authentication failed on last transaction and transaction declined offline

1 0 1 1 1 1 1

CVR Byte4 b8 b7 b6 b5 b4 b3 b2 b1 Meaning Number of Issuer Script commands received after the second GENERATE AC command containing secure messaging processed on last transaction Issuer Script processing failed on last transaction Offline dynamic data authentication failed on last transaction and transaction declined offline Offline dynamic data authentication performed Combined DDA/AC Generation performed

X

X

X

X

1 1 1 1

JCB Confidential

5-26

April 2008



CVR Byte5 b8 1 b7 b6 b5 b4 b3 b2 b1 Meaning Lower consecutive offline limit exceeded Upper consecutive offline limit exceeded Cumulative total transaction amount limit exceeded Floor limit exceeded RFU Cumulative total transaction amount upper limit exceeded RFU

1 1 1 0 0 1 0 Table 5-30Item No. 1 2 3 4 5

Data for CAAIData Online Authorization Indicator Issuer Authentication Failure Indicator Issuer Script Failure Indicator SDA Failure Indicator DDA Failure Indicator

NOTE: Each item in the CAAI is internal data in the IC Card with a value of either 0 or 1, and shall be stored in nonvolatile memory.

Table 5-31 lists the data used when checking Issuer Script Processing Failure on Last Online Transaction.Table 5-31 Data Used when Checking Issuer Script Processing Failure on Last Online TransactionItem No. Tag Data name Initial Storage C Presence

1

-

Issuer Script Command Counter

Optional

NOTE: Item 1 is used to store the number of Issuer Script commands that the IC Card receives from the Terminal during a transaction. This item is mandatory if the IC Card supports Issuer Script.

JCB Confidential

5-27

April 2008



Table 5-32 lists the data used in Card Velocity Checking.Table 5-32Item No.

Data Used in Card Velocity CheckingTag Data name Initial Storage T C T C C C C Presence

1 2 3 4 5 6 7 8 9 10

9F1A 5F28 5F2A 9F42 9F36 9F13 9F58 9F5A 9F57 9F59

Terminal Country Code Issuer Country Code Transaction Currency Code Application Currency Code ATC Last Online ATC Register Lower Consecutive Domestic Offline Limit Lower Consecutive International Offline Limit Upper Consecutive Domestic Offline Limit Upper Consecutive International Offline Limit

Optional Optional Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory

C C C

NOTE: Items 1 through 4 are used to determine whether the transaction is domestic or international. If either items 1 or 2 does not exist, items 3 and 4 alone determine whether the transaction is domestic or international, as described in Section 5.9.3.7.

Table 5-33 lists the data used in Cumulative Offline Transaction Amount Checking.Table 5-33Item No.

Data Used in Cumulative Offline Transaction Amount CheckingT

ic card specification 20 eng

Documents

event jcb

word of jcb

construed jcb andor

intellectual property

loss of information

uptodate information

exclusive information

documentations of emvco