Every exchange with the DynaFlex II Go— the commands you send and the responses and notifications it returns — uses the standard Multi-Interface Card Reader Platform (MMS) message format. This section defines how requests, responses, notifications, and file messages are framed and parsed. The format is the same across DynaFamily readers and is documented once in the shared reference.

Settings & Information - Group 0xD1nn

These sections detail a variety of information on OIDs, codes, tips & taxes and more.

The DynaFlex II Go is a portable secure card reader authenticator (SCRA) that reads contact chip, contactless (NFC), and magnetic-stripe cards in a compact, handheld device. It encrypts cardholder data at the point of read (SRED) and connects over USB or Bluetooth LE — suited to both mobile and countertop acceptance. It uses the shared Dyna-family MMS command set, so everything you build against it is documented in the API & Command Reference and linked below.

Key Capabilities

• Contact, contactless (NFC), and magnetic stripe card reading in one device

• SRED point-to-point encryption at the moment of read (TDES / AES DUKPT)

• NFC/MIFARE pass-through and NFC card emulation (DynaCast)

• Optional barcode reader (BCR) for scanning outside a transaction

• Portable and battery-powered, with status LEDs and a buzzer for prompts

• PCI PTS POI–approved SCRA (no PIN entry — see the DynaFlex II PED for PIN)

MMS notifications are the asynchronous messages the DynaFlex II Go reader sends while a transaction is running, reporting progress, state changes, and completion. Find the Notification Group you are looking for below and follow the links in the table to jump to a specific notification.

Working with contactless cards and tags on the DynaFlex II Go, the supported card technologies (NTag, MIFARE Ultralight, Classic, DESFire, Plus), how pass-through works, and NFC card emulation (DynaCast). This is shared DynaFamily content, documented once in the guide.

Data Types and Shared TLV Data Objects

This section defines the primitive and composed data types, TLV (Tag-Length-Value) data objects, file structures, and cryptographic key formats used throughout the device command set, including track data, display strings, EMV configuration file types (ARQC, ARPC, Batch, CA Public Keys), security parameters, TR‑31 key blocks, certificate and CSR file structures, and card emulation.

Information in this group

Overview

DynaFlex II Go and DynaFlex II Go BCR deliver the next generation of mobile payment solutions, both models are PCI PTS 6.x. 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.

Major Components

DynaFlex II Go Major Components

Top Face

Environmental Notice

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 (999999) 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:

This section focuses on properties, which the host can either read from the device to retrieve device information (such as its PCI hardware ID, serial number, firmware revision numbers, etc.), or write to the device to change device behavior, or to store values for future reference.

About Configuration

Financial Settings - Property Group 1.1.nnnn

The DynaFlex II Go accepts the Multi-Interface Card Reader Platform (MMS) command set — the messages you send to run transactions, read cards, manage keys and files, and query or configure the reader. Full syntax, parameters, responses, and examples are documented once in the shared reference; the families below are the commands the Go supports, each linking into that reference.

Transaction - Group 0x10nn

The DynaFlex II Go uses the shared Dyna-family Multi-Interface Card Reader Platform (MMS) command set. This manual is a device-scoped map into the API & Command Reference with the sections this device relies on linked below.

In this manual

• Security & Keys --> How the Go protects data and manages keys: DUKPT (3DES→AES), MAC, KSNs, encryption/decryption, and the PCI requirements like the 24-hour reset and device lock.

• Compliance--> The Go's PCI PTS POI security policy, certifications, and the regulatory documentation for deployment.

• NFC/MIFARE -->Working with contactless cards and tags — NFC/MIFARE pass-through and the supported card technologies (NTag, Classic, DESFire, Plus).

How the DynaFlex II Goprotects cardholder data and manages keys. These are shared DynaFamily concepts, documented in the Guides Section:

Security & Key Guides

This compliance documentation page provides the essential security and inspection guides required to maintain PCI PTS POS approval and ensure the physical integrity of DynaFlex II Go secure card readers before and after deployment.

Documents

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.

DynaFlex II Go Documentation

Firmware

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 Quickstart takes you from an unopened DynaFlex II Go to a completed test transaction.

Before You Start

• Your DynaFlex II Go unit

• USB Cable (or a Bluetooth LE-capable host)

• Your platform's SDK or the Web demo for sending commands

  • See SDKs & Tools

• Test keys injected, if you intend to decrypt output

  • See Security & Key Management