> For the complete documentation index, see [llms.txt](https://developer.magtek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/commands.md).
# 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.
{% hint style="success" %}
Applies to: All Dyna Family products
{% endhint %}
### Information in this group
| **Section** | **Information** |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [**0x10nn - Transactions**](https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/commands#transactions) | 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. |
| [**0x11nn - NFC/MIFARE Pass-Through Commands**](https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/commands#nfc-mifare) | 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) |
| [**0x18nn - User Interface**](https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/commands#user-interface) | 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. |
| [**0x1Fnn - Device Control**](https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/commands#device-control) | 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. |
| [**0x20nn - Banking Functions**](https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/commands#banking-functions-touch-display-only) | 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) |
| [**0x30nn - Generic Pass-Through Commands**](https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/commands#generic-pass-through-commands) | 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. |
| [**0xD1nn - Settings and Information**](https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/commands#settings-and-information) | 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. |
| [**0xD8nn - File Operations**](https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/commands#file-operations) | 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. |
| [**0xD9nn - Process Files**](https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/commands#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. |
| [**0xDFnn - Diagnostics and Utilities**](https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/commands#diagnostics-and-utilities) | General-purpose troubleshooting utilities, such as Echo to verify host-to-device communication. Use these to test connectivity and confirm the device is responding. |
| [**0xEnnn - Security**](https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/commands#security) | 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. |
| [**0xFnnn - Manufacturing**](https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/commands#manufacturing) | 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** |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------- |
| [**0x1001 - Start Transaction**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x10nn-transactions/0x1001-start-transaction.md) | The host uses this command to start a payment transaction. |
| [**0x1004 - Resume Transaction**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x10nn-transactions/0x1004-resume-transaction.md) | The host uses this command to provide the device with additional/modified data to resume a transaction that is currently paused. |
| [**0x1008 - Cancel Transaction**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x10nn-transactions/0x1008-cancel-transaction.md) | The host can use this command to cancel a transaction in progress that it initiated using Start Transaction. |
### NFC/MIFARE
| **Section** | **Information** |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**0x1100 - Pass Through Command For NTag/MIFARE Ultralight, Type 2**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x11nn-nfc-mifare-pass-through-commands-contactless-only/0x1100-pass-through-command-for-ntag-mifare-ultralight-type-2.md) | 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. |
| [**0x1101 - Pass Through Command for MIFARE Classic/MINI®/Plus SL1 (Security Level 1)**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x11nn-nfc-mifare-pass-through-commands-contactless-only/0x1101-pass-through-command-for-mifare-classic-mini-r-plus-sl1-security-level-1.md) | 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**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x11nn-nfc-mifare-pass-through-commands-contactless-only/0x1101-pass-through-command-for-mifare-classic-mini-r-plus-sl1-security-level-1.md) | 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. |
| [**0x1103 - Pass Through Command for MIFARE Plus, Type 2**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x11nn-nfc-mifare-pass-through-commands-contactless-only/0x1103-pass-through-command-for-mifare-plus-type-2.md) | 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** |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**0x1801 - Request Cardholder Signature (Touch Only)**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x18nn-user-interface/0x1801-request-cardholder-signature-touch-only.md) | The host uses this command to prompt a cardholder for a signature. |
| [**0x1802 - Report Cardholder Selection**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x18nn-user-interface/0x1802-report-cardholder-selection.md) | 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 (Display Only)**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x18nn-user-interface/0x1803-display-message-display-only.md) | The host uses this command to request that the device display a message for the cardholder. |
| [**0x1804 - Read Barcode (BCR Only)**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x18nn-user-interface/0x1804-read-barcode-bcr-only.md) | 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**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x18nn-user-interface/0x1805-buzzer.md) | The host uses this command to start a buzzer for playing a sequence of tones. |
| [**0x1806 - Personal Info Entry**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x18nn-user-interface/0x1806-personal-info-entry.md) | The host uses this command to prompt a cardholder for customer information. |
| [**0x1807 - LED Control**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x18nn-user-interface/0x1807-led-control.md) | The host uses this command to control the 4 LEDs of the device when the device is not in non-User Control LED states. |
| [**0x1821 - Show Image (Display Only)**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x18nn-user-interface/0x1821-show-image-display-only.md) | 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). |
| [**0x1822 - Show QR Code (Display Only)**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x18nn-user-interface/0x1822-show-qr-code-display-only.md) | 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). |
| [**0x1823 - how Bitmap Image (Display Only)**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x18nn-user-interface/0x1821-show-image-display-only.md) | 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). |
| [**0x1830 - Display Flexible UI Pages (Display Only)**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x18nn-user-interface/0x1830-display-flexible-ui-pages-display-only.md) | This command allows the host to bring up standalone pages. |
| [**0x1840 - Card Emulation**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x18nn-user-interface/0x1840-card-emulation.md) | Card emulation is initiated by receiving a 0x1840 command from the host. |
### Device Control
| **Section** | **Information** |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**0x1F01 - Reset Device**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x1fnn-device-control/0x1f01-reset-device.md) | The host uses this command to reset the device. |
| [**0x1F02 - et Notification Subscriptions**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x1fnn-device-control/0x1f02-set-notification-subscriptions.md) | The host uses this command to specify which notifications the device should send on each of its available interfaces. |
| [**0x1F03 - Extend Session (Session Managements Only)**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x1fnn-device-control/0x1f03-extend-session-session-management-only.md) | 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. |
| [**0x1F04 - Terminate Bluetooth LE Connection**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x1fnn-device-control/0x1f04-terminate-bluetooth-le-connection-bluetooth-le-only.md) | The host can use this command to terminate a Bluetooth LE connection. |
| [**0x1F05 - Erase All Bluetooth LE Bonds**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x1fnn-device-control/0x1f05-erase-all-bluetooth-le-bonds-bluetooth-le-only.md) | The host can use this command to erase all Bluetooth® LE bonds. |
### Banking Functions (Touch/Display Only)
| **Section** | **Information** |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| [**0x2001 - Request PIN with Host Supplied Account Data**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x20nn-banking-functions-touch-display-only/request-pin-with-host-supplied-account-data-banking-functions-only-command-0x2001.md) | 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**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x20nn-banking-functions-touch-display-only/request-pin-with-card-supplied-account-data-banking-functions-only-command-0x2002.md) | 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** |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**About**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x30nn-generic-pass-through-commands/about.md) | Basic information about generic pass-through commands |
| [**0x3001 - Pass-Through Mode Start/Stop**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x30nn-generic-pass-through-commands/0x3001-pass-through-mode-start-stop.md) | The host uses this command to enter or exit Pass-Through Mode. |
| [**0x3002 - Start/Top Polling**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x30nn-generic-pass-through-commands/0x3002-start-stop-polling.md) | 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 - SO 14443-4 APDU Pass-Through Commands**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0x30nn-generic-pass-through-commands/0x3003-iso-14443-4-apdu-pass-through-commands.md) | 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** |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**0xS101 - Get Property**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xd1nn-settings-and-information/0xd101-get-property.md) | The host uses this command to get information about the device or its configuration / settings. |
| [**0xD111 - Get Property (Unsecured)**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xd1nn-settings-and-information/0xd111-set-property-unsecured.md) | The host uses this command to set device configuration / settings that do not require security. |
| [**0xD112 - Set Property (Secured)**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xd1nn-settings-and-information/0xd112-set-property-secured.md) | 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** |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**About Files**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xd8nn-file-operations/about-files.md) | 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. |
| [**0xD811 - Load Firmware File**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xd8nn-file-operations/0xd801-load-firmware-file.md) | The host uses this command to send a firmware image file, signed by MagTek, to the device as the first step in updating firmware. |
| [**0xD812 - Start Send File to Device (Secured)**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xd8nn-file-operations/0xd801-load-firmware-file.md) | 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. |
| [**0xD821 - Start Send File to Device (Unsecured)**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xd8nn-file-operations/0xd812-start-send-file-to-device-unsecured-command.md) | 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. |
| [**0xD821 - Start Get File from Device**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xd8nn-file-operations/0xd821-start-get-file-from-device.md) | 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). |
| [**0xD825 - Get File Info from Device**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xd8nn-file-operations/0xd825-get-file-info-from-device-command.md) | 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). |
| [**0xD831 - Delete File from Device**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xd8nn-file-operations/0xd831-delete-file-from-device.md) | The host uses this command to request the deletion of a file stored on the device. |
### Process Files
| **Section** | **Information** |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**0xD901 - Commit Firmware from File**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xd9nn-process-files/0xd901-commit-firmware-from-file.md) | 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** |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| [**0xD01 - Echo**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xdfnn-diagnostics-and-utilities/0xdf01-echo.md) | The host uses this command to prompt the device for a response that contains the same payload it sent. |
### Security
| **Section** | **Information** |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**0xE001 - Get Challenge**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xennn-security/0xe001-get-challenge.md) | 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. |
| [**0xEEEE - Send Secured Command to Device**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xennn-security/0xeeee-send-secured-command-to-device.md) | The host uses this command to transmit another command securely. T |
| [**0xEF01 - Load Key Using TR-31**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xennn-security/0xef01-load-key-using-tr-31.md) | The host uses this command to load a key into one of several available slots in the device’s secure memory. |
| [**0xEF02 - Generate CSR Keys (WLAN Only)**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xennn-security/0xef02-generate-csr-keys-wlan-only.md) | The host uses this command to generate a key pair to be used for a certificate signing request (CSR). |
| [**0xEF03 - Generate CSR (WLAN Only)**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xennn-security/0xef02-generate-csr-keys-wlan-only.md) | The host uses this command to generate a certificate signing request (CSR) in PEM format. |
| [**0xEF06 - Change Device Lock State**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xennn-security/0xef06-change-device-lock-state.md) | The host can use this command to change the device’s lock state. |
| [**0xEF09 - Encrypt User Data**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xennn-security/0xef09-encrypt-user-data.md) | The host uses this command to request that the device encrypt a block of user data embedded in the command string. |
| [**0xEF11 - Get Key Info**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xennn-security/0xef11-get-key-info.md) | The host uses this command to retrieve information about a key slot, including details about the key stored in that slot. |
### Manufacturing
| **Section** | **Information** |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**0xF017 - Establish Ephemeral KBPK**](/api-and-command-reference/scra-dynafamily-programmers-manual/commands/0xfnnn-manufacturing/0xf017-establish-ephemeral-kbpk.md) | 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
{% hint style="info" %}
**Need Help?**
For additional support, please contact MagTek Support:
**Technical Support:**
* 📧 **Email:** [support@magtek.com](mailto:support@magtek.com?subject=Support%20Request)
* 📞 **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](mailto:feedback@magtek.com?subject=Feedback)
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://developer.magtek.com/api-and-command-reference/scra-dynafamily-programmers-manual/commands.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.