EMV Contactless on APTRA™ ANDC 04.04.

00
Requirements Guide
10th March, 2015
Version 1.0

This document and information herein is the property of NCR Corporation and all unauthorised use and reproduction is
prohibited. Copyright © 2016 NCR Corporation, Duluth, Georgia, USA. All rights reserved.
Confidential, unpublished property of NCR Corporation.
 EMV Contactless on APTRA™ ANDC 04.04.00 – v 1 0

1. Enhanced State Flow

The A, T and z008 card read states all have new extension states to have different next state numbers,
read conditions and error screens for the contact and contactless card readers. So you can now have a
totally separate state flow for contactless if you wish and it means you can use the Set OpCode Buffer
state to set a character to represent contactless.
The recommended way to implement contactless EMV smart cards is to accept a “tap” at the card read
state. The card read state will be the normal A or T, depending on whether you’re using a motorised or
DIP reader for the contact cards.
When the contactless device detects a card tap it will communicate with the card, get the track
information from the smart card and populate the mag stripe buffers in Advance NDC.
The software will ask the card to provide a cryptogram right there in the card read state. If you’re used to
EMV contact processing you would expect that not to happen until the end of the transaction when we
know all of the details about the type of transaction, the amount and the currency. But with contactless
we only get a very brief time where the card and the terminal can communicate, so it all has to happen up
front. Some card schemes ask us to tell the chip it is a zero amount cash withdrawal at an ATM, others
have special codes for us to use for ATM contactless transactions.
When we send the data on the Transaction Request, the issuer will know that it was a contactless
transaction on an ATM either by looking at the CAM Flags field, or by populating the OpCode with host
specific values. The host will use the traditional amount buffer to decide whether to approve the
transaction, rather than any EMV tags.

Version 1.0 Page 2 of 9 10/03/2016

© NCR Corporation 2016 All rights reserved. Confidential, unpublished property of NCR Corporation.
 EMV Contactless on APTRA™ ANDC 04.04.00 – v 1 0

1.1. Mid Flow Tap

Just before Transaction Request you can use the z008 Insert Card state, which is a way of doing card
read in the middle of a transaction. You ask the cardholder to insert or tap their card.
When a tap is detected it will talk to the card, this time it will use the real amount value, and it will get a
certificate that can be sent to the issuer.
It's going to use the real value from the Amount Buffer, so you have to make sure that it contains minor
currency units. So 1 0 0 is 1 dollar or 1 pound. If the transaction is for one hundred dollars or pounds,
then the Amount Buffer must contain 1 0 0 0 0.
The Amount Entry states will add zeroes for you automatically, if you configure the AppendBuffer.xml to
do so.
You also need to tell the chip how many decimal places the currency has. So you need to define EMV
tag 5F36, Currency Exponent, inside your ContactlessEnabler.xml file. So for dollars, pounds and euros
for example, 5F36 needs to be defined as 02. For dinar it will need to be 03 and for Yen 00.

Version 1.0 Page 3 of 9 10/03/2016

© NCR Corporation 2016 All rights reserved. Confidential, unpublished property of NCR Corporation.
 EMV Contactless on APTRA™ ANDC 04.04.00 – v 1 0

2. Card Read Extension State

All 3 of the card read states, A, Z and z008 have very similar extension states for contactless cards. The
Reference Guide has full details.
There is a Secondary Card Reader Good Read Next State Number so that we can branch to a different
state flow for a contactless tap.
There is an Active Card Readers entry that allows the host to control which card readers are enabled.
For example, if you’re going to implement Mid-Flow Tap, you would only have the primary card reader
available at the A state.
There are Read Conditions for the secondary card reader. You would never use 008 as one of these read
conditions because with a contactless tap, it is always the data in the magnetic stripe buffers that will be
searched against the FIT. Read Condition 008 is only for contact cards when the physical mag stripe is
damaged or empty.
Finally, there is a Contactless Tap Error screen which can contain dynamic text showing the cause of the
error.

Version 1.0 Page 4 of 9 10/03/2016

© NCR Corporation 2016 All rights reserved. Confidential, unpublished property of NCR Corporation.
 EMV Contactless on APTRA™ ANDC 04.04.00 – v 1 0

3. Automatic Language Selection

If you are initiating the transaction with a tap, then you can use the Automatic Language Selection state
from the EMV/CAM2 Exits product to automatically set the Language Offset value if the cardholder’s
language preference is stored on the card.

Version 1.0 Page 5 of 9 10/03/2016

© NCR Corporation 2016 All rights reserved. Confidential, unpublished property of NCR Corporation.
 EMV Contactless on APTRA™ ANDC 04.04.00 – v 1 0

4. EMV Data Objects

ContactlessEnabler.xml file must be edited to provide customer and transaction specific EMV data
objects.
EMV objects such as Terminal Country Code (tag 9F1A), Merchant Name and Location (tag 9F4E),
Interface Device (IFD) Serial Number (tag 9F1E), Terminal Capabilities (tag 9F33) and so on.
Transaction related objects such as Transaction Type (tag 9C), Transaction Currency Code (tag 5F2A)
and Transaction Currency Exponent (tag 5F36).
And then there are card scheme specific tags such as VISA’s Terminal Transaction Qualifiers (tag 9F66),
MasterCard’s Transaction Category Code (tag 9F53) and American Express’s ExpressPay Terminal
Capabilities (tag DF51).
In the EMV/CAM2 solution these would have all been downloaded from the host, but in the contactless
solution they are added to the ContactlessEnabler.xml file.

Version 1.0 Page 6 of 9 10/03/2016

© NCR Corporation 2016 All rights reserved. Confidential, unpublished property of NCR Corporation.
 EMV Contactless on APTRA™ ANDC 04.04.00 – v 1 0

5. Messaging
5.1. Send Configuration Information

Most hosts will use the Send Configuration Information terminal command with a command code of ‘7’
and a command modifier of ‘1’. The response is a Solicited Status Message that contains all the
available information relating to the hardware configuration of the SST.
The bit we’re interested in is field g4 which is a list of all Device Identifier Graphics (DIGs) followed by the
type of device fitted. A DIG of D is the primary card reader and y is the secondary. A value of 48 is the
EMV Contactless Card Reader, 47 for the older magnetic stripe data only contactless reader.

Version 1.0 Page 7 of 9 10/03/2016

© NCR Corporation 2016 All rights reserved. Confidential, unpublished property of NCR Corporation.
 EMV Contactless on APTRA™ ANDC 04.04.00 – v 1 0

5.2. Transaction Request Message

The most important thing for the Host to remember is that the EMV data for Amount will not be accurate
for tap initiated transactions and must use the traditional NDC Amount Buffer before the 5CAM separator.
All of the card and EMV interaction is at the Card Read state. The host will then use the on-line PIN and
the traditional Amount Buffer (rather than an EMV tag) to approve the transaction.

Version 1.0 Page 8 of 9 10/03/2016

© NCR Corporation 2016 All rights reserved. Confidential, unpublished property of NCR Corporation.
 EMV Contactless on APTRA™ ANDC 04.04.00 – v 1 0

5.3. CAM Flags

The first 2 bytes after the “5CAM” string are the CAM Flags. Only the least significant 3 bits of byte 2 will
be set in a contactless transaction.
The least significant bit of byte 2 will be 0 if a contact card is being used and 1 for a contactless card.
The next bit will be 0 if the contactless card is a magnetic stripe emulation card and 1 if it is an EMV
contactless card.
Bit 3 will be a 1 to indicate smart card processing was initiated.

Version 1.0 Page 9 of 9 10/03/2016

© NCR Corporation 2016 All rights reserved. Confidential, unpublished property of NCR Corporation.