Cancel before the cut-off
A pending transfer can be cancelled with a single API call before its origination window closes. The dashboard shows the deadline visibly and prevents the cancel after submission, when only a reversal is allowed.
ACH payment, unified
Send and receive ACH payment through one integration.
topropay is the layer that puts ACH payment next to cards, wallets and account-to-account on the same API. Collect bank mandates from a hosted form, originate debits and credits inside Nacha's cut-off windows, and reconcile every transfer in one ledger — without standing up a separate banking integration to handle it.
ACH payment form
Routing number 021 000 021 Chase, NY
Account number •••• •••• 4218
Account type Checking Savings
Window Same-day Standard
Mandate captured · Nacha-aligned authorisation on file
The short version
ACH payment info, in four lines
Before the integration detail, the basics. The ACH rail is older than the modern card network and quietly carries trillions of dollars a year between US bank accounts. Here is what the term actually means and how it moves.
- ACH payment full form
- Automated Clearing House — the US bank-to-bank network operated under Nacha rules that moves funds in batches between accounts.
- Who runs it
- Nacha sets the rulebook; the Federal Reserve and The Clearing House operate the rails that actually settle the batches.
- What moves
- Direct Debits (ACH debits — you pull funds from a customer) and Direct Credits (ACH credits — you push funds to a recipient).
- Typical timing
- Standard ACH settles in 1–3 business days; Same-Day ACH lands on the same banking day inside Nacha's cut-off windows.
ACH payment at a glance
- 1 integration
- Send and receive ACH payment from the same API that runs your card flow.
- 0.1% typical fee
- ACH transfers cost a fraction of card interchange on equivalent volume.
- 1–3 business days
- Standard ACH settlement, with same-day ACH available where the originator supports it.
- 1× ledger
- One reconciliation export across ACH, cards, wallets and account-to-account.
Why teams choose us
The case for online ACH payment
Teams move to ACH for fees, for predictability, and for recurring billing that does not break every twelve months. Here is what changes once you can send ACH payment and pull-debit it from the same place your cards live.
How it plugs into orchestration- Cost
Fees that scale, not punish
ACH payment is priced by transfer, not by ticket size, so taking a $5,000 invoice over ACH costs roughly the same as a $50 one. On large or recurring invoices the fee gap versus card processing pays for the integration on its own.
- Recurrence
Built for recurring billing
Stored bank mandates let you charge customers on a schedule with no card-expiry churn. Subscriptions, rent ledgers and B2B retainers run quietly in the background.
- Reach
Every US bank, one rail
ACH reaches every domestic US bank account — checking and savings, personal and business — so you can pay or be paid without onboarding a separate bank relationship for each.
- Control
Cancel, adjust, reverse
Pending transfers can be cancelled, completed transfers can be corrected with an ACH payment adjustment, and disputes follow Nacha's clear timeline — all from the same dashboard the rest of your payments live in.
How it works
From bank details to settled funds
Every transfer follows the same four-step path. topropay handles the Nacha-side mechanics — file origination, cut-offs, return codes — so you work in transfers and statuses, not in batch files.
-
Collect bank details
The customer enters routing and account numbers in a hosted form, or signs a mandate for recurring debits. Numbers are vaulted; your servers never store raw bank data.
-
Originate the batch
topropay submits the ACH file through its originating bank inside Nacha's cut-off windows. Same-day or standard windows are selectable per transfer.
-
Settle and post
The receiving bank credits or debits the account. Webhooks notify you of accepted, returned and reversed transfers as their status changes.
-
Reconcile and report
Every ACH posting lands in the same normalised ledger as cards and wallets, so finance closes the period without merging a separate bank file.
Rail vs rail
ACH payment format vs cards and wires
ACH is one of three rails most US merchants reach for. The right choice depends on ticket size, urgency and whether the customer is a consumer or a business. The shape below summarises where each rail belongs.
| Property | ACH | Card | Wire |
|---|---|---|---|
| Typical fee | Flat per transfer (cents) | ~1.5–3.5% + cents | Fixed $$ per transfer |
| Settlement time | 1–3 business days · same-day option | Minutes to next day | Same day, intraday |
| Reversible | Yes, by R-code rules | Yes, via chargeback | No, once cleared |
| Best for | Recurring, B2B, payouts | Consumer checkout | Large one-off treasury |
| Geography | US bank accounts | Global card networks | Global SWIFT |
Most platforms end up using two of the three together: cards for consumer checkout, ACH for the recurring or invoiced side. Because both run through one topropay integration, you do not need to split the engineering work — you just choose the rail per transfer.
Where it fits
Where teams put online ACH payment to work
The same rail serves a SaaS subscription and a property manager collecting rent. A few of the most common patterns:
-
Subscriptions and SaaS
Charge monthly or annual plans by ACH where the customer prefers it, escaping card-expiry churn on long-tenure accounts.
-
Invoiced B2B sales
Settle five- and six-figure invoices over ACH for a flat per-transfer fee, instead of paying a percentage to a card network.
-
Marketplaces and payouts
Disburse seller earnings, creator payouts and refunds straight into US bank accounts on a predictable schedule.
-
Property and rent ledgers
Run ACH payment for rent as a recurring debit with a clear mandate, so move-in dates and lease cycles stop colliding with card declines.
-
Financial services
Move funds for lenders, neobanks and savings products in and out of customer accounts with audit-grade traceability.
-
Donations and dues
Recurring giving and membership dues benefit most from a low-fee rail: more of every contribution reaches the cause.
Capabilities
Features for sending and receiving ACH payment
Everything you need to capture a mandate, originate a transfer, manage returns and reconcile a settlement — without picking up a separate banking integration.
Read the API documentation- Unified API
- Send ACH payment and pull-debit it from the same SDK you use for cards, wallets and account-to-account.
- Hosted bank form
- PCI- and NACHA-aware hosted form captures routing/account details with inline validation and pre-fill.
- Mandate management
- Store authorisations, regenerate signed PDFs, and revoke a mandate without losing the audit trail.
- Same-Day ACH
- Originate inside the morning and afternoon windows for same-day credit, or fall back to standard.
- Returns and reversals
- R-code handling, automatic retry policy on R01/R09, and a clean cancellation path before submission.
- Reconciliation export
- Normalised ACH postings sit beside card settlements in one ledger you export to your ERP.
Operations
Cancel ACH payment, adjust returns, sleep through cut-offs
Once a transfer is in the network, the question is rarely "is it sent?" — it is "what happens when something changes?" The platform makes the operational edges of ACH boring on purpose.
Adjust a settled transfer
When an ACH payment adjustment is needed — wrong amount, duplicate, mis-credited account — the originating institution submits the correction under Nacha rules. The change is recorded against the original transfer so the ledger never drifts.
Returns with R-code clarity
Every return arrives as a webhook with its Nacha R-code mapped to a human-readable reason. A sensible retry policy fires automatically on the codes that warrant it, and stops cleanly on the ones that do not.
Industry relevance
ACH across sectors
Anywhere revenue is recurring, invoiced or paid out to a US bank account, ACH carries more of the load than cards. Teams across these sectors run their ACH payment through topropay.
The platform serves both mainstream and demanding, high-volume merchants, and it serves payment service providers reselling capacity to their own customers. What stays constant across every sector is the shape of the problem: collect the right ACH payment information, originate cleanly, handle returns gracefully, and reconcile in one place. Solve that once and a new product line or a new billing model becomes a configuration change, not a project.
Trust & compliance
Compliance your finance and risk teams can sign off
Moving money between bank accounts is a regulated activity. The platform is built so the heavy lifting sits with us, keeping your own scope small.
Nacha-aligned
Origination follows Nacha's Operating Rules — mandate capture, return-code handling and cut-off discipline are built in.
Bank-grade vaulting
Routing and account numbers are tokenised and stored in a hardened vault so they never sit inside your application.
Audit-ready logs
Every transfer carries an immutable trail — originator, mandate, status changes, returns and adjustments — exportable on demand.
Resilient operations
Redundant originating relationships keep ACH flowing through bank-side incidents and cut-off-day surges.
Mandates are captured to a Nacha-aligned standard, routing and account numbers are tokenised on capture, and every state change in a transfer's life — accepted, settled, returned, reversed or adjusted — sits in an audit log you can export. The result is an ACH operation that holds up to an internal audit or a counterparty's due diligence without a fire drill. ACH transfers sit alongside cards inside the same end-to-end payment processing process, underneath the unified payment provider layer.
Common questions
Questions about ACH payment
What ACH payment information is needed to set up a transfer?
Three things: the recipient's bank routing number (nine digits, identifying the bank), the recipient's account number, and whether the account is checking or savings. For a debit (pulling funds from a customer) you also need a signed authorisation — a mandate — capturing their consent. topropay's hosted ACH payment form collects all of this with inline validation, so you never have to design the capture flow yourself.
How do I send ACH payment online through topropay?
After you connect the unified API, you create a transfer object with the originator and recipient details and submit it. The platform handles file origination, cut-off windows and webhook status updates. You can send ACH payment online as a one-off, or schedule recurring debits against a stored mandate. The same call works for ACH credits (pushing funds out) and debits (pulling funds in).
How do I receive ACH payment from a US customer?
Two patterns: either share your ACH payment instructions (your account and routing number) so the customer pushes funds to you, or — far more common — generate a hosted collection page where the customer authorises a debit. The hosted page asks for the ACH payment info, captures the mandate, and triggers the debit on the day you choose. Either way, the incoming credit posts to your reconciliation ledger automatically.
Can I cancel ACH payment after I submit it?
Yes, while it is still pending. Before the origination cut-off, a single API call (or a click in the dashboard) cancels the transfer cleanly. After origination, the transfer has already entered the network; at that point the path is a reversal or adjustment under Nacha rules rather than a cancel. Same-day transfers leave a shorter window to cancel, so the dashboard surfaces the deadline visibly.
What is an ACH payment adjustment?
An ACH payment adjustment is a correction to a settled transfer — typically because of a wrong amount, a duplicate, or an incorrect account credit. The originating financial institution submits the adjustment under Nacha's rules, and the platform records the change against the original transfer so your ledger never drifts from the bank's view. Returns (an unpaid debit, an invalid account) are handled separately, with R-codes mapped to clear webhook events.
What does the ACH payment full form actually stand for?
ACH stands for Automated Clearing House. It is the US bank-to-bank network governed by Nacha and operated by the Federal Reserve and The Clearing House, used to batch credits (push payments) and debits (pull payments) between bank accounts. It is the rail behind direct deposit, recurring bill pay, vendor payouts and most modern subscription billing in the United States.
Can I use ACH payment for rent and other recurring obligations?
Yes — and it is one of the most common patterns on the platform. ACH payment for rent runs as a recurring debit against a mandate the tenant signs once. The lease cycle and the debit cycle stay aligned automatically; the property manager sees rent post on the same day each month without chasing a card that expired.
Is ACH cheaper than taking a card?
On almost any non-micropayment ticket, yes. Card interchange is a percentage plus cents per transaction, so a $2,000 invoice on cards typically costs many dollars in fees. The same invoice over ACH costs cents. The break-even depends on your blended rate and ticket size, but for recurring B2B, property and high-ticket sales, ACH usually wins by a wide margin.
How fast does an ACH payment settle?
Standard ACH settles in one to three business days. Same-Day ACH, originated inside Nacha's morning and afternoon cut-offs, settles on the same banking day. topropay picks the right window per transfer based on the value and cut-off you select, and surfaces the expected settlement date on every transfer object.
How are returns handled?
Each return carries a Nacha R-code (R01 for insufficient funds, R03 for no account, and so on). The platform maps every R-code to a webhook event and applies a sensible default retry policy on the codes that warrant one — so a temporary R01 retries automatically while an R03 stops and alerts. You override the policy per merchant or per mandate from the dashboard.
Talk to our payments engineers
Add ACH payment to your stack on one integration.
Book a discovery call. We map your current billing setup, where ACH belongs alongside cards, and scope a single-API rollout — mandates, originations, returns and reconciliation included. No second banking integration, no separate ledger.