ACH Payments API
Move money across US bank accounts via ACH with same-day settlement, batch and real-time submission, and full webhook-driven reconciliation — through direct banking partnerships, not reseller chains.
ACH remains the dominant rail for high-volume, lower-cost money movement inside the United States — payroll, vendor disbursement, account-to-account funding, and recurring debits. Inyo's ACH API supports Same-Day ACH, standard next-day settlement, and balance verification, with the operational primitives (batches, return codes, NOC handling) you need to run ACH at scale.
For businesses that combine ACH with card processing, the same orchestration layer that picks the right card rail can route a payment to ACH instead — for example, downgrading a high-value card pay-in to ACH on soft decline, or splitting a payout flow between card and bank rails based on recipient eligibility.
Same-Day ACH and standard settlement
Submit credits and debits for Same-Day ACH cutoff windows or standard next-day settlement. Each submission carries a deterministic trace ID for reconciliation, and webhooks fire on submission, settlement, and any return event so your downstream systems stay in sync.
Real-time webhooks and reconciliation
Every status change on every transaction fires a webhook. Settlement files break down fees, returns, and notifications of change (NOCs) at the line level. The same transaction identifier follows the payment from submission through to settlement — see the payment reconciliation guide for how this works in practice.
Batch and per-transaction submission
For high-volume disbursement flows, batch submission is the most efficient and least costly path. For ad-hoc transactions, single-call API submission works the same way. Either path produces consistent transaction IDs and webhook semantics.
Return codes and NOC handling
ACH returns and Notifications of Change are surfaced as structured webhook events with the NACHA return code, original transaction reference, and recommended remediation. Common patterns — R01 (insufficient funds), R03 (no account), R10 (unauthorized) — are normalized into status transitions you can act on programmatically.
Frequently Asked Questions
Does Inyo support Same-Day ACH?
Yes. Inyo supports both Same-Day ACH (within NACHA cutoff windows) and standard next-day settlement, for both credits and debits.
How are ACH returns handled?
Returns and Notifications of Change are delivered as structured webhook events with the NACHA return code, original transaction reference, and a normalized status. Common return codes are mapped to actionable status transitions.
Can I combine ACH with card processing in the same flow?
Yes. Inyo's payment orchestration layer routes across card, ACH, and wire rails — including using ACH as a soft-decline fallback for higher-value card transactions where it makes sense.
Is ACH available outside the United States?
ACH is a US-domestic rail. For cross-border payouts, see Inyo's global payouts product, which uses local bank rails and card networks in 170+ countries.
How are batches submitted?
Via the same API used for single transactions, but tagged with a batch identifier and submitted as a single payload. Webhooks fire per-transaction within the batch as statuses change.
Send and receive ACH through one API
Talk to the Inyo team about Same-Day ACH, batch disbursements, and reconciliation at volume.
Talk to Sales