RTP
FPSThe Clearing House Real-Time Payments - the first modern instant payment system in the US (launched Nov 2017, 3 years before FedNow). 24/7/365. ISO 20022 native. Operated by TCH (same operator as CHIPS). Max $10M per transaction. Reaches 72%+ of US DDAs. From 4 October 2026 the RTP Operating Rules permit One-Leg-Out (OLO) payments, the U.S. leg of cross-border payments, for participants that opt into an early-adopter period; from 31 March 2028 all participants must receive inbound OLO payments. The Clearing House also plans an On-Chain Money network for tokenized deposits, powered by Quant, with connectivity to RTP and CHIPS, expected to be available to participating institutions in the first half of 2027.
ClearingPost does not assess whether RTP is running normally.
Next
All 1 upcoming →Dated items ClearingPost holds, each with its source and whether the date is confirmed
No supported upcoming items in ClearingPost's records for RTP.
Later: 1 dated item after 13 Nov 2027
Changed
All recorded changes →Material, sourced changes ClearingPost recorded; corrections to its own record are labelled as such
- Data updateRTP participant count updated to over 1,417 participants (as of October 2026) · RTP average daily value increased to $7B (as of October 2026)recorded 4 Nov 2026 · RTP Network | The Clearing House
- 1,280+ participants (as of 2026-06-30) changed to over 1,378 participants (as of 2026-09-30)recorded 12 Oct 2026 · The Clearing House - RTP networksource ↗
- Data updateRTP headline volume updated to 150 million (Q3 2026) · RTP average daily value increased to $6.9B (September 2026) · RTP participant count updated to Over 1,378 (September 2026)recorded 8 Oct 2026 · The Clearing House - RTP Network
Compendium of RTP Rule Change Summaries, section 1 'Summary of RTP Rule Changes - Effective October 4, 2026': the edition (i) supports One Leg Out (OLO) Payments on the RTP network, (ii) modifies rules on Requests for Payment that are RTP/Zelle Messages, and (iii) makes clarifying, conforming and cleanup changes. Section I.A adds ten defined terms: Domestic Payee, Domestic Payer, Foreign Payee, Foreign Payer, OLO Beneficiary, OLO Intermediary Institution, OLO Originator, OLO Payment, Swift, UETR. Section II.B adds an exception to the prohibition on RTP Payments involving a Foreign Financial Institution to permit OLO Payments and returns of funds from them. Section II.E is renamed 'Limitations on Foreign Payments' from 'Prohibition on Foreign Payments'. New Section III.K opens an optional early-adopter period on 4 October 2026, during which Participants may send OLO Payments only to other participating early adopters; from the general availability date of 31 March 2028 every Receiving Participant must receive inbound OLO Payments except where rejection is permitted. Section III.H requires OLO Payment Messages to use the OLO local instrument code, to identify the OLO parties and the OLO Originator or Foreign Payer address, and where provided to carry date, city and country of birth, legal entity identifier, and the Swift UETR. Section II.G extends fraud reporting to fraud affecting OLO Originators and Foreign Payers. Section V.E.2 lets a Receiving Participant that responded 'accept without posting' delay its funds-availability decision beyond 11:59 p.m. the next business day when it needs information from a third party to complete a legal or compliance review. Section VII.B.2.d disapplies the Request for Payment warranty to Requests for Payment that are RTP/Zelle Messages. Changes to Section III.I.2 (Minimum Requirements for OBO Payments; Requirements for Receiving Participants) take effect 31 March 2028.
took effect 4 Oct 2026 · The Clearing Housesource ↗Upcoming edition listed by The Clearing House as 'Upcoming RTP Operating Rules: Effective 09-30-2026' and published at https://www.theclearinghouse.org/-/media/New/TCH/Documents/Payment-Systems/RTP/RTP-Operating-Rules-Effective-September-30-2026.pdf. The cover reads 'RTP Operating Rules, September 30, 2026'. The document's Revision History states the edition was initially published in December 2025 following approval of changes regarding Indirect Domestic Send (IDS) Payments. The Revision History states an updated version was published in April 2026 to incorporate additional changes related to the Liquidity Management Transfer (LMT) Service and to make formatting enhancements. The Revision History records that the LMT Service changes were approved on 13 April 2026 and take effect on 1 June 2026. Supersedes the edition effective 1 June 2026.
took effect 30 Sep 2026 · The Clearing Housesource ↗
Rules & documents
All 4 documents ↓The rulebooks, operating rules and standards documents ClearingPost holds for RTP, each with its current version, or the latest published one when none is in force yet
- RTP System Operating RulesThe Clearing House · Effective 10-04-2026 · Effective Oct 4, 2026 · Authoritative (T1)
- RTP Participation RulesThe Clearing House · Effective 09-30-2026 · Effective Sep 30, 2026 · Authoritative (T1)
- RTP Customer Display Requirements for Credit Transfers and Requests for PaymentThe Clearing House · 5.0 (June 2026) · Authoritative (T1)
Sources No status page recorded · 9 of 17 fields carry a source and a recorded date · latest sourced entry recorded 6 Nov 2026 · evidence details ↓
Record · RTP
The Clearing House publishes RTP throughput as a quarterly payment count and a daily average value, not as a daily transaction count. The daily transaction figure held here is a desk derivation: the published Q3 2026 count of 150 million payments divided by the 92 days of the quarter, which gives about 1.63 million payments a day. Use the quarterly count for any comparison with operator-published figures.
Compendium of RTP Rule Change Summaries, section 1 'Summary of RTP Rule Changes - Effective October 4, 2026': the edition (i) supports One Leg Out (OLO) Payments on the RTP network, (ii) modifies rules on Requests for Payment that are RTP/Zelle Messages, and (iii) makes clarifying, conforming and cleanup changes. Section I.A adds ten defined terms: Domestic Payee, Domestic Payer, Foreign Payee, Foreign Payer, OLO Beneficiary, OLO Intermediary Institution, OLO Originator, OLO Payment, Swift, UETR. Section II.B adds an exception to the prohibition on RTP Payments involving a Foreign Financial Institution to permit OLO Payments and returns of funds from them. Section II.E is renamed 'Limitations on Foreign Payments' from 'Prohibition on Foreign Payments'. New Section III.K opens an optional early-adopter period on 4 October 2026, during which Participants may send OLO Payments only to other participating early adopters; from the general availability date of 31 March 2028 every Receiving Participant must receive inbound OLO Payments except where rejection is permitted. Section III.H requires OLO Payment Messages to use the OLO local instrument code, to identify the OLO parties and the OLO Originator or Foreign Payer address, and where provided to carry date, city and country of birth, legal entity identifier, and the Swift UETR. Section II.G extends fraud reporting to fraud affecting OLO Originators and Foreign Payers. Section V.E.2 lets a Receiving Participant that responded 'accept without posting' delay its funds-availability decision beyond 11:59 p.m. the next business day when it needs information from a third party to complete a legal or compliance review. Section VII.B.2.d disapplies the Request for Payment warranty to Requests for Payment that are RTP/Zelle Messages. Changes to Section III.I.2 (Minimum Requirements for OBO Payments; Requirements for Receiving Participants) take effect 31 March 2028.
Edition effective 30 September 2026, listed as the current RTP Participation Rules in the TCH document library on 12 October 2026 and published at https://www.theclearinghouse.org/-/media/New/TCH/Documents/Payment-Systems/RTP/RTP-Participation-Rules-Effective-September-30-2026.pdf. Section 2 of The Clearing House's Compendium of RTP Rule Change Summaries states that the PayCo Board approved changes to the RTP Participation and Operating Rules to permit Indirect Domestic Send (IDS) Payments on the RTP network and to make other clarifying or clean-up changes, taking effect on September 30, 2026. In the Participation Rules, Section II.B (Obligations and Options for Participation) is renamed and adds language permitting a Participant to be an IDS Originating Institution as long as it is not the Sending Participant of the IDS Payment. The summary also records a clarifying change to the definition of depository institution in Participation Rule I.B. Supersedes the edition effective 1 June 2026, whose Participation Rules change revised the definition of Funding Participant in Rule II.A.1 to reflect that a Funding Participant may use the FedNow Liquidity Management Transfer Service to fund the Prefunded Balance Account.
Version control history of RTP Customer Display Requirements 5.0 (RTP Version 5.0, June 2026) records two June 2026 changes: the 1 July 2026 compliance date option was eliminated, and truncation guidance for Name fields was added. The preceding February 2026 update had offered Receiving Participants two implementation approaches for the pacs.008 credit transfer display requirements effective 1 July 2026, the June 2025 'Interim Approach' or the 'Final Approach' in Section 3.1, with that optionality permitted only through 31 January 2027 and all Participants required to comply with the Final Approach as of 1 February 2027. Section 3 of version 5.0 is titled 'Credit Transfer - pacs.008.001.08 (Effective February 1, 2027)'. The requirements do not apply to RTP/Zelle Payment Messages, which are subject to separate display requirements under the Zelle Rules or Early Warning Services requirements.
Version 5.0 of the RTP message specifications, whose change history begins with an August 2024 entry, revised in October 2026: the revision adds product usage requiring an address when Ultimate Debtor is present (Index 2.732), clarifies when the Connectivity Status Broadcast (960) is sent and adds the purpose code TRAD. The June 2026 revision extended the temporary exception that lets Sending Participants include a code in the Debtor name field for instant bank account validation; the specification permits such a code through 31 January 2027.
Operations · RTP
Operational monitoring: not configured. ClearingPost does not monitor operational sources for this system and does not assess its current service condition.
Operations lists the systems ClearingPost monitors and the operational events it has recorded.
Intelligence for RTP (14)
Coverage whose headline or summary names RTP, or names its operator or country together with its system type. Each item quotes that evidence and says whether the source is the RTP operator or external.
Wider coverage that mentions RTP (3)
These articles mention RTP in their text but not in their headline or summary, so they are listed as context rather than as RTP intelligence.