Magtek DynaFlex II Go Programmer's Manual page 95

6 - Commands
i) If Card Type is NOT MSR Financial and Contact Chip Card (ICC), the host may
continue with the current transaction attempt using the magnetic stripe data. There is no need
to perform fallback-related operations.
ii) If Card Type is MSR Financial and Contact Chip Card (ICC), and the host has restarted
the same transaction because a previous attempt failed with the notification indicating MSR
Fallback, the chip card and the device communicated during the previous invocation of this
command, and determined they are not compatible. The host may continue the current
transaction using the magnetic stripe data.
iii) If Card Type is MSR Financial and Contact Chip Card (ICC) and the host has NOT
restarted the same transaction three times and failed with the notification indicating
Technical Fallback, the card has a chip the cardholder should use so the transaction will be
more secure. The host should guide the cardholder to use the chip card interface by sending
Command 0x1001 - Start Transaction and arm the device with the contact interface
enabled. The host may opt to also arm the contactless interface.
iv) If Card Type is MSR Financial and Contact Chip Card (ICC) and the host has restarted
the same transaction three times and failed with the notification indicating Technical
Fallback, the host may continue the current transaction using the magnetic stripe data.
c) If the transaction has failed and the notification indicates Payment Technology is None,
something went wrong at the very beginning of the transaction (for example, the host canceled),
and the host may simply end all attempts at performing the transaction, or it may opt to repeat the
original transaction with the same payment technologies enabled.
d) If the transaction has failed and the notification indicates Payment Technology is EMV Contact,
the host should examine the contents of the notification. Per payment brand fallback rules:
i) If the notification indicates MSR Fallback, the chip card and the device have communicated
and have determined they are not compatible. The host should guide the cardholder to use
the magnetic stripe interface by sending Command 0x1001 - Start Transaction and arm the
device with the Magnetic Stripe Reader interface enabled. The host may opt to also arm the
contactless interface.
ii) If the host has NOT restarted the same transaction three times and failed with the notification
indicating a Technical Fallback, the host should guide the cardholder to re-insert the chip
card by sending Command 0x1001 - Start Transaction and arm the device with the contact
interface enabled. The host may opt to also arm the contactless interface.
iii) If the host has restarted the same transaction three times and failed with the notification
reporting Technical Fallback, the host should guide the cardholder to use the magnetic stripe
reader by sending Command 0x1001 - Start Transaction and arm the device with the
Magnetic Stripe Reader interface enabled. The host may opt to also arm the contactless
interface.
13) (EMV Contactless Only)
For NFC Tag, the flow is as follows:
(1) Use Start Transaction command with the NFC enabled in Contactless Reader Mode
(2) If a NFC Tag is Detected
a. the terminal will send a notification that identifies the NFC card type, see Notification
0x0101 - Transaction Information Update
b. the terminal will send another notification with the UID as a payload, see Table 7.1-2 -
Notification Payload for Data Update, ARQC Update (Quick Chip), Data Attached
(3) No ARQC or BATCH data will be sent
(4) The host application can continue interfacing with the NFC tag by sending pass-through
commands
DynaFlex II Go| Secure Card Reader | Programmer's Manual (COMMANDS)
Page 95 of 301 (D998200597-102)