EMV®*

Contactless Specifications for

Payment Systems

Book B

Entry Point Specification

Version 2.1
March 2011

*
EMV is a registered trademark in the U.S. and other countries and an unregistered
trademark elsewhere. The EMV trademark is owned by EMVCo.

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV
Contactless Specifications for
Payment Systems

Book B

Entry Point Specification

Version 2.1
March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

Version History
Version Date Description
Entry Point Specification v1.0 May 2008 Preliminary document.

Book B: Entry Point Specification v2.1 March 2011 First publication.

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. 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. 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.

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

Contents
1 Scope ....................................................................................................................1
1.1 Underlying Standards ................................................................................... 1
1.2 Audience ....................................................................................................... 1
1.3 Overview ....................................................................................................... 1
2 References ........................................................................................................... 3
2.1 Volumes of the Contactless Specifications ................................................... 3
2.2 Related Specifications .................................................................................. 3
3 Entry Point Functionality .................................................................................... 5
3.1 Pre-Processing – Start A .............................................................................. 9
3.1.1 Pre-Processing Requirements .......................................................... 9
3.2 Protocol Activation – Start B ....................................................................... 14
3.2.1 Protocol Activation Requirements ................................................... 14
3.3 Combination Selection ................................................................................ 16
3.3.1 PPSE Data for Application Selection .............................................. 17
3.3.2 Selecting the Combination .............................................................. 22
Start C ............................................................................................. 28
3.3.3 Final Combination Selection ........................................................... 29
3.4 Kernel Activation – Start D.......................................................................... 31
3.5 Outcome Processing .................................................................................. 32
3.6 Data Element Processing ........................................................................... 34
3.6.1 Presence of Data ............................................................................ 34
3.6.2 Rules for Padding ........................................................................... 34
3.6.3 Order of Data Elements .................................................................. 34

Annex A Data Elements Dictionary .................................................................... 35

Annex B Glossary ................................................................................................ 37

March 2011 Page iii

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

Figures
Figure 3-1: Entry Point High Level Architecture ......................................................... 7
Figure 3-2: Entry Point Command-Response APDUs .............................................. 22

Tables
Table 3-1: Starting Points ...........................................................................................6
Table 3-2: SELECT Response Message Data Field (FCI) of the PPSE................... 18
Table 3-3: Format of Application Priority Indicator ................................................... 19
Table 3-4: Format of the Kernel Identifier – Byte 1 ................................................... 20
Table 3-5: Format of the Kernel Identifier – Byte 2 to Byte 8.................................... 21
Table 3-6: Default Value for Requested Kernel ID ................................................... 25
Table A-1: Data Elements Dictionary .......................................................................36

Page iv March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

Requirements
Requirements – Pre-Processing................................................................................ 10
Requirements – Protocol Activation .......................................................................... 14
Requirements – Protocol Activation – Collision ......................................................... 15
Requirements – PPSE Data for Application Selection .............................................. 19
Requirements – Combination Selection .................................................................... 23
Requirements – Final Combination Selection ........................................................... 29
Requirements – Final Combination Selection ........................................................... 30
Requirements – Communication Errors .................................................................... 30
Requirements – Kernel Activation ............................................................................. 31
Requirements – Outcomes ........................................................................................ 32
Requirements – Outcome – Try Again ...................................................................... 32
Requirements – Outcome – Select Next ................................................................... 32
Requirements – Outcome – Other ............................................................................. 33
Requirements – Presence of Data ............................................................................ 34
Requirements – Padding ........................................................................................... 34
Requirements – Order of Data Elements .................................................................. 34

March 2011 Page v

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

Page vi March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

1 Scope
This specification, the EMV Contactless Specifications for Payment Systems, Entry
Point Specification, defines the reader requirements necessary to support a
multi-kernel architecture that enables:
• discovery and selection of a contactless application that is supported by both the
reader and the card, and
• activation of the appropriate kernel for processing the contactless transaction in
an international interchange environment.

1.1 Underlying Standards

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

1.2 Audience
This specification is intended for use by manufacturers of readers. The specification
may also be of interest to manufacturers of contactless cards and financial institution
staff responsible for implementing financial applications in contactless cards.

1.3 Overview
This volume includes the following chapters and annexes.
Chapter 1 contains general information that helps the reader understand and use
this specification.
Chapter 2 lists related specifications and standards.
Chapter 3 describes Entry Point functionality, including pre-processing, protocol
activation, combination selection, kernel activation, and Outcome processing.
Annex A defines the data elements used in this specification.
Annex B is a glossary of terms and abbreviations used in this specification.

March 2011 Page 1

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

Page 2 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

2 References

2.1 Volumes of the Contactless Specifications

This specification is part of a seven-volume set:
Book A: Architecture and General Requirements
Book B: Entry Point Specification (supersedes Entry Point v1.0)
Book C-1: Kernel 1 Specification
Book C-2: Kernel 2 Specification
Book C-3: Kernel 3 Specification
Book C-4: Kernel 4 Specification
Book D: Contactless Communication Protocol (replaces CCP v2.0.1)

2.2 Related Specifications

[EMV 4.2 Book 1] EMV Integrated Circuit Card Specifications for Payment
Systems, version 4.2, Book 1, Application Independent ICC to
Terminal Interface Requirements, June 2008.

[EMV 4.2 Book 3] EMV Integrated Circuit Card Specifications for Payment
Systems, version 4.2, Book 3, Application Specification,
June 2008.

ISO 4217 Codes for the representation of currencies and funds.

March 2011 Page 3

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

Page 4 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

3 Entry Point Functionality

Entry Point consists of five main functional sections:
1) Preliminary transaction processing (hereafter called Pre-Processing):
Processing prior to the activation of the contactless interface of the reader
and before the cardholder is invited to present a contactless card. Specifics of
Pre-Processing are defined in section 3.1.
2) Protocol Activation: Activation of the contactless interface. Specifics of
Protocol Activation are defined in section 3.2.
3) Combination Selection: Selection of the Combination to use for the
transaction. Specifics of Combination Selection are defined in section 3.3.
4) Kernel Activation: Entry Point activates the selected kernel and this begins
kernel processing. Specifics of Kernel Activation are defined in section 3.4.
5) Outcome Processing: Entry Point processes an Outcome according to the
type of Outcome and the values of the Outcome parameters. Specifics of
Outcome Processing are defined in section 3.5.

March 2011 Page 5

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

Entry Point has four starting points, as shown in Table 3-1.

Table 3-1: Starting Points

Start at Activation
Start A Pre-Processing Start at Pre-Processing; activated by the
reader when Autorun is ‘No’. 1 This is typical
for a new transaction with a variable amount
in an EMV mode acceptance environment.
Start B Protocol Activation Activated in any of the following cases:
• activated by the reader when Autorun is
‘Yes’;1 this is typical for a new transaction
with a fixed amount in a mag-stripe mode
acceptance environment, or
• activated by the reader to handle issuer
responses after an Online Request or
End Application Outcome with
parameter Start = B, or
• handled internally by Entry Point for an
error situation, or
• handled internally by Entry Point for a Try
Again Outcome
Start C Combination Handled internally by Entry Point for a
Selection Select Next Outcome.
Start D Kernel Activation Activated by the reader to handle issuer
responses after an Online Request
Outcome with parameter Start = D.

Each Start has conditions that must be satisfied by the reader or terminal before
Entry Point is activated. The specific requirements are defined in the appropriate
section.
The starting points support the needs of the four EMV kernels contained within this
version of the specification.
Each new contactless transaction begins at Start A or Start B depending on whether
the transaction amount (as represented by Amount, Authorised) is variable or not.
A transaction amount is deemed to be invariable if for the given reader configuration
it is always the same for all transactions so that Pre-Processing may be
pre-computed for all transactions.

1
Autorun is discussed in Book A.

Page 6 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

Entry Point activates the card and selects the appropriate kernel, which then
conducts the contactless transaction with the card, until it finishes with an Outcome.
Try Again and Select Next Outcomes are immediately processed by Entry Point,
which re-starts at the appropriate point. All other Outcomes are considered to be
Final Outcomes and processing reverts to the reader and terminal. In some cases,
such as Approved or Declined Outcomes, the transaction is complete and no
further processing from Entry Point and the kernel is required. In other cases, such
as an Online Request Outcome, then after the reader and terminal have dealt with
the expected functionality, if applicable, Entry Point will be started at the requested
Start so that a kernel can complete the transaction.
The various start locations and the Outcome concept allows Entry Point to support a
wide range of kernel expectations. These concepts of Entry Point processing are
illustrated in Figure 3-1.

Figure 3-1: Entry Point High Level Architecture

March 2011 Page 7

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

Entry Point is designed around the use of a Proximity Payment System Environment
(PPSE) as the selection mechanism. For multi-brand acceptance, this allows a
reader to quickly obtain all the available brands and applications with a single
command and to make an immediate choice based on priority and kernel availability.

Page 8 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

3.1 Pre-Processing – Start A

Entry Point is initiated at Pre-Processing for a new transaction with a variable
amount.
Each reader Combination {AID - Kernel ID} may have a set of Entry Point
Configuration Data, as defined in Book A, Table 5-2, including CVM, floor limit(s),
online/offline capability, extended selection support, and contactless transaction limit.
If present, these limits are examined during Pre-Processing. The result is a set of
flags and data elements for each Combination; one of which will be used to define
the attributes of the transaction. The flags and limits referenced in this section are all
part of Entry Point Configuration Data as outlined in Book A, Table 5-2.
The indicators referenced in this section are all part of Entry Point Pre-Processing
Indicators as outlined in Book A, Table 5-3.
In some reader implementations, for instance a vending machine with identically
priced goods, the results of Pre-Processing do not vary per transaction and are made
available as configuration data for Start B.
Pre-Processing may set the Entry Point Pre-Processing Indicators per reader
Combination {AID - Kernel ID} as defined in Book A, Table 5-3.
Entry Point uses the ‘Contactless Application Not Allowed’ indicator to indicate that
the transaction cannot take place for this Combination.
A Copy of Terminal Transaction Qualifiers (TTQ) may be requested in the PDOL
(with Tag '9F66' 2) of contactless applications that require this data element to obtain
indication of the reader contactless capabilities and transaction requirements.
The technical details and the requirements of the Pre-Processing are documented in
section 3.1.1.

3.1.1 Pre-Processing Requirements

This section addresses the requirements for Pre-Processing.
If TTQ (see Book A, Table 5-4) is configured for a Combination, it will be modified
during Pre-Processing. These modifications are transient and do not affect the
original configuration values.

2
This is a payment system specific tag used by Kernel 3.

March 2011 Page 9

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

Requirements – Pre-Processing

3.1.1.1 For each Combination, Entry Point shall reset the Entry Point
Pre-Processing Indicators as defined in Table 5-3 of Book A
(Entry Point Pre-Processing Indicators) to 0.

3.1.1.2 If Terminal Transaction Qualifiers (TTQ) is part of the configuration

data for a Combination,
then:
• Entry Point shall copy the TTQ from Entry Point Configuration
Data (see Book A, Table 5-2) into the Copy of TTQ in the Entry
Point Pre-Processing Indicators.
• Entry Point shall reset byte 2, bit 8 and bit 7 in the Copy of TTQ
to 00b (‘Online cryptogram not required’ and ‘CVM not
required’).
The other bits are unchanged. 3
For each Combination, Entry Point shall perform the following actions:

3.1.1.3 If all of the following are true:

• the Status Check Support flag is present,
• and the Status Check Support flag is 1,
• and the Amount, Authorised is a single unit of currency,
then Entry Point shall set the ‘Status Check Requested’ indicator
for the Combination to 1.

3.1.1.4 If the value of Amount, Authorised is zero,

then:
• If the Zero Amount Allowed flag is present
and the Zero Amount Allowed flag is 0,
then Entry Point shall set the ‘Contactless Application Not
Allowed’ indicator for the Combination to 1.
• Otherwise, Entry Point shall set the ‘Zero Amount’ indicator for
the Combination to 1.

3
By copying TTQ into the Copy of TTQ during this step, the static configuration bits of TTQ
replace the bits cleared in the Entry Point Pre-Processing Indicators as stated in
requirement 3.1.1.1.

Page 10 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

Requirements – Pre-Processing

3.1.1.5 If the Reader Contactless Transaction Limit is present

and the value of Amount, Authorised is greater than or equal to
this limit,
then Entry Point shall set the ‘Contactless Application Not
Allowed’ indicator for the Combination to 1.

3.1.1.6 If the Reader Contactless Floor Limit is present

and the value of Amount, Authorised is greater than this limit,
then Entry Point shall set the ‘Reader Contactless Floor Limit
Exceeded’ indicator for the Combination to 1.

3.1.1.7 If all of the following are true:

• the Reader Contactless Floor Limit is not present,
• and the Terminal Floor Limit (Tag '9F1B') is present,
• and the value of Amount, Authorised is greater than the
Terminal Floor Limit (Tag '9F1B'),
then Entry Point shall set the ‘Reader Contactless Floor Limit
Exceeded’ indicator for the Combination to 1.

3.1.1.8 If the Reader CVM Required Limit is present

and the value of Amount, Authorised is greater than or equal to
this limit,
then Entry Point shall set the ‘Reader CVM Required Limit
Exceeded’ indicator for the Combination to 1.

March 2011 Page 11

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

Requirements – Pre-Processing
For each Combination that has a TTQ, Entry Point shall perform the
following actions:

3.1.1.9 If the ‘Reader Contactless Floor Limit Exceeded’ indicator is 1,

then Entry Point shall set byte 2, bit 8 in the Copy of TTQ for the
Combination to 1b (‘Online cryptogram required’).

3.1.1.10 If the ‘Status Check Requested’ indicator is 1,

then Entry Point shall set byte 2, bit 8 in the Copy of TTQ for the
Combination to 1b (‘Online cryptogram required’).

3.1.1.11 If the ‘Zero Amount’ indicator is 1,

then:
• If byte 1, bit 4 of the Copy of TTQ is 0b (‘Online capable
reader’),
then Entry Point shall set byte 2, bit 8 in the Copy of TTQ for
the Combination to 1b (‘Online cryptogram required’).
• Otherwise (byte 1 bit 4 of the Copy of TTQ is 1b (‘Offline-only
reader’)), Entry Point shall set the ‘Contactless Application Not
Allowed’ indicator for the Combination to 1.

3.1.1.12 If the ‘Reader CVM Required Limit Exceeded’ indicator is 1,

then Entry Point shall set byte 2, bit 7 in the Copy of TTQ for the
Combination to 1b (‘CVM required’).

Page 12 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

Requirements – Pre-Processing
When Pre-Processing for all Combinations has been performed, Entry
Point shall perform the following action:

3.1.1.13 If, for all the Combinations, the ‘Contactless Application Not
Allowed’ indicator is 1,
then Entry Point shall provide a Try Another Interface Outcome
with the following Outcome parameter values and shall continue
with Outcome Processing, section 3.5.
Try Another Interface:
• 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: Processing Error
• 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
Otherwise (at least one Combination is allowed) Entry Point shall
retain the Entry Point Pre-Processing Indicators for each allowed
Combination.

March 2011 Page 13

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

3.2 Protocol Activation – Start B

Protocol Activation is either the next step after Pre-Processing, or Entry Point may be
started at Protocol Activation for new transactions with a fixed amount or as Start B
after Outcome Processing.
During Protocol Activation, polling is started for card discovery (if this has not already
been performed) and appropriate User Interface messages are given. The retained
Entry Point Pre-Processing Indicators and the Candidate List are available if
required.

3.2.1 Protocol Activation Requirements

Requirements – Protocol Activation

3.2.1.1 If the Restart flag is 0,

then:
• If Entry Point is activated by the reader 4 at Start B,
then:
o For each Combination, Entry Point shall reset the Entry
Point Pre-Processing Indicators to 0.
o For each Combination,
if Terminal Transaction Qualifiers (TTQ) is configured,
then Entry Point shall copy the TTQ from Entry Point
Configuration Data (see Book A, Table 5-2) into the
Copy of TTQ in the Entry Point Pre-Processing Indicators.
• Entry Point shall clear the Candidate List.

4
Error situations (e.g. timeout) or Outcomes handled directly by Entry Point (e.g. Try Again)
are not considered an activation by the reader.

Page 14 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

Requirements – Protocol Activation

3.2.1.2 If the Restart flag is 1,

and the value of the retained 5 UI Request on Restart Present
parameter is 'Yes',
then Entry Point shall send the retained User Interface Request.
Otherwise (the Restart flag is 0 or the value of the retained
UI Request on Restart Present parameter is 'No'), Entry Point shall
send a User Interface Request with the following parameters:
• Message Identifier: '15' (“Present Card”)
• Status: Ready to Read

3.2.1.3 The field shall be powered up and polling performed as defined in

the Main Loop of Book D.

Requirements – Protocol Activation – Collision

3.2.1.4 If a collision as defined in Book D is reported to Entry Point,

then Entry Point shall send a User Interface Request with the
following parameters:
• Message Identifier: '19' (“Please Present One Card Only”)
• Status: Contactless collision detected (Processing Error)

3.2.1.5 When the collision condition is no longer indicated,

then Entry Point shall send a User Interface Request with the
following parameters:
• Message Identifier: '19' (“Please Present One Card Only”)
• Status: Ready to Read

5
As described in Book A, Requirements – Final Outcome Processing.

March 2011 Page 15

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

3.3 Combination Selection

Combination Selection is either the next step after Protocol Activation or Entry Point
may be started at Combination Selection as Start C after Outcome Processing.
This section describes the product and kernel selection process. It specifies the
logical structure of the data and files within the contactless card that are used for the
process, and then describes the logic to use the card file structure.
Entry Point does not rely on an exclusive link between the product, defined by its
Application Identifier (AID), and the kernel. A single product can run on different
kernels. Within the reader, a Kernel ID is used to distinguish between different
kernels that may be supported.
So in addition to the AID, Entry Point also needs information on which kernel to
activate. The combination of AID and Kernel ID is further referred to as a reader
Combination.
Following a method similar to the EMV contact application selection process, Entry
Point constructs a list of Combinations mutually supported by the contactless card
and the reader. If multiple Combinations are supported by both contactless card and
reader, Entry Point selects the Combination with the highest priority.
For this purpose, the contactless card has a PPSE that contains a list of products
and applications selectable over the contactless interface.
To recover the list of products and applications, Entry Point sends a SELECT (PPSE)
command. The SELECT command is defined in [EMV 4.2 Book 1], section 11.3.2.
The File Control Information (FCI, as defined in Table 3-2 below) in the response to
the SELECT (PPSE) contains a list of Directory Entries identifying:
• a product supported by the card
• the Kernel Identifier of the kernel required for the specific application
underpinning the product (conditional)
• the priority of the Combination (conditional)
In the card, the product is indicated by its ADF Name.
The kernel required for a specific card application is indicated by the Kernel Identifier
(Tag '9F2A').
The priority of the Combination is indicated by means of an Application Priority
Indicator with a value of '1' as the highest priority and 'F' the lowest. A value of '0'
means no priority is assigned and has the same priority as 'F'.
In the reader, the product is indicated by the AID. Readers must be able to link AIDs
to Kernel IDs.

Page 16 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

Entry Point finds Combinations by matching pairs of data elements (ADF Name
(Tag '4F') and Kernel Identifier (Tag '9F2A')) in the card with pairs of data elements in
the reader (AID and Kernel ID).
Once all supported Combinations have been found and the highest priority
Combination has been identified, Entry Point selects the associated card application
by sending a SELECT (AID) command. The SELECT command is defined in
[EMV 4.2 Book 1], section 11.3.2.

3.3.1 PPSE Data for Application Selection

The PPSE begins with a DDF given the name ‘2PAY.SYS.DDF01’. For support of
this specification, it is assumed that this DDF is present in the contactless card. The
FCI returned upon the selection of the PPSE is indicated in Table 3-2.

March 2011 Page 17

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

Table 3-2: SELECT Response Message Data Field (FCI) of the PPSE

'6F' FCI Template M

'84' DF Name (‘2PAY.SYS.DDF01’) O6
'A5' FCI Proprietary Template M
'BF0C' FCI Issuer Discretionary Data M
'61' Directory Entry M
'4F' ADF Name M
'50' Application Label O
'87' Application Priority Indicator (see C7
Table 3-3)
'9F2A' Kernel Identifier (see Table 3-4 C8
and Table 3-5)
'9F29' Extended Selection (see Table A-1 C9
on page 36)
'61' Directory Entry O
'4F' ADF Name M 10
'50' Application Label O10
'87' Application Priority Indicator C7,10
'9F2A' Kernel Identifier C8,10
'9F29' Extended Selection C9,10
'61' Directory Entry O
'4F' ADF Name M10
'50' Application Label O10
'87' Application Priority Indicator C7,10
'9F2A' Kernel Identifier C8,10
'9F29' Extended Selection C9,10

6
Tag '84' is Optional from a reader processing perspective, while from a card perspective it is
considered a Mandatory data element to personalize.
7
If the card supports multiple Combinations, each Combination should have its own
Application Priority Indicator.
8
If the card explicitly identifies the kernel to be used.
9
If the card supports Extended Selection.
10
Only relevant if this Directory Entry is present.

Page 18 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

Additional data elements may be included in the FCI Issuer Discretionary Data
(Tag 'BF0C') and Directory Entries (Tag '61'), for example, template '73'. Entry Point
ignores such data elements and their usage is proprietary. Note that the order of data
elements within the FCI may vary.
If the Kernel Identifier is absent from a Directory Entry, Entry Point bases its kernel
decision upon the ADF Name:
• For a JCB ADF Name, it will use Kernel 1 or the kernel associated with the
JCB ADF Name.
• For a MasterCard ADF Name, it will use Kernel 2.
• For a Visa ADF Name, it will use Kernel 3 (or Kernel 1: see
requirement 3.3.3.6).
• For an American Express ADF Name, it will use Kernel 4.
• For any other ADF Name, it will use the kernel associated with the ADF Name.
ADF Names can be obtained from the relevant payment system.

Requirements – PPSE Data for Application Selection

3.3.1.1 The coding of the Application Priority Indicator is indicated in

Table 3-3.
If the Application Priority Indicator is absent from a Directory
Entry,
then Entry Point shall assume b4-b1 to have a value of 0000b.

Table 3-3: Format of Application Priority Indicator

b8 b7–b5 b4–b1 Definition

x RFU
xxx RFU
0000 No priority assigned
xxxx Priority order of the application to be selected,
(except ranging from 1–15, with 1 being highest priority
0000)

March 2011 Page 19

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

The coding of the Kernel Identifier is indicated in Table 3-4 and Table 3-5.

Table 3-4: Format of the Kernel Identifier – Byte 1

b8 b7 b6 b5 b4 b3 b2 b1 Meaning
x x Type of kernel
An international kernel, with a
Kernel Identifier assigned by
0 0
EMVCo and coded in the
Short Kernel ID
0 1 RFU
A domestic kernel, with Kernel
Identifier in EMVCo format,
coded by the concatenation of
1 0
the Short Kernel ID and the
Extended Kernel ID
(see Table 3-5)
A domestic kernel, with the
Kernel Identifier in proprietary
format, coded by the
1 1 concatenation of the
Short Kernel ID and the
Extended Kernel ID
(see Table 3-5)
x x x x x x Short Kernel ID
The kernel is associated with
0 0 0 0 0 0
the corresponding ADF Name
0 0 0 0 0 1 Kernel 1
0 0 0 0 1 0 Kernel 2
0 0 0 0 1 1 Kernel 3
0 0 0 1 0 0 Kernel 4
0 0 0 1 0 1 5th kernel
– – – – – –
1 1 1 1 1 1 63rd kernel

Page 20 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

Table 3-5: Format of the Kernel Identifier – Byte 2 to Byte 8 11

Byte Meaning
Extended Kernel ID:
Byte 2 For international legacy kernel: RFU
For domestic legacy kernel Currency Code as defined
using the EMVCo format: by ISO 4217

Byte 3 For domestic legacy kernel Proprietary

using a proprietary format:

Byte 4 RFU
Byte 5 RFU
Byte 6 RFU
Byte 7 RFU
Byte 8 RFU

11
Kernel Identifier is of variable size and may be one, three, or more bytes in length, but not
two bytes.

March 2011 Page 21

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

3.3.2 Selecting the Combination

The selection process of Entry Point follows to a large extent the EMV contact
Application Selection requirements ([EMV 4.2 Book 1], section 12.3.2) with the
following exceptions:
• A PPSE is present in the contactless card.
• Usage of the PPSE is mandatory in Entry Point.
• The Directory Entries are located in the FCI Issuer Discretionary Data of the
PPSE.
Figure 3-2 illustrates the Command – Response APDU flow between contactless
card and reader.

Figure 3-2: Entry Point Command-Response APDUs

Contactless Card Reader

SELECT PPSE
List of ADF names +
kernel IDs

SELECT AID

FCI

Note: The response to the SELECT (AID) command is received and processed by
Entry Point, including SW1 SW2.

Page 22 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

Requirements – Combination Selection

3.3.2.1 If Entry Point is activated by the reader at Start B,

then:
• If Issuer Authentication Data and/or Issuer Script is present,
then processing shall continue at requirement 3.3.3.3 of Final
Combination Selection with the Combination that was selected
during the previous Final Combination Selection.
• Otherwise, Entry Point shall perform steps 1 to 3.
Else if Entry Point is activated by the reader at Start C,
then processing shall continue at Step 3.
Step 1

3.3.2.2 Entry Point shall send a SELECT (PPSE) command (as described in
[EMV 4.2 Book 1], section 11.3.2) to the card, with a file name of
‘2PAY.SYS.DDF01’.

3.3.2.3 If Entry Point receives SW1 SW2 = '9000' in response to the

SELECT (PPSE) command,
then Entry Point shall proceed to Step 2.
Otherwise, Entry Point shall add no Combinations to the
Candidate List and shall proceed to Step 3.

March 2011 Page 23

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

Requirements – Combination Selection

Step 2

3.3.2.4 If there is no Directory Entry (Tag '61') in the FCI,

then Entry Point shall add no Combinations to the Candidate List
and shall proceed to Step 3.

3.3.2.5 For each reader Combination {AID – Kernel ID} supported by the
reader for which the ‘Contactless Application Not Allowed’
indicator is 0, Entry Point shall process each Directory Entry
(Tag '61') from the FCI. When the Directory Entries have been
processed for all supported reader Combinations, Entry Point shall
proceed to Step 3.
To process the Directory Entries, Entry Point shall begin with the
first Directory Entry of the FCI and process sequentially for each
Directory Entry in the FCI as described in bullet A thru E below.
A. Entry Point shall examine the format of the ADF Name of the
Directory Entry.
If the ADF Name is missing
or is not coded according to [EMV 4.2 Book 1], section 12.2.1,
then Entry Point shall proceed with the next Directory Entry.
B. Entry Point shall examine whether the ADF Name matches the
AID of the reader Combination.
If the ADF Name has the same length and value as the AID
(full match),
or the ADF Name begins with the AID (partial match),
then the ADF Name matches the AID and the AID is referred to
as the “matching AID”.
Otherwise Entry Point shall return to bullet A and proceed with
the next Directory Entry.

Page 24 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

Requirements – Combination Selection

C. Entry Point shall examine the presence and format of the
Kernel Identifier (Tag '9F2A') to determine the
Requested Kernel ID.
If the Kernel Identifier (Tag '9F2A') is absent in the Directory
Entry,
then Entry Point shall use a default value for the
Requested Kernel ID, based on the matching AID, as indicated
in Table 3-6.

Table 3-6: Default Value for Requested Kernel ID

Matching AID Default Value for

Requested Kernel ID
American Express AID 00000100b

MasterCard AID 00000010b

Visa AID 00000011b

Other 00000000b

If the Kernel Identifier (Tag '9F2A') is present in the Directory

Entry,
then Entry Point shall examine the value field as follows:
o If the length of the Kernel Identifier value field is zero,
then Entry Point shall use a default value for the
Requested Kernel ID, based on the matching AID, as
indicated in Table 3-6.
o If byte 1, b8 and b7 of the Kernel Identifier have the value
00b or 01b 12,
then Requested Kernel ID is equal to the value of byte 1 of
the Kernel Identifier (i.e. b8b7||Short Kernel ID).

12
The value of 01b is RFU for cards.

March 2011 Page 25

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

Requirements – Combination Selection

o If byte 1, b8 and b7 of the Kernel Identifier have the value

10b or 11b,
then:
− If the length of the Kernel Identifier value field is less
than 3 bytes,
then Entry Point shall return to bullet A and proceed
with the next Directory Entry.
− If the Short Kernel ID is different from 000000b,
then the Requested Kernel ID is equal to value of the
byte 1 to byte 3 of the Kernel Identifier
(i.e. b8b7||Short Kernel ID||Extended Kernel ID).
− If the Short Kernel ID is equal to 000000b,
then the determination of the Requested Kernel ID is
out of scope of this specification.

Page 26 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

Requirements – Combination Selection

D. Entry Point shall examine whether the Requested Kernel ID is
supported for the reader Combination.
o If the value of the Requested Kernel ID is non-zero,
and the value of the Requested Kernel ID is equal to the
value of the Kernel ID,
then the kernel requested by the card is supported by the
reader;
otherwise Entry Point shall proceed with the next Directory
Entry (bullet A).
o If the value of the Requested Kernel ID is zero,
and the Kernel Identifier indicates an international kernel
(byte 1, b8 of the Kernel Identifier has the value 0b),
then the kernel requested by the card is supported by the
reader (e.g. a JCB product will use the Kernel ID of an
international kernel associated with the JCB AID);
otherwise Entry Point shall return to bullet A and proceed
with the next Directory Entry.
E. Entry Point shall add a Combination to the Candidate List for
final selection, consisting of:
o the ADF Name
o the Kernel ID
o the Application Priority Indicator (if present)
o the Extended Selection (if present)

March 2011 Page 27

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

Requirements – Combination Selection

Start C
Step 3

3.3.2.6 If the Candidate List contains at least one entry,

then Entry Point shall retain the Candidate List 13 and shall
continue with Final Combination Selection, section 3.3.3.

3.3.2.7 If the Candidate List is empty,

then Entry Point shall send an End Application Outcome with the
following Outcome parameter values and shall continue with
Outcome Processing, section 3.5.
End Application:
• Start: N/A
• Online Response Data: N/A
• CVM: N/A
• UI Request on Outcome Present: Yes
o Message Identifier: '1C' (“Insert, Swipe or Try Another
Card”)
o Status: Ready To Read
• 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

13
For use with Start D and Start B with issuer response data.

Page 28 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

3.3.3 Final Combination Selection

Once Entry Point determines the list of mutually supported Combinations, it shall
proceed as follows:

Requirements – Final Combination Selection

3.3.3.1 If there is only one Combination in the Candidate List,

then Entry Point shall select the Combination.

3.3.3.2 If there are multiple Combinations in the Candidate List,

then Entry Point shall select the Combination as follows:
• Consider each Combination that has an Application Priority
Indicator with a value of 0 or no Application Priority Indicator
to be of equal lowest priority.
• If a single Combination has a higher priority than any other
Combination in the Candidate List, select that Combination.
• If multiple Combinations in the Candidate List have the highest
priority,
then select the Combination that occurs first in the PPSE.

3.3.3.3 If all of the following are true:

• the Extended Selection data element (Tag '9F29') is present in
the Combination selected,
• and the Extended Selection Support flag is present for this
Combination,
• and the Extended Selection Support flag is 1,
then Entry Point shall append the value contained in Extended
Selection to the ADF Name in the data field of the SELECT
command.

3.3.3.4 Entry Point shall send the SELECT (AID) command with the ADF
Name of the selected Combination (with Extended Selection if
appended).

The response to the SELECT (AID) command is structured as defined in

[EMV 4.2 Book 1], Table 45, and is received and processed by Entry Point, including
the Status Word SW1 SW2.

March 2011 Page 29

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

Requirements – Final Combination Selection

3.3.3.5 If the response to the SELECT (AID) command includes an

SW1 SW2 other than '9000',
then Entry Point shall remove the selected Combination
associated with this ADF Name from the Candidate List and shall
return to Start C (Step 3 of Combination Selection
(requirement 3.3.2.6)).

3.3.3.6 If all of the following are true:

• the selected AID indicates Visa AID,
• and the kernel in the selected Combination is Kernel 3,
• and the PDOL in the FCI is absent
or the PDOL in the FCI does not include Tag '9F66',
then:
• If Kernel 1 is supported,
then Entry Point shall change the Kernel ID for this AID from
the initial Kernel 3 to Kernel 1.
• If Kernel 1 is not supported,
then Entry Point shall remove the selected Combination
associated with this ADF Name from the Candidate List and
shall return to Start C (Step 3 of Combination Selection
(requirement 3.3.2.6)).

Requirements – Communication Errors

3.3.3.7 If at any time during Protocol Activation or Combination Selection

a communications error as defined in Book D (Transmission,
Protocol, or Time-out) is reported to Entry Point,
then Entry Point shall return to Start B (Protocol Activation,
section 3.2.1).

Page 30 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

3.4 Kernel Activation – Start D

Kernel Activation is either the next step after Combination Selection, or Entry Point
may be started at Kernel Activation as Start D after Outcome Processing. In the
event that Entry Point is started as Start D, the FCI and the Status Word will not be
needed for the selected kernel.
During Kernel Activation, Entry Point hands over control to the kernel of the selected
Combination. Once the kernel is activated, all commands and responses are
processed by the kernel.

Requirements – Kernel Activation

3.4.1.1 Entry Point shall activate the kernel identified in the selected
Combination.

3.4.1.2 Entry Point shall make the Entry Point Pre-Processing Indicators
(as specified in Book A, Table 5-3) for the selected Combination
available to the selected kernel.

3.4.1.3 Entry Point shall make available the FCI and the Status Word
SW1 SW2 (both received from the card in the SELECT (AID)
response) to the selected kernel. This requirement does not apply
if Entry Point is restarted at Start D after Outcome Processing.

March 2011 Page 31

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

3.5 Outcome Processing

Each kernel finishes its processing by providing an Outcome with parameters. Some
Outcomes, such as Try Again and Select Next are processed immediately by Entry
Point which re-starts processing at the appropriate start. The rest, such as Approved
and Online Request are passed to the reader as a Final Outcome together with the
parameters and associated data.
In addition, for exception conditions within Entry Point processing, a Final Outcome
may be provided directly by Entry Point.
Full details of the Outcomes and parameter settings can be found in Book A,
Chapter 6.

Requirements – Outcomes

3.5.1.1 If the value of Outcome parameter UI Request on Outcome

Present is ‘Yes’,
then Entry Point shall send the associated User Interface Request.

3.5.1.2 If the Outcome parameter Field Off Request has a value other than
‘N/A’,
then the field shall be turned off and shall remain off for the
period indicated by the hold time.

Requirements – Outcome – Try Again

3.5.1.3 If the Outcome is Try Again,

then Entry Point shall return to Start B (Protocol Activation,
section 3.2.1).

Requirements – Outcome – Select Next

3.5.1.4 If the Outcome is Select Next,

then Entry Point shall remove the selected Combination
associated with this ADF Name from the Candidate List and shall
return to Start C (Step 3 of Combination Selection
(requirement 3.3.2.6)).

Page 32 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

Requirements – Outcome – Other

3.5.1.5 If the Outcome is other than Try Again or Select Next,

then Entry Point shall provide the Outcome to the reader as a
Final Outcome, together with:
• the Outcome parameter set
• associated data provided by the kernel
• the ADF Name of the application that was selected (with
Extended Selection if appended)

March 2011 Page 33

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

3.6 Data Element Processing

3.6.1 Presence of Data

Requirements – Presence of Data

3.6.1.1 If Entry Point encounters a data object from the card that is
designated as terminal or reader sourced,
then it shall ignore the data object and continue the transaction as
if the data object had not been present.

3.6.1.2 If Entry Point encounters a data object from the card that is not
recognised,
then the unrecognised data object shall be ignored and the
transaction shall continue as if the data object had not been
present.

3.6.2 Rules for Padding

Requirements – Padding

3.6.2.1 The reader shall apply padding according to the format of the data
elements and the rules as defined in [EMV 4.2 Book 1], Annex B
and Specification Bulletin 69.

3.6.3 Order of Data Elements

Requirements – Order of Data Elements

3.6.3.1 The reader shall accept TLV data elements in any order.

Page 34 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

Annex A Data Elements Dictionary

Table A-1 defines those data elements that are introduced by Entry Point and which
may be used for financial transaction interchange and their mapping onto data. For
other data elements referenced in this specification, see [EMV 4.2 Book 3], Annex A.
[EMV 4.2 Book 3] also defines the rules for handling the data elements.
The characters used in the “Format” column are described in Book A, section 3.2.

March 2011 Page 35

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

Table A-1: Data Elements Dictionary

Name Description Source Format Template Tag Length

Extended Selection The value to be appended to the ADF Name in the Card b '61' '9F29' var
data field of the SELECT command, if the Extended
Selection Support flag is present and set to 1.
Content is payment system proprietary.
Note: The maximum length of Extended Selection
depends on the length of ADF Name in the same
directory entry such that Length of Extended
Selection + Length of ADF Name <= 16.
Kernel Identifier Indicates the card’s preference for the kernel on Card b '61' '9F2A' 1 or 3-8
which the contactless application can be
processed.
Reader Contactless Indicates the contactless floor limit relating to the Entry n 12 — — 6
Floor Limit Combination. Point
Reader Contactless Indicates the limit for which contactless transactions Entry n 12 — — 6
Transaction Limit can be conducted relating to the Combination. Point
Reader CVM Required Indicates the limit for which a CVM is necessary Entry n 12 — — 6
Limit relating to the Combination. Point
Terminal Transaction Indicates the requirements for online and CVM Entry b '9F66' 4
Qualifiers processing as a result of Entry Point processing. Point
The scope of this tag is limited to Entry Point.
Kernels may use this tag for different purposes.

March 2011 Page 36

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be permitted only pursuant to the terms and conditions of the license
agreement between the user and EMVCo found at http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

Annex B Glossary
This annex provides a glossary of terms and abbreviations used in Book A and
Book B of the EMV Contactless Specifications for Payment Systems.

ADF Application Definition File

AID Application Identifier

Approved A Final Outcome

b Binary

C Conditional

C-APDU Command APDU

Candidate List The list of Combinations constructed by Entry Point during

the Combination Selection process.

Card As used in these specifications, a consumer device

supporting contactless transactions.

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

Verification Method
(CVM)

Combination Any of the following:

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

March 2011 Page 37

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

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

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

Contactless card See “Card”.

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

CVM Cardholder Verification Method

DDF Directory Definition File

Declined A Final Outcome

DF Dedicated File

Discovery Contactless readers poll for contactless cards. When one or

more contactless cards enter the field of the contactless
reader, this is called discovery.

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. Typically used in conjunction
with the term “transaction” (i.e., EMV mode transaction) to
indicate contactless payment utilising a full chip infrastructure
carrying EMV minimum data.

EMVCo EMVCo LLC is the organization of payment systems that

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

End Application A Final Outcome

Page 38 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

Extended Selection An option in which Entry Point appends the value indicated by
the Extended Selection data element (Tag '9F29') to the ADF
name in the SELECT command.

FCI File Control Information

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

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

Hz Hertz

Kernel The kernel contains interface routines, security and control

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

Kernel ID Identifier to distinguish between different kernels that may be

supported by the reader.

Kernel Identifier Identifier to distinguish between different kernels that may be

indicated by the card.

LED Light-Emitting Diode

M Mandatory

Mag-stripe mode An operating mode of the POS System that indicates that this
particular acceptance environment and acceptance rules
supports mag-stripe infrastructure. Typically used in
conjunction with the term “transaction” (i.e., mag-stripe mode
transaction) to indicate contactless payment based on Track
1 and/or Track 2 Data obtained from the card.

ms Millisecond

n Numeric

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

Final Outcome parameters

O Optional

March 2011 Page 39

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

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.

PDOL Processing Options Data Object List

PIN Personal Identification Number

POS Point of Sale

PPSE Proximity Payment System Environment

Proximity Payment A list of all Combinations supported by the contactless card.

System PPSE is used in the Entry Point Combination Selection
Environment
process.
(PPSE)

R-APDU Response APDU

Reader A component of the POS System; for details, please see

Book A, section 4.3.

Requested Internal Entry Point variable used to build the matching kernel
Kernel ID identification during the Combination Selection process

Restart flag Internal reader flag that indicates whether a kernel is being
started for a new transaction or in order to complete online
processing.

RFU Reserved for Future Use (by EMVCo)

Select Next An Outcome

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

SW1 SW2 Status Byte One, Status Byte Two

Page 40 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
 EMV Contactless Book B
Entry Point Specification version 2.1

Terminal A component of the POS System; for details, please see

Book A, section 4.3.

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

TTQ Terminal Transaction Qualifiers

UI User Interface

var Variable length

March 2011 Page 41

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.
EMV Contactless Book B
Entry Point Specification version 2.1

[ End of Document ]

Page 42 March 2011

© 2011 EMVCo, LLC (“EMVCo”). All rights reserved. Any and all uses of the EMV Specifications (“Materials”) shall be
permitted only pursuant to the terms and conditions of the license agreement between the user and EMVCo found at
http://www.emvco.com/specifications.aspx.