EMV®

Contactless Specifications for

Payment Systems

Book C-7

Kernel 7 Specification

Version 2.11
June 2023

June 2023 Page i

© 2023 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 Book C-7
Kernel 7 Spec v2.11

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 following 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 software 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 omissions
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 for any party's infringement of any intellectual property
rights in connection with these Specifications.

Page ii June 2023

© 2023 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 Book C-7
Kernel 7 Spec v2.11

Revision Log – Version 2.11

The following changes have been made to Book C-7 since the publication of Version
2.10:
 Split GPO Response Data table when the card's transaction disposition is
an ARQC into two tables, indicating ARQC without Offline Data
Authentication (Table 4-3) and ARQC with Offline Data Authentication
(Table 4-5) respectively. Adjusted wordings in 4.1.4.5 accordingly.

June 2023 Page iii

© 2023 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 Book C-7
Kernel 7 Spec v2.11

Contents
Revision Log – Version 2.9 ....................................................................................iii
1 General ...............................................................................................................8

1.1 Scope ..........................................................................................................8

1.2 Audience .....................................................................................................8
1.3 Volumes of the Contactless Specifications ..................................................8
1.4 Reference Materials ....................................................................................9
1.5 Overview .....................................................................................................9
2 POS System .....................................................................................................11
3 Processing Overview ....................................................................................... 13
3.1 General Description...................................................................................13
3.2 Overview of Transaction Processing ......................................................... 14
3.2.1 Kernel Activation ............................................................................14
3.2.2 Application Initialization..................................................................14
3.2.3 Read Application Data ...................................................................16
3.2.4 Offline Data Authentication ............................................................ 17
3.2.5 Online Processing..........................................................................18
3.2.6 Transaction Completion .................................................................18
3.3 General Transaction Flow .........................................................................19
4 Transaction Processing ..................................................................................21
4.1 Application Initialization .............................................................................21
4.1.1 Input .............................................................................................. 21
4.1.2 Commands ....................................................................................22
4.1.3 Flow Chart .....................................................................................23
4.1.4 Kernel Processing..........................................................................24
4.2 Read Application Data...............................................................................33
4.2.1 Input .............................................................................................. 34
4.2.2 Commands ....................................................................................34
4.2.3 Flow Chart .....................................................................................35
4.2.4 Kernel Processing..........................................................................36
4.3 Offline Data Authentication ........................................................................40
4.3.1 Input .............................................................................................. 40
4.3.2 Kernel Processing..........................................................................42
4.4 Cardholder Verification ..............................................................................46
4.4.1 General Requirements ...................................................................46
4.4.2 CVM Processing ............................................................................46
4.5 Outcome ...................................................................................................49

Page iv June 2023

© 2023 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 Book C-7
Kernel 7 Spec v2.11

4.5.1 Approved ....................................................................................... 49

4.5.2 Online Request ..............................................................................50
4.5.3 Try again (1) ..................................................................................52
4.5.4 Declined ........................................................................................ 53
4.5.5 Try Another Interface .....................................................................54
4.5.6 Select Next ....................................................................................55
4.5.7 End Application ..............................................................................56
4.5.8 Try again (2) ..................................................................................57
Annex A. Data Dictionary ....................................................................................59
Annex B. Fast Dynamic Data Authentication (fDDA) .........................................67
Annex C. Data Elements ...................................................................................... 69
Annex D. Transaction Log Retrieval ...................................................................72
Annex E. Glossary ............................................................................................... 73

June 2023 Page v

© 2023 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 Book C-7
Kernel 7 Spec v2.11

Figures
Figure 2-1 Logical Architecture ................................................................................12
Figure 3-1 Sample of EMV Mode Transaction Flow .................................................20
Figure 4-1 GPO Processing .....................................................................................23
Figure 4-2 Read Application Data ............................................................................35
Figure B-1 Sample of Data Exchange Related to fDDA ...........................................68

Tables
Table 3-1 Terminal Transaction Qualifiers ............................................................... 15
Table 4-1 Response of SELECT AID .......................................................................21
Table 4-2 GPO Command Message ........................................................................22
Table 4-3 GPO Response Data if The Card’s Transaction Disposition is an ARQC or
AAC.......................................................................................................29
Table 4-4 GPO Response Data if The Card’s Transaction Disposition is a TC.........30
Table 4-5 GPO Response Data if The Card’s Transaction Disposition is an ARQC
with Offline Data Authentication............................................................. 32
Table 4-6 Card Data used in Read Application Data ................................................34
Table 4-7 Offline Data Authentication--Terminal Data ..............................................40
Table 4-8 Offline Data Authentication--Card Data ....................................................40
Table 4-9 Dynamic Kernel Data to be Hashed ......................................................... 43
Table 4-10 IC Card Dynamic Data to be Hashed .....................................................44
Table A-1 Data Dictionary ........................................................................................ 60
Table C-1 Clearing Data Element ............................................................................69

Page vi June 2023

© 2023 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 Book C-7
Kernel 7 Spec v2.11

Requirements
Requirement – Online Authorization ........................................................................18
Requirement – PDOL Check....................................................................................24
Requirement – TTQ Resetting .................................................................................24
Requirement – Processing of Status Code .............................................................. 24
Requirement –Transaction Disposition ....................................................................26
Requirement – Mandatory-Data Check ....................................................................27
Requirement – L1 Errors in Reading Application Data .............................................36
Requirement – Processing of READ RECORD Response .......................................36
Requirement – Exception File ..................................................................................38
Requirement – Other Exception Handlings .............................................................. 38
Requirement – fDDA Version Check ........................................................................42
Requirement – fDDA Data Check ............................................................................43
Requirement – fDDA Verification .............................................................................44
Requirement – fDDA Failed or Not Performed ......................................................... 45
Requirement – CVM Check .....................................................................................47
Requirement – CVM Check .....................................................................................48
Requirement – APPROVED Outcome .....................................................................49
Requirement – ONLINE REQUEST Outcome .......................................................... 51
Requirement – TRY AGAIN Outcome ......................................................................53
Requirement – DECLINED Outcome .......................................................................54
Requirement – TRY ANOTHER INTERFACE Outcome...........................................55
Requirement – SELECT NEXT Outcome .................................................................56
Requirement – END APPLICATION Outcome ......................................................... 57
Requirement – TRY AGAIN Outcome ......................................................................58

June 2023 Page vii

© 2023 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.
1 General EMV Contactless Book C-7
1.1 Scope Kernel 7 Spec v2.11

1 General
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 7
Specification, describes one of several kernels defined for use with Entry Point.

1.2 Audience
This specification is intended to be used by system designers in payment systems
and financial institution staff responsible for implementing financial applications.

1.3 Volumes of the Contactless Specifications

This specification is part of a ten-volume set:
Book A: Architecture and General Requirements
Book B: Entry Point Specification
Book C-2: Kernel 2 Specification
Book C-3: Kernel 3 Specification
Book C-4: Kernel 4 Specification
Book C-5: Kernel 5 Specification
Book C-6: Kernel 6 Specification
Book C-7: Kernel 7 Specification
Level 1 Specifications for Payment Systems, EMV Contactless Interface
Specification

June 2023 Page 8

© 2023 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 Book C-7 1 General
Kernel 7 Spec v2.11 1.4 Reference Materials

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 4.3] EMV Integrated Circuit Card Specifications for Payment

Systems, Version 4.3, November 2011, including:

[EMV 4.3 Book 1] EMV Integrated Circuit Card Specifications for Payment
Systems, Book 1, Application Independent ICC to
Terminal Interface Requirements

[EMV 4.3 Book 2] EMV Integrated Circuit Card Specifications for Payment
Systems, Book 2, Security and Key Management

[EMV 4.3 Book 3] EMV Integrated Circuit Card Specifications for Payment
Systems, Book 3, Application Specification

[EMV 4.3 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 reader to understand the structure
of this specification so that they could read it effectively.
Chapter 2 introduces the main architecture of the POS System supported by
Kernel7.
Chapter 3 gives an overview of the features of Kernel7 and its configuration and
main functions.
Chapter 4 breaks down the main transaction steps, within each details are provided
to describe the necessary data to be processed, commands used and Kernel
processing as well.
Annex A contains the dictionary of data objects used by Kernel7,including the kernel
data elements and card elements must be supported by Kernel7 as well.
Annex B is a sample of Fast Dynamic Data Authentications and provides relevant
explanations.

June 2023 Page 9

© 2023 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.
1 General EMV Contactless Book C-7
1.5 Overview Kernel 7 Spec v2.11

Annex C lists authorization and clearing data needed to be provided by Kernel7

when the Kernel sends an ONLINE REQUEST or APPROVE as an output to Entry
Point.
Annex D describes the process of retrieving card transaction log.
Annex E is a glossary of terms and abbreviations in this specification.

Page 10 June 2023

© 2023 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 Book C-7 2 POS System
Kernel 7 Spec v2.11 1.5 Overview

2 POS System
This chapter lists the possible physical architectures of POS system conducting EMV
Mode contactless transactions; transactions using contact interface or magstripe are
out of the scope of this specification.
POS System shall be able to host the following functions in Kernel7:
 Interact with contactless card
 Process application selection, complete kernel activation and transfer
transaction outcomes
 Display transaction information to cardholders
 Display transaction information to merchants
 User Interface to input transaction amount
 Cardholder verification
 Online capabilities
 Store transaction data used for offline transaction clearing
In terms of hardware designing, it could be divided into the following 3 categories:
1． Programmable Contactless Readers (PCRs)

A PCR is a smart reader which is able to conduct all or partial kernel functions
including providing the contactless interface with the card and processing the
transaction data. A PCR is a programmable device to achieve alternative functions.
2． Combination of Terminal and Non-programmable Contactless Readers (Non-
PCRs)

All the features in a Non-PCR are hardcoded and cannot be re-programmed once
released. A Non-PCR is a separate entity connected with a terminal and it execute
instructions from the terminal to interact with card, control visual indicators, audio
indication and LCD display, and transfer outcomes as well.
Kernel functions are performed in the terminal.
3． Fully Integrated Terminal

Modules including contactless reading module are integrated in one device.

The design described in this document is based on a physical architecture that is

along the lines of Fully Integrated Terminal; however it is not intended to be
prescriptive.
June 2023 Page 11
© 2023 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.
2 POS System EMV Contactless Book C-7
1.5 Overview Kernel 7 Spec v2.11

The logical partitioning of the Fully Integrated Terminal is illustrated Figure 2-1.

Terminal Entry Point

Kernel 1

EMV Mode Kernel 2

Kernel 3

Kernel 4

Kernel 5
User
Interface Kernel 6

Kernel 7
Peripheral

Exception
Files

Others

Figure 2-1 Logical Architecture

The three main components in the above figure are frequently used in this
specification and each of them is responsible for specific functions as described
below:
Terminal – within this specification, the Terminal is a term embraces a range of
devices that provide the interaction for card acceptance at physical locations. The
Terminal hosts the user interface for card holder and merchant, Payment System
network connectivity and peripheral devices such as PIN pads and receipt printers.
Entry Point – see Book A and Book B.
Kernel – the Kernel within this specification refers to the Kernel 7 unless the word is
followed by a specific number.

Page 12 June 2023

© 2023 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 Book C-7 3 Processing Overview
Kernel 7 Spec v2.11 3.1 General Description

3 Processing Overview

3.1 General Description

Entry Point activates Kernel7 once completing Application Selection and passes the
control to the Kernel. The subsequent processing will be completed jointly by the
Kernel and Card. When the control transferred from Entry Point to the Kernel, Entry
Point shall provide transaction data, relevant configuration parameters and FCI
information returned in Application Selection. The EMV Mode supported by Kernel 7
is an optimization of EMV full transaction processing and command sequences to
guarantee the time that the cardholder holds the payment card close to the terminal
be as minimal as possible. Meanwhile, it supports the same data authentication
working in EMV full procedures, which allows for a quick transaction with a required
security level.
Kernel 7 possesses the following characteristics compared with EMV full processing:
1） Kernel 7 supports Online PIN, signature and CDCVM as cardholder verification
methods;

2） If Offline Data Authentication is performed, it is performed by the Kernel and

there’s no requirement of card’s presences in the communication field.

Once the Kernel completes its processing, it shall output the transaction Outcome to
Entry Point. Meanwhile the control will be transferred from the Kernel to Entry Point
for further handling, which starts from initiating an appropriate Start point based on
the Outcome and parameters in the Outcome. (Start point refers to different stages of
Entry Point in EMV contactless specification, including Start A, Start B, Start C and
Start D. Refer to Book A: Architecture and General Requirements for details).
Kernel 7 includes the following steps:
 Kernel Activation (Mandatory)

 Application Initiation (Mandatory)

 Read Application Data (Conditional, if the transaction is authorised offline)

 Offline Data Authentication (Mandatory if the transaction is authorized offline.

Optional if the transaction is authorized online)

 Online Processing (Conditional, if the transaction is authorized online)

 Transaction completion (Mandatory)

June 2023 Page 13

© 2023 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.
3 Processing Overview EMV Contactless Book C-7
3.2 Overview of Transaction Processing Kernel 7 Spec v2.11

Kernel 7 should support Payment Account Reference ("9F24") without disruption to

the terminal processing. Kernel 7 should be capable of reading PAR data.

3.2 Overview of Transaction Processing

3.2.1 Kernel Activation

Entry Point activates the Kernel once completing application selection, transfers
transaction processing control to the Kernel and provides card information as well as
transaction information to the Kernel for further use. On Kernel activation, the
interaction between the Kernel and the card has been established and the connection
will be maintained until the Kernel returns an Outcome to Entry Point.

Entry Point’s output to the Kernel includes the pre-processing results, the picked
combination profile, transaction data and configuration parameters. All these
information passed to the Kernel are crucial input for Transaction processing. These
data include the following elements:

 Transaction Amount;

 Terminal Transaction Qualifiers (TTQ) (Pre-configured in the Terminal which

will be reset in Entry Point pre-processing);

 Terminal Unpredictable Number;

 Copy of TTQ (Reset in Entry Point pre-processing)

 FCI of the selected application in pre-processing;

3.2.2 Application Initialization

Once the Kernel receives the copy of TTQ from Entry Point, it shall do the following
process:

1) Special readers such as transit acceptance terminals that support Offline Data
Authentication for online authorisation, check the presence and Byte 1 bit 7 of
DF61 in Select AID response:

If DF61 is not returned or Byte 1 bit 7 of the returned DF61 is "0", reset
the copy of TTQ Byte 1 bit 7 to "1" and continue with non-EMV
processing. This is out of scope of this specification. For further
information, please refer to your payment system for implementation guide.

Else (Byte 1 bit 7 of the returned DF61 is "1"), reset the copy of TTQ
Byte 1 bit 7 to "0", reset the copy of TTQ Byte 1 bit 1 to "1", reset the
copy of TTQ Byte 1 bit 6 to "1", reset the copy of TTQ Byte 2 bit 8 to "1".

2) Reset the copy of TTQ Byte 3 bit1 - 6 and bit 8 to “0”;

Page 14 June 2023
© 2023 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 Book C-7 3 Processing Overview
Kernel 7 Spec v2.11 3.2 Overview of Transaction Processing

3) Reset the copy of TTQ Byte 4 bit 8 to "1".

See Table 3-1 for the definition of TTQ supported by this specification. If not specified,
the TTQ in subsequent context refer to TTQ reset in this step.

The Kernel informs the card of the start of transaction by issuing GET PROCESSING
OPTIONS (GPO) command, and includes any data that the card requests in PDOL
during pre-processing.

The card provides transaction disposition in GPO response. If the card requests the
transaction to be authorized offline, the card shall generate dynamic signature data
and Fast Dynamic Data Authentication (fDDA) shall be performed to complete the
transaction..

If the returned Application Cryptogram is Offline Authorization, the Kernel shall read
card data according to Application File Locator (AFL) returned during application
initialization. Details of Read Record can be found in section 3.2.3. Multiple Read
Record message exchanges may happen until the last record is transferred before the
card leaves the field.

If Application Cryptogram is Online Authorization, the Kernel may or may not perform
Offline Data Authentication. If the kernel performs Offline Data Authentication, it will
read application data. Details of Online Processing can be found in section 3.2.5. Card
may leave the field once returning GPO response.

Table 3-1 Terminal Transaction Qualifiers

Byte Bit Definition

8 RFU1

1 – Full transaction flow in Contactless interface

Support
7
0 – Full transaction flow in Contactless interface
Not Support
1
1 – EMV Mode Supported
6
0 – EMV Mode Not supported

1 – Full transaction flow in contact interface

Support
5
0 –Full transaction flow in contact interface Not
Support

1
All RFU bits and bytes shall be set to zero unless explicitly specified otherwise.
June 2023 Page 15
© 2023 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.
3 Processing Overview EMV Contactless Book C-7
3.2 Overview of Transaction Processing Kernel 7 Spec v2.11

Byte Bit Definition

1 – Offline-only terminal
4
0 – Online-capable terminal

1 – Online PIN Supported

3
0 – Online PIN Not Supported

1 – Signature Supported
2
0 – Signature Not Supported

1 – Offline Data Authentication for Online

Authorisation Supported
1
0 – Offline Data Authentication for Online
Authorisation Not Supported

1 – Request Online cryptogram

8
0 – No Online cryptogram

2 1 –CVM Requested
7
0 – No CVM Requested

6-1 RFU

RFU
8

1- Consumer Device CVM Supported

3
0- Consumer Device CVM Not Supported
7

RFU
6-1

8 1 –fDDA v1.0 Supported

4
7-1 RFU

3.2.3 Read Application Data

Read Application Data Request shall be performed in offline transactions and may be
performed in online transactions. Read Application Data step is followed with Offline
Data Authentication.

Page 16 June 2023

© 2023 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 Book C-7 3 Processing Overview
Kernel 7 Spec v2.11 3.2 Overview of Transaction Processing

If the card requests offline authorization, it shall return AFL in the GPO response. The
Kernel uses READ RECORD command to retrieve the card data according to Short
File Identifier (SFI) and record number in AFL.

The Electronic Cash (EC) balance will not be updated in a persistent memory until the
last record is read by the Kernel. Once the last record is sent to the Kernel, the card
may leave the field and the Kernel performs Offline Data Authentication. Details of
Offline Data Authentication can be found in section 3.2.4.

3.2.4 Offline Data Authentication

Offline Data Authentication shall be supported by Offline-capable terminals and can be
performed in both online and offline transaction. fDDA is used to verify the dynamic
signature and authenticate the data from the card. fDDA is the Dynamic Data
Authentication(DDA) specifically used in contactless interface which not only to
guarantee that the card data has not been broken or manipulated since issued, but
also to confirm the legitimacy of critical ICC- resident/generated data and data received
by the terminal. fDDA precludes the counterfeiting of any such fake card. In order to
perform fDDA in offline transaction, the Kernel shall be capable to quickly shield SDA
support function when necessary. Once SDA is shielded, transactions could not be
approved offline unless the card supports fDDA.

Special readers such as transit acceptance terminals support Offline Data

Authentication for online authorisation. Offline Data Authentication feature is an
implementation option. Please refer to your payment system for implementation guide
including additional processing upon failure of Offline Data Authentication.

fDDA is different from standard DDA used in full flow2 for the following aspects:

 Instead of using INTERNAL AUTHENTICATE Command, the card generates

Dynamic signature on receiving GPO command. DDOL is not supported by
Kernel7.

 The result of fDDA verification is not stored in Terminal Verification Results

(TVR) or sent to Issuer in online message.

There are two versions of fDDA including version00 and version01 and an offline-
capable Kernel shall only support version 01. All the fDDA in this specification refer to
version01 by default unless explicitly specified otherwise.

2
Full flow refers to the EMV contact flow.
June 2023 Page 17
© 2023 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.
3 Processing Overview EMV Contactless Book C-7
3.2 Overview of Transaction Processing Kernel 7 Spec v2.11

3.2.5 Online Processing

If the card’s transaction disposition indicates an Online Authorization in the GPO
response, the Kernel sends an Online Request Outcome with parameters set
appropriately and clearing data as well (see 4.5.2). Online–capable terminal perform
online processing once Entry Point receives the outcome and alter the transaction
disposition to Declined Outcome with parameters if it failed to go online .(see 4.5.4)

Requirement – Online Authorization

3.2.5.1 The Kernel shall apply the following principles when performing online
authorization:
If TTQ Byte 1 bit 4 is "0", meaning the terminal is an Online-capable
terminal,

then the Kernel shall provide an Online Request Outcome, and

transfers the clearing data to Entry Point (see 4.5.2 for parameter
configuration) to perform an online transaction.
Else the Kernel declines the transaction with a Declined Outcome (see
4.5.4).

The terminal sends an authorisation request to the issuer host. Online Processing
allows the issuer host to review to approve or decline transactions using the issuer’s
host based risk management parameters.( Risk management in issuer host is out of
this specification.) If the issuer approves the transaction, the account will be updated
in the host whilst the EC balance on the card remains unchanged.

On receiving the decision from the issuer, the terminal displays the transaction
disposition to the cardholder. The transaction is considered as completed and the
Kernel will no longer be re-activated until next transaction.

3.2.6 Transaction Completion

From Kernel's perspective, an Outcome provided to Entry Point is considered as the
last step indicating the transaction is completed. The outcomes may be one of the
followings:

 Approved

 Online Request

 Try Again

 Declined

 Try Another Interface

 Select Next
Page 18 June 2023
© 2023 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 Book C-7 3 Processing Overview
Kernel 7 Spec v2.11 3.3 General Transaction Flow

 End Application

See 4.5 for details.

3.3 General Transaction Flow

Figure 3-1 illustrates a sample of a complete transaction in EMV Mode.

Before handing over the control to the Kernel, Entry Point finishes the pre-processing
(Start A), followed with establishing contactless communication connection (Start B),
then selects combination (Start C) and ends with activating Kernel (Start D).

The Kernel handles the interaction with the card until the transaction disposition has
been provided to Entry Point, attached with the necessary parameters and clearing
data if any.

Entry Point takes over the outcomes with the parameters and proceed with the rest of
the procedure including Online processing, CVM and transaction disposition display
without re-starting the Kernel.

June 2023 Page 19

© 2023 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.
3 Processing Overview EMV Contactless Book C-7
3.3 General Transaction Flow Kernel 7 Spec v2.11

EntryPonit
Performing the sequence of
StartA,StartB,StartC and StartD

Kernel processing

Procedures
required if
requested
Application
initialization

Normal
flow Exceptional
flow

Read application TC ARQC

data

fDDA AAC
verification
Read application data
fDDA verification

fDDA verification
No
succeeded

Yes

Transaction Transaction Online Other

approved declined request situations

EntryPoint Start A Start B Start C Start D

Figure 3-1 Sample of EMV Mode Transaction Flow

Page 20 June 2023

© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.1 Application Initialization

4 Transaction Processing

4.1 Application Initialization

4.1.1 Input
The input of Application Initialization includes the data passed from Entry Point which
is the result of pre-processing, the data can be found in 3.2.1.

Table 4-1 illustrates response of SELECT AID command which includes the FCI
template of the selected application:

Table 4-1 Response of SELECT AID

Tag Value Existence

‘6F’ FCI Module M

‘84’ DF name M

‘A5’ Special module for FCI data M

‘9F38’ PDOL M

‘50’ Application tag O

‘87’ Application priority indicator O

‘5F2D’ Preferred language O

‘9F11’ Issuer Code Table Index O

‘9F12’ Application Priority Name O

‘BF0C’ Issuer Discretionary data (FCI) O

One or more additional

(special) data elements from
‘xxxx’ O
application provider, issuer
or IC card provider

June 2023 Page 21

© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.1 Application Initialization Kernel 7 Spec v2.11

4.1.2 Commands
The Kernel uses GPO command in Application Initialization. The format of GPO
command conforms to [EMV 4.3 Book 3].

Definition and Scope

The GET PROCESSING OPTIONS command initiates the transaction within the
ICC.

Command Message

Table 4-2 GPO Command Message

Code Value

CLA “80”

INS “A8”

P1 “00”; all other values are RFU

P2 “00”; all other values are RFU

Lc var.

Processing Options Data Object

Data
List (PDOL) related data

Le “00”

Data Field Sent in the Command Message

The data field of the command message contains all the Kernel data requested in the
PDOL returned during pre-processing in Entry Point.

Data Field Returned in the Response Message

The coding of the data object shall be according to Format 2 described in [EMV 4.3
Book3] see 6.5.8.4.

Page 22 June 2023

© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.1 Application Initialization

4.1.3 Flow Chart

GPO
Processing

PDOL exists No

Yes

Return application
“9F66” exists in PDOL No
selection

Yes

TTQ resetting

Send GPO command

Card responds to GPO No Try Again

Yes

SW1 SW2 =‘9000’, and format No SW1SW2=‘6986’

correct? No

Yes
Yes
Try Again
Issuer Application Data
(“9F10”) exists in GPO No
Response

Yes

Application Cryptogram ARQC、AAC

TC
Mandatory-data check (AIP, ATC, AFL, Mandatory-data check (AIP, ATC, Track 2
Application Cryptogram) equivalent data, Application Cryptogram)

Data element
missing

Subsequent Yes Terminate transaction

processings

Figure 4-1 GPO Processing

June 2023 Page 23

© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.1 Application Initialization Kernel 7 Spec v2.11

4.1.4 Kernel Processing

Requirement – PDOL Check

4.1.4.1 The Kernel shall check the existence of PDOL and Terminal Transaction
Qualifiers (Tag "9F66"):

If PDOL doesn't exist in the FCI of the selected application which is passed
over from Entry Point,

Then the Kernel shall terminate the processing and select next
application in the candidate list by providing a Select Next Outcome,
see 4.5.6.

Else continue to check the existence of Terminal Transaction Qualifiers

(Tag ‘9F66’) in PDOL.

If exists,

Then the Kernel continues with TTQ resetting, see 4.1.4.2.

Else the Kernel shall terminate the processing and select next
application in the candidate list by providing a Select Next Outcome,
see 4.5.6.

Requirement – TTQ Resetting

4.1.4.2 The Kernel shall reset the copy of TTQ passed from Entry Point on
Kernel Activation
: Set the copy of TTQ Byte 4 bit 8 to "1".

Requirement – Processing of Status Code

4.1.4.3 The Kernel shall check SW1 SW2 in GPO response:

If any L1 error3 occurs,

Then the Kernel shall terminate the processing by providing a Try

Again Outcome, which will remind the cardholder to represent the card,
see 4.5.3.

3
L1 errors can be one of the following: timeout, protocol error or transmission error. See [Level
1 Specifications for Payment Systems, EMV Contactless Interface Specification ] for
details.
Page 24 June 2023
© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.1 Application Initialization

Requirement – Processing of Status Code

If SW1 SW2 does NOT equal to "9000",

If SW1 SW2 equals to “6986”

Then the Kernel shall terminate the processing by providing a Try

Again Outcome, which will remind the cardholder to represent the card,
see 4.5.8.

Else If TTQ Bit 5 Byte 1 is "1", indicating Contact interface is

supported,

or Magstripe is supported in the terminal,

Then the Kernel shall terminate the processing by providing a Try

Another Interface Outcome, which will remind the cardholder to
conduct the transaction in another interface. The Kernel sets the
Parameters as a result of the following check:

If the terminal supports contact interface,

Then the Kernel sets Alternate Interface Preference to Contact

Chip.

Else the Kernel sets Alternate Interface Preference to Mag-stripe.

Else the Kernel shall terminate the processing by providing an End

Application Outcome, see 4.5.7.

If SW1 SW2 equals to "9000",

Then the Kernel checks the data format of GPO response. Only Format
2 of GPO response is supported, see [EMV 4.3 Book3] see 6.5.8.4..

If there is any format error,

Then the Kernel shall terminate the processing by providing an

End Application Outcome, see 4.5.7

Else the Kernel continues with The Card’s Transaction Disposition, see
4.1.4.4.

June 2023 Page 25

© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.1 Application Initialization Kernel 7 Spec v2.11

Requirement –Transaction Disposition

4.1.4.4 The Card’s transaction disposition is included in the Cryptogram
Information Data (Tag “9F27”). If the card does not return CID, the
Kernel shall:
- Initialise CID to ‘00’
- Set CID bits 8-7 to the value of Issuer Application Data(Tag
“9F10”) Byte 5 bit 6-5

If the card returns an ARQC (CID bit8-7 = ‘10’), indicting an online

transaction is requested.

Then the Kernel continues with mandatory-data check for online

request, see 4.1.4.5.

If the card returns an AAC (CID bit8-7=’00’), indicting an offline decline.

Then the Kernel continues with mandatory-data check for offline

decline, see 4.1.4.5.

If the card returns a TC (CID bit8-7=’01’), indicting an offline approval.

Then the Kernel continues with mandatory-data check for offline

approval, see 4.1.4.6.

Page 26 June 2023

© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.1 Application Initialization

Requirement – Mandatory-Data Check

4.1.4.5 Table 4-3 illustrate the data returned in GPO response if the card’s
transaction disposition is an ARQC without Offline Data Authentication
or AAC, Table 4-5 illustrates the data returned in GPO reponse if the
card's transaction disposition is an ARQC with Offline Data
Authentication. Under these situations, the Kernel shall perform the
followings:

If the card’s disposition is ARQC (with or without Offline Data

Authentication), Then

If any Mandatory data listed in Table 4-3 and Table 4-5 is absent in the
GPO response,

Then the Kernel shall terminate the Kernel processing by

providing an End Application Outcome, see 4.5.7.

Else If AFL is returned (ARQC with Offline Data Authentication),

Then the Kernel continues with AFL format check, see 4.1.4.7.

The Kernel perform the Online Processing, see 3.2.5

If the card’s disposition is AAC.

If any Mandatory data listed in Table 4-3 is absent,

Then the Kernel shall terminate the processing by providing an

End Application Outcome, see 4.5.7.

Else the Kernel declines the transaction by providing a Declined

Outcome, see 4.5.4

June 2023 Page 27

© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.1 Application Initialization Kernel 7 Spec v2.11

Requirement – Mandatory-Data Check

4.1.4.6 Table 4-4 illustrate the data returned in GPO response if the card’s
transaction disposition is a TC, the Kernel shall perform the followings:

If the card’s transaction disposition is TC,

If any Mandatory data elements listed in Table 4-4 is absent,

Then the Kernel shall terminate the processing by providing an

End Application Outcome, see 4.5.7.

Else the Kernel continues with AFL format check, see 4.1.4.7.

4.1.4.7 Table 4-6 illustrates the definition and format of AFL. The Kernel shall
perform the followings:

If No Entry exists in AFL,

OR any one or more of the following format errors occurs:

 An SFI of 0 or 31;

 A starting record number of 0;

 An ending record number less than the starting record number

(byte 3 < byte 2).

 Number of records participating in offline data authentication

greater than the number of records (byte 4 > byte 3 - byte 2 + 1).
Then the Kernel shall terminate the processing by providing an End
Application Outcome, see 4.5.7.
Else the Kernel continues with Read Application Data, see 4.2.

Page 28 June 2023

© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.1 Application Initialization

Table 4-3 GPO Response Data if The Card’s Transaction Disposition is an

ARQC （without Offline Data Authentication） or AAC

Mandatory (M)
Tag Optional (O) Data Element Name
Conditional (C)

“82” M AIP

“9F36” M ATC

“57” M Track 2 Equivalent Data

“9F10” M Issuer Application Data.

“9F26” M Application Cryptogram

“9F27” M Cryptogram Information Data

Product Identification Information

C
“9F63” This data can either be retrieved in GPO or
If exists in card
READ RECORD

C
“5F34” Application PAN Sequence Number
If exists in card

C
“9F6C” Card Transaction Qualifiers
If exists in card

Available Offline Spending Amount.

Only if the Available Offline Spending
Amount("9F5D") is personalized to 1, the card
returns this data in GPO response or can be
C
retrieved by READ RECORD. Meanwhile, the
If the Available
“9F5D” Card Additional Processing (Byte 1 bit 1) shall be
Offline Amount
personalised to 1 to indicate that this amount will
display is allowed
be calculated and included in all contactless
transactions. Personalization of Available Offline
Spending Amount to 1 also means that this data
can be retrieved by GET DATA command.

C
"9F24" Payment Account Reference
If exists in card

June 2023 Page 29

© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.1 Application Initialization Kernel 7 Spec v2.11

Mandatory (M)
Tag Optional (O) Data Element Name
Conditional (C)

Cardholder Name
If the length of Cardholder Name is less than
“5F20” or equal to 26 bytes, "5F20" will be returned; if
or O the length of Cardholder Name is more than 26
“9F0B” bytes, "9F0B" will be returned.
This data can either be retrieved in GPO or
READ RECORD

Partner Proprietary Data

“9F7C” O This data can either be retrieved in GPO or
READ RECORD

C
“9F25” If using Token The last 4 numbers of PAN
instead of PAN

C
“9F19” If using Token Token requestor identifier
instead of PAN

Table 4-4 GPO Response Data if The Card’s Transaction Disposition is a TC

Mandatory (M)
Tag Data element name
Conditional (C)

“82” M AIP

“94” M AFL

“9F36” M ATC

“9F26” M Application Cryptogram

“9F10” M Issuer application data

“9F27” M Cryptogram Information Data

Page 30 June 2023

© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.1 Application Initialization

Mandatory (M)
Tag Data element name
Conditional (C)

C
If Track 2 Equivalent
“57” Data is not part of Track 2 Equivalent Data
Signed Static
Application Data.

C
“5F34” Application PAN Sequence Number.
If exists in card

Signed Dynamic Application Data

C
“9F4B” This data can either be retrieved in GPO or
If fDDA is supported.
READ RECORD

C
“9F6C” Card Transaction Qualifiers
If exists in card

Available Offline Spending Amount.

Only if the Available Offline Spending
Amount("9F5D") is personalized to 1, the card
returns this data in GPO response or can be
C
retrieved by READ RECORD. Meanwhile, the
If the Available
“9F5D” Card Additional Processing (Byte 1 bit 1) shall
Offline Amount
be personalised to 1 to indicate that this amount
display is allowed.
will be calculated and included in all contactless
transactions. Personalization of Available Offline
Spending Amount to 1 also means that this data
can be retrieved by GET DATA command.

C
"9F24" Payment Account Reference
If exists in card

Partner Proprietary Data

“9F7C” O This data can either be retrieved in GPO or
READ RECORD
C
“9F25” If using Token Last 4 Digits of PAN
instead of PAN
C
“9F19” If using Token Token Requestor ID
instead of PAN

June 2023 Page 31

© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.1 Application Initialization Kernel 7 Spec v2.11

Table 4-5 GPO Response Data if The Card’s Transaction Disposition is an

ARQC with Offline Data Authentication

Mandatory (M)
Tag Optional (O) Data Element Name
Conditional (C)

“82” M AIP

“94” M AFL

“9F36” M ATC

C
If Track 2
Equivalent Data is
“57” Track 2 Equivalent Data
not part of Signed
Static Application
Data.

“9F10” M Issuer Application Data.

“9F26” M Application Cryptogram

“9F27” M Cryptogram Information Data

C Signed Dynamic Application Data

“9F4B” If fDDA is This data can either be retrieved in GPO or
supported. READ RECORD

Product Identification Information

C
“9F63” This data can either be retrieved in GPO or
If exists in card
READ RECORD

C
“5F34” Application PAN Sequence Number
If exists in card

C
“9F6C” Card Transaction Qualifiers
If exists in card

Page 32 June 2023

© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.2 Read Application Data

Mandatory (M)
Tag Optional (O) Data Element Name
Conditional (C)

Available Offline Spending Amount.

Only if the Available Offline Spending
Amount("9F5D") is personalized to 1, the card
returns this data in GPO response or can be
C
retrieved by READ RECORD. Meanwhile, the
If the Available
“9F5D” Card Additional Processing (Byte 1 bit 1) shall be
Offline Amount
personalised to 1 to indicate that this amount will
display is allowed
be calculated and included in all contactless
transactions. Personalization of Available Offline
Spending Amount to 1 also means that this data
can be retrieved by GET DATA command.

C
"9F24" Payment Account Reference
If exists in card

Cardholder Name
If the length of Cardholder Name is less than
“5F20” or equal to 26 bytes, "5F20" will be returned; if
or O the length of Cardholder Name is more than 26
“9F0B” bytes, "9F0B" will be returned.
This data can either be retrieved in GPO or
READ RECORD

Partner Proprietary Data

“9F7C” O This data can either be retrieved in GPO or
READ RECORD

C
“9F25” If using Token The last 4 numbers of PAN
instead of PAN

C
“9F19” If using Token Token requestor identifier
instead of PAN

4.2 Read Application Data

Read Application Data can be performed in both online and offline transactions.

June 2023 Page 33

© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.2 Read Application Data Kernel 7 Spec v2.11

According to AFL in the GPO response, the Kernel reads the data contained in the
card to proceed fDDA verification and various functions including checking the
Application Expiration date and Exception File if any.

4.2.1 Input
Table 4-6 lists the data returned from the card in Application Initialization which will
be used in Read Application Data.

Table 4-6 Card Data used in Read Application Data

Data Object Description

Indicates the file location and range of records which

contain card data to be read by the Kernel. For each file
to be read, the AFL contains the following information:
 Byte 1 - Short File Identifier (a numeric file label)
 Byte 2 - Record number of the first record to be
Application File Locator read
(AFL)  Byte 3 - Record number of the last record to be
read
 Byte 4 - Number of consecutive records
containing data to be used in Offline Data Authentication
beginning with the first record to be read as indicated in
Byte 2.

4.2.2 Commands
The Kernel uses READ RECORD command in Read Application Data. The format of
READ RECORD command conforms to [EMV 4.3 Book 3].

Page 34 June 2023

© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.2 Read Application Data

4.2.3 Flow Chart

GPO processing

Read
Applica
tion
data

Read record
Mandatory process

L1 error Yes

Optional process It is the last record No

Yes
No

Save to Tearing
Transaction Log, and
remind cardholder to
represent the card

SW1 SW2=‘9000’? No

Yes

Data format error Yes

occurs

No

No Duplicated Tags Yes

returned

No

Same tag With the

one returned In GPO Yes
Response

No

It is the last record

Yes

Exception File
Processing

Offline
Data Terminate
Authent
transaction
ication

Figure 4-2 Read Application Data

June 2023 Page 35

© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.2 Read Application Data Kernel 7 Spec v2.11

4.2.4 Kernel Processing

Each file entry in AFL contains the information of consecutive records in the AEF. For
each record, the Kernel shall send a READ RECORD command until the last record is
retrieved. If there is more than one file entry in AFL, the Kernel repeats the steps until
all the entries have been process.

Requirement – L1 Errors in Reading Application Data

4.2.4.1 In case of L1 errors, the Kernel shall perform the followings:

If any L1 error occurs,

THEN the Kernel shall terminate the processing by providing a Try

Again Outcome, which will remind the cardholder to represent the card,
see 4.5.3.
Else the Kernel continues with Response Processing, see 4.2.4.2.

Requirement – Processing of READ RECORD Response

4.2.4.2 The Kernel shall process the READ RECORD Response:

If SW1 SW2 does NOT equal to ‘9000’,

Then the Kernel shall terminate the processing by providing an End

Application Outcome, see 4.5.7.
Else the Kernel performs Data Format check , see 4.2.4.3.

4.2.4.3 The Kernel shall check the data in READ RECORD response.

If any format error occurs in the response,

Then the Kernel shall terminate the processing by providing an End

Application Outcome, see 4.5.7.

Else the Kernel checks the data duplication, see 4.2.4.4.

Page 36 June 2023

© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.2 Read Application Data

Requirement – Processing of READ RECORD Response

4.2.4.4 The Kernel shall check the data duplication4 in response. Data
Duplication could happen between one data object returned in Read
Application Data and another returned in Application Initialization, or
between two data objects returned in Read Application Data.

If data duplication occurs,

Then the Kernel shall terminate the processing by providing an End

Application Outcome , see 4.5.7.

Else the Kernel continue with checking the application expiration date,
see 4.2.4.5.

4.2.4.5 Once the Kernel retrieves the Application Expiration Date (“5F24”), it
shall perform the followings:

If the current date obtained from the terminal is greater than the Application
Expiration Date (“5F24”), meaning the application is expired. The Kernel
shall do the following process:
If Card Transaction Qualifiers(“9F6C”), Byte 1 bit 4 value is “1”,
meaning Go Online if Application Expires,
Then the Kernel performs the Online Process, see 3.2.5, and
display "The application is expired, transaction is going online" on
screen.

Else the Kernel shall decline the transaction by providing a Declined

Outcome, see 4.5.4, and display "The application is expired,
transaction declined" on screen.

Else the Kernel perform the next step, see 4.2.4.6

4
The data objects with the same Tag value are considered as a duplication.
June 2023 Page 37
© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.2 Read Application Data Kernel 7 Spec v2.11

Requirement – Processing of READ RECORD Response

4.2.4.6 The Kernel shall see whether the current record is the last one to be
read.

If the current record is the last record,

If exception file exists in the terminal,

Then the Kernel performs exception file check, see 4.2.4.7..

Else the Kernel continues with Offline Data Authentication, see 4.3.

Else the Kernel reads the next record.

Requirement – Exception File

4.2.4.7 This is an optional feature which is done only if the exception file exists
in the terminal.

If the leftmost digits of PAN Number exists in the exception file5,

Then the Kernel declines transaction by providing a Declined

Outcome, see 4.5.4.

Requirement – Other Exception Handlings

4.2.4.8 If there exists any data object that in correct TLV format but undefined in
this specification,
Then the Kernel shall store them in memory for further use instead of
terminating the transaction.

5
There is no requirement in this specification for an exception file.
Page 38 June 2023
© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.2 Read Application Data

Requirement – Other Exception Handlings

4.2.4.9 If any one or more of the followings occurs, the Kernel shall store the
value and continue the transaction instead of terminating the transaction:
 The length of Cardholder Name (“5F20”) is not consistent with the
requirements specified in [EMV 4.3 Book3] Table A1.

 The length of Cardholder Name Extension (“9F0B”) is not consistent

with the requirements specified in [EMV 4.3 Book3] Table A1.

 Both Cardholder Name (“5F20”) and Cardholder Name Extension

(“9F0B”) are returned.

June 2023 Page 39

© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.3 Offline Data Authentication Kernel 7 Spec v2.11

4.3 Offline Data Authentication

The crucial requirement of a transaction over the contactless interface is the time that
the cardholder has to hold the card in the field. Dynamic Data Authentication used in
payment over the contactless interface is called fast Dynamic Data Authentication
(fDDA) which can be performed without the card’s presence in the field. This enables
the cardholder to remove the card just after Read Application Data and guarantee the
security of ICC transaction,

Only fDDA version 01 is supported in Kernel7.

4.3.1 Input
Table 4-7 lists the SDA-related data in the Kernel used for Offline Data
Authentication.

Table 4-7 Offline Data Authentication--Terminal Data

Data element Description

Identifies the Certificate Authority's public key in

Public Key Index (PKI) conjunction with the RID for use in offline static and
dynamic data authentication..

The Kernel uses CA Public Key to unlock the Issuer PK

CA Public Key
Certificate to recover the Issuer Public Key.

Part of AID (first 5 bytes), used to identify payment

Registered Application
systems. Identifies the application provider and the CA
Provider Identifier (RID)
public key in conjunction with PKI.

Table 4-8 illustrates all Card data used for the Kernel to decide whether to perform
SDA or fDDA.

Table 4-8 Offline Data Authentication--Card Data

Data element Description

Including indicators:
Application Interchange
 Byte 1 bit 7 indicates that the card supports SDA;
Profile (AIP)
 Byte 1 bit 6 indicates that the card supports fDDA.

June 2023 Page 40

© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.3 Offline Data Authentication

Data element Description

Used with the Registered Application Provider
Identifier (RID) to identify which Private Key was used
CA PKI to encrypt the Issuer PK Certificate and which
corresponding Public Key shall be used to recover the
Issuer PK Certificate.
Provided by the appropriate certification authority to
Issuer Public Key the card issuer. When the Kernel verifies this data
Certificate element, it authenticates the Issuer Public Key plus
additional data.
Issuer Public Key Provided by the issuer and used to retrieve signed
Exponent static application data and ICC PK certificate.
Issuer Public Key Includes the part of issuer public key which is not listed
Remainder in Issuer public key certificate
Part of AID (first 5 bytes), used to identify payment
Registered Application
systems. Identifies the application provider and the CA
Provider Identifier (RID)
public key in conjunction with PKI.
A signature used in the validation of the card’s static
Signature Static data. The SAD is signed with the Issuer Private Key a
Application Data (SAD) nd is placed on the card during the personalization
process.
This is an optional data which contains the tag of the
Application Interchange Profile (AIP) if it is to be
Static data authentication signed. Tags other than the tag of the AIP shall not be
tag list present in the SDA Tag List. The AIP shall be included
in the SDA Tag List if SDA, DDA, or CDA is supported.
This data element is used for SDA, DDA and CDA.
Data specified by Issuer and included in signed
ICC Dynamic Data
dynamic application data.
ICC dynamic number is the first data element of the
ICC Dynamic Number ICC dynamic data. The ICC dynamic number contains
a time-variant generated by the ICC.
ICC PK Certificate is created using the Issuer Private
Key and placed in the card during card
ICC PK Certificate
personalization. ICC PK Certificate contains the ICC
public key and a hash of static application data.
Used to recover the Signed Dynamic Application Data,
ICC PK Exponent
with the value of 3 or 65537.

June 2023 Page 41

© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.3 Offline Data Authentication Kernel 7 Spec v2.11

Data element Description

IC Card Public Key Part of the ICC PK which is not contained in the ICC
Remainder PK Certificate (if any)
Signed Dynamic The Signature generated by the card on receiving
Application Data GPO command.

4.3.2 Kernel Processing

Requirement – fDDA Version Check

4.3.2.1 The Kernel shall support fDDA.

If Kernel7 supports fDDA,

Then the Kernel shall check the fDDA version in the Card. See 4.3.2.2;

Else fDDA verification failed, and the Kernel continues with the subsequent
procedure in case that fDDA failed or not performed, see 4.3.2.5.

4.3.2.2 The card shall support fDDA.

If the Application Interchange Profile (AIP) indicates that the card supports
DDA (AIP Byte 1 bit 6 is "1"),

Then the Kernel performs fDDA data check. See 4.3.2.3;

Else fDDA verification failed, and the Kernel continues with the
subsequent procedure in case that fDDA failed or not performed, see
4.3.2.5.

Page 42 June 2023

© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.3 Offline Data Authentication

Requirement – fDDA Data Check

4.3.2.3 The Kernel is responsible to ensure that all fDDA related data exist.

Table 4-9 illustrates all the dynamic Kernel data to be hashed.

Card Authentication Related Data includes a card unpredictable number

and Card Transaction Qualifiers. As one of the Terminal Dynamic Data
elements, the card shall generate a card unpredictable number and pad the
Card Transaction Qualifiers into Card Authentication Related Data.
Note: If the Card Transaction Qualifiers is not placed in the card during
personalization, then the card shall set the value as zero for use in Card
Authentication Related Data.

Table 4-10 illustrates the data elements in ICC Dynamic Data.

If any data element listed in Table 4-9 and Table 4-10 is missing,

Then fDDA verification failed, and the Kernel continues with the
subsequent procedure in case that fDDA failed or not performed, see
4.3.2.5.
Else, the Kernel performs fDDA verification, see 4.3.2.4.

Table 4-9 Dynamic Kernel Data to be Hashed

Data element Tag Length Source

Unpredictable
9F37 4 bytes Kernel
number

Authorized
9F02 6 bytes Kernel
amount
Transaction
5F2A 2 bytes Kernel
currency code
Card Verification
9F69 Variable Card
Related Data

June 2023 Page 43

© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.3 Offline Data Authentication Kernel 7 Spec v2.11

Note: Card verification related data is variable-length data. Reader shall perform dynamic
signature authentication using the entire card verification related data returned by card.

Table 4-10 IC Card Dynamic Data to be Hashed

Tag Data element Length Source

Application
Transaction
9F36 2 bytes Card
Calculator
(ATC)

Requirement – fDDA Verification

4.3.2.4 The Kernel performs fDDA verification.
1. Obtain CA public key, this process conforms to Chapter 6.2 of [EMV
Book2].

2. Recover Issuer public key, this process conforms to Chapter 6.3 of

EMV Book2.

3. Recover IC card public key, this process conforms to Chapter 6.4 of

[EMV Book2].

4. Verify dynamic signature, this process conforms to Chapter 6.5 of

[EMV Book2], except the following contents:

If the Card Verification Related Data (Tag "9F69") is returned,

And the length of the Card Verification Related Data (Tag "9F69") is more
than or equal to 8 bytes and less than or equal to 16 bytes,

And the first byte of the Card Verification Related Data (Tag "9F69") is “01”,

then the Kernel continues with the following steps in fDDA verification;

Else fDDA verification failed, and the Kernel continues with the subsequent
procedure in case that fDDA failed or not performed, see 4.3.2.5.

If the cryptogram type is an ARQC,

then the kernel shall check the value of the Signed Data Format is '95'.
If it's not '95', the fDDA verification failed.

Page 44 June 2023

© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.3 Offline Data Authentication

Requirement – fDDA Verification

Dynamic Kernel data elements to be hashed shall not be specified in DDOL
(DDOL is an unidentifiable data in the Kernel), instead they are coded in
sequence as specified in Table 4-9.

If the card returns DDOL,

Then the Kernel ignores the data object, and shall not terminate the
transaction.

If the cryptogram type is not ARQC,

Then If fDDA verification is successful and,

Then the Kernel offline approve the transaction by providing an

Approved Outcome, see 4.5.1.

Else fDDA verification failed, and the Kernel continues with the
subsequent procedure in case that fDDA failed or not performed, see
4.3.2.5.

Note：In online transactions with offline data authorisation, the special terminals
may perform specific actions based on the results of fDDA verification on online
processing; this is out of the scope of this document.

Requirement – fDDA Failed or Not Performed

4.3.2.5 The issuer may request an Online processing if fDDA failed or not
performed besides terminating the transaction. The Kernel needs to
check with issuer’s intention on the further process.

If the Card Transaction Quality Byte 1 bit 6=‘1’ (Go Online if offline data
authentication fails and terminal is online capable)
And the TTQ Byte 1 bit 4 = ‘0’, indicating the terminal is online capable,

Then the Kernel goes for Online Processing, see 3.2.5 and the terminal
shall notify cardholder that the transaction is processing as well as
generate online message.
Else if the Card Transaction Quality Byte 1 bit 5 =’1’ (Terminate
Transaction and swith interface if full transaction flow in contact interface
supported.)
And the TTQ Byte 1 bit 5 = ‘1’ (Full transaction flow in contact interface
Supported)

June 2023 Page 45

© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.4 Cardholder Verification Kernel 7 Spec v2.11

Requirement – fDDA Failed or Not Performed

Then the Kernel shall terminate the transaction by providing a Try
Another Interface Outcome.
Else, fDDA verification fails, the Kernel declines transaction by providing
a Declined Outcome, see 4.5.4.
Note：In online transactions with offline data authorisation, the special
terminals may perform specific actions based on the results of fDDA verification
on online processing; this is out of the scope of this document.

4.4 Cardholder Verification

The kernel determines if a Cardholder Verification Method (CVM) is to be performed.
The CVMs that may be supported for Kernel 7 are Online PIN, Consumer Device CVM,
and Signature.
Note: A Consumer Device CVM is a CVM performed on, and validated by, the consumer’s
payment device, independent of the reader.

4.4.1 General Requirements

Terminal Implementation Requirements: With the exception of ATMs, Cardholder
Verification shall be implemented for Kernel7.
Note: ATMs may need to support an appropriate minimum level of cardholder verification, as
determined by the payment system or local law, regardless of the CVMs supported by the card.
As a consequence, ATMs are not subject to the Cardholder Verification processing
requirements of this specification.

Acquirer-Merchant Configure Requirements: The acquirer-merchant shall be able to

enable and disable the supported CVMs. However, support for the Consumer Device
CVM shall be enabled (TTQ byte 3 bit 7 is 1b).

4.4.2 CVM Processing

4.4.2.1 CTQ not returned by card

Page 46 June 2023

© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.4 Cardholder Verification

Requirement – CVM Check

The kernel checks CVM for the transaction

If the kernel requires a CVM, and the payment application does not
return the Card Transaction Qualifiers (CTQ, Tag ‘9F6C’),
Then the kernel shall
If the reader supports Signature
Then the kernel shall request a signature in the
Outcome.
If the reader supports only the Consumer Device CVM and
Online PIN
Then the kernel shall request Online PIN in the
Outcome.
If the reader supports only the Consumer Device CVM,
Then the kernel shall provide Declined Outcome with
CVM parameter set to N/A

4.4.2.2 CTQ returned by card

June 2023 Page 47

© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.4 Cardholder Verification Kernel 7 Spec v2.11

Requirement – CVM Check

If the card returns Card Transaction Qualifiers (“9F6C”), the kernel shall examine
the CTQ to determine the CVM to be performed:

If Online PIN Required by card (CTQ byte 1 bit 8 is 1)and Online PIN
supported by reader:
Then the Kernel shall provide an Online Request Outcome with CVM
parameter set to Online PIN.

Else if (Online PIN not required or not supported) and Consumer Device
CVM Performed by card (CTQ byte 2 bit 8 is 1),
If the Card Authentication Related Data(“9F69”) was returned during
the transaction, then

If Card Authentication Related Data bytes 6-7 match CTQ bytes 1-

2 (respectively),

Then the kernel shall set the CVM parameter in the Outcome to
Confirmation Code Verified.

Else the kernel shall provide Declined Outcome with CVM

parameter set to N/A;

Else (the Card Authentication Related Data(“9F69”) was not returned

during the transaction),then

If the cryptogram type is an ARQC,

Then the kernel shall provide an Online Request Outcome with

CVM parameter set to Confirmation Code Verified.

Else the kernel shall provide Declined Outcome with CVM

parameter set to N/A;

Else if Signature Required (CTQ byte 1 bit 7 is 1) and the reader supports
Signature (TTQ byte 1 bit 2 is 1),
Then the kernel shall set the CVM parameter in the Outcome to Obtain
Signature.
Else (No CVM is indicated in the CTQ)
If the reader requires a CVM

Then the kernel shall set the Decline Required by Reader Indicator to
1,

Else the kernel shall set the CVM parameter set to N/A;

Page 48 June 2023

© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.5 Outcome

4.5 Outcome
Outcomes are the important information transferred from the Kernel to Entry Point, with
parameters set, instructing the terminal for further processing. An Outcome indicates
the Kernel’s transaction disposition, and the parameters are additional instructions for
terminal. The parameters include information to be displayed on the screen, clearing
data for online transactions and Approved transactions, cardholder verification method,
power supply for the field, etc.
The value and meaning of Outcomes and parameters can be found in Chapter6 of
[EMV Contactless BookA].

This chapter describes specific Outcomes and corresponding parameters used in

Kernel7.

4.5.1 Approved
If the transaction is approved offline, then Kernel returns an Approved Outcome.

Requirement – APPROVED Outcome

4.5.1.1 The kernel shall provide an Approved Outcome with the following
parameters:
 Start: N/A
 Online Response Data: N/A

 CVM: as defined in 4.4.2

 UI Request on Outcome Present: Yes

o Message Identifier: ‘03’ (“Approved”)

o Status: Card Read Successfully

o 6(Value Qualifier: “Balance”

o Value: Available Offline Transaction Amount(’9F5D’)

o Currency Code: Transaction Currency Code)

6
If the Available Offline Spending Amount is returned, this will be displayed in Value Qualifier.
This applies to all Outcomes.

June 2023 Page 49

© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.5 Outcome Kernel 7 Spec v2.11

Requirement – APPROVED Outcome

 UI Request on Restart Present: No

 Data Record Present: Yes7

 Discretionary Data Present: No

 Alternate Interface Preference: N/A

 Receipt: Yes8

 Field Off Request: N/A

 Removal Timeout: zero

The Kernel shall provide clearing data in the Approved outcome, see 0 for

the data elements:

4.5.2 Online Request

If it is an online transaction, then the Kernel returns an Online Request Outcome.

7
If Data Record Present is “Yes”, then Kernel shall provide clearing data. See Annex C for
clearing data. This applies to all Outcomes.
8
If card returns Available Offline Spending Amount, the value shall be displayed on the receipt.
This applies to all Outcomes.

Page 50 June 2023

© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.5 Outcome

Requirement – ONLINE REQUEST Outcome

4.5.2.1 The kernel shall provide an Online Request Outcome with the
following parameters:
 Start: N/A

 Online Response Data: N/A

 CVM: as defined in 4.4.2

 UI Request on Outcome Present: Yes

o Message Identifier: ‘1B’ (“Authorizing, Please Wait”)

o Status: Card Read Successfully

o (Value Qualifier: “Balance”

o Value: Available Offline Transaction Amount(’9F5D’)

o Currency Code: Transaction Currency Code )

 UI Request on Restart Present: No

 Data Record Present: Yes

 Discretionary Data Present: No

 Alternate Interface Preference: N/A

 Receipt: N/A

 Field Off Request: N/A

 Removal Timeout: zero

The terminal goes online instructed by Entry Point on receiving Online Request
Outcome.

On receiving the response from the host, the Kernel will not be invoked again. Instead,
the terminal will process the transaction disposition based on the online authorization
to complete the transaction and display the corresponding information to the
cardholder.

June 2023 Page 51

© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.5 Outcome Kernel 7 Spec v2.11

If the Kernel requests an online transaction and the terminal failed to go online, then
the terminal declines transaction. This won’t restart the Kernel, however the terminal
will interact with the cardholder on the transaction disposition.

If the final disposition is Approved, the terminal will use data transmitted from the
Kernel in Outcome parameters to prepare clearing document, clearing data is shown
in 0:

4.5.3 Try again (1)

If Kernel requests the cardholder to re-present the card in any case, the Kernel
returns a Try Again Outcome.

Page 52 June 2023

© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.5 Outcome

Requirement – TRY AGAIN Outcome

4.5.3.1 The kernel shall provide a Try Again Outcome with the following
parameters:
 Start: B

 Online Response Data: N/A

 CVM: N/A

 UI Request on Outcome Present: Yes

o Message Identifier: ‘21’ (“Present Card Again ”)

o Status: Processing Error

o Hold Time: 13

o Language Preference: ‘en’

 UI Request on Restart Present: Yes

o Status: Ready to Read

 Data Record Present: No

 Discretionary Data Present: No

 Alternate Interface Preference: N/A

 Receipt: No

 Field Off Request: 13

 Removal Timeout: zero

The cardholder is requested to present the card again if the Kernel provides a Try
Again Outcome.

4.5.4 Declined
If transaction is declined offline, then the Kernel returns a Decline Outcome:

June 2023 Page 53

© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.5 Outcome Kernel 7 Spec v2.11

Requirement – DECLINED Outcome

4.5.4.1 The kernel shall provide a Declined Outcome with the following
parameters:
 Start: N/A

 Online Response Data: N/A

 CVM: N/A

 UI Request on Outcome Present: Yes

o Message Identifier: ‘07’ (“Not Authorised”)

o Status: Card Read Successfully

 UI Request on Restart Present: No

 Data Record Present: No

 Discretionary Data Present: No

 Alternate Interface Preference: N/A

 Receipt: No

 Field Off Request: N/A

 Removal Timeout: zero

4.5.5 Try Another Interface

If the Kernel requests to try another interface, is shall return a Try Another Interface
Outcome.

Page 54 June 2023

© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.5 Outcome

Requirement – TRY ANOTHER INTERFACE Outcome

4.5.5.1 The kernel shall provide a Try Another Interface Outcome with the
following parameters:
 Start: N/A

 Online Response Data: N/A

 CVM: N/A

 UI Request on Outcome Present: Yes

o Message Identifier: ‘18’ (“Please insert or swipe card”)

o Status: Ready to Read

 UI Request on Restart Present: No

 Data Record Present: No

 Discretionary Data Present: No

 Alternate Interface Preference: Can be Contact Chip or

Magstripe based on terminal capabilities.

 Receipt: N/A

 Field Off Request: N/A

 Removal Timeout: zero

4.5.6 Select Next

In any case that there is exception which requires go back to application selection for
another application, the Kernel shall return a Select Next Outcome to start another
combination selection.

June 2023 Page 55

© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.5 Outcome Kernel 7 Spec v2.11

Requirement – SELECT NEXT Outcome

4.5.6.1 The kernel shall provide a Select Next Outcome with the following
parameters:
 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

4.5.7 End Application

If the transaction is to be terminated, the Kernel returns an End Application
Outcome, with the parameter Start to N/A.

Page 56 June 2023

© 2023 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 Book C-7 4 Transaction Processing
Kernel 7 Spec v2.11 4.5 Outcome

Requirement – END APPLICATION Outcome

4.5.7.1 The kernel shall provide a Select Next Outcome with the following
parameters:
 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

4.5.8 Try again (2)

If the kernel receives SW1 SW2 = ‘6986’ in response to the GPO command then the
kernel shall provide a Try Again Outcome with the following parameters.

June 2023 Page 57

© 2023 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.
4 Transaction Processing EMV Contactless Book C-7
4.5 Outcome Kernel 7 Spec v2.11

Requirement – TRY AGAIN Outcome

4.5.8.1 The kernel shall provide a Try Again Outcome with the following
parameters:
 Start: B

 Online Response Data: N/A

 CVM: N/A

 UI Request on Outcome Present: Yes

o Message Identifier: ‘20’ (“See your mobile device for
instructions”)

o Status: Processing Error

o Hold Time: any value of 10, 11, 12, 13, 14 and 15

o Language Preference: ‘en’

 UI Request on Restart Present: Yes

o Status: Ready to Read

 Data Record Present: No

 Discretionary Data Present: No

 Alternate Interface Preference: N/A

 Receipt: No

 Field Off Request: any value of 10, 11, 12, 13, 14 or

15

 Removal Timeout: zero

Page 58 June 2023

© 2023 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 Book C-7 Annex A. Data Dictionary
Kernel 7 Spec v2.11

Annex A. Data Dictionary

This annex lists all the data elements used in Kernel7’s processing. The column
definition can be found below.

Name
Name of this data element;

Format Tag Length

 Data element’s format complies with [EMV Book3] Annex B;

 Data element’s tag is in sexadecima;

 Data element’s length is decimal indicating the length of value field.

Requirement
The Requirement column represents whether the data element’s existence in the
processing is Mandatory, Conditional or Optional, and indicates the source of the
data element including the Kernel and the Card.

Retrieval
Retrieval column indicates the capability of the Kernel to retrieve the data in the
card. If the Kernel is capable to retrieve the data, the table shall list the command
to be used.

Value
The definition of the data value.

June 2023 Page 59

© 2023 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.
Annex A. Data Dictionary EMV Contactless Book C-7
Kernel 7 Spec v2.11

Table A-1 Data Dictionary

Format Tag
Name Requirement Description Retrieval Value
Length

Only if the Available Offline

Spending Amount ("9F5D") is
personalized to 1, the card returns
this data in GPO response or can If the personalized value is greater than
be retrieved by READ zero, GET DATA command is allowed to
RECORD. Meanwhile, the Card GET DATA use retrieve the Available Offline
Available Offline F: n 12 Additional Processing (Byte 1 bit 1) Spending Amount;
S: Card GPO
Spending T: “9F5D” shall be personalised to 1 to If this data element is personalized to “1”
R: Optional READ
Amount L: 6 indicate that this amount will be and Card Application Process Byte 1 bit
RECORD
calculated and included in all 1 is “1”, Available Offline Spending
contactless transactions. Amount is returned in GPO and READ
Personalization of Available RECORD is allowed.
Offline Spending Amount to 1 also
means that this data can be
retrieved by GET DATA command.

Page 60 June 2023

© 2023 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 Book C-7 Annex A. Data Dictionary
Kernel 7 Spec v2.11

Format Tag
Name Requirement Description Retrieval Value
Length

Byte 1
Bit 8 1= Request Online PIN
Bit 7 1= Request Signature
Bit 6 1= If Offline Data Authentication
fails and terminal is online-capable, go
S: Card online
R: Conditional Bit 5 1= If Offline Data Authentication
If CVM fails and terminal supports standard
The requirement used to indicate
supported or debit/credit procedures, terminate the
Card F: b 16 to device the CVM, card
Card transaction.
Transaction T: “9F6C” capabilities and Issuer requested GPO
Transaction Bit 4 1= If application is expired, go
Qualifiers L: 2 by card.
Qualifiers online
perference is Bit 3~1= RFU
supported. Byte 2
Bit8:1=Consumer Device CVM
Performed
Note: Bit 8 is not used by cards
compliant to this specification, and is
set to 0b
Bit 7-1= RFU

Page 61 June 2023

© 2023 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.
Annex A. Data Dictionary EMV Contactless Book C-7
Kernel 7 Spec v2.11

Format Tag
Name Requirement Description Retrieval Value
Length

Byte 1
Bit 8 RFU
Bit 7 1= Support SDA
Bit 6 1= Support DDA
Bit 5 1= Support cardholder verification
method
Application F: b 16 S: Card
Bit 4 1= Support terminal risk
Interchange T: “82” R: Mandatory Describes the card capability GPO
management
Profile (AIP) L: 2
Bit 3 1= Support Issuer verification
Bit 2 1= RFU
Bit 1 1= Support CDA
Byte 2
Bit 8 = 01
Bit 7~1 RFU

Terminal F: b 32 S: Kernel Indicates terminal capabilities,

See Table 3-1 Terminal Transaction
Transaction T: “9F66” R: Mandatory requirements and results of Pre- N/A
Qualifiers (Tag “9F66”)
Qualifiers L: 4 processing

June 2023 Page 62

© 2023 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 Book C-7 Annex A. Data Dictionary
Kernel 7 Spec v2.11

Format Tag
Name Requirement Description Retrieval Value
Length

Byte 1: fDDA Version No. (“01” in this

version of specification)
Byte 2-5: Card Unpredictable Number
Byte 6-7: Card Transaction Qualifiers
Card
F: b READ Byte 8: RFU(00) implementation is out
Authentication S:Card Shall be returned in the last
T: “9F69” RECORD of this specification
Related Data R:Mandatory record retrieval.
L: var 8-16 GPO
Note: Card Verification Related Data is
a 8-byte data and is reserved in the
card during personalization.

Issuer F: b
Included in Issuer Application
Application T: “9F10” S:Card
Data GPO
Data L: var. up to R:Mandatory
32

Application F: b 16
GET DATA
Transaction T: “9F36” S:Card
GPO
Counter L: 2 R:Mandatory

Page 63 June 2023

© 2023 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.
Annex A. Data Dictionary EMV Contactless Book C-7
Kernel 7 Spec v2.11

Format Tag
Name Requirement Description Retrieval Value
Length

A non-financial reference
assigned to each unique PAN
Payment S:Card
F:an and used to READ
Account R:Conditional, See EMV Payment Tokenization
T: "9F24" link a Payment Account RECORD
Reference if the card Specification Technical Framework
L: 29 represented by that PAN to GPO
(PAR) uses Token.
affiliated Payment
Tokens.

Byte 1: Data ID, assign by Unionpay

Included the partner proprietary
F: b Value: 01-Data equivalent to JIS II
Partner data. This data should be READ
T: 9F7C S:Card Byte 2: Data Length
Proprietary returned var GPO or READ RECORD
L: var, up to R:Optional Byte 3-4: RFU
Data RECORD if it was personalized GPO
32 Byte 5-6: Partner identifier
into the card.
Byte 7-32: Partner proprietary data

June 2023 Page 64

© 2023 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 Book C-7 Annex A. Data Dictionary
Kernel 7 Spec v2.11

Format Tag
Name Requirement Description Retrieval Value
Length

The value field of the Application

Selection Registered Proprietary Data
object follows the following format:
A terminal in a specific market ID1, L1, V1, ID2, L2, V2,…
may be required by a local Where
regulatory authority to offer
• ID is a two byte Proprietary Data
specific services based on
Application Identifier. Proprietary Data Identifiers
ASRPD information.
Selection F: b are registered by EMVCo, and the ID
S:Card This data can be contain in the
Registered T: 9F0A SELECT registration process will be defined by
R:Optional template BF0C or 73, and
Proprietary L: var. EMVCo in a subsequent bulletin.
returned via SELECT.
Data, ASRPD • L is the length of the value field coded
The using of ASRPD is out of
in 1 byte (0 to 255)
scope of this document.
See more details in SB-175 • V is the value field. Its content is
EMVCo Spec Bulletin. proprietary and format is out of scope
of EMVCo
See more details in SB-175 EMVCo
Spec Bulletin.

Last 4 Digits of PAN, used in

S:Card
F: n 4 template 70 or 77. READ See more details in Payment
Last 4 Digits of R:Conditional,
T: 9F25 See more details in Payment RECORD Tokenisation Specification – Technical
PAN if Token is
L: 2 Tokenisation Specification – GPO Framework
used.
Technical Framework

Page 65 June 2023

© 2023 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.
Annex A. Data Dictionary EMV Contactless Book C-7
Kernel 7 Spec v2.11

Format Tag
Name Requirement Description Retrieval Value
Length

Token Requestor ID, used to

S:Card identify the token requestor and
F: n 11 READ See more details in Payment
Token R:Conditional, token domain.
T: 9F19 RECORD Tokenisation Specification – Technical
Requestor ID if Token is See more details in Payment
L: 6 GPO Framework
used. Tokenisation Specification –
Technical Framework

June 2023 Page 66

© 2023 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 Book C-7 Annex B. Fast Dynamic Data Authentication (fDDA)
Kernel 7 Spec v2.11

Annex B. Fast Dynamic Data Authentication

(fDDA)
There are Version 00 and Version 01 and only Version 01 is supported in Kernel7. A
fDDA V01 – supported card shall contain Card Verification Related Data (Tag “9F69”),
in which the Byte 1 indicating the lastest version of fDDA supported by card. If byte 1
of Card Verification Related Data (Tag “9F69”) specifies the version supported by card
is 00, the Kernel shall treat the fDDA verification as a failure followed by the process
in 4.3.2.5.

Dynamic data signature includes data from both the Kernel and the card. The
interaction starts from the combination selection in Pre-processing during the period
the Card returns PDOL containing the Kernel data to be signed in Dynamic Data
Generation. PDOL is transferred from the Entry Point to the Kernel for reference on
data to be passed to the card in GPO command. The data listed in PDOl include but
not limited to Terminal Unpredictable Number, Authorized Amount and Transaction
Currency Code. The Card uses the data to generate a Signature to be returned with
other data in GPO response to the Kernel. The Kernel starts fDDA verification once
the last record is read.

Figure B-1 describes a sample flow of fDDA-related data exchange.

Page 67 June 2023

© 2023 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.
Annex B. Fast Dynamic Data Authentication (fDDA) EMV Contactless Book C-7
Kernel 7 Spec v2.11

Entry Point
Pre-processing and Application selection

The Card requests data From the Kernel:

Terminal Transaction Quality (9F66)
Unpredictable number (9F37)
Authorized Amount (9F02)
Transaction Currency Code (5F2A)
Tags of other data

Kernel Card
Data elements returned to the Card in GPO command:
Terminal Transaction Quality (9F66)
Unpredictable Number (9F37)
Authorized Amount (9F02)
Transaction Currency Code (5F2A)
Other data

Data element in response to GPO :

Transaction Certificate (TC) ;
Dynamic signature;
AFL listing data related to fDDAa;
Other data not related to fDDA;

Read Record

READ RECORD response:

Certificate and data to be used For authentication;
Card Verification Related Data in the last record;

fDDA verification

Outcome
Entry Ponit

Figure B-1 Sample of Data Exchange Related to fDDA

June 2023 Page 68

© 2023 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 Book C-7 Annex C. Data Elements
Kernel 7 Spec v2.11

Annex C. Data Elements

Table C-1 lists the data elements provided by the Kernel in Outcomes for online
messages and clearing records. The terminal shall be able to assemble the data
elements into appropriet messages for the acquirers.

The network message is requested in Online transactions and offline approved

transactions, however the data elements required can be different which is defined in
the Authorization Mode column. The value of the column can be Offline and Online
standing for Offline approved transactions and Online transactions respectively.

Table C-1 Clearing Data Element

Authorization
Data element Tag Source Requirement
Mode

Amount, Authorised
‘9F02’ Terminal Offline and online Mandatory
(Numeric)

Amount, Other
‘9F03’ Terminal Offline and online Mandatory
(Numeric)

Application
‘9F26’ Card Offline and online Mandatory
Cryptogram (AC)

Application Interchange
‘82’ Card Offline and online Mandatory
Profile (AIP)

Application PAN ‘5A’ Card Offline and online Mandatory

Application PAN Conditional, only

‘5F34’ Card Offline and online if the card returns
Sequence Number
it back to kernel.

Application Transaction
‘9F36’ Card Offline and online Mandatory
Counter (ATC)

Page 69 June 2023

© 2023 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.
Annex C. Data Elements EMV Contactless Book C-7
Kernel 7 Spec v2.11

Authorization
Data element Tag Source Requirement
Mode

Cryptogram
‘9F27’ Card Offline and online Mandatory
Information Data (CID)

Issuer Application Data

‘9F10’ Card Offline and online Mandatory
(IAD)

Terminal Capabilities ‘9F33’ Terminal Offline and online Mandatory

Terminal Country Code ‘9F1A’ Terminal Offline and online Mandatory

Terminal Verification
‘95’ Kernel Offline and online ‘00 00 00 00 00’
Results (TVR)

Track 2 Equivalent
‘57’ Card Online Mandatory
Data

Transaction Currency
‘5F2A’ Terminal Offline and online Mandatory
Code

Transaction Date ‘9A’ Terminal Offline and online Mandatory

Transaction Type ‘9C’ Terminal Offline and online Mandatory

Unpredictable Number
‘9F37’ Terminal Offline and online Mandatory
(UN)

Payment Account Conditional, only

'9F24' Card Offline and online if the card returns
Reference (PAR)
it back to kernel.

Product Identification Conditional, only

‘9F63’ Card Offline and online if the card returns
Information
it back to kernel.

Track 1 Discretionary Conditional, only

‘9F1F’ Card Online if the card returns
Data
it back to kernel.

June 2023 Page 70

© 2023 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 Book C-7 Annex C. Data Elements
Kernel 7 Spec v2.11

Authorization
Data element Tag Source Requirement
Mode

Partner Proprietary
‘9F7C’ Card Offline and online Optional.
Data

Application Selection
Registered Proprietary ‘9F0A’ Card Offline and online Optional.
Data, ASRPD

Conditional, if
Last 4 Digits of PAN ‘9F25’ Card Offline and online
Token is used.
Conditional, if
Token Requestor ID ‘9F19’ Card Offline and online
Token is used.

Page 71 June 2023

© 2023 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is per mitted 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.
Annex D. Transaction Log Retrieval EMV Contactless Book C-7
Kernel 7 Spec v2.11

Annex D. Transaction Log Retrieval

Transaction Log retrieval is an optional feature.

Transaction Log is a fixed-length cyclic file tracking all transaction sucessfully

commited by the card. The records in the file shall not contain the Application
Elementary File (AEF) Data Template (tag '70'). The SFI of the Transaction Log and
record number are specified in Log Entry data element (Tag “9F4D”). The SFI of
Transaction Log shall range from 11 to 30. Transaction logging can be enabled or
disabled in the card during personalization, if the feature is enable, information of all
online transaction and offline approved transactions will be saved. Each transaction
only generates one record in the log and the maximum number of the records in a log
is 10.

If the card supports transaction logging, Log Entry (Tag “9F4D”) data element shall be
included in Issuer Discretionary data (Template “BFOC”) (see Table 4-1).

To retrieve Transaction Log, the Kernel shall go through the following steps in
sequence:

 Perform Application Selection and retrieve the Log Entry data element
located in the FCI Issuer Discretionary Data. If the Log Entry data
element is not present, the application does not support the Transaction
Log function.

 Send GET DATA command to read the Log Format(Tag “9F4F”) which
lists (in tag and length format) of data objects representing the logged
data elements.

 Issue READ RECORD command to read the Transaction Log.

Log Format and Transaction Log remains accessible when the application is blocked.
And the FCI of the selected application shall be returned in response to SELECT
command during pre-processing for log retrieval.

Page 72 June 2023

© 2023 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 Book C-7 Annex E. Glossary
Kernel 7 Spec v2.11

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

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.

AFL Application File Locator

AID Application Identifier

AIP Application Interchange Profile

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

ARQC Authorisation Request Cryptogram

ATC Application Transaction Counter

C Conditional

Card As used in these specifications, a consumer device supporting

contactless transactions.

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

use that card.

Page 73 June 2023

© 2023 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.
Annex E. Glossary EMV Contactless Book C-7
Kernel 7 Spec v2.11

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

Verification
Method (CVM)

CDOL Card Risk Management Data Object List

CID Cryptogram Information Data

CVM Cardholder Verification Method

DDA Dynamic Data Authentication

DDOL Dynamic Data Authentication Data Object List

Declined A Final Outcome

DOL Data Object List

EMV® A global standard for 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 An operating mode of the POS System that indicates that this
particular acceptance environment and acceptance rules
supports chip infrastructure. Especially indicate contactless
payment utilising a full chip infrastructure carrying EMV minimum
data.

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

fDDA Fast DDA. Leverages DDA as defined in [EMV 4.3]

specifications. Used in EMV mode transactions to allow the
reader to issue READ RECORD commands to obtain Dynamic
Data Authentication (DDA) related data from the card and
perform the DDA calculations after the card has left the field.

June 2023 Page 74

© 2023 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 Book C-7 Annex E. Glossary
Kernel 7 Spec v2.11

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 exception 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.

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.

L Length

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

Outcome Result from the kernel processing, provided to Entry Point, or

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

PAN Primary Account Number

Page 75 June 2023

© 2023 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is per mitted 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.
Annex E. Glossary EMV Contactless Book C-7
Kernel 7 Spec v2.11

PDOL Processing Options Data Object List

PICC Proximity IC Card

PIN Personal Identification Number

POS Point of Sale

Select Next An Outcome

SDA Static Data Authentication

SFI Short File Identifier

T Tag

TC Transaction Certificate

Terminal A component of the POS System; described in detail in Chapter

2.

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 Again An Outcome

Try Another A Final Outcome

Interface

TVR Terminal Verification Results

UN Unpredictable Number

June 2023 Page 76

© 2023 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 Book C-7 Annex E. Glossary
Kernel 7 Spec v2.11

*** END OF DOCUMENT ***

Page 77 June 2023

© 2023 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is per mitted 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.