How money moves on this rail, in 12 sourced records: what is final, what can be returned, recalled or refunded, who decides, and what the limits are. A profile belongs to the rulebook, so no reason code list is published on this page.
On a rail fact, every detail line names the section or instrument it rests on and whether that is a rule, a law, operator guidance, or observed practice.
Not yet covered: this directory holds the RTP profile only; RTP reason codes sit in corpus/rtp-return-request and corpus/rtp-reject; TCH's own permitted code lists and the pacs.002 and camt.029 status sets: they sit in the RTP Message Specifications, gated by the RTP Documentation Agreement, which Orca has not accepted (docs/rails/rtp.md, Blocked); the reject codes in corpus/rtp-reject come from public bank and processor pages instead; ISO identifiers for the Request for Payment, Request for Information, Remittance Advice and Payment Acknowledgement; only pacs.008, pacs.002, camt.056 and camt.029 are confirmed by a public TCH document; the payment response time-out that triggers a system cancellation: set in the RTP Technical Specifications and not published; prefunded requirement amounts, per-participant sending limits and TCH origination control values: set per participant and not published; participant eligibility criteria and the general limitation of TCH liability: both sit in the RTP Participation Rules, which have not been read; Regulation E was read through the CFPB's presentation rather than section by section; eCFR refused a plain fetch, so the consumer-law facet caps at medium; Operating Rules editions effective 2026-09-30 and 2026-10-04, which add indirect domestic send and on line originator arrangements, have not been read.