B67137 PDF
B67137 PDF
B67137 PDF
B006‐7137‐A000
Issue 1
October 2012
The products described in this document are copyrighted works of NCR Corporation.
This publication supports NCR EMV/ CAM2 functionality for both APTRA Activate NDC Business Services and APTRA
Edge NDC Business Services on Microsoft Windows.
Disclaimer:
It is the policy of NCR Corporation to improve products as technology, components, software and firmware become
available. NCR therefore reserves the right to change specifications without prior notice.
All features, functions and operations described herein may not be marketed by NCR in all parts of the world. In some
instances, photographs are of equipment prototypes. Therefore, before using this document, consult with your NCR
representative or NCR office for information that is applicable and current.
To maintain the quality of our publications, we need your comments on the accuracy, clarity, organisation and value of
this book.
© 2012
By NCR Corporation
Duluth, Georgia, USA
All Rights Reserved
Federal Communications
Commission (FCC) Radio Frequency
Interference Statement
Note: This equipment has been tested and found to comply with
the limits for a Class A digital device, pursuant to Part 15 of the
FCC Rules. These limits are designed to provide reasonable
protection against harmful interference when the equipment is
operated in a commercial environment. This equipment
generates, uses, and can radiate radio frequency energy and, if not
installed and used in accordance with the instruction manual,
may cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause
harmful interference in which case the user will be required to
correct the interference at his own expense.
This digital apparatus does not exceed the Class A limits for radio
Canadian Class A Device noise emissions from digital apparatus set out in the Radio
Declaration Interference Regulations of the Canadian Department of
Communications.
Le présent appareil numérique n’émet pas de bruits
radioélectriques dépassant les limites applicables aux appareils
numériques de la classe A prescrites dans le Réglement sur le
brouillage radioélectrique édicté par le ministère des
Communications du Canada.
APTRA™ NDC Business Services EMV™ Integrated Circuit Card (ICC) Reference Manual iii
Federal Communications Commission (FCC) Radio Frequency Interference Statement
iv APTRA™ NDC Business Services EMV™ Integrated Circuit Card (ICC) Reference Manual
Revision Record
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual v
Confidential and proprietary information of NCR.
Unauthorised use, reproduction and/or distribution is strictly prohibited.
vi APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Table of Contents
Contents
Preface
Chapter 1
Introduction to ICC Processing
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual vii
Table of Contents
Chapter 2
SST to Host Messages
Overview ................................................................................................2‐1
SST Application Version Information ................................................2‐2
SST Hardware Information ..................................................................2‐3
Transaction Request Message Format ................................................2‐4
Message Format ..............................................................................2‐4
CAM Flags .......................................................................................2‐7
Command Reject Messages..................................................................2‐9
Specific Command Rejects.............................................................2‐9
SCRW / MCRW Hardware Error Reporting....................................2‐10
Unsolicited Device Status Message ............................................2‐10
Unsolicited Device Status Message During Chip Power‐Up .2‐10
Solicited Device Status Message .................................................2‐10
ICC Application Solicited/ Unsolicited Error Message Format....2‐11
Issuer Script Results and Completion Data .....................................2‐13
Chapter 3
Host to SST Messages
Overview ................................................................................................3‐1
Customisation Data Commands .........................................................3‐2
EMV Configuration Message...............................................................3‐3
ICC Currency Data Objects Table.................................................3‐5
ICC Transaction Data Objects Table.............................................3‐7
ICC Language Support Table......................................................3‐10
ICC Terminal Data Objects Table ...............................................3‐12
ICC Terminal Acceptable Application IDs Table.....................3‐14
Transaction Reply................................................................................3‐24
Field ‘bc’ ‐ Transaction Data Objects Update Buffer................3‐27
Interactive Transaction Response......................................................3‐28
viii APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Table of Contents
Chapter 4
State Tables
State Tables.............................................................................................4‐1
Chapter 5
ICC Processing
Overview ................................................................................................5‐1
Issuer Script Processing ........................................................................5‐2
Data Object List (DOL) Processing .....................................................5‐3
BER‐TLV Data Object Processing........................................................5‐4
BER‐TLV Data Object Padding .....................................................5‐4
Terminal Specified BER‐TLV Data Objects .................................5‐4
Transaction Data Object List (TDOL) Processing ...........................5‐12
Printing EMV Data Values.................................................................5‐13
MAC Configuration ............................................................................5‐14
Terminal Verification Results (TVR) Processing ............................5‐16
Transaction Status Information (TSI) Processing ...........................5‐20
PIN Encryption and Verification.......................................................5‐22
ICC Application Name Display ........................................................5‐23
Voice Guidance ....................................................................................5‐24
Dynamic Currency Conversion.........................................................5‐25
Error Handling.....................................................................................5‐26
Fake ICC Application Errors .......................................................5‐27
ICC Application Journal Error Message ‐ Activate Only ..............5‐28
ICC Processing Termination ..............................................................5‐30
Authorisation Response Codes .........................................................5‐31
Appendix A
Related Documentation
Overview ...............................................................................................A‐1
Other NDC Business Services Documentation ................................A‐2
Other NCR Documentation ................................................................A‐3
Appendix B
Processing Restrictions
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual ix
Table of Contents
Glossary
Glossary .................................................................................... Glossary‐1
x APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Preface
About This Publication
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual xi
Preface
About This Publication
xii APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Preface
About This Publication
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual xiii
Preface
About This Publication
xiv APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Table of Contents
Introduction to ICC Processing
Chapter 1
Introduction to ICC Processing
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Table of Contents
Introduction to ICC Processing
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Introduction to ICC Processing
A
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 1-1
Introduction to ICC Processing
What Is ICC Processing?
1-2 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Introduction to ICC Processing
EMV Standards Compliance
The CAM ICC processing performed for NDC Business Services has
Implementation been designed to maximize flexibility and performance using
Compliance 1
configurable features. However, you need to be aware that certain
configurations in your SST network may result in partial
non‐compliance with Visa and/or MasterCard requirements.
NCR recommends you seek guidance from MasterCard and Visa to
ensure that your configured options do not contravene these
requirements.
SST Objects 1
Some objects are unsupported because they are not applicable to the
ICC processing performed.
The only objects maintained by CAM ICC are those identified in SST
specified“BER‐TLV Data Object Processing” in Chapter 5,
“Introduction to ICC Processing”. Where the content of an SST
maintained object is expected to be dynamically updated, the
support is as stated in the appropriate processing.
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 1-3
Introduction to ICC Processing
EMV Standards Compliance
1-4 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Introduction to ICC Processing
Host Processing
Host Processing 1
Where applicable, the NDC host is responsible and must cater for
the following requirements:
Brand Approval
PIN Entry
Track 2 Data
Transaction Amount
Fallback
Application Cryptogram
Receipt Printing
Script Errors & Card Declines on Second GENAC Command
Zero Length Objects
Transaction Request EMV Buffer Position
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 1-5
Introduction to ICC Processing
Host Processing
sent to the host in field ‘bd2c’, together with all the other objects the
host has requested.
There are two ways the NDC host can decode the PIN buffer and
pass Track 2 information to the issuer, as follows:
Recognize that the transaction is EMV based, and instead of
using the Track 2 data in the standard NDC Transaction Request
message, use the tag 0x57 data object in the CAM buffer.
However, this requires decoding of the CAM buffer, and
extraction and reformatting of the tag 0x57 object into the
standard Track 2 format; for example, addition of any start/end
sentinels, changing of any field separator characters, removal of
any padding ʹFʹ characters. Alternatively you can:
Use an option in the ICC Terminal Acceptable Application IDs
Table (refer to “ICC Terminal Acceptable Application IDs
Table” on page 3‐14) to force the Track 2 data used by the EMV
transaction to be sent to the host in the standard NDC Track 2
data buffer. To do this, set field f18 ‘Track 2 Data for the Host’ to
the value ‘02’. This method should require no additional host
processing. As no magnetic Track 2 data is sent to the host,
fallback is not possible in some scenarios.
NDC Business Services will populate the Amount Other object (tag
Transaction Amount 1
9F03) with a zero value if the Amount Authorised object (tag 9F02)
is set.
These tags are sent to the host if requested.
NDC Business Services supports the Account Type object (tag 5F57)
Account Type 1
defined by EMV.
Activate Only
Configure the EMVAccountMapping property on the
AccountService class using the .NET Class Configurator to
provide suitable values for the Account Type based on the types of
account in use for a solution.
Edge Only
The account type value to be provided for each Account
AcquirerType in use by a solution is configurable through the
CAM2AccountConfiguration area in
NDCBSCAM2TerminalConfig.xml.
1-6 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Introduction to ICC Processing
Host Processing
SST Configuration 1
Host Processing 1
In order to make the decision to allow fallback, the host must know
the nature and position of the failure during EMV processing. This
can be determined by a combination of the CAM flags in the
Transaction Request message and the OpCode buffer.
The OpCode is used as a mechanism to communicate the POS Entry
mode to the host.
The NDC Customiser must be configured to set the operations code
appropriately for fallback scenarios, based on its access to the
SessionAccessToken property.
Activate Only
Refer to the .NET NDC Customiser On‐line Documentation.
Edge Only
Refer to the NDC Business Services On‐line Documentation.
First GENAC Error 1
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 1-7
Introduction to ICC Processing
Host Processing
An unsolicited CAM status message is sent to the host for the initial
GENAC command that has failed, followed by a Transaction
Request containing CAM data.
By going online, the SST is simply requesting the host to complete
the NDC transaction; the transaction is already complete according
to the ICC.
The NDC host recognizes this request, and in these specific cases
does not involve the card’s issuer, but deals with the request itself
and declines or authorises the magnetic striped based ‘fallback’
transaction.
The host can identify these scenarios by checking the Cryptogram
Information Data object sent by the SST, which for an offline decline
has bits 7 and 8 set to ‘00’, that is, AAC. Additionally, if the
Cryptogram Information Data object communicates “service not
allowed” where bits 1, 2 and 3 are set to ‘1’, ‘0’ and ‘0’ respectively,
the same host behaviour is expected.
In these fallback scenarios, the relevant “CAM Flags” (byte 1 bit 5)
will be set to ‘1’ to enable the host to identify the scenario.
1-8 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Introduction to ICC Processing
Host Processing
The EMV CAM Transaction Request data buffer for NDC Business
Transaction Request EMV Services is provided in field ‘bd’ with buffer identifier ‘5’. For full
Buffer Position 1
details of the Transaction Request message format, refer to the
APTRA NDC Business Services, Reference Manual.
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 1-9
Introduction to ICC Processing
Host Processing
Activate Only
For further information refer to the APTRA NDC Business Services,
Reference Manual.
Edge Only
For further information refer to the .NET NDC Business Services
On‐line Documentation.
EMV commands sent to and from the ICC can be traced by setting
the appropriate KernelTracingLevel for the Card Service. For details
refer to the .NET EMV Card Services On‐line Documentation.
Transaction PIN 99
1-10 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Introduction to ICC Processing
Host Processing
Activate Only
Additional EMV tagged objects may be masked by configuration of
the AdditionalCAMTags property of the
ApplicationConnectionNDC class using the .NET Class
Configurator.
Edge Only
Additional tags for masking can be placed in the
NDCEMVCAM2MaskTags.xml configuration file .
A deployed SST should always provide this default masking as
above, as otherwise sensitive consumer information will be
captured in the Electronic Journal or PD trace log files.
Enabling logging will increase the transaction times but the traces
are useful for debugging issues with specific cards, and obtaining
test evidence in any Brand Approval process.
Additional Journal Tracing
ICC application journal error messages are written to the journal;
see “ICC Application Journal Error Message ‐ Activate Only” on
page 5‐28.
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 1-11
Introduction to ICC Processing
Host Processing
1-12 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Table of Contents
SST to Host Messages
Chapter 2
SST to Host Messages
Overview 2‐1
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Table of Contents
SST to Host Messages
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
SST to Host Messages
B
Overview
Overview 2
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 2-1
SST to Host Messages
SST Application Version Information
2-2 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
SST to Host Messages
SST Hardware Information
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 2-3
SST to Host Messages
Transaction Request Message Format
This section defines the format of the additional smart card data
held in field ‘bd1’ of the Transaction Request message. This message
will also contain the smart card data that the host requires to
authorise a smart card transaction at the SST.
The message is sent during a consumer transaction, either as a full
Transaction Request or in response to an Interactive Transaction
Request.
For full details of the Transaction Request message format, refer to
the APTRA NDC Business Services, Reference Manual.
For details of the issuer script results and completion data which
can be included, see “Issuer Script Results and Completion Data” on
page 2‐13.
Message Format 2
Number of
Field Mandatory/Optional Description
Characters
bd1 1 See Note 1: Buffer identifier. The value is fixed as ʹ5ʹ to indicate smart card data.
2-4 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
SST to Host Messages
Transaction Request Message Format
Number of
Field Mandatory/Optional Description
Characters
bd2c Var See Note 1:, ICC data objects requested by the host.
Note 2: and
Note 3: All the available data objects referenced in field f11 of the ICC
Terminal Acceptable Application IDs Table entry, and for which the
Full/Partial Primary Application ID Value matches the currently
selected ICC Application AID, are included in this field as individual
BER‐TLV formatted data objects. For details, see “ICC Terminal
Acceptable Application IDs Table” on page 3‐14.
This field would contain the following (actual values will vary):
ʹ9F 06 07 A0 00 00 00 08 00 01 57 12 12 34 56 78 90 12 34 56 78 90 D9 90
10 81 23 45 67 89 5A 0A 12 34 56 78 90 12 34 56 78 90 5F 34 01 00 9F 27 01
00 9F 26 08 12 34 56 78 90 12 34 56 9F 10 07 06 01 01 03 A0 00 00 82 02 7C
00 9F 36 02 01 23 8C 15 9F 02 06 9F 03 06 9F 1A 02 95 05 5F 2A 02 9A 03
9C 01 9F 37 04 9F 17 01 03ʹ
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 2-5
SST to Host Messages
Transaction Request Message Format
Number of
Field Mandatory/Optional Description
Characters
bd2d Var See Note 1:, Further ICC data objects requested by the host; see “ICC Transaction
Note 2:, Note 3: Data Objects Table” on page 3‐7.
and Note 4:
All the available data objects referenced within Card Risk
Management Data Object List 1 (CDOL1, tag 0x8C) are included in this
field as individual BER‐TLV formatted data objects.
For example, if CDOL1 references the following tags (as per Visa
Cryptogram Version Number 10):
Then this field would contain the following (actual values will vary):
ʹ9F 02 06 00 00 00 00 20 00 9F 03 06 00 00 00 00 00 00 9F 1A 02 08 26 95 05
80 00 04 00 00 5F 2A 02 08 26 9A 03 00 07 11 9C 01 00 9F 37 04 78 12 25
98ʹ
Note 2: If no data objects are identified, none are present and this
field is not present.
2-6 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
SST to Host Messages
Transaction Request Message Format
There are 16 available CAM flags. These are encoded as the bits in
two bytes, and are converted to ASCII hex (four bytes) for
transmission. Each can have the value 0 or 1, with the following
meanings:
NDC Business
Byte Bit Value Description
Services Support
1 8 ‐ Reserved. ‐
7 ‐ Reserved. ‐
1 ‐ Reserved. ‐
7 0 or 1 0 ‐ Card risk management Data Object List 1 (CDOL1) data valid. No Support
1 ‐ CDOL1 data invalid.
5 ‐ Reserved. ‐
2 0 Reserved. ‐
1 0 Reserved. ‐
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 2-7
SST to Host Messages
Transaction Request Message Format
2-8 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
SST to Host Messages
Command Reject Messages
Value Meaning
B95 Reserved.
B96 Reserved.
B98 The SST did not expect CAM data in the host response to a
Transaction Request as either no CAM data was sent in the
Transaction Request or CAM data was already included in
an earlier response corresponding to the same Transaction
Request.
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 2-9
SST to Host Messages
SCRW / MCRW Hardware Error Reporting
The SST attempts to power on the chip card up to three times. Each
Unsolicited Device Status failure will result in an unsolicited error being sent to the host. This
Message During Chip will have a T‐Code of 8H (as stated above).
Power‐Up 2
2-10 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
SST to Host Messages
ICC Application Solicited/ Unsolicited Error Message Format
Number of
Field Mandatory/Optional Description
Characters
g1/ 1 M Device Identifier Graphic ʹcʹ (Smart card application level error)
e1
FS 1 M Field Separator.
FS 1 M Field Separator.
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 2-11
SST to Host Messages
ICC Application Solicited/ Unsolicited Error Message Format
Number of
Field Mandatory/Optional Description
Characters
FS ‐ ‐ Field Separator.
Note 2: These fields will show the length of the command and
response data even if CmdData and RspData are not included.
2-12 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
SST to Host Messages
Issuer Script Results and Completion Data
When one or more issuer scripts are sent to the SST, the host will
require the results of the issuer script processing. The following are
scenarios in which Valid issuer scripts have been received by the
SST:
A valid Transaction Reply containing valid CAM data,
including issuer scripts, has been received.
A valid ITR (Interactive Transaction Response) containing valid
CAM data, including issuer scripts, has been received. A
corresponding valid Transaction Reply, with no CAM data of its
own, has also been received.
If one or more issuer scripts have been received by the SST, the
issuer script processing results are appended to the field ʹg4ʹ/ʹfʹ and
sent to the host in the next solicited status message (except for
command rejects or specific command rejects). For the message
format, see the table on the next page.
The selected ICC application AID will have a matching table entry
in the ʹICC Terminal Acceptable AIDs Tableʹ. This entry identifies
data objects required by the host upon completion of ICC
processing (also referred to as Completion Data). For details see
“ICC Terminal Acceptable Application IDs Table” on page 3‐14.
If available, the required data objects are provided to the host on the
next solicited status message (except for command rejects or specific
command rejects) sent in response to a valid Transaction Reply,
where valid CAM data has been received either in the Transaction
Reply or an earlier related valid ITR. If these conditions are met, the
required data objects are appended to the end of field ʹg4ʹ/ʹfʹ. For the
message format, see the table on the next page.
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 2-13
SST to Host Messages
Issuer Script Results and Completion Data
Number of
Field Mandatory/Optional Description
Characters
GS 1 M Group Separator
Then this field would contain the following (values will vary):
ʹ9F 27 01 00 9F 26 08 12 34 56 78 90 12 34 56 9F 10 07 06 01 01 03 A0 00 00
95 05 00 00 04 00 00 9B 02 74 00ʹ
2-14 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
SST to Host Messages
Issuer Script Results and Completion Data
Number of
Field Mandatory/Optional Description
Characters
For example:
If the script ID sent as part of the script is ‘9F180499999999’,
the script results will have a script identified field of
‘9F180499999999’
If the script ID sent as part of the script is ‘9F1800’, the script
results will have a script identified field of ‘9F1800’
If no script ID is sent as part of the script, the script results
will have a script identified field of ‘9F180400000000’.
Note 1: The first group separator and field ʹaʹ are omitted if the
application type for the data has already been sent in the message to
which it is being attached. For example, they would not be present
in an ʹICC Applicationʹ device status message, but would be present
in any other status message and the Transaction Request ʹLast
Transaction Status Informationʹ buffer (buffer id ʹ2ʹ).
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 2-15
SST to Host Messages
Issuer Script Results and Completion Data
Note 3: If a data object is identified, but not available, then the data
object will not be present. If no data objects are identified or none
are available, then field ʹbʹ is not present.
Note 5: Fields ʹcʹ to ʹeʹ inclusive are repeated for the number of
scripts present in the ITR or Transaction Reply CAM data, and are
configured to record the processing status of each script. If no
scripts are present, the third group separator and fields ʹcʹ through
ʹeʹ inclusive are omitted. If four scripts were present, the third group
separator is present, and fields ʹcʹ through ʹeʹ inclusive are repeated
four times.
Note 6: The values in fields ʹbʹ and ʹeʹ are normally binary, but are
converted to ASCII hex for transmission. For example, the
single‐byte value 0x9A would be transmitted as the two‐byte value
ʹ9Aʹ. The table above shows the message format transmitted by the
SST.
2-16 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Table of Contents
Host to SST Messages
Chapter 3
Host to SST Messages
Overview 3‐1
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Table of Contents
Host to SST Messages
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Host to SST Messages
C
Overview
Overview 3
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 3-1
Host to SST Messages
Customisation Data Commands
Message Message
Identifier Command
Class Sub-Class
8 1 ‐ EMV Configuration ‐
ICC Currency Data Objects Table
8 2 ‐ EMV Configuration ‐
ICC Transaction Data Objects Table
8 3 ‐ EMV Configuration ‐
ICC Language Support Table
8 4 ‐ EMV Configuration ‐
ICC Terminal Data Objects Table
8 5 ‐ EMV Configuration ‐
ICC Terminal Acceptable AIDs Table
3-2 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Host to SST Messages
EMV Configuration Message
Number of
Field Mandatory/ Optional Description
Characters
c 1 O Response Flag.
Included for future use and ignored by the SST.
FS 1 M Field Separator.
FS 1 M Field Separator.
e 1 M Message Sub‐Class.
ʹ1ʹ ‐ ʹICC Currency Data Objects Tableʹ data.
ʹ2ʹ ‐ ʹICC Transaction Data Objects Tableʹ data.
ʹ3ʹ ‐ ʹICC Language Support Tableʹ data.
ʹ4ʹ ‐ ʹICC Terminal Data Objects Tableʹ data.
ʹ5ʹ ‐ ʹICC Terminal Acceptable AIDs Tableʹ data.
FS 1 M Field Separator.
See the following sections in this chapter for each message sub‐class.
Eight digit ASCII hex value used to authenticate the message data.
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 3-3
Host to SST Messages
EMV Configuration Message
Note 1: The field separator and MAC Data field are only included if
the flag settings are correct. For details, refer to the APTRA NDC
Business Services, Reference Manual.
3-4 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Host to SST Messages
EMV Configuration Message
Message Format 3
The following details are provided for situations where the host will
still be providing this download table, to ensure valid message
content.
If the host downloads ICC Currency Data Objects Table data and it
does not conform to the above format, the NDC CAM application
generates a solicited error message with a Specific Command Reject
(value ʹB91ʹ).
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 3-5
Host to SST Messages
EMV Configuration Message
Number of
Field Mandatory/ Optional Description
Characters
This field contains the Transaction Currency Code (tag 0x5F2A) and
the Transaction Currency Exponent (tag 0x5F36) data objects.
For example:
ʹ77 09 5F 2A 02 08 26 5F 36 01 02ʹ
Where:
ʹ77ʹ ‐ ʹResponse Format 2ʹ data object tag
ʹ09ʹ ‐ ʹResponse Format 2ʹ data object length
ʹ5F 2Aʹ ‐ ʹTransaction Currency Codeʹ data object tag
ʹ02ʹ ‐ ʹTransaction Currency Codeʹ data object length
ʹ08 26ʹ ‐ ʹTransaction Currency Codeʹ data object value
ʹ5F 36ʹ ‐ ʹTransaction Currency Exponentʹ data object tag
ʹ01ʹ ‐ ʹTransaction Currency Exponentʹ data object length
ʹ02ʹ ‐ ʹTransaction Currency Exponentʹ data object value
Note 1: If field ʹf1ʹ is greater than ʹ01ʹ, the fields ʹf2ʹ and ʹf3ʹ are
repeated for the number of times indicated by field ʹf1ʹ.
Note 2: The data contained within fields ʹf1ʹ, ‘f2’ and ‘f3’ is normally
in binary. This field will be converted to ASCII hex for transmission.
Therefore the single‐byte value 0x9A would be transmitted as the
two‐byte value ʹ9Aʹ. The format description above shows the data
field sizes as sent by the host.
3-6 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Host to SST Messages
EMV Configuration Message
Activate Only
ICC Transaction Data
This table is obsolete in APTRA Activate NDC Business Services
Objects Table 3
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 3-7
Host to SST Messages
EMV Configuration Message
The configuration data required for this table is provided via the
EMV Configuration Message (sub‐class of ʹ2ʹ). The data is held in
field ʹfʹ of the EMV Configuration Message as follows:
Number of Mandatory /
Field Description
Characters Optional
Note: Only primitive BER‐TLV data objects of a type known to the SST
are stored for use in ICC processing.
This field contains the ʹTransaction Typeʹ (tag 0x9C) data object and
the MasterCard proprietary ʹTransaction Category Codeʹ (tag 0x9F53)
data object.
For example:
ʹ77 07 9C 01 01 9F53 01 5Aʹ
Where:
ʹ77ʹ = ʹResponse Format 2ʹ data object tag
ʹ07ʹ = ʹResponse Format 2ʹ data object length
ʹ9Cʹ = ʹTransaction Typeʹ data object tag
ʹ01ʹ = ʹTransaction Typeʹ data object length
ʹ01ʹ = ʹTransaction Typeʹ data object value
ʹ9F53ʹ = ʹTransaction Category Codeʹ data object tag
ʹ01ʹ = ʹTransaction Category Codeʹ data object length
‘5A’= ‘Transaction Category Code’ data object value
If the host downloads ICC Transaction Data Objects Table data and
it does not conform to the above format, the NDC CAM application
generates a solicited error message identifying a Specific Command
Reject (value ʹB92ʹ).
Note 1: If field ʹf1ʹ is greater than ʹ01ʹ, the fields ʹf2ʹ and ʹf3ʹ are
repeated for the number of times indicated by field ʹf1ʹ.
3-8 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Host to SST Messages
EMV Configuration Message
Example Data 3
Spaces are included for clarity, but do not appear in the actual
message to the SST.
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 3-9
Host to SST Messages
EMV Configuration Message
Number of
Field Mandatory/ Optional Description
Characters
ASCII character value in the range ʹaaʹ to ʹzzʹ inclusive (that is, lower
case alphabetic characters only, with no numerics).
3-10 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Host to SST Messages
EMV Configuration Message
Number of
Field Mandatory/ Optional Description
Characters
This value is used as the screen base, provided the ICC language
preference finds a match against the language code in field ʹf2ʹ.
This value is used to set the digital audio directory base, provided the
ICC language preference finds a match against the language code in
field ʹf2ʹ.
Three different ASCII decimal values, each in the range ʹ0ʹ to ʹ7ʹ
inclusive. No duplicate values should be present (that is, ʹ001ʹ is not
acceptable).
Three ASCII character values, each with a value in the range ʹAʹ to ʹDʹ
or ʹFʹ to ʹIʹ inclusive, or ʹ@ʹ.
If the host downloads ICC Language Support Table data and it does
not conform to the above format, the NDC CAM application will
generate a solicited error message identifying a Specific Command
Reject (value ʹB93ʹ) and the downloaded data is ignored.
Note 1: If field ʹf1ʹ is greater than ʹ01ʹ, the fields ʹf2ʹ through ʹf6ʹ
inclusive are repeated for the number of times indicated by field ʹf1ʹ.
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 3-11
Host to SST Messages
EMV Configuration Message
3-12 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Host to SST Messages
EMV Configuration Message
The configuration data required for this table is provided via the
EMV Configuration Message (sub‐class of ʹ4ʹ). The data is held in
field ʹfʹ of the EMV Configuration Message as follows:
Number of
Field Mandatory/ Optional Description
Characters
Note: Only the data objects listed above this table are made available
for use in ICC processing.
This field contains the ʹTerminal Country Codeʹ (tag 0x9F1A) and
ʹTerminal Typeʹ (tag 0x9F35) data objects.
For example:
ʹ77 09 9F 1A 02 08 26 9F 35 01 14ʹ
Where
ʹ77ʹ ‐ ʹResponse Format 2ʹ data object tag
ʹ09ʹ ‐ ʹResponse Format 2ʹ data object length
ʹ9F 1Aʹ ‐ ʹTerminal Country Codeʹ data object tag
ʹ02ʹ ‐ ʹTerminal Country Codeʹ data object length
ʹ08 26ʹ ‐ ʹTerminal Country Codeʹ data object value
ʹ9F 35ʹ ‐ ʹTerminal Typeʹ data object tag
ʹ01ʹ ‐ ʹTerminal Typeʹ data object length
ʹ14ʹ ‐ ʹTerminal Typeʹ data object value
If the host downloads ICC Terminal Data Objects data and it does
not conform to the above format, the NDC CAM application
generates a solicited error message with a Specific Command Reject
(value ʹB94ʹ) and the downloaded data is ignored.
Note: The data contained within field ʹfʹ is normally in binary. This
field is converted to ASCII hex for transmission; for example, the
single‐byte value 0x9A is transmitted as the two‐byte value ʹ9Aʹ. The
format description in the previous table shows the data field sizes as
they are sent to the host.
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 3-13
Host to SST Messages
EMV Configuration Message
Shortly after inserting an ICC into the card reader, each of the
previously downloaded table entries is processed in turn.
An attempt is made to select the first table entry’s Primary AID on
the ICC.
If the Primary AID exists on the card, this is added to the Candidate
List and processing continues with attempts to select each of the
Secondary AIDs for this table entry in turn. If a Secondary AID is
found to be present then this is also added to the Candidate List.
Once complete with the first table entry, the process repeats for each
of the following table entries.
On completing all table entries there is now a Candidate List of
EMV applications, from which the application to be used for EMV
transaction processing can be selected.
No table entries are discarded during processing of the table entries.
An attempt will always be made to select each of the Primary AIDs
for every table entry.
The SST reads records from the Payment System Directory on the
chip and attempts to match any applications found on the chip with
those supported by the SST. Matching applications are added to the
Candidate List.
Where the SST encounters a problem using the PSE method, or
simply finds no matching applications, it will revert to using the List
of Applications Method.
3-14 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Host to SST Messages
EMV Configuration Message
The configuration data required for this table is provided via the
EMV Configuration Message (sub‐class of ʹ5ʹ). Each table entry is
held in field ʹfʹ of the EMV Configuration Message as follows:
Number of
Field Mandatory/ Optional Description
Characters
f1 2 M Entry Number.
The length of the AID must be in the range ʹ01Hʹ to ʹ10Hʹ inclusive (1 to
16 decimal inclusive).
Note: This length is also the number of ICC AID bytes that will be
checked when compared to the Full / Partial Primary AID value (field
ʹf3ʹ).
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 3-15
Host to SST Messages
EMV Configuration Message
Number of
Field Mandatory/ Optional Description
Characters
f10 2 See Note 1: and Number of Data Object(s) for Transaction Request.
Note 2:
ASCII hex value in range ʹ00ʹ through ʹFFʹ inclusive.
f11 Var. See Note 1: and Data Object(s) for Transaction Request.
Note 2: ASCII hex value.
f12 2 See Note 1: and Number of Data Object(s) for Completion Data.
Note 2:
ASCII hex value in range ʹ00ʹ through ʹFFʹ inclusive.
f13 Var. See Note 1: and Data Object(s) for Completion Data.
Note 2:
ASCII hex value.
3-16 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Host to SST Messages
EMV Configuration Message
Number of
Field Mandatory/ Optional Description
Characters
The length of the AID must be in the range ʹ01ʹ to ʹ10ʹ inclusive (1 to 16
decimal inclusive).
(M if any 00 (Default) Use the card’s magnetic stripe data in the track 2
following fields buffer field of the transaction request.
are present)
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 3-17
Host to SST Messages
EMV Configuration Message
Number of
Field Mandatory/ Optional Description
Characters
01 Use the card’s magnetic stripe data in the track 2 buffer field of
the transaction request, unless there is no track 2 data
available, in which case use the ICC track 2 data defined in
field f19.
02 Always place the ICC track 2 data defined in field f19 in the
track 2 buffer field.
(M if any 00 (Default) Use the Track 2 Equivalent Data (tag 0x57) for all
following fields NDC processing, but if it is not supplied by the ICC, produce
are present) an ICC level fake error and terminate the ICC processing.
01 Use the Track 2 Equivalent Data (tag 0x57) for all NDC
processing, but if it is not supplied by the ICC, use the track 2
data from the magnetic card.
03 Use the Track 2 Equivalent Data (tag 0x57) for all NDC
processing, but if it is not supplied by the ICC, construct
simulated Track 2 data. For details of track 2 data simulation,
see “Simulated Track 2 Data” on page 3‐22.
f20 2 O (Mandatory Length of Additional Track 2 Data in the following field (f21).
if f19 is set to 03
or 04. Range 01 to 21 (ASCII Hexadecimal).
Should be
omitted for f19 For example, “21” hexadecimal means 33 characters to follow.
set to 00, 01, 02)
For details of track 2 data simulation, see “Simulated Track 2 Data” on
page 3‐22.
3-18 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Host to SST Messages
EMV Configuration Message
Note 3: Fields ʹf15ʹ and ʹf16ʹ are repeated as appropriate to the value
in field ʹf14ʹ. If field ʹf14ʹ is zero then fields ʹf15ʹ & ʹf16ʹ are omitted.
Note 7: If field ʹf1ʹ is sent without fields ʹf2ʹ through ʹf21ʹ, the entry
to which field ʹf1ʹ refers is deleted from the table.
0A 9F06575A5F349F279F269F10829F368C
05 9F279F269F10959B
01 06 A00000000201
0A 9F06575A5F349F279F269F10829F368C
05 9F279F269F10959B
00
0A 9F06575A5F349F279F269F10829F368C
05 9F279F269F10959B
02 07 A0000000031010
07 A0000000041010
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 3-19
Host to SST Messages
EMV Configuration Message
0A 9F06575A5F349F279F269F10829F368C
05 9F279F269F10959B
02 07 A0000000032010
07 A0000000033010
0A 9F06575A5F349F279F269F10829F368C
05 9F279F269F10959B
00
0A 9F06575A5F349F279F269F10829F368C
05 9F279F269F10959B
00
0A 9F06575A5F349F279F269F10829F368C
05 9F279F269F10959B
02 07 A0000000046000
07 A0000000043060
0A 9F06575A5F349F279F269F10829F368C
05 9F279F269F10959B
00
0A 9F06575A5F349F279F269F10829F368C
05 9F279F269F10959B
00
0A 9F06575A5F349F279F269F10829F368C
05 9F279F269F10959B
00
0A 9F06575A5F349F279F269F10829F368C
05 9F279F269F10959B
00
Where:
<GS> is a group separator.
Spaces and new lines are included for clarity, but do not appear in
the actual message to the SST.
3-20 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Host to SST Messages
EMV Configuration Message
This example has eleven CAM ICC application Primary AIDs, all
with a version number in the range 0x0000 to 0x0001 inclusive.
All entries identify that the following are to be included in the
transaction request:
Application Identifier (AID) (tag 0x9F06)
Track 2 Equivalent Data (tag 0x57)
Application PAN (tag 0x5A)
Application PAN Sequence Number (tag 0x5F34)
Cryptogram Information Data (tag 0x9F27)
Application Cryptogram (tag 0x9F26)
Issuer Application Data (tag 0x9F10)
Application Interchange Profile (AIP) (tag 0x82)
Application Transaction Counter (ATC) (tag 0x9F36) and
CDOL1 (tag 0x8C) data objects.
All entries identify that the following are to be included as
Completion Data in the first solicited status message that concludes
ICC processing for a transaction:
Cryptogram Information Data (tag 0x9F27)
Application Cryptogram (tag 0x9F26)
Issuer Application Data (tag 0x9F10)
Terminal Verification Results (TVR) (tag 0x95) and
Transaction Status Indicator (TSI) (tag 0x9B) data objects.
Entries ʹ00ʹ, ʹ02ʹ, ʹ03ʹ and ʹ06ʹ have secondary AID values.
Entries ʹ03ʹ and ʹ07ʹ have Default Application Label values.
Entries ʹ00ʹ, ʹ01ʹ and ʹ02ʹ have a ʹPrimary AID Terminal Action Code ‐
Denialʹ value indicating that a transaction should be declined offline
by the SST when:
Requested service is not allowed
ICC application has expired
ICC application is not yet effective.
Entries ʹ03ʹ, ʹ04ʹ, ʹ05ʹ and ʹ06ʹ have a ʹPrimary AID Terminal Action
Code ‐ Denialʹ value indicating that a transaction should be declined
offline by the SST only when the requested service is not allowed.
Entries ʹ07ʹ, ʹ08ʹ, ʹ09ʹ and ʹ0Aʹ have a ʹPrimary AID Terminal Action
Code ‐ Denialʹ value indicating that a transaction should be declined
offline by the SST when:
Offline static data authentication failed (not performed by SST).
Card is on the SST exception file (not performed by SST).
Requested service is not allowed.
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 3-21
Host to SST Messages
EMV Configuration Message
If simulated track 2 data is selected, the SST will construct this data
from the following ICC data objects:
Primary Account Number (0x5A),
Application Expiry Date (0x5F24) and
additional track 2 data downloaded in field f21 of the “ICC
Terminal Acceptable Application IDs Table”.
The simulated track two data is constructed as follows:
Primary
Application Additional
Start Account Field End
Expiry Date Track 2
Sentinel Number Separator Sentinel
(YYMM) Data
(PAN)
and
5F24 03 050301
then the simulated Track 2 data used by NDC for the transaction
would be:
;4916245531413011=05032231701?
As f18 is set to 01 in this example, this would only be sent to the host
if there was no track 2 data read successfully from the card, when
the data would be placed into the track 2 buffer of the Transaction
Request message.
3-22 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Host to SST Messages
EMV Configuration Message
When fields f18 to f21 are not supported by the host, they cannot be
configured locally.
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 3-23
Host to SST Messages
Transaction Reply
Transaction Reply 3
Note: Fields ʹat2bʹ, ʹat2cʹ, ʹat2dʹ, ‘bc2b’, ‘bc2d’, ‘bc2g’ are normally
binary values. These values are converted to ASCII hex for
transmission; for example, the single‐byte value 0x9A would be
transmitted as the two‐byte value ʹ9Aʹ. The table below shows the
data format as sent from the host.
Number of
Field Mandatory/ Optional Description
Characters
at1 1 See Note 1: Buffer Identifier. The value is fixed as ʹ5ʹ to indicate smart card data.
3-24 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Host to SST Messages
Transaction Reply
Number of
Field Mandatory/ Optional Description
Characters
at2b See Note 2: Issuer Authentication Data (up to 36 bytes) in BER‐TLV format, as
follows:
M
2 ʹ91ʹ for tag 0x91
M
2 Length, in hex, of the following Issuer Authentication Data. The length
value must be in the range 0x08 (ʹ08ʹ) to 0x10 (ʹ10ʹ) inclusive.
M
up to 16 Authorisation Response Cryptogram (ARPC) and any scheme
specific/proprietary Issuer Authentication Data.
at2c See Note 3: Authorisation Response Code (8 bytes) in BER‐TLV format, as follows:
Script commands will be held within script data objects and will be
identified with the tag value of 0x86.
Where:
72 = Issuer Script Tag
17 = Length of Data
9F 18 = Script ID Tag
04 = Length of Script ID
12 34 56 78 = Script ID
86 = Issuer Script Command Template Tag
0E = Issuer Script Command Template Tag length
04 DA 9F 58 09 05 01 23 45 67 89 AB CD EF = Issuer Script Command
(PUT DATA)
Note 1: The field separator, buffer identifier and smart card data
identifier may only be omitted from the Transaction Reply or
Interactive Transaction Reply if CAM data is not expected.
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 3-25
Host to SST Messages
Transaction Reply
Note 4: By default the card service does not place any limit on the
length of the EMV issuer scripts that are processed from the host
and no reject is sent relating to script length. If a limit is required
then this is set using the Card Service IssuerScriptLimit property
which is used by the EMV token during processing of the scripts.
Note 5: Issuer script(s) are optional and may be omitted. If this field
is not omitted, the field separator, buffer identifier and smart card
data identifier must also be present. For further details on Issuer
Scripts, see “Issuer Script Results and Completion Data” on
page 2‐13.
3-26 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Host to SST Messages
Transaction Reply
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 3-27
Host to SST Messages
Interactive Transaction Response
3-28 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Table of Contents
State Tables
Chapter 4
State Tables
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Table of Contents
State Tables
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
State Tables
D
State Tables
State Tables 4
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 4-1
State Tables
State Tables
4-2 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Table of Contents
ICC Processing
Chapter 5
ICC Processing
Overview 5‐1
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Table of Contents
ICC Processing
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
ICC Processing
E
Overview
Overview 5
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 5-1
ICC Processing
Issuer Script Processing
There are two types of issuer scripts which may be sent in the
response from the host, both of which are distinguished by their
tags. If the issuer script has a tag of 0x71, the issuer script is to be
submitted to the ICC immediately before the second GENERATE AC
command. If the issuer script has a tag of 0x72, the issuer script is to
be submitted to the ICC after the second GENERATE AC command.
If the issuer script processing is being performed before the second
GENERATE AC command, all the scripts beginning with tag 0x71
are executed sequentially as they are found in the the host response.
Similarly, each command within each script is also executed
sequentially as found.
If the issuer script processing is being performed after the second
GENERATE AC command, all the scripts beginning with tag 0x72
are executed sequentially as they are found in the the host response.
Similarly, each command within each script is also executed
sequentially as found.
Script processing results are sent to the host on the first available
solicited status message to be transmitted, following receipt of the
transaction reply currently being processed.
In an NDC Business Services solution, invalidly formatted issuer
script data is not rejected during transaction reply validation, prior
to issuer script processing. Instead, an attempt to process each script
is made until the script is complete, an ICC level error occurs, or a
formatting error is discovered. The results of issuer script
processing are passed to the host within the next solicited status
message. For details of issuer script process, see “Issuer Script
Results and Completion Data” on page 2‐13.
5-2 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
ICC Processing
Data Object List (DOL) Processing
All Data Object List (DOL) objects are processed in accordance with
the rules defined by the EMV standards. For the purpose of
processing objects identified by a DOL, the object type is also as
defined in the EMV standard.
In addition, the MasterCard proprietary Transaction Category Code
data object (tag 0x9F53) is defined as having the type
‘alphanumeric’ (ASCII encoded).
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 5-3
ICC Processing
BER-TLV Data Object Processing
ISO 7816‐4 indicates that one or more padding bytes, of the value
BER‐TLV Data Object 0xFF or 0x00, may precede or trail BER‐TLV formatted data objects.
Padding 5
This padding is to allow for data deletion and modification on the
ICC.
ISO 7816‐4 also indicates that BER‐TLV data objects cannot have a
tag starting with 0x00 or 0xFF.
Although padding is supported for BER‐TLV data obtained from
the ICC, all messages to the SST from the host must not include
padding in BER‐TLV formatted message fields. If padding is
included in a message, an appropriate reject response will be sent to
the host.
The messages from the SST to the host do not include any padding
in BER‐TLV formatted fields.
5-4 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
ICC Processing
BER-TLV Data Object Processing
No. of Configuration
Element Name Description Tag Value
bytes Options
Account Type Indicates the type of account 0x5F57 1 Value local config
selected on the SST. representing the
account type in 2
0x00 ‐ Default / unspecified Binary Coded
Decimal (BCD)
0x10 ‐ Savings digits.
0x20 ‐ Cheque
0x30 ‐ Credit
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 5-5
ICC Processing
BER-TLV Data Object Processing
No. of Configuration
Element Name Description Tag Value
bytes Options
Application Application version supported 0x9F09 2 Value taken from host download
Version by the SST. the ‘Primary AID
Number Highest
Application
Version Number’
field in the
selected ICC
applicationʹs
corresponding
‘ICC Terminal
Acceptable AID
Table’ entry.
See“ICC Terminal
Acceptable
Application IDs
Table” on
page 3‐14.
Authorisation Value generated by the 0x8A 2 This data object host download
Response Code authorisation authority for an will not be (Reply)
approved transaction available if tag
0x8A is not
provided by the
issuer in the
appropriate
Transaction
Reply/Interactive
Transaction
Response for the
transaction being
processed.
5-6 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
ICC Processing
BER-TLV Data Object Processing
No. of Configuration
Element Name Description Tag Value
bytes Options
Interface Device This Interface Device Serial 0x9F1E 8 The ATM serial local config,
Serial Number Number is the unique identifier number should be host download
for the SST. used to populate
this value.
This object must be locally If no serial
configured in an NDC Business number has been
Services solution. configured then
this object will not
be populated.
Issuer Script The results of the processing of 0x9F5B Var The results of automatic
Results any issuer scripts. processing the
Issuer scripts. If
no issuer scripts
have been
received then the
object will not be
populated.
(Activate only) Indicates the name and location 0x9F4E var alphanumeric local config,
Merchant Name of the merchant. characters. host download.
and Location
Point‐of‐Service Indicates the method by which 0x9F39 1 2 BCD digits Not directly
(POS) Entry the PAN was entered, provided by the
Mode according to the first two digits NDC Business
of the ISO 8583:1987 POS Entry Services. The
Mode NDC
Customiser can
be configured to
map an
OPCODE digit
for this purpose.
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 5-7
ICC Processing
BER-TLV Data Object Processing
No. of Configuration
Element Name Description Tag Value
bytes Options
Terminal Action Specifies the acquirer‘s ‐ 5 5 bytes used for host download
Code ‐ Denial conditions that cause the denial Terminal Action
of a transaction without an Analysis in
attempt to go online. conjunction with
the Terminal
Verification
Results (TVR).
Terminal Indicates the card data input, 0x9F33 3 The default value Activate:
Capabilities CVM and security capabilities provided is 0x60 automatic
of the SST. 0x40 0x20 (default),
local config,
0x60 ‐ Magnetic stripe and ICC When host download
with contacts capabilities. downloaded or
configured Edge:
0x40 ‐ On‐line enciphered PIN locally, only the automatic
is used for CVM. following bits of (default),
data can be host download
0x20 ‐ Card capture can be overridden in the
performed. default values:
byte 1, bits 8, 7, 6
byte 2, bits 8, 7, 4
byte 3 bit 6.
5-8 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
ICC Processing
BER-TLV Data Object Processing
No. of Configuration
Element Name Description Tag Value
bytes Options
Terminal Indicates the data input and 0x9F40 5 The default value Activate:
Capabilities output capabilities of the SST. provided is 0x8E automatic
(Additional) 0x00 0xB0 0x13 (default),
0x8E‐ payment, transfer, 0xFF local config,
enquiry and cash transactions host download
can be performed on this SST. Where byte 4
(0x13) is ORʹd Edge:
0x00 ‐ reserved for future use. with: automatic
(default),
0xB0 ‐ SST has numeric, 0x20 ‐ if TTU is host download
command and function keys. present
Terminal Floor A default floor limit of zero will 0x9F1B 4 Zero by default. automatic
Limit be set by the SST. (default),
local config,
host download
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 5-9
ICC Processing
BER-TLV Data Object Processing
No. of Configuration
Element Name Description Tag Value
bytes Options
Transaction Counter maintained by the SST 0x9F41 2 Value in the range automatic
Sequence that is incremented by one for 0001 to 9999
Counter each successful initialisation of (decimal)
an ICC application. inclusive, encoded
in BCD.
The counter is
cyclic, and
defaults to 0001
(decimal) on
power up.
5-10 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
ICC Processing
BER-TLV Data Object Processing
No. of Configuration
Element Name Description Tag Value
bytes Options
Note 1: Any objects not known by the SST (that is, not in the list
above) and not retrieved from the ICC , but referenced by a DOL,
are processed following the DOL processing rules identified in
“Data Object List (DOL) Processing”.
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 5-11
ICC Processing
Transaction Data Object List (TDOL) Processing
If the Transaction Certificate (TC) Hash Value (tag 0x98) data object
is requested by a DOL (principally CDOL1 or CDOL2), then
theʺEMV Kernelʺ needs to calculate the value for the data object so
that it can be output as part of the DOL data.
Processing the output of the TDOL with this algorithm provides a
checksum/signature which is 20 bytes long.
Activate Only
A new DefaultTDOL can be configured on NDCCardIssuerInfo
using the .NET Class Configurator.
5-12 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
ICC Processing
Printing EMV Data Values
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 5-13
ICC Processing
MAC Configuration
MAC Configuration 5
5-14 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
ICC Processing
MAC Configuration
Number of
Field Mandatory/ Optional Description
Characters
FS 1 O Field Separator.
o 5 See Note 1: and For each offset position, if the field contains ‘0’, no MAC is added to the
Note 2: message indicated. If it contains ‘1’, a MAC is added to the message.
Offset Description
0 ICC Currency Data Objects Table message
1 ICC Transaction Data Objects Table message
2 ICC Language Support Table message
3 ICC Terminal Data Objects message
4 ICC Terminal Acceptable AIDs Table message
Note 1: This field may be truncated, that is, trailing characters may
be omitted. The omitted characters have the value zero.
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 5-15
ICC Processing
Terminal Verification Results (TVR) Processing
3 0 Reserved.
2 0 Reserved.
1 0 Reserved.
If the version number returned from the Application Version Number (tag 0x9F08) data
object during ICC application processing is not within the specified range for the
matching ICC Terminal Acceptable AIDs Table entry (that is, whose Full/Partial Primary
AID Value matched the ICC AID for the ICC application being processed), this bit is set to
1.
For more details, see “ICC Terminal Acceptable Application IDs Table” on page 3‐14.
If the version number is in range, or if the Application Version Number data object was
not obtained from the ICC, or has no value field, this bit is set to 0.
5-16 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
ICC Processing
Terminal Verification Results (TVR) Processing
If the date from the Transaction Date (tag 0x9A) data object is after the expiry date
returned from the Application Expiration Date (tag 0x5F24) data object during ICC
Application processing, this bit is set to 1.
Otherwise, if the date is not after the expiry date, or if the Application Expiration Date
data object is not available, this bit is set to 0.
Note: If either data object two‐digit year value is in the range 00 to 49, the corresponding
full year value is 2000 to 2049. However, if the data object two‐digit year value is in the
range 50 to 99, the full year value is 1950 to 1999.
If the date from the Transaction Date (tag 0x9A) data object is before the effective date
returned from the Application Effective Date (tag 0x5F25) data object during ICC
application processing, this bit is set to 1.
Otherwise, if the date is not before the effective date, or if the Application Effective Date
data object is not available, this bit is set to 0.
Note: If either data object two‐digit year value is in the range 00 to 49, the corresponding
full year value is 2000 to 2049. However, if the data object two‐digit year value is in the
range 50 to 99, the full year value is 1950 to 1999.
3 0 Reserved
2 0 Reserved
1 0 Reserved
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 5-17
ICC Processing
Terminal Verification Results (TVR) Processing
5 0/1 PIN Entry Required But PIN Pad Not Present/Not Working Flag
May be set to 1 (PIN Entry Required But PIN Pad Not Present/Not Working) as a result of
CVM processing.
4 0 PIN entry required, PIN Pad present and PIN was entered.
If the PIN block is being included in the Transaction Request message and the CVM list
includes an On‐line PIN condition, this bit is set to 1. Otherwise, it is set to 0.
Note: This bit will only be set if the CVM chosen for the transaction was On‐line
enciphered PIN. If CVM processing failed or was not done then this bit will not be set.
2 0 Reserved
1 0 Reserved
If floor limit checking was performed and the amount was equal to or above the floor
limit, this bit is set to 1. Otherwise, it is set to 0.
3 0 Reserved
2 0 Reserved
1 0 Reserved
If the TC Hash Value (tag 0x98) was requested during DOL processing and the default
value for the TDOL (tag 0x97) data object was used, this bit is set to 1. Otherwise, it is set
to 0.
5-18 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
ICC Processing
Terminal Verification Results (TVR) Processing
If any tag 0x71 issuer scripts fail (returned in a host response to the Transaction Request),
this bit is set to 1.
If any tag 0x72 issuer scripts fail (returned in a host response to the Transaction Request),
this bit is set to 1.
4 0 Reserved
3 0 Reserved
2 0 Reserved
1 0 Reserved
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 5-19
ICC Processing
Transaction Status Information (TSI) Processing
If the ICC command EXTERNAL AUTHENTICATE has been submitted to the ICC, this
bit is set to 1. Otherwise, it is set to 0.
If the Terminal Floor Limit is downloaded from the host, terminal risk management is
performed and this bit is set to 1. Otherwise, it is set to 0.
If an attempt is made to process one or more issuer scripts (tag 0x71 or tag 0x72), this bit is
set to 1. Otherwise, it is set to 0.
2 0 Reserved
1 0 Reserved
2 8 0 Reserved
7 0 Reserved
6 0 Reserved
5 0 Reserved
4 0 Reserved
5-20 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
ICC Processing
Transaction Status Information (TSI) Processing
3 0 Reserved
2 0 Reserved
1 0 Reserved
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 5-21
ICC Processing
PIN Encryption and Verification
5-22 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
ICC Processing
ICC Application Name Display
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 5-23
ICC Processing
Voice Guidance
Voice Guidance 5
5-24 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
ICC Processing
Dynamic Currency Conversion
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 5-25
ICC Processing
Error Handling
Error Handling 5
5-26 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
ICC Processing
Error Handling
For the ICC application error message format, see “ICC Application
Solicited/ Unsolicited Error Message Format” on page 2‐11. For the
journal error format see “ICC Application Journal Error Message ‐
Activate Only” on page 5‐28.
Additional ICC application data may also be sent when a solicited
device status message is sent, see “Issuer Script Results and
Completion Data” on page 2‐13.
Fake ICC application errors, not explicitly generated by the ICC, can
Fake ICC Application be generated by NDC Business Services in the following
Errors 5
circumstances.
Track 2 Equivalent data(Tag 0x57) is not available for PIN Block
Generation ‐ A ‘Part of returned data may be corrupted’ fake
error is generated with CLA = 0xFF, INS = 0xFF, P1 = 0xFF, P2 =
0xFF, Lc = 0x00, Le = 0x00, SW1 = 0x62 and SW2 = 0x81.
Attempt to perform pre‐authorized processing (1st Generate
Application Cryptogram) results in an AAC (Transaction
Declined) from the ICC ‐ A fake ICC application level error is
generated with CLA = 0xFF, INS = 0xFF, P1 = 0xFF, P2 = 0xFF, Lc
= 0x00, Le = 0x00, SW1 = 0xFF and SW2 = 0xFF.
Attempt to perform post‐authorized processing (2nd Generate
Application Cryptogram command) when it is in the wrong
processing state. A fake ICC application level error generated
with CLA = 0xFF, INS = 0xFF, P1 = 0xFF, P2 = 0xFF, Lc = 0x00, Le
= 0x00, SW1 = 0xFF and SW2 = 0xFF.
A Generate Application Cryptogram command returns an
unexpected cryptogram (higher level than that requested). An
’Authentication Failed’ fake error is generated with CLA = 0xFF,
INS = 0xFF, P1 = 0xFF, P2 = 0xFF, Lc = 0x00, Le = 0x00, SW1 =
0x63 and SW2 = 0x00.
If at least one of the Issuer Script commands has failed, a fake
solicited ICC application level error is generated with CLA =
0xFF, INS = 0xFF, P1 = 0xFF, P2 = 0xFF, Lc = 0x00, Le = 0x00, SW1
= 0xFF and SW2 = 0xFF. Where the issuer script results are
included as detailed in “Issuer Script Results and Completion
Data” in Chapter 2, “SST to Host Messages”.
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 5-27
ICC Processing
ICC Application Journal Error Message - Activate Only
5-28 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
ICC Processing
ICC Application Journal Error Message - Activate Only
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 5-29
ICC Processing
ICC Processing Termination
5-30 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
ICC Processing
Authorisation Response Codes
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual 5-31
ICC Processing
Authorisation Response Codes
5-32 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Table of Contents
Related Documentation
Appendix A
Related Documentation
Overview A‐1
APTRA™ NDC Business Services EMV™ Integrated Circuit Card (ICC) Reference Manual
Table of Contents
Related Documentation
APTRA™ NDC Business Services EMV™ Integrated Circuit Card (ICC) Reference Manual
Related Documentation
A
Overview
Overview A
APTRA™ NDC Business Services EMV™ Integrated Circuit Card (ICC) Reference Manual A-1
Related Documentation
Other NDC Business Services Documentation
Table A-1
Other NDC Business Services
Documentation
APTRA NDC APTRA Activate NDC PDF Provides reference data used in NDC
Business Services Business Services, Reference Business Services to allow developers to
Manual customise the SST application and to write or
B006‐7073 modify the host control application.
.NET NDC .NET NDC Customiser Microsoft Context‐sensitive help and reference for the
Customiser HTML .NET NDC Customiser.
Help
(CHM)
NDC Business .NET NDC Business Services Microsoft Context‐sensitive help and reference for the
Services On‐line Documentation HTML Edge NDC Business Services.
APTRAbs20.chm Help
(CHM)
APTRA NDC APTRA NDC Business PDF/Paper Provides information on requirements and
Business Services Services, Systems Analysis information gathering for anyone who
Guide wishes to customise NDC Business Services
B006‐6380 for specific customers.
APTRA Activate .NET NDC Business Services Microsoft Context‐sensitive help and reference for
NDC Business On‐line Documentation HTML APTRA Activate NDC Business Services
Services APTRArc108.chm Help
(CHM)
.NET NDC .Net NDC Customiser Microsoft Context‐sensitive help and reference for the
Customiser HTML .NET NDC Customiser
Help
(CHM)
A-2 APTRA™ NDC Business Services EMV™ Integrated Circuit Card (ICC) Reference Manual
Related Documentation
Other NCR Documentation
Table A-2
Other NCR Documentation
Aggregate or
Title Format Description
Component
.NET EMV .NET EMV Card Services Microsoft Provides core EMV ICC processing functionality
Card On‐line Documentation HTML
Services APTRArc28.chm Help
(CHM)
APTRA™ NDC Business Services EMV™ Integrated Circuit Card (ICC) Reference Manual A-3
Related Documentation
Other NCR Documentation
A-4 APTRA™ NDC Business Services EMV™ Integrated Circuit Card (ICC) Reference Manual
Table of Contents
Processing Restrictions
Appendix B
Processing Restrictions
Overview B‐1
Restrictions B‐2
BER‐TLV Field Size B‐2
Candidate List Size B‐2
Static Candidate List B‐2
Number of Application IDs in Download B‐3
Reading/Writing Magnetic Stripes B‐3
Smart Card Reader/Writer (SCRW) B‐3
Smart Dip Card Readers B‐3
Communications Protocols B‐3
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Table of Contents
Processing Restrictions
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Processing Restrictions
B
Overview
Overview B
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual B-1
Processing Restrictions
Restrictions
Restrictions B
B-2 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Processing Restrictions
Restrictions
Note: Each of these terminal AID values may have more than one
corresponding ICC AID value during processing. This is because
the terminal AID value may be a partial AID value.
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual B-3
Processing Restrictions
Restrictions
B-4 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Glossary
Glossary 0
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual Glossary-1
Glossary
Glossary-2 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Glossary
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual Glossary-3
Glossary
SCIF Smart Card Interface. The interface board fitted to the MCRW
S to enable interaction with the SCRW.
SCRW Smart Card Reader Writer. The device fitted to the MCRW
providing an extension that can interact with an ICC.
Smart card General term for a card containing an Integrated Circuit
(IC). See IC and ICC.
SST Self Service Terminal. The terminal which the consumer uses
for self‐service. Also known as ‘the terminal’.
SW1 Status Word 1. The first part of the response status from an
ICC command.
SW2 Status Word 2. The second part of the response status from an
ICC command.
Glossary-4 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Glossary
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual Glossary-5
Glossary
Glossary-6 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Index
Index 0
Application IDs
A Number of B‐3
Table 3‐14
Application, ICC
Name display 5‐23
Application, Terminal
Version Number 5‐12
Authorisation Response Codes 5‐31
Commands
C Customisation data 3‐2
Communications protocols B‐3
Completion data 2‐13
Compliance
Acceptable non‐compliance 1‐3
Implementation 1‐3
Standards 1‐3
Customisation data
Commands 3‐2
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual Index-1
Index
Overview
O related documentation A‐1
Index-2 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
Index
Script, Issuer
S Processing 5‐2
Results 2‐13
Smart Card Reader/Writer (SCRW) B‐3
Hardware error reporting 2‐10
Solicited status messages 2‐9
Standards compliance 1‐3
State types
Begin ICC Initialisation 2‐4
Status messages
Solicited 2‐9
Supervisor keys (unsolicited message) 2‐10
APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual Index-3
Index
Index-4 APTRA™ NDC Business Services, EMV™ Integrated Circuit Card (ICC) Reference Manual
User Feedback Form
NCR welcomes your feedback on this publication. Your comments can be of great value in helping us improve
our information products.
Cut
You may send your comments to us electronically. See over for details.
Circle the numbers below that best represent your opinion of this publication.
Cut
Fold
If we may contact you concerning your comments, please fill in the information below:
Name:
Organisation:
Company:
Address:
Phone: Fax:
Thank you for your evaluation of this publication. Fold the form where indicated, tape (please do not staple),
and drop in the mail.
F 8763‐0695
Fold
Affix
Postage
Stamp
Here