Orca

Philippines InstaPay Rail Facts

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.

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 Bangko Sentral ng Pilipinas'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: InstaPay reject and return reason codes: the ACH operating guidelines and PSMB rulebooks that hold them are kept by PPMI and not published, so no code list exists for this rail; the InstaPay ACH operating guidelines are not public, so timeout values, settlement cycle times in the Peso RTGS, the rules for fee return and the entity-at-fault allocation are named here without their contents; BSP Circular No. 1196 (2024) on settlement, Circular Letter CL-2020-036 on PPMI accreditation and the National Payment Systems Act (RA 11127) are scanned images with no text layer and were not read; RA 12010 (AFASA) and RA 11765 were not read directly; liability and consumer-law rest on the BSP circulars that implement them; InstaPay Cash-in, InstaPay QR and the P2B bills payment use case are named but not described use case by use case.