Orca

GCC AFAQ Payment Rejections

27 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 SAMA (rules for Saudi direct participants); GCC central banks via GPC (system)'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: SAMA's code list gives each rejection code a short label and no definition, trigger or handling rule, so the triggers and actions in these records are mostly Orca's reading of the operating rules; the live code dictionary held in the AFAQ Central Component is not published and may differ from SAMA's appendix; which component raises each code (the sending or receiving Regional Payment Gateway, or the Central Component) is not stated per code in any public text; the message type and field that carry a rejection code back to a Saudi participant are set in participant-only format guides and were not consulted; the lists other GCC central banks give their own participants were not read.