ACH vs RTP vs FedNow: Choosing a Rail

The three rails side by side

	ACH	RTP	FedNow
Operator	Processed by the Federal Reserve and The Clearing House under Nacha Operating Rules	The Clearing House	The Federal Reserve Banks
Launched	1970s	2017	2023
Speed	Batches; same-day or later settlement	Seconds	Seconds
Hours	Business days, in processing windows	Around the clock, every day	Around the clock, every day
Direction	Credits (push) and debits (pull)	Credit push only, plus request-for-payment messages	Credit push only, plus request-for-payment messages
Per-payment limit	$1 million for Same Day ACH; Nacha has approved $10 million from September 17, 2027	$10 million network limit since February 2025	$10 million network limit since November 12, 2025
Finality	Entries can be returned under the rules	Final and irrevocable once sent	Final and irrevocable once sent
Message format	Nacha file format	ISO 20022	ISO 20022
Reach	Almost all U.S. banks and credit unions	Participating institutions only	Participating institutions only

ACH: cheap, flexible and reversible

ACH is the workhorse for payroll, bill pay, subscriptions and account top-ups. Its strengths are reach and the ability to pull money from an account with the account holder's authorization, which the instant rails cannot do.

The price of that flexibility is returns. A debit can come back after settlement for reasons such as insufficient funds, a closed account or a customer's claim that the debit was not authorized. Consumer claims of unauthorized debits can arrive well after settlement. The Nacha Operating Rules set return timeframes, authorization requirements and return-rate thresholds that originators are monitored against, and a fintech's partner bank will pass those obligations to the fintech.

RTP and FedNow: instant and final

RTP and FedNow both settle a credit transfer in seconds, at any hour, and the payment cannot be recalled by the sender's bank once it is sent. A "request for return" can be sent, but the receiver is not obliged to agree. That finality is what makes instant payouts possible, and it is also why fraud controls have to act before the payment, not after.

The two networks are separate. A bank can join one, both or neither, and a payment on one network cannot reach an account whose bank only participates in the other. Both networks let participants set limits lower than the network maximum, so the limit that applies to your product is the lowest one along the path.

Picking a rail by use case

Use case	Usual fit	Why
Recurring subscription or loan repayment	ACH debit	Needs a pull; not time-critical
Payroll	ACH credit, instant rails for early or on-demand pay	Reach and cost, with speed where it matters
Instant payout to a gig worker or seller	RTP or FedNow	Speed, around-the-clock availability
Adding money to a wallet	ACH debit with holds, or a card	Instant rails cannot pull, and a request-for-payment needs the payer to act
Large business-to-business payment	Wire, RTP or FedNow	Finality and higher limits
Refund to a customer	The rail the customer paid on, where possible	Keeps reconciliation simple and matches expectations

The mismatch that causes losses

The classic loss pattern is taking money in on a reversible rail and paying out by an irreversible one. A customer tops up by ACH debit, withdraws instantly by RTP, and the ACH debit is returned days later. Controls that address it:

Hold pulled funds until the return risk has passed, with shorter holds for established customers
Limit instant payouts for new accounts and grow the limit with history
Verify account ownership before the first debit
Score each transaction for risk before it is released
Show customers the difference between a pending and an available balance

Request for payment: the instant-rail answer to debits

Both instant networks support a request-for-payment message. A business sends a request, the payer's bank shows it to the payer, and the payer approves a credit transfer back. Nothing moves without the payer's action, which is why a request for payment is not a direct substitute for an ACH debit: it suits invoices and bills where the payer is present, not an automatic subscription charge. Check whether your bank, and the payer's bank, support sending and receiving requests before building a product around them.

How to add a rail, step by step

Check what your bank supports. Participation, send versus receive, limits, cut-off times and fees.
Map the rule obligations. Nacha rules for ACH; the network's operating rules for RTP or FedNow, which your bank will flow down in its agreement with you.
Update disclosures. Tell customers how long each option takes and whether it can be canceled. Consumer transfers bring Regulation E error-resolution duties.
Build exception handling. Returns, rejects, requests for return and payments to non-participating banks all need a path.
Reconcile daily across every rail, so your ledger matches the bank's.

Common questions

Is FedNow faster than RTP?

Both are designed to settle in seconds at any hour. For a given payment, the practical differences are whether both banks participate and what limits each bank sets.

Can a fintech connect to FedNow directly?

FedNow is available to eligible depository institutions. Most fintechs reach it through a partner bank or a provider that connects on a bank's behalf.

Is Same Day ACH instant?

No. Same Day ACH settles on the same business day within set processing windows, which is faster than standard ACH but not real time, and it is not available on weekends or holidays.

Can an instant payment be reversed for fraud?

Not by the sender's bank on its own. The sender can ask for the money back through a request for return, and the customer may have rights against its own institution, but the payment itself is final.

Cards and wires are covered in payment rails explained. The compliance obligations that come with each rail are on the compliance checklist.