Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Installing DynaFlex II products is straightforward: The manufacturer or acquirer configures the preferred settings, keys, terminal, and payment brand settings before deployment; end users need only set up a host with appropriate software, configure the software, and connect the device to the host. This section provides general information about inspecting, connecting, and installing DynaFlex II products.
In any solution, DynaFlex II products are connected to a host, which must have software installed that can communicate with the device, and which is capable of processing transactions. To set up the host to work with DynaFlex II products, follow the installation and configuration instructions provided by the vendor of the host or the host software. For information about developing custom host software, see Developing Custom Software.
The following sections provide information on how to connect DynaFlex II products to a host via USB.
Figure 3-1 - Connecting to a USB Host or USB Charger. Left: Countertop Models. Right: Kiosk Models
To connect DynaFlex II products to a USB host or charger using the USB-C port, follow these steps (for reference see Figure 3-1 and About DynaFlex II Components):
For best results, use the cable that is included with the device or another cable from Table 1-2 – DynaFlex II Accessories on page 7. These cables are designed specifically for DynaFlex II products and include ferrite shielding at both ends of the cable to reduce emissions and interference. If the solution design requires an alternate cable, contact MagTek for assistance with ferrite selection and placement, and with connector overmold design.
Connect the USB-C end of the cable to DynaFlex II or DynaFlex II PED.
If you plan to route the cable out the back of the device, route the cable through the cable management clip to change its direction. Even if you are not routing out the back, you may use the cable clip for strain relief, to help stabilize the mechanical connection when cardholders or operators move the device or the cable.
Route the cable in the desired direction (e.g., out the back, left, right, down into the countertop, or into the mounting compartment of a kiosk).
Connect the other end of the USB cable to the charger or to the host’s USB port.
As soon as the device starts receiving power through USB, it automatically powers on.
If the specific device serial number you are connecting has not been connected to the host before, the device shows Welcome on the display, and the Windows system tray on the host reports it is Setting up a device (see Figure 3-2 - Setting Up a Device), When installation is complete (approximately 30 seconds later depending on the host), Windows reports Device is ready,(see Figure 3-3 - Device is Ready) and the device shows in Windows Device Manager under Human Interface Devices as two devices HID-compliant vendor-defined device with VID 0801 and PID 2020 and USB Input Device.
Figure 3-2 - Setting Up a Device
Figure 3-3 - Device is Ready
After successfully connecting to the host operating system via USB, devices with a touchscreen display a Welcome screen or a customizable graphic.
The operating system may put the device into USB Suspend mode. See section 4.6.6 About USB Suspend.
The DynaFlex II product line offers versatile mounting solutions, including:
Integrated Slip-Resistant Adhesive Strips: The underside of the device features three adhesive mounting strips (see Figure 3-4) that provide secure attachment to any clean, non-porous surface. These strips come with a protective film that must be removed before installing onto a surface.
Figure 3-4 - Adhesive Mounting Strip and Protective Film
Lanyard Mount Point: The integrated mount point allows the device to be hung or carried, making it easy to store and handle, particularly in grab-and-go payment environments (see Figure 3-5).
Figure 3-5 - Lanyard Mount Point
Charging Station Compatibility (Non-Kiosk Models): Non-kiosk versions of the device can be placed in an optional charging station. This station can be used in conjunction with the lanyard mount point for quick access and easy drop-in charging between handheld uses.
Figure 3-6 - Charging Station Compatibility
Custom Mounting Options: DynaFlex II devices can be attached to custom mounting brackets or housed within an enclosure, enabling integration into larger system designs.
Verify that the protective film has been removed from the adhesive mounting strips located on the underside of the device (see Figure 3-4).
Mount DynaFlex II devices onto a smooth, flat, and non-porous surface by pressing the device firmly using the adhesive mounting strips (see Figure 3-7).
Figure 3-7 - Mounting DynaFlex onto a Nonporous Surface
Do not mount the device on rough, dirty, or uneven surfaces.
To uninstall the device, twist it to disengage the mounting feet from the mounting surface.
For instructions on using the optional charging station, refer to How to Mount the Charging Station.
If your installation requires custom mounting brackets, contact your MagTek representative for design advice and assistance from MagTek’s Engineering team.
This section provides information and guidelines for designing the mechanical aspects of a solution that incorporates DynaFlex II Kiosk models. MagTek strongly recommends vetting and testing solution designs before finalizing and deploying them to make sure the design meets all requirements (e.g., functional, legal, security, certification, safety, and so on).
When designing the mechanical portions of a solution that incorporates DynaFlex II Kiosk models, consider the following:
Review About DynaFlex II Components for an overall introduction to the device’s physical features and what they are called.
Review Appendix A Technical Specifications.
Review the information below about overall device dimensions and mounting hole locations and use.
Determine device orientation. The device supports all four orientations.
Overall dimensions of the device are shown in Figure 3-8 and Figure 3-9. On request, MagTek can provide a 3D model of the device’s envelope to assist with the mechanical portion of solution design. MagTek strongly recommends building and testing prototypes with actual devices before finalizing the solution design.
Figure 3-8 – DynaFlex II Kiosk Models Overall Dimensions
The screw hole placement on the bottom of DynaFlex II Kiosk models is detailed in Figure 3-9. The holes are designed to accommodate screw size M4 x 0.7mm and a maximum screw depth of 0.315 inches (8mm). The recommended torque range for installing the screws is 20 to 22 in-lbs. (2.3 to 2.5 N-m).
Figure 3-9 – DynaFlex II Kiosk Models Mounting Hole Locations
When designing an enclosure or mounting bracket, make sure there is adequate clearance for cardholders to swipe, insert, and tap. If the solution design includes metal objects anywhere near the device, including metal enclosures, ensure that at all points the metal is no further forward than 15mm below the top face of the device. Proximity to metal can adversely affect the device’s performance.
Figure 3-10 - Unobstructed View of Card Insertion Slot, Swipe Path and Contactless Landing Zone
As a security measure, the device must be installed such that cardholders have a full, unobstructed view of the housing around the card insertion slot opening (“entry zone”) and MSR swipe path prior to insertion or swipe (see Figure 3-10). This is to allow cardholders to easily detect suspicious objects in or around the swipe path and card slot entry, such as bugs / skimmers / tapping mechanisms, and their wires or antennas. Be sure to select an installation height and mounting angle that meet this requirement.
To mount the optional charging station to a countertop using the four adhesive mounting strips on the underside of the charging station (see Figure 3-12), follow these steps:
Determine where the charging station will be placed.
Remove the adhesive strip protective film, ensure the mounting surface is a clean, smooth, and flat surface. It is important to avoid rough, dirty, or uneven surfaces.
Consider the cable length, cardholder and operator ergonomics, and access for cleaning, maintenance, and repair.
If the charging station will be used for charging in handheld operations, unobstructed connection and disconnection of the device from the charging station is also a consideration.
Figure 3-11 - Charging Station Dimensions
Figure 3-12 - Charging Station Mounting Surfaces and Screw Holes
To mount the charging station to a countertop, table, or flat surface using the screw holes on the underside of the charging station (see Figure 3-12), follow these steps:
Determine where the charging station will be installed.
Mark the location of the screw holes by placing the device over the area where it is to be installed (see Figure 3-13).
Once the appropriate measurements have been taken and marked, drill the screw holes into the installation surface. Using (2) M4 x 0.7mm thread pitch (not included) screws, screw up through the drilled holes in the mounting surface, see Figure 3-14.
Connect the charging station to a USB port or to a USB charger with a minimum of 1A current capability. For the best results, use the cable that is included with the device. It includes shielding at both ends of the cable to reduce interference.
Figure 3-13 – Preparing a Flat Surface for Mounting the Charging Station
Figure 3-14 - Screw Installation
Figure 3-15 – Connecting DynaFlex II to the Optional Charging Station
Review any additional requirements from other agencies, such as PCI and EMV solution certification requirements, safety ordinances, and so on, which may introduce additional constraints to the design.
Connect the charging station to a USB port or to a USB charger with a minimum of 1A current capability. For the best results, use the cable that is included with the device. It includes shielding at both ends of the cable to reduce interference.
To uninstall, twist the charging station to disengage the adhesive mounting strips from any surface.
To uninstall, remove the screws from the underside of the charging station.


















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

Tailored for use with mobile handsets, tablets, and desktop computers, DynaFlex II Go offers a variety of accessories designed to meet a wide range of operational needs.
The Countertop Stand is well-suited for countertop placement or battery charging, providing a convenient and secure means of positioning the device.
Users can take advantage of the OtterBox® uniVERSE® adaptor for easy sliding and connection to a wide range of mobile devices, including phones and tablets.
DynaFlex II Go offers the option to install a half-rubber sleeve, intended to boost the device's ingress protection when utilizing the OtterBox® uniVERSE® adaptor for DynaFlex II Go.





The device does not have an on-screen configuration interface. However, it does have settings the host can change using commands. These settings are documented as in .
Installing DynaFlex II Go products is straightforward: The manufacturer or acquirer, configures the preferred settings, keys, terminal, and payment brand settings before deployment; end users need only set up a host with appropriate software, configure the software, and connect the device to the host. This section provides general information about inspecting, connecting, and installing DynaFlex II Go products.
Before unpacking the device, it is important to inspect its secure packaging to make sure it has not been tampered with in storage or in transit. MagTek provides details for inspecting the integrity of the device’s secure packaging in D998200594 DynaFlex II Go Package Inspection Document.
It is important to thoroughly inspect a new device before deployment, and regularly inspect devices in live usage (including its immediate surroundings) to make sure malicious individuals have not tampered with it. MagTek recommends conducting inspection training for all device operators, and an inspection schedule with checkpoints in place to make sure operators are performing inspections as specified and as scheduled. MagTek provides an easy-to-follow device inspection reference D998200593 DynaFlex II Go Device Inspection Document.
DynaFlex II Go products do not have a display. In any solution, DynaFlex II Go must be connected to a host, which must have software installed that can communicate with the device and is capable of processing transactions. To set up the host to work with DynaFlex II Go, follow the installation and configuration instructions provided by the vendor of the host or the host software. For information about developing custom host software, see section 9 Developing Custom Software.
The following sections describe how to connect DynaFlex II Go to a host using the available USB-C receptacle or Bluetooth® Low Energy (LE) connections.
Figure - Connecting to a Host via USB-C
To connect DynaFlex II Go products to a USB host computer or charger using the USB-C port, follow these steps (for reference see Figure 4-1):For best results, use the cable that is included with the device or another cable from Table 1-2 - DynaFlex II Go Accessories on page 9. Connect the USB-C end of the cable to DynaFlex II Go see Figure 4-1 - Connecting to a Host via USB-C.
Connect the other end of the USB cable to the host’s USB port.
As soon as the device starts receiving power through USB, it automatically powers on.
If the specific device serial number you are connecting has not been previously connected to the host, the Windows system tray on the host reports it is setting up a device.
When installation is complete, Windows reports Device is ready , (see Figure 4-2 – Setup Complete) and the device shows in Windows Device Manager under Human Interface Devices (see Figure 4-3 – Windows Device Manager) as two devices: HID-compliant vendor-defined device (see Figure 4-4 – HID Compliant Vendor-defined Device Properties) with VID 0801 and PID 2024 and USB Input Device ..
Figure – Setup Complete
Figure – Windows Device Manager
Figure – HID Compliant Vendor-defined Device Properties
The operating system may put the device into USB Suspend mode.
To connect DynaFlex II Go via Bluetooth® LE to an iOS device, refer to section 9 Developing Custom Software and D998200386 MagTek Universal SDK for MMS Devices Programmer's Manual ( iOS ).
1.1.2 How to Connect DynaFlex II Go to an Android Host via Bluetooth® Low Energy (LE)
To connect DynaFlex II Go to an Android host that supports Bluetooth® Low Energy (LE):
If any Bluetooth® Low Energy (LE) host software has an active data connection to the device, close the connection.
On the Android host, install and configure the host software you intend to use with DynaFlex II Go. If you do not yet have that software, you can download a test tool from the Google Play store called MTUSDK Demo , published by MagTek, Inc. .
Make sure the DynaFlex II Go output connection is configured to transmit card data over Bluetooth® LE. This is the factory default.
Press and hold the Power Button for 4 beeps until LED 4 starts flashing indicating Bluetooth®. Pairing is in process. The Bluetooth® Status LED flashes once per second for up to three minutes, or until a host pairs or connects.
To unpair from the device, follow these steps:
Locate the device in the Bluetooth configuration page.
Press the settings (gear) icon.
Press the Forget button and make sure the device disappears from the disappears from the Paired Devices list.
To connect DynaFlex II Go to a host with Windows 10 version 1703 or above, and Bluetooth® 4.0 or higher hardware that supports Bluetooth® Low Energy (LE), follow these steps:
Make sure the host’s Bluetooth® LE interface is turned on and working correctly.
If any Bluetooth® Low Energy LE host software has an active data connection to the device, close the connection.
On the host, install and configure the software you intend to use with DynaFlex II Go (if you do not yet have that software, you can use 1000007351 MagTek Universal SDK for MMS Devices (Windows) available from MagTek.com, to perform simple tests):
DynaFlex II Go products are designed to provide flexible mounting options:
The device can be mounted to the host via external clip or embedded lanyard.
This section provides information and guidelines for designing the mechanical aspects of a solution that incorporates DynaFlex II Go products. MagTek strongly recommends vetting and testing solution designs before finalizing and deploying them, to make sure the design meets all requirements (e.g., functional, legal, security, certification, safety, and so on).
When designing the mechanical portions of a solution that incorporates DynaFlex II Go products, consider the following:
Review section 1.1 Key Features and Components for an overall introduction to the device’s physical features and what they are called.
Review Appendix A Technical Specifications.
Review the information below about overall device dimensions and mounting hole locations and use.
Review any additional requirements from other agencies, such as PCI and EMV solution certification requirements, safety ordinances, and so on, which may introduce additional constraints to the design.
Overall dimensions of the device are shown in the below Figure. On request, MagTek can provide a 3D model of the device’s envelope to assist with the mechanical portion of solution design. MagTek strongly recommends building and testing prototypes with actual devices before finalizing the solution design.
Figure 4-5 - DynaFlex II Go Overall Dimensions
When designing an enclosure or mounting bracket, make sure there is adequate clearance for cardholders to tap or users to present a bar code. Proximity to metal can reduce the device’s reading range.
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

On the Android host, launch the Settings application and open the Bluetooth menu.
Press the SEARCH FOR DEVICES or Scan button to show an AVAILABLE Bluetooth Devices list.
Locate the seven-digit serial number on the label on the bottom of the device.
Device will appear in the list as
When the host pops up a DG II Go-xxxxxx where xxxxxx matches the serial number. message asking for a code, enter the configured passkey (or the default 000000) to return to the Bluetooth configuration page. The device appears in the PAIRED DEVICES list.
Use the host software or the MagTek Test app to test swiping a card.
Remember to change the default password. See 1000007352 MagTek Universal SDK for MMS Devices (Android).
Make sure the host software knows which device(s) it should interface with.
Make sure the host software is configured to properly interpret incoming data from the device. When using Bluetooth® LE, the device transmits data in GATT format.
Make sure the DynaFlex II Go output connection is configured to transmit card data over Bluetooth® LE. This is the factory default.
In the Start menu type Bluetooth and select Bluetooth and other device settings, or double-click the Bluetooth Devices icon in the taskbar to launch the Bluetooth® & other devices settings window.
Locate the seven-digit serial number on the label on the bottom of the device.
Press and hold the Power Button for 4 beeps until LED 4 starts flashing indicating Bluetooth® Pairing is in process. The Bluetooth® Status LED flashes once per second for up to three minutes, or until a host pairs or connects.
Press the Add Bluetooth or other device button to launch an Add a device window.
Under Choose the kind of device you want to add , select Bluetooth.
Locate the device called DF II Go-xxxxxxx , where xxxxxxx matches the device’s serial number. Enter the configured passkey (or the default 999999) and press the Connect button.
After a short period of time, the text Connected appears below the device you are pairing with. Note that in this case, “Connected” means the device is paired, but the host does not have an active data connection until the host software initiates one.
Press the Done button to close the Add a Device window.
Use the host software to test swiping a card.
Remember to change the default password. See the DynaFlex II Go Programmer’s Reference documents for detail to unpair the device:
Select the device in the Bluetoth and other device settings window.
Press the Remove device button.





The following documents may be used to provide additional details about the device and this security policy:
DynaFlex II Go Installation and Operation Manual
DynaFlex II Go Programmer’s Manual (COMMANDS)
DynaFlex II Go Device Inspection Document
DynaFlex II Go Package Inspection Document
NIST SP 800-57-1 Recommendation for Key Management
ANS X9.24 Part 3:2017, Retail Financial Services Symmetric Key Management, Part 3: Derived Unique Key Per Transaction Using Symmetric Techniques
X9 TR-31:2010, Interoperable Secure Key Exchange Key Block Specification for Symmetric Algorithms
After receiving the device, the customer should visually inspect the product as follows:
Inspect the label found on the back of the device (see section 2.3.1 Hardware Identification) and make sure the label is not missing, obscured, or modified.
Check the PCI Hardware Identifier on the device label and make sure it matches the Hardware # listed for the device on the PCI website for Approved Devices. Go to the PCI compliance web page and search for MagTek, and find the product name, iDynamo 5 Gen III. Compare the Hardware ID and Firmware ID: https://www.pcisecuritystandards.org/assessors_and_solutions/pin_transaction_devices
Check the Device serial number (SN) and make sure it matches with labels on shipping materials and documentation.
Visually inspect the device, per [2], which is included in the package with each device. See section 4.1 Periodic Inspection for more information regarding visual inspection of the device.
Follow the steps in Firmware Identification to view the PCI firmware versions installed on the device. Make sure this matches one of the Firmware # values listed on the PCI web site for iDynamo 5 Gen III.
Connect the device to a host via USB-C for control and power. iDynamo 5 Gen III products are designed to provide flexible mounting options such as:
External clip
Embedded lanyard
See the device installation and operation manual for more information on how to handle and operate the device, [1].
The specified environmental conditions to operate and store the device are:
Operating temperature range: 32°F to 95°F (0°C to 35°C) 5-90% RH with no condensation.
Storage temperature range: -4°F to 113°F (-20°C to 45°C) 10-90% RH with no condensation.
Power Supply: DC 5.0 V/1.0A
Any temperature or operating voltage outside the values listed above will trigger environmental security protections, resulting in a tamper condition. The device will need to be returned to the factory for inspection before this condition can be cleared.
iDynamo 5 Gen III products support a USB-C interface using the USB-HID protocol. Transactions, configuration, firmware updates, and key injection can all be performed using this interface type. Use of any method not listed in this security policy will invalidate the device’s PCI PTS approval.
iDynamo 5 Gen III products ship from the factory fully secure. The devices have no configuration settings that require modification by the user to meet PCI security requirements.
Sensor
Low Threshold Value
High Threshold Value
Internal Voltage
2.2V ± 0.1V
4.2V ± 0.2V
Temperature
-48°C to -27°C
95°C to 105°C
Document Number: D998200619-108
REGISTERED TO ISO 9001:2015
MagTek® is a registered trademark of MagTek, Inc.
MagnePrint® is a registered trademark of MagTek, Inc.
MagneSafe® is a registered trademark of MagTek, Inc.
Magensa™ is a trademark of MagTek, Inc. iDynamo™ is a trademark of MagTek, Inc.
ANSI®, the ANSI logo, and numerous other identifiers containing "ANSI" are registered trademarks, service marks, and accreditation marks of the American National Standards Institute (ANSI).
ISO® is a registered trademark of the International Organization for Standardization.
UL™ and the UL logo are trademarks of UL LLC.
PCI Security Standards Council® is a registered trademark of the PCI Security Standards Council, LLC.
Apple Pay®, Apple Wallet®, iPhone®, iPod®, Mac®, and OS X® are registered trademarks of Apple Inc., registered in the U.S. and other countries. iPad™ is a trademark of Apple. Inc. App StoreSM is a service mark of Apple Inc., registered in the U.S. and other countries. Apple and MFi are registered trademarks of Apple Inc. IOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used by Apple Inc. under license.
Google Play™ store, Google Wallet™ payment service, and Android™ platform are trademarks of Google LLC.
Microsoft®, Windows®, and .NET® are registered trademarks of Microsoft Corporation.
All other system names and product names are the property of their respective owners
Table 0-1
The device always encrypts account data from all three reader types using 112-bit TDEA, 128-bit AES, or 256-bit AES algorithms with X9.24 DUKPT key management. This device does not support any mechanisms such as whitelists or SRED disable that would allow the data to be sent out unencrypted.
The device includes the following cryptographic algorithms:
AES
TDEA
RSA
Rev Number
Date
Notes
108
December 18, 2024
Initial Release

ECDSA (P256 and P521 curves)
SHA-256
The device implements the original AES/TDEA DUKPT as its only key management method. Use of any other method will invalidate PCI approval. DUKPT derives a new unique key for every transaction. For more details, see ANS X9.24 Part 3:2017.
Key Name
Size
Algorithm
Purpose
Transport Keys
32 bytes
AES X9.143 KBPKs
Key Injection
The device does not support manual or plaintext cryptographic key entry. Only specialized tools, compliant with key management requirements and cryptographic methods, specifically ANSI X9.143, can be used for key loading. Use of any other methods will invalidate PCI approval.
Keys should be replaced with new keys whenever the original key is known or suspected to have been compromised, and whenever the time deemed feasible to determine the key by exhaustive attack has elapsed, as defined in NIST SP 800-57-1.
Account Data Key
16 bytes for TDEA and AES-128
32 bytes for AES-256
AES and TDEA DUKPT (ANS X9.24-3)
Encrypt and MAC Account Data
Firmware Protection Key
64 bytes for
ECDSA Curve P-256
ECDSA and SHA-256
Checks integrity and authenticity of firmware
EMV CA Public keys
Varies per issuer
RSA
Authenticate card data and keys
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.
Downloads, Compliance, & Marketing Materials is where you get the files and formal documentation and product brochures for MagTek devices — firmware images, PCI security policies and certifications, and product marketing materials like brochures and videos. It's the home for the artifacts you download for a specific device, kept out of the developer path so the guides and reference stay focused on integration. Product hubs link here for their device-specific files.
Reference Section
Information Available
This section holds links for non-firmware downloadable software for MagTek products, organized by device.



This section contains universal compliance documents as well as compliance and security documentation for specific products.
Find documentation and instructions for product-specific functions including installation and operational manuals.
Brochures, data sheets, videos and catalogs.
ISO 7810, ISO 7811, AAMVA
ISO/IEC 7816-1, 2, 3, & 4 Identification Cards Integrated Circuits with Contacts
EMV ICC Specifications for Payment Systems Version 4.3, L1 Contact and L2 Contact EMV Contactless Level 1 Version 3.0
MasterCard TQM
MCL v3.1.3, payWave v2.2, Expresspay 4.0.2, D-PAS Terminal Payment Application v1.0, D-PAS Terminal Application Specification Bulletins CL TAS-002 v1.1, CL TAS-003 v1.0, CL TAS-004 v1.0
PCI PTS POI v6.x PED
PCI PTS POI v6.x SCR
TDEA (3DES)-CBC using DUKPT
FCC Part 15 Low Power Transceiver, RX verified per FCC Title 47 Part 15 Subclass C
UL 60950 1, 2nd Edition, 2011 12 19 (Information Technology Equipment - Safety - Part 1: General
Requirements), CSA C22.2 No. 60950 1 07, 2nd Edition, 2011 12 (Information Technology Equipment - Safety - Part 1: General Requirements)
CE Certified
UKCA Certified
CE Safety: IEC 62368-1: 2014UL/CSA 62368-1: 2nd Edition
Canada ISED Certified
Japan VCCI Certified (not applicable to WLAN models)
Japan MIC Certified (not applicable to WLAN models)
AS/NZS CISPR 32 (2013), AS/NZS 4268 Table 1, Row 59 DTS 2400-2483MHz SRD (WLAN), and
AS/NZS 4268 (2017) Table 1, Row 43 13.553-13.567MHz (contactless reader)
RoHS Compliant the Electrical and Electronic Equipment (EEE) Reduction of Hazardous Substances (RoHS) European Directive 2002/95/EC
California Proposition 65 (California)
IPC-A-610 Class II Assembly
EU Directive Waste Electrical and Electronic Equipment (WEEE) EU
Directive Restriction of Hazardous Substances (RoHS)
Universal Serial Bus Specifications 1.1, 2.0
IEEE 802.11 b/g/n, IEEE 802.11i-2004 WPA2-PSK, TKIP, AES, SHA-256
TCP/IP secured by Transport Layer Security (TLS) Protocol v1.2
Physical Characteristics
Dimensions (L x W x H):
DynaFlex II and DynaFlex II PED:
4.1 in. W x 3.7 in. L x 1.9 in. H (103.3mm x 95.1mm x 48.5mm)
DynaFlex II Kiosk and DynaFlex II PED Kiosk:
4.1 in. W x 3.7 in. L x 1.9 in. H (103.3mm x 95.1mm x 48.3mm)
Weight
DynaFlex II USB = 8.4 oz. (238g) DynaFlex II PED USB= 8.7 oz. (246g) DynaFlex II PED WLAN = 8.9 oz. (252g) Kiosk Models, add 1.1 oz. (30g)
BCR Models, add 0.12 oz. (3.5g)
Supported Mounting Options:
· Adhesive mounting strips on the underside of the device
· Lanyard mount point
Reader Characteristics
Magnetic Stripe Reader:
Three track bidirectional encrypting reader with MagnePrint
Magnetic Stripe Decoding:
Financial (ISO Type B), AAMVA, or Other
Reference Standards and Certifications
Communication Characteristics
Wired Connection Types:
Magnetic Swipe Speeds:
6 inches per second to 60 inches per second
EMV Contact Reader:
EMVCo L1 and L2 Contact Reader
EMV Contactless Reader:
EMVCo L1 and L2 Contactless Reader
D-PAS, PayPass/MCL, payWave, Expresspay
Mobile wallets including but not limited to Apple Pay, Google Pay, Samsung Pay
Barcode Reader:
Barcode Media: Labels, paper, smartphone / computer displays Barcode Types: QR Codes, Linear Barcodes, UPC-A, UPC-E, Code 128, PDF417 / Data Matrix, etc.
Field Of View 31.5° total vertical sweep, 42° total horizontal sweep, perpendicular to device face
Depth Of Field 1.2 in. (30mm) to 13.8 in. (350mm) Integrated white indicator LED
User Interface Characteristics
Status Indicators:
4 RGB LEDs
Display Type:
TFT a-Si Active Matrix Color LCD with Touchscreen (Select Models)
Display Size (viewable area):
2.3 in. x 1.7 in. (57.6mm x 43.2mm) (Select Models)
Display Resolution:
320 x 240 px, 16-bit color depth (Select Models)
Keypad:
Touchscreen
Security Characteristics
Certifications:
PCI PTS POI 6.xPED PCI PTS POI 6.x SCR
Tamper Protection:
The enclosure and associated electronics form a Tamper Resistant Security Module (TRSM) where attempts to penetrate or modify the
unit cause all cryptographic keys to be cleared or rendered unusable.
Electrical Characteristics
Power Inputs:
USB powered via USB-C receptacle or charging station connectors
Power Outputs:
None
Battery Type:
Lithium Polymer rechargeable
Battery Capacity:
2100 mAh nominal (rated)
Battery Charge Time:
~7 hours connected to a 500mA host USB port
Battery Time, Powered Off
4 years or longer
Battery Time, Standby:
Wireless LAN: Reserved
Battery Time, Transactions:
Reserved
Voltage Requirements:
5 VDC from USB port
Current Requirements:
500mA from USB port
Data Storage:
Not Applicable
USB-C, compatible with USB 1.1, USB 2.0
Vendor-defined USB Human Interface Device (HID) data format
Wireless Connection Types:
TCP/IP over Wireless LAN (select models)
Wireless Range:
WLAN: 100m in a typical environment
Wireless Frequencies and Power:
Wireless LAN:
Frequency range = 2400 MHz to 2484 MHz Average power radiated = 0.80 mW (-0.97 dBm) NFC:
Frequency range = 13.56 MHz
Maximum power conducted = 794 mW (29 dBm)
RF Exposure:
Exempt from SAR requirements due to radiated power substantially below regulatory thresholds.
Software Characteristics
Tested Operating System(s):
USB Hosts: Windows 10, Windows 11
Environmental Resistance
Ingress Protection:
Splash Resistant
Operating Temperature:
32°F to 113°F (0°C to 45°C)
Operating Relative Humidity:
Up to 90% non-condensing
Storage Temperature:
14°F to 140°F (-10°C to 60°C)
Storage Relative Humidity:
Up to 90% non-condensing
Vibration Resistance:
5Hz to 500Hz sinusoidal vibrations at 15g acceleration, all 3 axes
Shock Resistance:
30g 11ms terminal sawtooth shocks, all 3 axes
ESD Tolerance (EMVCo):
±10kV air discharge when device is properly earth grounded
ESD Tolerance (FCC/CE):
±8kV contact discharge / ±12kV air discharge when properly grounded
Vapor Resistance:
Not Applicable
Reliability
Shelf Life:
24 months at 25°C nominal
Magnetic Read Head Life:
1 million swipes
ICC Read Head Life:
500,000 card insertions
Battery Shelf Life:
5 years or longer (backup battery)
Battery Cycle Life:
After 500 charge / discharge cycles, battery capacity remains above 80%.
Periodic cleaning of the device’s exterior may be required. To clean the outside of DynaFlex II products, including the LCD display, wipe down the device with a soft, slightly damp cloth and then wipe dry with a lint-free cloth. The display can also be cleaned using a slightly damp specialty cleaning cloth, like those used to wipe lenses, monitors, and smartphone displays.
MagTek’s double-sided cleaning card is designed to clean the magnetic read head in the MSR swipe path and the contact pins inside all chip card contact readers. Keeping both components clean is essential to the device’s functioning. MagTek recommends swiping and inserting a cleaning card once per week to avoid card misreads.
If the device’s micro-suction mounting feet lose their holding power over time, use a clean, damp, lint-free cloth to wipe the mounting feet and the mounting surface clean, then let both surfaces air dry. This should restore the mounting feet’s holding power. If the mounting feet are damaged and unusable, replacements are available. See Available Models and Accessories.
In addition to the security guidance in the product manuals, MagTek may provide updates to this document, as well as supplemental security guidance or notices regarding vulnerabilities, at developer.magtek.com. MagTek advises checking the product’s home page periodically for the most up-to-date information.
Any firmware updates addressing product features, bugs, or security vulnerabilities are also posted to developer.magtek.com or may be sent directly to affected customers. To update the device’s firmware:
Obtain the firmware image to install.
Download DynaFlex, DynaProx Firmware Upload Utility from the MagTek web site.
Follow the instructions in DynaFlex, DynaProx Firmware Update Utility Manual included in the firmware update utility’s Document subfolder.
Installing DynaProx products is straightforward: The manufacturer or acquirer configures the preferred settings, keys, and terminal and payment brand settings before deployment; end users need only set up a host with appropriate software, configure the software, and connect the device to the host. This section provides general information about inspecting, connecting, and installing DynaProx products.
Before unpacking the device, it is important to inspect its secure packaging to make sure it has not been tampered with in storage or in transit. MagTek provides details for inspecting the integrity of the device’s secure packaging in DynaProx / DynaProx BCR Package Inspection.
It is important to thoroughly inspect a new device before deployment, and regularly inspect devices in live usage (including its immediate surroundings) to make sure malicious individuals have not tampered with it. MagTek recommends conducting inspection training for all device operators, and an inspection schedule with checkpoints in place to make sure operators are performing inspections as specified and as scheduled. MagTek provides an easy-to-follow device inspection reference DynaProx / DynaProx BCR Device Inspection.
In any solution, DynaProx products are connected to a host, which must have software installed that knows how to communicate with the device, and which is capable of processing transactions. To set up the host to work with DynaProx, follow the installation and configuration instructions provided by the vendor of the host or the host software. For information about developing custom host software, see Developing Custom Software.
The following sections provide steps for connecting DynaProx to a host via the various available physical connection types.
Figure 4-1 - Connecting to a USB Host
To connect DynaProx products to a USB host using the USB-C port, follow these steps (for reference see Figure 4-1 and section 1.4 About DynaProx Components): For best results, use the cable that is included with the device or another cable from . These cables are designed specifically for DynaProx products and include ferrite shielding at both ends of the cable to reduce emissions and interference. If the solution design requires an alternate cable, contact MagTek for assistance with ferrite selection and placement, and with connector over mold design.
Connect the USB-C end of the cable to DynaProx.
Connect the other end of the USB cable to the host’s USB port.
As soon as the device starts receiving power through USB, it automatically powers on.
If the specific device serial number you are connecting has not been connected to the host before, Windows system tray on the host reports it is Setting up a device , see Figure 4-2 – Device Setup. When installation is complete (approximately 30 seconds later depending on the host), Windows reports Device is Ready, (see Figure 4-3 – Setup Complete) and the device shows in Windows Device Manager under Human Interface Devices (see Figure 4-4 – Windows Device Manager) as two devices: HID-compliant vendor-defined device (see Figure 4-5 – HID Compliant Vendor-defined Device Properties) with VID 0801 and PID 2020, and USB Input Device.
Figure 4-2 – Device Setup
Figure 4-3 – Setup Complete
Figure 4-4 – Windows Device Manager
Figure 4-5 – HID Compliant Vendor-defined Device Properties
The operating system may put the device into USB Suspend mode. DynaProx does not support USB Suspend mode since this device relies on USB full power support.
The RS-232 interface on DynaProx will provide a UART interface at RS-232 signal levels. No flow control is provided. The signals provided are on J1 of DynaProx and are listed below. See Table 4-1 - RS-232 Signals.
The RS-232 cable will be customer dependent. A sample cable can be provided that has the mating connector for DynaProx and color-coded wires. See Figure 4-6 - Cables and Connectors
Figure 4-6 - Cables and Connectors
The Chassis ground connection will also be a custom cable depending on the customer’s requirement.
DynaProx products are designed to provide flexible mounting options:
The device can be mounted to custom mounting brackets or mounted in an enclosure as part of a larger solution design.
The device can be mounted to the optional stand for countertop use.
This section provides information and guidelines for designing the mechanical aspects of a solution that incorporates DynaProx products. MagTek strongly recommends vetting and testing solution designs before finalizing and deploying them, to make sure the design meets all requirements (e.g., functional, legal, security, certification, safety, and so on).
When designing the mechanical portions of a solution that incorporates DynaProx products, consider the following:
Review for an overall introduction to the device’s physical features and what they are called.
Review .
Review the information below about overall device dimensions and mounting hole locations and use.
Review any additional requirements from other agencies, such as PCI and EMV solution certification requirements, safety ordinances, and so on, which may introduce additional constraints to the design.
Overall dimensions of the device are shown in Figure 4-7. On request, MagTek can provide a 3D model of the device’s envelope to assist with the mechanical portion of solution design. MagTek strongly recommends building and testing prototypes with actual devices before finalizing the solution design.
Figure 4-7 - DynaProx Overall Dimensions
The screw hole placement on the bottom of DynaProx products is detailed in Figure 4-8. The holes are designed to accommodate screw size M4 x 0.7mm and a maximum screw depth of 0.315 inches (8mm) into the device. The recommended torque range for installing the screws is 20 to 22 in-lbs. (2.3 to 2.5 N-m).
When mounting DynaProx, make sure gasket is seated properly to ensure IP65 rating, see Figure 4-9.
The suggested panel cutouts for the USB and RS-232 connectors are shown in Figure 4-10 with a DynaProx shown for reference. The dimensions for the suggested panel cutouts are shown in Figure 4-11.
Figure 4-8 - DynaProx Mounting Hole Locations
Figure 4-9 – DynaProx Gasket
Figure 4-10 – DynaProx Suggested USB and RS-232 Panel Cutouts
Figure 4-11 – DynaProx Suggested USB and RS-232 Panel Cutout Dimensions
When designing the enclosure or mounting bracket, make sure there is adequate clearance for cardholders to tap or users to present a bar code. If the solution design includes mounting to metal surfaces, there will typically not be any impact to performance or card reading range. If the design of the enclosure includes mounting the DynaProx such that the top surface is flush with adjacent metal on the same plane, the range of the contactless reader may be reduced. By keeping the card reading plane a few millimeters above any adjacent metal surfaces or providing a few millimeters of gap between the reader and adjacent metal will assure acceptable card reading performance. Proximity to metal can reduce the device’s reading range.
Major Components, see Figure 4-12 - DynaProx Major Components.
Figure 4-12 - DynaProx Major Components
Stand Contents:
Stand Body: The body of the stand. Angled for better ergonomics.
Cable Channel: Allows the cable to be channeled out the back of the stand body.
(4) M4 Screws: Attaches the stand body to the DynaProx device
(2) Flat-head Screws: Attaches the base plate to the stand body. Base Plate: Bottom of stand, can attach the stand to counter tops Installation of DynaProx Stand
Place the DynaProx face down on a clean, soft surface to avoid scratching the front face of the device. Using minimal toque, use (4) M4 screws to attach the stand to the body
Figure 4-13 - Suggested Installation for DynaProx Stand
Insert the cable and connect securely to the DynaProx device. Clip the cable securely into the cable management hooks. Channel the cable outside the back end of the stand body.
Figure 4-14 - Cable Management
Align the assembly base plate and using the (2) flat-head screws, screw the base plate to the stand body. See Figure 4-15 – Baseplate Installation.
Figure 4-15 – Baseplate Installation
Assembly is complete. Additionally, you can secure the base plate to almost any surface using (2) additional screws, not included.
Securing DynaProx Stand to Surface
Follow Steps 1 through 2, then:
Place baseplate on the location where you want to secure the device. Trace the baseplate and mark the two screw set locations (Drawn Outline). Remove the baseplate and drill down through the surface, checking to make certain everything is clear beneath.
Attach the baseplate to the stand body following step 3. Then align the surface to the tracing.
Using (2) M4 x 0.7mm thread pitch (not included) screws, screw up through the pre-drilled holes to the baseplate. Screws should be long enough to go through the surface and no more than 0.25” into the stand body.
Figure 4-16 - Recommended Disassembly Procedure
Repeat assembly in reverse order to remove device from counter installation and stand. See Figure 4-16 - Recommended Disassembly Procedure.
DynaFlex II is a secure card reader authenticator engineered for attended, unattended, and mobile payment environments. The reader features a magnetic stripe reader, EMV chip reader for both contact and contactless cards, an optional barcode reader, and support for NFC-enabled mobile wallets such as Samsung Pay®, Google Pay®, Apple Pay®, and Apple VAS. DynaFlex II communicates with host devices via USB or wireless local area network (WLAN) on pin entry devices (PED). DynaFlex II products are compatible with iOS, Android, and Windows operating systems.
In this document, DynaFlex II products are referred to as the device or inclusively as DynaFlex II products. They are designed to be connected to a host, which is a piece of general-purpose electronic equipment which sends commands and data to, and receives data from, the device. Host types include PC and Mac computers/laptops, tablets, and smartphones. The host must have software installed that communicates with the device and is capable of processing transactions. During a transaction, the host and its software interact with the operator, such as a customer service representative, while the device interacts with the cardholder (even if the cardholder is using a virtual representation of the card account, such as a smartphone).
Throughout this document:
DynaFlex II Product Family refers to all devices in the DynaFlex II family, including all DynaFlex II models and DynaFlex II PED models.
DynaProx and DynaProx BCR deliver the next generation in touchless payment acceptance. Both models come standard with contactless EMV and near field communication (NFC) technology for original equipment manufacturers (OEM), merchants, banks, and other developers looking to build a secure payment solution that accepts contactless EMV and NFC payments. Ideal for kiosks, vending machines, unattended payment terminals, and even countertop deployment with the optional stand, touchless payment and barcode scanning are made fast, reliable, and secure.
DynaProx and DynaProx BCR are equipped with the next generation of security and the MagneSafe® Security Architecture (MSA). The design and architecture meet the requirements for contactless EMV 3.0, PCI PTS POI v6.1, and support triple DEA encryption with DUKPT Key Management.
DynaProx and DynaProx BCR are easy to install and configure, with key features that include:
Contactless EMV 3.0 approved.
DynaFlex II Go and DynaFlex II Go with Barcode Reader (BCR) deliver the next generation of mobile payment solutions. Both models offer an integrated secure card reader authenticator for magnetic stripe cards, EMV chip cards (contact and contactless), and NFC enabled mobile wallets including Samsung Pay, Google Pay™ with support for Google VAS, and Apple Pay® with support for Apple VAS. Ideal for cafés, restaurants, boutiques, airlines, retail banks and other developers looking to build a secure payment solution that accepts contactless EMV and NFC payments. DynaFlex II Go is suited for deployment in many scenarios, including mobile handsets, tablets, and desktop computers.
DynaFlex II Go and DynaFlex II Go BCR are equipped with MagneSafe® Security Architecture (MSA). The design and architecture meet the requirements for contactless EMV 3.1, PCI PTS POI v6.2, and support triple DEA encryption with DUKPT Key Management.
DynaFlex II Go and DynaFlex II Go BCR are easy to install and configure, with key features that include:
Contactless EMV 3.1 Approved.
The operator initiates a transaction from the host, and the cardholder interacts with the device. Transaction types may include retail transactions, new accounts, teller window applications, checking, savings, mortgages, and any other type of transaction where there is interaction between the cardholder and the operator.
For each transaction type, the host software directs the cardholder. The transaction flow on the device may differ depending on what the host software specifies and what the cardholder does. Section 7.9 Card Reading provides examples of the cardholder experience for each type of payment. If the device cannot read payment data, the host software may require the cardholder to repeat the action or require the host to reject the transaction.
All DynaFlex II Go devices have a single physical button, see Figure 6-1 - Power Button. Pressing and holding this button can activate extra functions. To active a specific function, press and hold the button until a specific number of beeps are heard. Table 6-1 - Button Functions contains functions that can be activated. Beep counts that are not listed are not supported.
Barcode symbology refers to the way in which data is encoded in a barcode. It uses either spaced lines, dots, or squares. When read, these symbols are decoded and converted to data. The table below lists all of the supported symbologies and which are enabled by default.
800 mA recommended
2
5V
3
TXD
output of DynaProx
4
RXD
input to DynaProx
5
GND
6
GND
DynaProx
Comment
PIN/WIRE
SIGNAL
1
















5V
Aztec
Enabled
Codabar
Enabled
Code 11
Disabled
Code128
Enabled
Code 32
Disabled
Code 39
Enabled
Code 93
Disabled
Data Matrix
Enabled
EAN-8
Enabled
EAN-13
Enabled
Febraban
Disabled
GSI-128 (UCC/EAN-128)
Enabled
GS1 Databar (RSS)
Disabled
Industrial 25
Disable
Interleaved 2 of 5,
Enabled
ISSN
Disabled
ISBN
Disabled
ITF-14
Disabled
ITF-6
Disabled
Matrix 2 of 5
Enabled
Micro QR
Disabled
MSI Plessey
Disabled
PDF417
Enabled
Plessey
Disabled
QR Code
Enabled
Standard 25
Disabled
UPC-E
Enabled
UPC-A
Enabled
Symbology
Default
AIM 128
Disabled
DynaFlex II PED refers to DynaFlex II PED products with a display, including those with a kiosk back cover and barcode reader.
DynaFlex II refers to DynaFlex II devices that are not equipped with a touchscreen display, including those with a kiosk back cover and barcode reader.
DynaFlex II products can be paired with Magensa Services to make the certification cycle easier and remove unencrypted data from the payment environment. A service representative will collaborate with you to determine what service best for you.
For faster development, use MagneFlex Prism, a suite of interface tools for browser and middleware applications that streamline the development process. Instead of creating multiple interfaces for the hardware device, POS application, and gateway, you can use MagneFlex. It drives the hardware, interfaces with the POS app, and handles data processing commands.
Part No.
Description
Display
Connection(s)
21078307
DYNAFLEX II, PCI, BLACK, USB
None
USB-C
Part #
Description
Accessory Notes
1000006016
CABLE, USB A - C, 6FT, DYNAFLEX
Included with DynaFlex products
1000006017
The major components of the DynaFlex II product family are detailed in this section. For models without a touchscreen display (DynaFlex II and DynaFlex II Kiosk), the components are identical however, the touchscreen and its bezel are replaced with a faceplate displaying the contactless indicator logo at the optimal contactless landing zone (see Figure 1-1).
Figure 1-1 - DynaFlex II Major components
DynaFlex II PED models without a barcode reader are also identical however, the edge incorporating the barcode reader is a single straight line and there is no QR code marking on the face of the device (see Figure 1-2).
Figure 1-2 - DynaFlex II PED BCR Major Components
Figure 1-3 illustrates the major components of the optional charging station. Note, the charging station is only compatible with non-kiosk models of the device.
Figure 1-3 - Charging Station Major Components
Optical reading for many 2D and 1D barcodes including PayPal and Venmo (DynaProx BCR model required).
Transducer for audio alerts.
User configurable audio commands to play a sequence of tones.
USB (USB-C) or RS-232 interface
Triple DEA encryption / DUKPT key management.
Impact protection - IK 08.
Ingress protection - IP 66.
Apple Pay® / Apple Wallet® (Apple VAS protocol support).
NFC Compatibility: Smart cards and contactless IC products, including MIFARE Classic / MIFARE DESFire /MIFARE Plus cards, with the ability to send pass-through commands.
Optional countertop stand.
Hard mounting points to match common kiosk and ATM bezel mounts.
Flexible cable management.
Touchless payments are fast, convenient, and meet the needs of new growing markets. Major banks and card issuers are investing in contactless EMV cards and other barcodes. Combined with the rise of mobile wallets like Apple Pay, Samsung Pay, Google Pay, and others, there are major opportunities to deliver a reliable and affordable contactless EMV, NFC, and barcode reading device that is used in a variety of deployment scenarios.
Designed to simplify development efforts, DynaProx and DynaProx BCR are available with either a USB or RS-232 interface (with power provided over USB or separately powered for RS-232) and are compatible with Windows and Android applications. The beeper provides auditory feedback to cardholders and operators delivering a more universal appeal. Contact a representative to find the best fit for your application and to request the software developer kits (SDKs) and application programming interfaces (APIs).
Figure 1-1 shows the major components of DynaProx with barcode reader. Models without a barcode reader are identical to the diagram, but do not have a camera and do not have a QR code printed on the front face.
Figure 1-1 - DynaProx Major Components
Part No.
Description
Display
Connection(s)
Notes
21078013
DYNAPROX, PCI, BLACK, USB AND RS-232
None
Part #
Description
Accessory Notes
1000007268
CABLE, USB-C 90° RIGHT ANGLE TO USB TYPE A MALE USB 2.0, 6FT
Included with DynaProx products
1000005076
In this document, DynaProx products are referred to as the device. They are designed to be connected to a host, which is a piece of general-purpose electronic equipment which can send commands and data to, and receive data from, the device. Host types include PC and Mac computers/laptops, tablets, and smartphones. Generally, the host must have software installed that communicates with the device and is capable of processing transactions. During a transaction, the host and its software interact with the operator, such as a customer service representative, while the device interacts with the cardholder (even if the cardholder is using a virtual representation of the card account, such as a smartphone).
PCI PTS POI v6.2 Approved.
Optical reading for many 2D and 1D barcodes including PayPal and Venmo (DynaFlex II Go BCR Model Only).
Transducer for audio alerts.
User configurable audio commands to play a sequence of tones.
Bluetooth® Low Energy (LE).
USB-C interface.
iAP2® Protocol Support.
Triple DEA encryption / DUKPT key management.
AES-128 and AES-256 encryption.
Ingress protection - IP 30.
Apple Pay® / Apple Wallet® (Apple VAS protocol support).
Google Wallet Smart Tap. (Google VAS protocol support).
Google Pay™.
NFC Compatibility: Smart cards and contactless IC products, including MIFARE Classic / MIFARE DESFire /MIFARE Plus cards, with the ability to send pass-through commands.
Optional OtterBox® uniVERSE® case.
Optional countertop stand.
Figure 1-1 illustrates the major components of DynaFlex II Go (BCR model shown). Models without a barcode reader are identical to the illustration, but do not have a camera and do not have a QR code printed on the front face.
Figure - DynaFlex II Go Major Components
Part No.
Description
Display
Connection(s)
Operating Systems
21078400
DynaFlex II Go, PCI, BCR, BLACK, BLUETOOTH LE
None
Part #
Description
Accessory Notes
1000005076
CABLE, USB-C TO USB TYPE A MALE USB 2.0, 20AWG
Optional, specify in order
1000006016
In this document, DynaFlex II Go products are referred to as the device. They are designed to be connected to a host, which is a piece of general-purpose electronic equipment that can send commands and data to, and receive data from, the device. Host types include PC and Mac computers/laptops, tablets, and smartphones. Generally, the host must have software installed that communicates with the device and is capable of processing transactions. During a transaction, the host and its software interact with the operator, such as a customer service representative, while the device interacts with the cardholder (even if the cardholder is using a virtual representation of the card account, such as a smartphone).
Function
2
Power Off
Hold for two beeps to power the device off. The device will reboot if it is connected to USB when powered off.
3
Settings Menu
SoftAP Mode in the Settings Menu is Available on WLAN enabled devices only.
4
BLE Pairing
BLE Enabled devices only.
5
Demo
See Appendix C for more information.
6
Battery Level
Light the LEDs to indicate the current state of charge of the battery. The LEDs will light for 3 seconds then return to their original state.
See table bvelow for LED indicators
DynaFlex II Go has only green LEDs. Instead of lighting the first LED in amber, it will slowly flash the first LED. Instead of Red, the first LED will flash quickly.
During operation, DynaFlex II Go devices transition between distinct operating modes, which are important for operators to understand:
Powered Off Mode is the shipping and storage mode of the device. No external power is applied to the device through the USB cable or from the internal rechargeable battery. In this mode, the device consumes very little power. To set the device from Powered Off mode to Active Mode, connect the device to USB power, or press the power button, see Figure 6-1 - Power Button .
Active Mode is the device’s normal “awake” state when it is in use. In this mode, the device LED indicators are powered on, and the device is ready to receive commands from the host. For more information on Status LEDs and LED behavior see sections 7.4 About the Status LEDs, 7.5 Bluetooth® Low Energy (LE) LED Behavior, 7.5.7 DynaFlex II Go Bluetooth® Low Energy (LE) Sleep Mode
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
LED Behavior: Successful Transactions, and 7.7 LED Behavior: Errors, Timeouts, and Canceled Transactions. To set the device from Active mode to Powered Off mode remove power press and hold the power button for two beeps.
BLE Sleep Mode is a standard feature that conserves battery life by limiting power to non-essential hardware features. When in Sleep Mode, the device will appear to be powered off, with no LEDs illuminated, see 7.5.7 DynaFlex II Go Bluetooth® Low Energy (LE) Sleep Mode, for more information on BLE Sleep Mode.
DynaFlex II Go products have a beeper 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 two beeps when reading a card or contactless payment device to indicate a card read error 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. If the device is too quiet or too loud:
Make sure the device is being 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 D998200597 DynaFlex II Go Programmer’s Manual (COMMANDS).
To play a sequence of tones, follow these steps:
Make sure the device is in idle state.
Send an audio command to the device to play a sequence of tones. For details, see D998200597 DynaFlex II Go Programmer’s Manual (COMMANDS).

Beep Count
The front view of iDynamo 5 Gen III, is shown in Figure 2-1 below. The back view of iDynamo 5 Gen III is shown in Figure 2-2. The side views of iDynamo 5 Gen III can be seen in Figure 2-3 and Figure 2-4. The Top View displaying the pushbutton and LED indicator can be seen in Figure 2-5, and the Bottom View displaying the USB-C receptacle can be seen in Figure 2-6.
Figure 2-1 - Front View
Figure 2-2 - Back View
Figure 2-3 - Left Side View
Figure 2-4 - Right Side view
Figure 2-5 - Top View
Custom host software uses the same underlying device command set for all DynaFlex II Go product connection types. This section provides high-level information about communicating with the device via the various physical connection types in various software development frameworks, and provides pointers to available SDKs, which include sample code. Product documentation and SDKs are available for download by searching for the product name on and navigating to the tab.
MagTek provides convenient SDKs and corresponding documentation for many programming languages and operating systems. The API libraries included in the SDKs wrap the details of the connection in an interface that conceptually parallels the device’s internal operation, freeing software developers to focus on the business logic, without having to deal with the complexities of platform APIs for connecting to the various available connection types, communicating using the various available protocols, and parsing the various available data formats. Information about using MagTek wrapper APIs is available in separate documentation, including:
D998200380 MagTek Universal SDK Programmer’s Manual (Microsoft .NET)
D998200381 MagTek Universal SDK Programmer’s Manual (Microsoft C++ )
D998200385 MagTek Universal SDK for MMS Devices Programmer’s Manual (Java)
D998200386 MagTek Universal SDK for MMS Devices Programmer’s Manual (iOS)
D998200387 MagTek Universal SDK Programmer’s Manual (Android)
The documentation is bundled with the SDKs themselves, which include:
· 1000007351 MagTek Universal SDK for MMS Devices (Windows)
· 1000007352 MagTek Universal SDK for MMS Devices (Android)
The SDKs and corresponding documentation include:
Functions for sending the direct commands described in this manual
Wrappers for commonly used commands that further simplify development
Sample source code to demonstrate how to communicate with the device using the direct commands described in this manual
To download the SDKs and documentation, search www.magtek.com for “SDK” and select the SDK and documentation for the programming languages and platforms you need or contact MagTek Support Services for assistance.
In addition to the SDK API libraries, software developers also have the option to revert to direct communication with the device using libraries using the operating system’s native USB and serial port libraries. For example, custom software written in Visual Basic or Visual C++ may make API calls to the standard Windows USB HID driver. For more information about sending commands directly, see D998200597 DynaFlex II Go Programmer’s Manual (COMMANDS).
For more information about developing custom applications that integrate with DynaFlex II Go, see the MagTek web site or contact your reseller or MagTek Support Services.
21078309
DYNAFLEX II PED, PCI, TOUCHSCREEN DISPLAY, BLACK, USB
Touchscreen
USB-C
21078311
DYNAFLEX II PED, PCI, TOUCHSCREEN DISPLAY, BLACK, WLAN
Touchscreen
USB-C
Wireless LAN
21078314
DYNAFLEX II KIOSK, PCI, BCR, BLACK, USB
None
USB-C
21078321
DYNAFLEX II PED, KIOSK, PCI, TOUCHSCREEN DISPLAY, BLACK, USB
Touchscreen
USB-C
21078322
DYNAFLEX II, KIOSK, PCI, BLACK, USB
None
USB-C
21078325
DYNAFLEX II PED, KIOSK, PCI, TOUCHSCREEN DISPLAY, BLACK, WLAN
Touchscreen
USB-C
Wireless LAN
21078331
DYNAFLEX II, PCI, BCR, BLACK, USB
None
USB-C
21078332
DYNAFLEX II PED, PCI, TOUCHSCREEN DISPLAY, BCR, BLACK, WLAN
Touchscreen
USB-C
Wireless LAN
21078333
DYNAFLEX II PED, PCI, TOUCHSCREEN DISPLAY, BCR, BLACK, USB
Touchscreen
USB-C
21078334
DYNAFLEX II PED, KIOSK, PCI, TOUCHSCREEN DISPLAY, BCR, BLACK, USB
Touchscreen
USB-C
All models are black by default and have countertop, handheld, and custom mounting options.
CABLE, USB C - C, 6FT, DYNAFLEX
Optional, specify in order
21078006
CHARGING STATION, DYNAFLEX
Optional, specify in order
96700004
CLEANING CARD, DOUBLE SIDED
Optional, specify in order
1000008559
FOOT, BACK, SIDE A, ADHESIVE MOUNTING STRIP, DYNAFLEX
Optional, specify 1 ea. for complete replacement
1000008560
FOOT, BACK, SIDE B, ADHESIVE MOUNTING STRIP, DYNAFLEX
Optional, specify 1 ea. for complete replacement
1000008561
FOOT, FRONT, ADHESIVE MOUNTING STRIP, DYNAFLEX
Optional, specify 1 ea. For complete replacement



USB-C, RS-232
MS Windows, Mac OS, Linux; Android Phone
21078028
DYNAPROX, PCI, BCR, BLACK, USB AND RS-232
None
USB-C, RS-232
MS Windows, Mac OS, Linux; Android Phone
21078043
DYNAPROX, PCI, BLACK, USB AND RS-232, COUNTERTOP STAND
None
USB-C, RS-232
MS Windows, Mac OS, Linux; Android Phone
21078044
DYNAPROX, PCI, BCR, BLACK, USB AND RS-232, COUNTERTOP STAND
None
USB-C, RS-232
MS Windows, Mac OS, Linux; Android Phone
CABLE, USB-C 90° RIGHT ANGLE TO USB TYPE A MALE USB 2.0, 3FT
Optional, specify in order
21078012
DYNAPROX, KIT COUNTERTOP STAND
Kit only
1000007189
DynaProx Gasket
One (1) included with each DynaProx products. Replacement gaskets specify in order.
21078077
RS-232 Cable for Development use
Intended for development use only to connect to the RS-232 Port

USB-C, Bluetooth® (LE), iAP2®
MS Windows, Mac OS, Linux; Android Phone
21078401
DynaFlex II Go, PCI, BLACK, BLUETOOTH LE
None
USB-C, Bluetooth® (LE), iAP2®
MS Windows, Mac OS, Linux; Android Phone
21078402
DynaFlex II Go, PCI, BCR, BLACK
None
USB-C, iAP2®
MS Windows, Mac OS, Linux; Android Phone
21078403
DynaFlex II Go, PCI, BLACK
None
USB-C, iAP2®
MS Windows, Mac OS, Linux; Android Phone
21078404
DynaFlex II Go, PCI, BCR, BLACK, BLUETOOTH LE, LOCKED MAGENSA BUNDLE LMB
None
USB-C, Bluetooth® (LE), iAP2®
MS Windows, Mac OS, Linux; Android Phone
21078405
DynaFlex II Go, PCI, BLACK, BLUETOOTH LE, LOCKED MAGENSA BUNDLE LMB
None
USB-C, Bluetooth® (LE), iAP2®
MS Windows, Mac OS, Linux; Android Phone
21078406
DynaFlex II Go, PCI, BCR, BLACK, LOCKED MAGENSA BUNDLE LMB
None
USB-C, iAP2®
MS Windows, Mac OS, Linux; Android Phone
21078407
DynaFlex II Go, PCI, BLACK, LOCKED MAGENSA BUNDLE LMB
None
USB-C, iAP2®
MS Windows, Mac OS, Linux; Android Phone
USB CABLE TYPE A – C, 6FT
Optional, specify in order
1000006017
USB CABLE TYPE C, 6FT
Optional, specify in order
21078408
DYNAFLEX II GO, KIT COUNTERTOP STAND
Refer to Appendix C Optional Accessories for additional information.
21078409
DYNAFLEX II GO ADAPTOR FOR OTTERBOX
Refer to Appendix C Optional Accessories for additional information.
21078410
DYNAFLEX II GO RUBBER SLEEVE
Refer to Appendix C Optional Accessories for additional information.
21078411
DYNAFLEX II GO RUBBER SLEEVE HALF SIZE
Refer to Appendix C Optional Accessories for additional information.
Note: At least one cable will be shipped with the device, specify when ordering.



CTLS
Contactless
DES
Data Encryption Standard
DUKPT
Derived Unique Key Per Transaction
ECC
Elliptic-Curve Cryptography
FSK
Firmware Signing Key
ICCR
Integrated Circuit Card Reader
MAC
In cryptography: Message Authentication Code In networking: Media Access Control [address]
MSR
Magnetic Stripe Reader
NFC
Near Field Communication
POI
Point Of Interaction
S/N
Serial Number
SCRA
Secure Card Reader Authenticator
SHA
Secure Hash Algorithm
SRED
Secure Reading and Exchange of Data
TDEA
Triple Data Encryption Algorithm
USB
Universal Serial Bus
USB HID
USB Human Interface Device
Acronym
Definition
AES
Advanced Encryption Standard
BCR
Barcode Reader
Figure 2-6 - Bottom View
iDynamo 5 Gen III devices include a USB-C interface for Power and Communications, and a magnetic stripe reader (MSR). It is designed for attended and unattended environments.
iDynamo 5 Gen III can be used as a desktop or handheld device. It is approved as a secure card reader (SCR) under PCI PTS POI v6.2 requirements.
Usage in any other environment will invalidate PCI approval.
To find important product identification information, look for the printed product label on the back face of the device as shown in Figure 2-7 below.
Figure 2-7 – iDynamo 5 Gen III Device Label Location
The product label includes the following elements of device identification information, shown by the numbered callouts in Figure 2-8.
Product Name
PCI Hardware Identifier (“HW”)
Figure 2-8 -iDynamo 5 Gen III Device Label
The label also contains other supporting information about the device.
The hardware version of the device is 10PCI50U0xAx . All iDynamo 5 Gen III hardware configurations are listed in Table 2-1 below. The device utilizes one interface type, USB-C. Use of any interface otherthan USB-C will invalidate PCI approval.
PCI ID Tag
Configuration Description
10PCI50U0BA0
iDynamo 5 Gen III, PCI, BLACK
PCI Hardware ID Number
1
2
3
4
5
8
Fixed Position
Variable "X" Position
Description of Fixed or Variable “X” in the Selection Position
1-2
10 = iDynamo 5 Gen III
3-5
The most recent firmware versions for iDynamo 5 Gen III products are 1000009547-AAx-PCI for the secure bootloader, and 1000009535-AAx-PCI for the main firmware. The lowercase x in firmware versions indicates minor non-security related changes, see Table 2-3 and Table 2-4.
Firmware Number
1
2
3
4
5
8
Fixed Position
Variable “x” Position
Description of Fixed or Variable “x” in the Selected Position
1-10
1000009535 = iDynamo 5 Gen III Main Firmware Part Number
11
Firmware Number
1
2
3
4
5
8
Fixed Position
Variable “x” Position
Description of Fixed or Variable “x” in the Selected Position
1-10
1000009547 = iDynamo 5 Gen III Boot Firmware Part Number
11
All device identification information, including firmware versions and PCI Hardware ID, is accessible by connecting iDynamo 5 Gen III to a host device via USB-C using the latest software provided by MagTek, as seen in Figure 2-9 - Device Information Screen.
The host user can retrieve device information at any time using Command 0x0000 Get Property as described in [3].
Figure 2-9 - Device Information Screen





The device always encrypts account data from the MSR using 112-bit TDEA, 128-bit AES, or 256-bit AES algorithms with X9.24 DUKPT key management. This device does not support any mechanisms such as whitelists or SRED disable that would allow the data to be sent out unencrypted. The programmers need to follow the guidance provided in [3]. Use of the device with key-management systems not described in this policy will invalidate the PCI PTS POI v6.2 approval of the device.
The device includes the following cryptographic algorithms:
AES-128/256
TDEA-128
x
A
A
x
-
P
C
I
A
A
x
-
P
C
I
10
11
12
1
0
P
C
I
U
x
PCI = PCI Hardware
6
Device Options 5 = Standard
7
Option RFU (Reserved for Future Use) RFU 0 = as Certified
8
Interface Options U = USB
9
Option RFU (Reserved for Future Use) RFU 0 = as Certified
11
10
Cover Color: B = Black
11
Version A = as Certified
11
12
minor fixes not adding functionality or related to security (e.g., change component value for antenna matching): 0 = as certified
10
11
12
13
14
15
16
17
18
1
0
0
0
0
5
5
Delimiter (-)
12-13
AA = Certified Version
14
Minor Revisions, Bug Fixes
15
Delimiter (-)
16-18
PCI = PCI Version of Firmware
10
11
12
13
14
15
16
17
18
1
0
0
0
0
5
5
Delimiter (-)
12-13
AA = Certified Version
14
Minor Revisions, Bug Fixes
15
Delimiter (-)
16-18
PCI = PCI Version of Firmware





A
-
-
The device does not have an on-screen configuration interface. However, it does have settings the host can change using commands. These settings are documented as Properties in D998200597 DynaFlex II Go Programmer’s Manual (COMMANDS).
RSA2048
SHA-256
The device implements the original AES/TDEA DUKPT as its only key management method. Use of any other method will invalidate PCI approval. DUKPT derives a new unique key for every transaction. For more details, see [5] and [6].
Key Name
Size
Algorithm
Purpose
Transport Keys:
· Master Transport Key
· Device Transport Key
· Financial Transport Key
· Production Transport Key
· Manufacturing Transport Key
· MagTek KIF Financial Transport Key
32 bytes
AES X9.143 KBPKs
Key Injection
The device does not support manual or plaintext cryptographic key entry. Only specialized tools, compliant with key management requirements and cryptographic methods, specifically [6] and [7]. On the production line, the ANSI X9.143 format can be used for key loading by an HSM after mutual authentication. Use of any other methods will invalidate PCI approval.
Keys should be replaced with new keys whenever the original key is known or suspected to have been compromised, and whenever the time deemed feasible to determine the key by exhaustive attack has elapsed, as defined in [4].
After receiving the device, the customer should visually inspect the product as follows:
Inspect the label found on the bottom of the device (see section 2.3.1 Hardware Identification) and make sure the label is not missing, obscured, or modified.
Check the PCI Hardware Identifier on the device label and make sure it matches the Hardware # listed for the device on the PCI web site for Approved Devices. Go to the PCI compliance web page and search for MagTek, and find the product name, DynaFlex II Go. Compare the Hardware ID and Firmware ID: https://www.pcisecuritystandards.org/assessors_and_solutions/pin_transaction_devices
Check the Device serial number (SN) and make sure it matches with labels on shipping materials and documentation.
Visually inspect the device, per D998200593 DynaFlex II Go, Device Inspection Document, which is included in the package with each device. See section 4.1 Periodic Inspection for more information regarding visual inspection of the device.
Follow the steps in section 2.3.2 to view the PCI firmware versions installed on the device. Make sure this matches one of the Firmware # values listed on the PCI web site for DynaFlex II Go. Note that in PCI listings, lowercase “x” is a wildcard meaning ‘any single character.’
Connect the device to a USB host for control and power (if battery power is not sufficient). DynaFlex II Go products are designed to provide flexible mounting options such as:
External clip
Embedded lanyard
The specified environmental conditions to operate and store the device are:
Operating temperature range: 0°C to 35°C / 5% to 90% RH
Storage temperature range: -20°C to 45°C / 5% to 90% RH
For safety, battery charging is disabled when the device is outside the recommended operating temperature range.
The security of the reader is not compromised by altering the environmental conditions outside the stated operating ranges above. Any temperature or operating voltage outside the values in the table below will trigger environmental security protections, resulting in a tamper condition. The device will need to be returned to the factory for inspection before this condition can be cleared.
DynaFlex II Go products support a USB interface using the USB-HID protocol, and a Bluetooth LE interface. Transactions, configuration, firmware updates, and key injection can all be performed using these interface types. Use of any method not listed in this security policy will invalidate the device’s PCI PTS approval.
The device requires Bluetooth LE hosts to use version 4.2 or higher and use LE Security Mode 1 Level 4 (Secure Connections) only. “Just Works” cannot be used at any time. The device does not support or allow for the use of insecure communication options such as, but not limited to, LE Security Mode 2, and levels 1, 2, and 3 of LE Security Mode 1 and the “Just Works” secure pairing option of Security Mode 1.
DynaFlex II Go products ship from the factory fully secure. The devices have no configuration settings that require modification by the user to meet PCI security requirements.
MagTek warrants that the products sold pursuant to this Agreement will perform in accordance with MagTek’s published specifications. This warranty shall be provided only for a period of one year from the date of the shipment of the product from MagTek (the “Warranty Period”). This warranty shall apply only to the “Buyer” (the original purchaser, unless that entity resells the product as authorized by MagTek, in which event this warranty shall apply only to the first repurchaser).
During the Warranty Period, should this product fail to conform to MagTek’s specifications, MagTek will, at its option, repair or replace this product at no additional charge except as set forth below. Repair parts and replacement products will be furnished on an exchange basis and will be either reconditioned or new. All replaced parts and products become the property of MagTek. This limited warranty does not include service to repair damage to the product resulting from accident, disaster, unreasonable use, misuse, abuse, negligence, or modification of the product not authorized by MagTek. MagTek reserves the right to examine the alleged defective goods to determine whether the warranty is applicable.
Without limiting the generality of the foregoing, MagTek specifically disclaims any liability or warranty for goods resold in other than MagTek’s original packages, and for goods modified, altered, or treated without authorization by MagTek.
Service may be obtained by delivering the product during the warranty period to MagTek (1710 Apollo Court, Seal Beach, CA 90740). If this product is delivered by mail or by an equivalent shipping carrier, the customer agrees to insure the product or assume the risk of loss or damage in transit, to prepay shipping charges to the warranty service location, and to use the original shipping container or equivalent. MagTek will return the product, prepaid, via a three (3) day shipping service. A Return Material Authorization (“RMA”) number must accompany all returns. Buyers may obtain an RMA number by contacting MagTek Support Services at (562) 546-6800.
Upon receiving the device, inspect it to make sure it originated from an authentic source and has not been tampered with. For details, see D998200593 DynaFlex II Go Device Inspection Document, available from MagTek.
From device delivery through assembly, shipping, installation, usage, and maintenance, the device must not be exposed to conditions outside the ratings in Appendix A Technical Specifications.
If the device is exposed to cold temperatures, adjust it to warmer temperatures gradually to avoid condensation, which can interfere with the operation of the device or cause permanent damage. Do not drop or shake the device.
For information about ongoing maintenance of the device, such as cleaning, see section 8 Maintenance.
DynaFlex II Go products implement active tamper detection, which uses a small amount of electricity even when the device is completely powered off. When unpowered by an external power supply, the device powers its active tamper detection circuitry using its non-rechargeable internal backup battery. This provides 5 years of backup shelf life across the entire life of the device. If the backup battery is allowed to completely discharge, the device’s tamper detection engages and locks down the device, and it must be returned to the manufacturer to reset.
To avoid accidental tamper events and to optimally condition the battery, follow these precautions:
Periodic cleaning of the device’s exterior may be required. To clean the outside of DynaProx products, wipe down the device with a soft, slightly damp cloth and then wipe dry with a lint-free cloth. The glass on the face can also be cleaned using a slightly damp specialty cleaning cloth, like those used to wipe lenses, monitors, and smartphone displays.
In addition to the security guidance in the product manuals, MagTek may provide updates to this document, as well as supplemental security guidance or notices regarding vulnerabilities, at MagTek advises checking the product’s home page periodically for the most up-to-date information.
Any firmware updates addressing product features, bugs, or security vulnerabilities are also posted to or may be sent directly to affected customers. To update the device’s firmware:
Obtain the firmware image to install.
2) Download from the MagTek web site.
Before unpacking the device, it is important to inspect its secure packaging to make sure it has not been tampered with in storage or in transit. MagTek provides details for inspecting the integrity of the device’s secure packaging in DynaFlex II PED Package Inspection.
It is important to inspect a new device regularly and thoroughly before deployment and a device in live usage (including its immediate surroundings), to make sure malicious individuals have not tampered with it or its surroundings. MagTek recommends conducting inspection training for all device operators and an inspection schedule with checkpoints in place to make sure operators are performing inspections as specified and as scheduled. MagTek provides easy-to-follow
Upon receiving the device, inspect it to make sure it originated from an authentic source and has not been tampered with.
From device delivery through assembly, shipping, installation, usage, and maintenance, the device must not be exposed to conditions outside the ratings in Appendix A Technical Specifications.
If the device is exposed to cold temperatures, adjust it to warmer temperatures gradually to avoid condensation, which can interfere with the operation of the device or cause permanent damage. Do not drop or shake the device.
For information about ongoing maintenance of the device, such as cleaning, see section 5 Maintenance.
Account Data Key
· DKPTM7-FK
16 bytes for TDEA and AES- 128
32 bytes for AES-256
AES and TDEA DUKPT (ANS X9.24-3)
Encrypt and MAC Account Data
Firmware Protection Key
· Firmware Signing Key (FSK)
256 bytes
RSA2048 and SHA-256
Checks integrity and authenticity of firmware
Temperature is the most critical factor in extending battery life and preserving battery charge. Store the device at the lowest reasonable temperatures within its specified storage temperature range (see Appendix A Technical Specifications). Storing at temperatures between -4°F to 113°F (-20°C to 45°C).
Do not drop or shake the device.
Do not attempt to disassemble the device.
Sensor
Low Threshold Value
High Threshold Value
Internal Voltage
1.60V ± 0.055V
3.775V ± 0.1V
Temperature
-45°C ± 15°C
120°C ± 10°C
However, if the rechargeable battery completely discharges or the device does not contain a rechargeable battery, the device continues to power its active tamper detection circuitry using its non-rechargeable backup battery, which provides an additional 5 years of backup shelf life across the entire life of the device but does not recharge. If the rechargeable battery and the backup battery are both allowed to completely discharge, the device’s tamper detection engages and locks down the device, and it must be returned to the manufacturer to reset.
To avoid accidental tamper events and to optimally condition the battery, follow these precautions:
Temperature is the most critical factor in extending battery life and preserving battery charge. Store the device at the lowest reasonable temperatures within its specified storage temperature range (see Appendix A Technical Specifications). Storing below 77°F / 25°C is optimal.
Fully charge the device immediately upon receipt to extend its shelf life (see section 4.6.3 How to Charge the Battery).
Before storing the device, charge the battery to less than 100% (60% is optimal).
Before storing the device, power it off completely. See section 4.6.4 How to Power On / Wake Up from Standby Mode / Power Off.
When stored, charge the device for one hour every 6 months to keep the battery chemistry in optimal condition and to ensure it does not completely discharge.
Do not drop or shake the device.
This document addresses the proper use of iDynamo 5 Gen III secure card readers (SCR), in a secure manner. This includes information about key-management responsibilities, administrative responsibilities, device functionality, identification, and environmental requirements.
The use of this secure card reader in any method not described in this security policy will invalidate the PCI PTS POI v6.2 approval of the device.
Throughout this document:
iDynamo 5 Gen III refers to all products in the iDynamo 5 Gen III product family.
EACH BUYER UNDERSTANDS THAT THIS MAGTEK PRODUCT IS OFFERED AS-IS. MAGTEK MAKES NO OTHER WARRANTY, EXPRESS OR IMPLIED, AND MAGTEK DISCLAIMS ANY WARRANTY OF ANY OTHER KIND, INCLUDING ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IF THIS PRODUCT DOES NOT CONFORM TO MAGTEK’S SPECIFICATIONS, THE SOLE REMEDY SHALL BE REPAIR OR REPLACEMENT AS PROVIDED ABOVE. MAGTEK’S LIABILITY, IF ANY, SHALL IN NO EVENT EXCEED THE TOTAL AMOUNT PAID TO MAGTEK UNDER THIS AGREEMENT. IN NO EVENT WILL MAGTEK BE LIABLE TO THE BUYER FOR ANY DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS, OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF, OR INABILITY TO USE, SUCH PRODUCT, EVEN IF MAGTEK HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY CLAIM BY ANY OTHER PARTY.
LIMITATION ON LIABILITY
EXCEPT AS PROVIDED IN THE SECTIONS RELATING TO MAGTEK’S LIMITED WARRANTY, MAGTEK’S LIABILITY UNDER THIS AGREEMENT IS LIMITED TO THE CONTRACT PRICE OF THIS PRODUCT.
MAGTEK MAKES NO OTHER WARRANTIES WITH RESPECT TO THE PRODUCT, EXPRESSED OR IMPLIED, EXCEPT AS MAY BE STATED IN THIS AGREEMENT, AND MAGTEK DISCLAIMS ANY IMPLIED WARRANTY, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
MAGTEK SHALL NOT BE LIABLE FOR CONTINGENT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES TO PERSONS OR PROPERTY. MAGTEK FURTHER LIMITS ITS LIABILITY OF ANY KIND WITH RESPECT TO THE PRODUCT, INCLUDING NEGLIGENCE ON ITS PART, TO THE CONTRACT PRICE FOR THE GOODS.
MAGTEK’S SOLE LIABILITY AND BUYER’S EXCLUSIVE REMEDIES ARE STATED IN THIS SECTION AND IN THE SECTION RELATING TO MAGTEK’S LIMITED WARRANTY.
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) This device must accept any interference received, including interference that may cause undesired operation.
Note: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
Reorient or relocate the receiving antenna.
Increase the separation between the equipment and receiver.
Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
Consult the dealer or an experienced radio/TV technician for help.
This digital apparatus does not exceed the Class B limits for radio noise from digital apparatus set out in the Radio Interference Regulations of the Canadian Department of Communications.
Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la classe B prescrites dans le Réglement sur le brouillage radioélectrique édicté par le ministère des Communications du Canada.
This Class B digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe B est conformé à la norme NMB-003 du Canada.
This device complies with Industry Canada licence-exempt RSS standard(s). Operation is subject to the following two conditions: (1) This device may not cause interference, and (2) This device must accept any interference, including interference that may cause undesired operation of the device.
Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorisée aux deux conditions suivantes: (1) L'appareil ne doit pas produire de brouillage, et (2) L'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d'en compromettre le fonctionnement.
This product is recognized per Underwriter Laboratories and Canadian Underwriter Laboratories 1950.
Testing for compliance with CE requirements was performed by an independent laboratory. The unit under test was found compliant with standards established for Class B devices.
Hereby, MagTek Inc. declares that the radio equipment types Wideband Transmission System (802.11 wireless and Bluetooth® Low Energy), and Non-Specific Short Range Device (contactless) are in compliance with Directive 2014/53/EU. The full text of the EU declarations of conformity is available at the following internet addresses:
Hereby, MagTek Inc. declares that the radio equipment types Wideband Transmission System (802.11 wireless and Bluetooth® Low Energy), and Non-Specific Short Range Device (contactless) are in compliance with Directive 2014/53/EU. The full text of the EU declarations of conformity is available at the following internet address:
Testing for compliance with AS/NZS standards was performed by a registered and accredited laboratory. Per Subclause 53(4) of Part 15 of Schedule 5 to the General Equipment Rules, DynaFlex II GO meets the requirements of the Short-Range Equipment Standard as tested in EN 300 330 V2.1.1 (2017-02). The AS declaration of conformity is available at the following internet address:
When ordered as RoHS compliant, this product meets the Electrical and Electronic Equipment (EEE) Reduction of Hazardous Substances (RoHS) Directive (EU) 2015/863 amending Annex II to Directive 2011/65/EU. The marking is clearly recognizable, either as written words like “Pb-free,” “lead-free,” or as another clear symbol ( ).
PCI Security Standards Council, LLC (“PCI SSC”) has approved this PIN Transaction Security Device to be in compliance with PCI SSC’s PIN Security Requirements.
When granted, PCI SSC approval is provided by PCI SSC to ensure certain security and operational characteristics important to the achievement of PCI SSC’s goals, but PCI SSC approval does not under any circumstances include any endorsement or warranty regarding the functionality, quality or performance of any particular product or service. PCI SSC does not warrant any products or services provided by third parties. PCI SSC approval does not under any circumstances include or imply any product warranties from PCI SSC, including, without limitation, any implied warranties of merchantability, fitness for purpose, or non-infringement, all of which are expressly disclaimed by PCI SSC. All rights and remedies regarding products and services which have received PCI SSC approval shall be provided by the party providing such products or services, and not by PCI SSC.
This product has been tested to IEC 62368-1 -Audio/Video, information and communication technology equipment - Part 1: General Requirements and U.S. (UL 62368-1), Canadian, Australian & New Zealand National Deviations by an ISO 17025 Accredited Testing Laboratory.
This document is written specifically to work in conjunction with these safety and integrity features to protect the user and the device. It is very important to follow all steps in the product documentation carefully, in the order in which they are described, and at the recommended times. Failure to do so could result in personal injury, and / or cause damage to the device, and / or void the product warranty.
IMPORTANT: YOU SHOULD CAREFULLY READ ALL THE TERMS, CONDITIONS AND RESTRICTIONS OF THIS LICENSE AGREEMENT BEFORE INSTALLING THE SOFTWARE PACKAGE. YOUR INSTALLATION OF THE SOFTWARE PACKAGE PRESUMES YOUR ACCEPTANCE OF THE TERMS, CONDITIONS, AND RESTRICTIONS CONTAINED IN THIS AGREEMENT. IF YOU DO NOT AGREE WITH THESE TERMS, CONDITIONS, AND RESTRICTIONS, PROMPTLY RETURN THE SOFTWARE PACKAGE AND ASSOCIATED DOCUMENTATION TO THE ADDRESS IN THIS DOCUMENT, ATTENTION: CUSTOMER SUPPORT.
TERMS, CONDITIONS, AND RESTRICTIONS
MagTek, Incorporated (the "Licensor") owns and has the right to distribute the described software and documentation, collectively referred to as the "Software."
LICENSE: Licensor grants you (the "Licensee") the right to use the Software in conjunction with MagTek products. LICENSEE MAY NOT COPY, MODIFY, OR TRANSFER THE SOFTWARE IN WHOLE OR IN PART EXCEPT AS EXPRESSLY PROVIDED IN THIS AGREEMENT. Licensee
may not decompile, disassemble, or in any other manner attempt to reverse engineer the Software. Licensee shall not tamper with, bypass, or alter any security features of the software or attempt to do so.
TRANSFER: Licensee may not transfer the Software or license to the Software to another party without the prior written authorization of the Licensor. If Licensee transfers the Software without authorization, all rights granted under this Agreement are automatically terminated.
COPYRIGHT: The Software is copyrighted. Licensee may not copy the Software except for archival purposes or to load for execution purposes. All other copies of the Software are in violation of this Agreement.
TERM: This Agreement is in effect as long as Licensee continues the use of the Software. The Licensor also reserves the right to terminate this Agreement if Licensee fails to comply with any of the terms, conditions, or restrictions contained herein. Should Licensor terminate this Agreement due to Licensee's failure to comply, Licensee agrees to return the Software to Licensor. Receipt of returned Software by the Licensor shall mark the termination.
LIMITED WARRANTY: Licensor warrants to the Licensee that the disk(s) or other media on which the Software is recorded are free from defects in material or workmanship under normal use.
THE SOFTWARE IS PROVIDED AS IS. LICENSOR MAKES NO OTHER WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Because of the diversity of conditions and hardware under which the Software may be used, Licensor does not warrant that the Software will meet Licensee specifications or that the operation of the Software will be uninterrupted or free of errors.
IN NO EVENT WILL LICENSOR BE LIABLE FOR ANY DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS, OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE, OR INABILITY TO USE THE SOFTWARE. Licensee's sole remedy in
the event of a defect in material or workmanship is expressly limited to replacement of the Software disk(s) if applicable.
GOVERNING LAW: If any provision of this Agreement is found to be unlawful, void, or unenforceable, that provision shall be removed from consideration under this Agreement and will not affect the enforceability of any of the remaining provisions. This Agreement shall be governed by the laws of the State of California and shall inure to the benefit of MagTek, Incorporated, its successors or assigns.
ACKNOWLEDGMENT: LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS ALL OF ITS TERMS, CONDITIONS, AND RESTRICTIONS, AND AGREES TO BE BOUND BY THEM. LICENSEE ALSO AGREES THAT THIS AGREEMENT SUPERSEDES ANY AND ALL VERBAL AND WRITTEN COMMUNICATIONS BETWEEN LICENSOR AND LICENSEE OR THEIR ASSIGNS RELATING TO THE SUBJECT MATTER OF THIS AGREEMENT.
QUESTIONS REGARDING THIS AGREEMENT SHOULD BE ADDRESSED IN WRITING TO MAGTEK, INCORPORATED, ATTENTION: CUSTOMER SUPPORT, AT THE ADDRESS LISTED IN THIS DOCUMENT, OR E-MAILED TO SUPPORT@MAGTEK.COM.
DEMO SOFTWARE / SAMPLE CODE: Unless otherwise stated, all demo software and sample code are to be used by Licensee for demonstration purposes only and MAY NOT BE incorporated into any production or live environment. The PIN Pad sample implementation is for software PIN Pad test purposes only and is not PCI compliant. To meet PCI compliance in production or live environments, a third-party PCI compliant component (hardware or software-based) must be used.
Brochures
Description
DynaFlex II PED products are ready to launch your payment, banking, and access environment to the next level. DynaFlex II PED devices deliver a smart solution with great flexibility, in a small form factor.
This comprehensive catalog introduces MagTek as a leading manufacturer of secure electronic systems, including card readers, encrypting check scanners, PIN pads, and credential personalization systems.
This document addresses the proper use of the DynaFlex II Go family of secure card readers (SCR) in a secure manner. This includes information about key-management responsibilities, administrative responsibilities, device functionality, identification, and environmental requirements.
The use of this secure card reader in any method not described in this security policy will invalidate the PCI PTS POI v6.2 approval of the device.
Throughout this document:
DynaFlex II Go products refers to all products in the DynaFlex II Go product family, including DynaFlex II Go models equipped with a barcode reader (BCR) and Bluetooth LE connectivity.
Custom host software uses the same underlying device command set for all DynaFlex II product connection types. This section provides high-level information about communicating with the device via the various physical connection types in various software development frameworks, and provides pointers to available SDKs, which include sample code. Product documentation and SDKs are available for download by searching for the product name on and navigating to the tab.
MagTek provides convenient SDKs and corresponding documentation for many programming languages and operating systems. The API libraries included in the SDKs wrap the details of the connection in an interface that conceptually parallels the device’s internal operation, freeing software developers to focus on the business logic, without having to deal with the complexities of platform APIs for connecting to the various available connection types, communicating using the various available protocols, and parsing the various available data formats. Information about using MagTek wrapper APIs is available in separate documentation, including:
MagTek Universal SDK Programmer’s Manual (Microsoft .NET)
DynaFlex II SCR is a compact secure card reader authenticator that accepts magstripe, EMV contact, EMV contactless, and NFC mobile-wallet transactions — with optional barcode reading — for retail, hospitality, healthcare, and kiosk environments. It connects to Android and Windows hosts over USB and meets PCI PTS 6.x SCR/SRED requirements. Download brochures and spec sheets below.
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
Find downloadable software for MagTek's DynaFamily of MMS Dyna devices — SDKs, demo and sample apps, configuration utilities, and enterprise management tools. Choose a device below to see its full set of development and management resources.
DO NOT remove any of the covers or guards that are fastened with screws. There are no user-serviceable areas within these covers.
DO NOT override or “cheat” electrical or mechanical interlock devices.
DO NOT use EC3000 supplies or cleaning materials for other than their intended purposes.
DO NOT operate the equipment if you or anyone else have noticed unusual noises or odors.
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation! feedback@magtek.com
MagTek Universal SDK Programmer’s Manual (Java)
MagTek Universal SDK Programmer’s Manual (Android)
The documentation is bundled with the SDKs themselves, which include:
MagTek Universal SDK for MMS Devices (Windows)
MagTek Universal SDK for MMS Devices (Android)
The SDKs and corresponding documentation include:
Functions for sending the direct commands described in this manual.
Wrappers for commonly used commands that further simplify development.
Sample source code to demonstrate how to communicate with the device using the direct commands described in this manual.
To download the SDKs and documentation, go to Universal SDK Documentation for the programming languages and platforms you need or contact MagTek Support Services for assistance.
In addition to the SDK API libraries, software developers also have the option to revert to direct communication with the device using libraries using the operating system’s native USB or TCP/IP. For example, custom software written in Visual Basic or Visual C++ may make API calls to the standard Windows USB HID driver. For more information about sending commands directly, see DynaFamily Programmer’s Manual.
For more information about developing custom applications that integrate with DynaFlex II, see the MagTek web site or contact your reseller or MagTek Support Services.

Periodic cleaning of the device’s exterior may be required. To clean the outside of DynaFlex II Go products, wipe down the device with a soft, slightly damp cloth and then wipe dry with a lint-free cloth. The graphic overlay on the face of the device can also be cleaned using a slightly damp specialty cleaning cloth, like those used to wipe lenses, monitors, and smartphone displays.
In addition to the security guidance in the product manuals, MagTek may provide updates to this document, as well as supplemental security guidance or notices regarding vulnerabilities, at www.magtek.com. MagTek advises checking the product’s home page periodically for the most up-to-date information.
Any firmware updates addressing product features, bugs, or security vulnerabilities are also posted to www.magtek.com or may be sent directly to affected customers. To update the device’s firmware:
Obtain the firmware image to install from your MagTek representative.
Download 1000007406 DynaFlex, DynaProx Test Utility from the MagTek web site.
Follow the instructions in D998200402 DynaFlex, DynaProx Utility User Manual (Windows) included in the firmware update utility’s Docs subfolder.
A collection of short videos designed to give you an overview of the DynaFlex II SCR product, how to use it, and the features it offers.
Reference Section
Information Available
These catalogs highlights the DynaFlex II SCR, a secure card reader authenticator in a small form factor that is ready to accept tap, swipe, and dip payments in a wide variety of retail environments.
The essential software resources for developing with and managing the DynaFlex II PED PIN-entry reader.
The essential software resources for developing with and managing the DynaFlex II Go secure card reader.
The essential software resources for developing with and managing the DynaProx contactless reader.
Reference Section
Information Available
The essential software resources for developing with and managing the DynaFlex II SCR countertop secure card reader.
This brochure details the MagTek Dyna family of devices that bring a new level of security to your point-of-sale platform with dynamic authentication, encryption, and tokenization.
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.
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.
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".
A Barcode symbology refers to the way in which data is encoded in a barcode. It uses either spaced lines, dots or squares. When read, these symbols are decoded and converted to data. The table below lists all of the supported symbologies and which are enabled by default.
Symbology
Default
AIM 128
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)
The guidelines in the following sections are intended to help project planners and system administrators plan for the physical and logical requirements of deploying and using DynaFlex II Go products. The most effective way to ensure smooth deployment of a solution is to consider these factors before receiving the device.
Determine what type of host DynaFlex II Go will connect to. For a list of supported device types and operating systems, see Table - Available Models and Options. When planning, be sure to include any additional support or devices required by the host and DynaFlex II Go, such as physical locations, mounting, power connections, and charging cradles.
Determine what connection the host will use to communicate with the device. The available connections are USB-C for power and control and Bluetooth® Low Energy (LE) for wireless connectivity (see Table - Available Models and Options).
Determine what software will be installed on the host and how it will be configured. Software can include the operating system, transaction processing software, security software, and so on. If teams other than the software development team will be involved in preliminary device testing, MagTek recommends the solution development team provide a smoke test harness early in the development process to allow basic testing (for example, communication adapter testing). In addition, be sure to plan for any additional support required by the software, such as software licenses and network connections. Information about software is provided in section 4.2 About Host Software.
Determine how the device will be physically presented to the cardholder. If the device is mounted, make sure there is adequate clearance for cardholders to swipe, insert, and tap. If the solution design includes metal objects anywhere near the device, including metal enclosures, make sure that at all points the metal is no closer than 15mm from the MSR swipe path or card insertion slot. Proximity to metal can adversely affect the device’s performance.
Determine how the device should be configured and specify that configuration when ordering the device. A full list of configurable options is documented in D998200597 DynaFlex II Go Programmer’s Manual (COMMANDS).
Select and configure a secure workstation that advanced operators will use to configure and/or update the device. The workstation must be configured as follows:
Available USB port.
A secure means of obtaining files, either via the network (such as SFTP) or via removable media, such as USB flash drives. This is required for installing software tools, copying firmware files, etc. If you are using Magensa Services, make sure the secure workstation has an internet connection and has all the required Magensa Remote Services software components installed.
Determine the final set of tools advanced operators will use to configure, test, and update the device. This documentation uses the 1000007406 DynaFlex, DynaProx Test Utility as an example for configuring the device; it can be used for initial pre-deployment testing and development, and as sample code showing how to communicate with the device, but the full solution may call for customized, solution-specific software for configuring the device and updating firmware.
Determine how to inspect devices upon arrival, upon installation, and periodically during live usage, to ensure malicious individuals have not tampered with them. Details about inspection are provided in section 4.1 About Inspection.
Develop procedures for maintaining the device(s). Detailed guidance is provided in section 8 Maintenance.
Determine how to train operators. For example, training may include information extracted from section 5 Configuration, section 6 Operation, and section 8 Maintenance.
Review the device’s PCI Security Policy, posted to the PCI web site under Approved PIN Transaction Security (PTS) Devices, for additional information about using the device securely.
This document addresses the proper use of the DynaFlex II Go family of secure card readers (SCR) in a secure manner. This includes information about key-management responsibilities, administrative responsibilities, device functionality, identification, and environmental requirements.
Reference Section
Information Available
Addresses the proper use of the DynaFlex II Go family of secure card readers (SCR) in a secure manner.
DynaFlex II Go is a compact secure card reader authenticator that accepts tap (NFC and EMV contactless), swipe (magnetic stripe), and dip (EMV contact chip) transactions, with an optional barcode reader for 1D/2D and QR codes. It connects over USB or Bluetooth® LE and is built for mobile, countertop, and kiosk deployments on Windows, Android, and iOS. The guides below cover everything you need to install and operate the device.
Reference Section
Information Available
A short get-started reference for unpacking, connecting, and powering on DynaFlex II Go — the fastest path to a working device.
DynaProx is MagTek's rugged, contactless-only reader, combining the controller and NFC antenna in a compact sealed housing. It accepts EMV Contactless and NFC Contactless transactions — including mobile wallets and MIFARE® credentials — with an optional barcode reader (DynaProx BCR) for 1D/2D codes. Rated IP66/IK08 for harsh indoor and outdoor conditions, it's designed for kiosks, unattended terminals, and countertop use over USB, USB iAP2, or RS-232. The guide below covers everything you need to install and operate the device.
Reference Section
Information Available
The complete reference for planning, installing, configuring, operating, and maintaining DynaProx, plus pointers for developers integrating the device.
Brochures
Description
This brochure highlights the DynaFlex II Go, a secure card reader authenticator in a small form factor that is ready to accept tap, swipe, and dip payments in a wide variety of retail environments.
blurb
iDynamo 5 (Gen III) is a compact secure card reader authenticator (SCRA) that reads magnetic stripe cards that conform to ISO standards. iDynamo models are made for iOS, Android, and Windows devices equipped with a USB-C or Lightning interface. When a cardholder swipes a card, the device encrypts card data before they leave the encapsulated magnetic stripe reader head using the Triple Data Encryption Algorithm (TDEA, also known as Triple DES) and DUKPT key management.
The exterior of the device is a a rubberrized plastic. Visually inspect the device for signs of tampering. There should be no evidence of loose wires or screws, misplaced labels, cracked casing, holes, or tool marks.
Front Face: Inspect the overall form factor for signs of tampering. The front face has an embossed MagTek lock.
TOP: The top of the device has a single LED and power button.
The DynaProx is a next-generation, EMV Contactless, and NFC Contactless reader from MagTek, designed for original equipment manufacturers (OEMs) and developers building secure payment, access control, and identification solutions. It combines the controller and antenna in a small form-factor, and is available in two models: the standard DynaProx for EMV Contactless, and NFC transactions, and the DynaProx BCR which includes a camera for reading 1D/2D barcodes. The device is engineered with the MagneSafe® Security Architecture, meeting requirements for contactless EMV 3.0 and PCI PTS POI 6.x, and supports triple DEA and AES-256 encryption with DUKPT key management to safeguard sensitive payment data.
Beyond payments, DynaProx supports MIFARE® technology for access control, as well as Apple® VAS and Google SmartTap for mobile wallet protocols supporting event ticketing and loyalty programs. Ruggedized for unattended environments, it features IK08 impact resistance and IP66 water ingress protection, making it ideal for kiosks, vending machines, car washes, gas pumps, and countertop deployments with an optional stand. The device connects via USB, USB iAP2, or RS-232 interfaces, and is compatible with Windows, Linux, Android, and iOS applications. DynaProx is also ready for use with Magensa L3 certified gateway services. The official MagTek DynaProx support page is a central hub containing all the resources you'll need. There you can find product brochures, programmer's manuals for the MMS implementation, developer guides (including for EMV Common Kernel and L3 certification), a product catalog, and a comprehensive FAQ section with instructional videos.
The DynaFlex II Go is a PCI PTS v6.x certified Secure Card Reader Authenticator (SCRA) from MagTek, designed for mobility without compromising security. It features a compact, low-profile design and is ready to accept a wide range of payment types, including tap (contactless/NFC mobile wallets like Apple Pay, Google Pay, and Samsung Pay), swipe (magnetic stripe), and dip (EMV chip cards). The optional BCR model adds the ability to scan both 1D and 2D barcodes, and it also supports reading and writing non-payment NFC data for use in access control, loyalty, and transit ticketing applications.
The device offers flexible connectivity via USB-C or Bluetooth® LE, works across Windows, Android, and iOS hosts, and is backed by MagTek’s MagneSafe® Security Architecture, including AES encryption and DUKPT key management. The official MagTek DynaFlex II Go support page is a central hub containing all the resources you'll need. There you can find product brochures, compliance documentation (including device and package inspection guides), programmer’s manuals, SDKs, a comprehensive FAQ section, and instructional videos.
This compliance documentation page provides the essential security and inspection guides required to ensure the physical integrity of DynaFlex II Go secure card readers before and after deployment.
Disabled
Aztec
Enabled
Codabar
Enabled
Code 11
Disabled
Code128
Enabled
Code 32
Disabled
Code 39
Enabled
Code 93
Disabled
Data Matrix
Enabled
EAN-8
Enabled
EAN-13
Enabled
Febraban
Disabled
GSI-128 (UCC/EAN-128)
Enabled
GS1 Databar (RSS)
Disabled
Industrial 25
Disable
Interleaved 2 of 5,
Enabled
ISSN
Disabled
ISBN
Disabled
ITF-14
Disabled
ITF-6
Disabled
Matrix 2 of 5
Enabled
Micro QR
Disabled
MSI Plessey
Disabled
PDF417
Enabled
Plessey
Disabled
QR Code
Enabled
Standard 25
Disabled
UPC-E
Enabled
UPC-A
Enabled
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation! feedback@magtek.com
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation! feedback@magtek.com
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation! feedback@magtek.com
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 transaction requires a signature, the device sends a notification message to the host that includes the status Signature Capture Requested. In this case, the solution design collects the cardholder’s signature manually or via a different method.
The device ends the transaction and reports the transaction status to the host.
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.
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.
Do not tilt the barcode more than 60 degrees from parallel to the device’s face.
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.
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).
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.
The device notifies the host that the transaction has ended with the NFC Tag removed.
















An Android Software Development Kit that provides tools, a sample application, sample code, and documentation for developers creating solutions for MagTek MMS devices on Android hosts.
Contains the necessary tools for software developers who want to create software solutions for MagTek devices to a Windows based host using Java Virtual Machine.
A Linux-based SDK that includes sample applications, code, and documentation for building software solutions for MagTek MMS devices on Linux hosts.
A Windows SDK that provides sample code, documentation, and a demo application to help developers integrate MagTek MMS devices into Windows-based host applications.
Description
Summary
A full-featured Android browser designed for app development, enabling web apps to communicate with hardware without needing plugins, available on Google Play and the Amazon app store.
A Windows application that automates the configuration and firmware updates for a wide range of MagTek readers, including all DynaFlex II models, across an enterprise deployment.
Description
Summary
A configuration utility for a variety of DynaFlex and DynaProx devices used to change or update EMV configurations, run demo EMV transactions, upload bitmap images, and parse TLV data.
A demo web page designed to illustrate the functionality of the MagneFlex Browser, which can be launched on Android, iOS, and Windows versions of the browser.
The MagneFlex Browser is a full function browser this free development tool can be white-labelled and provides a turnkey integration solution for web applications, working with MagTek hardware and services. Sites developed in HTML 5 with device responsive views will work seamlessly in this browser allowing an app to respond to devices whether they are tablets or phones.
Description
Summary
A full-function HTML browser application for Windows x64, featuring a developer mode for debugging JavaScript, improved HTML/framework rendering, and tabbed browsing.
A full-function HTML browser application for Windows x86, featuring the same developer tools and modern rendering capabilities as the x64 version.
Description
Summary
A web console that accepts an OID and command data and returns the data to use for MTUSDK configuration commands on DynaFlex devices.
A utility for demonstrating and testing barcode-reading operations on DynaFlex BCR and DynaProx BCR devices (models equipped with a barcode reader).
General Status LED: Power on the device and make sure that there is no indication that potential tampering was detected. After the device goes through the boot-up process, the LED should be solid green.
Bottom: A single USB-C receptacle is on the bottom of the device with certification and compliance logos as shown in the image.
Reader Left: There are 2 adapter sleeve retainer holes. There are no other components.
Reader Right: There are 2 adapter sleeve retainer holes. There are no other components.
Reader Back: The MagTek logo is debossed into the plastic and the product label in located on the bottom right.
Magnetic Swipe Path: Check the card insert slot. The reader has a smooth, unobstructed path. Insert an embossed card into the device to check for any signs of obstructions inside the card insertion slot. Other than the magnetic head that reads magnetic stripes there are no electronics, objects, or wires in the path.
Product Label: The product label is located on the back of the device. Check PN, SN and HW number. Serial Number matches serial number on boot-up. Check the product label on the device is complete, fully attached, with no signs of modification.Check the information (part #, model name, and serial number) on the label and ensure it matches the information found on the package and in any documents such as invoices.
Check shipping documents and tracking information to ensure that the shipment origin and sender information are correct. Check for evidence of tampering with the package containing this device. Before shipment, the box is sealed with tamper evident tape that will show VOID and OPENED if removed. The box and seal should be intact when initially received.
Check all views of the device and compare to photos.
It is helpful to do the following for your device inspection audit.
Have a list of the devices and details listed on the asset tag.
Take photos of the front, back, and sides of each device.
Check device Part numbers, serial numbers and IDs and check physical connections. Report any suspected signs of tampering immediately.
PCI Web Site: https://www.pcisecuritystandards. org/assessors_and_solutions/pin_transaction_devices.
Search for MagTek and find the product name, oiDynamo 5 (Gen III), on the web page. Compare the Hardware # and Firmware #.
Periodically inspect the following items while in use:
Card swipe path
Power Button
Form factor
LED
Label
USB-C receptacle
Reference Section
Information Available
These catalogs highlights the DynaProx, a secure card reader authenticator in a small form factor that is ready to accept tap, swipe, and dip payments in a wide variety of retail environments.
A collection of short videos designed to give you an overview of the DynaProx product, how to use it, and the features it offers.
These catalogs highlights the DynaFlex II Go, a secure card reader authenticator in a small form factor that is ready to accept tap, swipe, and dip payments in a wide variety of retail environments.
A collection of short videos designed to give you an overview of the DynaFlex II Go product, how to use it, and the features it offers.
Reference Section
Information Available
This document addresses the proper use of the DynaFlex II Go family of secure card readers (SCR) in a secure manner.
Reference Section
Information Available
A manual that outlines the step-by-step procedures for visually inspecting the DynaFlex II Go's hardware label, physical appearance, and tamper indicators to verify its authenticity and security before use.
A guide that details how to examine the device's secure packaging for signs of tampering during storage or transit, helping to ensure the reader has not been compromised before deployment.
Name, appearance, and Identification
Inspection, installation, environmental conditions, security protocols, configuration settings.
Inspection, self-test, roles & responsibilities, Password & Certificates, Tamper Response, Patching & Updating, Decommissioning
Account data protection, algorithms supported, Key Management, key loading, key replacement.
Acronyms
The complete reference for planning, installing, configuring, operating, and maintaining DynaFlex II Go, plus pointers for developers building custom software.
Essential software resources for developing with and managing the oDynamo secure card reader,
This comprehensive catalog introduces MagTek as a leading manufacturer of secure electronic systems, including card readers, encrypting check scanners, PIN pads, and credential personalization systems.
This brochure details the MagTek Dyna family of devices that bring a new level of security to your point-of-sale platform with dynamic authentication, encryption, and tokenization.
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 manual, specific blinking patterns are described in more detail in the sections where they are relevant. For example, information about how the LEDs show the device’s connection status is in section Connecting DynaFlex II Go to a Host.
Brochures
Description
DynaFlex products are ready to launch your payment environment to the next level. DynaFlex products deliver a wide variety of payment acceptance in a small form-factor. All DynaFlex products offer an integrated secure card reader authenticator for magnetic stripe cards, EMV chip cards (contact and contactless), and NFC enabled mobile wallets including Samsung Pay, Google Pay, and Apple Pay. DynaFlex products designated as “Pro” include a responsive touchscreen with support for Manual Entry and Signature Capture.
DynaFlex II PED adds a color touchscreen for PIN on Glass, signature capture, and manual card entry to the full DynaFlex II payment set — magstripe, EMV contact, EMV contactless, and NFC mobile wallets, with optional barcode. Purpose-built for teller lines, branch automation, and point of sale, it meets PCI PTS 6.x PED/SRED requirements and connects to Android and Windows hosts over USB. Download brochures and spec sheets below.
Reference Section
Information Available
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.
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.
The Device Manuals page is where you will find documentation and instructions for product-specific functions including installation and operational manuals.
The Installation and Operation Manual is the primary reference for deploying and running DynaFlex II Go. It covers planning, physical installation, configuration, day-to-day operation across tap, swipe, dip, and optional barcode, the device's LED and audio indicators, routine maintenance, and guidance for developers building custom software. Use the reference sections below to jump to a topic.
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation! feedback@magtek.com
A sample Android application provided with the MTUSDK that demonstrates communication with MagTek card readers (including the DynaFlex II Go) and simulates a transaction process.
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation! feedback@magtek.com
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation! feedback@magtek.com
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation! feedback@magtek.com
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation! feedback@magtek.com

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.
In This Context
LED1
LED2
LED3
LED4
Active Mode, not armed for a tap transaction
Power
Connection
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
Reserved
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.
🕐 Hours: Monday-Friday, 6:00 AM - 5:00 PM PST
Online Resources:
🌐 Official Site: https://www.magtek.com
💬 Developer Forum: https://forum.magtek.com
Documentation Feedback:
Help us improve this documentation!
Includes the full Installation & Operational ManualT
Reference Section
Information Available
Includes Quick Installation Guide and the full Installation & Operational Manual
Includes the full Installation & Operational Manual
Lists all of the supported symbologies and which are enabled by default.
A variety of accessories designed to meet a wide range of operational needs.
Legal notifications
Reference Section
Information Available
Reference Standards and certifications
These catalogs highlights the DynaFlex II PED, a secure card reader authenticator in a small form factor that is ready to accept tap, swipe, and dip payments in a wide variety of retail environments.
A collection of short videos designed to give you an overview of the DynaFlex II Go product, how to use it, and the features it offerPED
This product-compliance compliance documentation page provides the essential compliance and security documentation required to ensure the integrity of specifc secure card readers before and after deployment.
Reference Section
Information Available
Compliance documentation for the DynaFlex II Go.
This universal compliance and security documentation page provides the essential security and inspection guides required to maintain and ensure the physical integrity of MagTek products before and after deployment.
Reference Section
Information Available
Common technical details for magnetic stripe cards.
This section holds compliance, security, and standards documentation that spans the product line — the cross-product references that apply regardless of which device you're integrating, such as magnetic-stripe (ANSI/ISO) card data standards, EMV specifications, and general PCI and regulatory guidance. For a specific device's security policy and certifications, see that product's Compliance page under Products.
Reference Section
Information Available
This compliance documentation page provides the essential security and inspection guides required to maintain and ensure the physical integrity of MagTek products before and after deployment.
The merchant or acquirer should daily check the appearance of secure card reader:
Inspect the appearance of secure card reader to make sure it is the right product.
Inspect whether the Swipe Path has an additional card reader or other inserted bugs, See Figure 4‑1, below.
Observe the Chip Card Insertion Slot to determine whether there are any wires or obstructions. See Figure 4‑1, below.
The Installation and Operation Manual is the primary reference for deploying and running DynaProx. It covers planning, physical installation, configuration, day-to-day operation across tap, swipe, dip, and optional barcode, the device's LED and audio indicators, routine maintenance, and guidance for developers building custom software. Use the reference sections below to jump to a topic.
Find installation, operation, and reference documentation for the DynaFlex II PIN entry device, including setup guidance and technical specifications for developers and integrators.
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation! feedback@magtek.com



🕐 Hours: Monday-Friday, 6:00 AM - 5:00 PM PST
Online Resources:
🌐 Official Site: https://www.magtek.com
💬 Developer Forum: https://forum.magtek.com
Documentation Feedback:
Help us improve this documentation!
🕐 Hours: Monday-Friday, 6:00 AM - 5:00 PM PST
Online Resources:
🌐 Official Site: https://www.magtek.com
💬 Developer Forum: https://forum.magtek.com
Documentation Feedback:
Help us improve this documentation!
Inspect whether the product appearance has been changed.
Check if the firmware version is correct.
Power on the secure card reader and check that the firmware runs well, as the startup will inspect the hardware security, authenticity, and integrity of firmware. Only the leftmost LED should be on and blinking green
Figure 4‑1 - Chip Card Insertion Slot and Swipe Path Examples
MagTek strongly recommends performing security inspections on a regular schedule. Additional information can be found in DynaFlex II Go, Device Inspection Document. If any problems are detected, stop using the device, set it aside in a secure location, and contact the manufacturer or your acquirer for further advice.
DynaFlex II Go performs self-tests at power-up and after reset. By default, the device automatically resets and performs self-tests every 23 hours if it is configured to automatically reset 23 hours after booting, otherwise the device automatically resets and performs self-tests every 24 hours if it is configured to automatically reset at a specific time of day. No manual intervention by the operator is required. Self-tests include:
Checking the integrity and authenticity of the firmware and cryptographic keys.
Checking security mechanisms for signs of tampering.
The secure card reader has no functionality that gives access to security-sensitive services based on roles. Such services are managed through dedicated tools, using cryptographic authentication.
DynaFlex II Go products ship from the factory fully secure. There are no security default values that require modifications by the user to meet PCI security requirements, except the “Bluetooth LE passkey.” MagTek recommends one of two options:
Devices are ordered with the default passkey changed by MagTek during device configuration prior to shipping
The customer change the default passkey with a software utility that changes Property 1.2.2.3.1.9 Bluetooth LE Passkey described in DynaFlex II Go Programmer’s Manual (COMMANDS).
If the device senses a physical or environmental attack, it erases all sensitive keys, and will have limited functionality. While powered on, the SCR indicates it is in a tampered state by flashing green LEDs 1,3, and 4 as depicted in Figure 4‑2 Tamper Response. If this occurs:
Remove the device from service immediately.
Store it securely for possible forensics investigation.
Contact the manufacturer for assistance. The device will likely need to be returned to the manufacturer for diagnosis and servicing.
Figure 4 2 Tamper Response
DynaFlex II Go products support file-based updates of the device’s core firmware (main firmware) and authorized commands for updating sensitive configuration. For optimal device security, MagTek recommends the latest versions of firmware should always be installed.
Firmware updates are provided as files that have been signed by MagTek. The firmware files can be loaded locally through USB or Bluetooth LE connection by using update tools available from the MagTek web site. The device verifies each update is newer than the installed version, and cryptographically authenticates the file. If version checking or authentication fails, the device erases the update file and reports an error to the host.
For help with updates to EMV configuration, contact Magensa Remote Services.
Before DynaFlex II Go products are permanently removed from service, all the keys and sensitive data must be erased. One way to accomplish this is by temporarily removing the back cover, which forces a tamper response.
If removal from service is only temporary, no action is required. All sensitive data will continue to be protected by the device’s physical and logical protection mechanisms.
Lists all of the supported symbologies and which are enabled by default.
Legal notifications
Reference Section
Information Available
Reference Standards and certifications
Compliance documentation for the iDynamo Gen III.
Provides the essential compliance documentation required to ensure the integrity of specifc secure card readers before and after deployment.
Reference Section
Information Available
Manuals and technical documentation for the DynaFlex II PED.
ISO 7810, ISO 7811, AAMVA
ISO/IEC 7816-1, 2, 3, & 4 Identification Cards Integrated Circuits with Contacts
EMV ICC Specifications for Payment Systems Version 4.3d, L1 Contact and Version 4.4a, L2 Contact EMV Contactless Level 1 Version 3.1a
MasterCard TQM
MCL v3.1.4, payWave v2.2c, Expresspay 4.1, D-PAS Terminal Payment Application v2.0 PCI PTS POI v6.2 SCR
DUKPT TDES, AES 128 DUKPT
FCC Part 15 Low Power Transceiver, RX verified per FCC Title 47 Part 15 Subclass C UL/CSA/IEC 62368-1, 2nd edition
CE Certified
CE Safety: IEC 62368-1: 2014
Canada ISED Certified
AS/NZS CISPR 32 (2013), AS/NZS 4268 Table 1, Row 59 DTS 2400-2483MHz SRD (802.11), and AS/NZS 4268 (2017) Table 1, Row 43 13.553-13.567MHz (contactless reader)
RoHS Compliant the Electrical and Electronic Equipment (EEE) Reduction of Hazardous Substances (RoHS) European Directive 2002/95/EC
California Proposition 65 (California) IPC-A-610 Class II Assembly
EU Directive Waste Electrical and Electronic Equipment (WEEE) EU Directive Restriction of Hazardous Substances (RoHS) Universal Serial Bus Specifications 1.1, 2.0
AES-128 and AES-256 Encryption Apple VAS
iAP2® Protocol Support Bluetooth® Core Specification 5.2
EMV Contactless Level 1 Version 3.0 MasterCard TQM
MCL v3.1.3, payWave v2.2, Expresspay 4.0.2, D-PAS Terminal Payment Application v1.0, D-PAS Terminal Application Specification Bulletins CL TAS-002 v1.1, CL TAS-003 v1.0, CL TAS-004 v1.0 PCI PTS POI v6.1 SCR
TDEA (3DES)-CBC using DUKPT
FCC Part 15 Low Power Transceiver, RX verified per FCC Title 47 Part 15 Subclass C UL/CSA/IEC 62368-1, 2nd edition
CE Certified
CE Safety: IEC 62368-1: 2014
Canada ISED Certified
AS/NZS CISPR 32 (2013), AS/NZS 4268 Table 1, Row 59 DTS 2400-2483MHz SRD (802.11), and
AS/NZS 4268 (2017) Table 1, Row 43 13.553-13.567MHz (contactless reader)
RoHS Compliant the Electrical and Electronic Equipment (EEE) Reduction of Hazardous Substances (RoHS) European Directive 2002/95/EC
California Proposition 65 (California) IPC-A-610 Class II Assembly
EU Directive Waste Electrical and Electronic Equipment (WEEE) EU Directive Restriction of Hazardous Substances (RoHS) Universal Serial Bus Specifications 1.1, 2.0
AES, SHA-256
Find marketing materials — brochures, spec sheets, and sell sheets — for MagTek products, organized by product family. Use the sections below to browse current card readers, check scanners, OEM components, card-issuance solutions, and legacy products.
Current-generation MMS Dyna payment devices (DynaFlex II and DynaProx).
Current secure card reader authenticators, by family.
Check scanners and MICR readers, many with an integrated card reader.
Reader modules, read heads, and ASICs for OEM integration.
Instant card issuance and PIN solutions for financial institutions.
Discontinued and superseded MagTek products.
Brochures
Description
DynaFlex products are ready to launch your payment environment to the next level. DynaFlex products deliver a wide variety of payment acceptance in a small form-factor. All DynaFlex products offer an integrated secure card reader authenticator for magnetic stripe cards, EMV chip cards (contact and contactless), and NFC enabled mobile wallets including Samsung Pay, Google Pay, and Apple Pay. DynaFlex products designated as “Pro” include a responsive touchscreen with support for Manual Entry and Signature Capture.
This compliance documentation page provides the essential security and inspection guides required to maintain PCI PTS approval and ensure the physical integrity of iDynamo 5 Gen III secure card readers before and after deployment.
Reference Section
Information Available
A manual that outlines the step-by-step procedures for visually inspecting the iDynamo 5 Gen III's hardware label, physical appearance, and tamper indicators to verify its authenticity and security before use.
The merchant or acquirer should inspect the appearance of secure card reader on a daily basis:
Inspect the appearance of secure card reader to make sure it is the right product.
Inspect whether the Swipe Path has an additional card reader or other inserted bugs, See Figure 4-1, below.
Inspect whether the product appearance has been changed.
Check if the firmware version is correct.
After connecting the device to a USB-C power supply, it will power on, the LED indicator should illuminate green and remain powered on to indicate the device is in an idle state, ready for a transaction. Powering on the secure card reader will test hardware security and authenticity, and the integrity of the installed firmware.
MSR Swipe Path: The swipe path is smooth. The only moving part is the spring-mounted read head that depresses into the device as the card’s magnetic stripe makes contact with the read head.
Figure 4-1 - Card Swipe Path Example
MagTek strongly recommends performing security inspections on a regular schedule. Additional information can be found in [2]. If any problems are detected, stop using the device, set it aside in a secure location, and contact the manufacturer or your acquirer for further advice.
iDynamo 5 Gen III performs self-tests at power-up and after reset. The device automatically resets and performs self-tests every 24 hours at the configured time of day. No manual intervention by the operator is required. Self-tests include:
Checking the integrity and authenticity of the firmware and cryptographic keys.
Checking security mechanisms for signs of tampering.
The secure card reader has no functionality that gives access to security-sensitive services based on roles. Such services are managed through dedicated tools, using cryptographic authentication.
iDynamo 5 Gen III products ship from the factory fully secure. The devices have no security related default values (e.g., passwords/authentication codes/certificates) that require modification by the user to meet PCI security requirements.
If the device senses a physical or environmental attack, it erases all sensitive keys and will have limited functionality. While powered on, the SCR indicates it is in a tampered state by illuminating its only LED solid red, as seen in Figure 4-2 Tamper Response. If this occurs:
Remove the device from service immediately.
Store it securely for a possible forensics investigation.
Contact the manufacturer for assistance. The device will likely need to be returned to the manufacturer for diagnosis and servicing.
Figure 4-2 Tamper Response
iDynamo 5 Gen III products support file-based updates of the device’s core firmware (main firmware) and authorized commands for updating sensitive configuration. For optimal device security, MagTek recommends the latest versions of firmware should always be installed.
Firmware updates are provided as files that have been signed by MagTek. The firmware files can be loaded locally through the USB-C interface by using update tools available from the MagTek web site. The device verifies each update is newer than the installed version, and cryptographically authenticates the file with RSA-2048 and SHA-256. If version checking or authentication fails, the device erases the update file and reports an error to the host.
Before iDynamo 5 Gen III products are permanently removed from service, all the keys and sensitive data must be erased. One way to accomplish this is by temporarily removing the back cover, which forces a tamper response.
If removal from service is only temporary, no action is required. All sensitive data will continue to be protected by the device’s physical and logical protection mechanisms.
The DynaFamily is MagTek's current generation of secure payment devices, built on a shared MMS command architecture so a single integration effort carries across form factors. Use this section to find brochures, spec sheets, and sell sheets for each DynaFamily device.
Reference Section
Information Available
Multi-interface secure card reader for retail and kiosk payments (no PIN pad).
The Installation and Operation Manual is the primary reference for deploying and running DynaProx. It covers planning, physical installation, configuration, day-to-day operation across tap, swipe, dip, and optional barcode, the device's LED and audio indicators, routine maintenance, and guidance for developers building custom software. Use the reference sections below to jump to a topic.
Reference Section
Information Available
Reference Standards and certifications
The following documents may be used to provide additional details about the device and this security policy:
MagTek iDynamo 5 Gen III Installation and Operation Manual PN: D998200614
MagTek iDynamo 5 Gen III SRED, Device Inspection Manual PN: D998200620
MagTek iDynamo 5 Gen III Programmer’s Manual COMMANDS PN: D998200587
NIST SP 800-57-1 Recommendation for Key Management
ANS X9.24 Part 3:2017, Retail Financial Services Symmetric Key Management, Part 3: Derived Unique Key Per Transaction Using Symmetric Techniques
X9 TR-31:2010, Interoperable Secure Key Exchange Key Block Specification for Symmetric Algorithms
X9.143 (TR-31) Symmetric Key
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation! feedback@magtek.com



🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation! feedback@magtek.com



EMV Contactless Reader:
EMVCo L1 and L2 Contactless Reader
D-PAS, PayPass/MCL, payWave, Expresspay
Mobile wallets including but not limited to Apple Pay, Google Pay, Samsung Pay
Barcode Reader:
Barcode Media: Labels, paper, smartphone / computer displays Barcode Types: QR Codes, Linear Barcodes, UPC-A, UPC-E, Code 128, PDF417 / Data Matrix, Aztec, etc.
Field Of View 31.5° total vertical sweep, 42° total horizontal sweep, perpendicular to device face
Depth Of Field 1.2 in. (30mm) to 13.8 in. (350mm) Integrated white indicator LED
Current Requirements:
500 mA Maximum
Data Storage:
Not Applicable
Storage Relative Humidity:
Up to 90% RH non-condensing
Vibration Resistance:
None
Shock Resistance:
None
ESD Tolerance (EMVCo):
±12.0 kV air discharge / 5 different paddles
ESD Tolerance (FCC/CE):
±8kV air discharge / ±4kV contact discharge
Vapor Resistance:
None
Dimensions (L x W x H):
2.76 in. x 2.57 in. x .79 in. (70.10mm x 65.3mm x20.1mm)
Weight
DynaFlex II Go = 3.17 oz. (90g) DynaFlex II Go BCR = 3.24 oz. (92g)
Supported Mounting Options:
Mounting to host via external clip or embedded lanyard
Magnetic Stripe Reader:
Three track bidirectional encrypting reader with MagnePrint
Magnetic Stripe Decoding:
Financial (ISO Type B), AAMVA, or Other
Magnetic Swipe Speeds:
6 inches per second to 60 inches per second
EMV Contact Reader:
Status Indicators:
4 Monochrome Green LEDs
1 Integrated white indicator LED for BCR
Display Type:
Not Applicable
Keypad:
Not Applicable
Certifications:
PCI PTS POI v6.2 Certified Secure Card Reader (SCR)
Tamper Protection:
The enclosure and associated electronics form a Tamper Resistant Security Module (TRSM) where attempts to penetrate or modify the unit cause all cryptographic keys to be cleared or rendered unusable.
Power Inputs:
USB powered via USB-C receptacle
Power Outputs:
None
Rechargeable Battery Type:
Lithium-Ion Polymer (LiPo)
Voltage Requirements:
Wired Connection Types:
USB-C, compatible with USB 1.1, USB 2.0, USB 3.0
Vendor-defined USB Human Interface Device (HID) data format
Wireless Connection Types:
None
RF Exposure:
SAR Certified
Tested Operating System(s):
USB Hosts: Windows 11
Ingress Protection:
IP30
Operating Temperature:
DynaFlex II Go/DynaFlex II Go BCR: 32°F to 95°F (0°C to 35°C)
Operating Relative Humidity:
Up to 90% RH non-condensing
Storage Temperature:
Shelf Life:
60 Months Minimum
Magnetic Read Head Life:
500k Swipes
Battery Shelf Life:
5 years or longer (backup battery)
Battery Cycle Life:
EMVCo L1 and L2 Contact Reader
5 VDC
DynaFlex II Go/DynaFlex II Go BCR: -4°F to 113°F (-20°C to 45°C)
NA
Not Applicable
Keypad:
Not Applicable
Security Characteristics
Certifications:
PCI PTS POI v6.1 Certified Secure Card Reader (SCR)
Tamper Protection:
The enclosure and associated electronics form a Tamper Resistant Security Module (TRSM) where attempts to penetrate or modify the unit cause all cryptographic keys to be cleared or rendered unusable.
Electrical Characteristics
Power Inputs:
USB powered via USB-C receptacle
RS-232 powered via RS-232 custom receptacle
Power Outputs:
None
Rechargeable Battery Type:
None
Voltage Requirements:
5 VDC
Current Requirements:
800 mA recommended.
Note: Avoid poor quality cables, or cables longer than 12ft in length, as they can lead to unexpected reader behavior. Refer to Table 1-2 - DynaProx Accessories for cable options.
Data Storage:
Not Applicable
Communication Characteristics
Wired Connection Types:
USB-C, compatible with USB 1.1, USB 2.0, USB 3.0
Vendor-defined USB Human Interface Device (HID) data format
RS-232 Interface
Wireless Connection Types:
None
RF Exposure:
Exempt from SAR requirements due to radiated power substantially below regulatory thresholds.
IP66
Operating Temperature:
DynaProx: -22°F to 185°F (-30°C to 85°C) – DynaProx BCR: -4F to 131°F (-20°C to 55°C)
Operating Relative Humidity:
Up to 90% non-condensing
Storage Temperature:
DynaProx: -30°C to 85°C (-22°F to 185°F) – DynaProx BCR: -30°C to 70°C (-22°F to 158°F)
Storage Relative Humidity:
Up to 90% non-condensing
Vibration Resistance:
5Hz to 50Hz sinusoidal vibrations for 10 minutes at 1g acceleration on each of XYZ axes
Shock Resistance:
IK08
ESD Tolerance (EMVCo):
Not Applicable
ESD Tolerance (FCC/CE):
±8kV contact discharge / ±16kV air discharge when properly grounded
Vapor Resistance:
Test Gasoline-96 RON (Reference Gasoline); Reference Fuel C; Diesel 2007 Emission Certification Fuel (Reference Diesel); E10; E25; E85; M15; Road-Use Diesel; Road Use Unleaded
Reliability
Shelf Life:
60 months at 25°C nominal
Magnetic Read Head Life:
Not Applicable
ICC Read Head Life:
Not Applicable
Battery Shelf Life:
5 years or longer (backup battery)
Battery Cycle Life:
NA
Dimensions (L x W x H):
2.09 in. x 2.52 in. x .72 in. (53mm x 64mm x18.5mm)
Weight
DynaProx = 2.0 oz. (56g) DynaProx BCR = 2.0 oz. (58g)
Supported Mounting Options:
Mounting Screw Holes Optional Stand
Magnetic Stripe Reader:
Not Applicable
EMV Contact Reader:
Not Applicable
EMV Contactless Reader:
EMVCo L1 and L2 Contactless Reader
D-PAS, PayPass/MCL, payWave, Expresspay
Mobile wallets including but not limited to Apple Pay, Google Pay, Samsung Pay
Barcode Reader:
Barcode Media: Labels, paper, smartphone / computer displays Barcode Types: QR Codes, Linear Barcodes, UPC-A, UPC-E, Code 128, PDF417 / Data Matrix, Aztec, etc.
Field Of View 31.5° total vertical sweep, 42° total horizontal sweep, perpendicular to device face
Depth Of Field 1.2 in. (30mm) to 13.8 in. (350mm) Integrated white indicator LED
User Interface Characteristics
Status Indicators:
4 Monochrome Green LEDs
Software Characteristics
Tested Operating System(s):
USB Hosts: Windows 10, Android 4.4.2 and above
Environmental Resistance
Display Type:
Ingress Protection:
MagneSafe V5 SCRAs
OEM Readers
OEM Components
Card Readers
Magnetic Stripe Readers
This comprehensive catalog introduces MagTek as a leading manufacturer of secure electronic systems, including card readers, encrypting check scanners, PIN pads, and credential personalization systems. It also details the capabilities of Magensa, MagTek's cloud service subsidiary, which provides secure gateway, remote management, and decryption services for processing transactions using authentication, encryption, and tokenization.
A guide that details how to examine the device's secure packaging for signs of tampering during storage or transit, helping to ensure the reader has not been compromised before deployment.
This document addresses the proper use of theiDynamo 5 Gen III secure card readers (SCR) in a secure manner.
PIN-on-Glass reader with touchscreen for banking and point of sale.
EMV contactless and optional-barcode reader for kiosks and unattended terminals.
Handheld Bluetooth / USB-C reader for mobile payments.
Legal notifications
Download the software for developing with and managing the DynaProx contactless reader. This page brings together the MagTek Universal SDK (MTUSDK) for MMS devices on Android, iOS, Linux, and Windows, along with demo and sample apps, EMV and barcode configuration utilities, EMV tag packages, the MagneFlex Browser and middleware, and the Reader Management System clients for enterprise firmware and configuration updates.
Description
Summary
A web console that accepts an OID and command data and returns the data to use for MTUSDK configuration commands on DynaFlex and DynaProx devices.
The MagneFlex Browser is a full function browser this free development tool can be white-labelled and provides a turnkey integration solution for web applications, working with MagTek hardware and services. Sites developed in HTML 5 with device responsive views will work seamlessly in this browser allowing an app to respond to devices whether they are tablets or phones.
MagTek warrants that the products sold pursuant to this Agreement will perform in accordance with MagTek’s published specifications. This warranty shall be provided only for a period of one year from the date of the shipment of the product from MagTek (the “Warranty Period”). This warranty shall apply only to the “Buyer” (the original purchaser, unless that entity resells the product as authorized by MagTek, in which event this warranty shall apply only to the first repurchaser).
During the Warranty Period, should this product fail to conform to MagTek’s specifications, MagTek will, at its option, repair or replace this product at no additional charge except as set forth below. Repair parts and replacement products will be furnished on an exchange basis and will be either reconditioned or new. All replaced parts and products become the property of MagTek. This limited warranty does not include service to repair damage to the product resulting from accident, disaster, unreasonable use, misuse, abuse, negligence, or modification of the product not authorized by MagTek. MagTek reserves the right to examine the alleged defective goods to determine whether the warranty is applicable.
Without limiting the generality of the foregoing, MagTek specifically disclaims any liability or warranty for goods resold in other than MagTek’s original packages, and for goods modified, altered, or treated without authorization by MagTek.
Service may be obtained by delivering the product during the warranty period to MagTek (1710 Apollo Court, Seal Beach, CA 90740). If this product is delivered by mail or by an equivalent shipping carrier, the customer agrees to insure the product or assume the risk of loss or damage in transit, to prepay shipping charges to the warranty service location, and to use the original shipping container or equivalent. MagTek will return the product, prepaid, via a three (3) day shipping service. A Return Material Authorization (“RMA”) number must accompany all returns. Buyers may obtain an RMA number by contacting MagTek Support Services at (888) 624-8350.
EACH BUYER UNDERSTANDS THAT THIS MAGTEK PRODUCT IS OFFERED AS-IS. MAGTEK MAKES NO OTHER WARRANTY, EXPRESS OR IMPLIED, AND MAGTEK DISCLAIMS ANY WARRANTY OF ANY OTHER KIND, INCLUDING ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IF THIS PRODUCT DOES NOT CONFORM TO MAGTEK’S SPECIFICATIONS, THE SOLE REMEDY SHALL BE REPAIR OR REPLACEMENT AS PROVIDED ABOVE. MAGTEK’S LIABILITY, IF ANY, SHALL IN NO EVENT EXCEED THE TOTAL AMOUNT PAID TO MAGTEK UNDER THIS AGREEMENT. IN NO EVENT WILL MAGTEK BE LIABLE TO THE BUYER FOR ANY DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS, OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF, OR INABILITY TO USE, SUCH PRODUCT, EVEN IF MAGTEK HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY CLAIM BY ANY OTHER PARTY.
LIMITATION ON LIABILITY
EXCEPT AS PROVIDED IN THE SECTIONS RELATING TO MAGTEK’S LIMITED WARRANTY, MAGTEK’S LIABILITY UNDER THIS AGREEMENT IS LIMITED TO THE CONTRACT PRICE OF THIS PRODUCT.
MAGTEK MAKES NO OTHER WARRANTIES WITH RESPECT TO THE PRODUCT, EXPRESSED OR IMPLIED, EXCEPT AS MAY BE STATED IN THIS AGREEMENT, AND MAGTEK DISCLAIMS ANY IMPLIED WARRANTY, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
MAGTEK SHALL NOT BE LIABLE FOR CONTINGENT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES TO PERSONS OR PROPERTY. MAGTEK FURTHER LIMITS ITS LIABILITY OF ANY KIND WITH RESPECT TO THE PRODUCT, INCLUDING NEGLIGENCE ON ITS PART, TO THE CONTRACT PRICE FOR THE GOODS.
MAGTEK’S SOLE LIABILITY AND BUYER’S EXCLUSIVE REMEDIES ARE STATED IN THIS SECTION AND IN THE SECTION RELATING TO MAGTEK’S LIMITED WARRANTY
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:
(1) This device may not cause harmful interference, and (2) This device must accept any interference received, including interference that may cause undesired operation.
Note: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
· Reorient or relocate the receiving antenna.
· Increase the separation between the equipment and receiver.
· Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
· Consult the dealer or an experienced radio/TV technician for help.
Caution: Changes or modifications not expressly approved by MagTek could void the user’s authority to operate this equipment.
This digital apparatus does not exceed the Class B limits for radio noise from digital apparatus set out in the Radio Interference Regulations of the Canadian Department of Communications.
Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la classe B prescrites dans le Réglement sur le brouillage radioélectrique édicté par le ministère des Communications du Canada.
This Class B digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe B est conformé à la norme NMB-003 du Canada.
This device complies with ISED Canada licence-exempt RSS standard(s). Operation is subject to the following two conditions: (1) This device may not cause interference, and (2) This device must accept any interference, including interference that may cause undesired operation of the device.
Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorisée aux deux conditions suivantes: (1) L'appareil ne doit pas produire de brouillage, et (2) L'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d'en compromettre le fonctionnement.
Testing for compliance with CE requirements was performed by an independent laboratory. The unit under test was found compliant with standards established for Class B devices.
Hereby, MagTek Inc. declares that the radio equipment types Wideband Transmission System (Wireless LAN and Bluetooth® Low Energy), and Non-Specific Short Range Device (contactless) are in compliance with Directive 2014/53/EU. The full text of the EU declarations of conformity is available at the following internet addresses:
· for DynaFlex with no display, USB connection
· for DynaFlex with no display, Bluetooth® LE connection
· for DynaFlex Pro with USB connection
· for DynaFlex Pro with Bluetooth® LE connection
· for DynaFlex Pro with WLAN connection
Hereby, MagTek Inc. declares that the radio equipment types Wideband Transmission System (Wireless LAN and Bluetooth Low Energy), and Non-Specific Short Range Device (contactless) are in compliance with Radio Equipment Regulations 2017 Directive S.I.2017:1206. The full text of the UKCA declarations of conformity is available at the following internet addresses:
· for DynaFlex with no display, USB connection
· for DynaFlex with no display, Bluetooth® LE connection
· for DynaFlex Pro with USB connection
· for DynaFlex Pro with Bluetooth® LE connection
· for DynaFlex Pro with WLAN connection
Testing for compliance with AS/NZS standards was performed by a registered and accredited laboratory. The unit under test was found compliant with standards established under AS/NZS CISPR 32 (2013), AS/NZS 4268 Table 1, Row 59 DTS 2400-2483MHz SRD (802.11), and AS/NZS 4268 (2017) Table 1,
Row 43 13.553-13.567MHz (contactless reader).
This product is recognized per UL 60950-1, 2nd Edition, 2011-12-19 (Information Technology Equipment - Safety - Part 1: General Requirements), CSA C22.2 No. 60950-1-07, 2nd Edition, 2011-12 (Information Technology Equipment - Safety - Part 1: General Requirements).
When ordered as RoHS compliant, this product meets the Electrical and Electronic Equipment (EEE) Reduction of Hazardous Substances (RoHS) Directive (EU) 2015/863 amending Annex II to Directive 2011/65/EU. The marking is clearly recognizable, either as written words like “Pb-free,” “lead-free,” or as another clear symbol ( ).
PCI Security Standards Council, LLC (“PCI SSC”) has approved this PTS POI device (SCR class) to be compliant with the PCI PTS POI Security Requirements v5.1.
When granted, PCI SSC approval is provided by PCI SSC to ensure certain security and operational characteristics important to the achievement of PCI SSC’s goals, but PCI SSC approval does not under any circumstances include any endorsement or warranty regarding the functionality, quality or performance of any particular product or service. PCI SSC does not warrant any products or services provided by third parties. PCI SSC approval does not under any circumstances include or imply any product warranties from PCI SSC, including, without limitation, any implied warranties of merchantability, fitness for purpose, or non-infringement, all of which are expressly disclaimed by PCI SSC. All rights and remedies regarding products and services which have received PCI SSC approval shall be provided by the party providing such products or services, and not by PCI SSC.
IMPORTANT: YOU SHOULD CAREFULLY READ ALL THE TERMS, CONDITIONS AND RESTRICTIONS OF THIS LICENSE AGREEMENT BEFORE INSTALLING THE SOFTWARE PACKAGE. YOUR INSTALLATION OF THE SOFTWARE PACKAGE PRESUMES YOUR ACCEPTANCE OF THE TERMS, CONDITIONS, AND RESTRICTIONS CONTAINED IN THIS AGREEMENT. IF YOU DO NOT AGREE WITH THESE TERMS, CONDITIONS, AND RESTRICTIONS, PROMPTLY RETURN THE SOFTWARE PACKAGE AND ASSOCIATED DOCUMENTATION TO THE ADDRESS IN THIS DOCUMENT, ATTENTION: CUSTOMER SUPPORT.
TERMS, CONDITIONS, AND RESTRICTIONS
MagTek, Incorporated (the "Licensor") owns and has the right to distribute the described software and documentation, collectively referred to as the "Software."
LICENSE: Licensor grants you (the "Licensee") the right to use the Software in conjunction with MagTek products. LICENSEE MAY NOT COPY, MODIFY, OR TRANSFER THE SOFTWARE IN WHOLE OR IN PART EXCEPT AS EXPRESSLY PROVIDED IN THIS AGREEMENT. Licensee may
not decompile, disassemble, or in any other manner attempt to reverse engineer the Software. Licensee shall not tamper with, bypass, or alter any security features of the software or attempt to do so.
TRANSFER: Licensee may not transfer the Software or license to the Software to another party without the prior written authorization of the Licensor. If Licensee transfers the Software without authorization, all rights granted under this Agreement are automatically terminated.
COPYRIGHT: The Software is copyrighted. Licensee may not copy the Software except for archival purposes or to load for execution purposes. All other copies of the Software are in violation of this Agreement.
TERM: This Agreement is in effect as long as Licensee continues the use of the Software. The Licensor also reserves the right to terminate this Agreement if Licensee fails to comply with any of the terms, conditions, or restrictions contained herein. Should Licensor terminate this Agreement due to Licensee's failure to comply, Licensee agrees to return the Software to Licensor. Receipt of returned Software by the Licensor shall mark the termination.
LIMITED WARRANTY: Licensor warrants to the Licensee that the disk(s) or other media on which the Software is recorded are free from defects in material or workmanship under normal use.
THE SOFTWARE IS PROVIDED AS IS. LICENSOR MAKES NO OTHER WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Because of the diversity of conditions and hardware under which the Software may be used, Licensor does not warrant that the Software will meet Licensee specifications or that the operation of the Software will be uninterrupted or free of errors.
IN NO EVENT WILL THE LICENSOR BE LIABLE FOR ANY DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS, OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE, OR INABILITY TO USE THE SOFTWARE. Licensee's sole remedy in
the event of a defect in material or workmanship is expressly limited to replacement of the Software disk(s) if applicable.
GOVERNING LAW: If any provision of this Agreement is found to be unlawful, void, or unenforceable, that provision shall be removed from consideration under this Agreement and will not affect the enforceability of any of the remaining provisions. This Agreement shall be governed by the laws of the State of California and shall inure to the benefit of MagTek, Incorporated, its successors or assigns.
ACKNOWLEDGMENT: LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS ALL OF ITS TERMS, CONDITIONS, AND RESTRICTIONS, AND AGREES TO BE BOUND BY THEM. LICENSEE ALSO AGREES THAT THIS AGREEMENT SUPERSEDES ANY AND ALL VERBAL AND WRITTEN COMMUNICATIONS BETWEEN LICENSOR AND LICENSEE OR THEIR ASSIGNS RELATING TO THE SUBJECT MATTER OF THIS AGREEMENT.
QUESTIONS REGARDING THIS AGREEMENT SHOULD BE ADDRESSED IN WRITING TO MAGTEK, INCORPORATED, ATTENTION: CUSTOMER SUPPORT, AT THE ADDRESS LISTED IN THIS DOCUMENT, OR E-MAILED TO .
DEMO SOFTWARE / SAMPLE CODE: Unless otherwise stated, all demo software and sample code are to be used by Licensee for demonstration purposes only and MAY NOT BE incorporated into any production or live environment. The PIN Pad sample implementation is for software PIN Pad test purposes only and is not PCI compliant. To meet PCI compliance in production or live environments, a third-party PCI compliant component (hardware or software-based) must be used.
The Installation and Operation Manual is the primary reference for deploying and running DynaProx. It covers planning, mounting and cabling, configuration, day-to-day contactless (and optional barcode) operation, routine maintenance, and guidance for developers integrating the device. Use the reference sections below to jump to a topic.
Reference Section
Information Available
Overview of DynaProx, its contactless transaction methods (EMV Contactless, NFC Contactless, MIFARE®, and optional barcode on BCR models), intended audience, and how to use this manual.
The Installation and Operation Manual is the primary reference for deploying and running DynaFlex II Go. It covers planning, physical installation, configuration, day-to-day operation across tap, swipe, dip, and optional barcode, the device's LED and audio indicators, routine maintenance, and guidance for developers building custom software. Use the reference sections below to jump to a topic.
Reference Section
Information Available
Overview of DynaFlex II Go, its supported transaction methods (tap, swipe, dip, and optional barcode), model variants, intended audience, and how to use this manual.
MagTek warrants that the products sold pursuant to this Agreement will perform in accordance with MagTek’s published specifications. This warranty shall be provided only for a period of one year from the date of the shipment of the product from MagTek (the “Warranty Period”). This warranty shall apply only to the “Buyer” (the original purchaser, unless that entity resells the product as authorized by MagTek, in which event this warranty shall apply only to the first repurchaser).
During the Warranty Period, should this product fail to conform to MagTek’s specifications, MagTek will, at its option, repair or replace this product at no additional charge except as set forth below. Repair parts and replacement products will be furnished on an exchange basis and will be either reconditioned or new. All replaced parts and products become the property of MagTek. This limited warranty does not include service to repair damage to the product resulting from accident, disaster, unreasonable use, misuse, abuse, negligence, or modification of the product not authorized by MagTek. MagTek reserves the right to examine the alleged defective goods to determine whether the warranty is applicable.
Without limiting the generality of the foregoing, MagTek specifically disclaims any liability or warranty for goods resold in other than MagTek’s original packages, and for goods modified, altered, or treated without authorization by MagTek.
Service may be obtained by delivering the product during the warranty period to MagTek (1710 Apollo Court, Seal Beach, CA 90740). If this product is delivered by mail or by an equivalent shipping carrier, the customer agrees to insure the product or assume the risk of loss or damage in transit, to prepay shipping charges to the warranty service location, and to use the original shipping container or equivalent. MagTek will return the product, prepaid, via a three (3) day shipping service. A Return Material Authorization (“RMA”) number must accompany all returns. Buyers may obtain an RMA number by contacting MagTek Support Services at (562) 546-6800.
The guidelines in the following sections are intended to help project planners and system administrators plan for the physical and logical requirements of deploying and using DynaProx products. The most effective way to ensure smooth deployment of a solution is to consider these factors before receiving the device.
Determine what type of host DynaProx will connect to. For a list of supported device types and operating systems, see . When planning, be sure to include any additional support or devices required by the host and DynaProx, such as physical locations, mounting, power connections, and charging cradles.
Determine what connection the host will use to communicate with the device. Depending on the device model (see), the connection can be USB or RS-232.
A sample iOS application that works with the MTUSDK to demonstrate communication with MagTek card readers and provide a user experience that simulates a transaction.
A utility for demonstrating and testing barcode-reading operations on DynaFlex BCR and DynaProx BCR devices (models equipped with a barcode reader).
An Android Software Development Kit that provides tools, a sample application, sample code, and documentation for developers creating solutions for MagTek MMS devices on Android hosts.
An iOS SDK that provides the necessary tools, sample application, sample code, and documentation for developers building iOS solutions for MagTek MMS devices.
A Linux-based SDK that includes sample applications, code, and documentation for building software solutions for MagTek MMS devices on Linux hosts.
A Windows SDK that provides sample code, documentation, and a demo application to help developers integrate MagTek MMS devices into Windows-based host applications.
Description
Summary
An iOS app that is part of a suite of tools for remotely configuring and updating a large number of geographically dispersed MagTek readers across an enterprise, including the DynaFlex II Go and other Dyna devices.
A Windows application that automates the configuration and firmware updates for a wide range of MagTek readers, including all DynaFlex II models, across an enterprise deployment.
Description
Summary
A configuration utility for a variety of DynaFlex and DynaProx devices used to change or update EMV configurations, run demo EMV transactions, upload bitmap images, and parse TLV data.
A demo web page designed to illustrate the functionality of the MagneFlex Browser, which can be launched on Android, iOS, and Windows versions of the browser.
Description
Summary
A downloadable package of Magensa Universal EMV configuration tags (TLV terminal settings) for provisioning DynaProx devices.
Description
Summary
A full-function HTML browser application for Windows x64, featuring a developer mode for debugging JavaScript, improved HTML/framework rendering, and tabbed browsing.
A full-function HTML browser application for Windows x86, featuring the same developer tools and modern rendering capabilities as the x64 version.
Description
Summary
A lightweight middleware application that manages communications between a POS application and the hardware for DynaFlex and DynaProx products, streamlining data processing.
A sample Android application provided with the MTUSDK that demonstrates communication with MagTek card readers (including the DynaFlex II Go) and simulates a transaction process.
EACH BUYER UNDERSTANDS THAT THIS MAGTEK PRODUCT IS OFFERED AS-IS. MAGTEK MAKES NO OTHER WARRANTY, EXPRESS OR IMPLIED, AND MAGTEK DISCLAIMS ANY WARRANTY OF ANY OTHER KIND, INCLUDING ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IF THIS PRODUCT DOES NOT CONFORM TO MAGTEK’S SPECIFICATIONS, THE SOLE REMEDY SHALL BE REPAIR OR REPLACEMENT AS PROVIDED ABOVE. MAGTEK’S LIABILITY, IF ANY, SHALL IN NO EVENT EXCEED THE TOTAL AMOUNT PAID TO MAGTEK UNDER THIS AGREEMENT. IN NO EVENT WILL MAGTEK BE LIABLE TO THE BUYER FOR ANY DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS, OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF, OR INABILITY TO USE, SUCH PRODUCT, EVEN IF MAGTEK HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY CLAIM BY ANY OTHER PARTY.
EXCEPT AS PROVIDED IN THE SECTIONS RELATING TO MAGTEK’S LIMITED WARRANTY, MAGTEK’S LIABILITY UNDER THIS AGREEMENT IS LIMITED TO THE CONTRACT PRICE OF THIS PRODUCT.
MAGTEK MAKES NO OTHER WARRANTIES WITH RESPECT TO THE PRODUCT, EXPRESSED OR IMPLIED, EXCEPT AS MAY BE STATED IN THIS AGREEMENT, AND MAGTEK DISCLAIMS ANY IMPLIED WARRANTY, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
MAGTEK SHALL NOT BE LIABLE FOR CONTINGENT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES TO PERSONS OR PROPERTY. MAGTEK FURTHER LIMITS ITS LIABILITY OF ANY KIND WITH RESPECT TO THE PRODUCT, INCLUDING NEGLIGENCE ON ITS PART, TO THE CONTRACT PRICE FOR THE GOODS.
MAGTEK’S SOLE LIABILITY AND BUYER’S EXCLUSIVE REMEDIES ARE STATED IN THIS SECTION AND IN THE SECTION RELATING TO MAGTEK’S LIMITED WARRANTY.
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) This device must accept any interference received, including interference that may cause undesired operation.
This digital apparatus does not exceed the Class B limits for radio noise from digital apparatus set out in the Radio Interference Regulations of the Canadian Department of Communications.
Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la classe B prescrites dans le Réglement sur le brouillage radioélectrique édicté par le ministère des Communications du Canada.
This Class B digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe B est conformé à la norme NMB-003 du Canada.
This device complies with Industry Canada licence-exempt RSS standard(s). Operation is subject to the following two conditions: (1) This device may not cause interference, and (2) This device must accept any interference, including interference that may cause undesired operation of the device.
Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorisée aux deux conditions suivantes: (1) L'appareil ne doit pas produire de brouillage, et (2) L'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d'en compromettre le fonctionnement.
This product is recognized per Underwriter Laboratories and Canadian Underwriter Laboratories 1950.
Testing for compliance with CE requirements was performed by an independent laboratory. The unit under test was found compliant with standards established for Class B devices.
Hereby, MagTek Inc. declares that the radio equipment types Wideband Transmission System (802.11 wireless and Bluetooth Low Energy), and Non-Specific Short Range Device (contactless) are in compliance with Directive 2014/53/EU. The full text of the EU declarations of conformity is available at the following internet addresses:
Testing for compliance with AS/NZS standards was performed by a registered and accredited laboratory. The unit under test was found compliant with standards established under AS/NZS CISPR 32 (2013), AS/NZS 4268 Table 1, Row 59 DTS 2400-2483MHz SRD (802.11), and AS/NZS 4268 (2017) Table 1,
Row 43 13.553-13.567MHz (contactless reader).
This product is recognized per UL 60950-1, 2nd Edition, 2011-12-19 (Information Technology Equipment - Safety - Part 1: General Requirements), CSA C22.2 No. 60950-1-07, 2nd Edition, 2011-12 (Information Technology Equipment - Safety - Part 1: General Requirements).
When ordered as RoHS compliant, this product meets the Electrical and Electronic Equipment (EEE) Reduction of Hazardous Substances (RoHS) Directive (EU) 2015/863 amending Annex II to Directive 2011/65/EU. The marking is clearly recognizable, either as written words like “Pb-free,” “lead-free,” or as another clear symbol ( ).
PCI Security Standards Council, LLC (“PCI SSC”) has approved this PIN Transaction Security Device to be in compliance with PCI SSC’s PIN Security Requirements.
When granted, PCI SSC approval is provided by PCI SSC to ensure certain security and operational characteristics important to the achievement of PCI SSC’s goals, but PCI SSC approval does not under any circumstances include any endorsement or warranty regarding the functionality, quality or performance of any particular product or service. PCI SSC does not warrant any products or services provided by third parties. PCI SSC approval does not under any circumstances include or imply any product warranties from PCI SSC, including, without limitation, any implied warranties of merchantability, fitness for purpose, or non-infringement, all of which are expressly disclaimed by PCI SSC. All rights and remedies regarding products and services which have received PCI SSC approval shall be provided by the party providing such products or services, and not by PCI SSC.
This product has been evaluated by multiple safety certification agencies, including Underwriters Laboratories (UL) and the United States Federal Communications Commission (FCC Class A and Class B), and is designed to protect both the user and the device. This document is written specifically to work in conjunction with these safety and integrity features to protect the user and the device. It is very important to follow all steps in the product documentation carefully, in the order in which they are described, and at the recommended times. Failure to do so could result in personal injury, and / or cause damage to the device, and / or void the product warranty.
IMPORTANT: YOU SHOULD CAREFULLY READ ALL THE TERMS, CONDITIONS AND RESTRICTIONS OF THIS LICENSE AGREEMENT BEFORE INSTALLING THE SOFTWARE PACKAGE. YOUR INSTALLATION OF THE SOFTWARE PACKAGE PRESUMES YOUR ACCEPTANCE OF THE TERMS, CONDITIONS, AND RESTRICTIONS CONTAINED IN THIS AGREEMENT. IF YOU DO NOT AGREE WITH THESE TERMS, CONDITIONS, AND RESTRICTIONS, PROMPTLY RETURN THE SOFTWARE PACKAGE AND ASSOCIATED DOCUMENTATION TO THE ADDRESS IN THIS DOCUMENT, ATTENTION: CUSTOMER SUPPORT.
TERMS, CONDITIONS, AND RESTRICTIONS
MagTek, Incorporated (the "Licensor") owns and has the right to distribute the described software and documentation, collectively referred to as the "Software."
LICENSE: Licensor grants you (the "Licensee") the right to use the Software in conjunction with MagTek products. LICENSEE MAY NOT COPY, MODIFY, OR TRANSFER THE SOFTWARE IN WHOLE OR IN PART EXCEPT AS EXPRESSLY PROVIDED IN THIS AGREEMENT. Licensee may not decompile, disassemble, or in any other manner attempt to reverse engineer the Software. Licensee shall not tamper with, bypass, or alter any security features of the software or attempt to do so.
TRANSFER: Licensee may not transfer the Software or license to the Software to another party without the prior written authorization of the Licensor. If Licensee transfers the Software without authorization, all rights granted under this Agreement are automatically terminated.
COPYRIGHT: The Software is copyrighted. Licensee may not copy the Software except for archival purposes or to load for execution purposes. All other copies of the Software are in violation of this Agreement.
TERM: This Agreement is in effect as long as Licensee continues the use of the Software. The Licensor also reserves the right to terminate this Agreement if Licensee fails to comply with any of the terms, conditions, or restrictions contained herein. Should Licensor terminate this Agreement due to Licensee's failure to comply, Licensee agrees to return the Software to Licensor. Receipt of returned Software by the Licensor shall mark the termination.
LIMITED WARRANTY: Licensor warrants to the Licensee that the disk(s) or other media on which the Software is recorded are free from defects in material or workmanship under normal use.
THE SOFTWARE IS PROVIDED AS IS. LICENSOR MAKES NO OTHER WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Because of the diversity of conditions and hardware under which the Software may be used, Licensor does not warrant that the Software will meet Licensee specifications or that the operation of the Software will be uninterrupted or free of errors.
IN NO EVENT WILL LICENSOR BE LIABLE FOR ANY DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS, OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE, OR INABILITY TO USE THE SOFTWARE. Licensee's sole remedy in
the event of a defect in material or workmanship is expressly limited to replacement of the Software disk(s) if applicable.
GOVERNING LAW: If any provision of this Agreement is found to be unlawful, void, or unenforceable, that provision shall be removed from consideration under this Agreement and will not affect the enforceability of any of the remaining provisions. This Agreement shall be governed by the laws of the State of California and shall inure to the benefit of MagTek, Incorporated, its successors or assigns.
ACKNOWLEDGMENT: LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS ALL OF ITS TERMS, CONDITIONS, AND RESTRICTIONS, AND AGREES TO BE BOUND BY THEM. LICENSEE ALSO AGREES THAT THIS AGREEMENT SUPERSEDES ANY AND ALL VERBAL AND WRITTEN COMMUNICATIONS BETWEEN LICENSOR AND LICENSEE OR THEIR ASSIGNS RELATING TO THE SUBJECT MATTER OF THIS AGREEMENT.
QUESTIONS REGARDING THIS AGREEMENT SHOULD BE ADDRESSED IN WRITING TO MAGTEK, INCORPORATED, ATTENTION: CUSTOMER SUPPORT, AT THE ADDRESS LISTED IN THIS DOCUMENT, OR E-MAILED TO feedback@magtek.com.
DEMO SOFTWARE / SAMPLE CODE: Unless otherwise stated, all demo software and sample code are to be used by Licensee for demonstration purposes only and MAY NOT BE incorporated into any production or live environment. The PIN Pad sample implementation is for software PIN Pad test purposes only and is not PCI compliant. To meet PCI compliance in production or live environments, a third-party PCI compliant component (hardware or software-based) must be used.
7811-3
Location of embossed characters
7811-4
Location of tracks 1 & 2
7811-5
Location of track 3
7811-6
Magnetic stripe - high coercivity
7813
Financial transaction cards
Measurement - 0.223"
Track
Recording Density (bits per inch)
Character Configuration (including parity bit)
Information Content (including control characters)
0.110"
1 IATA
210
76 alphanumeric data characters between Format Code and Discretionary Data.
SS
FC
PAN
FS
Name
FS
Additional data
Discretionary Data
ES
SS: Start Sentinel - %
FC: Format Code - ^
PAN: Primary Account Number (19 digits max.)
FS: Field Separator
NAME: Name (26 alphanumeric characters max.)
ADDITIONAL DATA: Number of characters:
Expiration Date (YYMM) - 4
Service Code - 3
DISCRETIONARY DATA: Number of characters:
PVKI - PIN Verification Key Number
PVV or Offset - PIN Verification Value
CVV or CVC - Card Verification Value, Card Vakudation Code
ES: End Sentinel - ?
LRC: Logitudinal Redundancy Check character
37 data characters between PAN and Discretionary Data.
SS
PAN
FS
Additional data
Discretionary Data
ES
LRC
SS: Start Sentinel - Hex B - ;
PAN: Primary Account Number (19 digits max.)
FS: Field Separator - Hex D - =
ADDITIONAL DATA: Number of characters:
Expiration Date (YYMM) - 4
Service Code - 3
DISCRETIONARY DATA: Number of characters:
PVKI - PIN Verification Key Number
PVV or Offset - PIN Verification Value
CVV or CVC - Card Verification Value, Card Vakudation Code
ES: End Sentinel - Hex F - ?
LRC: Logitudinal Redundancy Check character
104 numeric data characters between Format Code and Additional Data.
SS
FC
PAN
FS
USE AND SECURITY DATA
Additional data
ES
LRC
SS: Start Sentinel - Hex B - ;
PAN: Primary Account Number (19 digits max.)
FS: Field Separator - Hex D - =
USE AND SECURITY DATA - Number of characters
Country Code (optional) - 3
Currency Code - 3
Currency Exponent - 1
Amount Authorized per Cycle - 4
Amount Remaining this Cycle - 4
Cycle Begin (Validity Date) - 4
Cycle Length - 2
Retry Count - 1
PIN Control Parameters (optional) - 6
Interchange Controls - 1
PAN Service Restriction - 2
SAN-1 Service Restriction - 2
SAN-2 Service Restriction - 2
Expiration Date (optional) - 4
Card Sequence Number - 1
Card Security Number (optional) - 9
ADDITIONAL DATA: Number of characters:
First subsidiary account number (optional)
Second subsidiary account number (optional)
Relay marker - 1
ES: End Sentinel - Hex F - ?
LRC: Logitudinal Redundancy Check character
FC: Format Code - (2 digits) (in place of optional field)
7810
Physical characteristics of credit card size document
7811-1
Embossing
7811-2

Magnetic stripe - low coercivity
Determine how the device will be physically presented to the cardholder. If the device is mounted, make sure there is adequate clearance for cardholders to swipe, insert, and tap. If the solution design includes metal objects anywhere near the device, including metal enclosures, make sure that at all points the metal is no further forward than 15mm below the face of the device. Proximity to metal can adversely affect the device’s performance.
Determine how the device should be configured and specify that configuration when ordering the device. A full list of configurable options is documented in DynaProx Programmer’s Manual.
Select and configure a secure workstation that advanced operators will use to configure and/or update the device. The workstation must be configured as follows:
Available USB port.
A secure means of obtaining files, either via the network (such as SFTP) or via removable media, such as USB flash drives. This is required for installing software tools, copying firmware files, etc. If you are using Magensa Services, make sure the secure workstation has an internet connection and has all the required Magensa Remote Services software components installed.
installed, which advanced operators can use to configure and test the device.
installed, which advanced operators can use to update the device’s firmware.
Determine the final set of tools advanced operators will use to configure, test, and update the device. This documentation uses the as an example for configuring the device; it can be used for initial pre-deployment testing and development, and as sample code showing how to communicate with the device, but the full solution may call for customized, solution-specific software for configuring the device and updating firmware.
Determine how to inspect devices upon arrival, upon installation, and periodically during live usage, to ensure malicious individuals have not tampered with them. Details about inspection are provided in .
Develop procedures for maintaining the device(s). Detailed guidance is provided in .
Determine how to train operators. For example, training may include information extracted from , , and .
Review the device’s PCI Security Policy, posted to the PCI web site under Approved PIN Transaction Security (PTS) Devices, for additional information about using the device securely.
What to review before deployment: host and operating-system compatibility (Windows, Android, and iOS via USB iAP2), USB/USB iAP2 and RS-232 connectivity and power options, and mounting for kiosks, unattended terminals, and the optional countertop stand.
Safe handling, operating and storage environment limits (including the IP66/IK08 ratings for harsh conditions), ESD precautions, and tamper-evidence checks that keep the secure module valid.
Step-by-step physical setup — mounting to ATM/kiosk points or the optional stand, cabling and cable management, connecting to the host, and powering on.
How to configure device settings and behavior, connection modes, and security/Passcode Lock options (manual entry, QR code, and contactless workflows), plus firmware and configuration updates.
How to run transactions day to day — contactless tap and optional barcode/QR flows — and the device responses and audio cues to expect.
Cleaning and care, routine tamper inspection, and basic troubleshooting to keep the device in service.
Where developers go next: the Commands Programmer's Manual, SDKs and connection protocols (USB HID, USB iAP2, RS-232), and Magensa gateway integration for decryption and processing.
Reference material — technical specifications, standards and compliance (contactless EMV 3.0, PCI PTS POI 6.x), part numbers, and status/error-code references.
What to review before deployment: host and operating-system compatibility (Windows, Android, iOS), USB and Bluetooth® LE connectivity options, and power, accessory, and mounting/enclosure considerations.
Safe handling, operating and storage environment limits, ESD precautions, and tamper-evidence checks that keep the device's secure module valid.
Step-by-step physical setup — mounting, connecting to the host over USB or pairing over Bluetooth® LE, powering on, and verifying the connection.
How to configure device settings and behavior, connection modes, and security/Passcode Lock options, plus updating firmware, CAPKs, and EMV/application settings.
How to run transactions day to day — the tap, dip, swipe, and optional barcode/QR flows — and the device responses to expect.
The meaning of the device's LED indicators and audible (beeper) cues, and how operators and cardholders interact with the reader during a transaction.
Cleaning and care, routine tamper inspection, and basic troubleshooting to keep the device in service.
Where developers go next: the Commands Programmer's Manual, SDKs and connection protocols (USB HID, USB iAP2, Bluetooth® LE), and Magensa gateway integration for decryption and processing.
Reference material — technical specifications, standards and compliance (PCI PTS 6.x SCR, EMV), part numbers, and status/error-code references.
Download the software for developing with and managing the DynaFlex II PED PIN-entry reader. This page brings together the MagTek Universal SDK (MTUSDK) for MMS devices on Android, iOS, Java, Linux, and Windows, along with the MagneFlex Browser and browser apps, demo and sample applications, MagneFlex middleware, and the Reader Management System clients for enterprise firmware and configuration updates.
Description
Summary
A web console that accepts an OID and command data and returns the data to use for MTUSDK configuration commands on DynaFlex devices.
The MagneFlex Browser is a full function browser this free development tool can be white-labelled and provides a turnkey integration solution for web applications, working with MagTek hardware and services. Sites developed in HTML 5 with device responsive views will work seamlessly in this browser allowing an app to respond to devices whether they are tablets or phones.
DynaFlex II Go is a secure card reader authenticator in a small form factor that is ready to accept tap, swipe, and dip payments in a wide variety of retail environments. The small form factor is ready for countertop and mobile devices with USB or Bluetooth® LE connection. Start accepting mobile wallets including Samsung® Pay, Google® Pay and Apple® Pay via NFC Contactless or accept card payments via EMV® Contactless, EMV Contact Chip, and magnetic stripe.
Check the overall form factor for signs of attempted entry or tampering. The form factor is a smooth shell. The seam between the top and bottom shells are molded together. There are no additional electronics or wires. Any breaks in the plastic, scuffs, or damage could be signs of physical tampering and should be reported. Look for any added components, size, or weight: Dimensions: 2.76 in.x2.57 in.x0.79 in. (70.10mm x 65.3mm x20.1mm) DynaFlex II Go (w/BCR and Bluetooth LE): 92 grams, DynaFlex II Go (with Bluetooth LE): 90 grams.
Top of Device: This is the location of the EMV Chip Card insert position and magstripe swipe card reader slot.
Payment Methods: Directional icons for magstripe, EMV chip insert, and contactless tap landing pad are printed on the device front.
Chip Card Insertion Slot: The card slot for the EMV Contact Chip reader is a smooth, unobstructed path. Other than the contact points that read the chip there are no electronics, mechanics, or wires in the path.
DynaFlex II Go products are PCI PTS v6.x SCR, certified. The packaging is designed to be tamper evident and the closure uses security tape. Any attempt to open the package shows signs of tampering. This document explains how to detect tampering.
The basic form factor of the package is a folded white cardboard box with a cardboard insert where the device is nestled into Korrvu plastic wrap packaging. There are no rips or added materials on the package other than product and Lot labels. The package only has one color ink printed on the package: black. The box is made with corrugated white cardboard.
Certification Compliance Logos: Industry certification logos showing compliance are printed on the back of the package as shown. Manufacturer address is shown.
The front cover of the package lists the product name, MagneSafe Security information, PCI revision information, product read capability icons, QR Codes, and description.
On the left side of the package is printed a list of the package contents and the product label is adhered.
Custom host software uses the same underlying device command set for all DynaProx product connection types. This section provides high-level information about communicating with the device via the various physical connection types in various software development frameworks, and provides pointers to available SDKs, which include sample code. Product documentation and SDKs are available for download by searching for the product name on .
MagTek provides convenient SDKs and corresponding documentation for many programming languages and operating systems. The API libraries included in the SDKs wrap the details of the connection in an interface that conceptually parallels the device’s internal operation, freeing software developers to focus on the business logic, without having to deal with the complexities of platform APIs for connecting to the various available connection types, communicating using the various available protocols, and parsing the various available data formats. Information about using MagTek wrapper APIs is available in separate documentation, including:
Cryptographic check digits (optional) - 6
Discretionary Data
7 bits per character
79 alphanumeric characters
0.110"
ABA
75
5 bits per character
40 numeric characters
0.110"
THRIFT
210
5 bits per character
107 numeric characters
LRC
Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
Consult the dealer or an experienced radio/TV technician for help.
DO NOT remove any of the covers or guards that are fastened with screws. There are no user-serviceable areas within these covers.
DO NOT override or “cheat” electrical or mechanical interlock devices.
DO NOT use EC3000 supplies or cleaning materials for other than their intended purposes.
DO NOT operate the equipment if you or anyone else have noticed unusual noises or odors.
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation! feedback@magtek.com
The documentation is bundled with the SDKs themselves, which include:
The SDKs and corresponding documentation include:
Functions for sending the direct commands described in this manual
Wrappers for commonly used commands that further simplify development
Sample source code to demonstrate how to communicate with the device using the direct commands described in this manual
To download the SDKs and documentation, search developer.magtek.com for “SDK” and select the SDK and documentation for the programming languages and platforms you need or contact MagTek Support Services for assistance.
In addition to the SDK API libraries, software developers also have the option to revert to direct communication with the device using libraries using the operating system’s native USB and serial port libraries. For example, custom software written in Visual Basic or Visual C++ may make API calls to the standard Windows USB HID driver. For more information about sending commands directly, see DynaFlex / DynaProx Programmer’s Manual.
A sample iOS application that works with the MTUSDK to demonstrate communication with MagTek card readers and provide a user experience that simulates a transaction.
A utility for demonstrating and testing barcode-reading operations on DynaFlex BCR and DynaProx BCR devices (models equipped with a barcode reader).
An Android Software Development Kit that provides tools, a sample application, sample code, and documentation for developers creating solutions for MagTek MMS devices on Android hosts.
An iOS SDK that provides the necessary tools, sample application, sample code, and documentation for developers building iOS solutions for MagTek MMS devices.
Contains the necessary tools for software developers who want to create software solutions for MagTek devices to a Windows based host using Java Virtual Machine.
A Linux-based SDK that includes sample applications, code, and documentation for building software solutions for MagTek MMS devices on Linux hosts.
A Windows SDK that provides sample code, documentation, and a demo application to help developers integrate MagTek MMS devices into Windows-based host applications.
Description
Summary
A full-featured Android browser designed for app development, enabling web apps to communicate with hardware without needing plugins, available on Google Play and the Amazon app store.
An iOS app that is part of a suite of tools for remotely configuring and updating a large number of geographically dispersed MagTek readers across an enterprise, including the DynaFlex II Go and other Dyna devices.
Description
Summary
A configuration utility for a variety of DynaFlex and DynaProx devices used to change or update EMV configurations, run demo EMV transactions, upload bitmap images, and parse TLV data.
A demo web page designed to illustrate the functionality of the MagneFlex Browser, which can be launched on Android, iOS, and Windows versions of the browser.
Description
Summary
A full-function HTML browser application for Windows x64, featuring a developer mode for debugging JavaScript, improved HTML/framework rendering, and tabbed browsing.
A full-function HTML browser application for Windows x86, featuring the same developer tools and modern rendering capabilities as the x64 version.
Description
Summary
A lightweight middleware application that manages communications between a POS application and the hardware for DynaFlex and DynaProx products, streamlining data processing.
A Windows application that automates the configuration and firmware updates for a wide range of MagTek readers, including all DynaFlex II models, across an enterprise deployment.
A sample Android application provided with the MTUSDK that demonstrates communication with MagTek card readers (including the DynaFlex II Go) and simulates a transaction process.
Front Face Contactless Landing Zone: The Contactless landing zone is a smooth front cover with no moving parts and only the contactless symbol in the landing zone. Contactless indicator mark orientation may vary depending on installation.
Front Face (BCR ONLY) Barcode Reader: In barcode reader models (BCR), a barcode reader is along the right-facing side of the reader with a QR Code icon and directional arrow.
Front Face LED Feedback: There are four LED lights. These provide signals to the user. See installation and operation manual for complete LED signaling.
Front Face Devices Without Barcode Reader: These devices will have no lens or barcode icons.
Right-facing Side of Device Pushbutton: There is a tactile button with no other extraneous parts.
Bottom of Device USB-C Cable: There is a USB-C receptacle on bottom of the device. The USB-C cable is provided to power and charge. Ensure there are no extraneous cables. (Cable not shown to scale.)
Back Side of Device Product Label: The product label is located on the underside of the device. The Serial Number, Rev, Date, Part number (PN), and Hardware PN (HW) are listed as appropriate.
Back Side of Device Certificate Logos: Imprints in the plastic form factor of certification logos and patent information are listed.
To check for PCI Validation check the Hardware and Firmware ID. Hardware ID is printed on the label. The Firmware ID is accessible via the device. Go to the PCI compliance web page and search for MagTek, and find the product name, DynaFlex II Go. Compare the Hardware ID and Firmware ID: https://www.pcisecuritystandards.org/assessors_and_solutions/ pin_transaction_devices
As part of your inspection, include the following for your device inspection audit:
Be certain to have a list of the devices and include the details listed on the product label.
It may be helpful to take photos of the front, back, and sides of each device.
Be certain to check device part numbers, serial numbers, and IDs and check physical connections. Use the chart below as a checklist to inspect the device for signs of tampering.
Are there signs of tampering:
Signs of tampering
Site Inspection
YES
NO
FCC INFORMATION
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) This device must accept any interference received, including interference that may cause undesired operation.
CANADIAN DECLARATION OF CONFORMITY
This digital apparatus does not exceed the Class B limits for radio noise from digital apparatus set out in the Radio Interference Regulations of the Canadian Department of Communications.
Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la classe B prescrites dans le Réglement sur le brouillage radioélectrique édicté par le ministère des Communications du Canada.
This Class B digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe B est conformé à la norme NMB-003 du Canada.
INDUSTRY CANADA (IC) RSS
This device complies with Industry Canada licence-exempt RSS standard(s). Operation is subject to the following two conditions: (1) This device may not cause interference, and (2) This device must accept any interference, including interference that may cause undesired operation of the device.
Le présent appareil est conforme aux CNR d’Industrie Canada applicables aux appareils radio exempts de licence. L’exploitation est autorisée aux deux conditions suivantes: (1) L’appareil ne doit pas produire de brouillage, et (2) L’utilisateur de l’appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d’en compromettre le fonctionnement.
CUR/UR
This product is recognized per Underwriter Laboratories and Canadian Underwriter Laboratories 1950.
CE STANDARDS
Testing for compliance with CE requirements was performed by an independent laboratory. The unit under test was found compliant with standards established for Class B devices.
EU STATEMENT
Hereby, MagTek Inc. declares that the radio equipment types Wideband Transmission System (802.11 wireless and Bluetooth® Low Energy), and Non-Specific Short Range Device (contactless) are in compliance with Directive 2014/53/EU. The full text of the EU declarations of conformity is available at the following Internet addresses: https://www.magtek.com/content/documentationfiles/d998200650.pdf
Safety
This product has been tested to IEC 62368-1 -Audio/Video, information and communication technology equipment - Part 1: General Requirements plus U.S., Canadian, Australian & New Zealand National Deviations by an ISO 17025 Accredited Testing Laboratory.
ROHS STATEMENT
When ordered as RoHS compliant, this product meets the Electrical and Electronic Equipment (EEE) Reduction of Hazardous Substances (RoHS) Directive (EU) 2015/863 amending Annex II to Directive 2011/65/EU. The marking is clearly recognizable, either as written words like “Pb-free,” “lead-free,” or as another clear symbol ( Pb ).
PCI STATEMENT
PCI Security Standards Council, LLC (“PCI SSC”) has approved this PIN Transaction Security Device to be in compliance with PCI SSC’s PIN Security Requirements.
When granted, PCI SSC approval is provided by PCI SSC to ensure certain security and operational characteristics important to the achievement of PCI SSC’s goals, but PCI SSC approval does not under any circumstances include any endorsement or warranty regarding the functionality, quality or performance of any particular product or service. PCI SSC does not warrant any products or services provided by third parties. PCI SSC approval does not under any circumstances include or imply any product warranties from PCI SSC, including, without limitation, any implied warranties of merchantability, fitness for purpose, or non-infringement, all of which are expressly disclaimed by PCI SSC. All rights and remedies regarding products and services which have received PCI SSC approval shall be provided by the party providing such products or services, and not by PCI SSC.
UKCA STATEMENT
Hereby, MagTek Inc. declares that the radio equipment types Wideband Transmission System (Wireless LAN and Bluetooth Low Energy), and Non-Specific Short Range Device (contactless) are in compliance with Radio Equipment Regulations 2017 Directive S.I.2017:1206. The full text of the UKCA declarations of conformity is available at the following Internet addresses: https://www.magtek.com/content/documentationfiles/d998200651.pdf

The front of the package lists the product name, category, PCI certification, and Security Tape.
Security tape wraps onto the bottom of the package from the front flap of the package.
Adhered
Here security tape is applied and secured. Wrapping front to bottom of package.
Tape
Tape is removed VOID and OPENED appear on tape.
Package
Security tape wraps onto the bottom of the package from the front flap of the package.
Bottom
Security Tape: The Security Tape wraps from the front flap to the bottom of the package. Make certain there are no signs of tampering.
Lot Label: The lot label is placed on the bottom of the box. Make certain there are no false labels added or tampering.
Inside
DynaFlex II Go products are nestled inside the package with Korrvu packaging that uses cling wrap to hold the device securely in place for transit. The cling wrap is attached to an insert that has thumb-hole cuts on either side to make it easier to remove from the outer packaging. The package includes the device, cable(s), device inspection document, and quick installation guide.
To check for PCI Validation check the Hardware and Firmware ID. Hardware ID is printed on the label. The Firmware ID is accessible via the device. Go to the PCI compliance web page and search for MagTek, and find the product name, DynaFlex II Go. Compare the Hardware ID and Firmware ID: https:// www.pcisecuritystandards.org/assessors_and_solutions/pin_transaction_devices
As part of your inspection, include the following for your device inspection audit:
Be certain to have a list of the devices and include the details listed on the product label.
It may be helpful to take photos of the front, back, and sides of each device.
Be certain to check device part numbers, serial numbers, and IDs and check physical connections. Use the chart below as a checklist to inspect the device for signs of tampering.
Are there signs of tampering:
Signs of tampering
YES
NO



This page provides access to the essential software resources for developing with and managing the DynaFlex II Go secure card reader. Here you will find Software Development Kits (SDKs) for integrating the device into applications across Android, iOS, and Windows platforms. Additionally, you can download utility programs for device demonstration and configuration, as well as specialized browser applications and the Reader Management System (RMS) for remote, large-scale device management.
Description
Summary
A sample console application for Linux that demonstrates how to update DynaFlex II Go device firmware, update production firmware via RS2 web service, and update EMV configurations (tags and CAPK) from an XML file.
The MagneFlex Browser is a full function browser this free development tool can be white-labelled and provides a turnkey integration solution for web applications, working with MagTek hardware and services. Sites developed in HTML 5 with device responsive views will work seamlessly in this browser allowing an app to respond to devices whether they are tablets or phones.
This page provides essential software resources for developing with and managing the oDynamo secure card reader, including platform-specific SDKs for integration across Linux, Windows, .NET, and Java, as well as utility programs for device demonstration, remote configuration, and enterprise‑scale firmware and setting updates.
Description
Summary
A sample code package that demonstrates how to communicate with the oDynamo reader using the MagTek Common Message Structure (MTCMS) in a Linux environment.
Upon receiving the device, inspect it to make sure it originated from an authentic source and has not been tampered with. For details, see DynaProx / DynaProx BCR Device Inspection.
From device delivery through assembly, shipping, installation, usage, and maintenance, the device must not be exposed to conditions outside the ratings in Appendix A: Technical Specifications.
If the device is exposed to cold temperatures, adjust it to warmer temperatures gradually to avoid condensation, which can interfere with the operation of the device or cause permanent damage.
Do not drop or shake the device.
For information about ongoing maintenance of the device, such as cleaning, see Maintenance.
DynaProx products implement active tamper detection, which uses a small amount of electricity even when the device is completely powered off. When unpowered by an external power supply, the device powers its active tamper detection circuitry using its non-rechargeable backup battery. This provides 5 years of backup shelf life across the entire life of the device. If the backup battery is allowed to completely discharge, the device’s tamper detection engages and locks down the device, and it must be returned to the manufacturer to reset.
To avoid accidental tamper events and to optimally condition the battery, follow these precautions:
Temperature is the most critical factor in extending battery life and preserving battery charge. Store the device at the lowest reasonable temperatures within its specified storage temperature range (see Appendix A Technical Specifications). Storing at temperatures between -30°C to 85°C (-22°F to 185°F) – DynaProx BCR -30°C to 70°C (-22°F to 158°F).
Do not drop or shake the device.
Do not attempt to disassemble the device.
Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
Consult the dealer or an experienced radio/TV technician for help.
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation! feedback@magtek.com
Form Factor - check overall form factor
Front
4 LEDs
EMV/NFC Contactless landing zone
Barcode reader (BCR models only)
Printing and icons
Overall form factor
Sides and Top
Magnetic stripe swipe path
EMV contact card slot
Form factor
Right Facing Side: Push Button
Bottom Side: USB-C port
Cables and charging cradle
USB-C cable and port
Back
Certificate logos imprinted
Form factor
Cable connection
Pushbutton
Labels






🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation! feedback@magtek.com
Form Factor - check overall form factor
Front
Check form factor
Look for signs of tamper
Check printing and no added labels
Left, Right, and Back Sides
Check form factor
Look for signs of tamper
Check printing and no added labels
Check product label
Front Flap
Check Security Tape
Look for signs of tamper
Check printing and no added labels
Check form factor
Bottom
Check Security Tape
Look for signs of tamper
Check printing
Check form factor
Check lot Label







A sample iOS application that works with the MTUSDK to demonstrate communication with MagTek card readers and provide a user experience that simulates a transaction.
An Android Software Development Kit that provides tools, a sample application, sample code, and documentation for developers creating solutions for MagTek MMS devices on Android hosts.
A Linux-based SDK that includes sample applications, code, and documentation for building software solutions for MagTek MMS devices on Linux hosts.
A Windows SDK that provides sample code, documentation, and a demo application to help developers integrate MagTek MMS devices into Windows-based host applications.
An iOS SDK that provides the necessary tools, sample application, sample code, and documentation for developers building iOS solutions for MagTek MMS devices.
Description
Summary
A full-featured Android browser designed for app development, enabling web apps to communicate with hardware without needing plugins, available on Google Play and the Amazon app store.
An iOS app that is part of a suite of tools for remotely configuring and updating a large number of geographically dispersed MagTek readers across an enterprise, including the DynaFlex II Go and other Dyna devices.
Description
Summary
A configuration utility for a variety of DynaFlex and DynaProx devices used to change or update EMV configurations, run demo EMV transactions, upload bitmap images, and parse TLV data.
A demo web page designed to illustrate the functionality of the MagneFlex Browser, which can be launched on Android, iOS, and Windows versions of the browser.
Description
Summary
A full-function HTML browser application for Windows x64, featuring a developer mode for debugging JavaScript, improved HTML/framework rendering, and tabbed browsing.
A full-function HTML browser application for Windows x86, featuring the same developer tools and modern rendering capabilities as the x64 version.
Description
Summary
A lightweight middleware application that manages communications between a POS application and the hardware for DynaFlex and DynaProx products, streamlining data processing.
A Windows application that automates the configuration and firmware updates for a wide range of MagTek readers, including all DynaFlex II models, across an enterprise deployment.
A sample Android application provided with the MTUSDK that demonstrates communication with MagTek card readers (including the DynaFlex II Go) and simulates a transaction process.
A Software Development Kit (SDK) that includes tools, documentation, a demo application, and sample code for developers creating Windows .NET software solutions that include an oDynamo reader.
A developer resource containing instructions and content for software developers who want to create .NET or Java software solutions that include a MagTek Common Message Structure (MTCMS) device connected to a Windows PC.
A developer resource that provides instructions for creating Windows software solutions that include a MagTek Common Message Structure (MTCMS) device connected to a Windows PC, specifically for the Universal Windows Platform (UWP).
Description
Summary
A remote services tool used to perform reconfiguration of oDynamo devices already deployed in the field (contact MagTek support before performing updates).
A suite of apps and source code that automates the ability to configure and update a large quantity of geographically separated MagTek readers across an enterprise deployment, including the oDynamo and other Dyna devices.
Description
Summary
A program that demonstrates card reading for USB HID and keyboard emulation readers, allows users to send configuration commands manually or via text file, and includes the demo application's source code to assist developers.
A sample code package that demonstrates how to use the oDynamo Reader Management System.
Description
Summary
A software utility used for validating the EMV configuration (including EMV tags and Certificate Authority Public Keys) of a MagTek oDynamo or DynaWave reader.
A complete reference for setting up and operating the DynaFlex II PED, covering inspection and handling, installation, day-to-day operation, maintenance, custom software development, and supporting appendices.
Reference Section
Information Available
Overview of the DynaFlex II PED and how to use this manual.
Guidance on unpacking, inspecting, and storing the device before deployment.
Steps for physically installing and connecting the device.
Instructions for powering on and using the device's core functions.
Cleaning, upkeep, and troubleshooting procedures to keep the device running properly.
Guidance for developers building custom applications for the device.
Supplemental reference material, including specifications and additional technical details.
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.
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
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.
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.
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.
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.
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 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
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
Select Exit
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.
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.
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 . 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 .
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 and About Power.
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
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.
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 ). 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 ), 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.
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.
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 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 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 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:
An advanced operator has already made sure DynaFlex II or DynaFlex II PED is configured properly and is connected to the host (see ). 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 How to Power On / Wake Up from Standby Mode / Power Off and 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).
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.
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
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.
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
To tap a contactless card or smartphone, 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 show on-screen text and buttons (see Figure 4-12 below for examples).
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).
Figure 4-12 – Example Contactless Transaction Screens
Figure 4-13 – Tapping a Contactless Card / Smartphone
To tap a contactless NFC Tags / MIFARE Classic / MIFARE DESFire /MIFARE Plus cards, follow these steps:
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.
Devices with a touchscreen display on-screen text and buttons (see Figure 4-12 for examples) via the host.
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).
To scan a barcode, follow these steps:
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 ).
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.
Figure 4-15 – Scanning a Barcode
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:
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.
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.
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.
Figure 4-16 – Enter Card Number
Figure 4-17 – Enter Expiration Date
Figure 4-18 – Enter CVV/CVC/Card ID
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
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
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
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).
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.
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 steps required to resolve it.
Other Colors
Reserved
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.
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.
Battery is critically low, between 3% and 10% charged.
Battery is empty, below 3% charged.
Battery is charging.
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.
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 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 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 How to Enter Card Information Manually).
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
The device shows Please Wait and/or AUTHORIZING PLEASE WAIT .
If the transaction requires a signature, the device prompts for a signature (see How to Use Signature Capture).
The device shows REMOVE CARD .
The device shows THANK YOU .
The device ends the transaction and reports the transaction status to the host.
As a reminder to the cardholder to remove the card, the device beeps continuously until the card is removed.
If the device cannot communicate with the chip card:
The device illuminates LED4 red for a short time.
The device beeps twice.
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).
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).
As a reminder to the cardholder to remove the card, the device double-beeps continuously until the card is removed.
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 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.
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.
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).
The device beeps once.
If the device has a touchscreen:
The device may display PROCESSING .
The device displays REMOVE CARD .
If the transaction requires a signature, the device prompts for a signature (see How to Use Signature Capture).
The device displays THANK YOU .
The device ends the transaction and reports the transaction status to the host.
If the device cannot communicate with the card, smartphone, or other contactless payment device:
The device ends the transaction.
The device illuminates LED4 red, for a brief time.
The device beeps twice.
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).
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).
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”).
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 DynaFlex Products Programmer’s Manual.
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.
The device notifies the host that the transaction has ended with the NFC Tag removed.
Devices with a touchscreen display the prompt SCAN BARCODE .
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.
Hold the barcode in front of the barcode reader camera:
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.
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.
Do not tilt the barcode more than 60 degrees from parallel to the device’s face.
Wait for the device or the host to report the barcode has been read successfully:
Devices with a touchscreen will no longer display the prompt SCAN BARCODE.
The device beeps once.
The device turns off the barcode reader indicator LED.
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.
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).
Verify all the information is correct:
If it is correct, press the Enter button to proceed with the transaction.
If it is correct but the cardholder or operator wishes to stop the transaction, press the Cancel button to completely end the transaction.
If it is not correct, press Cancel button to completely end the transaction, and start the transaction again from the first step.
In This Context
LED1
LED2
LED3
LED4
Active Mode: Not Armed for a Tap Transaction
Power
Connection
Color
Means
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
Color
Means
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
Status Icon
Meaning
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
Battery Power Level and Charge Status Icons
Battery is fully charged.
Battery is OK, between 20% and 95% charged.












































Reserved
Go, going, or went.
LED3 will show status for WebSocket connection: Green connected, yellow Waiting for connection.
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.
Battery is low, between 10% and 20% charged.
During operation, DynaProx devices transition between distinct operating modes, which are important for operators to understand so they can properly control the device:
Powered Off Mode is the shipping and storage mode of the device. No external power is applied to the device through the USB cable or RS-232 cable. In this mode, the device consumes practically no power. To set the device from Powered Off mode to Active mode, connect the device to USB power or RS-232 power.
Active Mode is the device’s normal “awake” state when it is in use. In this mode, LEDs are powered on, and the device is ready to receive commands from the host. To set the device from Active mode to Powered Off mode remove power.
During normal operation, the operator initiates a transaction from the host, and the cardholder interacts with the device. Transaction types may include 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 directs the cardholder, and the transaction flow on the device may differ depending on what the host software specifies and what the cardholder does.
For full host control, the device should not be allowed to run for > = 23 hours without a reset. To accomplish this, have the host application send a reset command twice a day separated by at least one hour.
Example: Host software resets the device at 1 AM and 3AM. This keeps the device from initiating its own reset.
Card Reading provides examples of the cardholder experience for each type of payment. If the device cannot read payment data, the host software may prompt the cardholder to repeat the action or reject the transaction.
As mentioned in , DynaProx models equipped with a barcode reader (BCR) have a similar physical appearance as models without a BCR, as shown in Figure 6-1. BCR models are equipped with a camera and a QR code located on the front side of the device.
DynaProx devices have a user interface composed of two elements: a visual indicator consisting of four mono LEDs and a beeper that produces audible alerts.
DynaProx BCR devices have a user interface composed of three elements: a visual indicator consisting of four mono LEDs, a barcode reader, and a beeper that produces audible alerts.
DynaProx devices do not feature any input components such as buttons or touch screens.
Figure 6-1 – DynaProx and DynaProx BCR
The arrangement of the four mono LEDs on DynaProx and DynaProx BCR devices is illustrated in Figure 6-1. The LEDs are labeled LEDs 1 to 4 and are ordered from left to right on the device.
When DynaProx is powered on, its LEDs will illuminate green, when it is powered off, the LEDs will remain unlit. Figure 6-3 illustrates the on/off status of the LEDs.
Figure 6-3 - LED ON/OFF
DynaProx devices equipped with a bar code reader have a status light that indicates whether the barcode feature is powered on or off.
Figure 6-4 - BCR Light
All DynaProx 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.
This section contains information regarding the operational modes of DynaProx's LEDs, beeper, and BCR light. It is important to note that DynaProx devices are not equipped with batteries. If there is no power supply to the device through the USB cable or RS-232 serial port, all LEDs, along with the BCR light, will not illuminate. In such instances, the user interface will resemble the device as it appears in Figure 6-1.
When the device USB cable is connected to the host USB port, a brief beep will sound and all four LEDs will turn on for half a second, as shown in Figure 6-5. Following this, LED 1 and LED 2 will remain illuminated, while LED 3 and LED 4 will remain unlit. After a duration of 10 seconds, all LEDs will turn off, and the device will enter an idle state. This occurs because the host sets the USB port into suspension mode, prompting the device to enter an idle state.
Figure 6-5 – LED Power on Sequence – USB Power On
When DynaProx is in an idle state, it can be detected by a host through the USB HID port see Figure 6-6. After the host has connected to DynaProx, LED 1 and LED 2 will stay on. The device is in Ready State.
Figure 6-6 - LEDs Status (Idle State) Before Host Detection and LED Status (Ready State) After Connecting to Host
When the device is in ready state, two LEDs will be illuminated see Figure 6-7. When a card is detected only LED 1 will be on. If the device has a BCR and it is enabled, the BCR light will also be turned on see Figure 6-8.
Figure 6-7 - Ready State
Figure 6-8 – Card detected.
When a card is read, all four LEDs will turn on in sequence (1, 2, 3, and 4) followed by a long beep, indicating a successful transaction, see Figure 6-9. After a successful transaction, the device will return to the ready state when the transaction is complete, see Figure 6-10.
Figure 6-9 – LED Sequence – Payment Transaction Successful
Figure 6-10 – Return to Ready State After Successful Transaction
When the device is in ready state, two LEDs will be illuminated see Figure 6-11. When a card is detected, only LED 1 will be turned on. If the device has a BCR and it is enabled, the BCR light will also be turned on see Figure 6-12.
Figure 6-11 - Ready State
Figure 6-12 – Card Detected
In the event of a failed or canceled transaction, LED 1 will stay illuminated, and the device will emit two short beeps. If the device is equipped with a BCR, its light will also be on, as shown in Figure 6-13. The device will then return to the ready state, as demonstrated in Figure 6-14.
Figure 6-13 - Payment Transaction Failed
Figure 6-14 - Ready State
Upon being connected to USB power (after a delay of three seconds), the device will emit a short beep, and all four LEDs will turn on for half a second, as shown in Figure 6-15. The device will then return to the Ready State.
Figure 6-15 - Device Connected to USB Power
Upon being connected to RS-232 power (after a delay of three seconds), the device will emit a short beep, and all four LEDs will turn on for half a second, see Figure 6-16. The device will then return to ready state.
Figure 6-16 - Successful Connection to RS-232 Power Supply
Figure 6-17 - Device in Idle State Before RS-232 Power Supply Connection
When the device is in a ready state, as explained in section 6.3.2.1 Power On , connecting an RS-232 power supply to it will not change its state and it will remain in the ready state see Figure 6-18.
Figure 6-18 - Ready State
When the device is configured in Event Notification Mode, the user interface will have the same appearance as depicted in .
At present, no user interface elements such as LEDs or beeper sounds have been established for DynaProx.
DynaProx provides four Mono LEDs (see ), 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 and Error! Reference source not found. 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 well, as described in DynaProx LED Allocation. 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 manual, specific blinking patterns are described in more detail in the sections where they are relevant. For example, information about how the LEDs show the device’s connection status is in section .
DynaProx LED Allocation
DynaProx LED Patterns
DynaProx products have a beeper 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 two beeps when reading a card or contactless payment device to indicate a card read error 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. If the device is too quiet or too loud:
Make sure the device is being 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 .
To play a sequence of tones, follow these steps:
Make sure the device is in idle state.
Send an audio command to the device for playing a sequence of tones. For details, see .
When properly powered through its USB port or RS-232 port, the device powers on automatically. For USB mode it will remain full powered mode to provide power to device. This device does not support USB suspend mode.
The minimum required current and voltage are very important to the proper operation of the DynaProx reader. During contactless card reading, the NFC field is activated and the required current will rise from less than 100 mA to less than 800 mA for typically around 1 second. If the momentary current draw causes the supplied voltage to drop below 4 VDC, the DynaProx reader may reset and fail to complete the card read.
Embedded systems and Single Board Computers (SBC) may find use in a wide range of card tending terminals. If the DynaProx will be supplied power through a USB port from one of these SBCs, it is important to be aware of the USB port current limitations, such as all USB ports may share a given amount of current, or the upstream current limitation of the system power supply.
An optional power/ground connection is available on the DynaProx RS-232 connector, even if the actual RS-232 signals are not in use.
To power on the device connect the device to USB power or RS-232 Power. Recommended 800 mA available current during transactions.
To power off the device, disconnect the device from USB power or RS-232 Power. If all LEDs are off, the device is in Powered Off mode.
For full host control, the device should not be allowed to run for > = 23 hours without a reset. To accomplish this, have the host application send a reset command twice a day separated by at least one hour.
Example: Host software resets the device at 1 AM and 3AM. This keeps the device from initiating its own reset.
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 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 DynaProx is configured properly and is connected to the host (see ). When the device is connected to the host via USB and powered by the USB-C connector or RS-232, the host software may always keep a connection open to the device.
The operator makes sure DynaProx is receiving power either from the USB connection or from the RS-232 connection, and is awake and powered on (see and ).
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, 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).
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.
Figure 6-19 - Tapping a Contactless Card / Smartphone
Figure 6-20 – Contactless Read LED Sequence
To scan a barcode, follow these steps:
Make sure you are using a DynaProx model that includes a barcode reader, indicated by QR code markings on the face of the device surrounding the barcode reader lens (see ).
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.
Figure 6-21 - Scanning a Barcode
DynaProx 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 send 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.
For details, see .
DynaProx 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 shines steadily 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".
Card Read Result
Active Mode, armed for a tap transaction
Armed for Tap
Tap Read Progress
Tap Read Progress
Card Read Result
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, 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.
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 6-19). 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 6-20).
The device beeps once.
If the transaction requires a signature, the device sends 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.
The device ends the transaction and reports the transaction status to the host.
If the device cannot communicate with the card, smartphone, or other contactless payment device:
The device ends the transaction.
The device lights LED4 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.
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 1 inch 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.
Do not tilt the barcode more than 60 degrees from parallel to the device’s face.
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.
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 DynaProx Programmer’s Manual.
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.
The device notifies the host that the transaction has ended with the NFC Tag removed.
In This Context
LED1
LED2
LED3
LED4
Active Mode, not armed for a tap transaction
Power
Connection
In This Context
LED1
LED2
LED3
LED4
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.
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 connect to the 802.11 access point.
Short time























Reserved
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.
The front view of all DynaFlex II Go models (with and without BCR), are shown in Figure 2‑1 below. The back view of all DynaFlex II Go devices are identical, as seen in Figure 2‑2.
Figure 2 1 - DynaFlex II Go and DynaFlex II Go with BCR Front View
Figure 2 2 – Back View of all DynaFlex II Go Models
All DynaFlex II Go products include USB communications, a magnetic stripe reader (MSR), a contact chip card reader (ICCR), a contactless card reader (CTLS), and may also be purchased with an embedded barcode reader (BCR) and Bluetooth LE connectivity.
DynaFlex II Go models can be used as desktop or handheld devices. They are approved as a secure card reader (SCR) under PCI PTS POI v6.2 requirements.
Usage in any other environment will invalidate the approval.
To find important product identification, look on the printed product label on the back face of the device as shown in Figure 2‑3 below.
Figure 2 3 - DynaFlex II Go Device Label Location
The product label includes the following elements of device identification information, indicated by the numbered callouts in Figure 2‑4 and Figure 2‑5.
Product Name
PCI Hardware Identifier (“HW”)
Figure 2 4 - DynaFlex II Go Device Label
Figure 2 5 DynaFlex II Go with Bluetooth LE Device Label
The label also contains other supporting information about the device.
All DynaFlex II Go product family hardware configurations are listed in Table 2‑1 below. The device utilizes two interface types, USB and Bluetooth LE. Use of any interface other than USB or Bluetooth LE will invalidate PCI approval.
The most recent firmware versions for DynaFlex II Go products are 1000009446-AB0-PCI for the secure bootloader (Boot1 FW), 1000009421-AC0-PCI and 1000009714-AC0-PCI for the core firmware (Main FW), and 1000009327-AB0-PCI for the Bluetooth LE Firmware Version. The X in firmware versions indicates minor non-security related changes. The secure bootloader firmware version also covers the initial bootloader (Boot0) permanently programmed into the device. Any changes to either Boot0 or Boot1 will result in a change to the Boot1 FW version that is visible to the user, reported by the device, and listed on the PCI Approved Devices website.
All device identification information, including firmware versions and PCI Hardware ID, is accessible by connecting DynaFlex II Go to a host device via USB or Bluetooth LE, using the latest software provided by MagTek, as seen in Figure 2‑6 - Device Information Screen.
The host user can also can retrieve device information at any time using Command 0xD101 Get Property as described in DynaFlex II Go Programmer’s Manual (COMMANDS).
DynaFlex II Go, PCI, BLACK, BLUETOOTH LE
42PCI50B0BB0
DynaFlex II Go, PCI, BCR, BLACK, BLUETOOTH LE
42PCI30U0BC0
DynaFlex II Go, PCI, BLACK
42PCI50U0BC0
DynaFlex II Go, PCI, BCR, BLACK
42PCI30B0BC0
DynaFlex II Go, PCI, BLACK, BLUETOOTH LE
42PCI50B0BC0
DynaFlex II Go, PCI, BCR, BLACK, BLUETOOTH LE
42PCI30U0BD0
DynaFlex II Go, PCI, BLACK
42PCI50U0BD0
DynaFlex II Go, PCI, BCR, BLACK
42PCI30B0BD0
DynaFlex II Go, PCI, BLACK, BLUETOOTH LE
42PCI50B0BD0
DynaFlex II Go, PCI, BCR, BLACK, BLUETOOTH LE
9
10
11
12
PCI Hardware ID Number
4
2
P
C
I
3
0
U
0
B
PCI Hardware ID Number
4
2
P
C
I
5
0
U
0
B
PCI Hardware ID Number
4
2
P
C
I
3
0
B
0
B
PCI Hardware ID Number
4
2
P
C
I
5
0
B
0
B
PCI Hardware ID Number
4
2
P
C
I
3
0
U
0
B
PCI Hardware ID Number
4
2
P
C
I
5
0
U
0
B
PCI Hardware ID Number
4
2
P
C
I
3
0
B
0
B
PCI Hardware ID Number
4
2
P
C
I
5
0
B
0
B
PCI Hardware ID Number
4
2
P
C
I
3
0
U
0
B
PCI Hardware ID Number
4
2
P
C
I
5
0
U
0
B
PCI Hardware ID Number
4
2
P
C
I
3
0
B
0
B
PCI Hardware ID Number
4
2
P
C
I
5
0
B
0
B
PCI = PCI Hardware
6
Front options
3 = Standard
5 = includes Barcode Reader
7
Option RFU (Reserved for Future Use)
RFU 0 = as Certified
8
Interface Options
U = USB only
B = USB + Bluetooth LE
9
Option RFU (Reserved for Future Use)
RFU 0 = as Certified
10
Cover Color:
B = Black
11
Version
B and C and D = as Certified
12
minor fixes not adding functionality or related to security (e.g., change component value for antenna matching):
0 = as certified
8
9
10
11
12
13
14
15
16
17
18
1
0
0
0
0
0
9
4
2
1
1
0
0
0
0
0
9
4
1
1
1
0
0
0
0
0
9
4
2
1
1
0
0
0
0
0
9
7
1
4
1
0
0
0
0
0
9
7
1
4
1
0
0
0
0
0
9
4
2
1
1000009421 - AA, AB, and AC = Certified Version
1000009714 - AB and AC = Certified Version
14
Minor revisions, bug fixes
16-18
PCI = PCI version of firmware
9
10
11
12
13
14
15
16
17
18
1
0
0
0
0
0
9
4
4
6
-
AA = Certified Version
14
Minor revisions, bug fixes
16-18
PCI = PCI version of firmware
9
10
11
12
13
14
15
16
17
18
1
0
0
0
0
0
9
3
2
7
-
AA = Certified Version
14
Minor revisions, bug fixes
16-18
PCI = PCI version of firmware
PCI ID Tag
Configuration Description
42PCI30U0BB0
DynaFlex II Go, PCI, BLACK
42PCI50U0BB0
DynaFlex II Go, PCI, BCR, BLACK
PCI Hardware ID Number
1
2
3
4
5
6
7
Fixed Position
Variable “X” Position
Description of Fixed or Variable “X” in the Selection Position
1-2
42 = DynaFlex II Go
3-5
Firmware Number
1
2
3
4
5
6
Fixed Position
Variable “x”
Position
Description of Fixed or Variable “x” in the Selected Position
1-10
1000009421, 1000009714 = DynaFlex II Go Main firmware part number
12-13
Firmware Number
1
2
3
4
5
6
7
Fixed Position
Variable
“x” Position
Description of Fixed or Variable “x” in the Selected Position
1-10
1000009446 = DynaFlex II Go Boot firmware part number
12-13
Firmware Number
1
2
3
4
5
6
7
Fixed Position
Variable
“x” Position
Description of Fixed or Variable “x” in the Selected Position
1-10
1000009327 = DynaFlex II Go Bluetooth LE firmware part number
12-13








42PCI30B0BB0
8
7
8
8
B
0
B
0
B
0
B
0
C
0
C
0
C
0
C
0
D
0
D
0
D
0
D
0
-
A
A
X
-
P
C
I
-
A
B
X
-
P
C
I
-
A
C
X
-
P
C
I
-
A
B
X
-
P
C
I
-
A
C
X
-
P
C
I
-
A
C
x
-
P
C
I
A
A
x
-
P
C
I
A
A
x
-
P
C
I
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









Acronym
Definition
AES
Advanced Encryption Standard
BCR
Barcode Reader
CTLS
Contactless
DES
Data Encryption Standard
DUKPT
Derived Unique Key Per Transaction
ECC
Elliptic-Curve Cryptography
ICCR
Integrated Circuit Card Reader
MAC
In cryptography: Message Authentication Code
In networking: Media Access Control [address]
MSR
Magnetic Stripe Reader
NFC
Near Field Communication
POI
Point Of Interaction
S/N
Serial Number
SCRA
Secure Card Reader Authenticator
SHA
Secure Hash Algorithm
SRED
Secure Reading and Exchange of Data
TDEA
Triple Data Encryption Algorithm
USB
Universal Serial Bus
USB HID
USB Human Interface Device
DynaFlex II Go and DynaFlex II Go BCR deliver the next generation of mobile payment solutions, both models are PCI PTS 6.x. This document provides an abbreviated version of the Installation and Operation Manual, PN D998200595 hosted on www.magtek.com. These secure card reader authenticator devices accept magnetic stripe cards; EMV chip cards (contact and contactless); NFC enabled mobile wallets including Apple® Pay, Samsung™ Pay, Google Pay™, with support for Google Smart Tap and Apple VAS protocols, and MIFARE® Classic,
MIFARE® DESFire, and NTag. DynaFlex II Go BCR additionally has an integrated barcode reader. Ideal for cafés, restaurants, boutiques, airlines, retail banks, and other developers looking to build a secure payment solution that accepts swipe, tap, and dip technology.
DynaFlex II Go Major Components
Top Face
DynaFlex II Go products are designed to provide flexible mounting options. The device can be mounted to the host via an external clip or the embedded lanyard. When designing an enclosure or mounting bracket, ensure there is adequate clearance for cardholders to tap, swipe, dip, and
for users to present a bar code. Proximity to metal can reduce the device’s reading range. DynaFlex II Go offers an optional OtterBox uniVERSE clip adapter and a countertop stand.
DynaFlex II Go is available with USB-C or USB-C and Bluetooth LE connection. Check you model number for connection configuration.
For best results, use the cable that is included with the device. Connect the cable to the device. Connect the other end to the HOST USB port. Device will automatically power on. Windows will start an installation of the driver on initial connection. Windows will report DEVICE IS READY and device
shows in Windows Device Manager under HUMAN INTERFACE DEVICES as two devices HID-COMPLIANT VENDOR-DEFINED (VID 0801, PID 2024) and USB INPUT DEVICES.
See D998200386 MagTek Universal SDK
Disconnect any active connections to the device. Install Android HOST software. Press and hold the POWER BUTTON for 4 beeps until LED 4 starts flashing indicating Bluetooth LE pairing is in process. LED flashes once per second for up to 3 minutes. On the Android HOST, launch SETTINGS >BLUETOOTH> SEARCH FOR DEVICES > locate
the 7-digit serial number on the device label (DF II GO_xxxxxxx). Select device. When HOST shows BLUETOOTH PAIRING REQUEST and asks for configuration key, enter [000000]. The device appears in PAIRED DEVICES. Change the default passkey.
To UNPAIR, locate the device in BLUETOOTH configuration page on HOST, press the settings (gear) icon, press FORGET.
Ensure HOST Bluetooth LE is turned on and working. Disconnect any other connections to the device. On the HOST, install and configure the software. Ensure HOST software is configured to look for the device. The device transmits in GATT format. In START on HOST type BLUETOOTH and select BLUETOOTH AND OTHER DEVICE
SETTINGS. Locate the 7-digit serial number on device label. Press and hold the POWER BUTTON on device for 4 beeps until LED 4 starts flashing indicating Bluetooth pairing is in process. LED flashes once per second for up to 3 minutes. Press the ADD BLUETOOTH OR OTHER DEVICE button and launch ADD A DEVICE window. Under CHOOSE THE KIND OF DEVICE YOU WANT TO ADD select BLUETOOTH.
Locate the device called DF II GO-xxxxxxx. Enter configured passkey (000000) press the CONNECT button. After a short period CONNECTED appears. Press DONE. Change the default passkey.
To UNPAIR, select the device in BLUETOOTH AND OTHER DEVICE SETTINGS window and press the REMOVE DEVICE button.
DynaFlex II Go receives power from 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.
Powered Off Mode is the shipping and storage mode of the device. No external power is applied to the device through the USB cable or from the internal rechargeable battery.
Active Mode is the device’s normal “awake” state when it is in use. In this mode, the device LED indicators are powered on, and the device is ready to receive commands from the host.
To set the device from Active mode to Powered Off mode: remove power, and press and hold the power button for two beeps.
DynaFlex II Go has 4 LEDs that provide responses to the user for Power, Connection, Device Status, and Card Status. The Installation and Operation Manual has a more complete list of light signals.
The device does not have an on-screen configuration interface. However, it does have settings the HOST can change using commands.
Operator presses the Start transaction button on the HOST device. LED 1 and 2 will remain on. When a card is swiped, all four LEDs will turn on in sequence (1, 2, 3 then 4), followed by a long beep, indicating a successful transaction. Swipe the card with the magnetic stripe facing away from the face of the device. After a successful transaction, the device will return to the ready state.
Locate the insertion slot on the face of the device. Orient the chip card so the chip faces the face of the device. Insert the chip card into the slot, then push gently on the card until it stops. 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.
Hold QR Code or barcode approximately 6 inches away from barcode reader. The operator presses the Start button on the HOST device. LED 1,2, and the BCR status light will be illuminated see. When a barcode is detected, only LED 1 will remain illuminated, the BCR status LED will be off, and a long beep will sound.
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. Tap the card or electronic payment device on the contactless landing zone, indicated by the EMVCo Contactless Indicator on the device’s face. The card or device’s antenna* must be centered over the contactless landing zone. Remove the card or electronic payment device from the contactless landing zone.
Users can take advantage of the OtterBox® uniVERSE® adaptor for easy sliding and connection to a wide range of mobile devices, including phones and tablets
FCC INFORMATION
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) This device must accept any interference received, including interference that may cause undesired operation.
Note: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
Reorient or relocate the receiving antenna.
Increase the separation between the equipment and receiver.
Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/TV technician for help.
CAUTION
Changes or modifications not expressly approved by MagTek could void the user’s authority to operate this equipment.
CANADIAN DECLARATION OF CONFORMITY
This digital apparatus does not exceed the Class B limits for radio noise from digital apparatus set out in the Radio Interference Regulations of the Canadian Department of Communications.
Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la classe B prescrites dans le Réglement sur le brouillage radioélectrique édicté par le ministère des Communications du Canada.
This Class B digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe B est conformé à la norme NMB-003 du Canada.
INDUSTRY CANADA (IC) RSS
This device complies with Industry Canada licence-exempt RSS standard(s). Operation is subject to the following two conditions: (1) This device may not cause interference, and (2) This device must accept any interference, including interference that may cause undesired operation of the device.
Le présent appareil est conforme aux CNR d’Industrie Canada applicables aux appareils radio exempts de licence. L’exploitation est autorisée aux deux conditions suivantes: (1) L’appareil ne doit pas produire de brouillage, et (2) L’utilisateur de l’appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d’en compromettre le fonctionnement.
CUR/UR
This product is recognized per Underwriter Laboratories and Canadian Underwriter Laboratories 1950.
CE STANDARDS
Testing for compliance with CE requirements was performed by an independent laboratory. The unit under test was found compliant with standards established for Class B devices.
EU STATEMENT
Hereby, MagTek Inc. declares that the radio equipment types Wideband Transmission System (802.11 wireless and Bluetooth® Low Energy), and Non-Specific Short Range Device (contactless) are in compliance with Directive 2014/53/EU. The full text of the EU declarations of conformity is available at the following Internet addresses:
UL/CSA
This product is recognized per UL 60950 1, 2nd Edition, 2011 12 19 (Information Technology Equipment - Safety - Part 1: General Requirements), CSA C22.2 No. 60950 1 07, 2nd Edition, 2011 12 (Information Technology Equipment - Safety - Part 1: General Requirements).
ROHS STATEMENT
When ordered as RoHS compliant, this product meets the Electrical and Electronic Equipment (EEE) Reduction of Hazardous Substances (RoHS) Directive (EU) 2015/863 amending Annex II to Directive 2011/65/EU. The marking is clearly recognizable, either as written words like “Pb-free,” “lead-free,” or as another clear symbol ( Pb ).
PCI STATEMENT
PCI Security Standards Council, LLC (“PCI SSC”) has approved this PIN Transaction Security Device to be in compliance with PCI SSC’s PIN Security Requirements.
When granted, PCI SSC approval is provided by PCI SSC to ensure certain security and operational characteristics important to the achievement of PCI SSC’s goals, but PCI SSC approval does not under any circumstances include any endorsement or warranty regarding the functionality, quality or performance of any particular product or service. PCI SSC does not warrant any products or services provided by third parties. PCI SSC approval does not under any circumstances include or imply any product warranties from PCI SSC, including, without limitation, any implied warranties of merchantability, fitness for purpose, or non-infringement, all of which are expressly disclaimed by PCI SSC. All rights and remedies regarding products and services which have received PCI SSC approval shall be provided by the party providing such products or services, and not by PCI SSC.
UKCA STATEMENT
Hereby, MagTek Inc. declares that the radio equipment types Wideband Transmission System (Wireless LAN and Bluetooth Low Energy), and Non-Specific Short Range Device (contactless) are in compliance with Radio Equipment Regulations 2017 Directive S.I.2017:1206. The full text of the UKCA declarations of conformity is available at the following Internet addresses:
Storage temperature
-4°F to 113°F (-20°C to 45°C)
Operating temperature
32°F to 95°F (0°C to 35°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
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
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
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 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
DynaFlex II Go EMV Contact
Connected via USB
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
















































iDynamo 5 (Gen III) is a compact secure card reader authenticator (SCRA) that reads magnetic stripe cards that conform to ISO standards. iDynamo models are made for iOS, Android, and Windows devices equipped with a USB-C interface. When a cardholder swipes a card, the device encrypts card data before they leave the encapsulated magnetic stripe reader head using the Triple Data Encryption Algorithm (TDEA, also known as Triple DES) and DUKPT key management.
The basic form factor of the package is a folded white cardboard box with a cardboard insert where the device is nestled into the box. There are no rips or added materials on the package other than product and Lot labels. The package only has one color ink printed on the package: black. The box is made with corrugated white cardboard.
Back of Package
Industry certification logos showing compliance are printed on the back of the package as shown.
Manufacturer
Manufacturer address is shown.
Top of Package
The top of the package is printed as shown, with MFi logo, QR Code for Package inspection document and Quick Installation Guide, URL Links and product name and description.
Left Side of Package
On the left side of the package is printed with the contents and the product label is adhered.
Right Side of Package
The right side of the package lists the storage guidelines and CAUTION content regarding temperature and humidity.
Front of Package
The front of the package lists the product name, product category, and is secured with Security Tape.
Security Tape
Security tape wraps onto the bottom of the package from the front flap of the package.
Adhered
Here security tape is applied and secured. Wrapping front to bottom of package.
Tape - Removed Tape
Tape is removed VOID and OPENED appear on tape.
Package - Removed Tape
Tape is removed VOID and OPENED show as the inverse ink on the package.
Bottom
Security Tape
The Security Tape wraps from the front flap to the bottom of the package.
Make certain there are no signs of tampering.
Lot Label
The Lot label is adhered on the bottom of the box. Make certain there are no false labels added or signs of tampering.
Inside
Dynamo 5 (Gen III) products are nestled inside the package for transit. The package includes the device, cable(s), device inspection document, and quick installation guide.
To check for PCI Validation check the Hardware and Firmware ID. Hardware ID is printed on the label. The Firmware ID is accessible via the device.
Go to the PCI compliance web page and search for MagTek, and find the product name. Compare the Hardware ID and Firmware ID:
As part of your inspection, include the following for your inspection audit:
Be certain to have a list of the devices and include the details listed on the product label.
It may be helpful to take photos of the front, back, and sides of each device.
Be certain to check device part numbers, serial numbers, and IDs and check physical connections. Use the chart below as a checklist to inspect the device for signs of tampering.
Front
Check form factor
Look for signs of tamper
Check printing and no added labels
Left, Right, and Back Sides
Check form factor
Look for signs of tamper
Check printing and no added labels
Check product label
Front Flap
Check Security Tape
Look for signs of tamper
Check printing and no added labels
Check form factor
Bottom
Check Security Tape
Look for signs of tamper
Check printing
Check form factor
Check lot Label
Are there signs of tampering?
YES
NO
Package Inspection










Form Factor - check overall form factor