ACH API integration
An ACH API, wired into your systems.
Your platform creates payments, checks accounts and receives status updates, without anyone touching a file.
{ "type": "debit", "sec": "WEB",
"amount": 18600, "account": "acct_sample_6789",
"description": "PURCHASE",
"idempotency_key": "ord-20931" }
{ "id": "pay_sample_41c2", "status": "pending" }
Webhook: payment.settledOrder updated
Lifecycle
Every status change arrives as an event.
Pending, sent, settled or returned: your system hears it once, in order.
- payment.createdAccount already validated
- payment.sentIn the 2:45 PM window file
- payment.settledOrder marked paid
- payment.returned · R01Retry scheduled by your rule
Account checks
Accounts validated before the first debit.
Online debits need account validation first. The API refuses a debit until it passes.
{ "error": "account_not_validated",
"next": "start_verification" }
Micro-entries sent · ACCTVERIFYWaiting for customer
Amounts confirmedDebit accepted
Safe retries
Send it twice, and it still runs once.
Idempotency keys stop a network retry from creating a second payment.
- POST · first attempttimeoutUnknown
- POST · same key200Same payment returned
Payments created1, not 2
Questions
Asked on most calls.
- Whose ACH origination does it use?
- Your bank's, or a licensed processor's. The API sits in front of it.
- Can our platform send payments for our customers?
- That can make you a third-party sender with extra obligations. We scope it carefully.
- Do you provide sandbox testing?
- Yes. Sample payments and returns run end to end before anything goes live.
- What does a build cost?
- Every build is custom, so it is scoped and quoted on the call.
ACH API integration
Show us the system that needs to pay.
Thirty minutes with the people who build it.
