> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revolv3.com/llms.txt
> Use this file to discover all available pages before exploring further.

# ACH Payment Flow

> End-to-end ACH payment flow: verification and settlement. Sequence diagram and how timing differs from card payments. Links to ACH direct debit and test data.

This page describes how ACH (bank account) payments move through Revolv3: from your request through verification and settlement. ACH is **not** instant like card payments; it uses batch processing and can take several business days.

## Flow Overview

| Phase                         | What happens                                                         | Typical timing          |
| ----------------------------- | -------------------------------------------------------------------- | ----------------------- |
| **Submit**                    | You send the ACH payment request; Revolv3 accepts it.                | Immediate               |
| **Verification / processing** | Banks and the ACH network process the transaction in batches.        | 1–3 business days       |
| **Settlement**                | Funds are debited from the customer’s account and credited to yours. | Day 3–5 (business days) |

## Sequence: ACH Payment (Verification and Settlement)

```mermaid theme={null}
sequenceDiagram
  participant App as Your app
  participant Revolv3 as Revolv3 API
  participant Processor as ACH processor
  participant ACH as ACH network
  participant Bank as Customer bank

  App->>Revolv3: POST payment (ACH details, amount, invoice)
  Revolv3->>Processor: Submit ACH debit
  Processor->>ACH: Batch entry
  Revolv3-->>App: 200 + attempt id, status Pending

  Note over ACH,Bank: 1–3 business days

  ACH->>Bank: Debit request
  Bank-->>ACH: Accept/reject
  ACH-->>Processor: Result
  Processor-->>Revolv3: Status update (e.g. Paid / Noncollectable)

  Note over Revolv3: Webhook / polling

  Revolv3-->>App: Event or GET attempt: Paid or failed
```

**Important**: The API returns quickly with a “pending” attempt. Final outcome (e.g. `Paid`, `Noncollectable`) comes later via webhooks or by polling invoice/attempt status.

## Why ACH Takes Multiple Days

ACH does not authorize and settle in real time like cards. Transactions are batched and processed on business days by the ACH network and banks. For more detail, see [ACH Direct Debit Payments](/docs/core-concepts/paymentmethod/ach-direct-debit).

## Sample ACH Request (summary)

* **Endpoint**: Use the same payment/invoice flow as for cards, but send **ACH** details instead of `CreditCard` in `PaymentMethod` (e.g. routing number, account number, account type).
* **Base URL**: Use your environment (e.g. `https://api-sandbox.revolv3.com` for sandbox).
* **Response**: You get an attempt ID and a status such as `Pending`; final status is updated when the ACH cycle completes.

For full ACH object shape, required fields, and test values, see [ACH Direct Debit Payments](/docs/core-concepts/paymentmethod/ach-direct-debit) and [Test ACH for Account Verification](/docs/testing-sandbox/test-ach-for-validate-person).

## Where to Go Next

* [ACH Direct Debit Payments](/docs/core-concepts/paymentmethod/ach-direct-debit) — When to use ACH, object structure, and timing
* [Test ACH for Account Verification](/docs/testing-sandbox/test-ach-for-validate-person) — Sandbox test data for ACH