ACH API

An ACH API is a programming interface through which a business or fintech sends and receives payments on the US Automated Clearing House (ACH) network without building and transmitting Nacha files by hand. Payroll providers, lenders, marketplaces, billers and neobanks use ACH APIs to pay out salaries and vendor invoices, collect subscriptions and loan repayments, and move money between a customer's accounts.

The API is a convenience layer, not a separate rail. Behind it, the provider (a bank, or a fintech working with a bank) turns API calls into Nacha-formatted batch files that an originating depository financial institution (ODFI) submits to an ACH operator, either the Federal Reserve's FedACH or The Clearing House's EPN. The receiving bank, the RDFI, posts the entry to its customer's account. All parties remain bound by the Nacha Operating Rules, whatever the interface looks like.

Sending ACH payments the old way is like filling in a long paper form in a strict layout, with every box exactly the right width, and dropping it at the bank before closing time. One wrong character and the whole stack comes back.

An ACH API is like a helpful clerk who takes simple instructions, such as "pay Jane $500 on Friday from our operating account", fills in the forms correctly, hands them over on time and calls back later to say whether Jane's bank accepted the money or sent it back.

1. The client registers a counterparty with a routing number (see ABA number) and account number, ideally after bank account verification.
2. It creates a payment order: amount, direction (credit or debit, the ACH push and ACH pull cases), effective date and a Standard Entry Class code such as PPD (consumer), CCD (business) or WEB (internet-authorised debit). The request carries an idempotency key so a retry cannot create a second payment.
3. The provider groups orders into batches and builds a Nacha file of fixed 94-character records.
4. The file goes to the ODFI before its submission deadline. Same Day ACH offers several daily windows for payments of up to $1 million each; other entries settle on a later banking day.
5. Status changes, returns and corrections come back as webhooks or status fields the client can query.

ACH is not instant and not final in the way a wire is. The receiving bank can return an entry with a reason code, for example R01 (insufficient funds), R02 (account closed), R03 (no account or unable to locate) or R10 (customer advises unauthorised). Most returns must be sent within two banking days, but a consumer can dispute an unauthorised debit for up to 60 calendar days after settlement. Banks also send notifications of change (codes beginning with C) when account details need updating.

A good ACH API surfaces each of these as a distinct event, so that the client can mark a returned payment, update stored details or retry. Nacha limits re-presentment: a debit returned for insufficient or uncollected funds may be reinitiated no more than twice, within 180 days of the original settlement date, which shapes any payment retry logic.

An easy interface does not lighten the rules. The ODFI is responsible for every entry it sends, so it, or the sponsor bank behind a fintech, performs know-your-customer checks on originators, sets exposure limits and audits third parties. Key Nacha requirements include:

• Account validation for WEB debits. Since 2021, originators must include account validation in their fraud screening the first time they debit an account through an online authorisation.
• Fraud monitoring. New rules require risk-based monitoring to catch entries induced by fraud, including business email compromise. Phase 1 took effect on 20 March 2026 for all ODFIs and for large originators and third parties (more than 6 million ACH originations in 2023); Phase 2 extends the duty to everyone else from 19 June 2026.
• Data security. Account numbers stored by larger originators and third parties must be rendered unreadable when stored electronically.

Providers usually layer transaction monitoring and sanctions checks on top, as part of their wider AML compliance.

ACH remains the cheapest way to move money between US bank accounts in volume, which is why direct deposit payroll and recurring bills run on it. Its trade-offs are batch timing and a return window during which money can come back. A FedNow API or other instant-payment interface settles in seconds, around the clock, but is credit-push only and final, while Fedwire suits large, urgent, final transfers at a higher fee. Many businesses connect to all three through one bank API or orchestration layer and pick the rail per payment.

• Nacha Operating Rules
• Nacha: Risk Management Topics (Fraud Monitoring Phase 1)