> 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/products/dynafamily-mms-dyna-devices/dynaprox/programmers-manual.md).

# Programmer's Manual

The DynaProx uses the shared DynaFamily Multi-Interface Card Reader Platform (MMS) command set. This manual is a device-scoped map into the [<mark style="color:red;">**API & Command Reference**</mark>](https://developer.magtek.com/api-and-command-reference) with the sections this device relies on linked below.

{% hint style="success" %}
**Applies to:** DynaProx
{% endhint %}

### In this manual

<table data-header-hidden><thead><tr><th valign="middle"></th><th></th></tr></thead><tbody><tr><td valign="middle"><strong>Reference Section</strong></td><td><strong>Information Available</strong></td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/api-and-command-reference/dynafamily-command-matrix"><mark style="color:red;"><strong>Command Support Across Products</strong></mark></a></td><td>The full device Command matrix, if you're building for more than one Dyna reader.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/products/dynafamily-mms-dyna-devices/dynaprox/programmers-manual/message-format-and-structure"><mark style="color:red;"><strong>Message Format &#x26; Structure</strong></mark></a></td><td>How MMS requests, responses, and notifications are framed and parsed.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/products/dynafamily-mms-dyna-devices/dynaprox/programmers-manual/data-types-and-shared-tlv-objects"><mark style="color:red;"><strong>Data Types &#x26; Shared TLV Objects</strong></mark></a></td><td>The shared TLV and EMV objects the commands carry.</td></tr><tr><td valign="middle"><a href="/products/dynafamily-mms-dyna-devices/dynaprox/programmers-manual/commands.md"><mark style="color:red;"><strong>Commands</strong></mark></a></td><td>The MMS command set, scoped to the DynaProx, with a supported-commands view.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/products/dynafamily-mms-dyna-devices/dynaprox/programmers-manual/notifications"><mark style="color:red;"><strong>Notifications</strong></mark></a></td><td>Asynchronous messages the DynaProx sends during transactions, device events, and firmware updates.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/products/dynafamily-mms-dyna-devices/dynaprox/programmers-manual/configurations"><mark style="color:red;"><strong>Configurations</strong></mark></a></td><td>Configurable properties and parameters.</td></tr><tr><td valign="middle"><a href="/products/dynafamily-mms-dyna-devices/dynaprox/programmers-manual/appendices.md"><mark style="color:red;"><strong>Appendices</strong></mark></a></td><td>These sections detail a variety of information on OIDs, codes, tips &#x26; taxes and more.</td></tr></tbody></table>

### See Also <a href="#see-also" id="see-also"></a>

* [<mark style="color:red;">**Security & Keys**</mark>](https://developer.magtek.com/products/dynafamily-mms-dyna-devices/dynaprox/security-and-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.
* [<mark style="color:red;">**Documentation**</mark>](https://developer.magtek.com/products/dynafamily-mms-dyna-devices/dynaprox/documentation)**-->** This page provides access to the essential documentation resources for developing with and managing the DynaProx secure card reader.he DynaProx's PCI PTS POI security policy, certifications, and the regulatory documentation for deployment.
* [<mark style="color:red;">**NFC/MIFARE**</mark>](https://developer.magtek.com/products/dynafamily-mms-dyna-devices/dynaprox/nfc-mifare) **-->**&#x57;orking with contactless cards and tags — NFC/MIFARE pass-through and the supported card technologies (NTag, Classic, DESFire, Plus).

{% hint style="info" %}
**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:** [https://www.magtek.com](https://www.magtek.com/)
* 💬 **Developer Forum:** [https://forum.magtek.com](https://forum.magtek.com/)

**Documentation Feedback:**

Help us improve this documentation! [Submit feedback](broken://spaces/1lWLescKFIPsMeIJI6Cd/pages/5314c528980689961380bea0044c1256aaeb39bc)
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.magtek.com/products/dynafamily-mms-dyna-devices/dynaprox/programmers-manual.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.