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

Documents

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.

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

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

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.

Pass-through Commands

Working with contactless cards and tags on the DynaFlex II SCR, 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.

Pass-through Commands

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

System Status Information - Property Group 2.3.1.nnn

MMS notifications are the asynchronous messages the DynaFlex II PED 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.

This page provides access to the essential software resources for developing with and managing the DynaFlex II SCR 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.

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.

Every exchange with the DynaProx — 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.

MMS notifications are the asynchronous messages the DynaFlex II SCR 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.

From Transactions - Source 0x01nn

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)

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

System Status Information - Property Group 2.3.1.nnn

The DynaFlex Family resource hub provides documentation, software, and developer tools for a line of PCI PTS POI certified Secure Card Reader Authenticators (SCRAs) designed for modern, omni‑channel payment environments. The family includes the base DynaFlex, the DynaFlex Pro with a color touchscreen display, and the DynaFlex BCR with barcode scanning, all of which accept magnetic stripe, EMV® contact chip, EMV contactless, and NFC contactless payments (Apple Pay®, Google Pay™, Samsung Pay®) along with 1D/2D barcode scanning. Connectivity options include USB, Bluetooth® LE, and 802.11 wireless networking, all backed by MagTek’s MagneSafe® Security Architecture with AES‑256 encryption and DUKPT key management.

DynaFlex Pro/SCR (Gen I) Support Page

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.

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.

• Contactless (NFC) card and mobile wallet acceptance — tap-to-pay, no contact slot or magnetic stripe

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

Working with contactless cards and tags on the DynaProx, 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.

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

MMS notifications are the asynchronous messages the DynaProx 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.

From Transactions - Source 0x01nn

This page provides access to the essential software resources for developing with and managing the DynaFlex II PED 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.

Firmware

This page provides resources for MagTek's MMS (MagTek Messaging Schema) Dyna device family, which includes secure card readers and PIN pads that communicate using the MMS command set. These devices support reading magnetic stripe, EMV® Contact Chip, EMV Contactless, NFC Mobile Wallets, Non-payment NFC technologies, and 1D/2D barcodes. Here you will find documentation covering device communication protocols, developer tools, and configuration guides for various Dyna device models.

DynaFamily (MMS Dyna Devices)

Every exchange with the DynaFlex II SCR — 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 Dyna-family readers and is documented once in the shared reference.

Settings & Information - Group 0xD1nn

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.

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.

Working with contactless cards and tags on the DynaFlex II PED, 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.

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

The DynaFlex II SCR is a compact, countertop secure card reader authenticator (SCRA) that reads contact chip, contactless (NFC), and magnetic-stripe cards and encrypts cardholder data at the point of read (SRED). It connects over USB and uses the shared DynaFamily MMS command set, so everything you build against it is documented in the API & Command Reference and linked below.

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

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

The DynaFlex II SCR uses the shared DynaFamily Multi-Interface Card Reader Platform (MMS) command set. This manual is a device-scoped map into the with the sections this device relies on linked below.

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

This page provides access to the essential software resources for developing with and managing the DynaProx 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.

Firmware

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

Documents

Every exchange with the DynaFlex II PED — 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 Dyna-family readers and is documented once in the shared reference.

Settings & Information - Group 0xD1nn

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.

DynaFlex II Go Major Components

Top Face

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.

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.