> 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/~/revisions/nGirfT12ASLhMZcOe4y9/dynafamily-mms-dyna-devices/dynaflex-ii-go/compliance.md).

# Compliance

This compliance documentation page provides the essential security and inspection guides required to maintain PCI PTS POS approval and ensure the physical integrity of DynaFlex II Go secure card readers before and after deployment.

{% hint style="success" %}
**Applies to:** DynaFlex II Go
{% endhint %}

### Documents

<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/downloads-compliance-and-marketing-materials/compliance-security/product-specific-compliance/dynaflex-ii-go/pci-pts-poi-security-policy"><mark style="color:red;"><strong>Security Policy (PCI PTS POI)</strong></mark></a></td><td>This document details the device's PCI PTS POI security features, including its support for encryption algorithms (AES, TDEA) and DUKPT key management to ensure secure payment transactions.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/downloads-compliance-and-marketing-materials/compliance-security/product-specific-compliance/dynaflex-ii-go/device-inspection-document"><mark style="color:red;"><strong>Device Inspection Document</strong></mark></a></td><td>A manual that outlines the step-by-step procedures for visually inspecting the DynaFlex II Go's hardware label, physical appearance, and tamper indicators to verify its authenticity and security before use.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/downloads-compliance-and-marketing-materials/compliance-security/product-specific-compliance/dynaflex-ii-go/package-inspection-document-without-stand"><mark style="color:red;"><strong>Package Inspection Document</strong></mark></a></td><td>A guide that details how to examine the device's secure packaging for signs of tampering during storage or transit, helping to ensure the reader has not been compromised before deployment.</td></tr></tbody></table>

### For more help

{% 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/~/revisions/nGirfT12ASLhMZcOe4y9/dynafamily-mms-dyna-devices/dynaflex-ii-go/compliance.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.