All pages
Powered by GitBook
1 of 7

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Message Format & Structure

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.

Applies to: DynaFlex II Go

Settings & Information - Group 0xD1nn

Reference Section

Information Available

The host and the device communicate with each other by exchanging blocks of data called Messages, which are standardized wrappers containing a payload that is either a command Request, a command Response, an unsolicited Notification, or a File.

All messages exchanged between the host and the device are formatted using the tag-length-value Distinguished Encoding Rules (DER).

Each message type follows a specific structure described on this page.

Need Help?

For additional support, please contact MagTek Support:

Technical Support:

  • 📧 Email:

  • 📞 Phone: 1-562-546-6800 (US)

🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM Pacific

Online Resources:

  • 🌐 Support Portal: developer.magtek.com

  • 🌐 Official Site:

Documentation Feedback:

Help us improve this documentation!

About Messages
Message Format
Message Structure
support@magtek.com
https://www.magtek.com
feedback@magtek.com

Appendices

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

Applies to: DynaFlex II Go

System Status Information - Property Group 2.3.1.nnn

Reference Section

Information Available

For modular management of device functions, information, and settings, this standard makes extensive use of Object Identifiers (also known as Object IDs or OIDs) as defined in ITU-T X.660 | ISO/IEC 9834-1.

Barcode symbology refers to the way in which data is encoded in a barcode. It uses either spaced lines, dots or squares.

This section will help erase already existing EMV configurations.

DynaFlex II SCR features a single physical button. Pressing and holding this button can activate additional functions on the device.

For More Help

Need Help?

For additional support, please contact MagTek Support:

Technical Support:

  • 📧 Email:

  • 📞 Phone: 1-562-546-6800 (US)

🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM Pacific

Online Resources:

  • 🌐 Support Portal: developer.magtek.com

  • 🌐 Official Site:

Documentation Feedback:

Help us improve this documentation!

A: Object IDs and ITU-T x660
B: Barcode Reader Symbologies
C: Erasing EMV Configurations
E: Physical Button
support@magtek.com
https://www.magtek.com
feedback@magtek.com

Programmer's Manual

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.

Applies to: DynaFlex II Go

In this manual

Reference Section

Information Available

The full device Command matrix, if you're building for more than one Dyna reader.

How MMS requests, responses, and notifications are framed and parsed.

The shared TLV and EMV objects the commands carry.

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

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

Tag
Length
Type
Description
Requirement
Example Value

Notifications

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.

8

T

Terminal ID

Required

"TERM0001"

82

1

B

Transaction type

Required

00 = Purchase

83

1

B

Reader options (bitfield)

Optional

0F = All readers enabled

Commands

The MMS command set, scoped to the Go, with a supported-commands view.

Notifications

Asynchronous messages the Go sends during transactions, device events, and firmware updates.

Configurations

Configurable properties and parameters.

Appendices

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

80

2-4

I

Transaction amount (cents)

Required

03 E8 = 1000 ($10.00)

See Also

Need More Help

Need Help?

For additional support, please contact MagTek Support:

Technical Support:

  • 📧 Email: support@magtek.com

  • 📞 Phone: 1-562-546-6800 (US)

  • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM Pacific

Online Resources:

  • 🌐 Support Portal: developer.magtek.com

  • 🌐 Official Site:

Documentation Feedback:

Help us improve this documentation!

Security & Keys
NFC/MIFARE
Command Support Across Products
Message Format & Structure
Data Types & Shared TLV Objects

81

Reference Section

Information Available

This notification reports the successful completion of firmware update operations the host initiated

This notification reports the failure of a Firmware Update command the host initiated.

This notification reports Firmware is up to date for host initiated update.

Reference Section

Information Available

This notification reports general state changes outside a transaction, including the mDoc subscription warning (05000101) and subscription expired (05000102) events. |

The device sends this notification when the battery charge reaches 15 percent.

The device sends this notification one minute before it automatically powers down the device.

The device sends this notification when the battery charger detects that the battery is fully charged.

Reference Section

Information Available

This notification requests that the host take action during operations involving the device’s User Interface modules.

This notification shows that a UI operations involving the device’s User Interface modules is complete.

Reference Section

Information Available

This notification reports information about progress and state changes that occur during a Pass-Through Mode.

Reference Section

Information Available

0x0101 - Transaction Information Update

This notification reports progress and state changes during a transaction, including mDoc engagement status and verified mDoc results (Payment Technology 0x40).

0x0105 - Transaction Operation Complete

This notification reports the final result of a transaction started with Command 0x1001, or of an mDoc read started with Command 0x1201 or 0x1202, including timeouts and cancellations.

Applies to: DynaFlex II Go

From Transactions - Source 0x01nn

Firmware Updates - Source 0x09nn

From Device - Source 0x10nn

User Interface - Source 0x18nn

From Generic Pass-Through Mode - Source 0x03nn

For more help

Need Help?

For additional support, please contact MagTek Support:

Technical Support:

  • 📧 Email:

  • 📞 Phone: 1-562-546-6800 (US)

Data Types & Shared TLV Objects

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

Section

Information available

A list of primitive data types used by TLV data objects.

Information about parsing EMV ARQC Type or Merchant Data Container data for each track into individual values embedded in the tracks.

https://www.magtek.com
feedback@magtek.com

🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM Pacific

Online Resources:

  • 🌐 Support Portal: developer.magtek.com

  • 🌐 Official Site: https://www.magtek.com

Documentation Feedback:

Help us improve this documentation! feedback@magtek.com

0x0905 - Firmware Update Successful
0x0906 - Firmware Update Failed
0x0907 - Firmware is Up to Date
0x1001 - Device Information Update
0x1001 - Low Battery Warning
0x1001 - Low Battery Shutdown
0x1001 - Battery Charged
0x1803 - User Interface Host Action Request
0x1805 - User Interface Operation Complete
0x0301 - Pass-Through Mode Information Update
support@magtek.com

Display Strings

A pre-defined set of messages by string ID that the host and device use for various user interface features.

Encryption Type

Information on the key type, variant, and other information the host can use to decrypt encrypted data included in various payloads.

EMV ARQC Type

Information on how the device formats ARQC messages.

EMV ARPC Type

Information on how the device formats ARPC messages

EMV Batch Data Type

Information on the device formats EMV batch data, such as merchant data and pre-defined EMV batch data tags.

EMV Terminal Configuration Type

Information on loading this file type to control the behavior of the device’s EMV contact kernel.

EMV Processing Configuration File Type

Information on loading this file type to control the behavior of the device’s EMV kernel.

EMV Entry Point Configuration File Type

Information on loading this file type to control the behavior of the device’s EMV kernels.

EMV Configuration CA Public Keys File Type

Information on loading this file type to control the behavior of the device’s EMV contact and contactless kernels when the device should support Offline Data Authentication (ODA).

EMV American Express DRL Configuration Type

Information on loading this file type to control the behavior of the device’s American Express contactless kernel when the card sends tag 9F70 and one or more DRL is defined. (Not supported on Expresspay 4.x)

Signature Capture File Type

The signature capture file type produced when the host invokes Request Cardholder Signature - Command 0x1801 (Touch Only)

Security Operation Type

This non-TLV data structure consists of four or five bytes that describes a security operation, including the algorithms and methods to be used in that operation.

Security Parameters Type

Information on tags used with security parameters.

Key Information Type

Information on tags used to identify key types.

NFC UID Type

Information on tags used with NFC UID Types. (EMV Contactless Only)

TR-31 Key Block Type

Information on tags used with TR-31 Key Blocks.

DUKPT Key Mapping

Information on tags used with DUKPT Keys.

Common File Structure

Information on file types that conform to the common file structure format.

Certificate File Type

These file types conform to the Common File Structure format. The File Payload of these files contain a certificate in PEM format.

Certificate Signing Request (CSR) Files Types

Information on CSR File Types.

Certificate Store

The reader's store of trusted issuer certificates (the AAMVA VICAL file plus individual IACA certificates) used to verify mDoc responses, and how to load, fetch, and delete them.

Card Emulation

Card emulation enables a DynaFlex/DynaProx device to simulate a Type 4 smart card.

Tag Tables for ISO AAMVA Mpassport Request Items

Request-item tags for each mDoc namespace (ISO 18013-5 from 0xDFB001, AAMVA from 0xDFB041, mobile passport from 0xDFB061) used to build a Command 0x1201 request. |

Need Help?

For additional support, please contact MagTek Support:

Technical Support:

  • 📧 Email: support@magtek.com

  • 📞 Phone: 1-562-546-6800 (US)

  • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM Pacific

Online Resources:

  • 🌐 Support Portal: developer.magtek.com

  • 🌐 Official Site:

Documentation Feedback:

Help us improve this documentation!

Primitive Data Types
About Track Data

Configurations

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.

Applies to: DynaFlex II Go

About Configuration

Reference Section

Information Available

Detail on configuring the DynaFlex II Go device.

Financial Settings - Property Group 1.1.nnnn

Reference Section

Information Available

https://www.magtek.com
feedback@magtek.com

Configure the USB interface on USB-connected devices, including communication mode and power behavior during USB suspend. Applies only when connected over USB.

Configure the device's cardholder-facing interface — display behavior, LEDs, buzzer, and prompts — including the UI configuration file.

Continues UI configuration with the remaining interface properties, such as the card-logos page and related on-screen elements.

Set or read the name the device advertises over Bluetooth LE, used to identify the reader when pairing and connecting.

Configure the device's security posture, including SRED/encryption behavior and key status.

Configure the device's system settings

Properties that enable mDoc on the device, including the mDoc subscription (1.2.9.1.1.1) and the expiration-warning threshold (1.2.9.1.1.2). |

The identifier and version of the China UnionPay contactless kernel firmware.

Firmware and version information for the device's Wi-Fi (WLAN) module, on models equipped with a WLAN radio.

Identifies the custom user-interface package loaded on the device — which custom UI build (if any) is installed, and its version.

Firmware and version information for the device's NFC contactless module and controller.

EMV Settings A

Part A of EMV Terminal ID settings.

EMV Settings B

Part B of EMV Terminal ID settings.

EMV Settings C

Part C of EMV Terminal ID settings.

Reference Section

Information Available

SRED Settings - Property Subgroup 1.1.2.nnn - A

The device uses this property to determine what character it should use when sending masked ISO/ABA track data.

SRED Settings - Property Subgroup 1.1.2.nnn - B

The device sends this notification when the battery charge reaches 15 percent.

Reference Section

Information Available

Transaction Settings - A

Configure how the device runs financial transactions — EMV terminal and kernel parameters, supported entry methods, and amount, currency, and timeout handling.`

Transaction Settings - B

Continues the transaction group with the remaining financial/EMV properties, such as contactless and additional processing options.

Basic Properties

Read the device's core identity and status: model name, serial number, firmware and boot versions, real-time clock, and operational state. These are mostly read-only values for identifying and health-checking the reader.

WLAN Settings (WLAN Only) - A

Configure Wi-Fi connectivity on WLAN-equipped models, including network SSID, security mode, and credentials. Applies only to devices with a WLAN radio.

WLAN Settings (WLAN Only) - B

Continues WLAN configuration with the remaining network properties, such as IP addressing and connection behavior.

Reference Section

Information Available

Firmware Identification Information

The device's top-level firmware identifier — the composite firmware ID that ties together the individual component versions and checksums listed below.

Core Firmware Information

Part number, version, and build details for the device's core application firmware — the main firmware that runs the reader.

EMV Firmware Information

Part number and version for the EMV firmware component that handles Level 2 EMV processing for contact and contactless transactions.

EMC Contactless L1 Kernel Checksum (Contactless Only)

A checksum identifying the contactless Level 1 kernel firmware, used to confirm which L1 kernel build is installed.

Discover D-PAS Kernel Checksum (Contactless Only)

A checksum identifying the Discover D-PAS contactless kernel firmware installed on the device.

Reference Section

Information Available

Device Common Configuration Information

Read-only hardware information reported by the device, such as model, part number, and hardware revision.

Reference Section

Information Available

System Status Injected Key Information

This OID contains a 32-bit bitmap. Each bit indicates the status of a transaction key,

System Status Security Protection Information

The device uses this property to report its security status.

SRED Settings - Property Subgroup 1.1.2.nnn

Device Settings - Property Group 1.2.nnnn

Firmware Identification Information - Property Group 2.1.2.nnn

Hardware Information - Property Group 2.2.1.nnn Device

System Status Information - Property Group 2.3.1.nnn

Need Help?

For additional support, please contact MagTek Support:

Technical Support:

  • 📧 Email: support@magtek.com

  • 📞 Phone: 1-562-546-6800 (US)

  • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM Pacific

Online Resources:

  • 🌐 Support Portal: developer.magtek.com

  • 🌐 Official Site:

Documentation Feedback:

Help us improve this documentation!

About

https://www.magtek.com
feedback@magtek.com
USB Settings (USB Only)
User Interface Settings - A
User Interface Settings - B
Bluetooth LE Device Name
Security Settings
System Settings
Enable Mobile Document Features
China Union Pay Kernel ID (Contactless Only) (Common Kernel)
WLAN Information (WLAN Only)
Custom UI
NFC

Commands

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.

Applies to: DynaFlex II Go

Transaction - Group 0x10nn

Reference Section

Information Available

The host uses this command to start a payment transaction.

The host uses this command to provide the device with additional/modified data to resume a transaction that is currently paused.

The host uses this command to cancel a transaction that is currently in progress.

The host uses this command to prompt a cardholder for customer information.

The host uses this command to trigger the device to immediately show a pre-loaded image on the display.

The host uses this command to direct the device to immediately show a QR code on the display.

The host uses this command to trigger the device to immediately show a bitmap file the host includes as a parameter.

This command allows the host to bring up standalone pages.

The host uses this command to control the 4 LEDs of the device when the device is not in non-User Control LED states.

Card emulation is initiated by receiving a 0x1840 command from the host.

The host uses this command to request the file information of a file stored on the device.

The host uses this command to request the deletion of a file stored on the device.

Reference Section

Information Available

0x1100 - Pass Through Command For NTag/MIFARE Ultralight, Type 2

The host uses this command to send commands and receive responses to and from a NTag/MIFARE Ultralight.

0x1101 - Pass Through Command for MIFARE Classic/MINI®/Plus SL1 (Security Level 1), Type 2

After a MIFARE Tag is activated, the host uses this command to send commands and receive responses to and from a MIFARE tag.

0x1102 - Pass Through Command for MIFARE DESFire, Type 4

The host uses this command to send commands and receive responses to and from a MIFARE DESFire Tag.

0x1103 - Pass Through Command for MIFARE Plus, Type 2

The Host uses this command to send commands and receive responses to and from a MIFARE Plus tag.

Reference Section

Information Available

0x1201 - Read Mobile Document

The host uses this command to start an mDoc read, specifying the namespace, request items, timeout, output security, and engagement methods (NFC or QR).

0x1202 - Age Verification for ISO 18013-5

The host uses this command to run an age-only check (over 18, 21, or 25) without receiving the holder's name, birth date, or other identifying data.

Reference Section

Information Available

0x1801 - Request Cardholder Signature

The host uses this command to prompt a cardholder for a signature.

0x1802 - Report Cardholder Selection

The host uses this command to provide a cardholder selection to the device when the device itself does not have a display or inputs to prompt the cardholder for a selection.

0x1803 - Display Message

The host uses this command to request that the device display a message for the cardholder.

0x1804 - Read Barcode (BCR Only)

The host uses this command to direct the device to arm or disarm the barcode reader for reading a barcode outside the scope of a transaction.

0x1805 - Buzzer

The host uses this command to start a buzzer for playing a sequence of tones. Each sequence can have a minimum of 1 to maximum of 10 tones.

Reference Section

Information Available

About

Basic details about generic pass-through commands.

0x3001 - Pass-Through Mode Start/Stop

The host uses this command to enter or exit Pass-Through Mode.

0x3002 - Start/Stop Polling

After entering the Pass-Through Mode, the host use this command to request the device to start polling for a Type A and Type B PICC until it detects a PICC or times out.

0x3003 - ISO 14443-4 APDU Pass-Through Commands

The host uses this command to send application-level APDUs to a PICC that supports ISO 14443-4 Protocol

Reference Section

Information Available

0x1F01 - Reset Device

The host uses this command to reset the device.

0x1F02 - Set Notification Subscriptions

The host uses this command to specify which notifications the device should send on each of its available interfaces

0x1F03 - Extend Session

The host can use this command to erase all Bluetooth® LE bonds.

Reference Section

Information Available

0x2001 - Request PIN with Host Supplied Account Data

This command directs the device to prompt the cardholder to enter a PIN when a card is not present or is not presented.

0x2002 - Request PIN with Card Supplied Account Data

This command directs the device to prompt the cardholder to present their card by swiping, dipping or tapping, and to enter a PIN.

Reference Section

Information Available

0xD101 - Get Property

The host uses this command to get information about the device or its configuration / settings.

0xD111 - Set Property (Unsecured)

The host uses this command to set device configuration / settings that do not require security.

0xD112 - Set Property (Secured)

The host uses this command to set device configuration / settings securely.

Reference Section

Information Available

About Files

Large blobs of data uploaded to / downloaded from the device are referred to as “files” and share a common set of commands documented here, and special message type Data File Message.

0xD801 - Load Firmware File

The host uses this command to send a firmware image file, signed by MagTek, to the device as the first step in updating firmware.

0xD811 - Start Send File to Device (Secured)

The host uses this command to start sending secured files to the device for storage or processing.

0xD812 - Start Send File to Device (Unsecured)

The host uses this command to start sending unsecured files to the device for storage or processing

0xD821 - Start Get File from Device

The host uses this command to request a file stored on the device.

Reference Section

Information Available

0xD901 - Commit Firmware from File

The host uses this command to commit a file previously uploaded using Command 0xD801 - Load (Firmware File) into the device’s permanent memory after the device has authenticated the file.

Reference Section

Information Available

0xDF01 - Echo

The host uses this command to prompt the device for a response that contains the same payload it sent.

Reference Section

Information Available

0xE001 - Get Challenge

Requests a random challenge from the device, used to construct a secured command.

0xEEEE - Send Secured Command to Device

The host uses this command to request a random challenge from the device, used to construct a subsequent secured command.

0xEF01 - Load Key Using TR-31

The host uses this command to load a key into one of several available slots in the device’s secure memory.

0xEF07 - Change Device Lock Passcode

The host can use this command to change the device’s lock passcode.

0xEF11 - Get Key Info

The host uses this command to retrieve information about a key slot, including details about the key stored in that slot.

Reference Section

Information Available

0xF017 - Establish Ephemeral KBPK

The host uses this command to complete the ECDHE-ECDSA Key Exchange protocol, which enables the host and the device to generate the same TEMP KBPK key to use with Command 0xEF01 - Load Key Using TR-31 to load the Master Transport Key (MTK).

NFC/MIFARE Pass-Through - Group 0x11nn

Read Mobile Document - Group 0x12nn

User Interface - Group 0x18nn

Generic Pass-Through - Group 0x30nn

Device Control - Group 0x1Fnn

Banking Functions - Group 0x20nn

Settings & Information - Group 0xD1nn

File Operation - Group 0xD8nn

Process Files - Group 0xD9nn

Diagnostics & Utilities - Group 0xDFnn

Security - Grouo 0xEnnn

Manufacturing - Group 0xFnnn

Need Help?

For additional support, please contact MagTek Support:

Technical Support:

  • 📧 Email: support@magtek.com

  • 📞 Phone: 1-562-546-6800 (US)

  • 🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM Pacific

Online Resources:

  • 🌐 Support Portal: developer.magtek.com

  • 🌐 Official Site:

Documentation Feedback:

Help us improve this documentation!

0x1001 Start Transaction
0x1004 - Resume Transaction
Cancel Transaction - Command 0x1008

https://www.magtek.com
feedback@magtek.com
0x1806 - Personal Info Entry
0x1806 - Show Image
0x1822 - Show QR Code
0x1823 - Show Bitmap Image
0x1830 - Display Flexible UI Pages
0x1807 - LED Control
0x1840 - Card Emulation
0xD825 - Get File Info from Device
0xD831 - Delete File from Device