# Payment Processing

Payment processing is how your merchants accept and authorize card and bank payments on Xplor Pay.

Pick the integration based on channel (in-person, web, recurring, ACH) and UX control.

### Pick a Payment Integration

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Cloud EMV</strong></td><td>Card-present for POS and terminals (unified API).</td><td><a href="/pages/d50fd926a149570d6da53b6176593657487e4f5c">Learn more</a></td></tr><tr><td><strong>Mobile EMV SDK</strong></td><td>In-app card-present for iOS/Android (Bluetooth reader).</td><td><a href="/pages/5bcfe8770953b32f5aa2da108702851c69040757">Learn more</a></td></tr><tr><td><strong>JavaScript SDK</strong></td><td>Web checkout with hosted iframe + wallets.</td><td><a href="/pages/55614915657f2a4c778f1e4623ee4889c0bca0d8">Learn more</a></td></tr><tr><td><strong>Recurring Payments</strong></td><td>Stored payment methods + scheduled billing.</td><td><a href="/pages/6b28611c0fb3c40d2ccdd7afeff5743e7903a6fb">Learn more</a></td></tr><tr><td><strong>Paylink</strong></td><td>Payment links using SMS or email.</td><td><a href="https://docs.xplorpay.com/getting-started/getting-started/our-products/payment-processing/paylink">Learn more</a></td></tr><tr><td><strong>ACH Transactions</strong></td><td>Bank payments with tokenization.</td><td><a href="/pages/13240c96b287e48c735ff4f5076e88be2f8c4e8f">Learn more</a></td></tr></tbody></table>

{% hint style="info" %}
Rule of thumb:

* Building for **terminals / POS**: start with **Cloud EMV**.
* Building **mobile in-person** payments: use **Mobile EMV SDK**.
* Building **web checkout**: use the **JavaScript SDK**.
* Charging on a schedule: use **Recurring Payments** (needs a stored payment method).
* Requesting payment via a payment link: use **Paylink** (send link by SMS or email).
* Want lower-cost **bank payments**: use **ACH Transactions**.
  {% endhint %}

{% hint style="warning" %}
Card-present options are device-specific:

* **Cloud EMV** supports selected terminals (for example, PAX and Dejavoo).
* **Mobile EMV SDK** uses the **ID TECH VP3300** reader.
  {% endhint %}

### Comparison Matrix

| Solution                                                                                                     | Channel                   | Best for                                                | Integration type                          | Hardware required               |
| ------------------------------------------------------------------------------------------------------------ | ------------------------- | ------------------------------------------------------- | ----------------------------------------- | ------------------------------- |
| [Cloud EMV](/getting-started/getting-started/our-products/payment-processing/cloud-emv.md)                   | In-person (card-present)  | POS platforms supporting multiple terminals             | REST API                                  | Yes (supported terminals)       |
| [Mobile EMV SDK](/getting-started/getting-started/our-products/payment-processing/mobile-emv-sdk.md)         | In-person (card-present)  | Mobile apps that want embedded payments                 | iOS/Android SDK + Mobile Payments API     | Yes (VP3300 via Bluetooth)      |
| [JavaScript SDK](/getting-started/getting-started/our-products/payment-processing/javascript-sdk.md)         | Online (card-not-present) | Hosted checkout + wallet support with reduced PCI scope | JS SDK + backend token submission         | No (optional readers supported) |
| [Recurring Payments](/getting-started/getting-started/our-products/payment-processing/recurring-payments.md) | Scheduled billing         | Subscriptions, installments, maintenance plans          | API                                       | No                              |
| [Paylink](https://docs.xplorpay.com/getting-started/getting-started/our-products/payment-processing/paylink) | Online (card-not-present) | Link-based payments via SMS or email.                   | API                                       | No                              |
| [ACH Transactions](/getting-started/getting-started/our-products/payment-processing/ach-transactions.md)     | Bank payments             | Lower-cost payments and bank-based recurring            | API (also supported via JS SDK / PayLink) | No                              |

### Next Step

If you haven’t onboarded merchants yet, start with [Merchant Onboarding](/getting-started/getting-started/our-products/merchant-onboarding.md).

Once you’re processing payments, you’ll usually want [Reporting](/getting-started/getting-started/our-products/reporting-solutions/reporting.md) and [Financial Management](/getting-started/getting-started/our-products/financial-management.md) next.

### Need Help?

{% hint style="success" %}
Tell us your channel (POS, mobile, web) and devices. We’ll recommend the fastest path with the lowest compliance overhead.

<a href="https://xplorpay.com/getting-started/" class="button primary">Get in touch</a>
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.xplorpay.com/getting-started/getting-started/our-products/payment-processing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.