> 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/appendices.md).

# Appendices

## Appendices

These sections detail information about the device's status. 

{% hint style="success" %}
Applies to: All Dyna Family products
{% endhint %}

### Appendices in this Group

| **Notification**                                                                                                                                                                          | **Information**                                                                                                                                                                                                |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [<mark style="color:red;">**A: Object IDs and ITU-T x660**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/appendices/appendix-a-object-ids-oids-and-itu-t-x660.md) | For modular management of device functions, information, and settings, this standard makes extensive use of Object Identifiers (also known as Object IDs or OIDs) as defined in ITU-T X.660 \| ISO/IEC 9834-1. |
| [<mark style="color:red;">**B: Barcode Reader Symbologies**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/appendices/appendix-b-barcode-reader-symbologies.md)    | Barcode symbology refers to the way in which data is encoded in a barcode. It uses either spaced lines, dots or squares.                                                                                       |
| [<mark style="color:red;">**C: Erasing EMV Configurations**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/appendices/appendix-c-erasing-emv-configurations.md)    | This section will help erase already existing EMV configurations.                                                                                                                                              |
| [<mark style="color:red;">**D: Tip & Tax DIsplay**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/appendices/appendix-d-tip-and-tax-display-limits-touch-only.md)  | All of the space limitations on the device.                                                                                                                                                                    |
| [<mark style="color:red;">**E: Physical Button**</mark>](/api-and-command-reference/scra-dynafamily-programmers-manual/appendices/appendix-e-physical-button-dynaflex-only.md)            | Every DynaFlex device features a single physical button.  Pressing and holding this button can activate additional functions on the device.                                                                    |

### See Also

* <mark style="color:red;">**Commands**</mark>**&#x20;-->** This is what triggers a transaction
* <mark style="color:red;">**Messages**</mark>**&#x20;-->** The formats notifications are delivered in.


---

# 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/appendices.md?ask=<question>&goal=<endgoal>
```

`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.