Corpay

Real-Time Payments (RTP) for Business: RTP vs. FedNow (2026)

Category:Payments Automation, AP Automation
Updated:2026-07-09
Author:David Luther

A real-time payment is an irrevocable credit push that settles in seconds, any hour of any day, between two banks on the same instant network. The money moves and clears at once, and once it's gone, it's gone.

If you run accounts payable, the part that usually surprises people is that the United States has two of these networks, not one. The RTP network, run by The Clearing House, launched in 2017. The FedNow Service, run by the Federal Reserve, went live in 2023. They don't talk to each other, they have different transaction caps, and whether you can reach a given supplier depends on which one that supplier's bank joined.

The volume is real and growing fast. The RTP network alone moved 343 million payments worth $246 billion in 2024, a 94% jump in payment value over the prior year, according to The Clearing House's January 2025 report on RTP network growth. So this isn't a niche experiment anymore. It's a live rail your vendors may already be asking about.

This is the AP manager's guide to what these rails are, how RTP and FedNow differ, and the one question that actually matters at your desk. When does an instant payment earn its higher cost over a plain ACH transfer? Real-time payments sit inside the wider set of electronic payment methods for business, and the honest answer is that they're a targeted tool, not the new default.

Key Takeaways

  • A real-time payment is a credit push that settles in seconds, 24/7/365, and is irrevocable once sent. It is not the same thing as "instant" or "faster" used loosely, and it is not Zelle.

  • The U.S. runs two separate, non-interoperable instant networks: the RTP network from The Clearing House and the FedNow Service from the Federal Reserve. They have different operators, caps, and reach.

  • The two networks carry different transaction caps and reach different banks, so whether you can pay a given supplier instantly depends on the receiver's bank. A majority of enabling institutions now connect to both.

  • Instant rails cost more per payment than ACH, so the decision rule is narrow. Use them for time-sensitive, sub-wire-threshold pushes where the ACH window won't make it or a wire's cost and friction are the problem.

  • Because an instant payment is final, a mis-keyed or fraud-induced push can't be clawed back. Verify the account before you send, especially given that wire and push-payment fraud remain the top targets for scammers.

What are real-time payments, and how do they work?

Real-time payments are bank-to-bank transfers that clear and settle in seconds, run continuously with no cutoff times, and can't be reversed once they're sent. The sending bank pushes funds to the receiving bank, the receiver's account is credited within moments, and both sides get confirmation right away.

Three features define the category, and each one matters for how you'd use it:

  1. It's a credit push. You initiate the payment and send money out, rather than authorizing someone to pull from your account the way a direct debit works.

  2. Settlement is immediate and final. There's no float, no pending window, and no next-business-day posting.

  3. The rails run 24/7/365, weekends and holidays included, so a payment sent at 9 p.m. on a Sunday lands the same as one sent at 10 a.m. on a Tuesday.

There's also a two-way messaging layer worth knowing about. Both U.S. instant networks support request for payment, or RfP, which lets a biller send a structured request that the payer can review and approve with a single action. RfP flips the initiation without changing the finality, since the payer still pushes the credit while the biller kicks off the conversation. For AP, that's mostly a receivables-side feature today, though it shapes how supplier billing may reach you over time.

The rich data that travels with each payment is the quiet advantage. Instant rails use the ISO 20022 message format, which carries far more remittance detail than a legacy ACH addendum ever could. That means invoice numbers, adjustment codes, and reference data can ride along with the money, which is exactly what your team needs for clean payment reconciliation instead of chasing a bank memo line that got truncated to a reference number.

What makes a payment "real-time" versus "instant" or "faster"?

"Real-time," "instant," and "faster" get used interchangeably in marketing copy, but they describe different things, and the distinction changes what a payment can actually do. Real-time and instant generally mean the same category, the credit-push rails like RTP and FedNow that settle in seconds and can't be reversed. "Faster payments" is the loose umbrella, and it often gets stretched to cover Same Day ACH, which is quicker than standard ACH but works nothing like an instant rail.

The mechanism is where they part ways. Same Day ACH still moves in batches through defined processing windows, so it's faster-but-scheduled, not real-time; it settles in hours, not seconds, and only on business days. A wire transfer, by contrast, is same-day and effectively final. It runs only during banking hours, costs a great deal more, and involves manual handling on both ends. An instant payment is the only one of the three that combines seconds-level settlement with round-the-clock availability. When a vendor says they "take instant payments," it's worth confirming whether they mean a true instant rail or just same-day movement, because the cutoff times and the finality are completely different.

Is Zelle a real-time payment, and how is it different?

Zelle is not a payment rail, and it is not RTP, though the two get conflated constantly. Zelle is a consumer person-to-person service that sits on top of the banking network; some Zelle transactions actually settle over the RTP network behind the scenes, but Zelle itself is the front-end app-and-directory layer, not the rail underneath.

The practical differences matter for a business. Zelle is built for individuals sending money to individuals, with low transaction limits set by each bank and little of the structured remittance data that B2B payments require. RTP and FedNow are the underlying instant rails that banks and businesses use directly, with much higher caps and the ISO 20022 data layer that carries invoice detail. If someone asks whether your company can "just use Zelle" to pay a supplier, the answer is usually no. You'd reach for the instant rail your bank offers for business payments, which is RTP, FedNow, or both, depending on the institution.

How are RTP and FedNow different?

RTP and FedNow are both instant, credit-push, 24/7 networks, but they're run by different operators, launched years apart, and carry different transaction limits and reach. RTP is a private-sector network operated by The Clearing House, which is owned by a group of large banks; FedNow is operated by the Federal Reserve as public payment infrastructure open to any U.S. depository institution.

The two were built to do the same job, and from a payer's seat they behave almost identically. Two differences matter to you, the ceiling on a single payment and which banks you can actually reach. Here's the side-by-side.

Attribute

RTP network

FedNow Service

Operator

The Clearing House (private, bank-owned)

Federal Reserve (central bank)

Launched

2017

2023

Settlement

Seconds, final and irrevocable

Seconds, final and irrevocable

Availability

24/7/365

24/7/365

Transaction cap

Up to $10 million

Rising from $500,000 to $1 million

Direction

Credit push; supports request for payment

Credit push; supports request for payment

Message standard

ISO 20022

ISO 20022

Reach

Broad among large banks and their customers

1,400+ institutions, heavily community banks and credit unions

Sources: The Clearing House and PYMNTS (2025); Federal Reserve Financial Services (2025).

The gap in transaction caps is the first thing to note, and the figures above come from reporting by PYMNTS and The Clearing House in 2025. RTP's ceiling sits far higher than FedNow's, though FedNow's is climbing. For most AP payments that ceiling never binds, but if you're pushing a large settlement, the network you're on determines whether an instant rail is even an option.

Which banks support RTP and FedNow?

Whether you can send an instant payment to a specific supplier depends entirely on whether that supplier's bank participates in the network you're sending from. This is the single most important operational fact about instant payments, and it's the one most quick summaries gloss over. Reach is not universal.

FedNow adoption has climbed quickly. More than 1,400 financial institutions participate in the FedNow Service as of mid-2025, up from roughly 900 at its one-year anniversary, and about 95% are community banks and credit unions, according to the Federal Reserve Financial Services 2025 update on FedNow's growth. That community-bank tilt is deliberate; FedNow gives smaller institutions a way to offer instant payments without joining the bank consortium behind RTP. The RTP network, for its part, reaches a large share of U.S. demand-deposit accounts through its coverage of the biggest banks.

For an AP team, the takeaway is practical. Before you promise a vendor an instant payment, you or your bank has to confirm the receiving institution can accept one, and on which network. A payments platform that maintains this reachability lookup across both rails saves you from finding out at send time that the payment can't go through.

Why do many institutions run both RTP and FedNow?

Most banks that offer instant payments connect to both networks because doing so maximizes the number of counterparties they can reach and adds resilience if one network has an issue. Running a single rail leaves gaps; running both closes most of them.

The numbers bear this out. 58% of U.S. financial institutions that enable instant payments do so through both the RTP network and the FedNow Service, per PYMNTS and The Clearing House research from 2025. From your side of the transaction, that dual-rail reality is good news and a small complication at once. It's good news because more of your payees become reachable. It's a complication because "send this instantly" now means "route this over whichever network can reach this particular receiver," which is a decision better made by software than by a person checking two directories by hand.

Protect cash flow with modern AP

Modernize AP to cut costs, speed approvals, and mitigate payment risk — gaining the real-time visibility to protect cash flow and scale with confidence.

Download the whitepaper
protect-cashflow-with-ap.jpg

How do real-time payments compare to ACH and wire transfers?

Real-time payments settle faster than ACH and cost far less than a wire, but they're capped, irrevocable, and priced above ACH per transaction, which makes them a targeted tool rather than a wholesale replacement for either. The right way to think about it is a four-rail menu, where each payment gets matched to the rail that fits its urgency, size, and cost tolerance.

I'll route the deep mechanics elsewhere so this stays a comparison. If you want the full walk-through of how a direct debit and credit-push work, the guide to ACH payments covers it, and the breakdown of what wire transfers actually cost covers the fee side. Here's how the four rails line up on the dimensions an AP team weighs.

Dimension

RTP / FedNow

Same Day ACH

Standard ACH

Wire

Settlement speed

Seconds

Same business day

1–3 business days

Same business day

Cost per payment

Low, above ACH

Low

Lowest (often under $1)

Highest of the four

Finality

Irrevocable

Reversible within rules

Reversible within rules

Effectively final

Transaction cap

Network caps apply (see above)

Per-transaction limits apply

High

Very high

Operating hours

24/7/365

Business days, windowed

Business days, windowed

Banking hours

Typical B2B use

Urgent, time-sensitive push

Faster routine payroll, bills

Bulk scheduled vendor spend

Large or high-trust one-offs

Instant rails combine seconds-level settlement with round-the-clock availability; ACH remains the default for scheduled volume on cost.

The scale of ACH is worth keeping in perspective, because it explains why instant rails are a supplement and not a takeover. The ACH Network processed 35.2 billion payments worth $93 trillion in 2025, including 1.4 billion Same Day ACH payments worth $3.9 trillion, according to Nacha's 2025 ACH Network volume report. That's the workhorse handling the bulk of business payments, and its per-transaction economics are hard to beat for anything that can wait a day or two.

When is an instant rail worth more than ACH?

Reach for an instant rail when a payment is time-sensitive, falls below the amount where you'd normally wire, and either can't make the ACH window or would cost too much and cause too much friction as a wire. That's the whole rule, and it's narrower than "faster is better." Put concretely, an instant push earns its fee when all three of these hold:

  1. The payment is genuinely time-sensitive, meaning a delay carries a real cost rather than mild inconvenience.

  2. It sits below the dollar amount where you'd otherwise send a wire.

  3. Standard or same-day ACH can't get there in time, or a wire would cost and complicate more than the moment is worth.

Work it from the payment, not the technology. Most of your scheduled vendor spend, the recurring invoices with net terms and no urgency, should stay on standard ACH because it's the cheapest rail and a day or two of settlement time changes nothing. When something needs to move today, the next question is size. Below the wire threshold, an instant payment usually beats both alternatives. It lands in seconds, costs a fraction of a wire, and doesn't wait for a batch window the way Same Day ACH does. Above that threshold, or when the receiver can't take an instant payment, a wire is still the tool.

There's a real cost trade to respect here. An instant payment costs more per transaction than ACH, so pushing routine spend onto it just burns money for speed nobody needed. This is exactly the kind of call that ties into your broader business payment terms strategy. If a supplier offers an early-pay discount that clears the cost of an instant push, the math can favor paying now; if not, the scheduled ACH run is fine. And when the urgency is genuine but the receiver isn't RTP- or FedNow-reachable, a same-day ACH credit is often the practical fallback.

What does payment finality mean for fraud and errors?

Finality means an instant payment can't be recalled once it's sent, so a payment made to the wrong account, or induced by a fraudster, is gone with no clawback window. This is the flip side of speed, and it's the single biggest control consideration for putting instant rails into AP.

The exposure is not hypothetical. 79% of organizations were victims of attempted or actual payments fraud in 2024, with business email compromise cited as the top fraud avenue by 63% of respondents, according to the Association for Financial Professionals' 2025 Payments Fraud and Control Survey Report. BEC is precisely the attack that finality punishes. A spoofed email changes a supplier's bank details, the payment gets pushed, and by the time anyone notices, the funds have cleared. The same AFP research found wire transfers were the payment method most frequently targeted by these scammers in 2024, and push-based instant payments share the same irrevocable character that makes them attractive to fraudsters.

The control is verification before the push, not reversal after it. That means validating the supplier's bank account through a channel you trust, not the one in the incoming email, and applying the same discipline you'd use on a wire. Many of the account-validation and callback habits that finance teams built for preventing ACH credit fraud carry straight over to instant rails, and they matter more here because there's no recovery path once the money moves.

What are the best B2B use cases for real-time payments?

The best B2B use cases for real-time payments are the ones where timing has real economic value. Think of a payment that frees a held shipment, meets a hard deadline, or settles an obligation that can't wait for the next ACH batch. Outside those moments, ACH usually wins on cost.

A few patterns come up again and again in accounts payable:

  • Release-of-goods payments, where a supplier won't ship until funds are confirmed and an instant push turns a two-day wait into a two-minute one.

  • Urgent or off-cycle vendor settlements that miss the scheduled ACH run and would otherwise force a wire.

  • Just-in-time supplier payments in tight supply chains, where paying at the moment of delivery keeps inventory moving without prefunding.

  • Payouts to contractors and gig workers who value getting paid the day the work is done, especially over weekends when ACH sits idle.

  • Refunds and rebates to customers or partners, where speed is a service differentiator and the amounts sit comfortably under the caps.

The thread connecting these is that the timing itself is worth paying for. A finance team I'd expect to get value from instant rails isn't the one trying to move all its spend faster; it's the one that keeps hitting a handful of payments each month where a missed window costs more than the incremental fee. Those are the payments to route instantly. The rest belong on the rail that costs the least.

Where do instant payments fit in accounts payable?

Instant payments fit into AP as a fast lane for the small share of payments where speed carries real value, sitting alongside your existing rails rather than replacing any of them. The goal isn't to move everything to instant; it's to route each payment to the rail that fits.

In practice that means your default disbursement run still goes out on ACH, your rebate-eligible spend goes on cards, and the urgent, time-boxed exceptions peel off to an instant rail. The operational challenge is doing that routing reliably at volume without a person deciding rail-by-rail, which is where disbursement orchestration earns its keep. Getting suppliers set up to receive their preferred method is its own project, and the mechanics of supplier payment automation determine how smoothly enrollment and rail selection actually run. Suppliers, for their part, tend to care less about which rail you use and more about getting paid predictably with remittance data they can post, which is the core of how electronic payment solutions meet supplier needs.

Can real-time payments work cross-border?

Domestic instant rails like RTP and FedNow don't themselves cross borders; both are U.S.-only networks, so a real-time payment to an overseas supplier requires a different set of rails and arrangements. There's active work on linking national instant systems, but you shouldn't assume an instant domestic rail reaches an international payee today.

For now, paying a foreign supplier quickly means using a cross-border service designed for it, with its own settlement mechanics, currency handling, and timing that differ from a domestic instant push. How those payments get routed, priced, and delivered is a separate discipline covered in the guide to cross-border payments and their challenges. On the receivables side, if you're the one trying to collect faster, request for payment over a domestic instant rail can shorten the cycle for U.S. customers, which fits into the broader question of how to support accounts receivable with electronic payments. The short version is that instant is a domestic story for now, and cross-border speed is a different toolset.

How Corpay helps you route every payment to the right rail

Deciding which payment goes on which rail is the easy part on paper and the hard part in practice, because doing it reliably across hundreds of payments a week means maintaining reachability data, enrolling suppliers, and keeping reconciliation clean, all while your team is doing its actual job. That's the gap Corpay fills.

Corpay is a disbursement-orchestration platform that routes each payment to the right method, whether that's ACH, virtual card, check, wire, or a near-real-time rail, from a single workflow connected to your ERP through 180+ integrations. Instead of running batch files by hand or checking two instant-network directories to see who's reachable, your team approves payments and the platform sends each one on the rail that fits its urgency, size, and the receiver's capability. Because Corpay complements your ERP rather than replacing it, payment status and rich remittance data flow back into the systems you already run, so reconciliation stays a single clean round-trip.

What sets this apart from platform-only tools is the managed-service layer underneath it. Corpay enrolls your suppliers onto their preferred payment methods, handles the exceptions and follow-up when a payment fails or a vendor's details change, and takes reconciliation off your team's plate, the messy middle that software alone leaves for you to sort out. That combination of broad rail coverage and a human service layer is what lets an AP function add instant payments as a targeted tool without hiring a payments specialist to run it. To see how the routing and the managed service fit your stack, explore Corpay's payments automation platform or the broader AP automation suite.

Frequently Asked Questions

What are real-time payments in simple terms?

Real-time payments are bank-to-bank transfers that settle in seconds, run 24 hours a day every day of the year, and can't be reversed once sent. The sender pushes funds to the receiver's account, and both parties get confirmation almost immediately. In the U.S., they run over two networks, the RTP network and the FedNow Service.

What is the difference between RTP and FedNow?

Both are instant, 24/7, credit-push networks, but RTP is run by The Clearing House, a private bank-owned company, and launched in 2017, while FedNow is run by the Federal Reserve and launched in 2023. RTP carries a much higher per-transaction cap than FedNow, though FedNow's ceiling is climbing. They aren't interoperable, so reach depends on which network a receiver's bank joined.

What is RTP vs. ACH?

RTP settles in seconds and is irrevocable and available around the clock, while ACH moves in batches and settles in one to three business days, or same day for Same Day ACH, only on business days. ACH costs less per transaction and handles the bulk of scheduled B2B payments. RTP is the better fit for urgent, time-sensitive payments that can't wait for a batch window.

Is Zelle considered a real-time payment?

Not exactly. Zelle is a consumer person-to-person service, not a payment rail; some Zelle transactions settle over the RTP network behind the scenes, but Zelle itself is the app-and-directory layer, not the instant rail. Businesses paying suppliers use RTP or FedNow directly rather than Zelle, which is built for individuals and carries low limits.

Which banks support real-time payments?

Reach depends on the specific institution. More than 1,400 banks and credit unions participate in FedNow as of mid-2025, most of them community institutions, and the RTP network covers a large share of accounts through the biggest banks. Before sending, you or your provider should confirm the receiver's bank can accept an instant payment and on which network.

How much does a real-time payment cost compared to ACH or a wire?

An instant payment costs more per transaction than ACH, which often runs under a dollar, but far less than a wire, which typically costs $25 to $50 for domestic transfers. The economics favor instant rails for urgent payments below the wire threshold, and favor ACH for routine scheduled spend where a day or two of settlement time doesn't matter.

Are real-time payments reversible?

No. A real-time payment is final and irrevocable the moment it settles, with no clawback window. That makes account verification before you send far more important than it is on rails that allow returns, since a payment sent to a fraudulent or wrong account generally can't be recovered.

Can businesses send real-time payments internationally?

Not over RTP or FedNow, which are U.S.-only networks. Paying an overseas supplier quickly requires a dedicated cross-border service with its own settlement and currency handling. Efforts to link national instant-payment systems are underway, but instant domestic rails don't currently reach international payees on their own.

Headshot.JPG

David Luther

Product Marketing Program Manager
David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.
Payments Automation
AP Automation

Smarter payments. Stronger growth. Keep business moving.

Corpay powers payments for 800,000+ businesses worldwide. Let’s build what’s next for yours.