Orca

RTP Payment Rejects

59 codes that cover most of what an originator sees. Each one carries the decision: retry or stop, how long the receiving institution has to send it, what the guidance rests on, and when it was last checked.

What the tier labels mean, and how far this page has been checked
Draft
An agent wrote it from published material and nobody has checked it. Use it as a lead to confirm, never on its own as the basis for a retry, a return, a deadline or a compliance decision.
Corroborated
A validator found the same answer in one or more named public sources; the class in brackets says how strong they are. "Secondary sources only" means bank, processor or industry guides and nothing from the operator or regulator. Corroborated does not mean checked against the governing rulebook, so confirm before you act.
Verified
A person checked it against The Clearing House's own current text and recorded the edition and date. The strongest tier here, and still reference material, not legal or compliance advice.

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.

Known gaps in this build

Not yet covered: the reject code list here comes from public bank and processor pages; TCH's own list, in the RTP Technical Specifications, was not consulted because Orca has not accepted the terms it carries; 9901, 9909, 9910, 9954, FF02, SL03, FRTR, UPAY, BLKD, INSF, AC10, BE13, FF03, T104 and the codes seen only on pages that mix RTP with FedNow: the public sources either disagree on them or only one family lists them as RTP reject codes; which side sends most ISO codes, the receiving participant or the RTP System: no public source read says, so both are linked; the receiving participant response time-out figure: set in the RTP Technical Specifications and not published; the pacs.002 status codes (ACTC, RJCT, ACWP, RCVD) and the reject reasons of a request for payment response (pain.014).