Deep Dive — Emerging-Market Rails
UPI, PIX, M-Pesa, DuitNow, PromptPay, RuPay, Mada — what each rail actually does, who runs it, the quirks that bite you in production, and how crypto on/off-ramps interface.
Why this is the primary deep-dive
The role is explicit: "high-growth and emerging markets." If you can hold a 10-minute conversation about UPI and PIX and one Southeast-Asian QR rail, you outrun 80% of candidates. The interviewer is checking three things:
- Do you know who runs the rail (regulator, network operator)?
- Do you know the flow (initiation, settlement, dispute)?
- Do you know the production gotchas (recall windows, mandate UX, KYC overlay)?
India — UPI
UPI (Unified Payments Interface) is operated by NPCI (National Payments Corporation of India) under RBI. It is the dominant retail rail in India — >10B txns/month and counting.
The primitives
| Term | Meaning |
|---|---|
| VPA | Virtual Payment Address — name@bank (e.g. chris@okhdfcbank). Human-readable identifier for a bank account. |
| PSP app | The consumer-facing app — GPay, PhonePe, Paytm, BHIM. PSPs sit between user and NPCI. |
| P2P | Person-to-person — typically free, retail. |
| P2M | Person-to-merchant — historically MDR-zero (no merchant discount rate) by regulatory mandate. RBI subsidises. |
| UPI AutoPay | Recurring mandate framework — the way to do subscriptions, SIP investments, or recurring crypto buys. |
| UPI Lite | Small-value (currently up to ₹500/txn, ₹2000 wallet) on-device wallet for instant offline-feel txns; no PIN required per txn. |
| UPI Intent | App-to-app deep-link flow — your app hands off to the user's UPI PSP app for PIN entry, then returns. |
| QR (intent or collect) | QR codes can be static (intent — user scans, then PINs) or dynamic (collect request — server-initiated, user approves). |
The flow — UPI Intent payment
- User on the company app taps "Deposit via UPI."
- the company backend creates a UPI collect or intent transaction; gets a deep-link.
- User's device opens their PSP app (GPay etc.).
- User enters UPI PIN.
- PSP forwards to NPCI; NPCI routes to user's bank for debit.
- User's bank debits, NPCI credits the company's bank, the company backend gets a callback.
- the company credits the customer's balance.
Total time: typically <10 seconds end-to-end, with seconds-grade settlement to the company's nostro.
Production gotchas
- Crypto + UPI is regulator-sensitive. NPCI has historically been cool on direct crypto on-ramp via UPI. Most exchanges have used intermediate fiat partners or B2B rails. Stay current on the policy posture.
- AutoPay mandate UX is bumpy. Setting up recurring needs explicit user approval each time mandate caps change.
- Reconciliation is per-PSP. NPCI gives you final state, but you'll see mid-flight states ("pending") that the PSP didn't yet confirm.
- VPA vs account-number resolution — a VPA can change without warning if user moves PSPs. Don't store VPAs as long-lived identifiers.
India — IMPS, NEFT, IPI/FTS
- IMPS (Immediate Payment Service) — older instant rail, account-and-IFSC based, 24/7. Used heavily for bank-to-bank transfers where UPI isn't ideal (e.g. higher amounts, business contexts).
- NEFT (National Electronic Funds Transfer) — RBI-operated, batched, half-hourly settlement windows. Lower cost, higher latency than UPI/IMPS.
- RTGS — real-time gross settlement for high-value (₹2 lakh+) bank-to-bank.
- IPI / FTS — newer instant payment / fund-transfer specs that may show up in JDs; treat as adjacent to IMPS at the interview level unless you've shipped them.
Brazil — PIX
PIX is operated by BACEN (Banco Central do Brasil) — note this is unusual: the central bank runs the rail directly, not a private network. Launched 2020, now >90% of Brazilian adults use it.
The primitives
| Term | Meaning |
|---|---|
| PIX Key | An alias — CPF (tax ID), email, phone, or random UUID — pointing at an account. |
| PIX Copia e Cola | Copy-paste payment code — a long string the user pastes into their bank app. |
| PIX QR (static / dynamic) | Static for small-merchant repeat use; dynamic for one-shot, amount-locked. |
| MED (Mecanismo Especial de Devolução) | Special return mechanism — fraud-recovery flow. 80 calendar days to file; recipient bank has 7 days to hold/return. |
| MEC | Operational error return — separate from MED, for clerical/duplicate errors. |
| PIX Saque / Troco | PIX cash-withdrawal at merchants; cash-back style. |
| PIX Agendado | Scheduled PIX — future-dated. |
| PIX Automático (rolling out) | Recurring-payment / mandate equivalent — competes with card-on-file for subscriptions. |
Production gotchas
- PIX is free for P2P. Merchants pay (typically) — but it's still ~10x cheaper than card. Cost-stack math for a Brazilian on-ramp has to include PIX, or you're over-paying.
- MED returns are growing. Fraud-pattern: scammed customer pushes PIX, then files MED. As recipient, you may face a hold even though the funds settled. Plan for it.
- BACEN throttling. Each participant has rate ceilings. Burst behavior gets capped.
- Idempotency at the PIX message level — duplicate end-to-end IDs are rejected, so client-side idempotency keys must align.
EU — SEPA Instant (SCT Inst), TIPS
SEPA Instant runs across most EU/EEA banks; settlement under ~10 seconds, 24/7, up to €100,000 per txn. TIPS is the ECB-operated settlement service for SEPA Instant — most banks use it. Why a Payments PM cares:
- It's the EU rail you'd default to for instant fiat deposit/withdrawal across the Eurozone.
- Coverage isn't 100% — your acquiring / banking partner must support it.
- Verification of Payee (VoP) is an upcoming SEPA mandate (October 2025 onwards) that adds a payee-name check on initiation, with PM-relevant UX implications.
UK — FPS (Faster Payments) and Open Banking
FPS launched 2008 — UK's instant rail. Almost all retail UK bank-to-bank transfers ride it. For a crypto exchange, FPS is the floor for GBP in/out.
Open Banking in the UK (under FCA/PSD2 in EU, PSR in UK) is the framework letting third parties initiate payments and read account data with user consent. PIS (Payment Initiation Services) lets you initiate a bank push from inside your app — bypasses card cost, lower fraud, but UX is bumpy (user redirects to their bank). Used heavily by crypto on-ramp aggregators in UK.
SE Asia — PromptPay, PayNow, DuitNow, GCash, Maya, VietQR
| Rail | Country | Operator | Note |
|---|---|---|---|
| PromptPay | Thailand | BoT / ITMX | National-ID or mobile-aliased; QR-driven |
| PayNow | Singapore | MAS / ABS | NRIC / mobile aliased; SGQR for QR; cross-border to PromptPay live |
| DuitNow | Malaysia | PayNet / BNM | NRIC / mobile aliased; DuitNow QR consolidated standard |
| GCash / Maya | Philippines | BSP-regulated EMIs | Mobile-wallet first; de facto bank account; InstaPay underlying |
| VietQR / NAPAS 247 | Vietnam | NAPAS, SBV | QR-driven; bank-to-bank via NAPAS 247 |
The pattern: regulator-coordinated, QR-driven, mobile-first. ASEAN has live cross-border QR linkages (Thailand ↔ Singapore, etc.) — material for cross-border PM design.
Africa — M-Pesa, MoMo, NIP
- M-Pesa (Kenya, Tanzania, others, operated by Safaricom/Vodacom) — mobile-money pioneer, USSD-driven, dominant in Kenya. STK push for payment confirmation.
- MoMo (MTN Mobile Money) — across multiple African markets — Ghana, Uganda, Cameroon, Côte d'Ivoire, others.
- NIP (Nigeria Inter-Bank Settlement System Instant Payments) — instant bank-to-bank in Nigeria, operated by NIBSS.
- Verve — Nigeria's local card scheme.
USSD is still material — feature-phone users on flaky networks. If you're shipping into Nigeria or Kenya, USSD fallback is not optional.
Local card schemes
| Scheme | Country | Note |
|---|---|---|
| RuPay | India | NPCI-operated; mandated for some segments |
| Elo | Brazil | Operated by major Brazilian banks; significant share |
| Hipercard | Brazil | Itaú-backed; less dominant than Elo |
| Mir | Russia | Sanctioned context; relevant for compliance, not for new launches |
| Mada | Saudi Arabia | SAMA-mandated; most domestic txns route via Mada even on Visa/MC dual-badged cards |
| KNET | Kuwait | Domestic debit network |
| Troy | Turkey | BKM-operated |
Why this matters: your acquirer may not support all of them. Mada is a common stumbling block — international acquirers often can't route Mada domestic, you need a local sponsor bank.
Open Banking frameworks
- UK Open Banking (under PSD2 and now UK PSR) — 9 main banks mandated; mature ecosystem.
- EU PSD2 / PSD3 — PIS and AIS providers across EU.
- Brazil Open Finance — BACEN-mandated; phased rollout from 2021; one of the most ambitious globally.
- India Account Aggregator (AA) — RBI framework; consent-based data sharing; not payment initiation (yet).
- Australia CDR (Consumer Data Right) — data first, payments later.
For a crypto exchange: Open Banking PIS rails reduce card-cost burden and lift AAR (no issuer step-up) but at the cost of UX redirect friction. Tradeoff is per-market.
Where crypto on/off-ramps plug in
Tying it together — how each rail interfaces with the crypto side of a crypto exchange:
| Flow | Typical rail choice | Why |
|---|---|---|
| BR consumer on-ramp | PIX | Cheap, instant, dominant; cards as fallback |
| IN consumer on-ramp | UPI (with partner) or IMPS | Regulatory constraints; partner-mediated |
| UK consumer on-ramp | FPS via Open Banking PIS, or card | FPS dominant for higher-value |
| EU consumer on-ramp | SEPA Instant where supported, SEPA CT, card | SCT Inst best UX where available |
| PH consumer on-ramp | GCash / Maya / InstaPay | Wallet-first market |
| Cross-border B2B settlement | USDC / USDT | Stablecoins act as a settlement rail in themselves |
Stablecoin settlement is increasingly an option between the company and a banking partner — a real PM design space.