0% found this document useful (0 votes)

1K views138 pages

C 5 - Kernel 5 v2.10

Uploaded by

trahoada

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

1K views138 pages

C 5 - Kernel 5 v2.10

Uploaded by

trahoada

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 138

EMV®

Contactless Specifications for

Payment Systems

Book C-5

Kernel 5 Specification

Version 2.10
March 2021

© 2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only
pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries..
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10

Legal Notice

Unless the user has an applicable separate agreement with EMVCo or with the applicable
payment system, any and all uses of these Specifications is subject to the terms and
conditions of the EMVCo Terms of Use agreement available at www.emvco.com and the
f ollowing supplemental terms and conditions.

Except as otherwise may be expressly provided in a separate agreement with EMVCo, the
license granted in the EMVCo Terms of Use specifically excludes (a) the right to disclose,
distribute or publicly display these Specifications or otherwise make these Specifications
available to any third party, and (b) the right to make, use, sell, offer for sale, or import any
sof tware or hardware that practices, in whole or in part, these Specifications. Further, EMVCo
does not grant any right to use the Kernel Specifications to develop contactless payment
applications designed for use on a Card (or components of such applications). As used in
these supplemental terms and conditions, the term “Card” means a proximity integrated circuit
card or other device containing an integrated circuit chip designed to facilitate contactless
payment transactions. Additionally, a Card may include a contact interface and/or magnetic
stripe used to facilitate payment transactions. To use the Specifications to develop
contactless payment applications designed for use on a Card (or components of such
applications), please contact the applicable payment system. To use the Specifications to
develop or manufacture products, or in any other manner not provided in the EMVCo Terms
of Use, please contact EMVCo.

These Specifications are provided "AS IS" without warranties of any kind, and EMVCo neither
assumes nor accepts any liability for any errors or o missions contained in these
Specifications. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-
INFRINGEMENT, AS TO THESE SPECIFICATIONS.

EMVCo makes no representations or warranties with respect to intellectual property rights of

any third parties in or in relation to the Specifications. EMVCo undertakes no responsibility to
determine whether any implementation of these Specifications may violate, infringe, or
otherwise exercise the patent, copyright, trademark, trade secret, know-how, or other
intellectual property rights of third parties, and thus any person who implements any part of
these Specifications should consult an intellectual property attorney before any such
implementation.

Without limiting the foregoing, the Specifications may provide for the use of public key
encryption and other technology, which may be the subject matter of patents in several
countries. Any party seeking to implement these Specifications is solely responsible for
determining whether its activities require a license to any such technology, including for
patents on public key encryption technology. EMVCo shall not be liable under any theory f or
any party's infringement of any intellectual property rights in connection with these
Specifications.

March 2021 Page ii

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specification v2.10

Revision History

The following changes have been made to Book C-5 since the publication of version
2.9. Change bars are used in this specification to denote the sections that have been
updated. Some of the numbering and cross references in this specification have
been updated to reflect the modifications made in the new version.

No. Revision Date Chapter Contents of Revision

1 March, 2021 2.4 Legacy Mode removed from Implementation Options

3.9 and Various corrections and clarifications; the changes are

2 March, 2021
others identified by the change bar on the left

3.10 and
3 March, 2021 New requirements added
others

3.1
On-Device CVM Contactless Transaction Limit defined
4 March, 2021 3.8
and related requirements added
Annex C

March 2021 Page iii

Contents
1 Introduction ..................................................................................................... 1
1.1 Scope....................................................................................................... 1
1.2 Audience .................................................................................................. 1
1.3 Volumes of the Contactless Specifications................................................. 1
1.4 Reference Materials .................................................................................. 1
1.5 Overview .................................................................................................. 2
1.6 Conventions.............................................................................................. 3
1.7 Terminology.............................................................................................. 3

2 Overview of the Kernel 5 Approach ................................................................ 4

2.1 Two Transaction Modes............................................................................ 4
2.1.1 EMV Mode .................................................................................... 4
2.1.2 Legacy Mode................................................................................. 5
2.2 Transaction Processing............................................................................. 6
2.3 High Level Transaction Flow ..................................................................... 8
2.4 Implementation Options and Acquirer Options ......................................... 11
2.4.1 Implementation Options ............................................................... 11
2.4.2 Acquirer Options.......................................................................... 12

3 Kernel Processing ......................................................................................... 14

3.1 Kernel Activation ..................................................................................... 14
3.2 Transaction Initialisation.......................................................................... 20
3.3 Initiate Application Processing ................................................................. 23
3.4 Read Application Data ............................................................................ 25
3.5 Terminal Risk Management..................................................................... 27
3.5.1 Contactless Limit Check............................................................... 27
3.5.2 CVM Required Limit Check.......................................................... 27
3.5.3 Floor Limit Check......................................................................... 28
3.5.4 Random Transaction Selection .................................................... 28
3.5.5 Exception File Check ................................................................... 29
3.6 Processing Restrictions........................................................................... 30
3.6.1 Application Usage Control Check ................................................. 30
3.6.2 Application Expiration Date Check ............................................... 30
3.6.3 Application Effective Date Check.................................................. 31
3.7 Terminal Action Analysis ......................................................................... 32
3.8 Completion – EMV Mode ........................................................................ 34
3.8.1 GENERATE AC Command .......................................................... 34
3.8.2 Offline Data Authentication .......................................................... 37
3.8.3 CVM Processing.......................................................................... 38
3.8.4 Transaction Outcome................................................................... 40

March 2021 Page iv

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10

3.9 Completion – Legacy Mode .....................................................................43

3.9.1 GENERATE AC Command ..........................................................43
3.9.2 CVM Processing ..........................................................................44
3.9.3 Online Request Outcome .............................................................45
3.10 Issuer Update Processing........................................................................47
3.10.1 Issuer Update Initialisation ...........................................................47
3.10.2 Critical Script Processing .............................................................48
3.10.3 Second GENERATE AC Command..............................................49
3.10.4 Transaction Outcome ...................................................................51
3.10.5 Non-critical Script Processing.......................................................53
3.11 Error Handling.........................................................................................55
3.11.1 Processing Errors ........................................................................55
3.11.2 Communication Errors .................................................................56
3.11.3 Transaction Cancellation ..............................................................57
3.12 Transaction Outcomes ............................................................................58
3.12.1 Approved.....................................................................................58
3.12.2 Online Request............................................................................60
3.12.3 Online Request (“Two Presentments”)..........................................62
3.12.4 Online Request (“Present and Hold”) ............................................64
3.12.5 Declined ......................................................................................66
3.12.6 Try Another Interface ...................................................................67
3.12.7 End Application............................................................................68
3.12.8 End Application (with restart – communication error).....................69
3.12.9 End Application (with restart - On-Device CVM) ............................70
3.12.10 Select Next..............................................................................71
3.13 Torn Transaction Recovery .....................................................................72
3.13.1 SELECT Response Analysis ........................................................74
3.13.2 ECHO Command .........................................................................74
3.13.3 Transaction Initialisation...............................................................75
3.13.4 Initiate Application Processing ......................................................75
3.13.5 Read Application Data .................................................................75
3.13.6 Transaction Recovery Completion ................................................76
3.13.7 Reset Recovery Context ..............................................................78

4 APDU command description .........................................................................79

4.1 ECHO .....................................................................................................80
4.2 First GENERATE APPLICATION CRYPTOGRAM ...................................82
4.3 Second GENERATE APPLICATION CRYPTOGRAM ..............................85
4.4 GET PROCESSING OPTIONS................................................................87
4.5 READ RECORD .....................................................................................89
4.6 SELECT..................................................................................................90

March 2021 Page v

Annex A Coding of Data Elements Used in Transaction Flow ......................... 91

A.1 Application Interchange Profile (AIP) (Tag ‘82’)........................................ 91
A.2 Cardholder Verification Status (Tag ‘9F50’) ............................................. 92
A.3 Combination Options............................................................................... 93
A.4 CVM Results (Tag ‘9F34’) ....................................................................... 94
A.5 Device Information (Tag ‘9F6E’) .............................................................. 96
A.6 Issuer Update Parameter (Tag ‘9F60’)..................................................... 97
A.7 Partner Discretionary Data (Tag ‘9F7C’) .................................................. 97
A.8 Terminal Compatibility Indicator (Tag ‘9F52’) ........................................... 99
A.9 Terminal Interchange Profile (static/dynamic) (Tag ‘9F53’) ..................... 100
Annex B Data Elements Dictionary................................................................. 101
Annex C Kernel 5 Transaction Record ........................................................... 116
Annex D Default Terminal Action Code values .............................................. 120
Annex E Glossary ........................................................................................... 123

Figures
Figure 2-1: High-Level Sample Transaction Flow .................................................... 9
Figure 3-1 : Overview of the Recovery Transaction Flow ........................................ 73

Tables
Table 1-1: Conventions used for data format............................................................ 3
Table 1-2: Terminology............................................................................................ 3
Table 3-1: Static Kernel Configuration Parameters................................................ 15
Table 3-2: Dynamic Transaction Parameters ........................................................ 18
Table 4-1: List of APDU commands used by the Kernel ........................................ 79
Table 4-2: ECHO Command Message .................................................................. 80
Table 4-3: Data Objects Included in Response to Second GENERATE AC............. 85
Table 4-4: Data Objects Included in Response to GET PROCESSING OPTIONS . 88
Table A-1: Application Interchange Profile ............................................................ 91
Table A-2: Cardholder Verification Status ............................................................. 92
Table A-3: Combination Options ........................................................................... 93
Table A-4-1: CVM Results.................................................................................... 94
Table A-4-2: Setting of CVM Results..................................................................... 95
Table A-5: Device Information .............................................................................. 96
Table A-6: Issuer Update Parameter...................................................................... 97
Table A-7: Partner Discretionary Data.................................................................... 97
Table A-8: Terminal Compatibility Indicator ........................................................... 99

March 2021 Page vi

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10

Table A-9: Terminal Interchange Profile ..............................................................100

Table B-1: Data Elements Dictionary...................................................................101
Table C-1: Minimum Data Elements returned as Transaction Record ..................116
Table D-1: Default Terminal Action Code values .................................................120

March 2021 Page vii

Requirements
Requirement – Static Configuration Parameters..................................................... 14
Requirement – Dynamic Transaction Parameters .................................................. 14
Requirement – Recovering from Torn EMV Transaction ......................................... 20
Requirement – Transaction continuation ................................................................ 20
Requirement – SELECT response analysis............................................................ 21
Requirement – Variable Initialisation ...................................................................... 21
Requirement – Terminal Interchange Profile .......................................................... 21
Requirement – Legacy Mode Detection ................................................................. 22
Requirement – PDOL Processing and GPO Command .......................................... 23
Requirement – GPO Response Analysis................................................................ 23
Requirement – Reading Records........................................................................... 25
Requirement – Presence of Mandatory Data Elements .......................................... 25
Requirement – Contactless Limit Check................................................................. 27
Requirement – CVM Required Limit Check............................................................ 27
Requirement – Floor Limit Check........................................................................... 28
Requirement – Random Transaction Selection ...................................................... 28
Requirement – Exception File Check ..................................................................... 29
Requirement – Application Usage Control.............................................................. 30
Requirement – Application Expiration Date ............................................................ 30
Requirement – Application Effective Date .............................................................. 31
Requirement – Terminal Action Analysis................................................................ 32
Requirement – Terminal Action Analysis Completion ............................................. 33
Requirement – CDOL1 Processing ........................................................................ 34
Requirement – GENERATE AC............................................................................. 34
Requirement – GENERATE AC Response Analysis............................................... 35
Requirement – Card Removal ............................................................................... 37
Requirement – CDA Signature Verification ............................................................ 38
Requirement – CVM Evaluation............................................................................. 38
Requirement – CVM Consistency Check ............................................................... 39
Requirement – On-Device CVM Contactless Transaction Limit and Contactless Limit
Check ................................................................................................. 40
Requirement – Decision of Transaction Outcome................................................... 41
Requirement – Setting of Outcome Parameters ..................................................... 42
Requirement – Providing of Transaction Outcome ................................................. 42
Requirement – CDOL1 Processing ........................................................................ 43
Requirement – GENERATE AC............................................................................. 43
Requirement – CVM Required Check .................................................................... 44
Requirement – CVM Evaluation............................................................................. 45
Requirement – Decision of Online Request Outcome ............................................. 45
Requirement – CVM Consistency Check ............................................................... 46

March 2021 Page viii

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10

Requirement – Providing of Transaction Outcome..................................................46

Requirement – SELECT response analysis............................................................47
Requirement – Critical Script Processing ...............................................................48
Requirement – Critical Script Processing Completion .............................................49
Requirement – CDOL2 Processing ........................................................................50
Requirement – GENERATE AC .............................................................................50
Requirement – GENERATE AC Response Analysis...............................................51
Requirement – Transaction Outcome .....................................................................51
Requirement – Non-critical Script Processing.........................................................53
Requirement – Non-critical Script Processing Completion ......................................54
Requirement – Processing Errors - Default ............................................................55
Requirement – Communication Errors – First GENERATE AC ...............................56
Requirement – Communication Errors – Issuer Updates ........................................56
Requirement – Communication Errors – General ...................................................57
Requirement – Transaction cancellation by Reader................................................57
Requirement – Approved Outcome ........................................................................58
Requirement – Online Request Outcome ...............................................................60
Requirement – Online Request Outcome (“Two Presentments”) .............................62
Requirement – Online Request Outcome (“Present and Hold”) ...............................64
Requirement – Declined Outcome .........................................................................66
Requirement – Try Another Interface Outcome ......................................................67
Requirement – End Application..............................................................................68
Requirement – Communication Errors ...................................................................69
Requirement – On-Device CVM to be Performed ...................................................70
Requirement – Select Next ....................................................................................71
Requirement – SELECT Response Analysis ..........................................................74
Requirement – ECHO Command ...........................................................................74
Requirement – Transaction Initialisation.................................................................75
Requirement – Initiate Application..........................................................................75
Requirement – Read Application Data ...................................................................76
Requirement – Account Data Verification ...............................................................76
Requirement – Transaction Recovery Completion ..................................................77
Requirement – Reset Recovery Context ................................................................78

March 2021 Page ix

1 Introduction
This chapter contains information that helps the reader understand and use this
specification.

1.1 Scope
This document, the EMV Contactless Specifications for Payment Systems, Kernel 5
Specification, describes one of several Kernels defined for use with Entry Point.

1.2 Audience
This specification is intended for use by reader providers and financial institution staff
responsible for implementing financial applications.

1.3 Volumes of the Contactless Specifications

This specification is part of a multi-volume set:
Book A: Architecture and General Requirements
Book B: Entry Point Specification
Book C-n: Kernel Specifications
EMV L1 Contactless : EMV Contactless Interface Specification

1.4 Reference Materials

The following specifications and standards contain provisions that are referenced in
this specification. The latest version shall apply unless a publication date is explicitly
stated.
If any provision or definition in this specification differs from those in the listed
specifications and standards, the provision or definition herein shall take precedence.

[EMV] EMV Integrated Circuit Card Specifications for Payment

Systems, including:

March 2021 Page 1

[EMV Book 1] EMV Integrated Circuit Card Specifications for Payment

Systems, Book 1, Application Independent ICC to
Terminal Interface Requirements

[EMV Book 2] EMV Integrated Circuit Card Specifications for Payment

Systems, Book 2, Security and Key Management

[EMV Book 3] EMV Integrated Circuit Card Specifications for Payment

Systems, Book 3, Application Specification

[EMV Book 4] EMV Integrated Circuit Card Specifications for Payment

Systems, Book 4, Cardholder, Attendant, and Acquirer
Interface Requirements

1.5 Overview
This volume includes the following chapters and annexes:
Chapter 1 contains general information that helps the reader understand and use
this specification.
Chapter 2 provides an overview of the Kernel 5 approach, including
implementation/acquirer options and a high level transaction flow description.
Chapter 3 specifies transaction processing for Kernel 5.
Chapter 4 lists and describes the APDU commands used by Kernel 5.
Annex A defines data elements that are specific to Kernel 5.
Annex B is a dictionary of data elements used by Kernel 5 during the transaction
processing.
Annex C lists data elements that are required in the transaction record for approved,
declined, and online requested transactions.
Annex D defines the default Terminal Action Codes used by Kernel 5.
Annex E is a glossary of terms and abbreviations used in this specification.

March 2021 Page 2

1.6 Conventions
Table 1-1: Conventions used for data format

Convention Meaning
a Alphabetic
an Alphanumeric
ans Alphanumeric Special
b Binary
cn Compressed Numeric
n Numeric
Numeric value of y digits (Example n 12 means 12 digits numeric
ny
value)
YYMMDD Year, Month, Day
x Numeric value in decimal
‘x’ Numeric value in hexadecimal
“abc” Data string
var. Variable value

For data elements which have multiple bytes in this specification, the first byte or byte
1 is the leftmost byte, while the last byte is the rightmost byte.

1.7 Terminology
Table 1-2: Terminology

Terminology Meaning
Shall, “is
Denotes a mandatory requirement.
mandatory”
Should, may,
can, “is Denotes an optional requirement.
optional”
if test_condition
then Denotes a conditional test action, action_true is performed when
action_true test_condition result is true, action_false is performed when
else test_condition result is false.
action_false
and Logical AND which connects two conditional requirements
or Logical OR which connects two conditional requirements
= Logical comparison of two values
N/A Not applicable

March 2021 Page 3

2 Overview of the Kernel 5 Approach

This section is a high-level description of Kernel 5 features, capabilities, and
processes. Further details about the Transaction Flow and its implementation can be
found in Section 3.

2.1 Two Transaction Modes

Kernel 5 shall always support EMV Mode and Legacy Mode.

2.1.1 EMV Mode

EMV Mode is designed for Chip Grade payment infrastructures.
The support of EMV Mode is mandatory on the Kernel side. The card will select to
conduct the transaction in EMV Mode when the card supports it.
The EMV Mode has many similarities with the transaction flow designed for contact
EMV chips and defined in [EMV]. It is however simplified and adapted for contactless
ergonomics. Here are the main features:
• Online/offline capability: EMV Mode transactions can be completed either
online or offline. When completed online, the card is normally not informed
about the final transaction outcome.
• Offline Data Authentication: The kernel shall support CDA when at least
one of the conditions below is fulfilled:
o the Kernel is offline-capable;
o the Kernel is installed in a transit reader (where Cardholder
Verification is bypassed);
o the Kernel accepts On-Device CVM verification.
Other data authentication methods (SDA, DDA) are not supported.
• Online Data Authentication: An ARQC cryptogram is generated by the card
and verified by the Issuer host system.
• Cardholder Verification: The card determines the CVM requirement based
on issuer preference and acquirer requirement and the Kernel performs the
selected CVM.

March 2021 Page 4

2.1.2 Legacy Mode

Legacy Mode is available for Chip Grade acquirers to satisfy specific market
requirements. Please refer to payment system rules for further details. Here are the
main features:
• Online/offline capability: Legacy Mode transactions are always authorised
online. The card is not informed about the final transaction outcome.
• Offline Data Authentication: N/A
• Online Data Authentication: An ARQC cryptogram is generated by the card
and verified by the Issuer host system.
• Cardholder Verification: If the amount exceeds the CVM Required Limit, the
Kernel analyses the CVM List from the card to determine the CVM
requirement.

March 2021 Page 5

2.2 Transaction Processing

The transaction processing is summarised below.

1. Entry Point determines the most relevant Combination {ADF Name, AID,
Kernel ID, Application Priority Indicator} to process the transaction, based on
Reader Combinations and the card’s ADF parameters in the PPSE Response
(Application Priority Indicator, Kernel Identifier).
2. Entry Point activates the Kernel to process the transaction. The reader
provides transaction data and the relevant configuration parameters to the
Kernel.
a. Based on the card response to the SELECT (DF Name) command,
the Kernel can determine whether it is a legacy card or not.
3. The Kernel sends the GET PROCESSING OPTIONS command to the card to
initialise the card application.
a. Card returns the Application Interchange Profile (AIP) and the
Application File Locator (AFL).
b. For non-legacy cards, the card response enables to detect that the
card has selected the EMV Mode.
4. The Kernel reads the card data as indicated by the AFL.
5. The Kernel performs Terminal Risk Management, which consists of several
verifications:
a. Contactless Limit Check
b. CVM Limit Check
c. Floor Limit Check (EMV Mode only)
d. Random Transaction Selection (EMV Mode only)
e. Exception File Check (option only applying to EMV Mode)
These verifications update the Terminal Verification Results (TVR).
6. The Kernel performs Processing Restrictions, which consists of several
verifications:
a. Application Usage Control (EMV Mode only)
b. Application Expiration Date
c. Application Effective Date
These verifications update the Terminal Verification Results (TVR).

March 2021 Page 6

7. Based on the TVR value, as well as Terminal Action Codes (TAC) and Issuer
Action Codes (IAC), the Kernel computes the first transaction outcome.
a. If the outcome is a Decline, the transaction is declined offline and the
Kernel provides a Declined Outcome to the Entry Point.
b. In the case of Legacy Mode, unless the payment application declines
the transaction, then the outcome is Online Authorisation.
8. The Kernel then completes the transaction in the following steps:
a) If the transaction is in EMV Mode:
• The Kernel issues a GENERATE AC command including Combined
Data Authentication (CDA) request when supported.
• If the card approves or sends the transaction for authorisation
(TC/ARQC), the card response includes a CDA signature (if requested
by the Kernel) as well as the decision of the card regarding the
Cardholder Verification Method (CVM) to be applied.
• The Kernel verifies the CDA signature (if any) and if valid, executes
the card decision (TC/ARQC) and CVM policy.The Kernel then
provides an Approved or Online Request Outcome corresponding to
the decision for this transaction to the Entry Point.
b) If the transaction is in Legacy Mode:
• The Kernel issues a GENERATE AC command requesting an online
authorisation (ARQC) without CDA.
• The card returns the ARQC cryptogram.
• If the CVM Required Limit is exceeded, the Kernel analyses the CVM
list from the card to find an appropriate method.
• The Kernel provides an Online Request Outcome to the Entry Point
for this transaction for online authorisation.
9. Optionally, if the transaction is in EMV Mode and the Transaction Outcome is
Online Request, the reader may reactivate the Kernel when the online
response from the Issuer contains any information. At this point, the card may
still be in the field (e.g. “present-and-hold”) or requested to be presented
again (e.g. “two presentments”).
• For “present-and-hold”: when returning the ARQC cryptogram, the card
informs simultaneously the Kernel that it shall be maintained in the
contactless field during the online authorisation. After receiving the online
response, Issuer Scripts and/or Issuer Authentication Data can be
transmitted to the card.

March 2021 Page 7

• For “two presentments”: when returning the ARQC cryptogram, the card
informs simultaneously the Kernel that it supports a second presentment.
After receiving the online response, the cardholder is asked by Entry Point
to present the card again, and Issuer Scripts and/or Issuer Authentication
Data can be transmitted to the card.

2.3 High Level Transaction Flow

Figure 2-1 below illustrates the high-level transaction flow of Kernel 5.
The purpose is to provide a summarised overview of the normal Kernel 5 processing
and is not prescriptive. Note that specific processes like Transaction Recovery or
Issuer Update are not represented in this figure which features only a nominal
transaction flow.
Details about each step of the transaction can be found in Section 3.

March 2021 Page 8

Figure 2-1: High-Level Sample Transaction Flow

Transaction Flow

SELECT (PPSE)
Discovery
Process handled
by Entry Pont
SELECT (DF)

Legacy
Legacy
Yes mode No Select Next
Card?
supported?

Yes

GET PROCESSING OPTIONS (Card exception)

READ RECORD(s) (Card exception)

Terminal Risk Management:

- Contactless Limit Check
- CVM Limit Check
- Floor Limit Check
- Random Selection
- Exception File Check

Processing Restrictions
- Application Usage Control
- Application Expiration Date
- Application Effective Date

Legacy Mode, EMV/Legacy Mode,

Online
Terminal Action Analysis Declined
Declined

EMV Mode, Approved/Online

End
GENERATE AC (ARQC) Application GENERATE AC (CDA) AAC
(1st tap)
TC/ARQC
CARD REMOVAL

Declined
NOK
CDA Verification
NOK

CVM Process CVM Process

NOK
(Legacy Mode) (EMV Mode)

Online
ARQC Approved
Request

March 2021 Page 9

online response

Case of "present-and-hold" Case of "two presentment"

Correct FCI SELECT (ADF)

Incorrect FCI
contain
Issuer Script Template 1? No
(tag ‘71’)

Yes

Issuer Script Commands

contain
Issuer Authentication Data
(tag ‘91’) No
or Issuer Script Template 2?
(tag ‘72’)

Yes

- SW≠9000
2nd GENERATE AC - incorrect format

SW=9000

Prepare Outcome

contain
Issuer Script Template 2? No
(tag ‘72’)

Yes

Issuer Script Commands

Prepared Outcome is "Approved" Prepared Outcome is "Declined"

Approved Declined End Application

March 2021 Page 10

2.4 Implementation Options and Acquirer Options

2.4.1 Implementation Options

The provider of Kernel 5 will choose whether to support or not the following options in
the Kernel 5 implementation:
• Offline Data Authentication
o This implementation option enables support of CDA to authenticate
the card. CDA is only used for EMV Mode.
o Kernel 5 implementations for offline-capable readers, transit readers,
or readers accepting On-Device CVM shall support this option.
• Exception File Check
o This implementation option enables Kernel 5 to check during the
transaction whether the card appears in the Acquirer Exception File.
o Exception File Check is only used for EMV Mode.
o Implementations for transit readers shall support this option.
o The Data Exchange mechanism enable readers to update Acquirer
Exception File. Readers supporting Exception File Check should
support Data Exchange.
o The exact implementation of this option is left at the discretion of the
implementer. It may, for instance, take advantage of the Data
Exchange mechanism described in Book A.
• Issuer Update
o This implementation option enables to convey EMV data (Issuer
Authentication Data and/or Issuer Scripts, which are/is optionally
present in the Authorisation Response Message) to the contactless
card, upon completion of the Authorisation process.
o An Issuer Update may be transmitted to the card in one of two forms:
either as a single presentment of the card (i.e. card remains in the
contactless field while the authorisation process is ongoing), or as a
second presentment of the card after the authorisation. Readers
supporting Issuer Update shall support both ergonomics, as the
choice is indicated by the card.
o Issuer Update is only used for EMV Mode.
• Cardholder Verification Method
The Kernel 5 shall support all Cardholder Verification Methods described in
this specification except following case applies:

March 2021 Page 11

o If the Reader supports only Transit Reader, the Reader provider may
choose whether to support or not the Cardholder Verification Method.
o If the Reader supports offline environment only, the Reader provider
may choose whether to support or not the following Cardholder
Verification Method in the Reader implementation:
- Online PIN
o If the Reader supports ATM only, the Reader provider may choose
whether to support or not the following Cardholder Verification Method
in the Reader implementation:
- Signature
- On-Device CVM
o If the Reader supports Unattended Merchant Terminal only, the
Reader provider may choose whether to support or not the following
Cardholder Verification Method in the Reader implementation:
- Signature
- Online PIN

2.4.2 Acquirer Options

In addition to the Implementation Options, which define the features for a specific
Kernel 5 implementation, the Acquirer may also choose to support from these
implemented features for deployment. The Acquirer Options are defined below:
Acquirer Options are parameterised in the Combination Options parameter (see
Annex A.3) or in the static Terminal Interchange Profile (see Annex A.9) for each
supported Reader Combination.
• Legacy Mode
o This option activates Legacy Mode flow for the associated Reader
Combination.
• Offline Data Authentication
o This option activates CDA for EMV Mode. The option shall be
activated if any of the conditions below is true:
▪ the reader is offline-capable.
▪ the reader is a transit reader as configured in the Terminal
Interchange Profile (see Section A.9).

March 2021 Page 12

▪ the reader accepts “On-Device CVM” as a Cardholder

Verification Method in the Terminal Interchange Profile (see
Section A.9).
o The option is available only if Offline Data Authentication
(implementation option) is supported in EMV Mode.
• Exception File Check
o This option activates Acquirer Exception File Check during the
transaction.
o The option is available only if Exception File Check (implementation
option) is supported in EMV Mode.
• Random Transaction Selection
o This option activates Random Transaction Selection during Terminal
Risk Management.
• Issuer Update
o This option activates Issuer Update to convey EMV data (Issuer
Authentication Data and/or Issuer Scripts, which are/is optionally
present in the Authorisation Response Message) to the contactless
card, upon completion of the Authorisation process.
o The option is available only if Issuer Update (implementation option) is
supported in EMV Mode.

March 2021 Page 13

3 Kernel Processing
This chapter provides detailed transaction processing requirements for Kernel 5
including information related to EMV functions.

3.1 Kernel Activation

When activated, Kernel 5 requires certain data elements to be available in order to
process the transaction.
A data element or flag may be:
• Static (Configuration parameter): The value of this data is persistent from one
transaction to the next (See Table 3-1). Updates of the values are exceptional
and always outside the scope of Kernel 5 processing. A static data element may
be set:
o per POS System (e.g. Terminal Country Code), or
o per RID (e.g. CAPK key), or
o per AID (e.g. static Terminal Interchange Profile)
• Dynamic (Transaction parameter): Per transaction, e.g. Amount, Authorised
(Numeric) and Unpredictable Number (See Table 3-2).

Requirement – Static Configuration Parameters

3.1.1.1 When the Kernel is activated, the reader shall provide to the
Kernel the Configuration Data (see Table 3-1 : Static Kernel
Configuration Parameters) associated with the selected
Combination.

Requirement – Dynamic Transaction Parameters

3.1.1.2 When the Kernel is activated, the reader shall provide to the
Kernel:
• The Dynamic Transaction Parameters (see Table 3-2 :
Dynamic Transaction Parameters); and
• FCI received from the card as per section 3.4 in [EMV CL
Book B] (when applicable).

March 2021 Page 14

Table 3-1: Static Kernel Configuration Parameters

Varies Length
Name Description Presence1 Format Specified Tag
by (bytes)
On-Device CVM Indicates the limit for which contactless
Contactless transactions can be conducted when CVM is On- AID O n12 Kernel 5 - 6
Transaction Limit Device CVM (EMV Mode only).
Combination Defines some acquirer options for the Kernel 5
AID M b - 2
Options combination, e.g. modes supported. See A.3
Used in Kernel 5 Terminal Risk Management
Contactless Floor (EMV Mode only). Present if the Combination
AID C n12 Kernel 5 - 6
Limit supports Floor Limit Check or Random
Transaction Selection.
Used in Kernel 5 Terminal Risk Management.
Indicates the limit for which contactless
Contactless
transactions can be conducted when CVM is AID O n12 Kernel 5 - 6
Transaction Limit
other than On-Device CVM (EMV Mode), or when
Transaction Mode is Legacy Mode.
CVM Required Limit Used in Kernel 5 Terminal Risk Management. AID O n12 Kernel 5 - 6
Maximum Target
Percentage to be Present if the Combination supports Random
AID C n2 EMV - 1
Used for Biased Transaction Selection (EMV Mode only).
Random Selection

1
M = mandatory ; C = conditional ; O = optional
March 2021 Page 15

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.1 Kernel Activation

Varies Length
Name Description Presence1 Format Specified Tag
by (bytes)
Present if the Combination supports Issuer
Update as Acquirer Option (EMV Mode only).
In case of Online Request with “Present and
Removal Timeout Hold” outcome, this parameter corresponds to the AID C n4 Kernel - 2
time after which cardholder is asked to remove
the card.
Value is given in units of 100ms.
Target Percentage
to be Used for Present if the Combination supports Random
AID C n2 EMV - 1
Biased Random Transaction Selection (EMV Mode only).
Selection
Terminal Action Used in Kernel 5 Terminal Action Analysis (EMV
AID O b EMV - 5
Code - Default Mode only).
Terminal Action
Used in Kernel 5 Terminal Action Analysis. AID O b EMV - 5
Code - Denial
Terminal Action Used in Kernel 5 Terminal Action Analysis (EMV
AID O b EMV - 5
Code - Online Mode only).
Terminal Defines the Cardholder Verification Methods and
Kernel 5
Interchange Profile other reader capabilities (online capability, AID M b - 3
See A.9
(static) contact EMV capability) for the Combination.
Threshold Value for
Present if the Combination supports Random
Biased Random AID C n12 EMV - 6
Transaction Selection (EMV Mode only).
Selection
Uniquely identifies the acquirer within each
Acquirer Identifier POS M n 6-11 EMV ‘9F01’ 6
payment system.
Classifies the type of business being done by the
Merchant Category
merchant, represented according to ISO POS C n4 EMV ‘9F15’ 2
Code
8583:1993 for Card Acceptor Business Code.
March 2021 Page 16

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.1 Kernel Activation

Varies Length
Name Description Presence1 Format Specified Tag
by (bytes)
Merchant Name
Indicates the name and location of the merchant. POS M ans EMV ‘9F4E’ var.
and Location
Terminal Country Indicates the country of the terminal, represented
POS M n3 EMV ‘9F1A’ 2
Code according to ISO 3166. Requested in CDOL1.
Indicates the environment of the terminal, its
Terminal Type communications capability, and its operational POS M n2 EMV ‘9F35’ 1
control.
Transaction Indicates the currency code of the transaction
Currency Code according to ISO 4217. Requested in CDOL1. POS M n3 EMV ‘5F2A’ 2
Indicates the implied position of the decimal point
Transaction from the right of the transaction amount
Currency Exponent represented according to ISO 4217. Required to POS M n1 EMV ‘5F36’ 1
determine if Status Check is requested.
Present (up to 6 different instances) if Offline
Data Authentication is supported for at least one
of the Combinations with this RID (EMV Mode
only).
Certification Each CA Public Key in the list is composed of the
RID C b EMV - var.
Authority Public Key following mandatory fields:
- CAPK Index (b, 1 byte)
- CAPK Modulus (b, max. 248 bytes)
- CAPK Exponent (b, 1 or 3 bytes)
- CAPK SHA-1 Checksum (b, 20 bytes)

March 2021 Page 17

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.1 Kernel Activation

Table 3-2: Dynamic Transaction Parameters

Length
Name Description Presence2 Format Specified Tag
(bytes)
Amount, Authorised Authorised amount of the transaction.
M n12 EMV ‘9F02’ 6
(Numeric) Requested in CDOL1.
Secondary amount associated with the
Amount, Other
transaction representing a cashback amount. M n12 EMV ‘9F03’ 6
(Numeric)
Requested in CDOL1.
Code that defines the disposition of a
Authorisation message. ARC shall be present if the Kernel is
Response Code restarted after an Online Request Outcome. C an2 EMV ‘8A’ 2
(ARC) ARC shall not be present if it is a new
transaction.
Data sent to the card for online issuer
authentication. Issuer Authentication Data may
Issuer Authentication be present if the Kernel is restarted after an
O b EMV ‘91’ 8-16
Data Online Request Outcome. Issuer
Authentication Data shall not be present if it is
a new transaction.
Contains proprietary issuer data for
transmission to the card before the second
GENERATE AC command. Several
var.
Issuer Script occurrences of this data element may be
O b EMV ‘71’ max.
Template 1 present. Issuer Script Template 1 may be
128
present if the Kernel is restarted after an Online
Request Outcome. Issuer Script Template 1
shall not be present if it is a new transaction.

2
M = mandatory ; C = conditional ; O = optional
March 2021 Page 18

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.1 Kernel Activation

Length
Name Description Presence2 Format Specified Tag
(bytes)
Contains proprietary issuer data for
transmission to the card after the second
GENERATE AC command. Several
Issuer Script occurrences of this data element may be var.
O b EMV ‘72’ max.
Template 2 present. Issuer Script Template 2 may be
128
present if the Kernel is restarted after an Online
Request Outcome. Issuer Script Template 2
shall not be present if it is a new transaction.
Local date that the transaction was authorised.
Transaction Date M n6 EMV ‘9A’ 3
Requested in CDOL1.
Local time that the transaction was authorised.
Transaction Time M n6 EMV ‘9F21’ 3
Possibly requested in CDOL1.
Indicates the type of financial transaction,
represented by the first two digits of the ISO
8583:1987 Processing Code. Requested in
CDOL1. Possible values are:
Transaction Type M n2 EMV ‘9C’ 1
- ‘00’ for a purchase transaction
- ‘01’ for a cash advance transaction
- ‘09’ for a purchase with cashback
- ‘20’ for a refund transaction
Value to provide variability and uniqueness to
Unpredictable
the generation of a cryptogram. Requested in M b EMV ‘9F37’ 4
Number CDOL1.

March 2021 Page 19

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.2 Transaction Initialisation

3.2 Transaction Initialisation

During Transaction Initialisation, Kernel 5 initialises internal variables and performs
verifications.

Requirement – Recovering from Torn EMV Transaction

3.2.1.1 If the Kernel internal variable ‘Recovering from Torn EMV

Transaction’ has value TRUE,
Then the Kernel shall proceed with Torn Transaction Recovery as
described in section 3.13.
Otherwise the Kernel shall proceed with Requirement 3.2.1.2.

Requirement – Transaction continuation

3.2.1.2 If Authorisation Response Code (Tag ‘8A’) is present in the

Dynamic Transaction Parameters (see Table 3-2),
Then the Kernel shall proceed with Requirement 3.2.1.3.
Otherwise the Kernel shall proceed with Requirement 3.2.1.4.

3.2.1.3 If any of the following is present in the Dynamic Transaction

Parameters (see Table 3-2),
- Issuer Authentication Data (‘91’)
- At least one occurrence of Issuer Script Template 1 (‘71’)
- At least one occurrence of Issuer Script Template 2 (‘72’)
Then the Kernel shall restore transaction data from the Online
Transaction Context and proceed with Issuer Update Processing,
as described in section 3.10.
Otherwise the Kernel shall provide an End Application outcome as
described in section 3.12.7.

March 2021 Page 20

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.2 Transaction Initialisation

Requirement – SELECT response analysis

3.2.1.4 If the FCI is absent

Or if the FCI is not parsed correctly (see table 45 in [EMV Book 1])
Or if the PDOL data element is absent, or present but empty,
Then the Kernel shall terminate the transaction and provide a Select
Next Outcome as described in Section 3.12.10.

Requirement – Variable Initialisation

3.2.1.5 The Kernel shall reset the following data elements:

• Terminal Verification Results (Tag ‘95’) to ‘00 00 00 00 00’
• Terminal Compatibility Indicator (Tag ‘9F52’) to ‘00’,

3.2.1.6 The Kernel shall reset the following internal variables:

• Online Transaction Context
• Transaction Mode to ‘Undefined Mode’

Requirement – Terminal Compatibility Indicator

3.2.1.7 The Kernel shall set Terminal Compatibility Indicator (Tag ’9F52’)
to ’02’

Requirement – Terminal Interchange Profile

3.2.1.8 The Kernel shall initialise a dynamic Terminal Interchange Profile

(Tag ‘9F53’) from the value of the static Terminal Interchange
Profile (static configuration parameter – no tag) and perform the
following:
• Clear Byte 1 Bit 8 (“CVM required by reader”).
• If Issuer Update is not supported as an implementation
option,
Then clear Byte 2 Bit 8 (‘Issuer Update supported’).
Note: The dynamic Terminal Interchange Profile (Tag ‘9F53’) is
updated by the Kernel during subsequent processing.

March 2021 Page 21

At this stage, the Kernel will detect whether the presented card is a legacy card, and
if so, ensure that it has the capability to process such cards.

Requirement – Legacy Mode Detection

3.2.1.9 If the PDOL contains Terminal Compatibility Indicator (Tag ‘9F52’),

Then the Kernel shall proceed with section 3.3: Initiate Application
Processing.

Otherwise the card is a legacy card and the Kernel shall proceed
with Requirement 3.2.1.10.

3.2.1.10 If the Combination Options indicates ‘Legacy Mode Supported’ for

this AID,
Then the Kernel shall set Transaction Mode to ‘Legacy Mode’ and
proceed with section 3.3: Initiate Application Processing.

Otherwise the Kernel shall terminate the transaction and provide

a Select Next Outcome as described in Section 3.12.10.

March 2021 Page 22

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.3 Initiate Application Processing

3.3 Initiate Application Processing

The PDOL provided by the card in response to the SELECT command contains a list
of tags that the card requests to the reader. The reader provides the card with the
PDOL-related data elements when issuing the GPO command to the card.

Requirement – PDOL Processing and GPO Command

3.3.1.1 The Kernel shall process the PDOL and send the command data for
the GET PROCESSING OPTIONS as described in [EMV Book 3].

3.3.1.2 If the PDOL requires a data element that is not recognised by the
Kernel (not referenced in Annex B),
Then the Kernel shall fill in the corresponding PDOL related data
with zeroes.

The Application Interchange Profile (AIP) and Application File Locator (AFL) returned
by the card in response to the GPO command contain information on the card
configuration and data records to be read. The card response may use either Format
1 or Format 2, as described in [EMV Book 3].
The Kernel detects that EMV Mode is selected by the card by checking the value of
AIP returned by the card. The Kernel also ensures that the card supports CDA. Other
AIP bits are not analysed by the Kernel.

Requirement – GPO Response Analysis

3.3.1.3 If the AIP (Tag ‘82’) is absent from the GET PROCESSING OPTIONS
response,
Then the Kernel shall terminate the transaction and provide a
Select Next Outcome as described in Section 3.12.10.

3.3.1.4 If the Transaction Mode is equal to ‘Undefined Mode’,

Then
If the AIP (Tag ‘82’) returned by the card has Byte 2 Bit 8 set to
‘1’ (‘EMV Mode Selected’),
And the Terminal Compatibility Indicator Byte 1 Bit 2 is set to
‘1’ (‘EMV Mode Supported’),
Then the Kernel shall set Transaction Mode to ‘EMV Mode’.
Else the Kernel shall terminate the transaction and provide a
Select Next Outcome as described in Section3.12.10.

March 2021 Page 23

Requirement – GPO Response Analysis

3.3.1.5 If the AFL (Tag ‘94’) is absent from the data returned to the GET
PROCESSING OPTIONS response
Then the Kernel shall terminate the transaction and provide a
Select Next Outcome as described in Section 3.12.10.

3.3.1.6 If the AFL (Tag ‘94’) is present in the GET PROCESSING OPTIONS
RESPONSE
And its value is incorrectly formatted (e.g. not multiple of 4 bytes,
invalid SFI value...),
Then the Kernel shall terminate the transaction and provide a
Select Next Outcome as described in Section 3.12.10.

3.3.1.7 If any of the conditions below is true:

• the Transaction Mode is equal to ‘Legacy Mode’
• the Transaction Mode is equal to ‘EMV Mode’ and Offline Data
Authentication (implementation or acquirer option) is not
supported
• the Transaction Mode is equal to ‘EMV Mode’ and the AIP (Tag
‘82’) indicates that CDA is not supported (Byte 1 bit 1 is ‘0’)
Then the Kernel shall set TVR Byte 1 bit 8 (‘Offline Data
Authentication was not performed’) to ‘1’.

March 2021 Page 24

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.4 Read Application Data

3.4 Read Application Data

The Kernel uses the AFL to determine which records to request from the card. The
Kernel does not need to process any data at this point, except to determine if all the
mandatory data elements are present.

Requirement – Reading Records

3.4.1.1 If the AFL has been provided by the card, the Kernel shall read the
records indicated in the AFL using the READ RECORD command
and process the response as defined in [EMV Book 3].

At this point, the Kernel needs to determine if all mandatory data elements are
present. Even if the Kernel reads data objects that are not recognised by the Kernel
(that is, their tags are unknown by the Kernel), the Kernel shall not terminate the
transaction.

Requirement – Presence of Mandatory Data Elements

3.4.1.2 If any of the following mandatory Data Elements is absent from

the card:
• CDOL1 (Tag ‘8C’)
• Track2 Equivalent Data (Tag ‘57’)
• Application Expiration Date (Tag ‘5F24’)
Then the Kernel shall terminate the transaction and provide a
Select Next Outcome as described in Section 3.12.10.

If Offline Data Authentication is supported, CDA is the one and only mandatory Data
Authentication Method 3 supported by the Kernel in ‘EMV Mode’, hence the Kernel
shall ensure that all the appropriate data elements are present.

3
SDA/DDA is not supported for EMV Mode.

March 2021 Page 25

3.4.1.3 If the Transaction Mode is ‘EMV Mode’

And Offline Data Authentication is supported (implementation and
acquirer option)
And the AIP (Tag ‘82’) indicates that CDA is supported (Byte 1 bit 1
is ‘1’)
And any of the following Data Elements is absent from the card:
• Certification Authority Public Key Index (Tag ‘8F’)
• Issuer Public Key Certificate (Tag ‘90’)
• Issuer Public Key Exponent (Tag ‘9F32’)
• Issuer Public Key Remainder (Tag ‘92’), when required (based
on the sizes of tags ‘9F46’ and ‘90’, when both are present)
• ICC Public Key Certificate (Tag ‘9F46’)
• ICC Public Key Exponent (Tag ‘9F47’)
• ICC Public Key Remainder (Tag ‘9F48’), when required (based
on the ICC Public Key Length and the size of tag ‘9F46’, when
both are present)
Then the Kernel shall set TVR Byte 1 bit 6 (‘ICC Data Missing’) and
Byte 1 bit 3 (‘CDA Failed’) to ‘1’. (except for when Issuer Public Key
Remainder (Tag ‘92’) and ICC Public Key Remainder (Tag ‘9F48’)
are not required.)4

3.4.1.4 If the Transaction Mode is ‘EMV Mode’

And Offline Data Authentication is supported (implementation and
acquirer option)
And the Certification Authority Public Key corresponding to the
CAPK index (Tag ‘8F’) provided by the card is not present in the
Kernel configuration data,
Then the Kernel shall set TVR Byte 1 bit 3 (‘CDA Failed’) to ‘1’.
(Note: the kernel recovers the ICC public key later during the
transaction to optimise the performance.)

4
If the kernel perf orms the validation of certificates during CDA Signature verification, it is not
mandatory to check the absence of data elements and to set the TVR value described in the
requirement 3.4.1.3

March 2021 Page 26

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.5 Terminal Risk Management

3.5 Terminal Risk Management

Terminal Risk Management consists of verifications that compare the transaction
amount with reader based limits, and take appropriate action if the limit is exceeded.
The Acquirer's Exception List may also be checked.
Terminal Risk Management is mandatory and always performed.

3.5.1 Contactless Limit Check

Requirement – Contactless Limit Check

3.5.1.1 If the Transaction Mode is ‘Legacy Mode’

And the Contactless Transaction Limit is present
And the value of Amount, Authorised (Numeric) (Tag ‘9F02’) is
greater than or equal to this limit,
Then the Kernel shall terminate the transaction and provide a
Select Next Outcome as described in Section 3.12.10.

3.5.2 CVM Required Limit Check

Requirement – CVM Required Limit Check

3.5.2.1 If the CVM Required Limit is present

And the Transaction Type corresponds to a Purchase or Cash-
Advance transaction (i.e. value is ‘00’, ‘01’ or ‘09’)
And the value of Amount, Authorised (Numeric) (Tag ‘9F02’) is
greater than or equal to this limit,
Then the Kernel shall indicate ‘CVM Required by Reader’ (Byte 1,
bit 8) in the dynamic Terminal Interchange Profile (Tag ‘9F53’).

March 2021 Page 27

3.5.3 Floor Limit Check

Requirement – Floor Limit Check

3.5.3.1 If any of the conditions below is true:

• The Transaction Mode is ‘Legacy Mode’
• The Terminal Type (Tag ‘9F35’) indicates that the reader is
online-only (value = ‘x1’ or ‘x4’)
• The Amount, Authorised is a single unit of currency 5 and the
Combination Options Byte 1 Bit 7 is set to 1b (‘Status Check
Supported’)
Then the Kernel shall set TVR Byte 4 bit 8 (‘Transaction exceeds
Floor Limit’) to ‘1’.

3.5.3.2 If the Transaction Mode is ‘EMV Mode’

And the Contactless Floor Limit is present
And the value of Amount, Authorised (Numeric) (Tag ‘9F02’) is
greater than or equal to this limit,
Then the Kernel shall set TVR Byte 4 bit 8 (‘Transaction exceeds
Floor Limit’) to ‘1’.

3.5.4 Random Transaction Selection

Requirement – Random Transaction Selection

3.5.4.1 If the Transaction Mode is ‘EMV Mode’

And the Combination Options indicate that ‘Random Transaction
Selection supported’
And the TVR Byte 4 bit 8 has value ‘0’ (Floor Limit not exceeded),
Then the Kernel shall perform Random Transaction Selection as
described in [EMV Book 3].

5
The Amount corresponding to a single unit of currency is obtained as 10Transaction Currency
Exponent
. E.g. for USD, where Transaction Currency Exponent = 2, a single unit of currency
(1.00 USD) is coded as ‘000000000100’.
The Transaction Currency Exponent is a Kernel configuration parameter.

March 2021 Page 28

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.5 Terminal Risk Management

Requirement – Random Transaction Selection

3.5.4.2 If the transaction is randomly selected for online authorisation,

Then the Kernel shall set TVR Byte 4 bit 5 (‘Transaction selected
randomly for online processing’) to ‘1’.

3.5.5 Exception File Check

Exception file check is both an Implementation Option as well as an Acquirer Option.

When applicable, the exact implementation of this check is left at the discretion of the
implementer. It may, for instance, take advantage of the Data Exchange mechanism
described in Book A.

Requirement – Exception File Check

3.5.5.1 If all the conditions below are true:

• the Transaction Mode is ‘EMV Mode’
• Exception File Check is supported (Implementation Option)
• the Combination Options (Acquirer Options) indicate that
‘Exception File Check required’
Then the Kernel shall perform Exception File Check as described in
[EMV Book 4].

3.5.5.2 If the card number (PAN) has been found in the Exception File,
Then the Kernel shall set TVR Byte 1 bit 5 (‘Card appears on
terminal exception file’) to ‘1’.

March 2021 Page 29

3.6 Processing Restrictions

3.6.1 Application Usage Control Check

Requirement – Application Usage Control

3.6.1.1 If the Transaction Mode is ‘EMV Mode’

And the Application Usage Control (Tag ‘9F07’) has been provided
by the card,
Then the Kernel shall perform Application Usage Control as
described in [EMV Book 3].

3.6.1.2 If the result from Application Usage Control Check indicates that
the transaction is not allowed,
Then the Kernel shall set TVR Byte 2 bit 5 (‘Requested Service Not
Allowed for Card Product’) to ‘1’.

3.6.2 Application Expiration Date Check

Requirement – Application Expiration Date

3.6.2.1 The Kernel shall perform Application Expiration Date Check as

described in [EMV Book 3].

3.6.2.2 If the card application has expired,

Then the Kernel shall set TVR Byte 2 bit 7 (‘Expired Application’) to
‘1’.

March 2021 Page 30

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.6 Processing Restrictions

3.6.3 Application Effective Date Check

Requirement – Application Effective Date

3.6.3.1 If the Application Effective Date (Tag ‘5F25’) has been provided by
the card,
Then the Kernel shall perform Application Effective Date Check as
described in [EMV Book 3].

3.6.3.2 If the card application is not yet effective,

Then the Kernel shall set TVR Byte 2 bit 6 (‘Application Not Yet
Effective’) to ‘1’.

March 2021 Page 31

3.7 Terminal Action Analysis

Requirement – Terminal Action Analysis

3.7.1.1 If the Transaction Type indicates a Refund (‘20’),

Then the Kernel shall decline the transaction (i.e. Terminal Action
Analysis results in decline) and continue with Requirement 3.7.1.7
(“Terminal Action Analysis Completion”).

3.7.1.2 If Transaction Mode is ‘Legacy Mode’

And TIP indicates that Reader is a Transit Reader (Byte 1 bit 3 is
‘1’),
Then the Kernel shall decline the transaction as defined in section
3.12.5.

3.7.1.3 If TIP indicates that Reader is a Transit Reader (Byte 1 bit 3 is ‘1’)
And Exception File Check is supported (implementation and
acquirer option)
And “Card appears on terminal exception file” in TVR is set (Byte 1
bit 5 is ‘1’),
Then the Kernel shall decline the transaction as defined in section
3.12.5.

3.7.1.4 Issuer Action Code (IAC) Values:

If the Transaction Mode is ‘EMV Mode’,
Then the Kernel shall use the Issuer Action Code values provided
by the card for Terminal Action Analysis.
Otherwise for ‘Legacy Mode’ or no IAC values are provided by
card, the Kernel shall use the following default IAC values:
• IAC-Denial: 00 00 00 00 00
• IAC-Online: FF FF FF FF FF
• IAC-Default: FF FF FF FF FF

March 2021 Page 32

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.7 Terminal Action Analysis

Requirement – Terminal Action Analysis

3.7.1.5 Terminal Action Code (TAC) Values:

If Terminal Action Code values (Decline, Online, Default) are
parameterised as part of the Kernel configuration data,
Then the Kernel shall use the parameterised Terminal Action Code
values.

Otherwise the Kernel shall use the default TAC values as defined in
Annex D, Table D-1.

3.7.1.6 Terminal Action Analysis

The Kernel shall perform Terminal Action Analysis as described in
[EMV Book 3], using:
• Terminal Verification Results (TVR)
• TAC/IAC-Denial
• TAC/IAC-Online: If the Terminal Type (Tag ‘9F35’) indicates
that the reader is online-capable (‘x1’, ‘x2’, ‘x4’ or ‘x5’).
• TAC/IAC-Default: If the Terminal Type (Tag ‘9F35’) indicates
that the reader is offline-only (‘x3’ or ‘x6’).

Requirement – Terminal Action Analysis Completion

3.7.1.7 If the result of the Terminal Action Analysis is to decline the

transaction,
Then the Kernel shall decline the transaction as described in
Section 3.12.5.
Otherwise the Kernel shall proceed to completion as described in:
• Section 3.8 if Transaction Mode is ‘EMV Mode’
• Section 3.9 if Transaction Mode is ‘Legacy Mode’

March 2021 Page 33

3.8 Completion – EMV Mode

When the transaction is processed in ‘EMV Mode’, the Kernel will request the card to
generate a cryptogram corresponding to the decision taken during Terminal Action
Analysis, by issuing a GENERATE AC command. A CDA signature is systematically
requested if Offline Data Authentication is supported by the Kernel (implementation
and acquirer option).
If the CDA signature is valid, the Kernel will apply the decision of the card with
regards to the transaction outcome and the CVM to be performed.

3.8.1 GENERATE AC Command

The CDOL1 used to prepare the GENERATE AC command is obtained during READ
RECORD processing.

Requirement – CDOL1 Processing

3.8.1.1 The Kernel shall process the CDOL1 and construct the command
data for the GENERATE AC command, as described in
[EMV Book 3].

3.8.1.2 If the CDOL1 requests a Data Object that is not recognised by the
Kernel (not referenced in Annex B),
Then the Kernel shall fill in the corresponding CDOL1 related data
with zeroes.

Requirement – GENERATE AC

3.8.1.3 The Kernel shall request the card to generate a cryptogram using
the GENERATE APPLICATION CRYPTOGRAM command as defined
in Section 4.2 and [EMV Book 3]. 6
The type of cryptogram (TC or ARQC) requested by the Kernel in
the Reference Control Parameter (parameter P1) shall correspond
to the result of the Terminal Action Analysis.

6
The Kernel shall not change TVR af ter requesting GENERATE APPLICATION
CRYPTOGRAM command and before providing the first Outcome.

March 2021 Page 34

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.8 Completion – EMV Mode

Requirement – GENERATE AC

3.8.1.4 If Offline Data Authentication is supported (implementation and

acquirer option)
And the AIP (Tag ‘82’) indicates that CDA is supported (Byte 1bit 1
is ‘1’),
Then the Kernel shall request a CDA Signature in the Reference
Control Parameter (bit 5 is set to ‘1’).

At this stage the Kernel needs to analyse the GENERATE AC response.

Requirement – GENERATE AC Response Analysis

3.8.1.5 If the Status Word returned by the card is equal to ‘6986’,

Then the Kernel shall terminate the transaction with an End
Application (with restart, On-device CVM) Outcome as defined in
section 3.12.9.
This Status Word indicates that the CVM shall be performed on the
cardholder device prior to attempting the transaction (e.g. a
Confirmation Code shall be entered on the mobile device).

3.8.1.6 If the Status Word returned by the card is equal to ‘6984’,

Then the Kernel shall terminate the transaction with a Try Another
Interface Outcome as defined in section 3.12.6.
This Status Word indicates that the card is a dual-interface card
that prefers to conduct the transaction using the contact interface.

3.8.1.7 If the Status Word returned by the card is different from ‘6984’,
‘6986’ and ‘9000’,
Then the Kernel shall terminate the transaction with a Select Next
Outcome as defined in section 3.12.10.

March 2021 Page 35

Requirement – GENERATE AC Response Analysis

3.8.1.8 The Kernel shall parse the response to the GENERATE AC and
ensure that it is correctly formatted and that the card has provided
all mandatory data elements. The mandatory data elements
depend on the transaction context. They are listed in Table 4-,
Table 4- and Table 4-.
If the response to the GENERATE AC command is not parsed
correctly
Or if a mandatory data element is missing
Or if the format of a returned data element is incorrect,
Then the Kernel shall decline the transaction as defined in
section 3.12.5.

3.8.1.9 If the Cryptogram Information Data (Tag ‘9F27’) indicates an AAC,

Then the Kernel shall decline the transaction as defined in
section 3.12.5.

3.8.1.10 If the Cryptogram Information Data (Tag ‘9F27’) indicates a TC

And the Signed Dynamic Application Data (Tag ‘9F4B’) is absent
from the card response,
Then the Kernel shall decline the transaction as defined in section
3.12.5.

3.8.1.11 The Kernel shall analyse the type of cryptogram returned from the
card for consistency with the requested type of cryptogram.

If the Kernel requested ARQC, but the CID indicates a TC,

Then the Kernel shall decline the transaction as defined in section
3.12.5.

3.8.1.12 If Offline Data Authentication is supported (implementation and

acquirer option)
And the AIP (Tag ‘82’) indicates that CDA is supported (Byte 1bit 1
is ‘1’)
And the Signed Dynamic Application Data (Tag ‘9F4B’) is absent
from the card response,
Then the Kernel shall decline the transaction as defined in
section 3.12.5.

March 2021 Page 36

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.8 Completion – EMV Mode

Once the response has been received, if the card is no longer required in the field
and if CDA verification is to be performed, the indication is given to the cardholder
that the card can be removed.

Requirement – Card Removal

3.8.1.13 If Signed Dynamic Application Data (Tag ‘9F4B’) is present in the

card response,
And one of the following conditions is True:
• the Issuer Update Parameter (Tag ‘9F60’) is absent from the
card response
• the Issuer Update Parameter (Tag ‘9F60’) has a value = ‘02’
(“Second Presentment”)
• the Issuer Update Parameter (Tag ‘9F60’) has a value = ‘00’
(Issuer Update is not expected, card can be removed)
• Issuer Update is not supported by the Kernel
(implementation and acquirer option)
Then the Kernel shall send a User Interface Request with the
following parameters:
• Message Identifier: ‘17’ (“Card Read OK”)
• Status: Card Read Successfully
This will result in an indication to the cardholder that the card can
be removed from the field.

3.8.2 Offline Data Authentication

The Kernel verifies the CDA signature returned in the GENERATE AC response and
determines the Outcome and the associated parameters. Verification of the signature
includes recovery of the Issuer and card public keys from the certificates contained in
the data records.

March 2021 Page 37

Requirement – CDA Signature Verification

3.8.2.1 If the card has returned a Signed Dynamic Application Data (Tag
‘9F4B’),
Then the Kernel shall verify the signature as defined for CDA in
[EMV Book 2] and [EMV Book 3], including the retrieval of ICC
Public Key.
If any step of signature verification fails,
Then the Kernel shall decline the transaction as defined in
section 3.12.5.

3.8.3 CVM Processing

When Transaction Mode is ‘EMV Mode’, the Kernel is required to check the
consistency of the CVM decision (“Cardholder Verification Status”) that has been
provided by the card with the GENERATE AC response, and to apply this decision.
This Cardholder Verif ication Status, authenticated by the CDA signature, is computed
by the card based on its internal card risk management parameters, and based on
the transaction context as communicated by the Kernel in the CDOL1 related data.

Requirement – CVM Evaluation

3.8.3.1 The Kernel shall examine the Cardholder Verification Status (Tag
‘9F50’) returned by the card in the GENERATE AC response to
determine the card CVM requirement for the transaction:
• ‘00’: No CVM
• ‘10’: Obtain Signature
• ‘20’: Online PIN
• ‘3x’: On-Device CVM Selected
• Other: Not Applicable (no CVM preference)

March 2021 Page 38

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.8 Completion – EMV Mode

Requirement – CVM Consistency Check

3.8.3.2 If the Cardholder Verification Status indicates other than '00', ‘10’,
‘20’ or ‘3x’,
Then the Kernel shall decline the transaction as defined in
section 3.12.5.

3.8.3.3 If the Terminal Interchange Profile (dynamic) indicates ‘CVM

Required by Reader’ (byte 1 bit 8 = ‘1’)
And the Terminal Interchange Profile (dynamic) does not indicate
‘Reader is a Transit Reader’ (byte 1 bit 3 = ‘0’)
And the Cardholder Verification Status indicates ‘00’,
Then the Kernel shall decline the transaction as defined in
section 3.12.5.

3.8.3.4 If the Cardholder Verification Status has any value among ‘10’, ‘20’
or ‘3x’ (Signature, Online PIN, or On-Device CVM)
And the Terminal Interchange Profile (dynamic) does not indicate
‘Reader is a Transit Reader’ (byte 1 bit 3 = ‘0’)
And the corresponding CVM is not supported in the Terminal
Interchange Profile (dynamic),
Then the Kernel shall decline the transaction as defined in
section 3.12.5.

March 2021 Page 39

Requirement – On-Device CVM Contactless Transaction Limit and

Contactless Limit Check

3.8.3.5 If the Cardholder Verification Status indicates ‘3x’

And the On-Device CVM Contactless Transaction Limit is present
And the value of Amount, Authorised (Numeric) (Tag ‘9F02’) is
greater than or equal to this limit,
Then the Kernel shall terminate the transaction and provide a
Select Next Outcome as described in Section 3.12.10.

3.8.3.6 If the Cardholder Verification Status indicates other than ‘3x’

Then
If the Contactless Transaction Limit is present
Then
If the value of Amount, Authorised (Numeric) (Tag ‘9F02’)
is greater than or equal to this limit,
Then the Kernel shall terminate the transaction and
provide a Select Next Outcome as described in Section
3.12.10.
Else
If the On-Device CVM Contactless Transaction Limit is
present
And the value of Amount, Authorised (Numeric) (Tag
‘9F02’) is greater than or equal to the On-Device CVM
Contactless Transaction Limit,
Then the Kernel shall terminate the transaction and
provide a Select Next Outcome as described in Section
3.12.10

3.8.4 Transaction Outcome

The Outcome is set for Approved or Online Request, as per the card decision, with
the parameters indicating the CVM requirement (if any). The data elements for an
EMV clearing record or an online authorisation are made available to the reader.

March 2021 Page 40

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.8 Completion – EMV Mode

Requirement – Decision of Transaction Outcome

3.8.4.1 If the Cryptogram Information Data (Tag ‘9F27’) indicates a TC,

Then the Kernel shall decide the Outcome to Approved Outcome
as defined in section 3.12.1.

3.8.4.2 If the Cryptogram Information Data (Tag ‘9F27’) indicates an

ARQC,
And any of the conditions below is true:
• the Issuer Update Parameter (Tag ‘9F60’) is absent from the
card response
Or has value = ‘00’
• Issuer Update is not supported by the Kernel
(implementation and acquirer option)
Then the Kernel shall decide the Outcome to Online Request
Outcome as defined in section 3.12.2.

3.8.4.3 If the Cryptogram Information Data (Tag ‘9F27’) indicates an ARQC

And Issuer Update is supported (implementation and acquirer
option)
And the Issuer Update Parameter (Tag ‘9F60’) is present with
value ‘01’,
Then the Kernel shall decide the Outcome to Online Request
Outcome (“Present and Hold”) as defined in section 3.12.4.

3.8.4.4 If the Cryptogram Information Data (Tag ‘9F27’) indicates an ARQC

And Issuer Update is supported (implementation and acquirer
option)
And the Issuer Update Parameter (Tag ‘9F60’) is present with
value ‘02’,
Then the Kernel shall decide the Outcome to Online Request
Outcome (“Two Presentments”) as defined in section 3.12.3.

March 2021 Page 41

Requirement – Setting of Outcome Parameters

3.8.4.5 If the Terminal Interchange Profile (dynamic) indicates ‘Reader is a

Transit Reader’ (byte 1 bit 3 = ‘1’),
Then the CVM parameter in the Approved or Online Request
Outcome and CVM Results (Tag ‘9F34’) shall be set to “No CVM”.
Else the CVM parameter in the Approved or Online Request
Outcome and CVM Results (Tag ‘9F34’) shall be set to the result of
CVM Processing as specified in section 3.8.3.

3.8.4.6 The Message Identifier parameter in the Approved or Online

Request Outcome (UI Request on Outcome Present) shall take the
following value:
If the Outcome is an Approved Outcome,
Then
If CVM = Obtain Signature,
Then Message Identifier = ‘1A’ (“Approved, please sign”)
Else Message Identifier = ‘03’ (“Approved”)
Else (the Outcome is an Online Request Outcome)
If CVM = Online PIN,
Then Message Identifier = ‘09’ (“Please enter your PIN”)
Else Message Identifier = ‘1B’ (“Authorising, please wait”)
3.8.4.7 If the Outcome is an Online Request Outcome (“Present and
Hold”) or Online Request Outcome (“Two Presentments”) as per
Requirement 3.8.4.3 or 3.8.4.4,
Then the following information shall be retained as the Online
Transaction Context (for subsequent Kernel activation to perform
Issuer Update Processing):
• Transaction Record provided as part of the outcome (see
Annex C)
• CVM Parameter provided as part of the outcome
• CDOL2 data element (when provided by the card)

Requirement – Providing of Transaction Outcome

3.8.4.8 The Kernel shall provide the Outcome and Outcome Parameters.

March 2021 Page 42

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.9 Completion – Legacy Mode

3.9 Completion – Legacy Mode

If the transaction is to be processed as per ‘Legacy Mode’, the Kernel will req uest the
card to return an Authorisation Request Cryptogram (ARQC) by sending a
GENERATE AC command with the data requested in the CDOL1 obtained during
READ RECORD processing. No CDA signature is required.
Completion of online processing will normally occur after the card is no longer
required in the field.

3.9.1 GENERATE AC Command

The CDOL1 used to prepare the GENERATE AC command is obtained during READ
RECORD processing.

Requirement – CDOL1 Processing

3.9.1.1 The Kernel shall process the CDOL1 and construct the command
data for the GENERATE AC command, as described in
[EMV Book 3].

3.9.1.2 If the CDOL1 requests a data element that is not recognised by the
Kernel (i.e. not referenced in Annex B),
Then the Kernel shall fill in the corresponding CDOL1 related data
with zeroes.

Requirement – GENERATE AC

3.9.1.3 The Kernel shall request the card to generate an ARQC using the
GENERATE APPLICATION CRYPTOGRAM command and shall obtain
the response as defined in [EMV Book 3].

3.9.1.4 The kernel shall not change TVR after requesting GENERATE
APPLICATION CRYPTOGRAM command and before providing the
first Outcome.

3.9.1.5 If the Status Word returned by the card is different from ‘9000’,
Then the Kernel shall terminate the transaction with a Select Next
Outcome as defined in section 3.12.10.

March 2021 Page 43

Requirement – GENERATE AC

3.9.1.6 The Kernel shall ensure that the card response is correctly
formatted (see section 4.2).
If the response to the GENERATE AC command is not parsed
correctly
Or a mandatory data element is missing
Or the format of a returned data element is incorrect,
Then the Kernel shall decline the transaction as defined in
section 3.12.5.

3.9.1.7 If the Cryptogram Information Data (Tag ‘9F27’) does not indicate
an ARQC,
Then the terminal shall decline the transaction as defined in
section 3.12.5.

The Kernel evaluates the need for CVM processing and determines the Outcome
and associated parameters. The data for an online authorisation is prepared and
made available to the POS system.

3.9.2 CVM Processing

If a CVM is required according to the result of CVM Required Limit Check, the Kernel
evaluates the CVM list contained in the data records and determines the appropriate
CVM parameter setting for the Outcome. Kernel 5 CVM processing is a simplified
version of CVM list processing defined in [EMV Book 3] using only the CVM Code.
The CVM Condition byte is not evaluated.

Requirement – CVM Required Check

3.9.2.1 If the ‘CVM required by reader’ indicator is set to 1 in the dynamic

Terminal Interchange Profile (Tag ‘9F53’),
Then the Kernel shall evaluate the CVM List obtained from the
data records.
Otherwise processing shall continue with Online Request
Outcome (section 3.9.3), with CVM parameter set to “No CVM”.

March 2021 Page 44

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.9 Completion – Legacy Mode

Requirement – CVM Evaluation

3.9.2.2 If the CVM List is absent from the card,

Then the Kernel shall assume the CVM to be Not Applicable (no
CVM preference) and the Kernel shall decline the transaction as
defined in section 3.12.5.

3.9.2.3 If the CVM List is provided by the card,

Then the Kernel shall examine the CVM Codes in the CVM List
(Tag ‘8E’) in sequential order, comparing the static Terminal
Interchange Profile flags (‘Signature supported’ and ‘Online PIN
supported’) with the CVM Code values for ‘Enciphered PIN verified
online’ and ‘Signature (paper)’, as defined in [EMV Book 3],
Table 39.

The first positive comparison7 in the list shall determine the CVM
requirement for the transaction.

3.9.2.4 If no match is found after processing requirement 3.9.2.3,

Then the Kernel shall decline the transaction as defined in
section 3.12.5.

3.9.3 Online Request Outcome

The Outcome is set for Online Request with the parameters indicating the CVM
requirement (if any). The data elements for an EMV online authorisation are made
available to the Reader.

Requirement – Decision of Online Request Outcome

3.9.3.1 The Kernel shall decide the Outcome to Online Request Outcome
as defined in section 3.12.2.

7
It ref ers to the first matching CVM supported by both terminal and card. CV Rule Byte1bit7
is not evaluated.

March 2021 Page 45

Requirement – CVM Consistency Check

3.9.3.2 The CVM parameter in the Online Request Outcome and CVM
Results (Tag ‘9F34’) shall be the result of CVM Processing as
specified in section 3.9.2.
3.9.3.3 The Message Identifier parameter in the Online Request Outcome
(UI Request on Outcome Present) shall take the following value:
If CVM = Online PIN,
Then Message Identifier = ‘09’ (“Please enter your PIN”)
Else Message Identifier = ‘1B’ (“Authorising, please wait”)

Requirement – Providing of Transaction Outcome

3.9.3.4 The Kernel shall provide the Outcome and Outcome Parameters.

March 2021 Page 46

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.10 Issuer Update Processing

3.10 Issuer Update Processing

Issuer Update enables the Issuer to take advantage of a transaction authorisation
message to perform remote maintenance operations on the card – typically Issuer
Authentication enabling counter reset, or Issuer Scripts enabling updating card
parameters.
The card shall either be maintained in the RF field for the duration of the
authorisation request, or be represented to the reader when the online response is
received.
This section is performed when the Kernel is restarted after an Online Authorisation
to execute Issuer Update, provided that all the conditions below are fulfilled:
• The Kernel supports Issuer Update (implementation option) .
• The selected Combination supports Issuer Update (acquirer option) .
• The card has returned an ARQC in answer to the first GENERATE AC
command, with an Issuer Update Parameter requesting “Present-and-hold”
(‘01’) or “Two Presentment” (‘02’) behaviour.
• The Authorisation Response message contains Issuer Authentication Data
(Tag ‘91’) and/or Issuer Script(s) (Templates ‘71’ and/or ‘72’).
When activated again to process Issuer Update, the Kernel restores the Online
Transaction Context for the ongoing transaction that was retained before the online
authorisation request.

3.10.1 Issuer Update Initialisation

Requirement – SELECT response analysis

3.10.1.1 If the Terminal Interchange Profile (dynamic) indicates ‘Issuer

Update Supported’ (byte 2 bit 8 = ‘1’),
Then the kernel shall continue with the requirement 3.10.1.2.
Otherwise the kernel shall provide an End Application Outcome as
defined in Section 3.12.7

3.10.1.2 If the FCI has been provided by the reader with the Dynamic
Transaction Parameters (case of “Two Presentment”)
And the FCI is not parsed correctly (see table 45 in [EMV Book 1]),
Then the Kernel shall complete the transaction by returning an
End Application Outcome as defined in Section 3.12.7.

March 2021 Page 47

3.10.2 Critical Script Processing

This requirement is performed when the Dynamic Transaction Parameters provided
to the Kernel (see Table 3-2) contain at least one occurrence of Issuer Script
Template 1 (Tag ‘71’):

Requirement – Critical Script Processing

3.10.2.1 The Kernel shall process each occurrence of Issuer Script Template
‘71’ sequencially, in the order provided by the terminal as part of
the Dynamic Transaction Parameters. Each occurrence is
processed as follows:
• The Kernel shall ensure that the Issuer Script Template can
be parsed correctly, according to the format described in
[EMV Book 3], Section 10.10.
If the parsing is incorrect,
Then the Kernel shall:
o set TVR8 Byte 5 bit 6 to ‘1’ (‘Script processing failed
before final GENERATE AC’),
o proceed with the next ‘71’ tag occurrence, if any.
• The Kernel shall deliver each command to the card as a
command APDU in the sequence in which it appears in the
Issuer Script.
If the card returns an error SW to any script command (SW1
≠ ‘90’, ‘62’ and ‘63’),
Then the Kernel shall:
o terminate the delivery of commands from this Issuer
Script,
o set TVR Byte 5, bit 6 to ‘1’ (‘Script processing failed
before final GENERATE AC’),
o proceed with the next ‘71’ tag occurrence, if any.

8
TVR is restored from Online Transaction Context and updated.

March 2021 Page 48

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.10 Issuer Update Processing

Note: the processing of Issuer Script is identical to the processing described for
contact EMV kernels in [EMV], except that the Kernel does not generate the
Transaction Status Information (TSI) nor Issuer Script Results. In particular, the
following sections apply:
- [EMV Book 3], Sections 10.10 and Annex E
- [EMV Book 4], Sections 6.3.9 and 12.2.4

Requirement – Critical Script Processing Completion

3.10.2.2 Once all occurrences of Issuer Script Template ‘71’ have been
processed:
If the Dynamic Transaction Parameters provide neither Issuer
Authentication Data (Tag ‘91’) nor Issuer Script Template 2 (Tag
‘72’),
Then the Kernel shall complete the transaction by returning an
End Application Outcome as defined in Section 3.12.7.
Else the Kernel proceeds with Section 3.10.3.

Note: when the reader receives from the Kernel an End Application outcome
following an Online restart, the terminal determines the transaction disposition
according to the Authorisation Response Code provided by the Issuer (see Book A,
Table 6-4 for the processing of the End Application outcome following an Online
Request).

3.10.3 Second GENERATE AC Command

The requirements in this section are executed if Issuer Authentication Data ( Tag ‘91’)
or at least one occurrence of Issuer Script Template 2 (Tag ‘72’) is/are made
available to the Kernel upon restart.

March 2021 Page 49

Requirement – CDOL2 Processing

3.10.3.1 The Kernel shall retrieve the CDOL2 value from the Online
Transaction Context saved during the first part of the transaction.
If the CDOL2 is absent from the Online Transaction Context (i.e.
the card has not provided any CDOL2 value),
Then the Kernel shall return an End Application Outcome as
described in Section 3.12.7.

3.10.3.2 The Kernel shall process the CDOL2 and construct the command
data for the GENERATE AC command, as described in
[EMV Book 3].

3.10.3.3 If the CDOL2 requests a Data Object that is not recognised by the
Kernel (not referenced in Annex B),
Then the Kernel shall fill in the corresponding CDOL2 related data
with zeroes.

Requirement – GENERATE AC

3.10.3.4 The Kernel shall request the card to generate a cryptogram using
the GENERATE APPLICATION CRYPTOGRAM command as defined
in Section 4.3 and [EMV Book 3].
The type of cryptogram (TC or AAC) requested by the Kernel in the
Reference Control Parameter (parameter P1) depends on the
Authorisation Response Code (ARC, Tag ‘8A’) provided by the
reader:
If the ARC value corresponds to an Approval (“00”, “10”, “11”)
or a Referral (“01”, “02”),
Then an approval (TC) shall be requested;
Else a decline (AAC) shall be requested.

3.10.3.5 The Kernel shall not request any CDA Signature in the Reference
Control Parameter (bit 5 is set to ‘0’).

March 2021 Page 50

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.10 Issuer Update Processing

At this stage the Kernel needs to analyse the GENERATE AC response.

Requirement – GENERATE AC Response Analysis

3.10.3.6 If the Status Word returned by the card is different from ‘9000’,
Then the Kernel shall return an End Application Outcome as
described in Section 3.12.7.

3.10.3.7 If the response to the GENERATE AC command is not parsed

correctly
Or a mandatory data element is missing (see Table 4-3)
Or the format of a returned data element is incorrect,
Then the Kernel shall return an End Application Outcome as
defined in section 3.12.7.

3.10.3.8 If the Cryptogram Information Data (Tag ‘9F27’) indicates other

than AAC or TC,
Then the Kernel shall decline the transaction as defined in section
3.12.5.

3.10.3.9 If the Kernel requested AAC, but the CID indicates a TC,
Then the Kernel shall decline the transaction as defined in section
3.12.5.

3.10.4 Transaction Outcome

The Outcome is set for Approved or Declined, as per the card decision to the
second GENERATE AC command, with the parameters indicating the CVM
requirement (if any). The data elements for an EMV clearing record are made
available to the reader.

Requirement – Transaction Outcome

3.10.4.1 If the Cryptogram Information Data (Tag ‘9F27’) returned to the

second GENERATE AC indicates an AAC,
Then the Kernel shall prepare a Declined Outcome as defined in
section 3.12.5.

March 2021 Page 51

Requirement – Transaction Outcome

3.10.4.2 If the Cryptogram Information Data (Tag ‘9F27’) returned to the

second GENERATE AC indicates a TC,
Then the Kernel shall prepare an Approved Outcome as defined in
section 3.12.1.

3.10.4.3 The Kernel shall retrieve the CVM parameter from the Online
Transaction Context.
If the value retrieved is equal to Online PIN,
Then the CVM parameter in the Approved Outcome shall be set to
Not Applicable.
Else the CVM parameter in the Approved Outcome is equal to the
value in the Online Transaction Context.

3.10.4.4 The Message Identifier parameter in the Approved Outcome (UI

Request on Outcome Present) shall take the following value:
If CVM = Obtain Signature,
Then Message Identifier = ‘1A’ (“Approved, please sign”)
Else Message Identifier = ‘03’ (“Approved”)

3.10.4.5 The Transaction Record (see Annex C) provided with the Approved
Outcome is populated as follows:
• Cryptogram Information Data (Tag ‘9F27’), ATC (Tag ‘9F36’),
Application Cryptogram, Issuer Application Data (Tag ‘9F10’)
are the values returned by the card to the second
GENERATE AC command.
• TVR (Tag ‘95’) is the value updated during Issuer Update
Processing.
• Other data elements are recovered from the Online
Transaction Context.

3.10.4.6 If the Dynamic Transaction Parameters provide at least one

occurrence of Issuer Script Template 2 (Tag ‘72’),
Then the Kernel shall proceed with Section 3.10.5
Else the Kernel shall return the prepared Transaction Outcome.

March 2021 Page 52

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.10 Issuer Update Processing

3.10.5 Non-critical Script Processing

The Requirement below is executed when the Dynamic Transaction Parameters
provided to the Kernel (see Table 3-2) for restart contain at least one occurrence of
Issuer Script Template 2 (Tag ‘72’):

Requirement – Non-critical Script Processing

3.10.5.1 The Kernel shall process each occurrence of Issuer Script Template
‘72’ sequencially, in the order provided by the terminal as part of
the Dynamic Transaction Parameters. Each occurrence is
processed as follows:
• The Kernel shall ensure that the Issuer Script Template can
be parsed correctly, according to the format described in
[EMV Book 3], Section 10.10.
If the parsing is incorrect,
Then the Kernel shall:
o update TVR Byte 5 bit 5 to ‘1’ (‘Script processing
failed after final GENERATE AC’) in the Transaction
Outcome
o proceed with the next ‘72’ tag occurrence, if any.
• The Kernel shall deliver each command to the card as a
command APDU in the sequence in which it appears in the
Issuer Script.
If the card returns an error SW to any script command (SW1
≠ ‘90’, ‘62’ and ‘63’),
Then the Kernel shall:
o terminate the delivery of commands from this Issuer
Script,
o update TVR Byte 5, bit 5 to ‘1’ (‘Script processing
failed after final GENERATE AC’) in the Transaction
Outcome
o proceed with the next ‘72’ tag occurrence, if any.

March 2021 Page 53

Requirement – Non-critical Script Processing Completion

3.10.5.2 Once all occurrences of Issuer Script Template ‘72’ have been
processed, the Kernel shall complete the transaction by returning
the Transaction Outcome prepared in Section 3.10.4.

March 2021 Page 54

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.11 Error Handling

3.11 Error Handling

3.11.1 Processing Errors

Unless otherwise specified in the relevant transaction paragraph above, the
requirements in this section apply.
Processing errors for Completion (all modes) and Issuer Update are subject to
specific processing; please refer to the relevant sections (3.8 to 3.10).

Requirement – Processing Errors - Default

3.11.1.1 If the status bytes returned in the response to any command are
different from ‘9000’ or other acceptable values as defined in
section 4,
Then the Kernel shall terminate the transaction and provide a
Select Next Outcome as defined in section 3.12.10.

3.11.1.2 If the response to a command is not parsed correctly as defined

for the command in section 4
Or a mandatory data element is missing
Or the format of a returned data element is incorrect,
Then the Kernel shall terminate the transaction and provide a
Select Next Outcome as defined in section 3.12.10.

This rule includes (but is not limited to) the data format errors
listed in [EMV Book 3] Section 7.5.

March 2021 Page 55

3.11.2 Communication Errors

Requirement – Communication Errors – First GENERATE AC

3.11.2.1 If a Transmission, Protocol, or Timeout error as defined in [EMV

Level1 Contactless] is reported to the Kernel during the first
GENERATE APPLICATION CRYPTOGRAM command of a transaction
in EMV Mode,
Then the Kernel shall prepare the Recovery Context as follows:
• Set indicator ‘Recovering from Torn EMV Transaction’ to
value TRUE;
• Store the card Track 2 Equivalent Data value (Tag ‘57’) into
variable ‘Torn Track 2 Data’;
• If CDA has been requested by the Kernel, concatenate in
this order and store in variable ‘Torn CDA Hash Data Buffer’
o The values of the data elements specified by, and in
the order they appear in the PDOL, and sent by the
Kernel in the GET PROCESSING OPTIONS command.
o The values of the data elements specified by, and in
the order they appear in the CDOL1, and sent by the
Kernel in the GENERATE AC command.

3.11.2.2 The Reader shall retain the Recovery Context and make it available
to the Kernel for the next Kernel Activation.

The Kernel shall terminate the transaction and provide an End

Application (with restart – Communication errors) Outcome as
described in section 3.12.8.

Requirement – Communication Errors – Issuer Updates

3.11.2.3 If a Transmission, Protocol, or Timeout error as defined in [EMV

Level1 Contactless] is reported to the kernel while executing:
• critical Issuer Script commands (see Section 3.10.2)
• the second GENERATE AC command (see Section 3.10.3)
Then the Kernel shall return an End Application Outcome as
defined in Section 3.12.7.

March 2021 Page 56

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.11 Error Handling

Requirement – Communication Errors – Issuer Updates

3.11.2.4 If a Transmission, Protocol, or Timeout error as defined in [EMV

Level1 Contactless] is reported to the Kernel while executing non-
critical Issuer Script commands (see Section 3.10.5),
Then the Kernel shall return the Transaction Outcome as
previously determined in Section 3.10.4 after the second
GENERATE AC command.

Requirement – Communication Errors – General

3.11.2.5 If a Transmission, Protocol, or Timeout error as defined in [EMV

Level1 Contactless] is reported to the Kernel,
Then the Kernel shall terminate the transaction and provide an
End Application (with restart – Communication errors) Outcome
as described in section 3.12.8.

3.11.3 Transaction Cancellation

The Kernel may receive at any time a transaction cancellation order initiated by the
Merchant (attended terminal) or by the Cardholder (unattended terminal).

Requirement – Transaction cancellation by Reader

3.11.3.1 The Kernel shall be capable of receiving a cancellation order from

the reader at any time during transaction processing.

3.11.3.2 If a cancellation order is received from the reader,

Then the Kernel shall:
• clear all internal Kernel variables
• terminate the transaction and provide an End Application
Outcome as defined in section 3.12.7.

March 2021 Page 57

3.12 Transaction Outcomes

3.12.1 Approved
Requirement – Approved Outcome

3.12.1.1 The Kernel shall make available to the POS system the data
elements necessary for an offline clearing record (cf. Annex C).

March 2021 Page 58

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.12 Transaction Outcomes

Requirement – Approved Outcome

3.12.1.2 The Kernel shall provide an Approved Outcome with the following
parameters:
Approved:
• Start: N/A
• Online Response Data: N/A
• CVM: No CVM/ Obtain Signature/Confirmation Code Verified,
as applicable
• UI Request on Outcome Present: Yes
Message Identifier: as applicable:
‘03’ (“Approved”)
‘1A’ (“Approved – Please Sign”)
Status: Card Read Successfully
[Value Qualifier: “Balance”]10
[Value: Offline Balance (Tag ‘9F5F’) returned by card ]
[Currency Code: Transaction Currency Code]
• UI Request on Restart Present: No
• Data Record Present: Yes
The minimum data requirements for ‘EMV Mode’ clearing
records are specified in Annex C.
• Discretionary Data Present: No
• Alternate Interface Preference: N/A
• Receipt: Yes
• Field Off Request: N/A
• Removal Timeout: Zero

10
Parameters in brackets [ ] are provided only if the card has returned the Offline Balance
(Tag ‘9F5F’) in the GENERATE AC response (EMV Mode only).

March 2021 Page 59

3.12.2 Online Request

Requirement – Online Request Outcome

3.12.2.1 The Kernel shall prepare the data record for an online request
record (cf. Annex C) and make it available to the POS system.

March 2021 Page 60

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.12 Transaction Outcomes

Requirement – Online Request Outcome

3.12.2.2 The Kernel shall provide an Online Request Outcome with the
following parameters:
Online Request:
• Start: N/A
• Online Response Data: N/A
• CVM: No CVM/ Obtain Signature/ Confirmation Code Verified/
Online PIN, as applicable
• UI Request on Outcome Present: Yes
Message Identifier: as applicable:
‘1B’ (“Authorising, Please Wait”)
‘09’ (“Please enter your PIN”)
Status: Card Read Successfully
[Value Qualifier: “Balance”]11
[Value: Offline Balance (Tag ‘9F5F’) returned by card]
[Currency Code: Transaction Currency Code]
• UI Request on Restart Present: No
• Data Record Present: Yes
The minimum data requirements for online authorisation
records are specified in Annex C. Data requirements depend on
the Transaction Mode.
• Discretionary Data Present: No
• Alternate Interface Preference: N/A
• Receipt: N/A
• Field Off Request: N/A
• Removal Timeout: Zero

11
Parameters in brackets [ ] are provided only if the card has returned the Offline Balance
(Tag ‘9F5F’) in the GENERATE AC response (EMV Mode only).

March 2021 Page 61

3.12.3 Online Request (“Two Presentments”)

Requirement – Online Request Outcome (“Two Presentments”)

3.12.3.1 The Kernel shall prepare the data record for an online request
record (cf. Annex C) and make it available to the POS system.

March 2021 Page 62

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.12 Transaction Outcomes

Requirement – Online Request Outcome (“Two Presentments”)

3.12.3.2 The Kernel shall provide an Online Request Outcome with the
following parameters:
Online Request:
• Start: B
• Online Response Data: EMV Data
• CVM: No CVM/ Obtain Signature/ Confirmation Code Verified/
Online PIN, as applicable
• UI Request on Outcome Present: Yes
Message Identifier: as applicable:
‘1B’ (“Authorising, Please Wait”)
‘09’ (“Please enter your PIN”)
Status: Card Read Successfully
[Value Qualifier: “Balance”]12
[Value: Offline Balance (Tag ‘9F5F’) returned by card]
[Currency Code: Transaction Currency Code]
• UI Request on Restart Present: Yes
Message Identifier: ‘21’ (“Present Card Again”)
Status: Ready to Read
• Data Record Present: Yes
The minimum data requirements for online authorisation
records are specified in Annex C. Data requirements depend on
the Transaction Mode.
• Discretionary Data Present: No
• Alternate Interface Preference: N/A
• Receipt: N/A
• Field Off Request: N/A
• Removal Timeout: Zero

12
Parameters in brackets [ ] are provided only if the card has returned the Offline Balance
(Tag ‘9F5F’) in the GENERATE AC response (EMV Mode only).

March 2021 Page 63

3.12.4 Online Request (“Present and Hold”)

Requirement – Online Request Outcome (“Present and Hold”)

3.12.4.1 The Kernel shall prepare the data record for an online request
record (cf. Annex C) and make it available to the POS system.

March 2021 Page 64

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.12 Transaction Outcomes

Requirement – Online Request Outcome (“Present and Hold”)

3.12.4.2 The Kernel shall provide an Online Request Outcome with the
following parameters:
Online Request:
• Start: D
• Online Response Data: Any
• CVM: No CVM/ Obtain Signature/ Confirmation Code Verified/
Online PIN, as applicable
• UI Request on Outcome Present: Yes
Message Identifier: as applicable:
‘1B’ (“Authorising, Please Wait”)
‘09’(“Please enter your PIN”)
Status: Processing
[Value Qualifier: “Balance”]13
[Value: Offline Balance (Tag ‘9F5F’) returned by card]
[Currency Code: Transaction Currency Code]
• UI Request on Restart Present: Yes
Message Identifier: ‘16’ (“Processing”)
Status: Processing
• Data Record Present: Yes
The minimum data requirements for online authorisation
records are specified in Annex C. Data requirements depend on
the Transaction Mode.
• Discretionary Data Present: No
• Alternate Interface Preference: N/A
• Receipt: N/A
• Field Off Request: N/A
• Removal Timeout: Removal Timeout (static Kernel
configuration parameter, see Table 3-1)

13
Parameters in brackets [ ] are provided only if the card has returned the Offline Balance
(Tag ‘9F5F’) in the GENERATE AC response (EMV Mode only).

March 2021 Page 65

3.12.5 Declined
Requirement – Declined Outcome

3.12.5.1 The Kernel shall provide a Declined Outcome with the following
parameters:
Declined:
• Start: N/A
• Online Response Data: N/A
• CVM: N/A
• UI Request on Outcome Present: Yes
Message Identifier: ‘07’ (“Not Authorised”)
Status: Card Read Successfully
[Value Qualifier: “Balance”]14
[Value: Offline Balance (Tag ‘9F5F’) returned by card ]
[Currency Code: Transaction Currency Code]
• UI Request on Restart Present: No
• Data Record Present: Yes
The minimum data requirements for records associated to a
Declined Outcome are specified in Annex C.
• Discretionary Data Present: No
• Alternate Interface Preference: N/A
• Receipt: N/A
• Field Off Request: N/A
• Removal Timeout: Zero

14
Parameters in brackets [ ] are provided only if the card has returned the Offline Balance
(Tag ‘9F5F’) in the GENERATE AC response (EMV Mode only).

March 2021 Page 66

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.12 Transaction Outcomes

3.12.6 Try Another Interface

Requirement – Try Another Interface Outcome

3.12.6.1 The Kernel shall provide a Try Another Interface Outcome with the
following parameters:
Try Another Interface:
• Start: N/A
• Online Response Data: N/A
• CVM: N/A
• UI Request on Outcome Present: Yes
Message Identifier: ‘1D’ (“Please insert card”)
Status: Ready to Read
• UI Request on Restart Present: No
• Data Record Present: No
• Discretionary Data Present: No
• Alternate Interface Preference: Contact Chip
• Receipt: N/A
• Field Off Request: N/A
• Removal Timeout: Zero

March 2021 Page 67

3.12.7 End Application

Requirement – End Application

3.12.7.1 The Kernel shall provide an End Application Outcome with the
following parameters:
End Application:
• Start: N/A
• Online Response Data: N/A
• CVM: N/A
• UI Request on Outcome Present: No
• UI Request on Restart Present: No
• Data Record Present: No
• Discretionary Data Present: No
• Alternate Interface Preference: N/A
• Receipt: N/A
• Field Off Request: N/A
• Removal Timeout: Zero

Notes:
• When this Outcome is returned as a first Final Outcome (e.g. transaction
cancellation by reader), the POS System determines the transaction
disposition as “Terminated” and advises the cardholder of the situation.
• When this Outcome is returned as a second Final Outcome (i.e. following an
Online Restart “present and hold” or “two presentments”), the POS System
determines the final transaction disposition based on the online authorisation
response from the Issuer, and indicates the final transaction disposition to the
cardholder.
See Book A, Section 6.3 for further details.

March 2021 Page 68

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.12 Transaction Outcomes

3.12.8 End Application (with restart – communication error)

Requirement – Communication Errors

3.12.8.1 If the Kernel is informed of a contactless communication error,

Then the Kernel shall provide an End Application Outcome with
the following parameters:
End Application:
• Start: B
• Online Response Data: N/A
• CVM: N/A
• UI Request on Outcome Present: Yes
Message Identifier: ‘21’ (“Present Card Again”)
Status: Processing Error
Hold Time: 13
• UI Request on Restart Present: Yes
Message Identifier: ‘21’ (“Present Card Again”)
Status: Ready to Read
• Data Record Present: No
• Discretionary Data Present: No
• Alternate Interface Preference: N/A
• Receipt: N/A
• Field Off Request: N/A
• Removal Timeout: Zero

March 2021 Page 69

3.12.9 End Application (with restart - On-Device CVM)

Requirement – On-Device CVM to be Performed

3.12.9.1 If the Kernel is informed that the transaction shall be reattempted

to allow entry of a Confirmation Code into a mobile device,
Then the Kernel shall provide an End Application Outcome with
the following parameters:
End Application:
• Start: B
• Online Response Data: N/A
• CVM: N/A
• UI Request on Outcome Present: Yes
Message Identifier: ‘20’ (“See Phone for Instructions”)
Status: Processing Error
Hold Time: 13
• UI Request on Restart Present: Yes
Message Identifier: ‘21’ (“Present Card Again”)
Status: Ready to Read
• Data Record Present: No
• Discretionary Data Present: No
• Alternate Interface Preference: N/A
• Receipt: N/A
• Field Off Request: 13
• Removal Timeout: Zero

March 2021 Page 70

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.12 Transaction Outcomes

3.12.10 Select Next

Requirement – Select Next

3.12.10.1 The Kernel shall provide a Select Next Outcome with the following
parameters:
Select Next:
• Start: C
• Online Response Data: N/A
• CVM: N/A
• UI Request on Outcome Present: No
• UI Request on Restart Present: No
• Data Record Present: No
• Discretionary Data Present: No
• Alternate Interface Preference: N/A
• Receipt: N/A
• Field Off Request: N/A
• Removal Timeout: Zero

March 2021 Page 71

3.13 Torn Transaction Recovery

When a transaction performed in EMV mode is torn during the execution of the first
GENERATE AC command, it may be preferable to have the card repeat its last
GENERATE AC response (when available), instead of relaunching a new
transaction.This method reduces the impact of tearing on the cards, especially when
the card supports an offline stored value.
This section describes the sequence of requirements to follow in order to recover
from a torn transaction in EMV Mode.
The torn transaction recovery is successful when the same card is re-presented after
the torn transaction, and the card accepts the recovery (ECHO command).
If the Kernel detects by any means that a different card is presented, the transaction
is abandoned.
If the card is unable to process the ECHO command (function is deactivated, or
transaction tearing has occurred before the card could save the transaction context),
the Kernel resumes a normal transaction flow.
Payment applications on the card are designed to process the ECHO command only
once. If another communication error occurs during the transaction recovery flow,
cardholder is prompted to present the card again for a normal transaction flow.

Figure 3-1 provides an overview of the recovery transaction flow as well as the links
to the standard transaction flow.

March 2021 Page 72

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.13 Torn Transaction Recovery

Figure 3-1 : Overview of the Recovery Transaction Flow

Recovery Transaction Flow

Format errors? YES End

Legacy Card? Application

NO
NOK Resume Standard
Comm. Error ECHO
Transaction Flow

Transaction
Initialisation

End
Initiate Application
Application
(with Restart) Comm GET PROC. OPTIONS
Error
EMV Mode

Read Appli. Data End

Comm. Error NOK
READ RECORD Application

Same Card? NO

YES

Cryptogram? AAC Declined

TC/ARQC

CDA Verification NOK

CVM Process
(EMV Mode)

ARQC TC

Online
Approved
Request

March 2021 Page 73

3.13.1 SELECT Response Analysis

If SELECT response does not parse correctly, or the Kernel recognises the card as a
legacy card, this indicates that the represented card is not the same as in the first
presentment. The recovery transaction is rejected.

Requirement – SELECT Response Analysis

3.13.1.1 If the FCI is absent

Or the FCI is not parsed correctly (see table 45 in [EMV Book 1])
Or the PDOL data element is absent, or present but empty,
Then the Kernel shall reset the Recovery Context as defined in
section 3.13.7 and provide an End Application Outcome as
described in Section 3.12.7.

3.13.1.2 If the card does not request the Terminal Compatibility Indicator
(Tag ‘9F52’) in the PDOL (legacy card),
Then the Kernel shall reset the Recovery Context as defined in
section 3.13.7 and provide an End Application Outcome as
described in Section 3.12.7.

3.13.2 ECHO Command

Requirement – ECHO Command

3.13.2.1 The Kernel shall issue the ECHO command as described in

section 4.1.

3.13.2.2 If the card returns a Status Word different from ‘9000’,

Then the Kernel shall reset the Recovery Context as defined in
section 3.13.7 and resume with a normal transaction flow
from Requirement 3.2.1.5 onwards.

3.13.2.3 If a transmission, protocol, or timeout error is detected during

the processing of the ECHO command,
Then the Kernel shall reset the Recovery Context as defined in
section 3.13.7 and provide an End Application (with restart –
Communication error) Outcome as described in Section 3.12.8.

March 2021 Page 74

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.13 Torn Transaction Recovery

3.13.3 Transaction Initialisation

Requirement – Transaction Initialisation

3.13.3.1 The Kernel shall initialise the transaction data by applying

Requirements 3.2.1.5 through 3.2.1.8.

3.13.4 Initiate Application Processing

Requirement – Initiate Application

3.13.4.1 The Kernel shall initiate the application as described in section 3.3.
Note: the SW returned in case of successful processing during a
recovery transaction (warning SW=6200) differs from the SW
returned for a normal transaction (SW=9000).

3.13.4.2 If a transmission, protocol, or timeout error is detected in the GET

PROCESSING OPTIONS response,
Then the Kernel shall reset the Recovery Context as defined in
section 3.13.7 and provide an End Application (with restart –
Communication error) Outcome as described in Section 3.12.8.

3.13.4.3 If the result of Initiate Application (as per section 3.3) is a Select
Next outcome,
Then the Kernel shall reset the Recovery Context as defined in
section 3.13.7 and provide an End Application Outcome as
described in Section 3.12.7.

3.13.5 Read Application Data

March 2021 Page 75

Requirement – Read Application Data

3.13.5.1 The Kernel shall read the application data as described in section
3.4.

3.13.5.2 If a transmission, protocol or timeout error is detected in any of

the READ RECORD response,
Then the Kernel shall reset the Recovery Context as defined in
section 3.13.7 and provide an End Application (with restart –
Communication error) Outcome as described in Section 3.12.8.

3.13.5.3 If the result of Read Application Data (as per section 3.4) is a Select
Next outcome,
Then the Kernel shall reset the Recovery Context as defined in
section 3.13.7 and provide an End Application Outcome as
described in Section 3.12.7.

Transaction Recovery can occur only if the card presented for the first – torn –
transaction is the same as the card presented for recovery. Thus the Kernel
compares the card account data from both transactions.

Requirement – Account Data Verification

3.13.5.4 The Kernel shall compare the Track 2 Equivalent Data value (Tag
‘57’) retrieved during 3.13.5.1 with the ‘Torn Track 2 Data’ from
the Recovery Context.
If the value of Track 2 Equivalent Data is not equal to the value of
‘Torn Track 2 Data’,
Then the Kernel shall reset the Recovery Context as defined in
section 3.13.7 and provide an End Application Outcome as
described in Section 3.12.7.

3.13.6 Transaction Recovery Completion

March 2021 Page 76

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com.
EMV ® Contactless Specifications for Payment Systems 3 Kernel Processing
Kernel C-5 Specif ication v2.10 3.13 Torn Transaction Recovery

Requirement – Transaction Recovery Completion

3.13.6.1 The Kernel shall proceed with CDA verification (when dynamic
signature is returned) and transaction completion, from
Requirement 3.8.1.8 onwards, with the following adjustments:
• the response to the GENERATE APPLICATION CRYPTOGRAM
command is replaced by the response to the ECHO
command.
• verification of the CDA signature (requirement 3.8.2.1): the
Transaction Data Hash Code is created by the concatenation
in this order of:
o the ‘Torn CDA Hash Data Buffer’
o the tags, lengths, and values of the data elements
returned by the card in the response to the ECHO
command in the order they are returned - with the
exception of the Signed Dynamic Application Data.
3.13.6.2 The Kernel shall reset the Recovery Context as defined in section
3.13.7.

March 2021 Page 77

3.13.7 Reset Recovery Context

Requirement – Reset Recovery Context

3.13.7.1 The Kernel shall reset the Recovery Context as follows:

• reset the internal indicator ‘Recovering from Torn EMV
Transaction’ to value ‘FALSE’.
• reset the ‘Torn Track 2 Data’ value (to zeroes).
• reset the ‘Torn CDA Hash Data Buffer’ value (to zeroes).

March 2021 Page 78

4 APDU command description

This section describes the APDU command-response pairs that are used by the
Kernel during the transaction flow. These commands are summarized in below:

Table 4-1: List of APDU commands used by the Kernel

CLA INS Meaning Requirement

‘80’ ‘DF’ ECHO Mandatory

‘80’ ‘AE’ GENERATE APPLICATION Mandatory
CRYPTOGRAM

‘80’ ‘A8’ GET PROCESSING OPTIONS Mandatory

‘00’ ‘B2’ READ RECORD Mandatory
‘00’ ‘A4’ SELECT Mandatory

March 2021 Page 79

4.1 ECHO

Definition and Scope

The ECHO command is used by the Kernel to retrieve the latest GENERATE
APPLICATION CRYPTOGRAM response produced by the card.
It is used when the Kernel attempts to recover from a torn transaction in EMV Mode.

Command Message
The ECHO command message is coded as shown in Table 4-2:

Table 4-2: ECHO Command Message

Code Value

CLA ‘80’
INS ‘DF’
P1 ‘00’
P2 ‘00’

Lc Not present
Data Not present
Le ‘00’

Data Field Sent in the Command Message

The data field of the command message is not present.

Data Field Returned in the Response Message

In case of successful execution of the command, the response data is id entical to the
response data generated by the card during the latest GENERATE APPLICATION
CRYPTOGRAM command.
Further details can be found in Section 4.2.
Processing State Returned in the Response Message

• ‘9000’ indicates a successful execution of the command.

March 2021 Page 80

• ‘6985’ may indicate any of the following reasons:

o The command is not supported by the card.
o No recovery response is available from the card.
o The ECHO command has already been played once for this
transaction, and cannot be replayed any longer.

March 2021 Page 81

4.2 First GENERATE APPLICATION CRYPTOGRAM

Definition and Scope

The GENERATE APPLICATION CRYPTOGRAM command is used to complete a
transaction.
To a great extent, it inherits its scope and format from the same command defined in
[EMV Book 3].

Command Message
The GENERATE APPLICATION CRYPTOGRAM command is coded as described in
[EMV Book 3] Section 6.5.5.

Data Field Sent in the Command Message

As described in [EMV Book 3], the command data consists of the CDOL1 related
data. For further details, please refer to [EMV Book 3] Section 5.4.

Data Field Returned in the Response Message

The response data is formatted as described in [EMV Book 3] Section 6.5.5, with the
following additional specificities:
• Legacy Mode: Response data is returned as per Format 1 (the data
object returned in the response message is a primitive data object with tag
equal to ‘80’).
• EMV Mode: Response data is returned as per Format 2 (the data
object returned in the response message is a constructed data object with tag
equal to ‘77’). The data elements present in the response depend on the type
of cryptogram returned by the card.

Table 4-3: Legacy Mode - Data Objects Included in Response to First

GENERATE AC

Tag Length Description Presence

(9F27) (1) Cryptogram Information Data M
(9F36) (2) Application Transaction Counter M
(9F26) (8) Application Cryptogram M

March 2021 Page 82

Tag Length Description Presence

(9F10) (8) Issuer Application Data M
Note: Tag and length are not included in the response of Legacy Mode .

Table 4-4: EMV Mode - Data Objects Included in Response to First GENERATE
AC for [TC returned] or [ARQC returned, CDA requested]

Tag Length Description Presence

‘9F27’ 1 Cryptogram Information Data M

‘9F36’ 2 Application Transaction Counter M

‘9F4B’ NIC Signed Dynamic Application Data M

‘9F50’ 1 Cardholder Verification Status M
‘9F10’ var. up to
Issuer Application Data M
32

‘9F5F’ 6 Offline Balance O

‘9F60’ 1 Issuer Update Parameter O

Table 4-5: EMV Mode - Data Objects Included in Response to First GENERATE
AC for [ARQC returned, CDA not requested]

Tag Length Description Presence

‘9F27’ 1 Cryptogram Information Data M

‘9F36’ 2 Application Transaction Counter M

‘9F26’ 8 Application Cryptogram (ARQC) M

‘9F50’ 1 Cardholder Verification Status M
‘9F10’ var. up to
Issuer Application Data M
32
‘9F5F’ 6 Offline Balance O
‘9F60’ 1 Issuer Update Parameter O

March 2021 Page 83

Table 4-6: EMV Mode - Data Objects Included in Response to First GENERATE
AC for [AAC returned]

Tag Length Description Presence

‘9F27’ 1 Cryptogram Information Data M

‘9F36’ 2 Application Transaction Counter M

‘9F26’ 8 Application Cryptogram (AAC) M

‘9F10’ var. up to
Issuer Application Data O
32

‘9F5F’ 6 Offline Balance O

Processing State Returned in the Response Message

• ‘9000’ indicates a successful execution of the command.

• ‘6984’ indicates that the card prefers to conduct the transaction using the
contact chip interface.

• ‘6985’ indicates that the conditions of use are not satisfied.

• ‘6986’ indicates that On-device Cardholder Verification is required (e.g. PIN

code shall be entered on mobile device).

• ‘6A80’ indicates that the command is incorrectly formatted.

March 2021 Page 84

4.3 Second GENERATE APPLICATION

CRYPTOGRAM

Definition and Scope

The Second GENERATE APPLICATION CRYPTOGRAM command may be required
during Issuer Update Processing for a transaction executed in EMV Mode.
To a great extent, it inherits its scope and format from the same command defined in
[EMV Book 3].

Command Message
The GENERATE APPLICATION CRYPTOGRAM command is coded as described in
[EMV Book 3] Section 6.5.5.

Data Field Sent in the Command Message

As described in [EMV Book 3], the command data consists of the CDOL2 related
data. For further details, please refer to [EMV Book 3] Section 5.4.

Data Field Returned in the Response Message

Response data is returned as per Format 2 (the data object returned in the response
message is a constructed data object with tag equal to ‘77’). The data elements
present in the response depend on the type of cryptogram returned by the card.

Table 4-3: Data Objects Included in Response to Second GENERATE AC

Tag Length Description Presence

‘9F27’ 1 Cryptogram Information Data M

‘9F36’ 2 Application Transaction Counter M

‘9F26’ 8 Application Cryptogram (TC/AAC) M
‘9F10’ var. up to
Issuer Application Data O
32
‘9F5F’ 6 Offline Balance O

March 2021 Page 85

Processing State Returned in the Response Message

• ‘9000’ indicates a successful execution of the command.

• ‘6985’ indicates that the conditions of use are not satisfied.

• ‘6A80’ indicates that the command is incorrectly formatted.

March 2021 Page 86

4.4 GET PROCESSING OPTIONS

Definition and Scope

The GET PROCESSING OPTIONS command is used to initialise the transaction
inside the card.
To a great extent, it inherits its scope and format from the same command defined in
[EMV Book 3].

Command Message
See [EMV Book 3] Section 6.5.8.

Data Field Sent in the Command Message

See [EMV Book 3] Section 6.5.8.

Data Field Returned in the Response Message

The response data is formatted as described in [EMV Book 3] Section 6.5.8, with the
following additional specificities:
• Legacy Mode: Response data is returned as per Format 1 (the data
object returned in the response message is a primitive data object with tag
equal to ‘80’).
• EMV Mode: Response data is returned as per Format 2 (the data
object returned in the response message is a constructed data object with tag
equal to ‘77’).
The data elements present in the response may depend on the Transaction Mode
selected by the card, as can be seen from the Table 4-4 below.
The Kernel shall ignore data objects other than those described in this table that may
be returned with Format 2.

March 2021 Page 87

Table 4-4: Data Objects Included in Response to GET PROCESSING OPTIONS

Tag Presence Presence

(format 2 Length Description Legacy EMV
only) Mode Mode

Application
‘82’ 2 Interchange Profile M M
(AIP)
Application File
‘94’ var. M M
Locator (AFL)

Processing State Returned in the Response Message

• ‘9000’ indicates a successful execution of the command during a normal

transaction.

• ‘6200’ (warning) indicates a successful execution of the command during a

torn transaction recovery.

• ‘6985’ indicates that the conditions of use are not satisfied.

• ‘6A80’ indicates that the command is incorrectly formatted.

March 2021 Page 88

4.5 READ RECORD

Definition and Scope

See [EMV Book 3] Section 6.5.11.

Command Message
See [EMV Book 3] Section 6.5.11.

Data Field Sent in the Command Message

See [EMV Book 3] Section 6.5.11.

Data Field Returned in the Response Message

See [EMV Book 3] Section 6.5.11.

Processing State Returned in the Response Message

See [EMV Book 3] Section 6.5.11.

March 2021 Page 89

4.6 SELECT

Definition and Scope

See [EMV Book 1] Section 11.3.

Command Message
See [EMV Book 1] Section 11.3.

Data Field Sent in the Command Message

See [EMV Book 1] Section 11.3.

Data Field Returned in the Response Message

See [EMV Book 1] Section 11.3.

Processing State Returned in the Response Message

See [EMV Book 1] Section 11.3.

March 2021 Page 90

Annex A Coding of Data Elements Used in

Transaction Flow

A.1 Application Interchange Profile (AIP) (Tag ‘82’)

Table A-1: Application Interchange Profile

AIP Byte 1 (Leftmost)

b8 b7 b6 b5 b4 b3 b2 b1 Meaning

0 RFU
1 SDA Supported
1 DDA Supported
1 Cardholder verification is supported
1 Terminal risk management is to be
performed
1 Issuer authentication is supported

0 RFU
1 CDA Supported

AIP Byte 2 (Rightmost)

b8 b7 b6 b5 b4 b3 b2 b1 Meaning

1 EMV Mode has been selected

x x x x x x x Each bit RFU

Note: Cards using Legacy Mode have a value of zero for AIP Byte 2.

March 2021 Page 91

A.2 Cardholder Verification Status (Tag ‘9F50’)

Table A-2: Cardholder Verification Status

b8 b7 b6 b5 b4 b3 b2 b1 Meaning

0 RFU
0 0 0 No CVM required
0 0 1 Signature (paper) is to be performed
0 1 0 Enciphered PIN verified online is to be
performed
0 1 1 On-Device CVM has been successfully
performed – method used is indicated
in bits b4-b1

1 0 0
1 0 1
RFU
1 1 0
1 1 1
On-Device CVM selected:
x x x x
0000b – No On-Device CVM performed
0001b – Confirmation Code entered on
Mobile Device
Other values – RFU

March 2021 Page 92

A.3 Combination Options

Table A-3: Combination Options

Combination Options Byte 1 (Leftmost)

b8 b7 b6 b5 b4 b3 b2 b1 Meaning

0 RFU
1 Status Check supported
1 Offline Data Authentication supported

1 Exception File Check required15

1 Random Transaction Selection
supported

0 fixed to 0b
1 EMV Mode Supported (fixed to 1b)
1 Legacy Mode Supported

Combination Options Byte 2 (Rightmost)

b8 b7 b6 b5 b4 b3 b2 b1 Meaning

x x x x x x x x Each bit RFU

15
Applies only if Exception File Check is supported as an Implementation Option.

March 2021 Page 93

A.4 CVM Results (Tag ‘9F34’)

Table A-4-1: CVM Results

CVM Results Byte 1

b8 b7 b6 b5 b4 b3 b2 b1 Meaning

x x x x x x x x CVM Performed:
00111111b – No CVM performed
00011111b – No CVM required
00011110b – Signature
00000010b – Online PIN
00000001b – Plaintext PIN verification
performed by ICC or Confirmation
Code entered on Mobile Device
Other values – RFU

CVM Results Byte 2

b8 b7 b6 b5 b4 b3 b2 b1 Meaning

x x x x x x x x CVM Condition:
00000000b –always
Other values – RFU

CVM Results Byte 3

b8 b7 b6 b5 b4 b3 b2 b1 Meaning
x x x x x x x x CVM Result:
00000000b –unknown
00000010b – successful
Other values – RFU

March 2021 Page 94

Setting of CVM Results

Table A-4-2 shows the setting of CVM Results that correspond to each value of
Outcome Parameter CVM.

Table A-4-2: Setting of CVM Results

CVM Results
Outcome Parameter CVM
Byte 1 Byte 2 Byte 3

‘02’ –
No CVM ‘1F’ – No CVM required ‘00’
successful

Obtain Signature ‘1E’ – Signature ‘00’ ‘00’ –unknown

Online PIN ‘02’ – Online PIN ‘00’ ‘00’ –unknown
‘01’ – Plaintext PIN ‘02’ –
Confirmation Code Verified ‘00’
verification successful

N/A ‘3F’ – No CVM performed ‘00’ ‘00’ –unknown

March 2021 Page 95

A.5 Device Information (Tag ‘9F6E’)

Table A-5: Device Information

Byte 1 Device type

b8 b7 b6 b5 b4 b3 b2 b1 Meaning

x x x Device Factor Version

In this version, this value is ‘001’
x x x x x Device Factor Type:
00000b – Card
00001b – Smart Phone
00010b – Key fob
00011b – Watch
00100b – Mobile Tag
00101b – Wristband
00110b – Mobile Phone case or Sleeve
00111b – Glasses
01000b – Tablet
Others are RFU

Byte 2 Application Location

b8 b7 b6 b5 b4 b3 b2 b1 Meaning

x x x RFU
x x x x x SE Type:
00001b – IC CHIP
00010b – SIM
00011b – Embedded SIM
00100b – MicroSD
00101b – IC tag
00110b – Cloud SE(HCE)
Others are RFU

Byte 3-4 RFU

March 2021 Page 96

b8 b7 b6 b5 b4 b3 b2 b1 Meaning

0 0 0 0 0 0 0 0 RFU

A.6 Issuer Update Parameter (Tag ‘9F60’)

Table A-6: Issuer Update Parameter

b8 b7 b6 b5 b4 b3 b2 b1 Meaning

x x x x x x Each bit RFU

0 0 Issuer Update is not expected, card
can be removed

0 1 Issuer Update is expected, card shall

be kept in RF field during authorisation
process

1 0 Issuer Update is expected, card shall

be presented again if necessary after
authorisation process
1 1 RFU

A.7 Partner Discretionary Data (Tag ‘9F7C’)

Table A-7: Partner Discretionary Data

Length
Data Digit # Value
(nibbles)
0: Set to “0”, if this parameter is not used
PDD Type 1: Japanese Issuer
1 1
Indicator 2: Non Japanese Issuer
3-F: RFU
If PDD Type indicator is “1”, this field shall
Category be set to Issuer's Category Code.
1 2
Code If PDD Type indicator is “0” or “2”, this field
shall be set to “0”.

March 2021 Page 97

Length
Data Digit # Value
(nibbles)
If PDD Type indicator is “0”, this field shall
be set to “0000”.
Company If PDD Type indicator is “1”, this field shall
Code / 4 3-6 be set to Issuer's Company Code.
Country Code If PDD Type indicator is “2”, this field shall
be set to Issuer Country Code according to
ISO 3166.
If PDD Type indicator is “0”, this field shall
Issuer be set to All “0”.
Discretionary 58 7-64 If PDD Type indicator is “1” or “2”, this field
Field shall be set to issuer proprietary data
elements.

March 2021 Page 98

A.8 Terminal Compatibility Indicator (Tag ‘9F52’)

Table A-8: Terminal Compatibility Indicator

b8 b7 b6 b5 b4 b3 b2 b1 Meaning

x x x x x x Each bit RFU

1 EMV Mode Supported (fixed to 1b)
0 fixed to 0b

March 2021 Page 99

A.9 Terminal Interchange Profile (static/dynamic)

(Tag ‘9F53’)
Table A-9: Terminal Interchange Profile

TIP Byte 1 (Leftmost)

b8 b7 b6 b5 b4 b3 b2 b1 Meaning

1 CVM required by reader / N/A16

1 Signature supported
1 Online PIN supported

1 On-Device CVM supported

0 RFU
1 Reader is a Transit Reader
1 EMV contact chip supported

1 (Contact Chip) Offline PIN supported

TIP Byte 2

b8 b7 b6 b5 b4 b3 b2 b1 Meaning

1 Issuer Update supported 17

x x x x x x x Each bit RFU

TIP Byte 3 (Rightmost)

b8 b7 b6 b5 b4 b3 b2 b1 Meaning

x x x x x x x x Each bit RFU

16
This bit is not applicable for the static Terminal Interchange Profile data element. It is
dynamically set by Kernel 5 for the dynamic Terminal Interchange Profile data element.
17
Applies only if Issuer Update is supported as an Implementation Option.

March 2021 Page 100

Annex B Data Elements Dictionary

Table B-1 defines those data elements which may be used for financial transaction interchange and their mapping on to data.

The reader shall apply padding according to the format of the data elements and the rules as defined in [EMV Book 1] and Annex B. The
reader shall accept TLV data elements in any order. The format of the TLV data elements is defined in [EMV Book 3], Annex B. A data
element with length '00' shall be treated as not present.

Table B-1: Data Elements Dictionary

Name Description Source Presence Format Specified Tag Length

Uniquely identifies the acquirer within each Configuration
Acquirer Identifier M n 6-11 EMV ‘9F01’ 6
payment system. (POS)
Amount, Authorised Authorised amount of the transaction.
POS M n 12 EMV ‘9F02’ 6
(Numeric) Requested in CDOL1.
Secondary amount associated with the
Amount, Other
transaction representing a cashback POS M n 12 EMV ‘9F03’ 6
(Numeric)
amount. Requested in CDOL1.
Application Cryptogram returned by the card in
ICC M b EMV ‘9F26’ 8
Cryptogram (AC) response of the GENERATE AC command
Application Currency Indicates the currency in which the account
ICC O n3 EMV ‘9F42’ 2
Code is managed according to ISO 4217.
Application Dedicated Identifies the application as described in
ICC M b EMV ‘4F’ 5-16
File (ADF) Name ISO/IEC 7816-4.

March 2021 Page 101

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10
Annex B Data Elements Dictionary

Name Description Source Presence Format Specified Tag Length

Application Effective Date from which the application may be
Date used ICC O n6 EMV ‘5F25’ 3

Application Expiration n6
Date after which application expires. ICC M EMV ‘5F24’ 3
Date YYMMDD
Application File Indicates the location (SFI, range of records) var. up
ICC M var. EMV ‘94’
Locator (AFL) of the AEFs related to a given application. to 252
Application
Indicates the capabilities of the card to Kernel 5
Interchange Profile ICC M b ‘82’ 2
support specific functions in the application. See A.1
(AIP)
Mnemonic associated with the AID
Application Label according to ISO/IEC 7816-5 (with the ICC M ans EMV ‘50’ 1-16
special character limited to space)
Application Preferred Preferred mnemonic associated with the AID ICC O ans EMV ‘9F12’ 1-16
Name
Application Primary
cn var. up var. up
Account Number Valid cardholder account number. ICC M EMV ‘5A’
to 19 to 10
(PAN)
Application Primary
Account Number Identifies and differentiates cards with the
(PAN) Sequence same PAN. ICC O n2 EMV ‘5F34’ 1
Number
Application Priority Indicates the priority of a given application or
ICC O b EMV ‘87’ 1
Indicator group of applications in a directory.
Application Selection Proprietary data allowing for proprietary
Registered processing during application selection. For
ICC O b EMV ‘9F0A’ var.
Proprietary Data further detail, please refer to Specification
(ASRPD) Bulletin No. 175.
March 2021 Page 102

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10
Annex B Data Elements Dictionary

Name Description Source Presence Format Specified Tag Length

Application Counter maintained by the application in the
Transaction Counter card (incrementing the ATC is managed by ICC M b EMV ‘9F36’ 2
(ATC) the card)
Indicates issuer's specified restrictions on
Application Usage
the geographic usage and services allowed ICC O b EMV ‘9F07’ 2
Control
for the application.

Application Version Version number assigned by the payment

ICC O b EMV ‘9F08’ 2
Number system for the application
Code that defines the disposition of a
message. ARC shall be present if the Kernel
Authorisation
is restarted after an Online Request Issuer C an2 EMV ‘8A’ 2
Response Code
Outcome. ARC shall not be present if it is a
new transaction.
Card Risk List of data objects (tag and length) to be var. up
Management Data passed to the card in the first GENERATE ICC M b EMV ‘8C’
to 252
Object List 1 (CDOL1) AC command
Card Risk List of data objects (tag and length) to be
var. up
Management Data passed to the card in the second ICC O b EMV ‘8D’
to 252
Object List 2 (CDOL2) GENERATE AC command
Indicates cardholder name according to ISO
Cardholder Name ICC O ans EMV ‘5F20’ 2-26
7813.
Cardholder
Identifies a method of verification of the var. up
Verification Method ICC C b EMV ‘8E’
cardholder supported by the application. to 252
(CVM) List

March 2021 Page 103

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10
Annex B Data Elements Dictionary

Name Description Source Presence Format Specified Tag Length

Indicates the CVM choice (already done or

Cardholder to be subsequently applied) for the Kernel 5
transaction. Choice is made dynamically by ICC C b ‘9F50’ 1
Verification Status See A.2
card based on transaction context and card
risk management configuration.
Present (up to 5 different instances) if Offline
Data Authentication is supported for at least
one of the Combinations with this RID (EMV
Mode only).
Certification Authority Each CA Public Key in the list is composed Configuration
C b EMV - var.
Public Key of the following mandatory fields: (RID)
- CAPK Index (b, 1 byte)
- CAPK Modulus (b, max. 248 bytes)
- CAPK Exponent (b, 1 or 3 bytes)
- CAPK SHA-1 Checksum (b, 20 bytes)
Identifies the certification authority's public
Certification Authority
key in conjunction with the RID. Required for ICC C b EMV ‘8F’ 1
Public Key Index
EMV Mode.
Defines some acquirer options for the Configuration Kernel 5
Combination Options M b - 2
combination, e.g. modes supported. (AID) See A.3
Used in Kernel 5 Terminal Risk
Contactless Floor Management (EMV Mode only). Present if Configuration
C n 12 Kernel 5 - 6
Limit the Combination supports Floor Limit Check (AID)
or Random Transaction Selection.

March 2021 Page 104

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10
Annex B Data Elements Dictionary

Name Description Source Presence Format Specified Tag Length

Used in Kernel 5 Terminal Risk
Management.
Contactless Indicates the limit for which contactless Configuration
O n 12 Kernel 5 - 6
Transaction Limit transactions can be conducted when CVM is (AID)
other than On-Device CVM (EMV Mode), or
when Transaction Mode is Legacy Mode.
Cryptogram Indicates the type of cryptogram and the
Information Data actions to be performed by the terminal after ICC M b EMV ‘9F27’ 1
(CID) the GENERATE AC command.
Used in Kernel 5 Terminal Risk Configuration
CVM Required Limit O n 12 Kernel 5 - 6
Management. (AID)
Indicates the results of the last CVM
CVM Results Kernel M b EMV ‘9F34’ 3
performed.
Dedicated File (DF) Identifies the name of the DF as described
ICC M b EMV ‘84’ 5-16
Name in ISO/IEC 7816-4.
Attributes of the device that may be used to
Device Information identify the specific device where a PAN or a ICC O an EMV ‘9F6E’ 4
payment token is stored.
File Control Issuer discretionary part of the FCI.
Information (FCI) This data element is mandatory for the ‘BF0C var. up
ICC C var. EMV
Issuer Discretionary PPSE application, and optional for the ’ to 222
Data payment application.
File Control Identifies the data object proprietary to this
Information (FCI) specification in the FCI template according ICC M var. EMV ‘A5’ var.
Proprietary Template to ISO/IEC 7816-4.
File Control
Identifies the FCI template according to var. up
Information (FCI) ICC M var. EMV ‘6F’
ISO/IEC 7816-4. to 252
Template
March 2021 Page 105

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10
Annex B Data Elements Dictionary

Name Description Source Presence Format Specified Tag Length

The number that identifies the major industry
Issuer Identification and the card issuer and that forms the first ICC O n6 EMV ‘42’ 3
Number (IIN)
part of the Primary Account Number (PAN)
The number that identifies the major industry
and the card issuer and that forms the first
part (6 or 8-digits) of the Primary Account
Issuer Identification
Number (PAN). While the first 6-digits of the var. 3
Number Extended ICC O n 6 or 8 EMV ‘9F0C’
IINE (tag ’9F0C’) and IIN (tag ‘42’) are the or 4
(IINE)
same and there is no need to have both
data objects on the card, cards may have
both the IIN and IINE data objects present.
Integrated Circuit
Card (ICC) Public Key ICC Public Key certified by the issuer ICC C b EMV ‘9F46’ NI
Certificate
Integrated Circuit ICC Public Key Exponent used for the
Card (ICC) Public Key verification of the Signed Dynamic ICC C b EMV ‘9F47’ 1 to 3
Exponent Application Data
Integrated Circuit
Remaining digits of the ICC Public Key NIC -
Card (ICC) Public Key ICC C b EMV ‘9F48’
Modulus NI + 42
Remainder
Specifies the issuer's conditions that cause
Issuer Action Code - a transaction to be rejected if it might have
ICC O b EMV ‘9F0D’ 5
Default been approved online, but the terminal is
unable to process the transaction online.
Specifies the issuer's conditions that cause
Issuer Action Code -
the denial of a transaction without attempt to ICC O b EMV ‘9F0E’ 5
Denial
go online.

March 2021 Page 106

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10
Annex B Data Elements Dictionary

Name Description Source Presence Format Specified Tag Length

Issuer Action Code - Specifies the issuer's conditions that cause
Online a transaction to be transmitted online. ICC O b EMV ‘9F0F’ 5

Contains proprietary application data for

Issuer Application var. up
transmission to the issuer in an online ICC M b EMV ‘9F10’
Data (IAD) to 32
transaction.
Data sent to the card for online issuer
authentication. Issuer Authentication Data
Issuer Authentication may be present if the Kernel is restarted
Data after an Online Request Outcome. Issuer Issuer O b EMV ‘91’ 8-16
Authentication Data shall not be present if it
is a new transaction.
Indicates the code table according to
Issuer Code Table
ISO/IEC 8859 for displaying the Application ICC O n2 EMV ‘9F11’ 1
Index
Preferred Name.

Issuer Country Code Indicates the country of the issuer according ICC O n3 EMV ‘5F28’ 2
to ISO 3166
Issuer Public Key Issuer public key certified by a certification
ICC C b EMV ‘90’ NCA
Certificate authority
Issuer public key exponent used for the
Issuer Public Key
verification of the Signed Static Application ICC C b EMV ‘9F32’ 1 to 3
Exponent
Data and the ICC Public Key Certificate.
NI -
Issuer Public Key Remaining digits of the Issuer Public Key
ICC C b EMV ‘92’ NCA +
Remainder Modulus
36
Issuer Script Contains a command for transmission to the var. up
Issuer O b EMV ‘86’
Command card. to 125
Issuer Script Identif ier Identification of the Issuer Script Issuer O b EMV ‘9F18’ 4

March 2021 Page 107

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10
Annex B Data Elements Dictionary

Name Description Source Presence Format Specified Tag Length

Contains proprietary issuer data for
transmission to the card before the second
GENERATE AC command. Several
occurrences of this data element may be
Issuer Script var. up
present. Issuer Script Template 1 may be Issuer O b EMV ‘71’
Template 1 to 128
present if the Kernel is restarted after an
Online Request Outcome. Issuer Script
Template 1 shall not be present if it is a new
transaction.
Contains proprietary issuer data for
transmission to the card after the second
GENERATE AC command. Several
occurrences of this data element may be
Issuer Script var. up
present. Issuer Script Template 2 may be Issuer O b EMV ‘72’
Template 2 to 128
present if the Kernel is restarted after an
Online Request Outcome. Issuer Script
Template 2 shall not be present if it is a new
transaction.
Parameter from the ICC to indicate the
behaviour/ergonomics (e.g. “present-and-
Issuer Update
hold” or “two presentments” or none) for ICC O b Card ‘9F60’ 1
Parameter
processing the results of the online
authorisation request

March 2021 Page 108

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10
Annex B Data Elements Dictionary

Name Description Source Presence Format Specified Tag Length

1-4 languages stored in order of preference,
each represented by 2 alphabetical
characters according to ISO 639.
Note: EMVCo strongly recommends that
Language Preference ICC O an 2 EMV ‘5F2D’ 2-8
cards be personalised with data element
‘5F2D’ coded in lowercase, but that
terminals accept the data element whether it
is coded in upper or lower case.
Represents the last four digits of the
underlying PAN affiliated with the payment
Last 4 digits of PAN token. Its purpose is to support customer Issuer O n4 EMV ‘9F25’ 2
service, for example digital wallet display or
receipt creation.
Maximum Target Value used in terminal risk management for
Percentage to be random transaction selection - present if the Configuration
C n2 EMV - 1
Used for Biased Combination supports Random Transaction (AID)
Random Selection Selection (EMV Mode only)
Classifies the type of business being done
Merchant Category by the merchant, represented according to Configuration
C n4 EMV ‘9F15’ 2
Code ISO 8583:1993 for Card Acceptor Business (POS)
Code.
Merchant Name and Indicates the name and location of the Configuration
M ans EMV ‘9F4E’ var.
Location merchant. (POS)
In the case of a prepaid card, represents the
Offline Balance value stored in card. May be returned in the ICC O n 12 Card ‘9F5F’ 6
GENERATE AC response.

March 2021 Page 109

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10
Annex B Data Elements Dictionary

Name Description Source Presence Format Specified Tag Length

On-Device CVM Indicates the limit for which contactless
Contactless transactions can be conducted when CVM is Configuration O n 12 Kernel 5 - 6
(AID)
Transaction Limit On-Device CVM (EMV Mode only).
A set of persistent data elements
representing the context of an ongoing
online transaction. The Online Transaction
Context is saved by the Kernel bef ore
returning the Online Request outcome, and
is restored if Kernel is restarted for an Issuer
Online Transaction Update.
It consists of: Kernel C - Kernel - var.
Context
• CDOL2 value provided by card
• The CVM parameter returned with
the Online Request outcome
• The Transaction Record (EMV Mode
– see Annex C) returned with the
Online Request outcome
Partner Discretionary Partner Discretionary Data, if present, var up
consists of one or more Issuer proprietary ICC O b Card ‘9F7C’
Data to 32
elements.
A non-financial reference assigned to each
Payment Account unique PAN and used to link a payment
ICC / Issuer O an EMV ‘9F24’ 29
Reference account represented by that PAN to
affiliated payment tokens.
Contains a list of terminal resident data
Processing Options
objects (tags and lengths) needed by the
Data Object List ICC M b EMV ‘9F38’ var.
card in processing the GET PROCESSING
(PDOL)
OPTIONS command.

March 2021 Page 110

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10
Annex B Data Elements Dictionary

Name Description Source Presence Format Specified Tag Length

Contains the contents of the record read.
READ RECORD
Response Message (Mandatory for SFIs 1-10. Response ICC M var. EMV ‘70’ var. up
messages for SFIs 11-30 are outside the to 252
Template
scope of EMV, but may use template ‘70’).
‘Recovering from Internal Kernel variable (Boolean) set to
Torn EMV TRUE when the Kernel attempts to recover Kernel 5 C - Kernel 5 - -
Transaction’ Flag from a torn transaction (EMV Mode only)
A set of persistent Kernel 5 parameters
involved in the management of torn EMV
transactions. It consists of:
Recovery Context - ‘Recovering from Torn EMV Kernel 5 C - Kernel 5 - -
Transaction’ Flag
- ‘Torn Track 2 Data’
- ‘Torn CDA Hash Data Buffer’
Present if the Combination supports Issuer
Update as Acquirer Option (EMV Mode
only).
In case of Online Request with “Present and Configuration
Removal Timeout C n4 Kernel - 2
Hold” outcome, this parameter corresponds (AID)
to the time after which cardholder is asked
to remove the card.
Value is given in units of 100ms.
Contains the data objects (without tags and
Response Message
lengths) returned by the ICC in response to ICC C var. EMV ‘80’ var.
Template Format 1
a command.
Contains the data objects (with tags and
Response Message
lengths) returned by the ICC in response to ICC M var. EMV ‘77’ var.
Template Format 2
a command.

March 2021 Page 111

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10
Annex B Data Elements Dictionary

Name Description Source Presence Format Specified Tag Length

Signed Dynamic Digital signature on critical application
Application Data parameters for DDA or CDA ICC C b EMV ‘9F4B’ NIC

List of tags of primitive data objects defined

Static Data
in this specification whose value fields are to
Authentication Tag ICC O - EMV ‘9F4A’ var.
be included in the Signed Static or Dynamic
List
Application Data
Value used in terminal risk management for
Target Percentage to
random transaction selection. Present if the Configuration
be Used for Biased Combination supports Random Transaction (AID) C n2 EMV - 1
Random Selection
Selection (EMV Mode only)
Terminal Action Code Used in Kernel 5 Terminal Action Analysis. Configuration
– Default (EMV Mode only) (AID) O b EMV - 5
Terminal Action Code Configuration
Used in Kernel 5 Terminal Action Analysis. O b EMV - 5
– Denial (AID)
Terminal Action Code Used in Kernel 5 Terminal Action Analysis. Configuration
O b EMV - 5
– Online (EMV Mode only) (AID)
Terminal Indicates to the card the transaction modes Kernel 5
Kernel 5 M b ‘9F52’ 1
Compatibility Indicator (EMV) supported by the Kernel. See A.8
Indicates the country of the terminal,
Terminal Country Configuration
represented according to ISO 3166. M n3 EMV ‘9F1A’ 2
Code (POS)
Requested in CDOL1.
Defines the reader CVM requirement and
Terminal Interchange capabilities, as well as other reader Kernel 5 M b Kernel 5 ‘9F53’ 3
Profile (dynamic) capabilities (online capability, contact EMV See A.5
capability) for the Transaction.

March 2021 Page 112

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10
Annex B Data Elements Dictionary

Name Description Source Presence Format Specified Tag Length

Defines the Cardholder Verification Methods
Terminal Interchange and other reader capabilities (online Configuration Kernel 5
M b - 3
Profile (static ) capability, contact EMV capability) for the (AID) See A.5
Combination.
Indicates the environment of the terminal, its Configuration
Terminal Type communications capability, and its M n2 EMV ‘9F35’ 1
(POS)
operational control.
Terminal Verification Status of the different functions as seen EMV /
Results (TVR) from the terminal Kernel 5 M b Kernel 5 ‘95’ 5
Value used in terminal risk management for
Threshold Value for
random transaction selection. Present if the Configuration
Biased Random Combination supports Random Transaction (AID) C n 12 EMV - 6
Selection
Selection (EMV Mode only)
An 11-digit numeric value that identifies
each unique combination of token requestor
Token Requestor ID ICC / Issuer O n 11 EMV ‘9F19’ 6
and token domain(s) for a given token
service provider.
A copy of the PDOL related data and
CDOL1 related data sent to the card during
Torn CDA Hash Data a torn transaction in EMV Mode. This copy var. up
Kernel 5 C b Kernel 5 -
Buffer is used to verify the CDA signature during to 507
the subsequent transaction recovery
process.
A copy of the card Track 2 Equivalent Data,
kept by the Kernel after a torn transaction in
var. up
Torn Track 2 Data EMV Mode to ensure that the card Kernel 5 C b Kernel 5 -
to 19
presented for recovery is the same as for
the torn transaction

March 2021 Page 113

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10
Annex B Data Elements Dictionary

Name Description Source Presence Format Specified Tag Length

Track 1 Discretionary Discretionary part of track 1 according to
Data ISO/IEC 7813 ICC O ans EMV ‘9F1F’ var.

Contains the data elements of track 2

Track 2 Equivalent according to ISO/IEC 7813, excluding start var. up
ICC M b EMV ‘57’
Data sentinel, end sentinel, and Longitudinal to 19
Redundancy Check (LRC).
Indicates the currency code of the
Transaction Currency Configuration
transaction according to ISO 4217. M n3 EMV ‘5F2A’ 2
Code Requested in CDOL1. (POS)
Indicates the implied position of the decimal
point from the right of the transaction
Transaction Currency amount represented according to ISO 4217. Configuration M EMV ‘5F36’
Exponent (POS) n1 1
Required to determine if Status Check is
requested.
Local date that the transaction was
Transaction Date POS M n6 EMV ‘9A’ 3
authorised. Requested in CDOL1.
An internal Kernel indicator storing the
transaction mode selected for conducting
the transaction. It admits the following
Transaction Mode values: Kernel 5 M - Kernel 5 - -
- Undefined Mode
- EMV Mode
- Legacy Mode
Local time that the transaction was n6
Transaction Time POS M EMV ‘9F21’ 3
authorised HHMMSS

March 2021 Page 114

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10
Annex B Data Elements Dictionary

Name Description Source Presence Format Specified Tag Length

Indicates the type of financial transaction,
represented by the first two digits of the ISO
8583:1987 Processing Code. Requested in
CDOL1. Possible values are:
Transaction Type - ‘00’ for a purchase transaction POS M n2 EMV ‘9C’ 1
- ‘01’ for a cash advance transaction
- ‘09’ for a purchase with cashback
- ‘20’ for a refund transaction
Uniquely identifies the transit agent within
Configuration
Transit Agent ID each region and location. Requested in O b Kernel ‘DF83’ 16
CDOL1. (AID)
Contains transit agent proprietary data for a Configuration
Transit Related Data O b Kernel ‘DF84’ 50
transit transaction. Requested in CDOL1. (AID)
Value to provide variability and uniqueness
Unpredictable
to the generation of a cryptogram. POS M b EMV ‘9F37’ 4
Number
Requested in CDOL1.

March 2021 Page 115

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10
Annex C Kernel 5 Transaction Record

Annex C Kernel 5 Transaction Record

Table C-1 lists the minimum data elements in the data record returned to the Entry Point, depending on the Transaction Mode (EMV,
Legacy) and the Transaction Outcome (Approved, Online Request, Declined).18
Data elements that are mentioned as ‘Conditional’ (‘C’) shall be present in the Transaction Record whenever they are provided by the
card.
Card data which was not provided by the card shall not be returned. 19

Table C-1: Minimum Data Elements returned as Transaction Record

18
Please note that Table C-1 does not list the data elements to be sent in the online authorization request.
19
For example, the terminal shall not send Tag '9F08' with length 00 in the online authorization request when Tag ‘9F08’ was not provided by the card.
March 2021 Page 116

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10
Annex C Kernel 5 Transaction Record

Data Element Name Tag Source Approved & Online Declined

Request

Amount, Authorised (Numeric) ‘9F02’ POS M M

Amount, Other (Numeric) ‘9F03’ POS M M
Application Cryptogram (AC) ‘9F26’ Card M C
Application Interchange Profile (AIP) ‘82’ Card M M
Application Expiration Date ‘5F24’ Card M M
Application Label ‘50’ Card M M
Application PAN ‘5A Card M M
Application PAN Sequence Number ‘5F34’ Card C C
Application Transaction Counter (ATC) ‘9F36’ Card M C
Application Version Number ‘9F08’ Card C C
Cardholder Name ‘5F20’ Card C C
CVM Results20 ‘9F34’ Kernel 5 M M
Dedicated File Name ‘84’ Card M M
Cryptogram Information Data (CID) ‘9F27’ Card M C

20
About the value of CVM Results, please refer to Table A-4-2: Setting of CVM Results

March 2021 Page 117

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10
Annex C Kernel 5 Transaction Record

Data Element Name Tag Source Approved & Online Declined

Request

Device Information ‘9F6E’ Card C C

Issuer Application Data (IAD) ‘9F10’ Card M C
Partner Discretionary Data ‘9F7C’ Card C C
Payment Account Reference ‘9F24’ Card C C
Transaction Mode 21 - Kernel 5 M M
Terminal Country Code ‘9F1A’ POS M M
Terminal Verification Results (TVR) ‘95’ Kernel 5 M M
Token Requestor ID ‘9F19’ Card C C
Track 1 Discretionary Data ‘9F1F’ Card C C
Track 2 Equivalent Data ‘57’ Card M M
Transaction Currency Code ‘5F2A’ POS M M
Transaction Date ‘9A’ POS M M
Transaction Time ‘9F21’ POS M M

21
Transaction Mode is used by the reader to map the POS Entry Mode data element in the authorisation/clearing message, according to Payment
System rules.
March 2021 Page 118

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specif ication v2.10
Annex C Kernel 5 Transaction Record

Data Element Name Tag Source Approved & Online Declined

Request

Transaction Type ‘9C’ POS M M

Unpredictable Number (UN) ‘9F37’ POS M M

March 2021 Page 119

© 2009-2021 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and
EMVCo found at www.emvco.com.
EMV® Contactless Specifications for Payment Systems
Kernel C-5 Specification v2.10
Annex D Default Terminal Action Code values

Annex D Default Terminal Action Code values

This section details the coding of the default Terminal Action Code values that the
Kernel shall use in case the Acquirer has not explicitly parameterised other values for
the Combination.

Table D-1: Default Terminal Action Code values

Terminal Action Code – Byte 1 (Leftmost)

Meaning Denial Online Default

Offline data authentication was not performed 0 1 1

SDA failed 0 0 0
ICC data missing 0 0 0

Card appears on terminal exception file 0 1 1

DDA failed 0 0 0
CDA failed 1 0 0
RFU 0 0 0
RFU 0 0 0

Terminal Action Code – Byte 2

Meaning Denial Online Default

ICC and terminal have different application 0 0 0

versions
Expired application 0 1 1
Application not yet effective 0 1 0
Requested service not allowed for card 1 0 0
product
New card 0 0 0

RFU 0 0 0
RFU 0 0 0
RFU 0 0 0

March 2021 Page 120

Terminal Action Code – Byte 3

Meaning Denial Online Default

Cardholder verification was not successful 0 0 0

Unrecognised CVM 0 0 0
PIN Try Limit exceeded 0 0 0
PIN entry required and PIN pad not present or 0 0 0
not working
PIN entry required, PIN pad present, but PIN 0 0 0
was not entered

Online PIN entered 0 0 0

RFU 0 0 0
RFU 0 0 0

Terminal Action Code – Byte 4

Meaning Denial Online Default

Transaction exceeds floor limit 0 1 1
Lower consecutive offline limit exceeded 0 0 0

Upper consecutive offline limit exceeded 0 0 0

Transaction selected randomly for online 0 1 0
processing

Merchant forced transaction online 0 0 0

RFU 0 0 0
RFU 0 0 0
RFU 0 0 0

March 2021 Page 121

Terminal Action Code – Byte 5 (Rightmost)

Meaning Denial Online Default

Default TDOL used 0 0 0

Issuer authentication failed 0 0 0
Script processing failed before final 0 0 0
GENERATE AC
Script processing failed after final GENERATE 0 0 0
AC
RFU 0 0 0

RFU 0 0 0
RFU 0 0 0
RFU 0 0 0

March 2021 Page 122

Annex E Glossary
This is a glossary of terms and abbreviations used in this specification. For
descriptions of data elements, see Annex A.

a Alphabetic

AAC Application Authentication Cryptogram

AC Application Cryptogram

Acquirer A financial institution that signs a merchant (or disburses

currency to a cardholder in a cash disbursement) and directly or
indirectly enters the resulting transaction into interchange.

ADF Application Definition File

AFL Application File Locator

AID Application Identifier

AIP Application Interchange Profile

APDU Application Protocol Data Unit

Application Cryptogram returned by the card; one of the following cryptogram

Cryptogram types:

AAC Application Authentication Cryptogram

ARQC Authorisation Request Cryptogram
TC Transaction Certificate

Approved A Final Outcome to approve the transaction

ARQC Authorisation Request Cryptogram

ATC Application Transaction Counter

b Binary

C Conditional

March 2021 Page 123

Card As used in these specifications, a consumer device supporting

contactless transactions. It may be a plastic card, a mobile
phone, a key fob, a watch or any other suitable form factor

Cardholder An individual to whom a card is issued or who is authorised to

use that card.

Cardholder A method used to confirm the identity of a cardholder.

Verification
Method (CVM)

CDOL Card Risk Management Data Object List

Chip Grade An operating mode of the POS System that indicates that this
particular acceptance environment and acceptance rules
supports chip infrastructure.

CID Cryptogram Information Data

CL Contactless

cn Compressed Numeric

Combination Any of the following:

For: The combination of:
a card • an ADF Name
• a Kernel Identifier
a reader • an AID
• a Kernel ID
the Candidate List • an ADF Name
for final selection • a Kernel ID
• the Application Priority
Indicator (if present)
• the Extended Selection
(if present)

Confirmation A code or password entered into a mobile device in order to

Code confirm that a user wishes to perform a contactless mobile
payment transaction.

Contactless See “Card”.

card

March 2021 Page 124

Contactless The symbol identifying the contactless “landing pane” near the
Symbol antenna of a contactless acceptance device, where the
cardholder shall present the card.

CVM Cardholder Verification Method

CVS Cardholder Verification Status

Declined A Final Outcome to decline the transaction

DOL Data Object List

EMV® A global standard f or credit and debit payment cards based on

chip card technology. The EMV Integrated Circuit Card
Specifications for Payment Systems are developed and
maintained by EMVCo.

EMV Mode One of the two Kernel 5 transaction modes. EMV Mode is
selected for the transaction in a Chip Grade acceptance, when
also supported by the card.

EMVCo EMVCo LLC is the organisation of payment systems that

manages, maintains, and enhances the EMV specifications.
EMVCo is currently operated by American Express, Discover,
JCB, MasterCard, UnionPay and Visa.

End Application A Final Outcome

F Format

FCI File Control Information

Final Outcome Result provided to the reader as a result of Entry Point

processing the Outcome from the kernel, or provided directly by
Entry Point under exceptional conditions.

GPO GET PROCESSING OPTIONS command

IAD Issuer Application Data

ICC Integrated Circuit Card

Issuer A financial institution that issues contactless cards or contactless

payment applications that reside in consumer devices.

March 2021 Page 125

Kernel The Kernel contains interface routines, security and control

functions, and logic to manage a set of commands and
responses to retrieve the necessary data from a card to complete
a transaction. The Kernel processing covers the interaction with
the card between the Final Combination Selection (excluded) and
the Outcome Processing (excluded).

Kernel ID Identifier to distinguish between different Kernels that may be

supported by the reader.

Kernel Identifier Identifier to distinguish between different Kernels that may be

indicated by the card.

L Length

Legacy Mode One of the two Kernel 5 transaction modes. Legacy Mode is
selected for the transaction in a Chip Grade acceptance, when
the card is a legacy card.

M Mandatory

n Numeric

N/A Not Applicable; a possible value for several Outcome and Final
Outcome parameters

O Optional

Online PIN A method of PIN verification where the PIN entered by the
cardholder into the terminal PIN pad is encrypted and included in
the online authorisation request message sent to the issuer.

Online Request A Final Outcome to request online authorization

Outcome Result from the Kernel processing, provided to Reader, or under

exceptional conditions, result of Entry Point processing. In either
case, a primary value with a parameter set.

PAN Primary Account Number

PDOL Processing Options Data Object List

PIN Personal Identification Number

POS Point of Sale

March 2021 Page 126

Reader A component of the POS System; described in detail in Book A.

RFU Reserved for Future Use (by EMVCo / JCB)

A bit specified as Reserved for Future Use (RFU) is set as
specified. A data field having a value coded on multiple bits or
bytes cannot be set to a value specified as RFU. If the reader
receives a data field having a value specified as RFU, the reader
behaves as defined by the requirement that specifically
addresses the situation.

SE Secure Element

Select Next An Outcome which leads to re-starting the processing at the

appropriate start

SFI Short File Identifier

Status Check Option within the Combination related to the checking of a single
Support unit of currency. A single unit of currency has the value of 1 of the
(major) unit of currency as defined in ISO 4217. As an example a
single unit of currency for Euro is 1.00.

SW1 SW2 Status Byte 1, Status Byte 2

T Tag

TC Transaction Certificate

Terminal A component of the POS System; described in detail in [EMV CL

Book A].

TIP Terminal Interchange Profile

TLV Tag Length Value

Transaction The reader-card interaction between the first presentment of the

card and the decision on whether the transaction is approved or
declined. If the transaction is authorised online, this may involve
multiple presentments of the card on the reader.

Try Another A Final Outcome

Interface

TVR Terminal Verification Results

March 2021 Page 127

UI User Interface

var. Variable Length

* END OF DOCUMENT *

March 2021 Page 128

MC Quick Reference Booklet
No ratings yet
MC Quick Reference Booklet
386 pages
EMV Level 1 Contactless Interface Specification V3.0 180423 PDF
No ratings yet
EMV Level 1 Contactless Interface Specification V3.0 180423 PDF
261 pages
Visa Integrated Circuit Card Specification
100% (3)
Visa Integrated Circuit Card Specification
370 pages
Unit 4 E-Banking
No ratings yet
Unit 4 E-Banking
25 pages
Debit Card FAQs
No ratings yet
Debit Card FAQs
7 pages
Buypass 31240B Base53.40.00
No ratings yet
Buypass 31240B Base53.40.00
85 pages
Conway - The Personal Security Handbook
No ratings yet
Conway - The Personal Security Handbook
271 pages
C-6 Kernel 6 V 2 7 Final
No ratings yet
C-6 Kernel 6 V 2 7 Final
125 pages
EMV Level 1 Contactless Interface Specification V3.2
No ratings yet
EMV Level 1 Contactless Interface Specification V3.2
267 pages
IR Prognosis Summit PnI - Customer Use Case Discussions
No ratings yet
IR Prognosis Summit PnI - Customer Use Case Discussions
23 pages
EMV SWG NK15r4 EMVCo Card Personalisation Specification With AES 4august2021
No ratings yet
EMV SWG NK15r4 EMVCo Card Personalisation Specification With AES 4august2021
114 pages
Dashen Bank Interview Questions
No ratings yet
Dashen Bank Interview Questions
74 pages
EPC020-08 Book 3 - Data Element Spreadsheet - SCS Volume v7.1
No ratings yet
EPC020-08 Book 3 - Data Element Spreadsheet - SCS Volume v7.1
9 pages
EMV Reading PAN Code - Apdu
No ratings yet
EMV Reading PAN Code - Apdu
4 pages
EMVCo 3DS Spec v220 122018
No ratings yet
EMVCo 3DS Spec v220 122018
286 pages
The Helen Rose Report
0% (1)
The Helen Rose Report
5 pages
C 0.8 Reference Manual: Ardpeek
No ratings yet
C 0.8 Reference Manual: Ardpeek
60 pages
Kernel C 4 Specification v2.11
No ratings yet
Kernel C 4 Specification v2.11
165 pages
EMV Contactless Book B Entry Point Specification v2.10
No ratings yet
EMV Contactless Book B Entry Point Specification v2.10
58 pages
D EMV Contactless Communication Protocol v2.1 March2011 20110406010859160
No ratings yet
D EMV Contactless Communication Protocol v2.1 March2011 20110406010859160
247 pages
Atm Technical Requirements
No ratings yet
Atm Technical Requirements
13 pages
Kavita Sahu....
No ratings yet
Kavita Sahu....
80 pages
Vatsals Blackbook Final 2
No ratings yet
Vatsals Blackbook Final 2
80 pages
C-2 Kernel 2 v2.1 March2011 20110407012007159
No ratings yet
C-2 Kernel 2 v2.1 March2011 20110407012007159
536 pages
State of The Art Secure Mobile Payment
No ratings yet
State of The Art Secure Mobile Payment
18 pages
Corporatecardsuserguide 110221
No ratings yet
Corporatecardsuserguide 110221
49 pages
EPC020-08 SEPA Cards Standardisation Volume v7.1 Book 2
No ratings yet
EPC020-08 SEPA Cards Standardisation Volume v7.1 Book 2
107 pages
Annex A Singapore Quick Response Code SGQR
No ratings yet
Annex A Singapore Quick Response Code SGQR
2 pages
C-2 Kernel 2 V2.6 Final-For EMVCo 20160923093817522
No ratings yet
C-2 Kernel 2 V2.6 Final-For EMVCo 20160923093817522
589 pages
EMV Contactless Book A Architecture and General Rqmts v2.10
No ratings yet
EMV Contactless Book A Architecture and General Rqmts v2.10
119 pages
C 3 Kernel 3 v2.11 June 2023
No ratings yet
C 3 Kernel 3 v2.11 June 2023
150 pages
C 2 Kernel 2 v2.10
100% (1)
C 2 Kernel 2 v2.10
593 pages
C 2 Kernel 2 V2.11 Final June 2023
No ratings yet
C 2 Kernel 2 V2.11 Final June 2023
458 pages
EMVCo Payment Tokenisation Specification Technical Framework v1.0
No ratings yet
EMVCo Payment Tokenisation Specification Technical Framework v1.0
84 pages
Emv Especifications
100% (1)
Emv Especifications
44 pages
C 7 Kernel 7 v2 11 Clean 1
No ratings yet
C 7 Kernel 7 v2 11 Clean 1
77 pages
C-3 Kernel 3 v2.2 20120629080636649
100% (1)
C-3 Kernel 3 v2.2 20120629080636649
165 pages
C-4 Kernel 4 v2.2 20120629080511149
No ratings yet
C-4 Kernel 4 v2.2 20120629080511149
169 pages
C 8 Kernel 8 V1.0
No ratings yet
C 8 Kernel 8 V1.0
316 pages
EMV Next Gen Architecture Overview v1.0 201409160406534
No ratings yet
EMV Next Gen Architecture Overview v1.0 201409160406534
65 pages
C-4 Kernel 4 v2.6 20160512101635327
No ratings yet
C-4 Kernel 4 v2.6 20160512101635327
168 pages
VIS 140 Updates
No ratings yet
VIS 140 Updates
20 pages
BCA ECR Documentation Fase III
No ratings yet
BCA ECR Documentation Fase III
70 pages
C-5 Kernel 5 v2.6 20160512102630338
No ratings yet
C-5 Kernel 5 v2.6 20160512102630338
131 pages
C-6 Kernel 6 V 2 11 Final
No ratings yet
C-6 Kernel 6 V 2 11 Final
148 pages
C-5 Kernel 5 V 2 7 Final
No ratings yet
C-5 Kernel 5 V 2 7 Final
132 pages
Owning and Cloning NFC Payment Cards
100% (1)
Owning and Cloning NFC Payment Cards
42 pages
Contactless Specifications For Payment Systems: Book B
No ratings yet
Contactless Specifications For Payment Systems: Book B
52 pages
C 7 Kernel 7 v2 9 1
No ratings yet
C 7 Kernel 7 v2 9 1
75 pages
Ic Card Specification 20 Eng
100% (1)
Ic Card Specification 20 Eng
124 pages
Hardware Security Module
100% (3)
Hardware Security Module
2 pages
EMV Contactless PDF
No ratings yet
EMV Contactless PDF
111 pages
Debit Card - Project Wark PDF
No ratings yet
Debit Card - Project Wark PDF
158 pages
C 4 Kernel 4 v2.10
No ratings yet
C 4 Kernel 4 v2.10
177 pages
C-6 Kernel 6 V 2 8 Final
No ratings yet
C-6 Kernel 6 V 2 8 Final
120 pages
C-1 Kernel 1 v2.1 March2011 20110407011833378
No ratings yet
C-1 Kernel 1 v2.1 March2011 20110407011833378
41 pages
EMVCo Consumer Presented QR Specification v1 1
50% (2)
EMVCo Consumer Presented QR Specification v1 1
32 pages
UPI QuickPass Testing Guide For Acquirers - V202205
No ratings yet
UPI QuickPass Testing Guide For Acquirers - V202205
17 pages
EMVCo Software Based Mobile Payment Security Requirements - V1.0 - 20161213 - 20161213093622436
No ratings yet
EMVCo Software Based Mobile Payment Security Requirements - V1.0 - 20161213 - 20161213093622436
42 pages
EMVCo White Paper On Payment Account Reference v2.1.1 Final
No ratings yet
EMVCo White Paper On Payment Account Reference v2.1.1 Final
25 pages
EMVCo Consumer Presented QR Specification v1.1
No ratings yet
EMVCo Consumer Presented QR Specification v1.1
34 pages
Debit Mastercard For Single Message System Guide: 25 October 2018
100% (1)
Debit Mastercard For Single Message System Guide: 25 October 2018
83 pages
EMVCo A Guide To EMV 2011051203091992
No ratings yet
EMVCo A Guide To EMV 2011051203091992
35 pages
HSM
No ratings yet
HSM
92 pages
C-4 Kernel 4 V 2 7 Final PDF
No ratings yet
C-4 Kernel 4 V 2 7 Final PDF
173 pages
C-5 Kernel-5 v2.11
No ratings yet
C-5 Kernel-5 v2.11
126 pages
C 2 Kernel 2 V2.8
No ratings yet
C 2 Kernel 2 V2.8
580 pages
A Architecture and General Rqmts v2 7 Final
No ratings yet
A Architecture and General Rqmts v2 7 Final
116 pages
EMV (Chip & PIN) Protocol: Märt Bakhoff Supervised: Arnis Paršovs
No ratings yet
EMV (Chip & PIN) Protocol: Märt Bakhoff Supervised: Arnis Paršovs
41 pages
Recommendations For EMV Processing For Industry-Specific Tra
No ratings yet
Recommendations For EMV Processing For Industry-Specific Tra
18 pages
Nexo FAST: PURE Kernel
No ratings yet
Nexo FAST: PURE Kernel
35 pages
7 EMVCo Level3 Framework Implementation Guidelines V 1 1 20190411
No ratings yet
7 EMVCo Level3 Framework Implementation Guidelines V 1 1 20190411
103 pages
SB286 Update For EMV Book C 5
No ratings yet
SB286 Update For EMV Book C 5
4 pages
C-7 Kernel 7 V 2 7 Final
No ratings yet
C-7 Kernel 7 V 2 7 Final
73 pages
Users Manual 3704697
No ratings yet
Users Manual 3704697
442 pages
C-1 Kernel 1 v2.6 20160512101416661
No ratings yet
C-1 Kernel 1 v2.6 20160512101416661
34 pages
EMV Contactless Kernel PR FINAL
No ratings yet
EMV Contactless Kernel PR FINAL
2 pages
EMV - Understanding
No ratings yet
EMV - Understanding
3 pages
Part V Contactless Integrated Circuit Card Payment Specification
100% (1)
Part V Contactless Integrated Circuit Card Payment Specification
103 pages
EMV v4.3 Book 3 Application Specification 20120607062110791
No ratings yet
EMV v4.3 Book 3 Application Specification 20120607062110791
230 pages
DCI Contactless D-PAS Acquirer Host Test Plan v1.2
No ratings yet
DCI Contactless D-PAS Acquirer Host Test Plan v1.2
88 pages
book2-EMV v4.2 Book 2 Security and Key Management CR05 - 20090122094212
100% (1)
book2-EMV v4.2 Book 2 Security and Key Management CR05 - 20090122094212
176 pages
A Guide To EMV Chip Technology v3.0 1
No ratings yet
A Guide To EMV Chip Technology v3.0 1
33 pages
PayPass - MChip (V1.3)
No ratings yet
PayPass - MChip (V1.3)
125 pages
Quick Chip For EMV and QVSDC, Specification Version 2.0 (Visa, 2017)
100% (1)
Quick Chip For EMV and QVSDC, Specification Version 2.0 (Visa, 2017)
18 pages
EMV v4.3 Book1 ICC To Terminal Interface 2011113003541414
100% (1)
EMV v4.3 Book1 ICC To Terminal Interface 2011113003541414
189 pages
PayPass - MChip - Acquirer - Imlementation - Requirements - PPMCAIR (V1.0 - July 2008)
No ratings yet
PayPass - MChip - Acquirer - Imlementation - Requirements - PPMCAIR (V1.0 - July 2008)
88 pages
EMV v4.3 Book2 Security and Key Management 20111130035544327
No ratings yet
EMV v4.3 Book2 Security and Key Management 20111130035544327
174 pages

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.