FedNow vs RTP for payouts

Two rails, one idea

RTP (Real-Time Payments) is operated by The Clearing House, a private company owned by a group of large commercial banks, and has been live since 2017. FedNow is operated by the Federal Reserve and launched in 2023. Both move money bank-to-bank in seconds with immediate settlement finality.

Both are credit-push rails: the sender initiates and pushes funds, which is exactly the shape of a payout. Nobody pulls money from your account, and a recipient cannot be debited by mistake.

FedNow vs RTP side by side

Bank and network coverage

The difference that matters most for payouts is coverage. Neither network reaches every US bank account. Joining is a choice each bank makes, and it takes real integration work, so participation grew bank by bank rather than all at once. Some banks joined RTP years ago, some picked FedNow because their Federal Reserve relationship made it the easier path, some run both, and some, often smaller institutions, have joined neither yet. A bank can also receive on a rail without sending on it, which is the side that matters for payouts.

The result: whether a given recipient can be paid instantly depends on whether their bank participates in one network, the other, both, or neither, and that is not something you can know in advance across a batch of dozens of recipients.

Availability: always on, for both

On availability the two rails are identical, and identically different from everything that came before. Both settle in seconds, around the clock, every day of the year. There is no batch window, no cutoff time, and no banking-holiday pause. For a payout program that means a settlement run at midnight after a Saturday event clears the same way a Tuesday-morning run does. When a recipient’s bank supports the rail, funds typically arrive in about a minute.

Why a payout program wants both rails

A team payroll, a settlement night or a creator payout run is a batch of people with accounts at dozens of different banks. Route everything over one rail and every recipient outside that network’s coverage fails or falls back to slow rails. Supporting both RTP and FedNow roughly means covering each network’s strengths: RTP’s reach among larger banks plus FedNow’s spread through community banks and credit unions. The answer is rail-aware routing: for each recipient, pick the fastest rail their bank actually accepts, in real time. You can see how the decision plays out for different banks in the rail selector tool.

Payout: $500

RTP       unavailable
FedNow    available
ACH       available

Selected route
FedNow

• Bank supports RTP: route RTP.
• FedNow only: route FedNow.
• Neither, but they have a debit card: push to the card over Visa Direct.
• None of the above: ACH, on standard timelines.

Fallback routing when the bank is on neither

Some recipients will bank somewhere that has not joined RTP or FedNow. The payout still has to land, so the router falls back. The first fallback is usually push-to-card: if the recipient has an eligible debit card, funds move to it over Visa Direct, typically in about a minute. The last resort is ACH, which reaches essentially every US bank account but settles on standard ACH timelines rather than instantly; the tradeoffs are covered in ACH vs instant rails.

That decision has to be made per payment, at send time, against live network participation, which is why it belongs in infrastructure rather than in a spreadsheet. With a payout API that does automatic rail selection, the application asks for an outcome and the payout layer picks the rail, falling back gracefully when an instant rail is not available.

Application
    |
Payout router
  /   |   \
RTP FedNow ACH

Where DiscoFi fits

DiscoFi routes every payout over the fastest rail the recipient’s bank accepts across RTP, FedNow, Visa Direct and ACH, retries on decline, and reconciles the whole batch to one ledger. On instant rails, funds typically land in about a minute.* See Instant Pay disclosure The request behind all of that is one call, documented in the API reference.