The Federal Reserve’s FedNow service launched in July 2023 as a public alternative to The Clearing House’s RTP network, yet by 2026 adoption patterns reveal a fragmented landscape: smaller regional banks and credit unions dominate FedNow usage, while larger institutions maintain dual participation or favour RTP for their highest-value flows. The choice between them isn’t technical — it’s strategic, tied to settlement costs, existing correspondent banking relationships, and whether a bank’s real-time payment volume justifies the infrastructure investment each platform demands.
Why Two Real-Time Networks Exist at All
The United States arrived late to real-time payments. By 2023, instant payment systems operated across the EU (SEPA Instant), the UK (Faster Payments Service), Singapore, and India. The Federal Reserve entered the market with FedNow partly to democratise real-time access — any depository institution with a Fed master account could theoretically plug in. The Clearing House’s RTP, operational since 2017, had already built a subscriber base among larger banks but faced criticism for exclusivity and cost barriers that locked out smaller players.
That competitive origin matters. Today, practitioners at mid-sized banks and regional credit unions face a genuine question: which network reduces friction for the payment flows that matter to their business? The answer isn’t “both equally.” It’s messier, more political, and far more revealing about how American banking infrastructure actually works beneath regulatory announcements.
FedNow: Accessibility vs. Scale
FedNow’s design prioritises reach. Any institution with a Federal Reserve account — roughly 10,000 across the country — can technically participate. No separate clearing membership. No membership fees measured in millions. Settlement happens directly at the Fed, cutting out intermediaries.
That architecture attracted credit unions, community banks under $5 billion in assets, and regional banks in markets where RTP membership fees weren’t justified. At a typical regional bank serving agricultural lenders or small business networks, FedNow became the platform of choice because the upfront cost was near zero and transaction volumes didn’t justify separate RTP infrastructure investment.
But accessibility masks a critical limitation: throughput. FedNow’s early transaction volumes sit well below RTP’s. In the first full year of operation, FedNow processed millions of transactions monthly; RTP, operating across fewer but larger banks, processes tens of millions. For a practitioner at a money center bank processing thousands of real-time payments daily, this matters. Smaller volumes mean less operational pressure on the system, which also means less operational certainty — your institution may process its real-time payment successfully, but you lack the redundancy and stress-tested infrastructure that comes from a heavily trafficked network.
FedNow also operates within Federal Reserve hours. The platform runs 24/7, but settlement into Fed accounts follows Fed operating calendars. RTP, being a private network, can settle around the clock. For Treasury teams managing intraday liquidity, that difference compounds. A payment that settles immediately into a Fed account at 11 PM on a Saturday lacks the same operational utility as one that clears and settles into a correspondent banking relationship in real time, any day, any hour.
RTP: Network Effects and Correspondent Banking Lock-in
The Clearing House’s RTP operates differently. It’s a closed network; membership is selective. Settlement happens at The Clearing House, not the Federal Reserve. Costs are higher — membership fees, per-transaction fees, and integration expenses. Yet by 2026, RTP has become the platform of choice for banks processing high-value, time-sensitive flows: corporate payroll, same-day B2B settlements, and institutional fund transfers.
That preference reflects network effects. The larger banks — JPMorgan Chase, Bank of America, Citigroup, Wells Fargo, and others — committed to RTP early. Their customers, in turn, migrated flows to RTP because the banks themselves offered RTP as a primary channel. A corporate treasury team at a mid-market manufacturing firm discovered its bank offered RTP natively, reducing operational friction for payroll funding and vendor payments. The feedback loop locked RTP into the largest transaction flows.
More subtly, RTP embedded itself into correspondent banking relationships. For banks managing interbank settlement, the Clearing House already operated other critical infrastructure — ACH, wire transfer networks, and FedWire. RTP became another layer in that ecosystem. A regional bank might not be an RTP member itself, but it sends real-time payment requests through a larger correspondent bank that is. That arrangement works only if the correspondent bank treats RTP as a preferred channel, which most larger banks now do.
For compliance and risk teams, this correspondent relationship introduces a hidden operational risk. When a regional bank depends on a correspondent’s RTP participation, the regional bank loses direct visibility into settlement mechanics. If the correspondent experiences a real-time payment failure, the regional bank’s customers bear the delay while the correspondence relationship absorbs the friction. FedNow, by contrast, offers direct settlement, making the regional bank’s operations transparent to itself.
The Real Adoption Choice: Volume Thresholds and Strategic Intent
Here’s what practitioners at Algoy’s core audience should understand: the FedNow vs. RTP choice isn’t a technology decision. It’s a threshold decision tied to real-time payment transaction volume and the type of customer a bank serves.
For a bank processing fewer than 10,000 real-time payments monthly, FedNow is economically rational. Membership costs are immaterial. Integration effort is moderate. The network supports the use case. A credit union serving small business owners who demand same-day payroll funding doesn’t need RTP’s scale — FedNow suffices.
For a bank processing 50,000+ real-time payments monthly, especially high-value B2B flows, RTP becomes the logical choice. The per-transaction cost, multiplied across volume, becomes justified. The network effects — tighter integration with the largest banks and their corporate customers — compound. A regional bank with significant commercial banking operations will likely participate in both, using FedNow for lower-priority or lower-volume corridors and RTP for its core business flows.
For money center banks, the decision was made long ago: RTP is table stakes. JPMorgan Chase, Goldman Sachs, and Bank of America treat RTP participation as a customer expectation. Many also participate in FedNow but don’t market it heavily because their customers don’t demand it — they demand RTP speeds and integration with the bank’s existing transaction platforms.
The strategic implication is stark: real-time payment platforms are becoming embedded into liquidity management infrastructure, not treated as independent rails. Banks that integrate real-time capabilities into cash management systems see customer stickiness; those that treat FedNow or RTP as a separate, optional channel lose relevance to treasurers who need intraday liquidity visibility.
Interoperability, Routing Logic, and the Practitioner’s Burden
A Treasury manager at a regional bank with $12 billion in assets now faces a genuine problem: interoperability between FedNow and RTP remains limited. If Bank A uses FedNow and Bank B uses RTP primarily, a real-time payment from A to B doesn’t route seamlessly. Someone — usually at Bank A’s operations desk — has to route the payment to the recipient’s bank, confirm which platform that bank prefers, and potentially retry if the destination bank has participation constraints.
That operational friction is invisible in regulatory announcements but very visible to practitioners. A payments operations officer I’ve spoken with at a mid-tier bank noted that their real-time payment success rates diverge by corridor: near 100% for payments to RTP-heavy banks, closer to 97% for FedNow corridors because re-routing and confirmation steps add failure points.
The Federal Reserve has published interoperability guidance, but it stops short of automated routing. The onus sits with sending banks to understand their counterparty’s platform preferences and route accordingly. For a bank serving customers across geographies and industries, that means maintaining routing tables, updating them as smaller banks shift platforms, and training operations staff on the logic. It’s operationally expensive and easy to bungle — a common source of failed real-time payment attempts.
Regulatory Pressure and Compliance Considerations
Regulators have largely stayed quiet on FedNow vs. RTP preference, which itself is informative. The Federal Reserve didn’t launch FedNow to mandate adoption; it launched it to create competition. But that hands-off stance creates a coordination problem: no regulator is forcing a unified routing standard, so banks are left to negotiate.
From a third-party risk perspective, choosing RTP introduces dependency on The Clearing House’s operational and security standards. Banks increasingly face scrutiny on third-party operational resilience, and the Federal Reserve’s own guidance on third-party risk now explicitly mentions payments infrastructure. Choosing FedNow, by contrast, introduces dependency on Federal Reserve infrastructure — arguably more resilient but less agile than a private network when problems arise.
A compliance officer managing vendor risk should ask: which platform’s outage would harm us more? For most banks, an FedNow outage is inconvenient. An RTP outage would be catastrophic if RTP handles the bank’s highest-value flows. That asymmetry explains why risk teams at large banks insist on dual participation — not because they expect interoperability, but because they can’t afford single-platform dependency.
What US Banks Are Actually Choosing: Current-State Adoption Patterns
| Bank Size / Type | Primary Platform | Secondary Participation | Driver |
|---|---|---|---|
| Money Center Banks ($1T+) | RTP | FedNow (limited) | Customer base demand; high-value flows |
| Regional Banks ($50B–$500B) | Both (RTP primary) | FedNow for lower-volume corridors | Correspondent relationship; volume-driven |
| Community Banks ($1B–$50B) | FedNow | RTP via correspondent | Cost; direct Fed access |
| Credit Unions (<$1B) | FedNow | None (typically) | Accessibility; cost-prohibitive RTP membership |
This isn’t uniform. Some regional banks with strong RTP relationships (particularly those operating in major financial hubs like New York or Chicago) have minimised FedNow adoption. Others, especially those with significant agricultural or rural lending operations, have gone all-in on FedNow because their customer base prefers lower-cost, accessible platforms.
The data also reveals winner-take-most dynamics in certain segments: RTP dominates corporate-to-corporate transactions and payroll processing in major metros. FedNow dominates small-business-to-small-business payments and credit union corridors. The middle — regional corporate payments and interbank settlements — remains contested, with corridor-by-corridor decisions based on counterparty preferences.
The Hidden Cost: Operations and Dual-Infrastructure Maintenance
Banks that support both platforms incur operational costs that don’t appear in P&L statements clearly. A payments team must monitor both networks, maintain separate settlement reconciliation logic, handle dual-platform incidents, and staff operations centers familiar with each platform’s failure modes.
I’ve observed banks where the real-time payments desk runs separate monitoring for FedNow and RTP, requiring different dashboards, different incident escalation procedures, and different documentation. When a real-time payment fails, the first troubleshooting question is always: “Which platform did it go through?” If the answer is unclear, operators lose time determining where to look.
This operational tax explains why smaller banks rationally chose FedNow exclusivity — it eliminates complexity. Larger banks absorb the complexity because their customer base is distributed and diverse enough to demand both. The middle tier bears the heaviest burden, forced to maintain dual platforms without the scale to justify it fully.
Cross-Border Real-Time Implications
Neither FedNow nor RTP currently enables real-time cross-border payments. That’s a separate problem, but it informs the domestic choice. If a US bank knows its international Treasury operations require overnight or next-business-day settlement anyway, the incremental value of same-day domestic real-time payments diminishes slightly. Some banks have deprioritised real-time domestic investments partly because their customer base operates globally and expects consistency across corridors.
This matters for strategy: as cross-border real-time corridors eventually open (particularly between the US and Canada, and the US and EU), domestic real-time platform choices may shift. A bank that built its entire Treasury operations around FedNow might discover that future integration with faster cross-border rails requires RTP’s technical architecture. That lock-in risk is not yet priced into most banks’ strategic decisions but should be.
The Algoy Perspective
Most practitioner discussions of FedNow vs. RTP focus on technical features or settlement mechanics. The real issue is institutional lock-in masquerading as choice. Large banks locked into RTP early because its governance sat at The Clearing House, where those banks already had influence. The Federal Reserve launched FedNow partly to break that lock-in for smaller players. But by 2026, the result isn’t healthy competition — it’s fragmentation.
The strategic problem no one discusses: a dual-platform market creates operational friction that advantages banks large enough to absorb it and disadvantages those that can’t. A $20 billion regional bank might have the customer demand for RTP but lacks the transaction volume to justify the membership costs. It therefore participates via correspondence, losing direct control of settlement. A credit union has zero ability to influence RTP governance but must live with whatever interoperability decisions RTP makes unilaterally.
The outcome is a real-time payments market that looks competitive on the surface but operates with hidden hierarchy. FedNow is the platform of the structurally weak; RTP is the platform of the structurally strong. That’s not sustainable long-term, and regulators will eventually have to address it — either by mandating interoperability standards (expensive, slow) or by consolidating the networks (unlikely, given Fed-vs.-private-sector politics).
Frequently Asked Questions
Can a bank participate in both FedNow and RTP simultaneously?
Yes. Larger banks and many regional banks now maintain dual participation, using each platform for different transaction types and corridors. However, there is no automatic routing between them — a bank must determine which platform a recipient bank prefers and route accordingly, adding operational overhead.
What happens if a real-time payment fails on FedNow — does it automatically retry on RTP?
No. The sending bank must detect the failure, determine why it occurred, and decide whether to re-route to RTP or retry on FedNow. This is a manual process at most institutions, not an automated failover, which is why some real-time payment attempts fail entirely if the operator misdiagnoses the problem.
Which platform costs less to implement?
FedNow typically costs less in membership and integration fees because participation is subsidised by the Federal Reserve. RTP requires higher upfront investment but spreads costs across higher transaction volumes at larger banks. For a bank processing fewer than 5,000 real-time payments monthly, FedNow is almost always more economical.
Are there settlement differences between FedNow and RTP that affect Treasury operations?
FedNow settles into Federal Reserve accounts on Fed operating schedules; RTP settles into Clearing House accounts 24/7. For intraday liquidity management, this difference is material — FedNow payments cannot be accessed or re-used immediately at non-Fed hours, while RTP payments settle in real time regardless of the time of day or day of the week.
