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

# Overview

The **Quick Starts** help you launch the right Xplor Pay integration fast. Use this page to choose a solution, prepare your environment, and complete the core setup steps.

### What to expect

Use this space to:

* Choose the integration that matches your product.
* Complete the minimum setup required to start.
* Test the full flow before production.

{% hint style="info" %}
Each Quick Start includes its own prerequisites, setup steps, and solution-specific details.
{% endhint %}

### Required steps

{% stepper %}
{% step %}

### Get access and configuration

Make sure you have the credentials and environment details required for your solution.

This usually includes:

* API or public keys.
* Sandbox or test URLs.
* Account or pricing configuration.
  {% endstep %}

{% step %}

### Choose the right integration path

Pick the solution that matches your customer journey and device model.

Use a hosted flow when you want less implementation work. Use an SDK or device-based option when you need more control in your app or checkout experience.
{% endstep %}

{% step %}

### Build the minimum flow

Implement the shortest path to integrate successfully.

For most integrations, this means you:

* Collect payment or onboarding data.
* Send the required API request or SDK call.
* Handle the response, token, or status update.
  {% endstep %}

{% step %}

### Test before go-live

Run the full flow in your test environment.

Confirm that you can:

* Complete the main success path.
* Handle errors or declines.
* Verify downstream updates such as status, reporting, or saved payment data.
  {% endstep %}
  {% endstepper %}

### Choose a Quick Start

#### Payments and onboarding

* [Hosted Merchant Onboarding](/quick-starts/hosted-merchant-onboarding.md)
* [JavaScript](/quick-starts/javascript.md)
* [Cloud EMV](/quick-starts/cloud-emv.md)

#### Mobile SDKs

* [iOS Framework](/quick-starts/ios-framework.md)
* [Payment UI](/quick-starts/payment-ui.md)
* [Android Framework](/quick-starts/android-framework.md)

#### Additional solutions

* [Recurring Payments](/quick-starts/recurring-payments.md)
* [ACH Transactions](/quick-starts/ach-transactions.md)
* [Disputes Management](/quick-starts/disputes-management.md)
* [Reporting](/quick-starts/reporting.md)

### Next step

Start with the Quick Start that matches your integration model, then complete its prerequisites before you begin implementation.


---

# 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/quick-starts/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.