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)
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.Sample ACH Request (summary)
- Endpoint: Use the same payment/invoice flow as for cards, but send ACH details instead of
CreditCardinPaymentMethod(e.g. routing number, account number, account type). - Base URL: Use your environment (e.g.
https://api-sandbox.revolv3.comfor sandbox). - Response: You get an attempt ID and a status such as
Pending; final status is updated when the ACH cycle completes.
Where to Go Next
- ACH Direct Debit Payments — When to use ACH, object structure, and timing
- Test ACH for Account Verification — Sandbox test data for ACH