The US was late to instant payments. The UK had Faster Payments in 2008. The eurozone had SCT Inst in 2017. India's UPI, launched 2016, moved more transactions last year than every US card network combined. The Federal Reserve launched FedNow in July 2023 to close that gap, and adoption has moved faster than most people expected. If you run a US business and haven't looked at it, it's worth understanding what's different.
What FedNow actually is
FedNow is a real-time gross settlement service run by the Federal Reserve. It lets participating banks and credit unions send and receive payments between US bank accounts instantly, 24 hours a day, every day of the year, including weekends and federal holidays. Settlement happens in central bank money at the Fed, not in commercial bank money, which is the same mechanism that underpins Fedwire for large-value wires.
That 24/7/365 operation is the piece that separates FedNow from ACH. ACH closes on weekends and holidays. FedNow doesn't.
How a FedNow payment moves
Every FedNow payment is credit-push. The sender's bank initiates the payment; the receiver never pulls funds. That's a structural difference from ACH debits and from cards. It also means FedNow is not a substitute for card processing, because you can't initiate a merchant-pull transaction on it.
Under the hood, FedNow uses ISO 20022 messaging. The two message types you'll hear cited most are pacs.008, which is the customer credit transfer initiation, and pacs.002, which is the acknowledgment or status report that tells the sender whether the payment was accepted or rejected. Settlement finality happens within seconds: the sender's bank gets debited, the Fed moves the funds, the receiver's bank gets credited, and the receiver gets their money. There's no reversal mechanism once the payment settles, which is a deliberate design choice.
The $500k cap
At launch in 2023, FedNow's per-transaction cap was $500,000. The default cap for banks is typically lower unless they opt up. The $500k ceiling applies to individual transactions; there's no daily cap, so a business could in theory send many $500k transactions in a day.
That's well above the old RTP $1 million cap as of 2022, but well below what you can wire via Fedwire. FedNow sits in the instant-payments-for-most-business-needs zone, not the large-value-wire zone.
FedNow vs RTP
The Clearing House launched its RTP network in 2017, six years before FedNow. RTP is owned by a consortium of the largest US banks; FedNow is run by the central bank. Both are 24/7, both settle instantly, both use ISO 20022, and both are credit-push.
The practical difference is reach. RTP connects large banks and a growing set of mid-size banks. FedNow, because the Fed connects to every US depository institution, has been able to sign up community banks and credit unions that RTP didn't reach. By early 2026, FedNow had well over 1,000 participating institutions and the network effect was starting to compound.
Most large transactions in the US will end up settleable on either rail, and banks will route based on whichever side supports it. For a business picking a rail, it's a bit like asking whether to accept Visa or Mastercard: pick the provider whose platform supports both and let them figure it out.
FedNow vs ACH
ACH is batch. FedNow is real time. ACH is cheap. FedNow costs more per transaction but the Fed sells it at a near-flat price that's still well under card rates. ACH supports debit pulls. FedNow doesn't.
For recurring low-value B2B billing, ACH is still the right rail. For payroll, ACH direct deposit is still the standard. For a supplier payment where the supplier wants confirmation before shipping, FedNow is genuinely new capability, because the money moves and the supplier's bank account shows it in seconds.
Who's participating
Adoption started modestly in 2023 with around 35 participating institutions and ballooned through 2024 and 2025. By the end of 2025 the participant list was into four figures, including most of the top-30 US banks and an increasing number of credit unions. JPMorgan Chase, Wells Fargo, US Bank, PNC, and BNY were among the first wave. The Fed publishes the current participant list and it's worth checking before assuming a counterparty can receive FedNow.
"Send-capable" and "receive-only" are different tiers. A bank can join as receive-only and still have a customer experience that works for consumer inbound payments, even if that bank doesn't let its customers originate outbound FedNow transfers.
What it means for B2B and for phone payments
B2B is where FedNow's impact has been biggest so far. Freight, construction, wholesale, and any industry where "did the money land yet" is a blocker on the next step of the job has grabbed onto real-time settlement. The Fed's own research shows a material share of FedNow volume in the first two years has been B2B invoice payment and account funding.
For phone payments, FedNow is starting to show up as an option on outbound invoice calls. A customer on the phone confirms they want to pay, the agent sends a payment link or asks the customer to push the funds from their banking app, and the money lands before the call ends. That's not the same flow as a card authorization, and it doesn't replace cards for one-off consumer transactions, but for high-ticket B2B calls it's starting to matter.
Consumer-facing adoption
Consumer adoption is slower than bank adoption. Most US consumers don't have a "Send FedNow" button in their banking app yet; they have Zelle, which runs largely on RTP today. As more banks build FedNow originations into their consumer apps through 2026 and 2027, the user-visible label will shift, but most consumers will never know which rail moved their money. They'll just see "instant."
For businesses thinking about where to take US phone payments next, the short version is this: cards aren't going anywhere, ACH is still the right rail for recurring low-value billing, and FedNow is the rail you offer when the customer wants confirmation the money moved before they hang up. Our FedNow glossary entry has more on the message types and settlement mechanics if you want to go deeper.
Request-for-payment and the next phase
FedNow's initial launch was send-only from an initiator's perspective. The second major feature set the Fed has been rolling out through 2025 and 2026 is Request for Payment, or RFP. RFP lets a business send a structured payment request to a consumer or counterparty, who then approves the push payment from their banking app. The money still moves as a credit-push, so the design stays out of debit-authorization territory, but the user experience is closer to a bill presentment.
This matters for phone payments because it changes the flow. Instead of reading a routing number or navigating a payment link, the agent initiates an RFP, the customer gets a notification in their banking app, taps approve, and the money lands. No card data, no ACH authorization, no chargeback window. The settlement is final within seconds. For high-value B2B invoices, that's a genuinely new capability that doesn't map neatly onto anything the US rails offered before.
Risks and fraud patterns
Instant finality cuts both ways. FedNow payments, once settled, can't be clawed back the way a card chargeback or an ACH return can. That's designed protection for the receiver and intentional friction for the sender. It also means FedNow is a prime target for authorized push payment fraud, where a consumer is socially engineered into sending funds to a fraudster. UK Faster Payments, which has been live since 2008, saw exactly this fraud pattern emerge and drove the push for mandatory reimbursement rules. Expect US regulators and banks to go down a similar path over the next few years as FedNow volume grows. For merchants accepting FedNow-originated payments, the counterparty risk is much lower than with cards because there's no chargeback, but you still want to validate who's on the other side.
