3 - Operation
iDynamo 6| Secure Card Reader Authenticator | Installation and Operation Manual
Page 33 of 41 (
D998200321-20
)
3.5
Card Reading
If the solution design includes accepting contactless payments while iDynamo 6 is powered
by a handheld host (that is, not powered through the USB-C receptacle from a high-
powered USB-C power source), the device must have the battery pack installed. iDynamo
6 only uses the battery pack to power its on-board contactless reader, and receives all
other operating power from the connected host.
3.5.1
About Reading Cards
The steps for starting a transaction and reading a card or contactless payment device are different
depending on iDynamo 6’s configuration and on the design of the host software. Host software
for implementation references. The
solution developer should provide solution-specific instructions for operators to follow. A transaction
generally follows this essential flow:
1)
If the device will be used to accept contactless transactions while handheld, the operator makes sure
the battery pack is installed and charged.
2)
The operator makes sure iDynamo 6 is configured properly and is connected to the host (see section
3)
The operator uses the host user interface to finalize a transaction amount, then initiates a transaction.
4)
The host communicates with the device, and reports to the operator when the device is ready.
5)
The operator makes sure iDynamo 6 is receiving power from the host and has powered itself on.
When the device is powered via the USB-C receptacle (only possible on models without a host plug),
the host may always keep a connection open to the device. When the device is not powered via the
USB-C receptacle, the host generally opens a session with the device to process a transaction, then
closes the session after the transaction is complete to power off the device and conserve power.
6)
The operator guides the cardholder in presenting payment.
7)
The cardholder interacts with the device to present payment. The following sections provide
additional details about presenting each of the available payment methods.
8)
Because the device does not have its own display, the device may send messages to the host
prompting the cardholder to perform certain actions; the host software should process these requests
by displaying the requested messages, and depending on the placement of the host display(s), the
operator may need to relay the messages to the cardholder. For example:
a)
If the device can not read the card, it may prompt the cardholder to swipe, insert, or tap again.
b)
If the device repeatedly can not read a chip card, it may prompt the cardholder to use the
magnetic stripe reader instead of the chip card slot. This is known as
EMV fallback
.
9)
The device reports the success or failure of the transaction to the host, which should report the results
to the operator.
