Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
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.
Applies to: DynaProx
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: support@magtek.com
📞 Phone: 1-562-546-6800 (US)
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation!
These sections detail a variety of information on OIDs, codes, tips & taxes and more.
Applies to: DynaFlex II SCR
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.
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 PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation!
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.
Applies to: DynaProx
Reference Section
Information Available
This notification reports information about progress and state changes that occur during a transaction.
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.
Applies to: DynaProx
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)
NFC/MIFARE pass-through and NFC card emulation (DynaCast)
Compact contactless reader for attended checkout, transit, and access control
PCI PTS POI–approved SCRA for attended acceptance (no PIN entry — see the DynaFlex II PED for PIN debit)
The device sends this notification when the battery charger detects that the battery is fully charged.
This notification reports the final result of a transaction the host initiated using Command 0x1001 - Start Transaction.
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 information about general state changes that occur within the device, outside the context of specific operations like transactions
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.
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.
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 PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation!
Security & Keys
DUKPT (3DES→AES), MAC, KSNs, encryption/decryption, and PCI requirements.
NFC/MIFARE
Working with contactless cards and tags (NTag, Classic, DESFire, Plus).
Reference Section
Information Available
Programmer's Manual
The MMS command set scoped to DynaProx message format, commands, notifications, configuration, and status codes.
Commands
The commands DynaProx supports, each linking into the shared reference.
Command Support Across Products
The full device Command matrix, if you're building for more than one Dyna reader.
Reference Section
Information Available
Firmware & Downloads
The MMS command set scoped to the DynaProx: message format, commands, notifications, configuration, and status codes.
Compliance
Compliance documentation for the DynaProx, including inspection documents.
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 PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation!
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.
Applies to: DynaFlex II PED
Reference Section
Information Available
Security Policy (PCI PTS POI)
Device Inspection Document
Package Inspection Document
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 PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation!
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.
Send commands to and receive responses from a MIFARE DESFire (Type 4) tag.
Send commands to and receive responses from a MIFARE Plus (Type 2) tag.
Exchange raw ISO 14443-4 APDUs with any card that supports the protocol.
Enter or leave contactless pass-through mode.
Start or stop the reader polling for a contactless card.
The device will prepare card emulation with the parameters provided in the command and start card emulation.
Reference Section
Information Available
The NFC/MIFARE Guide section give you a selection of how-to guides on working with NFC/MIFARE.
Reference Section
Information Available
Send commands to and receive responses from an NTag or MIFARE Ultralight (Type 2) tag.
After the tag is activated, send commands to and receive responses from a MIFARE Classic, MINI, or Plus SL1 (Type 2) tag.
Need Help?
For additional support, please contact MagTek Support:
Technical Support:
📧 Email:
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.
Applies to: DynaProx
Reference Section
Information Available
Latest Firmware
📞 Phone: 1-562-546-6800 (US)
🕐 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
Universal SDK - Linux
MagneFlex Browser Web API
OID Converter
EMVConfiguration Console
Firmware Update Utility
BCR Utility
Demos & Sample Code
Reader Management System (RMS)
How to Update
Reference Section
Information Available
Installation & Operation Manual
Quick Installation Guide
Reference Section
Information Available
Universal SDK - .NET
Universal SDK - Java
Universal SDK - iOS
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 PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation!
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.
Reference Section
Information Available
Part A of EMV Terminal ID settings.
Part B of EMV Terminal ID settings.
Part C of EMV Terminal ID settings.
Reference Section
Information Available
The device uses this property to determine what character it should use when sending masked ISO/ABA track data.
The device sends this notification when the battery charge reaches 15 percent.
Reference Section
Information Available
Configure how the device runs financial transactions — EMV terminal and kernel parameters, supported entry methods, and amount, currency, and timeout handling.`
Continues the transaction group with the remaining financial/EMV properties, such as contactless and additional processing options.
Configure the USB interface on USB-connected devices, including communication mode and power behavior during USB suspend. Applies only when connected over USB.
Reference Section
Information Available
The device's top-level firmware identifier — the composite firmware ID that ties together the individual component versions and checksums listed below.
Part number, version, and build details for the device's core application firmware — the main firmware that runs the reader.
Part number and version for the EMV firmware component that handles Level 2 EMV processing for contact and contactless transactions.
Reference Section
Information Available
Read-only hardware information reported by the device, such as model, part number, and hardware revision.
Reference Section
Information Available
This OID contains a 32-bit bitmap. Each bit indicates the status of a transaction key,
The device uses this property to report its security status.
The device uses this property to report its operational status.
Reference Section
Information Available
Detail on configuring the DynaProx device.
Applies to: DynaProx
Need Help?
For additional support, please contact MagTek Support:
Technical Support:
📧 Email:
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.
Applies to: DynaFlex II PED
Section
Information available
A list of primitive data types used by TLV data objects.
📞 Phone: 1-562-546-6800 (US)
🕐 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
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
The identifier and version of the China UnionPay contactless kernel firmware.
Identifies the custom user-interface package loaded on the device — which custom UI build (if any) is installed, and its version.
Information about parsing EMV ARQC Type or Merchant Data Container data for each track into individual values embedded in the tracks.
A pre-defined set of messages by string ID that the host and device use for various user interface features.
Information on the key type, variant, and other information the host can use to decrypt encrypted data included in various payloads.
Information on how the device formats ARQC messages.
Information on how the device formats ARPC messages
Information on the device formats EMV batch data, such as merchant data and pre-defined EMV batch data tags.
Information on loading this file type to control the behavior of the device’s EMV contact kernel.
Information on loading this file type to control the behavior of the device’s EMV kernel.
Information on loading this file type to control the behavior of the device’s EMV kernels.
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).
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)
The signature capture file type produced when the host invokes Request Cardholder Signature - Command 0x1801 (Touch Only)
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.
Information on tags used with security parameters.
Information on tags used to identify key types.
Information on tags used with NFC UID Types. (EMV Contactless Only)
Information on tags used with GPORT-1 Types. (EMV Contactless Only)
Information on tags used with TR-31 Key Blocks.
Information on tags used with DUKPT Keys.
Information on file types that conform to the common file structure format.
These file types conform to the Common File Structure format. The File Payload of these files contain a certificate in PEM format.
Information on CSR File Types.
Card emulation enables a DynaFlex/DynaProx device to simulate a Type 4 smart card.
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 PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation!
How the DynaProx protects cardholder data and manages keys. These are shared DynaFamily concepts, documented in the Guides Section:
Applies to: DynaProx
Reference Section
Information Available
DUKPT: 3DES/TDEA --> AES Migration
How DUKPT derives a unique key per transaction, and the path (and reasons) for moving from legacy 3DES/TDEA DUKPT to AES DUKPT on your devices and host.
Key Serial Numbers (KSN)
What a KSN is, how it's structured, and how it identifies the unique key used to encrypt a given transaction under DUKPT.
Message Authentication Codes (MAC)
How a MAC lets the host and device confirm a message hasn't been altered in transit, and when one is required.
Encryption & Decryption
How the reader encrypts data at the point of read (SRED), how to determine which key was used, and how to decrypt the output on your host.
TR-31 Key Blocks
The ANSI TR-31 key-block format used to transport and load keys securely into the device.
PCI requirements (24-hour Reset, device lock)
The operational requirements the device enforces for PCI compliance: the 24-hour automatic reset and the device lock feature.
Reference Section
Information Available
This section covers how DynaFamily readers protect cardholder data and manage keys.
Need Help?
For additional support, please contact MagTek Support:
Technical Support:
📧 Email: support@magtek.com
📞 Phone: 1-800-788-6835 (US) | +1-562-546-6616 (International)
🕐 Hours: Monday-Friday, 6:00 AM - 5:00 PM PST
Online Resources:
🌐 Official Site:
💬 Developer Forum:
Documentation Feedback:
Help us improve this documentation!
The DynaProx uses the shared DynaFamily 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: DynaProx
Reference Section
Information Available
The full device Command matrix, if you're building for more than one Dyna reader.
Security & Keys --> How the DynaProx 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 DynaProx'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).
Message Format & Structure
How MMS requests, responses, and notifications are framed and parsed.
Data Types & Shared TLV Objects
The shared TLV and EMV objects the commands carry.
Commands
The MMS command set, scoped to the Go, with a supported-commands view.
Notifications
Asynchronous messages the DynaProx sends during transactions, device events, and firmware updates.
Configurations
Configurable properties and parameters.
Status Codes & Responses
Result and error codes the device returns.
Need Help?
For additional support, please contact MagTek Support:
Technical Support:
📧 Email: support@magtek.com
📞 Phone: 1-800-788-6835 (US) | +1-562-546-6616 (International)
🕐 Hours: Monday-Friday, 6:00 AM - 5:00 PM PST
Online Resources:
🌐 Official Site:
💬 Developer Forum:
Documentation Feedback:
Help us improve this documentation!