> For the complete documentation index, see [llms.txt](https://developer.magtek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.magtek.com/downloads-compliance-and-marketing-materials/device-manuals-product-specific/dynaflex-ii-ped-manuals/installation-and-operation-manual/operation.md). # Operation ## About Operating Modes While in use, the DynaFlex II family of products switch between distinct operating modes. It is crucial for operators to comprehend these modes to effectively operate the device: * Powered Off Mode is the shipping and storage mode of the device. Operators would not generally use this mode during a work shift or during off-shift recharging. It occurs when the operator holds the pushbutton for more than 8 seconds (or more than 12 seconds to force immediate power off without a proper shutdown sequence), or if the device’s battery is critically low and the device is not connected to a USB power source. In this mode, the device consumes practically no power. To move the device from Powered Off Mode to Active Mode, press the pushbutton for one second with the battery charged, or connect the device to USB power. If the device is already connected to USB power when it enters Powered Off Mode, it automatically powers back on. * Reset Mode is a transient mode where the device first transitions to Powered Off Mode, then automatically powers back on. It occurs when the operator presses the recessed switch, or the host sends the Reset Device command, or the device automatically performs a daily security reset. * USB Suspend Mode occurs when the USB host that is providing power to the device sends a USB Suspend control event to the device to conserve power. The device responds by powering off nearly all its modules including the display and listening for the USB host to send a USB Resume control event. To move the device from USB, Suspend Mode to Active Mode, the host software must open a USB connection to communicate with the device, which signals the operating system that the device is in active use and should be allowed to draw full power from the USB port. It is not necessary for the host software to send commands to the device at that time. * Active Mode is the device’s normal “awake” state when it is in use. In this mode, the touchscreen display and LEDs are powered on, and the device is ready to receive commands from the host. This mode can be divided into substates like Active/Host Not Connected, Active/Host Connected, Active/Host Communicating, Active/Armed for Read, Active/Reading, and so on. These substates differ in the amount of power they consume and are mostly under the control of the host software. To move the device from Active Mode to Powered Off mode, press and hold the pushbutton for 8 seconds. If the device does not respond, continue holding the pushbutton for longer than 12 seconds to force immediate power off without a proper shutdown sequence. To move the device from ActiveMode to Reset Mode, press the recessed switch. ## Operation Overview During normal operation, the operator initiates a transaction from the host, and the cardholder interacts with the device. Devices with a touchscreen display provide on-screen prompts and interactive features such as buttons and signature capture. Transaction types may include sales, refunds, voids, authorization, new accounts, teller window applications, checking, savings, mortgages, retail transactions, or any other type of transaction where there is interaction between the cardholder and the operator. For each transaction type, the host software can direct the device to prompt the cardholder for any combination of magnetic stripe swipe, EMV contact card insertion, and/or contactless payment tap, and the transaction flow on the device may differ depending on what the host software specifies and what the cardholder does. Section 4.8 Using the Reader provides examples of the cardholder experience for each type of payment. Figure 4-1 shows a typical point of sale (POS) transaction sequence. If the device cannot read payment data, the host software may direct it to prompt the cardholder to repeat the action or request the cardholder revert to a different form of payment (such as using the magnetic stripe reader as a fallback instead of the chip card insertion slot).

Figure 4-1 - Typical Transaction Sequence

## About the Status LEDs DynaFlex II provides four RGB LEDs directly below the chip card insertion slot (see section 1.5 About DynaFlex II Components), 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 4.1 About Operating Modes and Table 4-1 below. 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 colors have specific meanings, as described in Table 4-2. They are based on international conventions for traffic light colors, with additional colors reserved for unusual / special cases. * LED blinking patterns have specific meanings as well, as described in Table 4-3. A blinking LED 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 manual, specific combinations of LED colors and blinking patterns are described in more detail in the sections where they are relevant and use the same icons in the tables below to indicate color and blinking patterns. For example, information about how the LEDs show the device’s connection status is in section 3.2 Connecting to a Host. #### DynaFlex II LED Allocation
In This ContextLED1LED2LED3LED4
Active Mode: Not Armed for a Tap TransactionPowerConnectionReservedCard 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 steps required to resolve it.
#### DynaFlex II LED Colors
ColorMeans

Red

Stop or stopped

Example: LED1 is red. Stop using device: Battery is about to run out of charge.

Yellow

Wait or waiting

LED2 will show status for Access Point connection: Green connected, yellow waiting for connection.

Green

Go, going, or went.

LED3 will show status for WebSocket connection: Green connected, yellow Waiting for connection.

Other Colors

Reserved

#### DynaFlex II LED Patterns
ColorMeans
Solid

Solid LEDs 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 indicate the device is in the process of doing / attempting something. Blink duty cycle and blink period are selected to show urgency or ongoing progress through a series of steps.

Example: Device is attempting to connect to the WLAN access point.

Short time

LEDs sometimes illuminate for a short time to indicate a process has ended (success or failure) and the device is going to transition to another state soon.

Example: Successful card read.

## About the Touchscreen Display This section applies only to DynaFlex II PED models, which are equipped with a display and touchscreen. When using a DynaFlex II model that does not have a display, the device reports ongoing status to the host, which must present any necessary prompts and status information to the operator and / or the cardholder. ### **Welcome Page / Active Idle Page** When the device is powered on, in Active mode, and idle (not performing a transaction or displaying host-driven user interface prompts), it displays Welcome or a custom graphic if it is configured to do so. If the host software is designed to receive and respond to cardholder input messages, pressing any area on the touchscreen when it is idle may trigger the host to perform an operation, such as starting a transaction. For more information about custom graphics, see **DynaFlex and DynaFlex Pro Programmer’s Manual (COMMANDS).** WLAN enabled devices also report current status in a set of icons at the top of the Welcome screen. Table 4-4 below shows the icons and describes their meanings. For example, in Figure 4-2, the device is connected to a USB host and wireless access point, TLS is enabled, the battery level is OK, the device is charging, and it is idle, waiting for the host to initiate a transaction. #### Status Icon Meaning
Status IconMeaning
Device’s Active Connection is set to USB, and the device has successfully established a USB communication connection with the host.
WLAN is not configured
Blinking to show device is connecting to a wireless access point
WebSocket is active or connected
WebSocket is inactive or disconnected
Device’s Active Connection is set to 802.11 wireless, and the device is connected to a wireless access point. The number of bars indicates the strength of the signal the device is receiving from the wireless access point (commonly known as RSSI).
and TLS security on the 802.11 wireless connection is Disabled (red open padlock) TLS security on the 802.11 wireless connection is Enabled (black closed padlock)
Battery is fully charged.
Battery is OK, between 20% and 95% charged.
Battery is low, between 10% and 20% charged.
Battery is critically low, between 3% and 10% charged.
Battery is empty, below 3% charged.
Battery is charging.

Figure 4-2 - Welcome Page Examples

The device may show text other than “Welcome” when it is Active / idle under certain conditions: * **OFFLINE/Tampered**: indicates the device has detected an attempt to tamper with it (for example, physical tampering, out-of-spec temperature range, electrical attack). If this occurs, remove the device from service and set it aside in a secure location for possible forensic analysis, and contact the manufacturer or your reseller for support. This mode can only be reset in the manufacturing facility. * **OFFLINE/Tamper not active:** indicates the device’s tamper detection system is not activated. The device is not configured properly. If this occurs, remove the device from service and contact the manufacturer or your reseller for support. * **OFFLINE/Security not activated:** indicates the device’s data security features have not been activated. The device is not configured properly. If this occurs, remove the device from service and contact the manufacturer or your reseller for support. * **OFFLINE/Security activated:** indicates the device is ready to have keys injected. If this occurs, remove the device from service and contact the manufacturer or your reseller for support. * **OFFLINE/HW missing: i**ndicates the device cannot detect one or more of its installed modules. This may indicate a mechanical or electrical failure. If this occurs, remove the device from service and contact the manufacturer or your reseller for support. * **OFFLINE/Keys missing:** indicates the device is missing one of the encryption keys that are critical to its data security systems. The device needs to have keys properly injected. If this occurs, remove the device from service and contact the manufacturer or your reseller for support. * **OFFLINE:** without any clarifying text indicates the device is not ready for normal operation. ## **Device Information Page** While powering on, the touchscreen briefly displays a page of information about the device, including the installed firmware part numbers and versions and other identifying information. To determine a device’s PCI certification status, compare the contents of this screen to the device’s listing on [**www.pcisecuritystandards.org**,](http://www.pcisecuritystandards.org/) *Approved PTS Devices*. Note that in PCI listings, lowercase “x” is a wildcard meaning ‘any single character.

Figure 4-3 - Device Information Screen

To view details pertinent to the device’s PCI certification status on WLAN enabled devices - including the installed firmware part numbers and versions as well as other identifying information (see Figure 4-4) complete the following actions: While on the Welcome screen, press the Pushbutton and hold for 3 beeps to access the Settings menu, then select Firmware and Main to return to the Welcome screen, select Back and Exit.

Figure 4-4 - Device Information Screen for WLAN device

**1.1.1 Connection Status Page** In addition to the icons at the top of the display, WLAN enabled devices have a WLAN Status screen that reports more details about the device’s 802.11 wireless (see Figure 4-5) connection. To access it: * While on the Welcome screen, press the Pushbutton and hold for three beeps to get to the Settings menu. * Select Connection * Select WLAN Settings * Select WLAN Status To return to the Welcome screen: * Select Back * Select Exit
## **SoftAP Page** To configure WLAN enabled devices via SoftAP mode (see Figure 4-6) complete the following steps: 1. While on the Welcome screen, press the Pushbutton and hold for three beeps to get to the Settings menu. 2. Press Connection 3. Press WLAN Settings 4. Press SoftAP Mode​ To return to the Welcome screen: * Select Back * Select Exit ## **Power Management** This device incorporates a built-in Lithium-ion rechargeable battery, which requires little maintenance. It is not subject to “charge memory” and therefore does not require deep discharge cycles to restore its charge capacity like many other battery technologies. When properly powered through its USB port, the device powers on automatically, remains powered on provided the host does not put it in USB Suspend mode, and draws power both for operation and for recharging the battery (see **How to Charge the Battery**). While charging, the device consumes more power from the USB connection than when the battery is fully charged. The device stops charging the battery when it determines it is optimally full, to prevent overcharging. If the device is not connected to USB power, or if the USB connection does not provide enough power, the device powers itself using the rechargeable battery. When the battery discharges to a critically low level, the device powers down automatically. It is important to not allow the device’s main battery to remain completely discharged any longer than necessary. For information about how to prevent this from occurring during handling and storage, see section 2.3 Handling to Avoid Accidental Tamper. To prevent this from occurring during regular use: · Do not allow the device’s main battery to remain completely discharged for prolonged periods of time, and ideally do not allow it to ever reach 0%. Create a charging schedule that recharges the battery well before it is fully depleted. · When the device is not connected to USB power, preserve the battery’s charge when it is not in use by putting the device into Sleep mode or powering it off completely (see **How to Power On / Wake Up from Standby Mode / Power Off**). The device’s rechargeable battery is designed to last hundreds of charging cycles, but with time and / or with use, its charge capacity will naturally degrade. Following the recommendations in this section will maintain the battery’s charge capacity for as long as possible. ## **How to Check Battery Level** When powered on, DynaFlex II starts in the idle / waiting state and shows a Welcome page on the touchscreen. See **How to Power On / Wake Up from Standby Mode / Power Off**. This page indicates battery level and charge status on the top right corner of the screen. See Figure 4-7 Welcome Screen.

Figure 4-7 Welcome Screen

The table of symbols below describes the various power level and charge status icons. #### Battery Power Level and Charge Status Icons
Battery Power Level and Charge Status Icons
Battery is fully charged.
Battery is OK, between 20% and 95% charged.
Battery is low, between 10% and 20% charged.
Battery is critically low, between 3% and 10% charged.
Battery is empty, below 3% charged.
Battery is charging.
{% hint style="warning" %} **Notice:** 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. {% endhint %} ## **How to Charge the Battery** DynaFlex II products have an onboard rechargeable battery to supply their own power when not powered through the USB-C port. The battery must be periodically recharged by connecting the device to the optional charging station, or to a USB port or stand-alone USB charger. Both the charging station and the device require a USB power supply that can provide at least 500mA @ 5V, optimally 1A @ 5V. To charge the device without an optional charging station, connect it to a USB charger or a USB host as described in How to [**Connect DynaFlex II Products to a Host or Charger via USB**](https://developer.magtek.com/downloads-compliance-and-marketing-materials/~/revisions/MW79pcnG8UAYcysAAY9u/device-manuals-product-specific/dynaflex-ii-ped-manuals/installation-and-operation-manual/installation#how-to-connect-dynaflex-ii-products-to-a-host-or-charger-via-usb). For best results, use the cable that is included with the device; it includes shielding at both ends to reduce interference. When charging, make sure the device is receiving enough power from the USB connection (the battery level should increase even when device is in use). A full recharge cycle for a completely drained battery depends on how it is being charged. From a host USB port at 500mA or dedicated wall charger, full charge takes approximately 7 hours. After connecting the device to a power source, make sure the LEDs indicate the device is charging (see section 4.3 About the Status LEDs). To charge the device in the optional charging station *for power only (no USB communication)*: 1. Make sure the charging station is properly installed and is receiving USB power. See [**How to Mount the Charging Station**](https://developer.magtek.com/downloads-compliance-and-marketing-materials/~/revisions/MW79pcnG8UAYcysAAY9u/device-manuals-product-specific/dynaflex-ii-ped-manuals/installation-and-operation-manual/installation#how-to-mount-the-charging-station). 2. Place the device in the charging station with the charging contacts pointing into the charging station and the device’s face pointing toward the ceiling as shown in Figure 3-15 – Connecting DynaFlex II to the Optional Charging Station. 3. Check the device’s LEDs to make sure it is charging. 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 [**Handling to Avoid Accidental Tamper**](https://developer.magtek.com/downloads-compliance-and-marketing-materials/~/revisions/MW79pcnG8UAYcysAAY9u/device-manuals-product-specific/dynaflex-ii-ped-manuals/installation-and-operation-manual/inspection-handling-and-storage#id-2.3_handling_to_avoid_accidental_tamper) and **About Power**. ### **How to Power On / Wake Up from Standby Mode / Power Off** To power on the device, press and hold the Pushbutton for one second, or connect the device to USB power. After powering on, devices with touchscreens show a page of information about the device, then transition to showing the Welcome page or custom graphics, if they are configured to do so. For more information about custom graphics, see [**DynaFamily Programmer’s Manual.**](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual) To power off the device, disconnect the device from USB power. To reset the device, see section **How to Force Reset**. If all LEDs are off, the device is in Powered Off mode, USB Suspend mode, or Standby mode. For details about reading the status of the device with LEDs, see **About Operating Modes** and **About the Status LEDs.** ### **How to Force Reset** To force the device to reset, power it off then power it on again (see **How to Power On / Wake Up from Standby Mode / Power Off**). Alternatively, you may use a small tool such as a paperclip to carefully press the Recessed Switch inside the small hole on the bottom of the device (see [**About DynaFlex II Components**](https://developer.magtek.com/downloads-compliance-and-marketing-materials/~/revisions/MW79pcnG8UAYcysAAY9u/device-manuals-product-specific/dynaflex-ii-ped-manuals/installation-and-operation-manual/introduction#id-1.5_about_dynaflex_ii_components)). The host may also reset the device by sending the Reset Device command (see **Developing Custom Software**). The device also automatically powers off if the rechargeable battery reaches a level that is low enough to prevent the device from successfully completing a transaction. **About USB Suspend** When the device is connected to a host via USB (see [**How to Connect DynaFlex II Products to a Host or Charger via USB**](https://developer.magtek.com/downloads-compliance-and-marketing-materials/~/revisions/MW79pcnG8UAYcysAAY9u/device-manuals-product-specific/dynaflex-ii-ped-manuals/installation-and-operation-manual/installation#how-to-connect-dynaflex-ii-products-to-a-host-or-charger-via-usb)), the host and its operating system can use standard USB functions to put the device into USB Suspend mode to conserve power (see **About Operating Modes**). This occurs when there is no software running on the host that has an active USB connection with the device. When the device goes into USB Suspend mode, the device’s display and LEDs turn off. When the host wakes up the device from USB Suspend, the device returns to normal operation. It is possible to configure a Windows host to not suspend the device by editing the registry. Open HKEY\_LOCAL\_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID\_0801\&PID\_2020, then open the folder with the device’s serial number inside that folder and open the Device Parameters folder inside that. Set the value of EnhancedPowerManagementEnabled equal to 0. After changing the setting, physically disconnect and re-connect the device to the host.
### **About Maintenance Reset** For security purposes, the device is designed to perform an automatic maintenance reset periodically to clear all data from memory. When the device has been on continuously for 23 hours, it terminates all current operations, stops responding to new commands, and immediately performs a full reset. At the end of the automatic maintenance reset, the device powers back on and returns to normal operation. ## How to Start a Handheld Transaction Using Wireless LAN The operator uses the point of sale to start a transaction by following these steps and guidelines below: 1. Ensure that the device is powered on, see **How to Power On / Wake Up from Standby Mode / Power Off.** 2. Ensure that the device is connected to a wireless access point and has good signal strength (Refer to **Connection Status Page**.) 3. Start the transaction using the point of sale’s interface. Depending on how the host software is designed, the host sends various messages requesting that the cardholder or operator enter additional information, and the device requests payment as described in **Using the Reader.** 4. Should the device run out of battery or the device is disconnected from the network during a transaction, the operator should cancel the transaction on the point of sale, and proceed to repeat these steps to initiate the transaction again. ## Using the Reader The steps for starting a transaction and reading a card or contactless payment device are different depending on the device’s configuration and on the design of the host software. Host software developers should see **Developing Custom Software** for implementation references. The solution developer should provide solution-specific instructions for operators to follow. A transaction follows this essential flow: 1. An advanced operator has already made sure DynaFlex II or DynaFlex II PED is configured properly and is connected to the host (see [**Connecting to a Host**](https://developer.magtek.com/downloads-compliance-and-marketing-materials/~/revisions/MW79pcnG8UAYcysAAY9u/device-manuals-product-specific/dynaflex-ii-ped-manuals/installation-and-operation-manual/installation#id-3.2_connecting_to_a_host)). When the device is connected to the host via USB and powered by the USB-C connector, the host software may always keep a connection open to the device. 2. The operator makes sure DynaFlex II or DynaFlex II PED is receiving power either from its rechargeable battery or from the USB connection, and is awake and powered on (see How to Power On / Wake Up from Standby Mode / Power Off and About the Status LEDs). 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 swiping, inserting, or tapping a card or electronic payment device, or pressing the touchscreen, the host software may respond to those inputs by notifying the host, and 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). 4. The host communicates with the device, and reports to the operator when the device is ready. 5. The operator guides and assists the cardholder in presenting payment. 6. The cardholder interacts with the device to present payment. The following sections provide additional details about presenting each of the available payment methods. 7. Devices with a touchscreen, display messages prompting the cardholder to perform certain actions. The host should also monitor the progress of the transaction, and when necessary, should report issues to the operator, who may need to relay the messages to the cardholder. 8. The device reports the success or failure of the transaction to the cardholder and to the host. ### **How to Swipe Magnetic Stripe Cards** To swipe magnetic stripe cards, follow these steps: 1. Wait for the device to display an action prompt, or, if the solution is designed to respond to cardholder actions that occur while the device is idle, such as swiping, inserting, or tapping a card or electronic payment device, or pressing the touchscreen, initiate the transaction by performing one of those actions instead of waiting. In these cases, the device may automatically and rapidly pass through several of the steps below without requiring cardholder interaction. 1. Devices with a display show on-screen text and buttons (see Figure 4-8 below for examples). 2. The device shows the transaction status using the LEDs. If the host has directed the device to enable the contactless interface, LED1 lights solid green and all other LEDs are off, per EMV standards, to indicate it is ready for a tap. If the host has directed the device to disable the contactless interface, the device continues to show idle statuses on LED1 and LED2. 3. 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, “swipe, insert, or tap your card now please”). 2. Locate the magnetic stripe reader swipe path on the face of the device. 3. Orient the card with the magnetic stripe facing away from the cardholder and the touchscreen or contactless landing zone, toward the LEDs and the chip card insertion slot as shown in Figure 4-9. 4. Swipe the card through the magnetic stripe reader in either direction. 5. Look for a prompt that the device has successfully read the card: 1. The device turns LED4 green for a short time. 2. The device beeps once. 3. If the device has a display: 1. The device displays PROCESSING . 2. The device may display AUTHORIZING PLEASE WAIT . 3. If the transaction requires a signature, the device prompts for a signature (see **How to Use Signature Capture**). 4. The device shows THANK YOU . 4. The device ends the transaction and reports the transaction status to the host. 6. If the device cannot read the card’s magnetic stripe data: 1. The device turns LED4 red for a brief time. 2. The device beeps twice. 3. The device ends the transaction. 4. Devices with a display show FAILED , then THANK YOU , then return to the idle page (see **Welcome Page / Active Idle Page**). 5. 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 enter card data manually (see How to Enter Card Information Manually). Immediately after the user swipes a magnetic stripe card, the device disables the option to use the contactless interface. If the cardholder needs to revert to a contactless card or device for payment while a transaction is in process, the operator should cancel the transaction and start again.


Figure 4-8 – Example Card Swipe Screens

Figure 4-9 – Swiping a Magnetic Stripe Card

## **How to Insert Contact Chip Cards** To insert contact chip cards, follow these steps: 1. Wait for the device to display an action prompt, or, if the solution is designed to respond to cardholder actions that occur while the device is idle, such as swiping, inserting, or tapping a card or electronic payment device, or pressing the touchscreen, initiate the transaction by performing one of those actions instead of waiting. In these cases, the device may automatically and rapidly pass through several of the steps below without requiring cardholder interaction. 1. Devices with a touchscreen display on-screen text and buttons (see Figure 4-10 below for examples). 2. Devices with or without a touchscreen show the transaction status using the LEDs. If the host has directed the device to enable the contactless interface, LED1 lights solid green and all other LEDs are off, per EMV standards, to indicate it is ready for a tap, swipe, or insert. If the host has directed the device to disable the contactless interface, the device continues to show idle statuses on LED1 and LED2. 3. 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, “swipe, insert, or tap your card now please”). 2. Locate the chip card insertion slot on the face of the device, as shown in Figure 4-11. 3. Orient the chip card so the chip faces the cardholder, toward the touchscreen or contactless landing zone and the LEDs. 4. Insert the chip card into the slot, then push gently on the card until it stops. There should not be any substantial resistance until the chip card is fully inserted. 5. Wait for a prompt that the device has successfully read the card, then remove the card. 1. The device turns LED4 green for a brief time. 2. The device beeps once. 3. If the device has a display: 1. The device shows Processing 2. The device shows Please Wait and/or AUTHORIZING PLEASE WAIT . 3. If the transaction requires a signature, the device prompts for a signature (see **How to Use Signature Capture**). 4. The device shows REMOVE CARD . 5. The device shows THANK YOU . 4. The device ends the transaction and reports the transaction status to the host. 5. As a reminder to the cardholder to remove the card, the device beeps continuously until the card is removed. 6. If the device cannot communicate with the chip card: 1. The device illuminates LED4 red for a short time. 2. The device beeps twice. 3. Devices with a touchscreen display FAILED, then Remove if the card is still in the slot, then THANK YOU, when the card is removed. The device then returns to the idle page (see **Welcome Page / Active Idle Page**). 4. The device ends the transaction and notifies the host that the transaction failed. If this occurs, the host software may choose to retry the transaction (for example, with different payment types enabled) or revert to prompting the operator to enter card data manually (see **How to Enter Card Information Manually**). 5. As a reminder to the cardholder to remove the card, the device double-beeps continuously until the card is removed. Immediately after the user inserts a chip card, the device disables the option to use the contactless interface. If the cardholder needs to revert to a contactless card or device for payment while a transaction is in process, the operator should cancel the transaction and start again.

Figure 4-10 – Example Card Insertion Screens

Figure 4-11 – Inserting a Chip Card

## **How to Tap Contactless Cards / Devices** To tap a contactless card or smartphone, follow these steps: 1. Wait for the device to display an action prompt, or, if the solution is designed to respond to cardholder actions that occur while the device is idle, such as swiping, inserting, or tapping a card or electronic payment device, or pressing the touchscreen, initiate the transaction by performing one of those actions instead of waiting. In these cases, the device may automatically and rapidly pass through several of the steps below without requiring cardholder interaction. 1. Devices with a touchscreen show on-screen text and buttons (see Figure 4-12 below for examples). 2. Devices with or without a touchscreen show the transaction status using the LEDs. LED1 lights solid green and all other LEDs are off, per EMV standards, to indicate it is ready for a tap (or swipe or insert, if the host has enabled those interfaces for this transaction). 3. 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”). 2. 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. 3. 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 4-12). 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. 4. Wait for a prompt that the device has successfully read the card, smartphone, or other contactless payment device, then remove it from the contactless landing zone. 1. The device quickly lights the second LED green to show it is processing, then lights the third LED green to show it has successfully read the tap, then lights the fourth LED green to show the read is complete (see Figure 4-14). 2. The device beeps once. 3. If the device has a touchscreen: 1. The device may display PROCESSING . 2. The device displays REMOVE CARD . 3. If the transaction requires a signature, the device prompts for a signature (see **How to Use Signature Capture**). 4. The device displays THANK YOU . 4. The device ends the transaction and reports the transaction status to the host. 5. If the device cannot communicate with the card, smartphone, or other contactless payment device: 1. The device ends the transaction. 2. The device illuminates LED4 red, for a brief time. 3. The device beeps twice. 4. Devices with a touchscreen display INSERT, SWIPE, OR TRY ANOTHER CARD , then THANK YOU. The device then returns to the idle page (see **Welcome Page / Active Idle Page**). 5. The device notifies the host that the transaction failed. If this occurs, the host software may choose to retry the transaction (for example, with different payment types enabled) or revert to prompting the operator to enter card data manually (see **How to Enter Card Information Manually**).

Figure 4-12 – Example Contactless Transaction Screens

Figure 4-13 – Tapping a Contactless Card / Smartphone

## **How to Tap Contactless NFC Tags / MIFARE Classic / MIFARE DESFire /MIFARE Plus Cards and Send Pass-through Commands** To tap a contactless NFC Tags / MIFARE Classic / MIFARE DESFire /MIFARE Plus cards, follow these steps: 1. Wait for the device to display an action prompt. If the solution is designed to respond to cardholder actions that occur while the device is idle, such as swiping, inserting, or tapping a card or electronic payment device, or pressing the touchscreen, initiate the transaction by performing one of those actions instead of waiting. In these cases, the device may automatically and rapidly pass through several of the steps below without requiring cardholder interaction. 1. Devices with a touchscreen display on-screen text and buttons (see Figure 4-12 for examples) via the host. 2. Devices with or without a touchscreen show the transaction status using the LEDs. LED1 illuminates solid green, and all other LEDs are off, per EMV standards, to indicate it is ready for a tap (or swipe / insert, if the host has enabled those interfaces for this transaction). 3. 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”). 2. 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. 3. Wait for LED status: 1. 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. 2. The Host application can further interact with the NFC Tag using pass-through commands. For details, see[ **DynaFlex Products Programmer’s Manual**](https://developer.magtek.com/api-and-command-reference/dynafamily-programmers-manual)*.* 3. 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. 4. 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. 4. The device notifies the host that the transaction has ended with the NFC Tag removed. ### **How to Scan Barcodes** To scan a barcode, follow these steps: 1. Make sure you are using a DynaFlex II model that includes a barcode reader, indicated by QR code markings on the face of the device surrounding the barcode reader lens (see [**About DynaFlex II Components**](https://developer.magtek.com/downloads-compliance-and-marketing-materials/~/revisions/MW79pcnG8UAYcysAAY9u/device-manuals-product-specific/dynaflex-ii-ped-manuals/installation-and-operation-manual/introduction#id-1.5_about_dynaflex_ii_components)). 2. 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*. 3. 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. 4. Wait for the device, the host, or the operator to prompt for a barcode read: 1. Devices with a touchscreen display the prompt SCAN BARCODE . 2. When the cardholder (or operator on devices without a touchscreen) presses SCAN BARCODE , the device illuminates the barcode reader indicator LED next to the barcode reader lens. 5. Hold the barcode in front of the barcode reader camera: 1. If possible, use the barcode reader's indicator LED light to align the barcode within its field of view. The barcode reader lens’ field of view spans 16 degrees above and below the lens, and 21 degrees to the left and right of a line perpendicular to the lens. 2. Hold the barcode as close as one inch from the barcode reader lens. For smaller barcodes, the device will read immediately. If it does not, gradually pull back 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. 3. Do not tilt the barcode more than 60 degrees from parallel to the device’s face. 6. Wait for the device or the host to report the barcode has been read successfully: 1. Devices with a touchscreen will no longer display the prompt SCAN BARCODE. 2. The device beeps once. 3. The device turns off the barcode reader indicator LED.

Figure 4-15 – Scanning a Barcode

## **How to Enter Card Information Manually** Devices with touchscreen displays provide support for starting a transaction that immediately prompts the operator or cardholder to enter card data manually. Manual card entry can be useful in the following situations: * **As a last resort form of transaction fallback:** * The cardholder swiped during a transaction that had one or more card interfaces enabled, but the device could not read card data. * The cardholder inserted a chip card during a transaction that had one or more card interfaces enabled, but the device could not read card data and could not fall back to swipe. * In card not present transactions, including merchant locations where cardholders do not have their card, in telephone call centers, and so on. In these cases, the operator uses the device to keep sensitive data out of the merchant’s domain, for compliance and security reasons. To enter card information manually, follow these steps. For every prompt below, press the Enter button after entering data to move to the next step, or press the Backsp button to delete data that has already been entered but stay on the same step, or press the Cancel button to completely end the transaction: 1. The operator starts a transaction, specifying manual card entry, optionally specifying a transaction amount and cash back amount. If the solution is designed to respond to cardholder actions that occur while the device is idle, such as pressing the touchscreen, the operator may initiate the transaction by performing one of those actions instead of initiating the transaction from the host. 2. The device shows a numeric keypad and a prompt to enter Card Number (see Figure 4-16). Enter the card number and press the Enter button. If the device double-beeps when pressing the Enter button and does not proceed to the next step, the PAN is not valid. The device may be configured to enable MOD10 validation, which makes sure the card number passes a validity check to prevent errors during entry. It is also possible you have entered too many or too few PAN digits. Double-check the card number and use the Backsp button to correct any errors, then press Enter. 3. The device displays a numeric keypad and a prompt to enter Exp Date (MMYY) (see Figure 4-17). Enter the expiration date on the card and press the Enter button. 4. The device shows a numeric keypad and a prompt to enter CVV/CVC/Card ID . Enter the card verification code / value, then press the Enter button. This code is a 3- or 4- digit number printed on the front or back of the card, and is also referred to as a security code, security validation value, CAV2, CVC2, CVV2, or CID, depending on which payment brand issued the card. 5. The device shows a summary of all the data that was entered during the transaction. If the operator specified a transaction amount when starting the transaction, the summary includes the total transaction amount (purchase amount plus cash back, if any). 6. Verify all the information is correct: 1. If it is correct, press the Enter button to proceed with the transaction. 2. If it is correct but the cardholder or operator wishes to stop the transaction, press the Cancel button to completely end the transaction. 3. If it is not correct, press Cancel button to completely end the transaction, and start the transaction again from the first step.

Figure 4-16 – Enter Card Number

Figure 4-17 – Enter Expiration Date

Figure 4-18 – Enter CVV/CVC/Card ID

## **How to Verify the Transaction Amount** When the device is processing a transaction using the EMV Transaction Flow (as opposed to the Quick Chip Transaction Flow), devices with a touchscreen display the amount of the transaction when they prompt the cardholder to swipe, dip, or tap a card or payment device, as shown in Figure 4-19. The cardholder implicitly confirms / accepts the transaction amount by presenting payment.

Figure 4-19 - Example Transaction Amount Screens

## **How to Enter PINs** Devices with a touchscreen display provide support for requesting a PIN from the cardholder. The device prompts the cardholder to Enter PIN (see Figure 4-20) as required by the financial institution. The device expects the PIN to be between 4 and 12 digits long. After entering the PIN, the cardholder must press the Enter button.

Figure 4-20 – Enter PIN

If the double PIN entry option is enabled, the device prompts the cardholder to enter the PIN a second time (see Figure 4-21). *The process for re-entry is identical to the process for the first entry*.

Figure 4-21 – Enter PIN Again

## **How to Enter Tip** Devices with a touchscreen display provide support for requesting a Tip Entry from the cardholder. The device prompts the cardholder to Enter Tip (see Figure 4-22 – Enter Tip).

Figure 4-22 – Enter Tip

If the cardholder selects a Custom button, the device prompts a keypad for the cardholder to ENter Tip Amount (see Figure 4-23 – Enter Tip Amount). After entering the Tip Amount, the cardholder must press the Enter button.

Figure 4-23 – Enter Tip Amount

After finalizing the Tip, and pressing the Subnmit button, the device prompts the cardholder to present a payment (see Figure 4-24). The on-screen prompt is different depending on which payment method(s) the host directed the device to enable for the transaction. If the Quick Chip flow is in effect, the prompt does not include the transaction amount. If the Full EMV flow is in effect, the prompt includes the transaction amount.

Figure 4-24 – Example Present Payment Screen

### **How to Enter Sale Amount** Devices with a touchscreen display and active connection to a Wireless Local Area Network (WLAN) Host provide support for entering a Sale Amount from the cardholder. The device prompts the cardholder with the Start Sale button (see Figure 4-25).

Figure 4-25 - Start Sale Screen

When the cardholder presses the Start Sale button, the device prompts the cardholder to Enter Sale Amount (see Figure 4-26).

Figure 4-26 - Enter Sale Amount

After the cardholder enters the Sale Amount and presses Enter, the device prompts the cardholder to enter Tip (see **How to Enter Tip**). ## **How to Use Signature Capture** {% hint style="warning" %} **Caution:** Do not use a stylus or other hard object on the touchscreen. The touchscreen is designed for fingers only and can be scratched or damaged if misused. {% endhint %} When a device with a touchscreen display prompts cardholders with a Please Sign page, (Figure 4-27 - Signature Capture Requested) cardholders should use the tip of their finger to *press and glide against the screen to sign*, then press the OK button. To clear the current signature on the display and start over, press the Clear button.

Figure 4-27 - Signature Capture Requested

Devices that do not have a touchscreen display cannot prompt for or collect a signature. When these devices are aware that a signature is required to complete a transaction, they send a notification message to the host that includes the status Signature Capture Requested. In this case, the solution design collects the cardholder’s signature via a different method. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://developer.magtek.com/downloads-compliance-and-marketing-materials/device-manuals-product-specific/dynaflex-ii-ped-manuals/installation-and-operation-manual/operation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.