Magtek DynaFlex II Go Programmer's Manual page 94

6 - Commands
8) The device sends Notification 0x0101 - Transaction Information Update to report the payment
technology being used / Data Update / ARQC Update / Data Attached.
9) If the host specified Quick Chip Transaction Flow in the Transaction Flow parameter:
a) The device immediately constructs its own internal ARPC Response, with tag 8A set to 'Z3' to
coordinate the transaction with the card or other payment method, and sends the host Notification
0x0105 - Transaction Operation Complete to report the payment technology being used /
Kernel Outcome / Quick Chip Deferred /outcome detail. A Transaction Option parameter can
be set to display on amount or not.
b) (No Display only) The device sends the host Notification 0x1803 - User Interface Host Action
Request to report Display/Display Message/Data Attached with message
notify the cardholder the card can be removed.
c) The host should then process the ARQC Message data, including replacing the default amount
with the final transaction amount, and should coordinate with the transaction processor to retrieve
a final transaction result. Because in this case the device is not involved in determining the final
transaction result, it does not send a notification to the host to show
i) (No Display Only) Instead, the host should use its local display to show an appropriate
message to the cardholder, such as
transaction result.
10) If the host specified EMV Transaction Flow in the Transaction Flow parameter:
a) The host processes the ARQC Message data and uses it to coordinate with the transaction
processor to receive an ARPC Response, which it processes and sends to the device using
Command 0x1004 - Resume Transaction.
b) The device waits for the period of time specified in Property 1.1.1.1.1.5 ARPC Receive
Timeout. If an ARPC timeout occurs, the device sends the ARQC again based on the setting in
Property 1.1.1.1.1.6 ARPC Retry Attempts.
c) (EMV Contact Only) If the cardholder inserted a contact chip card, the device communicates with
the card to determine whether to approve or decline the transaction.
d) The device sends the host Notification 0x0105 - Transaction Operation Complete to report the
payment technology being used / Kernel Outcome / Approved or Declined /outcome.
e) (No Display Only) The device sends the host Notification 0x1803 - User Interface Host Action
Request to report Display/Display Message/Data Attached with message
to notify the cardholder of the transaction result.
DECLINED
11) The device sends Notification 0x0105 - Transaction Operation Complete to report the payment
technology used / Outcome / the final result of the transaction.
12) (MSR Only) If Property 1.2.1.1.1.1 Device-Driven Fallback Behavior (MSR Only) is configured
so the device does not perform fallback operations, and if the solution design requires payment brand
fallback logic, the host may use the contents of the notifications above to implement fallback flow
according to the following rules, which mimic the automatic fallback behaviors the device
implements during a single invocation of this command. The primary difference is that the host must
keep track of its own final Fallback Indicator instead of receiving it from the device in the EMV
ARQC Type:
a) If the transaction was successful and the notification indicates Payment Technology is EMV
Contact or EMV Contactless, there is no need to perform fallback-related operations.
b) If the transaction was successful and the notification indicates Payment Technology is Magnetic
Stripe Reader, the host should check the contents of the Card Type tag DFDF52 in the EMV
ARQC Type from the notification. Per payment brand fallback rules:
DynaFlex II Go| Secure Card Reader | Programmer's Manual (COMMANDS)
APPROVED
Page 94 of 301 (D998200597-102)
REMOVE CARD
APPROVED
or , based on the final
DECLINED
APPROVED
to
or .
DECLINED
or