Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
This section contains information on DynaFlex II Go's LEDs, beeper, and BCR status LED. It is important to note that DynaFlex II Go devices are equipped with an optional rechargeable battery. If there is no power supply to the device through the USB cable or optional internal rechargeable battery, all LEDs, along with the BCR status LED, will not illuminate. When this occurs, the user interface will resemble the device as shown in Figure 7-1.
As mentioned in section 1.1 Key Features and Components, DynaFlex II Go models equipped with a barcode reader (BCR) have a similar physical appearance as models without a BCR, as shown in Figure 7-1. BCR models are equipped with a camera and a QR code located on the front side of the device.
DynaFlex II Go devices have a user interface composed of three elements: a visual indicator consisting of four LEDs, a beeper that produces audible alerts, and a power button see Figure 6-1 - Power Button.
DynaFlex II Go BCR devices have a user interface composed of four elements: a visual indicator consisting of four LEDs, a barcode reader status LED, a beeper that produces audible alerts, and a power button see Figure 6-1 - Power Button.
DynaFlex II Go devices do not feature input components such as touch screens.
Figure – DynaFlex II Go and DynaFlex II Go BCR
When DynaFlex II Go is connected via USB in an idle state, it can be detected by a host through the USB HID port see Figure 7-6. After the host has connected to DynaFlex II Go, LED 1 will stay on. The device is in Ready State.
Figure - LED Status (Idle State) Before Host Detection and LED Status (USB Ready State) After Connecting to Host
DynaFlex II Go will power on immediately when connected to USB power. A brief beep will sound, and all four LEDs will turn on for half a second, as shown in the Figure below. Following this, LED 1 and LED 2 will remain illuminated, while LED 3 and LED 4 will remain unlit.
Figure – LED Power on Sequence – USB Power On
DynaFlex II Go provides four LEDs (see section 7.1 Component Details), numbered LED1 through LED4, which report the device’s current operating status.
The meaning of each LED depends on the device’s operating mode, see section 6 Operation. Most of the time, operators will check the device’s status using the LEDs when it is in Active Mode while the device is not performing a transaction.
LED blinking patterns have specific meanings as described in Table 7-. A blinking LED generally means the device is actively doing something to change the state that the LED is indicating, and solid indicates a persistent state that would require an operator or cardholder to take action to change. One major exception is a device-wide functional failure state, such as a tamper state, where all LEDs flash urgently to call the attention of an advanced operator to intervene.
In This Context
LED1
LED2
LED3
LED4
Active Mode, not armed for a tap transaction
Power
Connection
Reserved
Color
Means
Solid
Solid LEDs generally require an operator or cardholder to take action to change the state the LED is reporting.
Example: Host is connected. Cardholder or host would have to disconnect. Example: Host is disconnected. Host would have to initiate connection.
Blinking
Blinking LEDs generally indicate the device is in the process of doing / attempting something. Blink duty cycle and blink period are generally selected to show urgency or ongoing progress through a series of steps. Example: Device is attempting to pair with the host via Bluetooth® Low Energy (LE).
Short time
LEDs sometimes light for a short time to indicate some process has ended (success or failure) and the device is going to transition to another state soon. Example: Successful card read.
Card Read Result
Active Mode, armed for a tap transaction
Armed for Tap
Tap Read Progress
Tap Read Progress
Card Read Result
Device-wide failure
During major failures (such as tamper), LED1-LED4 report the nature of the failure based on the most likely steps required to resolve it.
During major failures (such as tamper), LED1-LED4 report the nature of the failure based on the most likely steps required to resolve it.
During major failures (such as tamper), LED1-LED4 report the nature of the failure based on the most likely steps required to resolve it.
During major failures (such as tamper), LED1-LED4 report the nature of the failure based on the most likely steps required to resolve it.
When the operator presses the Start button on the host device, LED 1,2, and the BCR status light will be illuminated see the Figure below. When a barcode is detected, only LED 1 will remain illuminated, the BCR status LED will be off, and a long beep will sound see the next Figure.
Figure – BCR Transaction USB Ready State
Figure – BCR Transaction Barcode Detected (Connected via USB)
When the operator presses the Start transaction button on the host device, LED 1 and 2 will remain on. When a card is swiped, LEDs 1,2 and 4 will turn on in sequence (1,2 then 4), followed by a long beep, indicating a successful transaction, see the Figure below. After a successful transaction, the device will return to the ready state, see the next Figure.
Figure – LED Sequence – Payment Transaction Successful MSR Swipe (Connected via USB)
Figure – Return to Ready State After Successful Transaction
When the operator presses the Start transaction button on the host device, LED 1 and 2 will remain on. When a card is inserted, LEDs 1, 2 and 4 will turn on in sequence, followed by a long beep, indicating a successful transaction, see Figure 7-20 – LED Sequence – Payment Transaction Successful EMV Contact (Connected via USB). LED 4 will remain on, and the device will sound a double beep until the card is removed from the slot. After a successful transaction, the device will return to the ready state, see Figure 7-19.
Figure – LED Sequence – Payment Transaction Successful EMV Contact (Connected via USB)
When the operator presses the Start transaction button on the host device, LED 1 will remain on. When a card is presented within range of the contactless reader, LEDs 1,2,3, and 4 will turn on in sequence, followed by a long beep, indicating a successful transaction, see Figure 7-21 - LED Sequence – Payment Transaction Successful EMV Contactless (Connected via USB). After a successful transaction, the device will return to the ready state, see Figure 7-19.
Figure - LED Sequence – Payment Transaction Successful EMV Contactless (Connected via USB)
When the operator presses the button on the host device, LED 1,2, and the BCR status light will be illuminated see Figure 7-22. When a barcode is detected, only LED 1 will remain illuminated, the BCR status LED will be off, and a long beep will sound see Figure 7-23.
Figure 7-22 – BCR Transaction Bluetooth® LE Ready State
Figure – BCR Transaction Barcode Detected (Connected via Bluetooth® LE)
When the operator presses the transaction button on the host device, LED 1 and 2 will remain on. When a card is swiped, LEDs 1,2 and 4 will turn on in sequence (1,2, then 4), followed by a long beep, indicating a successful transaction, see Figure 7-24. After a successful transaction, the device will return to the ready state, see Figure 7-25.
Figure – LED Sequence – Payment Transaction Successful MSR Swipe (Connected via Bluetooth® LE)
Figure – Return to Ready State After Successful Transaction (Bluetooth® LE Ready State)
When the operator presses the transaction button on the host device, LED 1 and 2 will remain on. When a card is inserted, LEDs 1,2 and 4 will turn on in sequence, followed by a long beep, indicating a successful transaction, see Figure 7-26 - LED Sequence – Payment Transaction Successful EMV Contact (Connected via Bluetooth® LE). LED 4 will remain on and the device will sound a double beep until the card is removed from the slot. After a successful transaction, the device will return to the ready state, see Figure 7-25.
Figure - LED Sequence – Payment Transaction Successful EMV Contact (Connected via Bluetooth® LE)
When the operator presses the Start transaction button on the host device, LED 1 will remain on from ready state. When a card is presented within range of the contactless reader, LEDs 1,2,3, and 4 will turn on in sequence, followed by a long beep, indicating a successful transaction, see Figure 7-27. After a successful transaction, the device will return to the ready state, see Figure 7-25.
Figure - LED Sequence – Payment Transaction Successful EMV Contactless (Connected via Bluetooth® LE)
LED 2 is designated for indicating Bluetooth® connection status, not USB connection status.
When LED 2 is off, it indicates that the device is not currently connected via Bluetooth®. In most cases, this implies that the device has a Bluetooth® signal that is not connected, unless this has been intentionally disabled through configuration.
When LED 2 is on, it indicates that the device is currently connected via Bluetooth®. LED 3 is designated for indicating readiness for Bluetooth® message exchange.
When LED 3 is off, it indicates that the Bluetooth® connection is not yet ready. This could be due to the absence of a secure connection or the non-activation of device-to-host characteristic notifications.
When LED 3 is on, it indicates that the Bluetooth® connection is ready, signaling the establishment of a secure connection and the activation of device-to-host characteristic notifications.
Press and hold the Power Button for two seconds: initially, LED 4 will light up, followed by all four LEDs illuminating for one second. This is followed by LEDs 1 and 2 remaining lit for 2 seconds, after which only LED 1 will be active.
Figure - Power On in Battery Operating Mode
Figure - LED Behavior for Bluetooth® Low Energy (LE) Ready State
If the host is within the Bluetooth® Low Energy (LE) connection range, all three LEDs (LED 1, 2, 3) will be illuminated, as described in Figure 7-8 - LED Behavior for Bluetooth® Low Energy (LE) Ready State.
DynaFlex II Go is capable of being powered off while in Battery Operating Mode only. To initiate the power-off sequence, press and hold the Power Button for two beeps then release. It's important to note that DynaFlex II Go cannot be powered off while connected via USB. If a two-beep sequence is initiated while connected to USB the device will reboot.
Figure - Power Off Device in Battery Operating Mode
DynaFlex II Go must first be paired with the host device before a secure Bluetooth® connection can be established. Follow the steps below to activate Bluetooth® pairing mode:
Press and Hold the Power Button for 4 beeps
Release the Power Button
LED 1 will remain steadily illuminated while LED 4 will begin to blink. When LED 4 is blinking it indicates the device is waiting to pair with the host. It will continue to blink for 3 minutes, waiting to pair with the host.
Figure - Activate BLE Pairing Mode
When the host is pairing with DynaFlex II GO, LED 4 will remain off and LED 2 will power on, indicating the pair is processing.
Figure - Bluetooth® LE Pair Processing
The device will return to Power On status if pairing Succeeds or Fails. LED 2 will power off and LED 1 will remain powered on.
Figure - Pairing Successful/Failed
When the device establishes a connection to the host via BLE and is prepared for secure communication, all three LEDs (LED 1, 2, 3) will illuminate steadily.
Figure - BLE Connected to Host
When the device is disconnected from the host Bluetooth® Low Energy (LE) connection, LED 3 will power off first and after 4 seconds, LED 2 will power off, LED 1 will remain powered on as the device returns to Ready State.
Figure 7-14 - Bluetooth® LE Disconnect LED Sequence
When in Bluetooth® LE Sleep Mode, DynaFlex II Go will conserve battery life by limiting power to non-essential hardware features and entering low power mode. When in Sleep Mode, the device will appear to be powered off, with no LEDs illuminated, see Figure 7-15 – Bluetooth® (LE) Sleep Mode. For information on how to disable this feature, see D998200597 DynaFlex II Go Programmer’s Manual (COMMANDS).
Figure – Bluetooth® (LE) Sleep Mode
The steps for starting a transaction and reading a contactless payment device are different depending on the device’s configuration and on the design of the host software. Host software developers should see section 9 Developing Custom Software for implementation references. The solution developer should provide solution-specific instructions for operators to follow. A transaction generally follows this essential flow:
An advanced operator has already made sure DynaFlex II Go is configured properly and is connected to the host (see section 4.3 Connecting DynaFlex II Go to a Host). When the device is connected to the host and powered via the USB-C connector or internal rechargeable battery, the host software may keep a connection open to the device.
The operator makes sure DynaFlex II Go is receiving power either from the USB connection, or from the internal rechargeable battery, and is awake and powered on (see section 7.8.3)
The operator uses the host software’s user interface (for example, a point of sale) to finalize a transaction amount, then initiates a transaction. In solutions that are designed to respond to cardholder input events that occur when the device is idle, such as unprompted tapping of a card or electronic payment device, the host software may respond to those inputs by notifying the host. The host software may trigger other operations without being initiated by an operator (for example, the host software may immediately start a transaction, or alert the cardholder or operator to take action).
The host communicates with the device, and reports to the operator when the device is ready.
The operator guides and assists the cardholder in presenting payment.
The cardholder interacts with the device to present payment. The following sections provide additional details about presenting each of the available payment methods.
The host monitors the progress of the transaction, and when necessary, and should report issues to the operator, who may need to relay the messages to the cardholder.
The device reports the success or failure of the transaction to the cardholder and to the host.
To tap a contactless card or smartphone, follow these steps:
Check LED status:
The device shows the transaction status using the LEDs. LED1 lights solid and all other LEDs are off, per EMV standards, to indicate it is ready for a tap.
All devices report detailed transaction status to the host, and host software may report that information to operators so they can guide cardholders through the transaction (for example, “please tap your card now”).
If the cardholder is using an electronic payment device, such as a smartphone, make sure the payment device has NFC turned On and has a payment app configured to process transactions. For details, see the documentation provided by the smartphone manufacturer and payment app publisher.
Briefly hold the card, smartphone, or other contactless payment device over the contactless landing zone, indicated by the EMVCo Contactless Indicator symbol on the device’s face (see Figure 7-28). Because each smartphone model may have its NFC antenna placed differently, the ideal tap position may vary by make and model. For example, Samsung users may need to center the phone on the contactless landing zone, while Apple users may need to tap the top of the phone on the contactless landing zone.
Wait for LED status:
The device quickly lights the second LED to show it is processing, then lights the third LED to show it has successfully read the tap, then lights the fourth LED to show the read is complete (see Figure 7-29) The device then returns to Ready State, when connected to USB ready state is LED 1 and 2 on only, ready state for BLE is LED 1,2, and 3 on.
The device beeps once.
If the device cannot communicate with the card, smartphone, or other contactless payment device:
The device ends the transaction.
The device lights LED 4 for a short time.
The device beeps twice.
The device notifies the host that the transaction failed. If this occurs, the host software may choose to retry the transaction or revert to prompting the operator to perform another operation that is specific to the solution design.
Figure - Tapping a Contactless Card / Smartphone
Figure – Contactless Read LED Sequence – Read Complete (Connected via Bluetooth® LE)
To scan a barcode, follow these steps:
Make sure you are using a DynaFlex II Go model that includes a barcode reader, indicated by QR Code markings on the face of the device surrounding the barcode reader lens (see section 1.1 Key Features and Components).
If the barcode being scanned is not on a self-illuminated source such as a smartphone, make sure there is enough ambient light for the camera to read the barcode. In low light conditions, the barcode reader will only be able to read self-illuminated sources.
In some solutions, the operator may have to perform an operation in the host software to enable the barcode reader, or to start a transaction with the barcode reader enabled.
Wait for the device, the host, or the operator to prompt for a barcode read:
The device lights the barcode reader indicator LED next to the barcode reader lens.
Hold the barcode in front of the barcode reader camera:
If possible, use the light from the barcode reader indicator LED to align the barcode within the barcode reader’s field of view, which extends 16 degrees above / below and 21 degrees to the left/right of a line perpendicular to the barcode reader lens.
Hold the barcode as close as 6 inches from the lens. For smaller barcodes, the device will read immediately. If it does not, gradually move away up to 14 inches from the lens until the device reports a successful read. Larger barcodes must be far enough away from the device that the whole barcode is within the camera’s field of view; if a large barcode is too close, the barcode reader can only see a zoomed in portion of the barcode.
Wait for the device or the host to report the barcode has been read successfully:
The device beeps once.
The device turns off the barcode reader indicator LED.
DynaFlex II Go products support Apple Value Added Services (Apple VAS) protocol.
Contactless transactions using the Apple VAS protocol permits the device reader to perform the following supported operations:
The device reads both Apple VAS data and EMV payment data from a tapped smartphone or reads EMV payment data from a tapped card. When device sends ARQC to the host to conclude the transaction, it includes EMV payment data in container FC and includes VAS data, if available, in container FE
The device reads only Apple VAS data from a tapped smartphone and does not read data from a tapped card. If the tapped smartphone does not support VAS, the device does not detect or read from the smartphone. When the device sends ARQC to conclude the transaction, it includes VAS data in container FE and does not include EMV payment data in container FC.
The device reads only Apple VAS data from a tapped smartphone or reads EMV payment data from a tapped card. When the device sends ARQC to conclude the transaction, it only includes either EMV payment data in container FC for cards, or includes VAS data in container for smartphones.
The device operates the same as EMV mode (01). It reads only EMV payment data from a tapped smartphone or a tapped card. When the device sends ARQC to conclude the transaction, it includes EMV payment data in container FC and does not include VAS data in container FE. Note: THIS MODE MAY NOT BE NEEDED.
For details, see D998200597 DynaFlex II Go Programmer’s Manual (COMMANDS).
1.1.1 How to Tap Contactless NFC Tags / MIFARE Classic / MIFARE DESFire /MIFARE Plus Cards and Send Pass-through Commands
DynaFlex II Go is compatible with near field communication (NFC) technology such as MIFARE Classic/MIFARE DESFire /MIFARE Plus contactless IC products (smart cards).
To tap an NFC Contactless IC product and send pass-through commands, follow these steps:
Check LED status:
Per EMV standards, the device indicates transaction status through its LED indicators, located on the front face of the device. When ready for a tap, LED 1 is steadily illuminated while all other LEDs remain unlit.
All devices communicate transaction details to the host. The host software will relay this information to operators, allowing them to direct cardholders during the transaction, such as prompting "please tap your card now".
Place the card over the device's designated contactless landing zone, marked by the EMVCo Contactless Indicator symbol on the front face of the device.
Wait for LED status:
Initially, LED 2 illuminates, signaling the device is processing. The device subsequently illuminates LED 3 and LED 4, indicating card detection. Notifications are then sent to identify the card type and UID.
The Host application can further interact with the NFC Tag using pass-through commands. For details, see D998200597 DynaFlex II Go Programmer’s Manual (COMMANDS).
The device notifies the host that the transaction has ended with the NFC Tag removed.
The arrangement of the four LED indicators on DynaFlex II Go devices is illustrated in Figure 7-2. The LEDs are designated 1 to 4 and are ordered from left to right on the device.
Figure - LED Ordering
When DynaFlex II Go is powered on, its LEDs will illuminate green, when it is powered off, the LEDs will remain unlit.
The figure below illustrates the On/Off status of the LEDs.
Figure - LED ON/OFF
DynaFlex II Go devices equipped with a bar code reader have a status LED that indicates whether the barcode feature is scanning.
BRC Status Light On BCR Status Light OFF
Figure - BCR Status LED
All DynaFlex II Go devices are equipped with a beeper that produces a short beep lasting for half a second and a long beep that lasts for one second.
With a sufficiently charged battery, the device will power on when the power button is pressed (see Figure 6-1 - Power Button). The device will also power on when connected to USB power. In USB mode the device will remain in full power mode to provide power to device. If a power-off sequence is initiated, the device will reboot and remain in full power mode.
DynaFlex II Go products have an optional rechargeable battery to supply their own power when they are not powered through the USB-C port. The battery must be periodically recharged by connecting the device to a USB port or stand-alone USB charger. The device requires a USB power supply that can provide at least 500mA @ 5V.
To charge the device, connect it to a USB-C charger or a USB host as described in section 4.3.1 How to Connect DynaFlex II Go to a Host Computer via USB-C. For best results, use the cable that is included with the device. When charging, make sure the device is receiving enough power from the USB connection (the battery level should increase even when the device is in use). A full recharge cycle for a completely drained battery depends on the charging method. From a host USB port at 500mA, full charge takes approximately 5 hours. From a dedicated wall charger, a full charge may take approximately 5 hours. After connecting the device to a power source, make sure the LEDs indicate the device is charging (see sec - How to Connect DynaFlex II Go to a Host Computer via USB-C)
For important information about the device’s power systems, optimal charging methods during regular use, optimal handling and storage, and other information about keeping the device’s power systems in the best possible condition, see section - Handling to Avoid Accidental Tamper and section About Power.
The device ends the transaction and reports the transaction status to the host.
Do not tilt the barcode more than 60 degrees from parallel to the device’s face.
If the pass-through command is the last successful command, the device will end the transaction, emitting a single beep signaling a successful transaction. The user then needs to remove the card.
If an error is detected, the device will end the transaction and emit two beeps to signal the error. The user then needs to remove the card.
To power on the device connect the device to USB power. To power off the device, disconnect the device from USB power. Press and hold the power button (see Figure 6-1 - Power Button) on the device (for two beeps), all LED indicators should power off and remain unlit. If all LEDs are off, the device is in Powered Off mode. It is important to note the device cannot be powered off when connected via USB.
DynaFlex II Go will automatically reset once every 24 hours if it is continuously powered on.
Per UL requirements, the device is designed to not recharge its internal battery when the external temperature is below 0°C or above 40°C.
Table - LED Behavior for Errors, Timeouts, and Canceled Transactions, contains LED behavior related to errors, timeouts, and canceled transactions. If the device is exhibiting LED behavior not previously mentioned, it may be contained in this section.
LED
BCR Indicator Light
LED 1,2 ON - BCR ON
> LED1,2 ON - BCR
OFF + Double Beeps
> Ready
DynaFlex II Go MSR Connected via USB
LED 1,2 ON
> LED1,2,3 OFF – LED
4 ON + Double beeps
LED1,2,3 OFF – LED4
ON + Double beeps
LED 1,2 ON
> LED1,2 ON + Double Beeps
> Ready
LED 1,2 ON
> LED1,2,3 OFF – LED
4 ON + Double beeps
LED 1,2,3 OFF – LED 4
ON + Double Beeps
LED 1 ON
> LED1 ON + Double Beeps
> Ready
DynaFlex II Go EMV Contact
Connected via Bluetooth® LE
LED 1,2 ON
> LED1,2,3 OFF – LED
4 ON + Double Beeps
LED 1,2,3 OFF – LED 4
ON + Double Beeps
LED 1,2 ON
> LED1,2 ON + Double Beeps
> Ready
DynaFlex II Go EMV Contactless
Connected via USB
LED 1 ON
> LED1,2,3 OFF – LED
4 ON + Double beeps
LED 1,2,3 OFF – LED4
ON + Double beeps
LED 1 ON
> LED1 ON + Double Beeps
> Ready
Device Model
Error LED Behavior
Timeout LED Behavior
Cancel LED Behavior
DynaFlex II Go BCR Connected via USB
LED 1,2 ON – BCR ON
> LED1,2 ON, BCR
OFF + Double Beeps
> Ready
LED1,2,3 OFF – LED 4
BCR ON + Double Beeps
LED 1,2 ON – BCR ON
> LED1,2 ON – BCR
OFF + Double Beeps
> Ready
DynaFlex II Go BCR
Connected via Bluetooth® LE
LED 1,2 ON – BCR ON
> LED1,2 ON, BCR
OFF + Double Beeps
> Ready
Device Model
Error LED Behavior
Timeout LED Behavior
Cancel LED Behavior
DynaFlex II Go MSR
Connected via Bluetooth® LE
LED 1,2 ON
> LED1,2,3 OFF – LED
4 ON + Double beeps
LED1,2,3 OFF – LED 4
ON + Double beeps
LED 1,2 ON
> LED1,2 ON + Double Beeps
> Ready
Device Model
Error LED Behavior
Timeout LED Behavior
Cancel LED Behavior
DynaFlex II Go EMV Contactless
Connected via Bluetooth® LE
LED 1 ON
> LED1,2,3 OFF – LED
4 ON + Double Beeps
LED 1,2,3 OFF – LED4
ON + Double Beeps
LED 1 ON
> LED1 ON + Double Beeps
> Ready
LED1,2,3 OFF – LED 4
BCR ON + Double Beeps
DynaFlex II Go EMV Contact
Connected via USB
