In The Know Insights Blog Orchestrating Real-Time Payments: FedNow, RTP and Every Rail in Between fali02 Nov 10, 2026 05 Minutes 05 Minutes 0 Share Copy link Link copied to clipboard! Share to Facebook X Linkedin Instagram Threads Email Save Get Started with i2c Real-time payments have been “right around the corner” for years. That era is over. Instant payments are now an operating priority for banks, credit unions and fintechs, and the shift took center stage at our Accelerate Summit 2026, where we joined payments leaders from across the industry to dig into what it takes to orchestrate real-time payments across multiple rails. 🎥 WATCH NOW: Orchestrating Real-Time Payments for Multi-Rail Optimization From where we sit, connecting financial institutions and fintechs to multiple payment rails, the question is no longer whether to offer instant payments. It’s how quickly institutions can move from receive to send, and how well they can route every payment to the right rail. Instant Payments Have Moved Beyond Proof Point The numbers tell the story. According to The Clearing House, the RTP® network processed 150 million transactions totaling $621 billion in the third quarter of 2026 alone, and it now supports transactions up to $10 million. That shifts real-time payments from a consumer convenience to a business-critical rail for treasury, supplier payments, merchant settlement and account funding. FedNow® has scaled just as quickly. More than 1,800 financial institutions now participate, giving the U.S. a second real-time rail with national reach. At the same time, ISO 20022 adoption across Fedwire and other interbank systems is bringing data-rich messaging to critical mass. Demand is the other driver. Consumers and businesses get instant gratification in nearly every part of their lives, so they expect the same from payments. Soon, customers won’t ask for instant payments at all. They’ll simply expect them, and if their financial institution doesn’t offer them, they’ll go somewhere else. Receive Is a Switch. Send Is an Operating Discipline. Most institutions start with receive, and for good reason: it’s close to flipping a switch. Send is different. It touches liquidity, 24/7 operations, service models and the control environment. The gap shows up in the data. According to the Federal Reserve, more than a third of FedNow participants are send-enabled, yet only 8% to 10% of the network actively sends. The blockers tend to fall into three buckets: Technology: The institution’s service provider hasn’t enabled send, or the back end can’t support it. Fraud concerns: Teams worry that instant, irrevocable payments mean instant, irrevocable losses. The business case: Leaders want proof that send will pay for itself, and treasury teams aren’t yet confident leading that conversation with clients. The fraud concern is often more perception than reality. With instant payments, the control point moves to the front of the transaction. Good funds checks, OFAC screening and fraud scoring all happen before the payment is released, and The Clearing House reports RTP fraud rates measured in basis points. Pairing those front-end controls with AI-driven fraud detection keeps risk decisions sharp without slowing the payment down. The institutions moving fastest roll out send in a measured way. They set limits, start with known use cases and restrict time windows, then expand as confidence grows. Done right, enabling send should strengthen your operating model, not stretch your risk appetite. FedNow and RTP: Ubiquity Without Interoperability RTP and FedNow aren’t interoperable, and that isn’t changing anytime soon. That doesn’t put ubiquity out of reach. Cards offer a useful parallel. The major card networks run on similar but distinct standards, and together they still cover nearly every point of sale. Wires work the same way, with two networks that each serve a purpose. Running two instant payment networks also adds resiliency, since either one can serve the market. The better way to measure ubiquity is as a client outcome. Can the payment reach the counterparty? Can it clear and settle immediately? Can it reconcile cleanly? With roughly 9,000 U.S. financial institutions, reaching the long tail through a single network is unlikely. Reaching it across both is achievable. That puts the routing burden on the technology layer, and it’s a problem we know well. As a processor, our job is to support multiple standards and route each payment to the network that can reach its endpoint. We built our Payment Hub for exactly that kind of payment orchestration, connecting to FedNow, Mastercard Send, Visa Direct and ACH through a single integration, and we’re continuing to expand its rails and routing capabilities. It’s also why Payment Hub won Best As-a-Service Solution – Payments at last year’s Banking Tech Awards USA. Payment Hub sits above your existing cores and processors or runs as part of i2c’s unified platform across two fully redundant data centers that ensure 99.999% historical uptime—less than five minutes of downtime per year. Liquidity Management Goes 24/7 Pre-funding and settlement carry the most operational weight, and the two networks approach them differently. RTP uses ledger-based pre-funding backed by funds held at the Federal Reserve Bank of New York. That design ring-fences exposure: in a stress event, a participant’s risk is limited to its pre-funded RTP position. FedNow settles through participants’ master accounts. To manage the risk, institutions can set network send limits, apply account activity thresholds by customer segment or even individual account and use liquidity management transfers to move funds between accounts around the clock, including when wire isn’t available. Request for Payment: The Next Adoption Curve If receive is the first step and send is the second, request for payment (RFP) is the third. It gives institutions the pull mechanism they’ve been missing, which matters for top-up and disbursement models and for B2B flows that need to match incoming receipts with outgoing funds. Adoption is still early. RFP needs technical enablement from service providers, risk controls at the institutions responding to requests and a clear business case. The fraud question is real, too. After years of telling customers not to click, RFP asks them to click. The safeguards are stronger than they look. Accepting a request doesn’t release a payment; it still flows through normal controls first. Requests arriving through a trusted financial institution channel can be screened, and RFP warranties create a path to recover losses when they’re violated. The institutions seeing the most success approve funding and technical capacity for all three phases (receive, send and RFP) up front, then roll them out in sequence. The payoff is a single connected flow from invoice to approval to payment to reconciliation. Multi-Rail Payments: Match the Rail to the Workflow Instant payments won’t replace every other rail. ACH and wires aren’t going away, and even checks, long predicted to disappear, are still hanging on. Each rail has its place. What sets instant payments apart is immediate and final settlement, 24/7 availability, confirmation for both sender and receiver and data-rich ISO 20022 messaging. James Dillard, Director, Client Relationship Management at The Clearing House, was quick to drive that point home to the Accelerate Summit audience. “You don’t want to match the workflow to the rail,” he said. “You want to match the rail to the workflow.” New rails also create new payments rather than simply cannibalizing old ones. When the UK looked back at its Faster Payments launch, the vast majority of volume turned out to be net new. On-demand payroll is a U.S. example: one paycheck a month can become 31 payments or more. Where Instant Payouts Fit in Card Portfolios For institutions built around card programs, instant payments can feel like they belong to a different department. They don’t. Instant payments sit alongside cards, handling the money movement that happens after the transaction, from cash out to merchant settlement. The most relevant B2C use cases include: Instant payroll and earned wage access: Some of our clients already offer it for card programs, and it’s popular enough in the gig economy that consumers will pay for it. Insurance claims and disaster relief: Instant disbursement can skip the plastic and the payment terminal entirely, which matters for prepaid and benefits-style programs. Account funding and top-ups: Moving money into a card account the moment it’s needed. Stablecoins are an open question for some B2C payout models, since they can move value as a simple ledger transfer. The catch is that recipients ultimately need to convert those funds to fiat to spend them, so instant payment rails keep the advantage in the near term. The Business Case: Direct Revenue or Relationship Economics Instant payments remove float and interchange from the equation, which leads to the obvious question: how do institutions make money? The biggest opportunity may be the one the industry has undersold. “I think the industry’s done itself a bit of a disservice by branding this just as faster payments, not faster, more data-rich payments,” said Seth Perlman, Global Head of Product at i2c. ISO 20022 lets invoice data travel with the payment, which is how B2B payments, trade finance and other manual, paper-based processes move onto electronic rails. Adoption depends on ERP systems enabling that data, and progress is underway. Institutions are monetizing instant payments in two ways: Direct revenue: Pricing instant payments as a premium service, such as instant retail payments that replace wires at a lower price point. This works best when clients already have a proven use case, because a CFO will eventually ask you to deliver the number you projected. Relationship economics: Using instant payments to retain deposits, deepen client relationships and stay competitive. Some corporates now send their payments instantly, even at a higher cost, because it differentiates their own service. Workflow shifts before relationships do, and institutions that wait risk watching clients move to competitors that offer instant payments. Lower fraud rates, better fraud scoring from richer data and reduced operations costs add to the case. The institutions that treat instant payments as a fundamental relationship tool, not just a line on the payments P&L, will be the ones that win. Ready to orchestrate real-time payments across every rail your clients need? Let’s talk. Performance Check: Key Questions Answered Q: Why are real-time payments a priority now? Both U.S. instant payment networks have reached national scale, ISO 20022 is approaching critical mass and consumers and businesses now expect payments to be instant. Real-time payments have moved from proof point to operating priority. Q: Why do so many institutions start with receive only? Receive is close to flipping a switch, while send requires 24/7 operations, liquidity management, fraud controls and a clear business case. A measured rollout with limits and known use cases helps institutions move to send with confidence. Q: Can FedNow and RTP reach ubiquity without interoperability? Yes. Like the card networks, they don’t need to be interoperable to reach nearly every account. Institutions on both networks, supported by smart routing and orchestration, can reach virtually any counterparty. Q: How do financial institutions make money on instant payments? Through direct revenue from premium-priced services and through relationship economics such as deposit retention and deeper client relationships. Data-rich payments, lower fraud and reduced operations costs strengthen the case. Categories: Platform Self-issuance AI United Banking Credit published by fali02 More blog posts from fali02