Pix vs UPI vs SPEI vs PromptPay: Real-Time Rail Economics Compared
Compare Pix, UPI, SPEI, and PromptPay across confirmation speed, settlement, identifiers, risk controls, and operator trade-offs.
Explore by subject
Choose the country and rail for your customer, then check acceptance, settlement and cross-border requirements in the relevant market guide.
Briefings, grouped by decision
Analytical and comparative pieces on rail economics, design lessons, and emerging infrastructure. Start here before diving into market-specific guides.
Compare Pix, UPI, SPEI, and PromptPay across confirmation speed, settlement, identifiers, risk controls, and operator trade-offs.
Both launched as central-bank-mandated real-time payment systems. Pix hit 160M users in 18 months. CoDi is effectively dead. The delta isn't luck.
Market guides and ecosystem analysis across Asia — from UPI at scale to SEA super-apps and wallet wars.
UPI merchant pricing, access and NPCI infrastructure, including the deferred selected-P2M MDR start and what operators must confirm before implementation.
PayNow Corporate fees by bank, UEN registration, and DBS/OCBC/UOB API paths — sourced, dated pricing for Singapore B2B collections and payouts.
How payments actually work in Japan: JCB and global cards, PayPay and QR wallets, konbini cash, and what cross-border operators need to accept them locally.
Southeast Asia's digital wallet market is fragmenting by country, consolidating by regulation, and being forced open by QRIS and interoperability.
How Thailand's PromptPay became the blueprint for instant payment infrastructure across Southeast Asia, and what other markets can learn from its.
InstaPay vs PESONet for Philippine payouts: real-time low-value vs batch high-value clearing, disbursement-API routing, and EMI vs bank-partner trade-offs.
Pix acceptance in Brazil and the US-Mexico remittance corridor address different operator tasks: domestic acceptance and cross-border transfers.
SEPA rail mechanics, EU regulatory mandates, open banking in the UK, and market guides for Saudi Arabia and East Africa.
SEPA payments explained for operators: SCT, SCT Inst, and SDD Direct Debit, with scheme coverage, timing, fees, and merchant use cases.
Regulation (EU) 2024/886 makes euro PSPs offer instant credit transfers at standard prices with IBAN/name checks. The full operator compliance timeline.
Understand UK commercial VRP, consent limits and provider eligibility. Separate a usable recurring-payment service from EU legislative forecasts.
The cross-market infrastructure layer — subscription rails across A2A networks, B2B receivables, and tokenisation mandates.
PayNow can't pull recurring. UPI AutoPay tripled in one year. Pix Automático launched June 2025. What each market's recurring billing rail delivers.
The SWIFT correspondent chain and its ISO 20022 CBPR+ migration — field-by-field message mapping, investigation and recall messages, account reporting, and payment initiation status.
What a SWIFT payment actually costs — correspondent fees, FX spread, charge options — and when to use SWIFT vs a local rail or platform instead.
Field-by-field mapping of MT103 to ISO 20022 pacs.008 for payment operators: UETR, EndToEndId, party fields, charges, and post-migration investigation flow.
Field-by-field MT103 reference: mandatory/optional status, format specs, and failure modes for fields 20 through 77T, plus MT103 vs MT103+ vs REMIT.
Operator reference for cover payments: MT202 COV and pacs.009 COV, SttlmMtd codes, UETR sharing, reconciliation, and the failure modes that strand funds.
Operator reference for the ISO 20022 camt investigation messages — camt.056, camt.029, camt.110, camt.111 — and how scheme scope changes their use.
Operator reference for camt.052 (intraday report), camt.053 (end-of-day statement), and camt.054 (debit/credit notification): structure and reconciliation use.
pain.001 and pain.002 explained for payment operators: message structure, the pain.002 status-code lifecycle, the pacs.008 handoff, and MT101/CBPR+ migration.
Operator-facing decision frameworks for choosing between PSPs, acquirers, and payment method providers. Archetype-driven, not feature checklists.
Stripe dominates online and SaaS; Square dominates card-present retail and SMB. Here's how to choose based on your business model, not feature checklists.
Compare Adyen and Worldpay on a matched European acquiring profile: channel integration, settlement reporting, contract costs and testing.
Klarna, Afterpay, and Affirm: different merchant fees, consumer networks, and geographic coverage. Operator comparison for checkout BNPL selection.
Not a feature comparison — a decision framework based on operator archetype. Marketplaces, SaaS platforms, enterprise global expanders, and high-volume.
Compare terminal, connectivity, risk and reconciliation paths for card-present and online payments, including offline EMV and store-and-forward modes.
Integration is a one-time project. Running hundreds of live terminals — provisioning, firmware, keys, tamper events, RMA — is a permanent operating discipline.
What a merchant must actually build integrating Pix, UPI, PayNow, PromptPay, and SEPA Instant — and what's portable from one A2A rail to the next.
How Ghana's mobile money and GhIPSS services work, and what merchants should verify about acceptance, licensing, payouts, the e-levy and FX.
TCMB licensing, FAST participation, TROY and instalment rules, with the residence-specific currency conditions foreign operators must check.
Other briefings in this topic
Compare Peru's Plin QR, Yape Empresa and gateway-based Yape online checkout, and ask the right questions about proof of payment, fees and reconciliation.
Online mada payment states, capture, void, refund and bank settlement, with a scoped Moyasar example.
pacs.002 reports a payment instruction's status; pacs.004 returns settled funds. Match each message to the original payment and actual money outcome.
Mastercard Wallet Pay, announced 9 September 2026: the eight products it covers, what was already live, how account tokenization works and what is unannounced.
A fixed euro peg, a mobile-money payout that cannot receive foreign funds directly, and an instant rail that stops at the union border.
Transbank's tariffs were deregulated in January 2026, and Chile now has a formal cross-border acquiring regime. What changed for operators.
How Pix Automático actually behaves in production — mandate states, the two retry obligations, MED refund tracks, and the identifiers you reconcile against.
Regulation E on the sending side, MTSS and RDA on the receiving side. What each actually requires, and why UPI is not a US–India remittance rail.
How Colombia treats foreign capital in payments: SFC ownership rules, SEDPE capital, the acquiring entry route, and FX repatriation mechanics.
How Pakistan's payment stack works for operators: SBP EMI/PSO capital rules, 1LINK/PayPak card acquiring, foreign ownership, and profit repatriation.
How operators actually accept payments in Egypt: routing across cards, Meeza, InstaPay, Fawry, wallets, and cash — and reconciling the lot.
Operator guide to Australia's A2A rails: the NPP real-time rail, PayTo (the NPP Mandated Payments Service), centrally-held mandates, and BECS migration.
A KPI scorecard for SCT Inst health: initiation, timeouts, rejections, recalls, reconciliation, and VoP — with operator-set targets and fixed scheme deadlines.
Operator guide to Mexico's SPEI rail: Banxico-operated real-time A2A transfers, CLABE routing, irrevocability, refunds as new transfers, and PSP due diligence.
Operator runbook for SCT Inst rejections, timeouts, returns, and recalls — pacs.002 status handling, action per failure class, and bank escalation checklists.
SEPA R-transaction types and selected reason codes across SCT, SCT Inst, and SDD, with scheme-specific context and operator next steps.
How foreign operators handle local acquiring in South Korea — the PG and VAN requirements, KakaoPay/Naver Pay, FSC-regulated MDR, data residency.
How foreign operators accept Alipay, WeChat Pay, and UnionPay. PBOC licensing realities, CIPS for B2B CNY settlement, and 2024–2026 regulatory changes.
An operator guide to Indonesia's QRIS and wallets, local acquiring through licensed PSPs, BI-FAST payouts, and QRIS merchant fees effective 1 October 2026.
Stack map
Check these dimensions against the target customer, transaction type and provider route you can actually use.
Rail landscape
Which rails serve your customer segment, and who operates them?
Regulatory model
Check the operating model, oversight, access conditions and applicable pricing rules.
Acceptance economics
Compare acceptance fees, conversion costs and settlement terms for the intended use case.
Integration path
Direct API to the rail, local acquirer required, or aggregator sufficient?
Cross-border settlement
Can money leave via the local rail, or does it require SWIFT or a bilateral linkage?
Consumer context
Mobile-first, card-habituated, or cash-to-digital — determines which product assumption survives the market.
Reference
A real-time payment rail moves money between accounts quickly, often around the clock — examples include UPI, Pix, PayNow and Faster Payments. It differs from a card network in initiation, access and dispute processes. Merchant prices are not uniformly zero: Pix merchant acceptance is market-priced, and India's selected UPI P2M payments above ₹2,000 gain a 0.4% fee from a post-Diwali date still to be notified with caps and exemptions. Operators need each rail's current fee and refund rules.
Regulation, consumer adoption and distribution all shape which payment method dominates. India's 2020 UPI zero-MDR rule helped merchant adoption, but selected merchant payments gain a fee from a post-Diwali date still to be notified. Brazil's Pix has a different model: P2P is free while merchant pricing is market-based. Operators entering a market should identify the dominant rail and verify the current commercial and regulatory terms for their own use case.
Start with the payment methods relevant to your target customer segment and transaction type. Check acceptance, provider access, pricing, refunds and reconciliation for that use case. Use the market guide to plan coverage rather than assuming national adoption establishes the right mix for every merchant.
A merchant accepting international card payments is primarily using Visa or Mastercard's cross-border acquiring rules — the card scheme routes the transaction globally, the merchant's acquirer converts currency, and the issuer pays in the cardholder's home currency. For bank transfer payments (SWIFT), the payment travels through correspondent bank chains that add cost and delay. For digital wallets (Alipay, WeChat Pay), the operator typically needs a local aggregator licensed to settle cross-border wallet transactions. Distinguish bilateral real-time rail linkages such as UPI-PayNow from the multilateral Nexus framework. Verify the participants, provider, product and availability of any proposed corridor before relying on it as an alternative route.
Project Nexus is a BIS Innovation Hub initiative designed to interconnect domestic instant payment systems through a multilateral framework, rather than a separate bilateral connection for every pair of systems. The bilateral UPI-PayNow connection and Nexus are distinct: an existing bilateral linkage does not establish that Nexus is operational on that corridor. Assess the available provider, participants and payment product for your intended route. For operators, Nexus matters because it is the emerging architecture for low-cost, real-time cross-border settlement — and it may eventually make SWIFT correspondent banking optional for retail payment corridors where Nexus has coverage.
UPI timing update (27 October 2026): NPCI’s 13 October notice deferred selected-merchant MDR until after Diwali, with the date to be notified separately. The prior 15 October start does not apply.
Global payments is a patchwork of national rails, regional schemes, and private networks. Real-time A2A networks like UPI, Pix, PayNow and PromptPay carry huge volume, but their merchant fees differ by rail and transaction category. India’s selected UPI merchant payments above ₹2,000 gain a 0.4% fee from a post-Diwali date still to be notified, subject to caps and exemptions. Cards remain widely accepted across markets; local-rail coverage and economics still matter for operators entering each market.
For operators, the practical implication is that payment localisation is not optional — it is the margin. A merchant entering India should assess UPI coverage against its target customers rather than assuming international-card acceptance is sufficient. A subscription business in Brazil should assess Pix Automático alongside cards, including customer adoption, mandate setup, payment recovery and reconciliation. The cross-border layer adds another dimension: SWIFT correspondent chains, FX timing risk, and memo truncation remain the default for B2B flows, while bilateral real-time linkages and stablecoin routes need corridor-specific checks of access, cost and recipient availability.
The briefings in this topic are the operator’s reference for understanding which rail matters in each market, what it costs to connect, and what regulatory forces will reshape the landscape over the next 12–24 months.