> 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/oem-readers-and-components/oem-readers/odynamo/compliance-documentation.md).

# Compliance Documentation

This page provides the compliance documentation required to maintain PCI PTS approval for the oDynamo hybrid insertion secure card reader authenticator (SCRA), including the device and package inspection guides for tamper detection and physical security verification.

### **Compliance 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/products/oem-readers-and-components/oem-readers/odynamo/compliance-documentation/device-inspection-document"><mark style="color:red;"><strong>Device Inspection Document</strong></mark></a></td><td>A step‑by‑step service and repair manual that explains how to visually inspect the oDynamo’s enclosure, bezel, screws, ventilation holes, dismount switches, and connection ports for signs of tampering or unauthorized modification to help ensure the device remains PCI PTS 5.x SRED compliant before deployment.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/products/oem-readers-and-components/oem-readers/odynamo/compliance-documentation/package-inspection-document-single-and-multi-pack"><mark style="color:red;"><strong>Package Inspection Document - Single and Multi-Pack</strong></mark></a></td><td>The Package Inspection Document provides step-by-step visual and physical verification procedures for detecting tamper evidence on oDynamo packaging—including security tape inspection, seal integrity checks, and serial number validation—to ensure the single‑pack and multi‑pack devices remain PCI compliant before installation.</td></tr></tbody></table>

### 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 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/oem-readers-and-components/oem-readers/odynamo/compliance-documentation.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.