> 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/hardware/card-readers/mms-dyna-devices/dynaflex-ii-ped/documentation/user-manuals/dynaflex-ii-product-family-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><img src="/files/UWURLBCGaWTICgd3N3t1" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/7izTMmYOFFC8oXPRNQH1" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/T41LaKf8JoCQ9BtrmihA" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/Z7rtXIwnETaIozoF58RH" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/dg219JjyEuw1AUGwmEhz" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/TLNKtNIHIPWzwNbkWyDr" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/dlhUovJIgxPtSAtURO3x" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/fENMfBiNsU2vV3RZEdO1" alt=""><figcaption></figcaption></figure>

<p align="center"><strong>Figure 4-1 - Typical Transaction Sequence</strong></p>

## 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.

## Table – DynaFlex II LED Allocation

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th><th valign="top"></th><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">In This Context</td><td valign="top">LED1</td><td valign="top">LED2</td><td valign="top">LED3</td><td valign="top">LED4</td></tr><tr><td valign="top">Active Mode: Not Armed for a Tap Transaction</td><td valign="top">Power</td><td valign="top">Connection</td><td valign="top">Reserved</td><td valign="top">Card Read Result</td></tr><tr><td valign="top"><p> </p><p>Active Mode: Armed for a Tap Transaction</p></td><td valign="top"><p> </p><p>Armed for Tap</p></td><td valign="top"><p> </p><p>Tap Read Progress</p></td><td valign="top"><p> </p><p>Tap Read Progress</p></td><td valign="top"><p> </p><p>Card Read Result</p></td></tr></tbody></table>

{% hint style="danger" %}
**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.
{% endhint %}

## Table – DynaFlex II LED Colors

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Color</td><td valign="top">Means</td></tr><tr><td valign="top"><p> </p><p> Red <img src="/files/X43tpbjZesAhgb4cfwXF" alt=""></p></td><td valign="top"><p>Stop or stopped</p><p>Example: LED1 is red. Stop using device: Battery is about to run out of charge.</p></td></tr><tr><td valign="top"><p> </p><p> Yellow <img src="/files/BLyYUm8DXsi2uFl3d3C5" alt=""></p></td><td valign="top"><p>Wait or waiting</p><p> </p><p>LED2 will show status for Access Point connection: Green connected, yellow waiting for connection.</p></td></tr><tr><td valign="top"><p> </p><p> Green <img src="/files/TzAVRnuSBtUOoXfgzsn9" alt=""></p></td><td valign="top"><p>Go, going, or went.</p><p>LED3 will show status for WebSocket connection: Green connected, yellow Waiting for connection.</p></td></tr><tr><td valign="top"><p> </p><p>Other Colors</p></td><td valign="top"><p> </p><p>Reserved</p></td></tr></tbody></table>

## Table – DynaFlex II LED Patterns

<table data-header-hidden><thead><tr><th width="139.33331298828125" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Color</td><td valign="top">Means</td></tr><tr><td valign="top"><p>Solid</p><p><img src="/files/8vJUvkAfq0wyi2Zp798C" alt=""><br></p></td><td valign="top"><p>Solid LEDs require an operator or cardholder to take action to change the state the LED is reporting.</p><p> </p><p>Example: Host is connected. Cardholder or host would have to disconnect. Example: Host is disconnected. Host would have to initiate connection.</p></td></tr><tr><td valign="top"><p>Blinking</p><p><img src="/files/bRbtgSuCGJoWaPzdVrHw" alt=""></p></td><td valign="top"><p>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.</p><p> </p><p>Example: Device is attempting to connect to the WLAN access point.</p></td></tr><tr><td valign="top">Short time <img src="/files/RctMPSPMU6sABk7WUtYL" alt=""></td><td valign="top"><p>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.</p><p>Example: Successful card read.</p></td></tr></tbody></table>

## 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 *D998200383 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.

The Table below shows the icons and describes their meanings. For example, in the previous Figure, 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.

## Table – Status Icon Meaning

<table data-header-hidden><thead><tr><th width="116" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Status Icon</td><td valign="top">Meaning</td></tr><tr><td valign="top"> <img src="/files/LgD7en0SHvgn9e1qhXZN" alt=""></td><td valign="top">Device’s Active Connection is set to USB, and the device has successfully established a USB communication connection with the host.</td></tr><tr><td valign="top"> <img src="/files/BCljci4vEQvjIx1nTBTY" alt=""></td><td valign="top">WLAN is not configured</td></tr><tr><td valign="top"> <img src="/files/QUQREytCSKalQHmEOlHS" alt=""></td><td valign="top">Blinking to show device is connecting to a wireless access point</td></tr><tr><td valign="top"> <img src="/files/5UNZdRG0ZXupamVSiOWX" alt=""></td><td valign="top">WebSocket is active or connected</td></tr><tr><td valign="top"> <img src="/files/o7RDwH86XapwSGYtb2Iu" alt=""></td><td valign="top">WebSocket is inactive or disconnected</td></tr><tr><td valign="top"> <img src="/files/zI9nI1H37fwWLGDyq5SH" alt=""></td><td valign="top">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).</td></tr><tr><td valign="top"><p> <img src="/files/tjeaQA8C4TNINRBSOLUC" alt=""> </p><p>and <img src="/files/Skhe7vkVuYxlxWE1hDAz" alt=""></p></td><td valign="top">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)</td></tr><tr><td valign="top"> <img src="/files/oV2KsuTQT7QfXFTWEsj5" alt=""></td><td valign="top">Battery is fully charged.</td></tr><tr><td valign="top"> <img src="/files/cqtPd9CopDl4Rmzlelo9" alt=""></td><td valign="top">Battery is OK, between 20% and 95% charged.</td></tr><tr><td valign="top"> <img src="/files/gLmhQt16VJI1RgB1dvDu" alt=""></td><td valign="top">Battery is low, between 10% and 20% charged.</td></tr><tr><td valign="top"> <img src="/files/1Z6PIBx2enUhZaYDYaeJ" alt=""></td><td valign="top">Battery is critically low, between 3% and 10% charged.</td></tr><tr><td valign="top"> <img src="/files/7sfLnTUfQHgzbMKgLley" alt=""></td><td valign="top">Battery is empty, below 3% charged.</td></tr><tr><td valign="top"> <img src="/files/WjssmDb1Egar1XkzX9Zq" alt=""></td><td valign="top">Battery is charging.</td></tr></tbody></table>

<figure><img src="/files/8q64ozxddsLAh8vFp60F" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/n3KC5cXNKlMmUMTuGVbQ" alt=""><figcaption></figcaption></figure>

<p align="center"><strong>Figure - Welcome Page Examples</strong></p>

The device may show text other than “Welcome” when it is Active / idle under certain conditions:

* OFFLINE/Tampered ndicates 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 indicates 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.

<p align="center"><img src="/files/ddClHJ0XFIAZmXMhxJCl" alt=""><br></p>

<p align="center"><strong>Figure - Device Information Screen</strong></p>

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 Pusbutton 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><img src="/files/lc3XUK1jO1ms8btVfZyg" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/2Y91SZIhhmMoZb8MMars" alt=""><figcaption></figcaption></figure>

<p align="center"><strong>Figure - Device Information Screen for WLAN device</strong></p>

In addition to the icons at the top of the display, WLAN enabled devices have a WLAN Status screen what reports more details about the device’s 802.11 wireless (see Figure 4-5) connection. To access it, while on the Welcome screen, press thePusbutton and hold for three beeps to get to theSettings menu, then select Connection , and WLAN Settings, then select WLAN Status . To return to the Welcome screen, select Back and Exit.

<figure><img src="/files/e6Vn3R5zhJ3kq4mFh76b" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/aarkyA1n7tywOirGeMs7" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/BgFWseIJ4dGDxFu4DHxg" alt=""><figcaption></figcaption></figure>

<p align="center"><strong>Figure - WLAN Status Screen</strong></p>

## **SoftAP Page**

To configure WLAN enabled devices via SoftAP mode (see Figure 4-6) complete the following steps:

* While on the Welcome screen, press the Pushbutton and hold for three beeps to get to the Settings menu.
* Press Connection
* Press WLAN Settings
* Press SoftAP Mode ​

To return to the Welcome screen, select Back and Exit.

<figure><img src="/files/e8WkvhGCymT4b3yaxgN6" alt=""><figcaption></figcaption></figure>

<p align="center"><strong>Figure – SoftAP Mode screen</strong></p>

## About Sounds

DynaFlex II products are equipped with an audio transducer (audible signal) that provides feedback to operators and cardholders about the internal state of the device:

* The device sounds one short beep after it has successfully read a contactless tap, and the cardholder can safely remove the card or device from the contactless landing zone.
* The device emits short beeps continuously when a transaction is complete, but the card is still present in the insertion slot.
* The device emits two beeps when reading a card or contactless payment device to indicate that a read error has occurred.
* The device sounds two beeps when an operator cancels a pending EMV transaction.

The device provides an internal setting the host can use to adjust the global system volume. The device does not provide an interface to change the volume setting directly via buttons or the touchscreen. If the device is too quiet or too loud:

* Make sure the device is ordered from the manufacturer with the desired volume setting.
* Check to see whether the host software you are using provides a feature to check and/or adjust the volume setting.
* If the host software does not provide that feature, request help from the development team that built the host software to check / change the volume setting. For details, see *D998200383 DYNAFLEX PRODUCTS PROGRAMMER’S MANUAL (COMMANDS)*.

## &#x20;**How to Play a Sequence of Tones**

DynaFlex II devices can play a customizable sequence of tones if configured to do so. To play a sequence of tones, follow these steps:

* Make sure the device is in idle state.
* Send a Buzzer command to the device to play a sequence of tones. For details, see *D998200383 DYNAFLEX PRODUCTS PROGRAMMER’S MANUAL (COMMANDS)*.

## Power Management <a href="#id-4.6_power_management" id="id-4.6_power_management"></a>

### **About Power**

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 section 4.6.3 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 section 4.6.4 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.

### &#x20;**How to Check Battery Level**

When powered on, DynaFlex II starts in the idle / waiting state and shows a                                                                                                    page on the touchscreen. See 4.6.4 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 - Welcome Screen.

<figure><img src="/files/k8qzpMdEalguJ8sRLDyf" alt=""><figcaption></figcaption></figure>

<p align="center"><strong>Figure - Welcome Screen</strong></p>

The table of symbols below describes the various power level and charge status icons. See Table - Battery Power Level and Charge Status Icons.

## **Table - Battery Power Level and Charge Status Icons**

<table data-header-hidden><thead><tr><th width="172.66668701171875" valign="top"></th><th></th></tr></thead><tbody><tr><td valign="top">Battery Power Level and Charge Status Icons</td><td></td></tr><tr><td valign="top"> <img src="/files/fcjxRfHHYZCTS3xLBpvu" alt=""></td><td>Battery is fully charged.</td></tr><tr><td valign="top"> <img src="/files/tIEOrO31ziuDgtVtWfCp" alt=""></td><td>Battery is OK, between 20% and 95% charged.</td></tr><tr><td valign="top"> <img src="/files/Lj9mqfHFToq2vMN7lFnz" alt=""></td><td>Battery is low, between 10% and 20% charged.</td></tr><tr><td valign="top"> <img src="/files/CwNd8DIO1jPSmmpsUMEk" alt=""></td><td>Battery is critically low, between 3% and 10% charged.</td></tr><tr><td valign="top"> <img src="/files/4sTjrbYsesJwnTQ5Zqgk" alt=""></td><td>Battery is empty, below 3% charged.</td></tr><tr><td valign="top"> <img src="/files/owd2QHP35ySPInbWp5rK" alt=""></td><td>Battery is charging.</td></tr></tbody></table>

## **How to Charge the Battery**

{% hint style="warning" %}
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 %}

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 section 3.2.2 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)*:

* Make sure the charging station is properly installed and is receiving USB power. See section 3.3.4 How to Mount the Charging Station.
* 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.
* 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 section 2.3 Handling to Avoid Accidental Tamper and section 4.6.1 About Power.

### **How to Power On / Wake Up from Standby Mode / Power Off**

To power on the device, press and hold the Pusbutton 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 *D998200383 DynaFlex Products Programmer’s Manual (COMMANDS)*.

To power off the device, disconnect the device from USB power. To reset the device, see section 4.6.5 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 section 4.1 About Operating Modes and section A**bout the Status LEDs.**

### **How to Force Reset**

To force the device to reset, power it off then power it on again (see section 4.6.4 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 section 1.5 About DynaFlex II Components on page 8). The host may also reset the device by sending the Reset Device command (see section 6 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 section 3.2.2 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 section 4.1 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\ESB\VID\_0801\&PID\_202, 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 WnhancedPowerManagementEnabled equal toi 0. After changing the setting, physically disconnect and re-connect the device to the host.

<p align="center"><img src="/files/OGlGIB8MwibfChzdXsyz" alt=""><br></p>

### **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 <a href="#id-4.7_how_to_start_a_handheld_transaction" id="id-4.7_how_to_start_a_handheld_transaction"></a>

The operator uses the point of sale to start a transaction by following these steps and guidelines below:

* Ensure that the device is powered on, see 4.6.4 How to Power On / Wake Up from Standby Mode / Power Off.
* Ensure that the device is connected to a wireless access point and has good signal strength (Refer to section 4.4.3 Connection Status Page.
* 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 section 4.8 Using the Reader.
* 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 <a href="#id-4.8_using_the_reader" id="id-4.8_using_the_reader"></a>

### **About Reading Cards**

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 section 6 Developing Custom Software for implementation references. The solution developer should provide solution-specific instructions for operators to follow. A transaction follows this essential flow:

* An advanced operator has already made sure DynaFlex II or DynaFlex II PED is configured properly and is connected to the host (see section 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.
* 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 section 4.6.4 How to Power On / Wake Up from Standby Mode / Power Off and section 4.3 About the Status LEDs).
* 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).
* 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.
* 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.
* 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:

* 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.
  * Devices with a display show on-screen text and buttons (see Figure 4-8 below for examples).
  * 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.
  * 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”).
* Locate the magnetic stripe reader swipe path on the face of the device.
* 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.
* Swipe the card through the magnetic stripe reader in either direction.
* Look for a prompt that the device has successfully read the card:
  * The device turns LED4 green for a short time.
  * The device beeps once.
  * If the device has a display:
  * The device displays PROCESSING .
  * The device may display AUTHORIZING PLEASE WAIT .
  * If the transaction requires a signature, the device prompts for a signature (see section 4.8.12 How to Use Signature Capture).
  * The device shows THANK YOU .
  * The device ends the transaction and reports the transaction status to the host.
* If the device cannot read the card’s magnetic stripe data:
  * The device turns LED4 red for a brief time.
  * The device beeps twice.
  * The device ends the transaction.
  * Devices with a display show FAILED , then THANK YOU , then return to the idle page (see section 4.4.1 - Welcome Page / Active Idle Page).
  * 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 section 4.8.7 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><img src="/files/mbEJJelbRf3msMkHP9tK" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/Nfl06y4xrkI9tpoMKRze" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/7ebjUYnfrchtXH3Cv4nu" alt=""><figcaption></figcaption></figure>

<p align="center"><strong>Figure – Swiping a Magnetic Stripe Card</strong></p>

## **How to Insert Contact Chip Cards**

To insert contact chip cards, follow these steps:

* 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.
  * Devices with a touchscreen display on-screen text and buttons (see Figure 4-10 below for examples).
  * 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.
  * 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”).
* Locate the chip card insertion slot on the face of the device, as shown in Figure 4-11.
* Orient the chip card so the chip faces the cardholder, toward the touchscreen or contactless landing zone and the LEDs.
* 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.
* Wait for a prompt that the device has successfully read the card, then remove the card.
  * The device turns LED4 green for a brief time.
  * The device beeps once.
  * If the device has a display:
    * The device shows Processing.

ii)    The device shows                          and/or AUTHORIZING PLEASE WAIT .

iii)   If the transaction requires a signature, the device prompts for a signature (see section 4.8.12 How to Use Signature Capture).

iv)   The device shows REMOVE CARD .

v)     The device shows THANK YOU .

d)     The device ends the transaction and reports the transaction status to the host.

e)     As a reminder to the cardholder to remove the card, the device beeps continuously until the card is removed.

<p align="right">6)     If the device cannot communicate with the chip card:</p>

<p align="right">a)     The device illuminates LED4 red for a short time.</p>

b)     The device beeps twice.

c)     Devices with a touchscreen display FAILED , then                  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 section 4.4.1Welcome Page / Active Idle Page).

d)     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

<br>

&#x20;

enabled) or revert to prompting the operator to enter card data manually (see section 4.8.7 How to Enter Card Information Manually).

e)     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.


---

# 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/hardware/card-readers/mms-dyna-devices/dynaflex-ii-ped/documentation/user-manuals/dynaflex-ii-product-family-installation-and-operation-manual/operation.md?ask=<question>&goal=<endgoal>
```

`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.
