> 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/api-reference/api/payments.md).

# Payments

The **Payments APIs** let you process and manage payment transactions across multiple channels, including card-not-present, card-present (terminal), ACH, and mobile payments.

Using Payments APIs, you can:

* Process card and ACH transactions.
* Process in-person (terminal) and remote (online or mobile) payments.
* Store and reuse payment methods using tokens.
* Manage transaction batches and settlement.
* Configure payment processing settings.
* Set up recurring payments and customer billing.
* Retrieve transaction data, receipts, and reports.

### Payment types

The Payments APIs support the following payment types:

* **Cards (card-not-present):** Process remote payments such as eCommerce or manually entered card transactions.
* **Terminal (card-present):** Process in-person payments using EMV-enabled devices, including signature capture and batch processing.
* **ACH:** Process bank-to-bank transactions, including debit and credit transfers.
* **Mobile:** Process payments through mobile applications using secure tokens or device-based integrations.

Related topics:

* [Cards (card-not-present)](/api-reference/api/payments/cards-card-not-present.md)
* [Terminal (card-present)](/api-reference/api/payments/terminal-card-present.md)
* [ACH](/api-reference/api/payments/ach.md)
* [Mobile](/api-reference/api/payments/mobile.md)
* [Batches](/api-reference/api/payments/batches.md)
* [Batches Warehouse](/api-reference/api/payments/batches-warehouse.md)
* [Recurring Payments Service](/api-reference/api/payments/recurring-payments-service.md)
* [Gateway Settings](/api-reference/api/payments/gateway-settings.md)
* [Receipt Service](/api-reference/api/payments/receipt-service.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/api-reference/api/payments.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.