> 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/downloads-compliance-and-marketing-materials/compliance-security/product-specific-compliance/idynamo-5-gen-iii/secure-card-reader-security-policy/appendix-a-references.md).

# Appendix A References

The following documents may be used to provide additional details about the device and this security policy:

* MagTek iDynamo 5 Gen III Installation and Operation Manual PN: D998200614
* MagTek iDynamo 5 Gen III SRED, Device Inspection Manual PN: D998200620
* MagTek iDynamo 5 Gen III Programmer’s Manual COMMANDS PN: D998200587
* NIST SP 800-57-1 Recommendation for Key Management
* ANS X9.24 Part 3:2017, Retail Financial Services Symmetric Key Management, Part 3: Derived Unique Key Per Transaction Using Symmetric Techniques
* X9 TR-31:2010, Interoperable Secure Key Exchange Key Block Specification for Symmetric Algorithms
* X9.143 (TR-31) Symmetric Key


---

# 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/downloads-compliance-and-marketing-materials/compliance-security/product-specific-compliance/idynamo-5-gen-iii/secure-card-reader-security-policy/appendix-a-references.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.
