> For the complete documentation index, see [llms.txt](https://docs.xplorpay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xplorpay.com/guides/mobile-emv.md).

# Mobile EMV

The **Mobile EMV** SDK helps you integrate payment acceptance into your iOS or Android app. It works with the [Mobile Payments API](https://docs.xplorpay.com/api-references/payments/mobile/mobile-payment-transactions) to reduce PCI scope through layered security controls. The SDK supports audio‑jack and Bluetooth‑enabled mobile card readers so you can accept various payment types, including chip card payments.

See the following articles to integrate the **Mobile EMV** SDK:

* [iOS framework](https://docs.xplorpay.com/guides/mobile-emv/ios-framework.md)
* [Android framework](https://docs.xplorpay.com/guides/mobile-emv/android-framework.md)
* [IDTech VP3300](https://docs.xplorpay.com/guides/mobile-emv/idtech-vp3300.md)
* [Start transaction](https://docs.xplorpay.com/guides/mobile-emv/start-transaction.md)
* [Generate JSON Web Token](https://docs.xplorpay.com/guides/mobile-emv/generate-json-web-token.md)
* [Feedback messages](https://docs.xplorpay.com/guides/mobile-emv/feedback-messages.md)
* [ClearentWrapper](https://docs.xplorpay.com/guides/mobile-emv/clearentwrapper.md)


---

# 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://docs.xplorpay.com/guides/mobile-emv.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.
