Picture opening your money app and watching the balance update before you lift your thumb. That’s the promise of instant rails. Yet the industry still treats them like a curiosity, despite the data saying they’re safer than what we use every day.
The Stat That Should End the Debate
A new intelligence report with The Clearing House says fraud is 31x more likely on checks than on real-time rails.
Just 2% of firms reported any fraud on RTP® or FedNow, versus 63% reporting check fraud in 2024, with ACH at 38% and wires at 30%. Only 3% of financial institutions called real-time fraud “significant.”
Still, 85% of U.S. payment pros expect fraud to rise with instant payments, and that jumps to 95% at the largest institutions.
Two Years In, FedNow is Moving Real Money
FedNow just turned two, and it’s not a pilot anymore.
In Q2 2025, the network processed $245 billion, up from $492 million in Q2 2024 – that’s ~49,000% YoY and ~405% QoQ growth. Participation has climbed to roughly 1,400 banks, and the per-payment limit rose to $1 million in June 2025.
Meanwhile, The Clearing House lifted the RTP limit to $10 million in February 2025.
Receive-Only is Not Real-Time
Most participating banks are still in receive-only mode.
78% of organizations start that way (only 22% enable both send and receive), and the “receive-only problem” persists even as volumes surge.
Why? Legacy cores and middleware. In a joint survey, 73.4% of FIs said legacy systems are a moderate to severe barrier to enabling send.
Until those switches flip, customers experience a half-built bridge.
Fraud Fear vs. Fraud Facts
The rails themselves are designed to blunt common attack vectors: push-only flows, API-level controls, real-time visibility, and bank-to-bank collaboration.
Confirmation of Payee – a simple name/beneficiary check—has 96% support among U.S. banks and has cut fraud by ~60% in the U.K.
The paradox is perception: highly publicized authorized push-payment scams dominate headlines, while the day-to-day safety advantage over checks rarely does.
The Real Bottleneck Lives Inside the Bank
Connecting to FedNow or RTP is table stakes; operationalizing real-time is the work. That means rewiring posting rules, exception handling, risk checks, and reconciliation to run at the same speed as the rail. Their prescription is a dual-speed architecture, an orchestration layer that handles instant flows while legacy systems catch up, plus earlier fraud controls embedded in the flow (not bolted on after settlement).
Where The Value Shows Up First
The early use cases with real returns aren’t speculative. Insurance disbursements and emergency payouts (customers want money now, not in 70 days), marketplace/gig payouts, and B2B flows where just-in-time supplier payments and intraday liquidity matter.
With limits at $1M (FedNow) and $10M (RTP), these rails are already sized for meaningful commercial traffic. Some industry experts even expect instant payments to reach ~25% of U.S. electronic volumes within three years, if send catches up to receive. And with banks already exploring crypto vs. traditional rails, real-time settlement may be the bridge that keeps them competitive.
What “Good” Looks Like in Practice
The banks that turn real-time from a feature into a franchise tend to do the same handful of things well:
- Rewire before launch. Adjust risk checks, posting, and exception triggers so ops can match the rail’s speed.
- Run a dual-speed stack. Use an orchestration layer to insulate instant flows from core bottlenecks.
- Pick high-ROI lanes first. Think emergency payroll, claim payouts, supplier payments, places where speed pays for itself.
- Move fraud left. Insert controls earlier in the journey to prevent, not just clean up.
The Signal in The Noise
Ignore the hype cycles and watch these three tells instead:
- Send-enablement. As more banks enable send on FedNow/RTP, utility compounds.
- Fraud controls are going mainstream. Wider rollouts of tools like Confirmation of Payee should track with lower loss rates and rising comfort.
- Operational maturity. More orchestration layers, fewer manual handoffs, and cleaner real-time reconciliation indicate the shift from “connected” to capable.
Where This Lands
The numbers are not subtle: checks remain the fraud magnet; instant rails are scaling fast; receive-only is holding back the customer experience.
The technology works. The safety case is strong.
What’s left is execution – turning connections into capabilities and letting the rails do what they were built to do.
