Commands
Commands
The DynaFamily card readers accept the Multi-Interface Card Reader Platform (MMS) command set — the messages you send to run transactions, read cards, drive the display and prompts, manage keys and files, and query or configure the reader. Full syntax, parameters, responses, and examples are maintained in the shared reference.
Applies to: All Dyna Family products
Information in this group
Section
Information
Start, resume, and cancel EMV, contactless, and magnetic-stripe payment transactions. This is the core command group for running a sale or authorization on the device.
Send native card commands to read and write NFC tags and MIFARE cards (Ultralight, Classic, Plus, DESFire). Used for non-payment contactless applications such as loyalty, access, and ticketing. (Contactless Only)
Control the device's cardholder- and operator-facing features: prompts and messages, LEDs, the buzzer, barcode scanning, personal-info entry, and card emulation. Use these to guide the user through a transaction and capture input.
Manage the device's operational and connection state: reset the device, set notification subscriptions, and manage Bluetooth LE sessions and bonds. These govern how the device runs and communicates rather than how it processes cards.
Prompt the cardholder for a PIN and generate the encrypted PIN block for online-PIN debit and banking, using host-supplied or card-supplied account data. Available only on devices with a PIN-entry surface. (Touch/Display Only)
Open a direct channel to a contactless card and exchange raw ISO 14443-4 APDUs, with control over card polling. Use this for custom or proprietary contactless schemes not covered by the dedicated command groups.
Read and change the device's configuration by getting and setting individual properties, in both secured and unsecured forms. This is how you query device state and adjust its behavior.
Transfer files to and from the device: send firmware, configuration, and certificate files, retrieve them, query file info, and delete them. Handles moving files; applying them is covered under Process Files.
Act on files already loaded onto the device, such as committing a transferred firmware file to activate it. These commands complete operations that begin as a transfer in File Operations.
General-purpose troubleshooting utilities, such as Echo to verify host-to-device communication. Use these to test connectivity and confirm the device is responding.
Perform cryptographic and device-security operations: challenge/response authentication, sending secured commands, loading keys via TR-31, retrieving key information, and managing the device lock. These establish and maintain the device's secure state.
Provisioning and production-time operations, such as establishing an ephemeral key block protection key (KBPK) for secure key injection. Typically used during manufacturing and key loading rather than day-to-day integration.
Transactions
Section
Information
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 can use this command to cancel a transaction in progress that it initiated using Start Transaction.
NFC/MIFARE
Section
Information
After an NTag/MIFARE Ultralight is activated, 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.
After a MIFARE DESFire Light/EV1/EV2/EV3 Tag is activated, the host uses this command to send commands and receive responses to and from a MIFARE DESFire Tag.
After a MIFARE Plus EV1/EV2/SE/X Tag is activated, the Host uses this command to send commands and receive responses to and from a MIFARE Plus tag.
User Interface
Section
Information
The host uses this command to prompt a cardholder for a signature.
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 request that the device display a message for the cardholder.
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.
The host uses this command to start a buzzer for playing a sequence of tones.
The host uses this command to prompt a cardholder for customer information.
The host uses this command to control the 4 LEDs of the device when the device is not in non-User Control LED states.
The host uses this command to trigger the device to immediately show a pre-loaded image on the display, provided the device is not in a mode that has exclusive use of the display (such as during a transaction).
The host uses this command to direct the device to immediately show a QR code on the display, provided the device is not in a mode that has exclusive use of the display (such as during a transaction).
The host uses this command to trigger the device to immediately show a bitmap file the host includes as a parameter, provided the device is not in a mode that has exclusive use of the display (such as during a transaction).
This command allows the host to bring up standalone pages.
Card emulation is initiated by receiving a 0x1840 command from the host.
Device Control
Section
Information
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.
The host can use this command to extend a session for open protocol interfaces, such as the WLAN interface, which require session management to meet PCI requirements.
The host can use this command to terminate a Bluetooth LE connection.
The host can use this command to erase all Bluetooth® LE bonds.
Banking Functions (Touch/Display Only)
Section
Information
This command directs the device to prompt the cardholder to enter a PIN when a card is not present or is not presented.
This command directs the device to prompt the cardholder to present their card by swiping, dipping or tapping, and to enter a PIN.
Generic Pass-through Commands
Section
Information
Basic information about generic pass-through commands
The host uses this command to enter or exit Pass-Through Mode.
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.
After the NFC Type A or Type B card is activated, the host uses this command to send application-level APDUs to a PICC that supports ISO 14443-4 Protocol.
Settings and Information
Section
Information
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.
The host uses this command to set device configuration / settings securely. Properties that require security should specify that they do in their documentation.
File Operations
Section
Information
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.
The host uses this command to start sending secured files to the device for storage or processing. It is similar to Start Send File to Device (Unsecured), but is used to send a different subset of file types that impact device security and require some form of authentication from the host.
The host uses this command to start sending unsecured files to the device for storage or processing. It is similar to Start Send File to Device (Secured) but is used to send a different subset of file types that do not impact device security.
The host uses this command to request a file stored on the device. File types include standard files (images and certificates), MagTek custom files (configuration, firmware), and in some cases even large data blob output (such as signature capture data).
The host uses this command to request the file information of a file stored on the device. File types include standard files (images and certificates), MagTek custom files (configuration, firmware), and in some cases even large data blob output (such as signature capture data).
The host uses this command to request the deletion of a file stored on the device.
Process Files
Section
Information
The host uses this command to commit a file previously uploaded using Command 0xD801 into the device’s permanent memory after the device has authenticated the file.
Diagnostics and Utilities
Section
Information
The host uses this command to prompt the device for a response that contains the same payload it sent.
Security
Section
Information
The host uses this command to request challenge data from the device, which the host can then use to perform a specific sensitive operation / modify a specific type of device setting.
The host uses this command to transmit another command securely. T
The host uses this command to load a key into one of several available slots in the device’s secure memory.
The host uses this command to generate a key pair to be used for a certificate signing request (CSR).
The host uses this command to generate a certificate signing request (CSR) in PEM format.
The host can use this command to change the device’s lock state.
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.
Manufacturing
Section
Information
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 Load Key Using TR-31 to load the Master Transport Key (MTK).
Need More Help
Last updated