Reading List
Real-Time Rails: The Operator's Path Reading List
Real-time account-to-account rails are the most-written-about and least-operationally-documented part of payments. The coverage is nearly all adoption statistics; almost none of it tells you what changes in your stack when a payment is push rather than pull, final rather than reversible, and confirmed asynchronously rather than in the authorisation response. This list runs economics first, then the acceptance architecture that applies to all of them, then six national rails in the depth an integration actually needs — and closes on the rail that failed, because the contrast explains more about rail design than any of the successes do individually.
Who this is for
Payments engineers and product teams integrating A2A acceptance, operators expanding into markets where the domestic rail outperforms cards, and anyone modelling the cost of moving volume off card rails.
Reading order
The full reading list
-
Pix vs UPI vs SPEI vs PromptPay: Real-Time Rail Economics Compared
Start with the economics. Pix, UPI, SPEI and PromptPay compared on the axes that decide whether a rail is worth integrating — MDR model, settlement window, identifier scheme, and who actually bears the cost.
12 min read
-
A2A Merchant Acceptance Architecture: What to Build, What Carries Over
The architecture that applies to all of them. Push versus pull and what it changes, asynchronous confirmation (pending is not failed), the idempotency gap in webhook retries, finality, refund and return mechanics by rail, and the portability map for what carries across markets.
16 min read
-
Brazil's PIX: What Payment Operators Entering LatAm Must Understand
Pix is the reference implementation everyone else is measured against. What a central-bank-operated rail with mandated participation does to acceptance economics, and what it means for an operator entering LatAm.
8 min read
-
India's UPI at Scale: Infrastructure Realities for Payment Operators
UPI at scale. The infrastructure realities behind the transaction counts — VPA addressing, the collect-request model and its consent step, and why zero-MDR changes the business case rather than removing it.
8 min read
-
SPEI Mexico: An Operator Guide to the Payment Rail
SPEI, and the contrast with Pix that matters: a capable rail whose adoption curve looks nothing like Brazil's. Operating hours, CLABE addressing, and the practical integration path.
13 min read
-
PayNow Corporate Fees, UEN Registration, and Bank APIs in Singapore
PayNow Corporate, in the depth a business integration needs — UEN aliasing, per-bank API differences, FAST as the underlying rail, and the reconciliation reference that carries through to the recipient bank record.
17 min read
-
PayTo and the NPP: An Operator Guide to Australia's A2A Rails
PayTo is the most interesting rail on this list for subscription businesses, because it is the one that solved the pull problem directly: a mandate layer built on top of the NPP rather than bolted beside it.
14 min read
-
Vietnam's Payment Rails: VietQR, NAPAS 247, and What Operators Need to Know
VietQR and NAPAS 247, including the part most rail guides skip — that a push-only rail leaves recurring billing to proprietary wallet schemes, and what the routing mandate does and does not cover for card-not-present e-commerce.
14 min read
-
Why CoDi Failed and Pix Didn't: Lessons for New Rail Launches
Finish with the failure. CoDi and Pix launched into comparable markets with comparable technology and diverged completely. The reasons are structural and they are the best available checklist for judging any rail launch you are asked to bet on.
7 min read