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

# ACH

The **ACH API** allows you to process electronic bank-to-bank payments using your customer's checking or savings account information. This API provides a secure alternative to card-based payments for businesses that prefer bank transfers.

ACH transactions are not processed in real time. They require completion of the banking process before funds are confirmed.

### ACH transaction processing steps

Unlike card transactions, ACH payments are not approved in real time. Transactions are submitted and processed in batches through the banking network.

After transaction submission, they move through the following statuses:

* The transaction is created with a **Pending** status
* The transaction enters the processing queue
* The transaction status updates to **Settling** during processing
* The transaction completes as:
  * **Settled** – Funds are successfully cleared
  * **Returned** – The transaction failed (for example, because of insufficient funds or an invalid account).

### Integration options

The following integration methods also support ACH payments:

* [Paylink](https://docs.xplorpay.com/api-reference/api/payments/gateway-settings#paylink) - Supports ACH direct debit payments.
* [JavaScript SDK](https://docs.xplorpay.com/guides) - Supports ACH credit and direct debit payments.

{% hint style="info" %}
Paya and DCS, third-party service providers, handle ACH transactions and reporting.
{% endhint %}

* [ACH Transaction](https://docs.xplorpay.com/api-reference/api/payments/ach/ach-transaction.md)
* [ACH Vault (Token)](https://docs.xplorpay.com/api-reference/api/payments/ach/ach-vault-token.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/ach.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.
