> 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/sdks-and-tools/universal-sdk-documentation/android/appendices.md).

# Appendices

### Appendices

Supplementary reference material for the MagTek Universal SDK, including the full status-code list, a step-by-step API walk-through, the EMV transaction flow, and integration guidance for mobile-wallet value-added services (Apple VAS and Google Wallet Smart Tap).

### In This Section

<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/sdks-and-tools/universal-sdk-documentation/android/appendices/appendix-a-status-codes"><mark style="color:red;"><strong>A: Status Codes</strong></mark></a></td><td>The complete list of status and result codes returned by the SDK, with their meanings for handling success and error conditions.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/universal-sdk-documentation/android/appendices/appendix-b-api-walk-through"><mark style="color:red;"><strong>B: API Walk Through</strong></mark></a></td><td>A step-by-step walk-through of a typical integration, showing the API calls in sequence from connection through a completed transaction.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/universal-sdk-documentation/android/appendices/appendix-c-emv-transaction-flow"><mark style="color:red;"><strong>C: EMV Transaction Flow</strong></mark></a></td><td>The end-to-end EMV transaction sequence — the stages and SDK interactions involved in processing a chip-card payment.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/universal-sdk-documentation/android/appendices/appendix-d-apple-vas"><mark style="color:red;"><strong>D: Apple VAS</strong></mark></a></td><td>Guidance for using Apple Value Added Services to read Apple Wallet passes over contactless.</td></tr><tr><td valign="middle"><a href="https://developer.magtek.com/sdks-and-tools/universal-sdk-documentation/android/appendices/appendix-e-google-wallet-smart-tap-vas"><mark style="color:red;"><strong>E: Google Wallet Smart Tap VAS</strong></mark></a></td><td>Guidance for using Google Wallet Smart Tap to read passes and value-added service data over contactless.</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 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/sdks-and-tools/universal-sdk-documentation/android/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.