EMV v4.1 Book 1 ICC to Terminal Interface (2024)

(1)

EMV

Integrated Circuit Card

Specifications for Payment Systems

Book 1

Application Independent ICC to Terminal

Interface Requirements

Version 4.1

May 2004

(2)(3)

© 1994-2004 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at

http://www.emvco.com/specifications.cfm.

EMV

Integrated Circuit Card

Specifications for Payment Systems

Book 1

Application Independent ICC to Terminal

Interface Requirements

Version 4.1

May 2004

(4)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

(5)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

May 2004 Page iii

Revision Log - Version 4.1

The following changes have been made to Book 1 since the publication of Version 4.0.

Incorporated changes described in the following General bulletins:

General Bulletin no. 11: Book 1 - Amendment 1 - Electromechanical Characteristics for Cards and Terminals operating at 5V, 3V and 1.8V

Incorporated changes described in the following Specification Updates:

Specification Update Bulletin no. 4: Change to status of ‘Presence’ of the Application Label data element

Specification Update Bulletin no. 14: Change to format specification for the Application Label and Application Preferred Name

Specification Update Bulletin no. 19: Support for Transaction Log Files Specification Update Bulletin no. 24: Terminal Behaviour During Application Selection

Specification Update Bulletin no. 25: Common Core Definitions

Specification Update Bulletin no. 29: Error Handling during Application Selection

Specification Update Bulletin no. 32: New data elements for domestic/proprietary processing

Specification Update Bulletin no. 33: Terminate clarification

Updated in support of the following Application Notes:

Application Note no. 1: IFSC Negotiation during Chaining Application Note no. 2: Coding and Usage of TA2

Application Note no. 6: Clarification to Application Selection

Application Note no. 7: Data Element Format Convention Definition Application Note no. 12: Clarification of Coding of Language Preference Application Note no. 14: Considerations when using Higher ‘D’ Values to Increase Data Transfer Rates

Application Note no. 15: Additional Data Allowed in the FCI Returned in Response to a SELECT Command

(6)

Revision Log EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

Application Note no. 20: Data allowed in the Directory Discretionary Template

Updated general sections:

Increased consistency of section 1, Scope, across the four Books.

Merged contents of the following sections, so that they contain complete information for all four Books:

section 2, Normative References section 3, Definitions

section 4, Abbreviations, Notations, Conventions, and Terminology

Minor editorial clarifications, including those described in the following

Specification Updates:

Specification Updates Bulletin no. 5: Update to Reference for ISO 639 Specification Updates Bulletin no. 8: Editorial Changes to EMV 2000 - Version 2.0

(7)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

May 2004 Page v

Contents

Part I - General 1 Scope 31.1 Changes in Version 4.1 31.2 Structure 31.3 Underlying Standards 41.4 Audience 42 Normative References 53 Definitions 9

4 Abbreviations, Notations, Conventions, and Terminology 19

4.1 Abbreviations 19

4.2 Notations 27

4.3 Data Element Format Conventions 29

4.4 Terminology 31

Part II - Electromechanical Characteristics, Logical Interface, and Transmission Protocols

5 Electromechanical Interface 35

5.1 Lower Voltage ICC Migration 36

5.2 Mechanical Characteristics of the ICC 37

5.2.1 Physical Characteristics 37

5.2.2 Dimensions and Location of Contacts 38

5.2.3 Contact Assignment 39

5.3 Electrical Characteristics of the ICC 40

5.3.1 Measurement Conventions 405.3.2 Input/Output (I/O) 405.3.3 Programming Voltage (VPP) 425.3.4 Clock (CLK) 435.3.5 Reset (RST) 445.3.6 Supply Voltage (VCC) 455.3.7 Contact Resistance 46

5.4 Mechanical Characteristics of the Terminal 47

5.4.1 Interface Device 47

5.4.2 Contact Forces 48

(8)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

5.5 Electrical Characteristics of the Terminal 48

5.5.1 Measurement Conventions 485.5.2 Input/Output (I/O) 495.5.3 Programming Voltage (VPP) 515.5.4 Clock (CLK) 525.5.5 Reset (RST) 535.5.6 Supply Voltage (VCC) 545.5.7 Contact Resistance 56

5.5.8 Short Circuit Resilience 56

5.5.9 Powering and Depowering of Terminal with ICC in Place 57

6 Card Session 59

6.1 Normal Card Session 59

6.1.1 Stages of a Card Session 59

6.1.2 ICC Insertion and Contact Activation Sequence 60

6.1.3 ICC Reset 61

6.1.4 Execution of a Transaction 62

6.1.5 Contact Deactivation Sequence 63

6.2 Abnormal Termination of Transaction Process 64

7 Physical Transportation of Characters 65

7.1 Bit Duration 65

7.2 Character Frame 66

8 Answer to Reset 69

8.1 Physical Transportation of Characters Returned at Answer to Reset 698.2 Characters Returned by ICC at Answer to Reset 70

8.3 Character Definitions 72

8.3.1 TS - Initial Character 73

8.3.2 T0 - Format Character 74

8.3.3 TA1 to TC3 - Interface Characters 74

8.3.4 TCK - Check Character 83

8.4 Terminal Behaviour during Answer to Reset 838.5 Answer to Reset - Flow at the Terminal 85

9 Transmission Protocols 87

9.1 Physical Layer 87

9.2 Data Link Layer 88

9.2.1 Character Frame 88

9.2.2 Character Protocol T=0 89

9.2.3 Error Detection and Correction for T=0 93

9.2.4 Block Protocol T=1 94

9.2.5 Error Detection and Correction for T=1 104

(9)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

May 2004 Page vii

9.3.1 Transport of APDUs by T=0 107

9.3.2 Transportation of APDUs by T=1 115

9.4 Application Layer 115

9.4.1 C-APDU 116

9.4.2 R-APDU 117

Part III - Files, Commands, and Application Selection

10 Files 121

10.1 File Structure 121

10.1.1 Application Definition Files 121

10.1.2 Application Elementary Files 122

10.1.3 Mapping of Files Onto ISO/IEC 7816-4 File Structure 122

10.1.4 Directory Structure 12210.2 File Referencing 12310.2.1 Referencing by Name 12310.2.2 Referencing by SFI 12311 Commands 12511.1 Message Structure 125

11.1.1 Command APDU Format 126

11.1.2 Response APDU Format 127

11.2 READ RECORD Command-Response APDUs 127

11.2.1 Definition and Scope 127

11.2.2 Command Message 128

11.2.3 Data Field Sent in the Command Message 12811.2.4 Data Field Returned in the Response Message 12811.2.5 Processing State Returned in the Response Message 128

11.3 SELECT Command-Response APDUs 129

11.3.1 Definition and Scope 129

11.3.2 Command Message 130

11.3.3 Data Field Sent in the Command Message 13011.3.4 Data Field Returned in the Response Message 13111.3.5 Processing State Returned in the Response Message 134

12 Application Selection 135

12.1 Overview of Application Selection 135

12.2 Data in the ICC Used for Application Selection 13612.2.1 Coding of Payment System Application Identifier 136

12.2.2 Structure of the PSE 137

12.2.3 Coding of a Payment System Directory 138

(10)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

12.2.5 Error Handling for FCI Response Data 140

12.3 Building the Candidate List 140

12.3.1 Matching Terminal Applications to ICC Applications 141

12.3.2 Using the PSE 142

12.3.3 Using a List of AIDs 145

12.4 Final Selection 148

Part IV - Annexes

Annex A Examples of Exchanges Using T=0 153

A1 Case 1 Command 153

A2 Case 2 Command 154

A3 Case 3 Command 154

A4 Case 4 Command 155

A5 Case 2 Command Using the '61' and '6C' Procedure Bytes 155A6 Case 4 Command Using the '61' Procedure Byte 156A7 Case 4 Command with Warning Condition 156

Annex B Data Elements Table 157

B1 Data Elements by Name 157

B2 Data Elements by Tag 162

Annex C Examples of Directory Structures 163

C1 Single Application Card 163

C2 Single Level Directory 164

C3 Multi-Level Directory 165

Part V - Common Core Definitions

Common Core Definitions 169

Changed Sections 169

10 Files 170

10.1 File Structure 170

10.1.4 Directory Structure 170

11 Commands 170

11.3 SELECT Command-Response APDUs 170

(11)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

May 2004 Page ix

12 Application Selection 171

12.2 Data in the ICC Used for Application Selection 171

12.2.2 Structure of the PSE 171

12.2.3 Coding of a Payment System Directory 171

(12)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

(13)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

May 2004 Page xi

Tables

Table 1: Lower Voltage Card Migration 36

Table 2: ICC Contact Assignment 39

Table 3: Electrical Characteristics of I/O for ICC Reception 41Table 4: Electrical Characteristics of I/O for ICC Transmission 42Table 5: Electrical Characteristics of CLK to ICC 43Table 6: Electrical Characteristics of RST to ICC 44

Table 7: Classes of Operation 45

Table 8: Mandatory and Optional Operating Voltage Ranges 46

Table 9: IFD Contact Assignment 48

Table 10: Electrical Characteristics of I/O for Terminal Transmission 50Table 11: Electrical Characteristics of I/O for Terminal Reception 51Table 12: Electrical Characteristics of CLK from Terminal 52Table 13: Electrical Characteristics of RST from Terminal 53Table 14: Terminal Supply Voltage and Current 55

Table 15: Basic ATR for T=0 Only 70

Table 16: Basic ATR for T=1 Only 71

Table 17: Terminal Behaviour 73

Table 18: Basic Response Coding of Character T0 74Table 19: Basic Response Coding of Character TB1 76Table 20: Basic Response Coding of Character TC1 77Table 21: Basic Response Coding of Character TD1 78Table 22: Basic Response Coding of Character TD2 80Table 23: Basic Response Coding of Character TA3 81Table 24: Basic Response Coding of Character TB3 82Table 25: Terminal Response to Procedure Byte 91

Table 26: Status Byte Coding 92

Table 27: Structure of a Block 94

Table 28: Types of Blocks 95

Table 29: Coding of the PCB of an I-block 96

Table 30: Coding of the PCB of a R-block 96

Table 31: Coding of the PCB of a S-block 96

Table 32: Structure of Command Message 114

Table 33: GET RESPONSE Error Conditions 114

Table 34: Definition of Cases for Data in APDUs 115

Table 35: C-APDU Structures 116

Table 36: Command APDU Content 126

Table 37: Response APDU Content 127

Table 38: READ RECORD Command Message 128

Table 39: READ RECORD Command Reference Control Parameter 128

Table 40: SELECT Command Message 130

Table 41: SELECT Command Reference Control Parameter 130Table 42: SELECT Command Options Parameter 130Table 43: SELECT Response Message Data Field (FCI) of the PSE 131Table 44: SELECT Response Message Data Field (FCI) of a DDF 132

(14)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

Table 45: SELECT Response Message Data Field (FCI) of an ADF 133Table 46: Payment System Directory Record Format 138

Table 47: DDF Directory Entry Format 138

Table 48: ADF Directory Entry Format 139

Table 49: Format of Application Priority Indicator 139

Table 50: Data Elements Table 157

(15)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

May 2004 Page xiii

Figures

Figure 1: ICC Contact Location and Dimensions 38

Figure 2: Layout of Contacts 39

Figure 3: Terminal Contact Location and Dimensions 47

Figure 4: Maximum Current Pulse Envelope 54

Figure 5: Maximum Current Pulse Envelopes 56

Figure 6: Contact Activation Sequence 60

Figure 7: Cold Reset Sequence 61

Figure 8: Warm Reset Sequence 62

Figure 9: Contact Deactivation Sequence 63

Figure 10: Character Frame 66

Figure 11: ATR - Example Flow at the Terminal 85

Figure 12: Character Repetition Timing 93

Figure 13: Chaining C-APDU 103

Figure 14: Chaining I-Blocks 103

Figure 15: Command APDU Structure 126

Figure 16: Response APDU Structure 127

Figure 17: Terminal Logic Using Directories 144Figure 18: Using the List of AIDs in the Terminal 147Figure 19: Simplest Card Structure Single Application 163

Figure 20: Single Level Directory 164

(16)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

(17)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

May 2004 Page 1

Part I

General

(18)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

(19)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

May 2004 Page 3

1 Scope

This document, the Integrated Circuit Card (ICC) Specifications for Payment Systems - Book 1, Application Independent ICC to Terminal Interface

Requirements, describes the minimum functionality required of integrated circuit cards (ICCs) and terminals to ensure correct operation and

interoperability independent of the application to be used. Additional proprietary functionality and features may be provided, but these are beyond the scope of this specification and interoperability cannot be guaranteed.

The Integrated Circuit Card Specifications for Payment Systems includes the following additional documents, all available on http://www.emvco.com: • Book 2 - Security and Key Management

• Book 3 - Application Specification

• Book 4 - Cardholder, Attendant, and Acquirer Interface Requirements

1.1 Changes in Version 4.1

This release incorporates all relevant Specification Update Bulletins, Application Notes, amendments, etc. published up to the date of this release.

The Revision Log at the beginning of the Book provides additional detail about changes to this Book.

1.2 Structure

Book 1 consists of the following parts: Part I - General

Part II - Electromechanical Characteristics, Logical Interface,

and Transmission Protocols

Part III - Files, Commands, and Application Selection Part IV - Annexes

Part V - Common Core Definitions

Part I includes this introduction, as well as data applicable to all Books:

normative references, definitions, abbreviations, notations, data element format convention, and terminology.

(20)

1 Scope EMV 4.1 Book 1 1.3 Underlying Standards Application Independent ICC to Terminal Interface Requirements

Part II defines electromechanical characteristics, logical interface, and

transmission protocols as they apply to the exchange of information between an ICC and a terminal. In particular it covers:

• Mechanical characteristics, voltage levels, and signal parameters as they apply to both ICCs and terminals.

• An overview of the card session.

• Establishment of communication between the ICC and the terminal by means of the answer to reset.

• Character- and block-oriented asynchronous transmission protocols. Part III defines data elements, files, and commands as they apply to the

exchange of information between an ICC and a terminal. In particular it covers: • Data elements and their mapping onto data objects.

• Structure and referencing of files.

• Structure and coding of messages between the ICC and the terminal to achieve application selection.

Part III also defines the application selection process from the standpoint of both the card and the terminal. The logical structure of data and files within the card that is required for the process is specified, as is the terminal logic using the card structure.

Part IV includes examples of exchanges using T=0, a data elements table specific to application selection, and example directory structures.

Part V defines an optional extension to be used when implementing the Common Core Definitions (CCD).

The Book also includes a revision log and an index.

1.3 Underlying

Standards

This specification is based on the ISO/IEC 7816 series of standards and should be read in conjunction with those standards. However, if any of the provisions or definitions in this specification differ from those standards, the provisions herein shall take precedence.

1.4 Audience

This specification is intended for use by manufacturers of ICCs and terminals, system designers in payment systems, and financial institution staff responsible for implementing financial applications in ICCs.

(21)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

May 2004 Page 5

2 Normative

References

The following standards contain provisions that are referenced in these specifications. The latest version shall apply unless a publication date is explicitly stated.

FIPS 180-2 Secure Hash Standard

ISO 639-1 Codes for the representation of names of languages – Part 1: Alpha-2 Code

Note: This standard is updated continuously by ISO. Additions/changes to ISO 639-1:1988: Codes for the Representation of Names of Languages are available on:

http://lcweb.loc.gov/standards/iso639-2/codechanges.html

ISO 3166 Codes for the representation of names of countries and their subdivisions

ISO 4217 Codes for the representation of currencies and funds

ISO/IEC 7811-1 Identification cards – Recording technique – Part 1: Embossing

ISO/IEC 7811-3 Identification cards – Recording technique – Part 3: Location of embossed characters on ID-1 cards

ISO/IEC 7813 Identification cards – Financial transaction cards ISO/IEC 7816-1 Identification cards – Integrated circuit(s) cards

with contacts – Part 1: Physical characteristics ISO/IEC 7816-2 Information technology – Identification cards –

Integrated circuit(s) cards with contacts – Part 2: Dimensions and location of contacts

ISO/IEC 7816-3 Information technology – Identification Cards – Integrated circuit(s) cards with contacts – Part 3: Electronic signals and transmission protocols

(22)

2 Normative References EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

ISO/IEC 7816-4 Information technology – Identification cards – Integrated circuit(s) cards with contacts – Part 4: Interindustry commands for interchange

ISO/IEC 7816-5 Identification cards – Integrated circuit(s) cards with contacts – Part 5: Numbering system and registration procedure for application identifiers ISO/IEC 7816-6 Identification cards – Integrated circuit(s) cards

with contacts – Part 6: Interindustry data elements

ISO 8583:1987 Bank card originated messages – Interchange message specifications – Content for financial transactions

ISO 8583:1993 Financial transaction card originated messages – Interchange message specifications

ISO/IEC 8825-1 Information technology – ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and

Distinguished Encoding Rules (DER)

ISO/IEC 8859 Information processing – 8-bit single-byte coded graphic character sets

ISO 9362 Banking – Banking telecommunication messages – Bank identifier codes

ISO 9564-1 Banking – PIN management and security – Part 1: Basic principles and requirements for online PIN handling in ATM and POS systems ISO 9564-3 Banking – PIN management and security –

Part 3: Requirements for offline PIN handling in ATM and POS systems

ISO/IEC 9796-2:2002 Information technology – Security techniques – Digital signature schemes giving message recovery – Part 2: Integer factorization based mechanisms

ISO/IEC 9797-1 Information technology – Security techniques – Message Authentication Codes – Part 1:

(23)

EMV 4.1 Book 1 2 Normative References Application Independent ICC to

Terminal Interface Requirements

May 2004 Page 7

ISO/IEC 10116 Information technology – Security techniques – Modes of operation for an n-bit block cipher ISO/IEC 10118-3 Information technology – Security techniques –

Hash-functions – Part 3: Dedicated hash-functions ISO/IEC 10373 Identification cards – Test methods

ISO 11568-2:1994 Banking – Key management (retail) – Part 2: Key management techniques for symmetric ciphers ISO 13491-1 Banking – Secure cryptographic devices (retail) –

Part 1: Concepts, requirements and evaluation methods

ISO 13616 Banking and related financial services – International bank account number (IBAN) ISO 16609 Banking – Requirements for message

(24)

2 Normative References EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

(25)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

May 2004 Page 9

3 Definitions

The following terms are used in one or more books of these specifications.

Accelerated

Revocation A key revocation performed on a date sooner than the published key expiry date.

Application The application protocol between the card and the terminal and its related set of data.

Application Authentication Cryptogram

An Application Cryptogram generated when declining a transaction

Application Authorisation Referral

An Application Cryptogram generated when requesting an authorisation referral

Application

Cryptogram A cryptogram generated by the card in response to a GENERATE AC command. See also: • Application Authentication Cryptogram

• Application Authorisation Referral • Authorisation Request Cryptogram • Transaction Certificate

Authorisation

Request Cryptogram An Application Cryptogram generated when requesting online authorisation

Authorisation Response Cryptogram

A cryptogram generated by the issuer in response to an Authorisation Request Cryptogram.

Asymmetric Cryptographic Technique

A cryptographic technique that uses two related transformations, a public transformation (defined by the public key) and a private transformation (defined by the private key). The two transformations have the property that, given the public transformation, it is computationally infeasible to derive the private transformation.

Authentication The provision of assurance of the claimed identity of an entity or of data origin.

(26)

3 Definitions EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

Block A succession of characters comprising two or three fields defined as prologue field, information field, and epilogue field.

Byte 8 bits.

Card A payment card as defined by a payment system.

Certificate The public key and identity of an entity together with some other information, rendered unforgeable by signing with the private key of the certification authority which issued that certificate.

Certification

Authority Trusted third party that establishes a proof that links a public key and other relevant information to its owner.

Ciphertext Enciphered information.

Cold Reset The reset of the ICC that occurs when the supply voltage (VCC) and other signals to the ICC are raised from the inactive state and the reset (RST) signal is applied.

Combined

DDA/Application Cryptogram Generation

A form of offline dynamic data authentication.

Command A message sent by the terminal to the ICC that initiates an action and solicits a response from the ICC.

Compromise The breaching of secrecy or security.

Concatenation Two elements are concatenated by appending the bytes from the second element to the end of the first. Bytes from each element are represented in the resulting string in the same sequence in which they were presented to the terminal by the ICC, that is, most significant byte first. Within each byte bits are ordered from most significant bit to least significant. A list of elements or objects may be concatenated by concatenating the first pair to form a new element, using that as the first element to concatenate with the next in the list, and so on.

(27)

EMV 4.1 Book 1 3 Definitions Application Independent ICC to

Terminal Interface Requirements

May 2004 Page 11

Contact A conducting element ensuring galvanic continuity between integrated circuit(s) and external interfacing equipment.

Cryptogram Result of a cryptographic operation.

Cryptographic

Algorithm An algorithm that transforms data in order to hide or reveal its information content.

Data Integrity The property that data has not been altered or destroyed in an unauthorised manner.

Deactivation

Sequence The deactivation sequence defined in section 6.1.5. Decipherment The reversal of a corresponding encipherment.

Digital Signature An asymmetric cryptographic transformation of data that allows the recipient of the data to prove the origin and integrity of the data, and protect the sender and the recipient of the data against forgery by third parties, and the sender against forgery by the recipient.

Dynamic Data Authentication

A form of offline dynamic data authentication

Embossing Characters raised in relief from the front surface of a card.

Encipherment The reversible transformation of data by a cryptographic algorithm to produce ciphertext.

Epilogue Field The final field of a block. It contains the error detection code (EDC) byte(s).

Exclusive-OR Binary addition with no carry, giving the following values: 0 + 0 = 0 0 + 1 = 1 1 + 0 = 1 1 + 1 = 0 Financial

Transaction The act between a cardholder and a merchant or acquirer that results in the exchange of goods or services against payment.

(28)

3 Definitions EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

Function A process accomplished by one or more commands and resultant actions that are used to perform all or part of a transaction.

Guardtime The minimum time between the trailing edge of the parity bit of a character and the leading edge of the start bit of the following character sent in the same direction.

Hash Function A function that maps strings of bits to fixed–length strings of bits, satisfying the following two properties: • It is computationally infeasible to find for a given

output an input which maps to this output. • It is computationally infeasible to find for a given

input a second input that maps to the same output.

Additionally, if the hash function is required to be collision–resistant, it must also satisfy the following property:

• It is computationally infeasible to find any two distinct inputs that map to the same output.

Hash Result The string of bits that is the output of a hash function.

Inactive The supply voltage (VCC) and other signals to the ICC are in the inactive state when they are at a potential of 0.4 V or less with respect to ground (GND).

Integrated Circuit

Module The sub-assembly embedded into the ICC comprising the IC, the IC carrier, bonding wires, and contacts.

Integrated Circuit(s) Electronic component(s) designed to perform

processing and/or memory functions.

Integrated Circuit(s)

Card A card into which one or more integrated circuits are inserted to perform processing and memory functions.

Interface Device That part of a terminal into which the ICC is inserted, including such mechanical and electrical devices as may be considered part of it.

(29)

EMV 4.1 Book 1 3 Definitions Application Independent ICC to

Terminal Interface Requirements

May 2004 Page 13

Issuer Action Code Any of the following, which reflect the issuer-selected action to be taken upon analysis of the TVR:

• Issuer Action Code - Default • Issuer Action Code - Denial • Issuer Action Code - Online

Kernel The set of functions required to be present on every terminal implementing a specific interpreter. The kernel contains device drivers, interface routines, security and control functions, and the software for translating from the virtual machine language to the language used by the real machine. In other words, the kernel is the implementation of the virtual machine on a specific real machine.

Key A sequence of symbols that controls the operation of a cryptographic transformation.

Key Expiry Date The date after which a signature made with a particular key is no longer valid. Issuer certificates signed by the key must expire on or before this date. Keys may be removed from terminals after this date has passed.

Key Introduction The process of generating, distributing, and beginning use of a key pair.

Key Life Cycle All phases of key management, from planning and generation, through revocation, destruction, and archiving.

Key Replacement The simultaneous revocation of a key and

introduction of a key to replaced the revoked one.

Key Revocation The key management process of withdrawing a key from service and dealing with the legacy of its use. Key revocation can be as scheduled or accelerated.

Key Revocation Date The date after which no legitimate cards still in use

should contain certificates signed by this key, and therefore the date after which this key can be deleted from terminals. For a planned revocation the Key Revocation Date is the same as the key expiry date.

Key Withdrawal The process of removing a key from service as part of its revocation.

(30)

3 Definitions EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

Keypad Arrangement of numeric, command, and, where required, function and/or alphanumeric keys laid out in a specific manner.

Library A set of high-level software functions with a published interface, providing general support for terminal programs and/or applications.

Logical Compromise The compromise of a key through application of improved cryptanalytic techniques, increases in computing power, or combination of the two.

Magnetic Stripe The stripe containing magnetically encoded information.

Message A string of bytes sent by the terminal to the card or vice versa, excluding transmission-control characters.

Message

Authentication Code A symmetric cryptographic transformation of data that protects the sender and the recipient of the data against forgery by third parties.

Nibble The four most significant or least significant bits of a byte.

Padding Appending extra bits to either side of a data string.

Path Concatenation of file identifiers without delimitation.

Payment System

Environment The set of logical conditions established within the ICC when a payment system application conforming to this specification has been selected, or when a Directory Definition File (DDF) used for payment system application purposes has been selected.

Physical Compromise The compromise of a key resulting from the fact that

it has not been securely guarded, or a hardware security module has been stolen or accessed by unauthorised persons.

PIN Pad Arrangement of numeric and command keys to be used for personal identification number (PIN) entry.

Plaintext Unenciphered information.

Planned Revocation A key revocation performed as scheduled by the published key expiry date.

(31)

EMV 4.1 Book 1 3 Definitions Application Independent ICC to

Terminal Interface Requirements

May 2004 Page 15

Potential

Compromise A condition where cryptanalytic techniques and/or computing power has advanced to the point that compromise of a key of a certain length is feasible or even likely.

Private Key That key of an entity’s asymmetric key pair that should only be used by that entity. In the case of a digital signature scheme, the private key defines the signature function.

Prologue Field The first field of a block. It contains subfields for node address (NAD), protocol control byte (PCB), and length (LEN).

Public Key That key of an entity’s asymmetric key pair that can be made public. In the case of a digital signature scheme, the public key defines the verification function.

Public Key

Certificate The public key information of an entity signed by the certification authority and thereby rendered unforgeable.

Response A message returned by the ICC to the terminal after the processing of a command message received by the ICC.

Script A command or a string of commands transmitted by the issuer to the terminal for the purpose of being sent serially to the ICC as commands.

Secret Key A key used with symmetric cryptographic techniques and usable only by a set of specified entities.

Signal Amplitude The difference between the high and low voltages of a signal.

Signal Perturbations Abnormalities occurring on a signal during normal

operation such as undershoot/overshoot, electrical noise, ripple, spikes, crosstalk, etc. Random

perturbations introduced from external sources are beyond the scope of this specification.

Socket An execution vector defined at a particular point in an application and assigned a unique number for reference.

(32)

3 Definitions EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

State H Voltage high on a signal line. May indicate a logic one or logic zero depending on the logic convention used with the ICC.

State L Voltage low on a signal line. May indicate a logic one or logic zero depending on the logic convention used with the ICC.

Static Data

Authentication Offline static data authentication Symmetric

Cryptographic Technique

A cryptographic technique that uses the same secret key for both the originator’s and recipient’s

transformation. Without knowledge of the secret key, it is computationally infeasible to compute either the originator’s or the recipient’s transformation.

T=0 Character-oriented asynchronous half duplex transmission protocol.

T=1 Block-oriented asynchronous half duplex transmission protocol.

Template Value field of a constructed data object, defined to give a logical grouping of data objects.

Terminal The device used in conjunction with the ICC at the point of transaction to perform a financial

transaction. The terminal incorporates the interface device and may also include other components and interfaces such as host communications.

Terminal Action

Code Any of the following, which reflect the acquirer-selected action to be taken upon analysis of the TVR:

• Terminal Action Code - Default • Terminal Action Code - Denial • Terminal Action Code - Online

Terminate Card Session

End the card session by deactivating the IFD contacts according to section 6.1.5, and displaying a message indicating that the ICC cannot be used to complete the transaction

Terminate

(33)

EMV 4.1 Book 1 3 Definitions Application Independent ICC to

Terminal Interface Requirements

May 2004 Page 17

Transaction An action taken by a terminal at the user’s request. For a POS terminal, a transaction might be payment for goods, etc. A transaction selects among one or more applications as part of its processing flow.

Transaction

Certificate An Application Cryptogram generated when accepting a transaction

Virtual Machine A theoretical microprocessor architecture that forms the basis for writing application programs in a specific interpreter software implementation.

Warm Reset The reset that occurs when the reset (RST) signal is applied to the ICC while the clock (CLK) and supply voltage (VCC) lines are maintained in their active state.

(34)

3 Definitions EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

(35)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

May 2004 Page 19

4

Abbreviations, Notations, Conventions, and

Terminology

4.1 Abbreviations

µA Microampere

µm Micrometre

µs Microsecond

a Alphabetic (see section 4.3, Data Element Format Conventions) AAC Application Authentication Cryptogram

AAR Application Authorisation Referral

AC Application Cryptogram

ACK Acknowledgment

ADF Application Definition File AEF Application Elementary File AFL Application File Locator

AID Application Identifier AIP Application Interchange Profile an Alphanumeric (see section 4.3)

ans Alphanumeric Special (see section 4.3) APDU Application Protocol Data Unit

API Application Program Interface ARC Authorisation Response Code

ARPC Authorisation Response Cryptogram ARQC Authorisation Request Cryptogram ASI Application Selection Indicator ASN Abstract Syntax Notation

(36)

4 Abbreviations, Notations, Conventions, and Terminology EMV 4.1 Book 1 4.1 Abbreviations Application Independent ICC to Terminal Interface Requirements

ATC Application Transaction Counter ATM Automated Teller Machine ATR Answer to Reset

AUC Application Usage Control b Binary (see section 4.3) BCD Binary Coded Decimal

BER Basic Encoding Rules (defined in ISO/IEC 8825–1) BIC Bank Identifier Code

BGT Block Guardtime

BWI Block Waiting Time Integer BWT Block Waiting Time

C Celsius or Centigrade CAD Card Accepting Device C-APDU Command APDU CBC Cipher Block Chaining CCD Common Core Definitions CCI Common Core Identifier

CDA Combined DDA/Application Cryptogram Generation CDOL Card Risk Management Data Object List

CID Cryptogram Information Data CIN Input Capacitance

CLA Class Byte of the Command Message

CLK Clock

cn Compressed Numeric (see section 4.3) CPU Central Processing Unit

CSU Card Status Update C-TPDU Command TPDU

(37)

EMV 4.1 Book 1 4 Abbreviations, Notations, Conventions, and Terminology

Application Independent ICC to 4.1 Abbreviations

Terminal Interface Requirements

May 2004 Page 21

CV Cryptogram Version

CVM Cardholder Verification Method CVR Card Verification Results CV Rule Cardholder Verification Rule CWI Character Waiting Time Integer CWT Character Waiting Time

D Bit Rate Adjustment Factor DAD Destination Node Address

DC Direct Current

DDA Dynamic Data Authentication DDF Directory Definition File

DDOL Dynamic Data Authentication Data Object List DES Data Encryption Standard

DF Dedicated File

DIR Directory

DOL Data Object List ECB Electronic Code Book EDC Error Detection Code

EF Elementary File

EN European Norm

etu Elementary Time Unit

f Frequency

FC Format Code

FCI File Control Information

FIPS Federal Information Processing Standard

GND Ground

(38)

4 Abbreviations, Notations, Conventions, and Terminology EMV 4.1 Book 1 4.1 Abbreviations Application Independent ICC to Terminal Interface Requirements

Hex Hexadecimal

HHMMSS Hours, Minutes, Seconds

I/O Input/Output

IAC Issuer Action Code (Denial, Default, Online) IAD Issuer Application Data

IBAN International Bank Account Number I-block Information Block

IC Integrated Circuit

ICC Integrated Circuit(s) Card ICC Current drawn from VCC

IEC International Electrotechnical Commission

IFD Interface Device

IFS Information Field Size

IFSC Information Field Size for the ICC IFSD Information Field Size for the Terminal IFSI Information Field Size Integer

IIN Issuer Identification Number

IK Intermediate Key for session key generation INF Information Field

INS Instruction Byte of Command Message IOH High Level Output Current

IOL Low Level Output Current

ISO International Organization for Standardization IV Initial Vector for session key generation

KM Master Key

KS Session Key

(39)

EMV 4.1 Book 1 4 Abbreviations, Notations, Conventions, and Terminology

Application Independent ICC to 4.1 Abbreviations

Terminal Interface Requirements

May 2004 Page 23

l.s. Least Significant

Lc Exact Length of Data Sent by the TAL in a Case 3 or 4 Command

LCOL Lower Consecutive Offline Limit LDD Length of the ICC Dynamic Data

Le Maximum Length of Data Expected by the TAL in Response to a Case 2 or 4 Command

LEN Length

Licc Exact Length of Data Available or Remaining in the ICC (as Determined by the ICC) to be Returned in Response to the Case 2 or 4 Command Received by the ICC

Lr Length of Response Data Field LRC Longitudinal Redundancy Check

M Mandatory

mΩ Milliohm

MΩ Megohm

m.s. Most Significant m/s Meters per Second

mA Milliampere

MAC Message Authentication Code

max. Maximum

MF Master File

MHz Megahertz

min. Minimum

MK ICC Master Key for session key generation

mm Millimetre

MMDD Month, Day

MMYY Month, Year

(40)

4 Abbreviations, Notations, Conventions, and Terminology EMV 4.1 Book 1 4.1 Abbreviations Application Independent ICC to Terminal Interface Requirements

n Numeric (see section 4.3)

NAD Node Address

NAK Negative Acknowledgment

nAs Nanoampere-second

NCA Length of the Certification Authority Public Key Modulus

NF Norme Française

NI Length of the Issuer Public Key Modulus NIC Length of the ICC Public Key Modulus

NPE Length of the ICC PIN Encipherment Public Key Modulus

ns Nanosecond

O Optional

O/S Operating System

P Parent key for session key generation

P1 Parameter 1

P2 Parameter 2

P3 Parameter 3

PAN Primary Account Number

PC Personal Computer

PCA Certification Authority Public Key PCB Protocol Control Byte

PDOL Processing Options Data Object List

pF Picofarad

PI Issuer Public Key PIC ICC Public Key

PIN Personal Identification Number

PIX Proprietary Application Identifier Extension POS Point of Service

(41)

EMV 4.1 Book 1 4 Abbreviations, Notations, Conventions, and Terminology

Application Independent ICC to 4.1 Abbreviations

Terminal Interface Requirements

May 2004 Page 25

pos. Position

PSE Payment System Environment PTS Protocol Type Selection

R-APDU Response APDU R-block Receive Ready Block RFU Reserved for Future Use

RID Registered Application Provider Identifier RSA Rivest, Shamir, Adleman Algorithm

RST Reset

SAD Source Node Address S-block Supervisory Block

SCA Certification Authority Private Key SDA Static Data Authentication

SFI Short File Identifier SHA-1 Secure Hash Algorithm 1 SI Issuer Private Key

SIC ICC Private Key

SK Session Key for session key generation SW1 Status Byte One

SW2 Status Byte Two

TAC Terminal Action Code(s) (Default, Denial, Online) TAL Terminal Application Layer

TC Transaction Certificate

TCK Check Character

TDOL Transaction Certificate Data Object List

tF Fall Time Between 90% and 10% of Signal Amplitude TLV Tag Length Value

(42)

4 Abbreviations, Notations, Conventions, and Terminology EMV 4.1 Book 1 4.1 Abbreviations Application Independent ICC to Terminal Interface Requirements

TPDU Transport Protocol Data Unit

tR Rise Time Between 10% and 90% of Signal Amplitude

TS Initial Character

TSI Transaction Status Information TTL Terminal Transport Layer TVR Terminal Verification Results UCOL Upper Consecutive Offline Limit

UL Underwriters Laboratories Incorporated

V Volt

var. Variable (see section 4.3)

VCC Voltage Measured on VCC Contact

VCC Supply Voltage

VIH High Level Input Voltage VIL Low Level Input Voltage VOH High Level Output Voltage VOL Low Level Output Voltage

VPP Programming Voltage

VPP Voltage Measured on VPP contact WI Waiting Time Integer

WTX Waiting Time Extension WWT Work Waiting Time

YYMM Year, Month

(43)

EMV 4.1 Book 1 4 Abbreviations, Notations, Conventions, and Terminology

Application Independent ICC to 4.2 Notations

Terminal Interface Requirements

May 2004 Page 27

4.2 Notations

‘0’ to ‘9' and 'A' to 'F' 16 hexadecimal characters

xx Any value

A := B A is assigned the value of B

A = B Value of A is equal to the value of B

A ≡ B mod n Integers A and B are congruent modulo the integer n, that is, there exists an integer d such that

(A – B) = dn

A mod n The reduction of the integer A modulo the integer n, that is, the unique integer r, 0 ≤ r < n, for which there exists an integer d such that

A = dn + r

A / n The integer division of A by n, that is, the unique integer d for which there exists an integer r, 0 ≤ r < n, such that

A = dn + r b-ary representation

(x0, x1, . . . , xn–1) of

X

For a positive integer b, the representation of a nonnegative integer X in the base b:

X = x0bn–1 + x1bn–2+ . . . + xn–2b + xn–1

for the unique integers x0, x1, …, x(n–1) and n satisfying

n > 0 and 0 ≤ xi < b for i=0 to n–1

Y := ALG(K)[X] Encipherment of a data block X with a block cipher as specified in Annex A1 of Book 2, using a secret key K X = ALG-1(K)[Y] Decipherment of a data block Y with a block cipher as

specified in Annex A1 of Book 2, using a secret key K Y := Sign (SK)[X] The signing of a data block X with an asymmetric

reversible algorithm as specified in Annex A2 of Book 2, using the private key SK

(44)

4 Abbreviations, Notations, Conventions, and Terminology EMV 4.1 Book 1 4.2 Notations Application Independent ICC to Terminal Interface Requirements

X = Recover(PK)[Y] The recovery of the data block X with an asymmetric reversible algorithm as specified in Annex A2 of Book 2, using the public key PK

C := (A || B) The concatenation of an n-bit number A and an m-bit number B, which is defined as C = 2m A + B.

Leftmost Applies to a sequence of bits, bytes, or digits and used interchangeably with the term “most significant”. If C = (A || B) as above, then A is the leftmost n bits of C. Rightmost Applies to a sequence of bits, bytes, or digits and used

interchangeably with the term “least significant”. If C = (A || B) as above, then B is the rightmost m bits of C.

H := Hash[MSG] Hashing of a message MSG of arbitrary length using a 160-bit hash function

X ⊕ Y The symbol '⊕' denotes bit-wise exclusive-OR and is defined as follows:

X ⊕ Y The bit-wise exclusive-OR of the data blocks X and Y. If one data block is shorter than the other, then it is first padded to the left with sufficient binary zeros to make it the same length as the other.

(45)

EMV 4.1 Book 1 4 Abbreviations, Notations, Conventions, and Terminology

Application Independent ICC to 4.3 Data Element Format Conventions

Terminal Interface Requirements

May 2004 Page 29

4.3 Data Element Format Conventions

The EMV specifications use the following data element formats:

a Alphabetic data elements contain a single character per byte. The permitted characters are alphabetic only (a to z and A to Z, upper and lower case).

an Alphanumeric data elements contain a single character per byte. The permitted characters are alphabetic (a to z and A to Z, upper and lower case) and numeric (0 to 9).

ans Alphanumeric Special data elements contain a single character per byte. The permitted characters and their coding are shown in the Common Character Set table in Annex B of Book 4.

There is one exception: The permitted characters for Application Preferred Name are the non-control characters defined in the ISO/IEC 8859 part designated in the Issuer Code Table Index associated with the Application Preferred Name.

b These data elements consist of either unsigned binary numbers or bit combinations that are defined elsewhere in the specification.

Binary example: The Application Transaction Counter (ATC) is defined as “b” with a length of two bytes. An ATC value of 19 is stored as Hex '00 13'.

Bit combination example: Processing Options Data Object List (PDOL) is defined as “b” with the format shown in Book 3, section 5.4.

cn Compressed numeric data elements consist of two numeric digits (having values in the range Hex '0'–'9') per byte. These data elements are left justified and padded with trailing hexadecimal 'F's.

Example: The Application Primary Account Number (PAN) is defined as “cn” with a length of up to ten bytes. A value of 1234567890123 may be stored in the Application PAN as Hex '12 34 56 78 90 12 3F FF' with a length of 8.

n Numeric data elements consist of two numeric digits (having values in the range Hex '0'–'9') per byte. These digits are right justified and padded with leading hexadecimal zeroes. Other specifications

sometimes refer to this data format as Binary Coded Decimal (“BCD”) or unsigned packed.

Example: Amount, Authorised (Numeric) is defined as “n 12” with a length of six bytes. A value of 12345 is stored in Amount, Authorised (Numeric) as Hex '00 00 00 01 23 45'.

(46)

4 Abbreviations, Notations, Conventions, and Terminology EMV 4.1 Book 1 4.3 Data Element Format Conventions Application Independent ICC to Terminal Interface Requirements

var. Variable data elements are variable length and may contain any bit combination. Additional information on the formats of specific variable data elements is available elsewhere.

(47)

EMV 4.1 Book 1 4 Abbreviations, Notations, Conventions, and Terminology

Application Independent ICC to 4.4 Terminology

Terminal Interface Requirements

May 2004 Page 31

4.4 Terminology

proprietary Not defined in this specification and/or outside the scope of this specification

shall Denotes a mandatory requirement should Denotes a recommendation

(48)

4 Abbreviations, Notations, Conventions, and Terminology EMV 4.1 Book 1 4.4 Terminology Application Independent ICC to Terminal Interface Requirements

(49)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

May 2004 Page 33

Part II

Electromechanical Characteristics,

Logical Interface, and Transmission

(50)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

(51)

EMV 4.1 Book 1

Application Independent ICC to Terminal Interface Requirements

May 2004 Page 35

5 Electromechanical

Interface

This section covers the electrical and mechanical characteristics of the ICC and the terminal. ICC and terminal specifications differ to allow a safety margin to prevent damage to the ICC.

The ICC characteristics defined herein are based on the ISO/IEC 7816 series of standards with some small variations.

(52)

5 Electromechanical Interface EMV 4.1 Book 1 5.1 Lower Voltage ICC Migration Application Independent ICC to Terminal Interface Requirements

5.1 Lower Voltage ICC Migration

A phased migration to lower voltage cards is underway. Cards that support class A only are being phased out and shall be replaced by class AB or class ABC cards by end June 2009. When all cards in use support class AB or class ABC, it will be possible to deploy terminals that support class B only in addition to class A only terminals. Refer to General Bulletin 11 on the EMVCo website at http://www.emvco.com for details of the migration schedule.

Section 5 describes the requirements for cards and terminals as the transition occurs. Differences are indicated using the notations shown in Table 1:

Notation Information applies: Values:

class A cards until end June 2009

to class A cards are permitted for cards in circulation until end June 2009. From July 2009, all cards in circulation shall be either class AB or class ABC.

new card values from July 2009

to the following cards:1

• class A (until end June 2009) • class AB • class ABC

are permitted immediately and until further notice. No class A cards shall be in circulation from July 2009; only class AB or class ABC cards shall be in circulation from July 2009.

class A terminals until end June 2009

to class A terminals (or the class A component of

multi-class terminals)

shall be used for class A terminals until end June 2009. From July 2009, there is no requirement to update terminals already in the field built using these values.

new terminal values from July 2009

to class A, class B, and

class C terminals shall not be used before end June 2009. From July 2009, shall be used for new class A or class B terminals. Class C terminals shall not be deployed until stated by EMVCo (except for proprietary purposes outside the scope of EMV).

Table 1: Lower Voltage Card Migration

(53)

EMV 4.1 Book 1 5 Electromechanical Interface

Application Independent ICC to 5.2 Mechanical Characteristics of the ICC

Terminal Interface Requirements

May 2004 Page 37

5.2 Mechanical Characteristics of the ICC

This section describes the physical characteristics, contact assignment, and mechanical strength of the ICC.

5.2.1 Physical Characteristics

Except as otherwise specified herein, the ICC shall comply with the physical characteristics for ICCs as defined in ISO/IEC 7816-1. The ICC shall also comply with the additional characteristics defined in ISO/IEC 7816-1 as related to ultraviolet light, X-rays, surface profile of the contacts, mechanical strength, electromagnetic characteristics, and static electricity and shall continue to function correctly electrically under the conditions defined therein.

5.2.1.1 Module

Height

The highest point on the IC module surface shall not be greater than 0.10mm above the plane of the card surface.

The lowest point on the IC module surface shall not be greater than 0.10mm below the plane of the card surface.

(54)

5 Electromechanical Interface EMV 4.1 Book 1 5.2 Mechanical Characteristics of the ICC Application Independent ICC to Terminal Interface Requirements

5.2.2 Dimensions and Location of Contacts

The dimensions and location of the contacts shall be as shown in Figure 1:

10.25 max12.25 min17.87 max19.87 min19.23 max20.93 min21.77 max23.47 min24.31 max26.01 min26.85 max28.55 minC1 C5C2 C6C3 C7C4 C8All dimensionsin millimetresUpper EdgeLeft Edge

Figure 1: ICC Contact Location and Dimensions

Areas C1, C2, C3, C5, and C7 shall be fully covered by conductive surfaces forming the minimum ICC contacts. Areas C4, C6, C8, and areas Z1 to Z8 as defined in ISO/IEC 7816-2 Annex B may optionally have conductive surfaces, but it is strongly recommended that no conductive surfaces exist in areas Z1 to Z8. If conductive surfaces exist in areas C6, and Z1 to Z8, they shall be electrically isolated from the integrated circuit (IC), from one another, and from any other contact area. (Electrically isolated means that the resistance measured between the conductive surface and any other conductive surface shall be ≥10MΩ with an applied voltage of 5V DC.) In addition, there shall be no connection between the conductive surface of any area and the conductive surface of any other area, other than via the IC. The minimum ICC contacts shall be connected to the IC contacts as shown in Table 2.

(55)

EMV 4.1 Book 1 5 Electromechanical Interface

Application Independent ICC to 5.2 Mechanical Characteristics of the ICC

Terminal Interface Requirements

May 2004 Page 39

The layout of the contacts relative to embossing and/or magnetic stripe shall be as shown in Figure 2:

Front of Card

MagneticStripe(Back of Card)EmbossingAreaMandatoryContactsOptionalContacts

Figure 2: Layout of Contacts

Note: Care should be taken that card embossing does not damage the IC. Further, positioning of the signature panel behind the IC may lead to damage due to heavy pressure being applied during signature.

5.2.3 Contact Assignment

The assignment of the ICC contacts shall be as defined in ISO/IEC 7816-2 and is shown in Table 2:

C1 Supply voltage (VCC) C5 Ground (GND)

C2 Reset (RST) C6 RFU 2

C3 Clock (CLK) C7 Input/output (I/O) C4 Not used; need not be

physically present

C8 Not used; need not be physically present

Table 2: ICC Contact Assignment

(56)

5 Electromechanical Interface EMV 4.1 Book 1 5.3 Electrical Characteristics of the ICC Application Independent ICC to Terminal Interface Requirements

5.3 Electrical Characteristics of the ICC

This section describes the electrical characteristics of the signals as measured at the ICC contacts.

5.3.1 Measurement Conventions

All measurements are made at the point of contact between the ICC and the interface device (IFD) contacts and are defined with respect to the GND contact over an ambient temperature range 0° C to 50° C. ICCs shall be capable of correct operation over an ambient temperature range of at minimum 0° C to 50° C.

All currents flowing into the ICC are considered positive.

Note: The temperature range limits are dictated primarily by the thermal

characteristics of polyvinyl chloride (which is used for the majority of cards that are embossed) rather than by constraints imposed by the characteristics of the IC.

5.3.2 Input/Output (I/O)

This contact is used as an input (reception mode) to receive data from the terminal or as an output (transmission mode) to transmit data to the terminal. During operation, the ICC and the terminal shall not both be in transmission mode. In the event that this condition occurs, the state (voltage level) of the I/O contact is indeterminate and no damage shall occur to the ICC.

(57)

EMV 4.1 Book 1 5 Electromechanical Interface

Application Independent ICC to 5.3 Electrical Characteristics of the ICC

Terminal Interface Requirements

May 2004 Page 41

5.3.2.1 Reception

Mode

When in reception mode, and with the supply voltage (VCC) for the applicable class in the range specified in section 5.3.6, the ICC shall correctly interpret signals from the terminal having the characteristics shown in Table 3:

Symbol Conditions Minimum Maximum Unit

VIH 0.7 x VCC VCC V

VIL 0 0.8 V

tR and tF — 1.0 µs

The ICC shall not be damaged by signal perturbations on the I/O line in the range –0.3 V to VCC + 0.3 V.

class A cards until end June 2009; see Table 1

Symbol Conditions Minimum Maximum Unit

VIH 0.7 x VCC VCC V

VIL 0 0.2 x VCC V

tR and tF — 1.0 µs

The ICC shall not be damaged by signal perturbations on the I/O line in the range –0.3 V to VCC + 0.3 V.

new card values from July 2009; see Table 1

(58)

5 Electromechanical Interface EMV 4.1 Book 1 5.3 Electrical Characteristics of the ICC Application Independent ICC to Terminal Interface Requirements

5.3.2.2 Transmission

Mode

When in transmission mode, the ICC shall send data to the terminal with the characteristics shown in Table 4:

Symbol Conditions Minimum Maximum Unit

VOH –20 µA < IOH < 0, VCC = min. 0.7 x VCC VCC V VOL 0 < IOL < 1 mA, VCC = min. 0 0.4 V tR and tFCIN (terminal) = 30 pF max. — 1.0 µs class A cards until end June 2009; see Table 1

Symbol Conditions Minimum Maximum Unit

VOH –20 µA < IOH < 0 0.7 x VCC VCC V VOL Class A: 0 < IOL < 1 mA 0 0.08 x VCC V Classes B and C: 0 < IOL < 0.5 mA 0 0.15 x VCCtR and tFCIN (terminal) = 30 pF max. — 1.0 µs new card values from July 2009; see Table 1

Table 4: Electrical Characteristics of I/O for ICC Transmission

Unless transmitting, the ICC shall set its I/O line driver to reception mode. There is no requirement for the ICC to have any current source capability to I/O.

5.3.3 Programming Voltage (VPP)

(59)

EMV 4.1 Book 1 5 Electromechanical Interface

Application Independent ICC to 5.3 Electrical Characteristics of the ICC

Terminal Interface Requirements

May 2004 Page 43

5.3.4 Clock (CLK)

With VCC in the range specified for the applicable class in section 5.3.6, the ICC shall operate correctly with a CLK signal having the characteristics shown in Table 5:

Symbol Conditions Minimum Maximum Unit

VIH VCC – 0.7 VCC V VIL 0 0.5 V tR and tF VCC = min. to max. — 9% of clock period

The ICC shall not be damaged by signal perturbations on the CLK line in the range –0.3 V to VCC+ 0.3 V.class A cards until end June 2009; see Table 1

Symbol Conditions Minimum Maximum Unit

VIH 0.7 x VCC VCC V

VIL 0 0.2 x VCC V

tR and tF — 9% of clock

period

The ICC shall not be damaged by signal perturbations on the CLK line in the range –0.3 V to VCC+ 0.3 V.new card values from July 2009; see Table 1

Table 5: Electrical Characteristics of CLK to ICC

The ICC shall operate correctly with a CLK duty cycle of between 44% and 56% of the period during stable operation.

The ICC shall operate correctly with a CLK frequency in the range 1 MHz to 5 MHz.

Note: Frequency shall be maintained by the terminal to within ± 1% of that used during the answer to reset throughout the card session.

(60)

5 Electromechanical Interface EMV 4.1 Book 1 5.3 Electrical Characteristics of the ICC Application Independent ICC to Terminal Interface Requirements

5.3.5 Reset (RST)

With VCC in the range specified for the applicable class in section 5.3.6, the ICC shall correctly interpret a RST signal having the characteristics shown in

Table 6:

Symbol Conditions Minimum Maximum Unit

VIH VCC – 0.7 VCC V

VIL 0 0.6 V

tR and tF VCC = min. to max. — 1.0 µs The ICC shall not be damaged by signal perturbations on the RST line in the range –0.3 V to VCC + 0.3 V.class A cards until end June 2009; see Table 1

Symbol Conditions Minimum Maximum Unit

VIH 0.7 x VCC VCC V

VIL 0 0.2 x VCC V

tR and tF VCC = min. to max. — 1.0 µs The ICC shall not be damaged by signal perturbations on the RST line in the range –0.3 V to VCC + 0.3 V.new card values from July 2009; see Table 1

Table 6: Electrical Characteristics of RST to ICC

(61)

EMV 4.1 Book 1 5 Electromechanical Interface

Application Independent ICC to 5.3 Electrical Characteristics of the ICC

Terminal Interface Requirements

May 2004 Page 45

5.3.6 Supply Voltage (VCC)

The ICC shall operate correctly with a supply voltage VCC of 5 V ± 0.5 V DC and have a maximum current requirement of 50 mA when operating at any frequency within the range specified in section 5.3.4. class A cards until end June 2009; see Table 1 Three classes of operation are defined based on the nominal

supply voltage applied to the ICC. These are defined in Table 7. The ICC shall support class A and may optionally support one or more additional consecutive classes. The ICC shall operate

correctly on any supply voltage lying within the range(s) specified for the class(es) it supports.

Symbol Conditions Minimum Maximum Unit

VCC Class A Class B Class C 4.50 2.70 1.62 5.50 3.30 1.98 V ICC Class A Class B Class C 50 50 30 mA

The maximum current consumptions shown apply when operating at any frequency within the range specified in section 5.3.4.

Table 7: Classes of Operation

new card values from July 2009; see Table 1

EMV v4.1 Book 1 ICC to Terminal Interface (2024)

References

Top Articles
Latest Posts
Article information

Author: Nathanael Baumbach

Last Updated:

Views: 6715

Rating: 4.4 / 5 (55 voted)

Reviews: 86% of readers found this page helpful

Author information

Name: Nathanael Baumbach

Birthday: 1998-12-02

Address: Apt. 829 751 Glover View, West Orlando, IN 22436

Phone: +901025288581

Job: Internal IT Coordinator

Hobby: Gunsmithing, Motor sports, Flying, Skiing, Hooping, Lego building, Ice skating

Introduction: My name is Nathanael Baumbach, I am a fantastic, nice, victorious, brave, healthy, cute, glorious person who loves writing and wants to share my knowledge and understanding with you.