FedNow is the U.S. Federal Reserve's instant payment infrastructure, giving American financial institutions a government-operated rail for settling transactions in real time, every hour of every day. Since its July 2023 launch, it has been quietly reshaping expectations around payment speed for banks, fintechs, merchants, and their customers.
How FedNow Works
FedNow operates as a credit-push system: the sender's financial institution initiates the payment, the Federal Reserve validates and settles it, and the recipient's institution credits the funds — all within seconds. Here is the step-by-step flow.
Sender initiates a payment
A customer or business instructs their participating bank or credit union to send a payment via FedNow. This can happen through a mobile app, API call, or business payment portal, depending on how the institution has implemented the service.
Sending institution submits the message
The sending bank formats the payment as an ISO 20022 message and submits it to the FedNow Service. ISO 20022 is a global messaging standard that carries richer data than older formats like ACH's NACHA files, enabling better remittance information and fraud screening.
FedNow validates and routes
The Federal Reserve's FedNow Service validates the message format, checks that the sending institution has sufficient funds in its Federal Reserve account (or intraday credit), and routes the payment to the receiving institution.
Instant settlement occurs
The Fed debits the sending institution's reserve account and credits the receiving institution's reserve account simultaneously. This is final, irrevocable settlement — unlike ACH, there is no return window for standard credit transfers.
Recipient institution credits the end user
The receiving bank or credit union credits the end customer's account and sends a confirmation back through the network. From the end user's perspective, the funds appear almost immediately.
Request for Payment (optional)
FedNow also supports a Request for Payment (RFP) flow, where a biller sends a structured payment request to a payer's institution. The payer can review and approve it, triggering the same instant credit-push flow above. This enables instant bill payment without requiring the biller to pull funds.
Why FedNow Matters
The U.S. has historically lagged behind markets like the UK, India, and the EU in instant payment adoption. FedNow represents a structural shift — a government-operated rail available to every federally regulated financial institution, not just large banks willing to join a private network.
The numbers tell the story. As of early 2024, more than 700 financial institutions had joined FedNow, with the Federal Reserve targeting broad coverage across U.S. banks and credit unions. The Federal Reserve's own research found that 65% of U.S. consumers experienced a situation where faster payments would have been valuable, including avoiding late fees or covering an urgent expense. On the business side, the Association for Financial Professionals reports that over 50% of finance professionals cite payment speed as a top priority when selecting payment methods for disbursements.
The broader U.S. instant payment market — covering both FedNow and the RTP network — processed over 1 billion transactions in 2023 for the first time, according to The Clearing House. FedNow's addition to the landscape gives smaller community banks and credit unions, which already hold Federal Reserve master accounts, a lower-friction path to offering real-time capabilities without joining a separate private consortium.
Finality matters
Unlike ACH, FedNow credit transfers are final upon settlement. There is no two-day return window. This eliminates a class of return-related disputes but means fraud prevention must happen before the payment is sent, not after.
FedNow vs. ACH
Both FedNow and ACH move money between U.S. bank accounts, but they are built for different jobs. The table below captures the most important distinctions for payment professionals.
| Feature | FedNow | ACH |
|---|---|---|
| Settlement speed | Seconds, 24/7/365 | 1–2 business days (Same-Day ACH: same day) |
| Operating hours | Always on | Business days only |
| Transaction finality | Irrevocable upon settlement | Returns possible for up to 2 days |
| Transaction limit | $500,000 default | $1,000,000 (Same-Day ACH) |
| Message format | ISO 20022 | NACHA format |
| Operator | U.S. Federal Reserve | NACHA (private) via Fed and EPN |
| Best use case | Urgent disbursements, bill pay, account funding | Payroll, recurring billing, high-volume batch |
| Cost per transaction | Higher than ACH | Lower (fractions of a cent to a few cents) |
| Pull payments supported | No (credit-push only) | Yes (ACH debits) |
ACH remains the backbone of high-volume, low-urgency payments. FedNow addresses the use cases where waiting a day or two creates real friction — think insurance claim payouts, earned wage access, or a small business needing to fund payroll on a Friday afternoon.
Types of FedNow Transactions
FedNow currently supports two primary transaction types, with the service expected to expand its feature set over time.
Credit Transfer is the core FedNow message type. The sender's institution pushes funds to the receiver's institution. This covers most disbursement and payment scenarios: payroll, vendor payments, consumer transfers, and refunds.
Request for Payment (RFP) allows a biller or payee to send a structured, data-rich request to a payer. The payer's institution presents the request, and upon approval, a credit transfer is triggered. RFP is positioned as the instant-payment equivalent of an invoice or bill, enabling real-time bill pay without ACH debit authorization.
Liquidity Management Transfer (LMT) is a specialized message type for financial institutions to move funds between their own accounts at the Federal Reserve and at Federal Home Loan Banks. This supports intraday liquidity management rather than end-customer payments.
Best Practices
For Merchants
Treat FedNow as a disbursement-first rail in the near term. Refunds, marketplace payouts, earned wage access programs, and insurance claim payments are the highest-value use cases today, given that credit-push is the primary supported flow. Work with your bank or payment service provider to confirm their FedNow participation status — not all institutions are live yet. Build your customer-facing UX to set expectations around irrevocability: once a FedNow payment is sent, it cannot be recalled unilaterally the way an ACH return can be initiated. Implement robust pre-send verification (account validation, fraud scoring) to compensate.
When evaluating FedNow for receivables, explore the Request for Payment capability. RFP can replace ACH debit authorizations for customers who prefer approving payments from their own bank interface rather than authorizing a pull from a merchant.
For Developers
Implement ISO 20022 message handling from the start — FedNow's richer data format is both a capability and a responsibility. Parse and store remittance data fields so downstream reconciliation systems can use them. Design your payment flows to handle the synchronous, near-real-time response pattern: unlike ACH batch processing, FedNow expects near-instant acknowledgment messages, so your integration must be able to handle responses within seconds. Build idempotency keys into your payment requests to guard against duplicate submissions during network retries. Monitor the Federal Reserve's FedNow Service participant directory programmatically if your platform needs to validate whether a recipient institution is FedNow-enabled before routing.
Common Mistakes
Assuming all banks participate. FedNow participation is voluntary, and adoption is still growing. As of early 2024, more than 700 institutions have joined, but there are roughly 10,000 federally insured institutions in the U.S. Always validate recipient bank participation before promising instant delivery to end users.
Treating FedNow like ACH for fraud response. Many teams apply ACH-era fraud workflows to FedNow — approving payments and relying on the return process to catch fraud. FedNow credit transfers are final. Fraud detection must occur before the payment is authorized, not after. Retrofitting ACH-style chargeback logic onto FedNow flows leads to unrecoverable losses.
Ignoring the Request for Payment flow. Teams building push-payment infrastructure often overlook RFP entirely. For billing and collections use cases, RFP can improve conversion versus ACH debit by giving consumers control and reducing authorization friction — especially relevant as debit-pull regulations tighten.
Underestimating infrastructure requirements. FedNow operates 24/7/365, which means your payment processing systems must too. Teams that build on-hours batch architectures and bolt on FedNow as an afterthought encounter gaps: payments arriving at 2 a.m. on a Sunday that no process is running to reconcile.
Conflating FedNow with faster-payments broadly. FedNow is one rail. A comprehensive instant payment strategy in the U.S. may involve FedNow, RTP, and enhanced ACH depending on counterparty institution coverage, transaction size, and use case. Designing around a single rail creates coverage gaps.
FedNow and Tagada
Orchestrate FedNow alongside your other payment rails
Tagada's payment orchestration layer lets you route disbursements intelligently across FedNow, RTP, and ACH based on real-time rules: recipient bank participation, transaction urgency, cost thresholds, and fallback logic. When a recipient institution isn't FedNow-enabled, Tagada can automatically fall back to Same-Day ACH without any code changes on your side. For platforms running marketplace payouts, earned wage access, or insurance disbursements, this multi-rail orchestration means you can promise fast payments to end users without being constrained by any single network's coverage gaps.