3 - Command Set
DynaPro Mini| PIN Encryption Device | Programmer’s Manual (Commands)
Page 73 of 128 (
D99875629-43
)
3.6.3.1
Standard EMV Transaction
The sequence for calling the command is as follows:
1)
As a cautionary measure, the host may send the device
the device does not have a previous unfinished transaction lingering, which would block initiation of
a new transaction.
2)
The host finalizes the amount for the transaction.
3)
Command 0xA2 - Start EMV Transaction
4)
The device prompts the cardholder to present payment by displaying pre-defined EMV messages:
a)
DynaPro Mini cycles between showing
(AMOUNT)
,
(AMOUNT) OK?
and
CANCEL OR
ENTER
, and waits for the cardholder to select
Enter
or
Cancel
.
5)
If the cardholder confirms the amount or makes a payment type selection, then depending on the card
type the host specified in the command, the device arms the MSR and/or ICC slot, turns on the LED
near the slot (if any), and displays either
SWIPE
or
INSERT CARD
. If the cardholder presses the
Cancel
button or the transaction times out, the device performs
6)
If the cardholder swipes a magnetic stripe card, the device meets EMV 4.x requirements by checking
the service code from the magnetic stripe data to see if it begins with a 2 or a 6 to determine if the
card also includes a chip, and advises the cardholder that EMV is preferred by displaying
USE CHIP
READER
(similar to the screenshots for
Command 0x07 - Display Message
). If the chip fails or the
service code does not begin with a 2 or a 6, the device prompts the cardholder for an MSR swipe.
After a successful swipe, the device prompts the cardholder to select
Debit
or
Credit
. If this is a
debit account type, the device requests a PIN.
7)
If the cardholder inserts a contact chip card, depending on the device’s payment brand account type
setting for ICC the Acquirer has set in tag DFDF73 [see
Appendix D MagTek Custom EMV Tags
] the device does one of the following:
a)
Assume Credit, Debit, or Default.
b)
Prompt the cardholder to select
Credit
,
Default
, or
Debit
.
8)
If the cardholder has inserted a contact chip card, the device shows ICC applications that are mutually
supported by both the card and the device, and asks the cardholder to choose the preferred ICC
application. If there is no mutually supported application, the device may show
CARD BLOCKED
.
If a PIN entry is needed per
EMV 4.x
requirements, the device shows
ENTER PIN
and starts the PIN
entry timer (similar to the screenshots for
Command 0x04 - Request PIN Entry
). If the cardholder
cancels the transaction or the transaction times out, the device performs
. When the device is configured to allow PIN bypass using tag DFDF68, the PIN
requirement can be bypassed by the merchant by setting bit 0, byte 6 of the 0xA2 command. The
TVR bits will be set appropriately per EMV 4.x requirements. The PIN requirement can also be
bypassed by the cardholder.
9)
After PIN entry, the device displays either
PIN OK
or cycles through
INCORRECT PIN
and
TRY
AGAIN
up to the PIN retry limit (similar to the screenshots in
). If the number of attempts reaches PIN try limit-1, the device displays
Last PIN Try
briefly
before returning to
TRY AGAIN
. If the cardholder exceeds the PIN entry retry limit, the device
performs
, otherwise the transaction proceeds to the approval stage.
10)
The device determines the appropriate transaction approval method per
EMV 4.x
requirements. A
transaction can be forced online by the merchant by setting the
Options
in the invocation of
Command 0xA2 to
Force Online
.
a)
For offline transactions, the device gets the TC or AAC from the chip for later transmission to the
host. Depending on the transaction outcome, the device shows
APPROVED
,
DECLINED
, or
