# 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.

* [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: 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/api-reference/api/payments.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.