Real-time payments let money move between bank accounts in seconds, around the clock. Instead of waiting for a batch-processing window or the next business day, a payment can clear and settle immediately, including nights, weekends, and holidays.
In the U.S., this guide focuses on the RTP network operated by The Clearing House, which launched in 2017 and now supports payments of up to $10 million. The network is used for everything from instant payouts and account-to-account transfers to loan funding, merchant settlement, and large business payments.
One terminology note: real-time payments describes the broader type of payment. The RTP network refers specifically to the real-time payment network operated by The Clearing House.
TLDR:
- Real-time payments on the RTP network clear and settle within seconds and operate 24/7/365.
- Payments are final once accepted and settled. A sender cannot simply cancel or recall a completed payment, although financial institutions can request that funds be returned.
- The RTP network supports payments of up to $10 million per transaction.
- More than 1,200 financial institutions were live on the RTP network by April 2026.
- RTP is particularly useful for time-sensitive payouts, account funding, merchant settlement, loan disbursements, B2B payments, and treasury workflows.
- RTP, ACH, and wires overlap, but each has different strengths around speed, availability, transaction size, and payment finality.
What Are Real-Time Payments?
Real-time payments are electronic bank-to-bank payments that are processed, cleared, and settled within seconds.
The RTP network has several characteristics that distinguish it from traditional payment methods:
- 24/7/365 availability: Payments can be sent and received outside traditional banking hours, including weekends and holidays.
- Immediate funds availability: Receiving financial institutions generally make funds available within seconds, subject to limited exceptions under the network rules.
- Final settlement: Once a payment has been submitted, accepted, and settled, the sending financial institution cannot unilaterally revoke or recall it.
- Structured payment data: RTP uses ISO 20022 messaging, allowing payment and remittance information to travel with the transaction.
The Clearing House describes the network as providing real-time and final interbank settlement, immediate availability of funds, continuous operation, payment-status transparency, and rich messaging. The Clearing House
How Do Real-Time Payments Work?
A real-time payment can move from initiation to settlement in just a few seconds.
First, the sender initiates a payment through their bank, financial application, or another product connected to a participating financial institution.
The sending financial institution authenticates the sender, verifies that the payment can be made, and submits the payment instruction to the RTP network.
The network routes the payment to the receiving financial institution. The receiving institution either accepts or rejects the payment.
If the payment is accepted, settlement occurs in real time. The receiving institution makes the funds available to the recipient and both sides can receive immediate confirmation of the payment's status.
Unlike ACH, RTP payments are not accumulated into batches that wait for a settlement window. Each payment is processed and settled individually. The network's technical specifications use ISO 20022 messages for the payment itself and for immediate status responses.
Can an RTP payment be reversed?
Not in the same way an ACH payment can.
An accepted RTP payment has final settlement, so the sender cannot simply recall it after the fact. The RTP network does, however, support messages through which a financial institution can request the return of funds. A request is not the same thing as reversing the original transaction: the return depends on the circumstances and the receiving side's response.
That distinction matters for product design. With real-time payments, fraud prevention and payment validation need to happen before money leaves.
The Clearing House RTP Network
The Clearing House launched the RTP network in 2017 as the first new core U.S. payments infrastructure introduced in more than 40 years.
Any eligible insured U.S. depository institution can participate. Banks and credit unions can connect directly to the network or use an approved third-party service provider for connectivity.
Adoption has increased significantly. By April 2026, more than 1,200 financial institutions were live on the network. On May 1, 2026, RTP processed a then-record 2.27 million transactions worth $8.62 billion in a single day. Through August 2026, the network had processed more than 371 million transactions worth approximately $1.47 trillion during the year.
The current transaction limit is $10 million per payment, up from $1 million in February 2025. The increase expanded RTP beyond smaller consumer and payout transactions into use cases such as supplier payments, real estate, treasury activity, and intercompany liquidity management.
RTP vs. ACH vs. Wire Transfers
RTP does not replace ACH or wires. The three rails solve overlapping but different payment needs.
| RTP | ACH / Same Day ACH | Wire | |
|---|---|---|---|
| Speed | Seconds | Batch-based; Same Day ACH settles within defined same-day windows | Typically same business day |
| Availability | 24/7/365 | Banking-day processing windows | Fedwire operates 22 hours per business day |
| Settlement | Individual, real-time settlement | Batch settlement | Individual, real-time gross settlement |
| Returns / reversals | Final once accepted; return can be requested | Defined return and reversal mechanisms | Generally final once settled |
| Current transaction limit | $10M | Same Day ACH: $1M | Designed for high-value payments |
| Common fit | Instant payouts, funding, B2B, treasury | Payroll, recurring payments, debits, high-volume payments | Large, time-sensitive payments |
Same Day ACH's current per-payment limit is $1 million. Nacha has approved an increase to $10 million, but it does not take effect until September 17, 2027.
Fedwire, meanwhile, operates from 9:00 p.m. ET on the preceding calendar day until 7:00 p.m. ET on each funds-transfer business day. Saturdays, Sundays, and Federal Reserve holidays are not funds-transfer business days. That makes it substantially more available than the phrase “business hours” suggests, but it is still not continuously available like RTP.
One other distinction is messaging. RTP was designed around ISO 20022 from the beginning, but structured ISO 20022 data is no longer unique to RTP: Fedwire completed its own migration to ISO 20022 in July 2025.
How Much Do RTP Payments Cost?
The price a business or end user pays for an RTP payment depends on its bank or financial provider.
At the network level, The Clearing House currently charges participating financial institutions $0.045 for an inter-participant payment sent over RTP and no network fee for receiving an RTP transaction. Those are network-participant fees, not necessarily the price a business or end user will pay.
That is why I would not compare “4.5 cents for RTP” directly with a "$15–$50 wire fee." One is an underlying network charge to a participating financial institution; the other is typically a bank's customer-facing price.
Benefits of Real-Time Payments
The biggest benefit of RTP is not simply that the rail is faster. It is that speed and availability can change the surrounding product experience.
A worker can receive earned wages after completing a shift instead of waiting for the next banking day. A business can receive merchant proceeds over the weekend. A borrower can access approved funds immediately. A treasury team can move liquidity when the need arises instead of planning around payment-system hours.
The $10M per-transaction limit, raised in February 2025, expanded RTP's practical scope. Treasury teams that previously defaulted to wires for larger inter-company transfers now have a 24/7 alternative with the same finality and lower per-transaction cost.
Real-time status information can also improve the software experience around a payment. Instead of submitting a payment and waiting for a later settlement file, an application can react immediately to whether the payment completed or was rejected.
Common Real-Time Payment Use Cases
Instant payouts
Marketplaces, payroll products, gig platforms, and other software companies can make earnings available shortly after work is completed instead of forcing recipients to wait for an ACH settlement window.
Account-to-account transfers
Customers can move money between eligible bank accounts in seconds, making RTP useful for funding and liquidity-management experiences.
Business and supplier payments
The $10 million transaction limit makes RTP relevant to a much wider range of B2B transactions, particularly when payment timing affects the release of goods, services, or inventory.
Loan and capital disbursements
Once financing is approved, funds can be made available quickly rather than waiting for a traditional banking-day payment.
Merchant settlement
Businesses can receive proceeds outside standard banking hours, improving access to working capital.
Treasury and cash management
Finance teams can move funds between accounts around the clock for liquidity management, cash concentration, and other time-sensitive treasury needs.
Risks and Challenges of Real-Time Payments
The same characteristics that make RTP useful also change the risk model.
Finality makes fraud prevention more important
Because an accepted payment cannot simply be recalled, there is less opportunity to catch fraud after money has moved.
Authorized payment scams are a particular concern. In these schemes, a legitimate account holder is manipulated into sending money to a fraudster, meaning the payment system may receive a technically valid instruction from the actual user.
Deloitte estimates U.S. losses associated with authorized payment fraud could reach approximately $14.9 billion by 2028 under its baseline scenario, up from an estimated $8.3 billion in 2024.
For companies offering instant payments, controls around authentication, account security, transaction limits, anomaly detection, and payment review therefore need to operate before a payment is released.
Not every destination is reachable
An RTP payment can only be delivered when the receiving financial institution is enabled to receive payments over the network.
That makes reachability an important part of the payment experience. Before allowing a customer to initiate an RTP payment, a product should know whether the destination institution is eligible for that rail and what alternative rail to use when it is not.
Speed increases the importance of good payment data
A payment that completes in seconds needs equally fast status and exception handling.
Software teams should understand what payment states, rejection reasons, counterparty information, remittance details, and webhook events their infrastructure exposes. The quality of that information determines what the product can tell a customer when something does not go as expected.
How Platforms Access Real-Time Payment Rails
The RTP network is built for financial institutions rather than direct connections from ordinary software companies.
Insured depository institutions can connect directly to The Clearing House or through a third-party service provider such as a core processor, hosted gateway, bankers' bank, or corporate credit union.
For a software company building RTP into its product, the more practical questions are:
- Can customers send, receive, or both?
- Can the product check whether a destination institution can receive RTP before sending?
- What payment statuses and rejection reasons are available through the API?
- What counterparty and remittance information is returned?
- How do completed payments appear on the account ledger?
- How are return requests and exceptions handled?
- Can the same product use ACH, wires, checks, and other rails when RTP is not the right fit?
The value of instant payments is much greater when the rail is integrated into the rest of the money-movement experience rather than treated as a separate payment system.
The practical model: platforms connect through participating banks and a financial infrastructure layer that maintains those bank relationships, with sending and receiving support checked separately since not every bank partner supports both. The infrastructure handles prefunding management, message formatting, settlement reporting, and bank oversight requirements underneath. Unit's documentation referenced here covers receiving RTP payments and reflects an early preview, not confirmation of production availability.
A few things matter when choosing an access path:
- Which networks your bank partner supports for both send and receive, since receive-only enrollment limits what end users can do
- Whether multi-rail fallback is available when a counterparty bank is not on the same network
- Where compliance ownership sits, including transaction monitoring and fraud controls on outbound payments, a key consideration covered in the enterprise-grade financial infrastructure guide
Multi-bank infrastructure reduces single-point risk. If one bank's prefunded balance runs low or a network is temporarily unavailable, payments can route through an alternate path without changes on your end. Unit's Custom implementation path is built for exactly this kind of complexity.
Real-Time Payments on Unit
Unit lets software companies send and receive Real-Time Payments over The Clearing House RTP network, with funds moving in seconds, 24/7/365.
Unit connects directly to The Clearing House, without an intermediary processor. RTP runs on the same Payments API, native ledger, and dashboard as ACH, wires, checks, and international payments. That means teams can add instant payments without introducing a separate payment provider, integration, or operating system.
Through Unit, companies can:
- Send and receive RTP payments directly into customer accounts.
- Check recipient-bank eligibility before sending, so applications can determine whether RTP is available and choose another supported rail when it is not.
- Build around payment outcomes in code, including network rejection details, transaction IDs, and a
TimedOutstatus for payments that do not resolve. - Reconcile payments to the underlying workflow using tags for identifiers such as orders, invoices, or claims.
- Access structured payment data, including sender account details on incoming payments, ultimate debtor and creditor information where applicable, and ISO 20022 data exposed through the API.
- Retry safely with idempotency, without creating duplicate payments.
Because RTP shares the same ledger and payment infrastructure as Unit's other rails, companies can build multi-rail workflows around a single account balance. For example, a platform can check whether a recipient can receive RTP and fall back to ACH when needed, receive funds over RTP on a weekend and make them available for card spend, or combine incoming RTP with wires and other payment methods without stitching together separate systems.
Read the docs to learn more about Real-Time Payments on Unit.
Final Thoughts on Real-Time Payments
Real-time payments are not simply faster ACH.
The RTP network combines continuous availability, immediate settlement, payment finality, higher transaction limits, and structured payment data in a rail designed for an always-on economy.
That makes it particularly valuable when waiting for the next banking day creates a genuine product or business problem. For software companies, the important question is not whether every payment should move in real time. It is whether RTP belongs alongside ACH, wires, and other rails so the right payment method can be used for each workflow.
FAQ
What does RTP stand for in payments?
RTP commonly stands for real-time payments. In the U.S., RTP® is also the name of the real-time payment network operated by The Clearing House.
How fast are RTP payments?
Payments on The Clearing House RTP network generally complete within seconds. The network operates continuously, 24 hours a day, 365 days a year.
Are RTP payments available on weekends and holidays?
Yes. The RTP network operates 24/7/365, including nights, weekends, and holidays.
What is the RTP transaction limit?
The current limit is $10 million per payment. The Clearing House increased the limit from $1 million in February 2025.
Can an RTP payment be reversed?
An RTP payment cannot be unilaterally canceled or recalled after it has been accepted and settled. A financial institution can request that funds be returned, but that is different from reversing the original payment.
What is the difference between RTP and ACH?
RTP processes and settles individual payments within seconds and operates continuously. ACH is a batch-based network that settles payments during defined banking-day windows. ACH also supports debit transactions and has established return and reversal processes that differ substantially from RTP.
What is the difference between RTP and a wire transfer?
Both can provide final, high-speed bank-to-bank payments. RTP operates continuously, including weekends and holidays, and currently supports up to $10 million per payment. Fedwire supports substantially larger payments but operates on a Federal Reserve business-day schedule rather than 24/7/365.
Which banks support RTP?
More than 1,200 financial institutions were live on The Clearing House RTP network by April 2026. The Clearing House maintains a current directory of participating institutions and routing numbers.
The content in this article is provided for general informational and educational purposes only and should not be construed as legal, tax, accounting, or regulatory advice. Unit does not warrant or guarantee the accuracy, completeness, adequacy, or currency of the information provided, and the content may not reflect all considerations relevant to a particular business, product, or use case.
Unit is a financial technology company and is not a bank. Banking services are provided by Unit's bank partner(s), Members FDIC. Unit provides technology infrastructure and program management services to enable clients to offer financial products. Banking and payment services are provided by Unit's bank partners, Members FDIC, and are subject to applicable program terms, eligibility, and approval requirements.
