FedNow is the Federal Reserve's instant payments network. It launched on 20 July 2023 and lets banks settle payments between each other in under 15 seconds, around the clock, every day of the year. The settlement limit started at $500,000 and was raised to $1 million in February 2024. By 2026 more than a thousand US banks are live on the network.
What FedNow isn't is a consumer brand. You don't open a FedNow account or download a FedNow app. The network sits behind the bank — if your bank's joined, the instant transfer you initiate in your banking app might travel over FedNow, over RTP, or over neither. The pipe is the Fed's. The user experience belongs to whoever built it on top.
Why the Fed built it#
For years, the US lagged behind other developed economies on real-time payments. The UK had Faster Payments since 2008. The EU built SEPA Instant. India's UPI handles billions of transactions a month. The US had ACH, which clears in one to two business days, and Fedwire, which is real-time but designed for large-value bank-to-bank transfers — not the use case that needed solving.
The Clearing House, a consortium of large US banks, launched the RTP network in 2017 to fill the gap. RTP works, but ownership concentrated in the largest banks meant smaller institutions felt squeezed. The Federal Reserve announced FedNow in 2019 as a public alternative — owned by the Fed, available to any depository institution, designed to coexist with RTP rather than replace it.
That's the political shape of the network. The technical shape is that FedNow is a credit-push, ISO 20022-formatted, request-response system that settles funds in central bank money in seconds. Each transaction is final on settlement. There's no batching, no overnight cycle, no "pending" state that resolves later in the day.
How a FedNow payment moves#
A FedNow transaction starts at the originating bank. A customer or business sends a payment instruction through their bank's interface — a banking app, an online portal, an API call from an enterprise treasury system. The bank validates the instruction, debits the sender's account, and sends a message to FedNow.
FedNow checks the message format, verifies the receiving bank is reachable, and forwards the message. The receiving bank validates, credits the recipient's account, and sends back an acceptance message. FedNow then settles the funds between the two banks' Federal Reserve master accounts. The whole sequence takes under 15 seconds from initiation to settlement. If anything fails, the sender's bank gets a rejection message and reverses the debit.
Settlement is in central bank money — the same money commercial banks hold as reserves at the Fed. That's what makes the payment final and irrevocable. No three-day clearing window, no chargeback right, no return file the next morning. Once it's settled, it's settled.
Building a payment flow that takes ACH, FedNow, or card alongside phone payments? Book a 15-minute demo — we'll show you the architecture options.
FedNow vs RTP: same idea, different ownership#
FedNow and RTP do roughly the same job. Both are real-time, 24/7/365, ISO 20022, credit-push networks settling in central bank money. The differences are mostly structural rather than functional.
RTP, launched in 2017, is run by The Clearing House — a private consortium owned by the largest US banks. It reached every bank in the US in 2024, in the sense that any bank can join. FedNow, launched in 2023, is run by the Federal Reserve and reaches more banks more easily because smaller institutions trust the Fed as a counterparty more than they trust the largest banks.
From a sender's perspective, you usually don't know or care which network your bank routes your payment over. The recipient gets the money in seconds either way. Behind the scenes, the bank's payment routing engine picks the network based on cost, reliability, and reach. Some banks are on both. Some are on only one. Over time the expectation is that interoperability between the two will improve, but for now they run in parallel.
The settlement limit on FedNow is currently $1 million per transaction. RTP raised its limit to $10 million in February 2025. For the use cases most US businesses care about — payroll, supplier invoices, B2B settlement — both limits are well above what a typical transaction needs.
What FedNow is good for#
Payroll is the clearest use case. ACH payroll cycles run a day or two before payday because of clearing time. FedNow lets a business run payroll the morning of payday, and employees see the money in their accounts the same morning. For hourly workers, contractors, and gig workers, that's a real cash-flow improvement.
B2B invoice settlement is the second. A supplier sends an invoice, the buyer pays it on the same day, and the funds are confirmed in the supplier's account before the buyer hangs up the phone. That eliminates the float that traditional check or ACH payments create, and it removes the awkward "the payment's gone but we can't see it yet" period that breaks small-business cash management.
Account-to-account transfers — moving money between accounts at different banks, paying back a friend, sending an emergency family transfer — work over FedNow when both banks are on the network. This is where FedNow overlaps with what Zelle has been doing for years using ACH rails. The user experience is similar; the underlying settlement is faster and final.
Treasury operations and just-in-time cash management round out the corporate side. A finance team can pull cash from one bank, move it to another, settle a wire-equivalent payment, and have it all reconciled within minutes instead of overnight.
What FedNow isn't replacing#
FedNow isn't a card network replacement. You can't tap a FedNow card at a point-of-sale terminal — the network doesn't issue cards. To accept a FedNow payment at checkout, a merchant needs a front-end service that issues a payment request to the customer's bank app, the customer approves, and the funds settle. That front-end layer exists in pilot form (request for payment, or RfP) but isn't widely deployed at retail point-of-sale yet.
FedNow isn't replacing ACH either, at least not soon. ACH handles roughly $80 trillion in annual volume across the US — payroll, bill payment, direct deposit, B2B invoicing. The economics of ACH (fees typically $0.25 to $1.50 per transaction) are hard to beat for batch payments where speed doesn't matter. FedNow's pricing structure positions it for the speed-matters cases, not the high-volume background plumbing.
And FedNow doesn't change anything about cardholder data protection. If your business takes card payments by phone, online, or in person, PCI DSS still applies. FedNow is a different rail with different rules — for ACH transactions, the equivalent regime is NACHA Operating Rules.
How merchants can think about FedNow#
For most US merchants in 2026, FedNow shows up indirectly. Your bank's treasury services team probably mentions it when discussing supplier payment options. Your accounts-receivable team might use it for invoice settlements where the customer's on a participating bank. Your payroll provider might route same-day payroll over it. The retail use case — accepting a FedNow payment at checkout — is still mostly hypothetical for non-pilot merchants.
The interesting question is how front-end services will mature. Request for Payment over FedNow lets a merchant push a payment request to a customer's bank, the customer authorizes it inside their bank app, and the funds settle instantly. That's a credible card-alternative model for high-value, low-frequency transactions where the 1.5-3% card interchange genuinely hurts and the customer is willing to authorize a payment from their bank account rather than tap a card. Verticals to watch: B2B sales, real-estate transactions, larger insurance settlements, healthcare.
For card-not-present and card-present retail, FedNow doesn't change the model. Cards still win on convenience, chargeback protection, and existing customer behavior.
Where Paytia fits with FedNow-style payments#
Paytia's role on a phone call is to capture the sensitive payment data from a customer without that data entering the agent's headset, the call recording, or the contact center systems. Card numbers are the obvious case. The same principle — channel separation and DTMF masking — applies to any sensitive identifier the customer needs to provide during a call, including ACH routing and account numbers.
If a merchant wants to take a FedNow payment over the phone — for example, an invoice settlement where the customer authorizes a Request for Payment from their bank — the same capture pattern works. The customer enters their bank-app authorization code or one-time passcode on the phone keypad, the digits are intercepted before they reach the agent, and the payment flow completes inside the bank's environment rather than the merchant's contact center.
FedNow doesn't change Paytia's architecture. It expands the set of payment types the same architecture can carry.
Related reading#
- ACH Payments for B2B: A Practical Guide for US Businesses
- Zelle and Real-Time Payments for US Merchants
- What Is Tokenization? A Plain-English Guide
- Tokenization vs Encryption: What's the Difference?
Building a payment flow that takes ACH, FedNow, or card alongside phone payments? Book a 15-minute demo — we'll show you the architecture options.
