Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
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 API & Command Reference with the sections this device relies on linked below.
Applies to: DynaFlex II SCR
Reference Section
Information Available
The full device Command matrix, if you're building for more than one Dyna reader.
--> How the SCR protects data and manages keys: DUKPT (3DES→AES), MAC, KSNs, encryption/decryption, and the PCI requirements like the 24-hour reset and device lock.
--> The SCR's PCI PTS POI security policy, certifications, and the regulatory documentation for deployment.
-->Working with contactless cards and tags — NFC/MIFARE pass-through and the supported card technologies (NTag, Classic, DESFire, Plus).
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)
Optional barcode reader (BCR) for scanning outside a transaction
Compact countertop secure card reader authenticator (SCRA)
PCI PTS POI–approved SCRA for attended acceptance (no PIN entry — see the DynaFlex II PED for PIN debit)
Section
Description
The MMS command set scoped to the SCR: message format, commands, notifications, configuration, and status codes.
The commands the SCR supports, each linking into the shared reference.
Section
Description
The MMS command set scoped to the SCR: message format, commands, notifications, configuration, and status codes.
Applies to: DynaFlex II SCR
How MMS requests, responses, and notifications are framed and parsed.
The shared TLV and EMV objects the commands carry.
The MMS command set, scoped to the SCR, with a supported-commands view.
Asynchronous messages the SCR sends during transactions, device events, and firmware updates.
Configurable properties and parameters.
Result and error codes the device returns.
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.
🕐 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 full device Command matrix, if you're building for more than one Dyna reader.
DUKPT (3DES→AES), MAC, KSNs, encryption/decryption, and PCI requirements.
Working with contactless cards and tags (NTag, Classic, DESFire, Plus).
After the tag is activated, send commands to and receive responses from a MIFARE Classic, MINI, or Plus SL1 (Type 2) tag.
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
Send commands to and receive responses from an NTag or MIFARE Ultralight (Type 2) tag.
How the DynaFlex II SCR protects cardholder data and manages keys. These are shared DynaFamily concepts, documented in the Guides Section:
Applies to: DynaFlex II SCR
Reference Section
Information Available
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.
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.
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.
🕐 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
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.
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.
Applies to: DynaFlex II SCR
What a KSN is, how it's structured, and how it identifies the unique key used to encrypt a given transaction under DUKPT.
How a MAC lets the host and device confirm a message hasn't been altered in transit, and when one is required.
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.
The ANSI TR-31 key-block format used to transport and load keys securely into the device.
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.
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.
These are the display limits that are supported.
DynaFlex II SCR features a single physical button. Pressing and holding this button can activate additional functions on the device.
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 SCR
Reference Section
Information Available
Detail on configuring the DynaFlex II SCR device.
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.
🕐 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.
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.
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.
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.
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.
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.
Configure the USB interface on USB-connected devices, including communication mode and power behavior during USB suspend. Applies only when connected over USB.
Part number and version for the EMV firmware component that handles Level 2 EMV processing for contact and contactless transactions.
The device uses this property to report its operational status.
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.
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
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 transaction.
Applies to: DynaFlex II SCR
🕐 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 notification reports Firmware is up to date for host initiated update.
The DynaFlex II SCR 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 SCR supports, each linking into that reference.
Applies to: DynaFlex II SCR
Reference Section
Information Available
The host uses this command to start a payment transaction.
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.
The Host uses this command to send commands and receive responses to and from a MIFARE Plus tag.
The host uses this command to prompt a cardholder for customer information.
Card emulation is initiated by receiving a 0x1840 command from the host.
The host uses this command to start sending unsecured files to the device for storage or processing
The host uses this command to request a file stored on the device.
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.
The host can use this command to change the device’s lock state.
The host can use this command to change the device’s lock passcode.
The host uses this command to request that the device encrypt a block of user data embedded in the command string.
The host uses this command to retrieve information about a key slot, including details about the key stored in that slot.
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.
Reference Section
Information Available
The host uses this command to send commands and receive responses to and from a NTag/MIFARE Ultralight.
After a MIFARE Tag is activated, the host uses this command to send commands and receive responses to and from a MIFARE tag.
Reference Section
Information Available
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.
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.
Reference Section
Information Available
The host uses this command to reset the device.
The host uses this command to specify which notifications the device should send on each of its available interfaces
Reference Section
Information Available
The host uses this command to get information about the device or its configuration / settings.
The host uses this command to set device configuration / settings that do not require security.
Reference Section
Information Available
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.
The host uses this command to send a firmware image file, signed by MagTek, to the device as the first step in updating firmware.
Reference Section
Information Available
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
The host uses this command to prompt the device for a response that contains the same payload it sent.
Reference Section
Information Available
Requests a random challenge from the device, used to construct a secured command.
The host uses this command to request a random challenge from the device, used to construct a subsequent secured command.
Reference Section
Information Available
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).
The host uses this command to send commands and receive responses to and from a MIFARE DESFire Tag.
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.
The host uses this command to set device configuration / settings securely.
The host uses this command to start sending secured files to the device for storage or processing.
The host uses this command to load a key into one of several available slots in the device’s secure memory.
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.
E
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.
Section
Information available
Applies to: DynaFlex II SCR
A list of primitive data types used by TLV data objects.
🕐 Hours: Monday-Friday, 5:30 AM - 5:00 PM PST
Online Resources:
🌐 Support Portal: developer.magtek.com
Documentation Feedback:
Help us improve this documentation!