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

# Overview

Our SDKs help you accept payments across web, mobile, and point-of-sale experiences. Choose the SDK that matches your customer touchpoint, device model, and Payment Card Industry (PCI) scope.

### Choose the right SDK

#### JavaScript SDK

Use the **JavaScript SDK** to accept payments on a website. It provides a browser-based payment framework, supports responsive design, and lets you style the payment experience from the host page.

This SDK is a fit when you need to:

* Collect payments in a web checkout flow.
* Support Apple Pay or Google Pay on the web.
* Work with supported web-connected readers.

Start here: [JavaScript](/guides/javascript.md)

#### Mobile EMV

Use **Mobile EMV** to accept payments in an iOS or Android app with supported mobile card readers. It works with the Mobile Payments API and supports chip card acceptance through audio-jack and Bluetooth-enabled devices.

This SDK is a fit when you need to:

* Accept in-person payments in a mobile app.
* Connect to supported mobile readers.
* Build an app-based checkout experience for staff or customers.

Start here: [Mobile EMV](/guides/mobile-emv.md)

#### Cloud EMV

Use **Cloud EMV** for a semi-integrated point-of-sale payment flow. It lets you connect to supported payment terminals through a unified cloud-based integration.

This SDK is a fit when you need to:

* Integrate payment terminals into a POS platform.
* Reduce PCI DSS scope.
* Avoid separate integrations for each terminal model.

Start here: [Cloud EMV](/guides/cloud-emv.md)

### What to prepare

Before you start, confirm these details:

* Your target platform — web, mobile app, or POS.
* Your supported payment devices and checkout flow.
* The API access and credentials your integration requires.

### Recommended path

Use this sequence to integrate with our SDKs faster:

1. Pick the SDK that matches your platform and hardware.
2. Complete the prerequisites for that SDK.
3. Build the payment form, device flow, or terminal flow.
4. Process test transactions before going live.


---

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