• What "Real-Time Payments" Means in B2B
  • Why B2B Adoption Trails P2P

A working guide to real-time payments in U.S. B2B operations, focused on what changed when both FedNow and RTP raised their per-transaction limit to USD 10 million in 2025.

Quick Answer Real-time payments (RTP network and FedNow) settle in seconds, run 24/7, and now support transactions up to USD 10 million on both rails. B2B adoption trails P2P because B2B requires invoice reconciliation, dual authorization, and exception handling that consumer apps do not. The use cases working at scale today are vendor pay, instant payroll for off-cycle pay and contractor disbursements, insurance claim refunds, and corporate treasury sweeps. The bigger limit raise unlocked commercial real estate closings, large escrow funding, and treasury liquidity moves that previously required Fedwire.

Key Takeaways

What "Real-Time Payments" Means in B2B

In the U.S., real-time payments means either the RTP network operated by The Clearing House (live since 2017) or the FedNow Service operated by the Federal Reserve (live since 2023). Both networks settle credit-push payments between participating financial institutions in seconds, 24/7/365, with finality. Both use ISO 20022 messaging. Both raised their per-transaction limit to USD 10 million in 2025.

The defining characteristic for B2B operations is irrevocability. Once a real-time payment settles, the originating party cannot pull it back the way ACH allows under Nacha R-codes. That single property reshapes how AP, treasury, and fraud teams think about authorizing a payment.

Why B2B Adoption Trails P2P

Person-to-person real-time payments hit critical mass in the U.S. faster than business payments. Zelle, which runs on RTP and FedNow under the hood, processes hundreds of billions of dollars annually. The same rails carrying that traffic have been available for B2B for years, but business adoption lagged. Five operational reasons explain the gap.

Invoice reconciliation overhead. A P2P payment is a one-time transfer between two phones. A B2B payment usually settles a specific invoice, a partial invoice, a credit note, or a netted statement. AR teams need to match the incoming payment to the right invoice number, often across hundreds of open items per customer. Real-time rails support remittance data, but the field formats and field sizes were initially narrower than the ISO 20022 pain/pacs standards used elsewhere.

Dual control on outgoing payments. Most corporate AP processes require a maker-checker pattern: one person creates the payment, another approves it. Adding real-time speed without rebuilding the approval workflow risks losing a meaningful internal control. The slow adoption was partly companies waiting for their treasury management systems to add real-time approval support.

Exception handling without reversibility. ACH lets a sender claw back a wrong payment within a few banking days under specific R-codes. RTP and FedNow do not. The remedy for an erroneous real-time payment is a separate return request that the receiving party voluntarily honors. AP teams used to ACH return rights had to develop new processes (and stronger upfront validation) before trusting real-time at scale.

Bank participation gaps. Both sender and receiver banks must be on the same rail. As of late 2025, FedNow has roughly 1,600 participating financial institutions and RTP has about 950 in active B2B traffic. The U.S. has about 9,000 banks and credit unions combined, so coverage is significant but not universal. Until your largest customers and suppliers all bank with a participating institution, the routing decision adds friction.

Limit caps. Before 2025, the per-transaction limit on FedNow was USD 1 million, and on RTP it was USD 1 million through February 2025. Many B2B vendor payments exceed that, so businesses had to either split a payment or fall back to Fedwire. The USD 10M raise in 2025 removed that ceiling for the vast majority of B2B traffic.

The November 2025 Limit Raise Changed Treasury Operations

The Federal Reserve increased the FedNow per-transaction limit to USD 10 million effective November 2025, in response to growing commercial demand. That follows RTP's matching raise in February 2025. The Fed cited three specific commercial use cases the raise enabled:

  • Corporate treasury sweeps between internal business accounts at different banks, where the prior USD 1M cap forced multiple parallel transactions and reconciliation work.
  • Corporate payroll funding without prefunding payroll accounts days in advance, freeing working capital.
  • Vendor payments and immediate clearing of high-dollar commercial real estate closings, including escrow account funding.

The treasury implication is concrete: a CFO that previously needed to time end-of-month vendor payments around Fedwire's operating window can now run those payments on FedNow at any time, including weekends and overnight, with same-second finality. The Federal Reserve's Q1 2025 FedNow data showed average payment size jumping to USD 101,435 in 2025 (from USD 25,376 in 2024). Transactions are getting larger as the corporate use cases come online.

B2B Use Cases That Work Today

Use Case Rail Why It Works Why It Replaces What
Vendor pay (urgent) RTP or FedNow Sub-second settlement, USD 10M limit Replaces wire transfers; lower cost
Vendor pay (Request for Payment) RTP RfP Biller sends structured invoice to payer's bank app for one-click approval Replaces emailed PDFs + manual ACH
Off-cycle payroll RTP or FedNow Instant funds to employees on termination, last-day, or off-cycle bonuses Replaces overnight ACH + check pickup
Contractor / gig pay RTP or FedNow 24/7 disbursement matches gig schedule Replaces weekly ACH batches
Insurance claim refunds RTP or FedNow Customer expects immediate payout Replaces check mailings (7-10 days)
Merchant funding (POS settlement) RTP Same-day card settlement to merchant accounts Replaces T+1 ACH net settlement
Real estate closing funds RTP or FedNow (post Nov 2025) USD 10M limit covers most residential and small commercial deals Replaces Fedwire, lower cost
Treasury liquidity sweeps RTP or FedNow 24/7 means weekend and holiday balancing Replaces Monday-morning Fedwire batch

Sources: TCH RTP 2024 records release, Federal Reserve B2B instant payments white paper, J.P. Morgan instant payments guide.

Vendor Pay With Request for Payment

The most operationally interesting B2B use case is Request for Payment (RfP) on RTP. RfP is a structured message: the biller pushes an electronic invoice to the payer's bank app or treasury system, including invoice number, amount, due date, and remittance details. The payer reviews and clicks once to authorize the credit-push payment back. The flow eliminates emailed PDFs that the payer has to manually re-key into their AP system.

By Q2 2025, more than 950 financial institutions on RTP were sending and receiving transactions, with about 285,000 businesses using the network monthly for supply chain, bill pay, and merchant settlement. Industry consensus is that RfP starts to meaningfully reshape B2B invoicing in 2026 as more billers go live with structured RfP outflows.

Instant Payroll

Payroll is the use case the Federal Reserve specifically called out in the USD 10M limit raise. The mechanics matter. Traditional payroll runs as a Same Day ACH or next-day ACH batch on a fixed schedule. To meet that schedule, employers prefund the payroll bank account several business days in advance, tying up working capital. With FedNow or RTP, the employer can fund payroll the day of pay, even on weekends, at the moment the payroll system runs.

For staffing agencies, gig platforms, and businesses with high contractor turnover, the use case extends to per-job disbursement. A contractor finishes a Saturday job and is paid Saturday night.

Refunds and Disbursements

Insurance, healthcare, and merchant refund flows are some of the fastest-adopting B2B use cases because the receiving party is a consumer with high expectations. A customer waiting 7-10 days for a check has a different perception of the brand than a customer paid in seconds.

Corporate Treasury

The use case the USD 10M raise specifically unlocked. Treasury teams running cash sweeps across multiple banks previously had three options: Fedwire (expensive, business hours), Same Day ACH (cheap, capped at USD 1M, business days), or batched standard ACH (cheap, slow). FedNow or RTP at USD 10M makes 24/7 sweeps practical at meaningful dollar amounts.

Original Research: Float Value Lost to ACH Settlement Delays

For a mid-market business running USD 5 million in monthly vendor payments through standard ACH (T+1 settlement) instead of a real-time rail, we modeled the implicit cost of the one-day float at three interest rate environments:

Annual Money-Market Rate Daily Float Value on USD 5M Annualized (250 banking days)
1.0% USD 137 USD 34,247
3.0% USD 411 USD 102,740
5.0% USD 685 USD 171,233

At 5% money-market rates, the implicit float subsidy ACH provides on USD 5 million of monthly vendor traffic exceeds USD 170,000 per year. That is the cost a treasury team can attribute to staying on ACH for time-sensitive vendor pay rather than moving to RTP or FedNow. The per-transaction cost difference (USD 0.50 ACH vs. USD 0.50 - USD 1.00 RTP) is essentially noise compared to the float math.

The opposite calculation is true for non-urgent recurring payments. If you are sending payroll on a fixed two-week cadence and the funds were already in the payroll account, real-time delivers no float advantage. ACH still wins.

Where Real-Time Falls Short for B2B

No debit pull. Both RTP and FedNow are credit-push only. The biller cannot debit the payer's account directly. This is intentional (it eliminates a category of fraud) but it means recurring billing models that depend on pulls must either use RfP (an authorized push) or stay on ACH.

Irrevocability raises the bar on fraud controls. Business email compromise (BEC) attacks are the primary fraud vector for corporate payments. The 2025 AFP Payments Fraud and Control Survey reported that 79% of organizations experienced attempted or actual payments fraud in 2024, with 63% experiencing BEC specifically. ACH gives a return window; RTP and FedNow do not. AP teams moving to real-time need stronger up-front controls: verified callback, dual authorization, and out-of-band confirmation for new vendor bank instructions.

Bank participation gaps. If your largest supplier banks with a community institution that has not joined either real-time network, the payment falls back to wire or ACH. Confirming counterparty bank participation is the new prerequisite for choosing the rail.

Remittance data limits. Early real-time messaging carried less structured remittance data than ACH CCD+ or CTX formats. ISO 20022 has narrowed that gap, but legacy AR systems still sometimes struggle to map ISO 20022 remittance to internal invoice fields. Test before assuming.

Receiver capability is not universal. A FedNow-participating bank may be configured for receive-only, not send. A treasury team relying on real-time outbound has to confirm the destination bank is configured to receive the inbound transaction, not just registered for the network.

Adoption Timeline: Where We Are in 2026

The maturity curve for U.S. B2B real-time payments looks roughly like this:

  • 2017-2019: RTP launches; early bank participation. P2P (Zelle on RTP) drives most volume. B2B is experimental.
  • 2020-2023: RTP expands to about 280 financial institutions. FedNow launches in July 2023. B2B starts to adopt for instant payroll and refunds.
  • 2024: RTP value grows 94% to USD 246B. FedNow ends the year with about 1,100 participants and USD 38B in value.
  • February 2025: RTP raises limit to USD 10M. B2B vendor pay and commercial use cases accelerate.
  • November 2025: FedNow raises limit to USD 10M. Corporate treasury, real estate closings, and large vendor pay shift from Fedwire to FedNow.
  • 2026: Request for Payment (RfP) reaches scale on RTP for B2B billing. Both networks expand to 1,800+ FIs.
  • 2027 (proposed): Same Day ACH limit raised to USD 10M (Nacha proposal, effective March 2027). ACH narrows the gap on dollar amounts but stays slower than real-time.
  • 2028: Deloitte's conservative scenario projects USD 18.9 trillion of U.S. B2B payments shifting from ACH and checks to real-time.

When This Guide Isn't For You

If you are a sole proprietor sending fewer than 10 payments a month, the operational overhead of standing up FedNow or RTP outbound usually exceeds the float benefit. Stick with ACH or card.

If your business operates exclusively in cross-border B2B, RTP and FedNow are domestic U.S. rails only. SWIFT gpi, regional instant payment links (FedNow-Banco de Mexico pilot, RTP cross-border initiatives), and emerging on-chain settlement options like USDC are the international equivalents to evaluate.

If your largest counterparties bank with institutions that have not joined either real-time network, the routing fallback to ACH or wire negates much of the operational benefit. Audit your top 20 trading partners' bank participation before building a real-time strategy.

If your payment workflow depends on debit pulls (subscription auto-pay, utility billing, gym memberships), ACH or card networks remain the only practical option. RTP's RfP is a push with authorization, not a pull.

How We Verified This

RTP volume and value statistics are from The Clearing House 2024 records announcement and the ABA Banking Journal summary. FedNow participation, volume, and limit data are from the Federal Reserve Financial Services FedNow Volume and Value page, the September 2025 press release on the USD 10M limit increase, and Federal Reserve Fed360 coverage. The Deloitte B2B real-time payments prediction is the source for the USD 18.9 trillion / USD 37 trillion 2028 scenarios. Fraud statistics come from the 2025 AFP Payments Fraud and Control Survey.

Frequently Asked Questions

Is Zelle considered an RTP?

Zelle is a consumer-facing brand that increasingly settles over the RTP network and the FedNow Service underneath. It is not a standalone payment rail. The transaction limits, dispute rules, and bank participation for Zelle differ from raw RTP or FedNow access; banks set their own per-day and per-transaction caps on the Zelle service.

What is the $3,000 bank rule?

The USD 3,000 figure refers to the Bank Secrecy Act recordkeeping requirement for monetary instruments (cashier's checks, money orders, traveler's checks) at or above USD 3,000. It is not an ACH, RTP, or FedNow rule and does not cap real-time payment amounts. The current per-transaction caps are USD 10 million on RTP, USD 10 million on FedNow, and USD 1 million on Same Day ACH (with a proposed increase to USD 10 million in March 2027).

Is RTP the same as ACH?

No. RTP is a real-time, credit-push, 24/7/365 network operated by The Clearing House with irrevocable settlement in seconds. ACH is a batch network governed by Nacha rules, operated by the Federal Reserve and EPN, settling in 1-2 business days for standard transactions or same banking day for Same Day ACH, with return rights under R-codes. They are completely separate networks.

What are the payment methods for B2B?

The most common U.S. B2B payment methods in 2026 are ACH (still the dominant rail by both volume and dollar value), wire transfer (Fedwire and CHIPS for very large or cross-border), checks (declining but still material; 26% of B2B payments per Nacha's 2024 AFP citation), real-time payments (RTP and FedNow), commercial cards (V-cards, virtual cards, P-cards), and increasingly stablecoin settlement for cross-border. See our FedNow vs RTP vs ACH comparison for the full operational picture.

Are RTP and FedNow available 24/7?

Yes. Both networks operate 24 hours a day, 7 days a week, including weekends and federal holidays. Settlement is in seconds. In 2024, 42% of RTP transactions occurred outside standard business hours, which is the period ACH and Fedwire do not cover.

Related Articles

Share

Was this article helpful?