Real-Time Payments by Country: A 2026 Global Guide

Real-time payments have gone from novelty to expectation. Over 80 countries now operate domestic instant payment systems, processing transactions in seconds rather than the one-to-three business days that legacy batch networks require. For platforms building cross-border payout products — payroll systems paying contractors in Brazil, marketplaces settling sellers in India, fintechs moving funds across Southeast Asia — understanding which real-time rails exist in each corridor is a core infrastructure decision.

This guide breaks down the major real-time payment networks by country, compares their settlement speeds and transaction limits, and explains what these systems mean for cross-border payments. Whether you are evaluating local payment rails vs SWIFT or designing a multi-rail payment orchestration strategy, this is the reference you need.

Real-time payments are electronic fund transfers that are initiated, cleared, and settled within seconds — typically under 10 — with 24/7/365 availability. Unlike batch-processed systems such as traditional ACH, real-time payment networks process each transaction individually and provide immediate confirmation to both sender and receiver. The funds become available to the recipient instantly, with no holds or pending periods.

Three characteristics define a true real-time payment system: **instant clearing** (the payment instruction is validated and confirmed in seconds), **immediate settlement** (funds move between institutions without delay), and **always-on availability** (the network operates continuously, including weekends and holidays). Systems that offer same-day processing but not instant settlement — like Same-Day ACH — are faster than legacy batch networks but do not qualify as real-time.

Each country's real-time payment network reflects local regulatory priorities, banking infrastructure, and adoption patterns. Below are the systems that matter most for cross-border payment platforms.

UPI is the largest real-time payment system in the world by transaction volume. Operated by the National Payments Corporation of India (NPCI), UPI processes over 16 billion transactions per month. Settlement is instant and 24/7, with a per-transaction limit of ₹100,000 (approximately $1,200 USD) for standard transfers. The IMF has recognized UPI as accounting for roughly 49% of global real-time transactions. India's RBI has been actively linking UPI to other real-time systems, with live connections to Singapore's PayNow and pilots with several other markets.

PIX, launched by the Central Bank of Brazil in November 2020, is one of the fastest-adopted real-time payment systems in history. Within three years, PIX reached over 4 billion transactions per month and roughly 160 million registered users. Settlement is under 10 seconds, 24/7/365, with no hard per-transaction limit for individuals. PIX has effectively replaced older systems like TED and DOC for most use cases. Routefusion uses PIX as the last-mile delivery mechanism for cross-border payouts to Brazil, settling with recipients in seconds rather than the two to three days SWIFT requires.

The US operates two competing real-time payment networks. The **RTP network**, launched in 2017 by The Clearing House, reaches approximately 71% of US demand deposit accounts with a $1 million per-transaction limit. The **FedNow Service**, launched by the Federal Reserve in July 2023, has a default limit of $500,000 (configurable up to $1 million). Both settle instantly, operate 24/7, and support ISO 20022 messaging. For cross-border platforms, these rails are most relevant for inbound collection — gathering funds from US businesses before disbursing internationally through local payment rails in destination countries.

The UK's Faster Payments Service, launched in 2008, is one of the longest-running real-time payment systems globally. Operated by Pay.UK, FPS processes payments in near-real-time (typically under two minutes), operates 24/7, and has a per-transaction limit of £1 million. FPS handles over 4 billion transactions per year. The New Payments Architecture (NPA) initiative is modernizing FPS onto ISO 20022 messaging. For cross-border use cases, FPS is the standard last-mile rail for GBP payouts.

SEPA Instant covers 36 European countries with settlement in under 10 seconds, 24/7 availability, and a per-transaction limit of €100,000. A critical development: the EU Instant Payments Regulation, adopted in 2024, mandates that all eurozone payment service providers must send and receive instant payments by late 2025. This transforms SEPA Instant from optional overlay to baseline capability — making it the default rail for EUR-denominated payouts.

Mexico's SPEI (Sistema de Pagos Electrónicos Interbancarios), operated by Banco de México, processes interbank transfers in under 30 seconds during extended hours (6 AM to 5:30 PM on business days, with 24/7 expansion planned). SPEI handles both low-value and high-value transfers with no hard per-transaction cap. For the USD→MXN corridor — one of the highest-volume remittance corridors globally — SPEI is the critical last-mile rail. Platforms using Routefusion's cross-border payments API settle payouts to Mexico via SPEI in seconds.

Australia's NPP, launched in 2018, provides instant settlement 24/7 through its consumer-facing PayID service. Transactions settle in under a minute with a per-transaction limit of AUD $1 million for most participating banks. NPP uses ISO 20022 messaging natively, supporting richer payment data than legacy systems.

Southeast Asia has seen rapid real-time payments adoption. **Singapore's PayNow** settles in seconds with a S$200,000 limit. **Thailand's PromptPay** has over 70 million registered IDs in a country of 72 million, with no per-transaction limit for bank-initiated transfers. **Malaysia's DuitNow** provides instant interbank transfers 24/7. **The Philippines' InstaPay** settles in seconds with a ₱50,000 limit. ASEAN nations are actively linking these systems — the PayNow-PromptPay connection went live in 2021, with additional bilateral linkages rolling out.

Nigeria's NIP system, operated by NIBSS, is Africa's largest real-time payment network — processing over 1 billion transactions per quarter. NIP settles in seconds, operates 24/7, and is the primary rail for NGN payouts. Combined with stablecoin settlement for the cross-border leg (USD→USDC→NGN), NIP enables fast, cost-effective end-to-end payouts to Nigeria.

• **UPI (India)** — Settlement: under 10 sec | Limit: ~$1,200 | Hours: 24/7 | Messaging: proprietary (ISO 20022 planned)
• **PIX (Brazil)** — Settlement: under 10 sec | Limit: no hard cap | Hours: 24/7 | Messaging: ISO 20022
• **RTP (US)** — Settlement: seconds | Limit: $1,000,000 | Hours: 24/7 | Messaging: ISO 20022
• **FedNow (US)** — Settlement: seconds | Limit: $500,000 default | Hours: 24/7 | Messaging: ISO 20022
• **Faster Payments (UK)** — Settlement: under 2 min | Limit: £1,000,000 | Hours: 24/7 | Messaging: ISO 8583 (migrating)
• **SEPA Instant (Europe)** — Settlement: under 10 sec | Limit: €100,000 | Hours: 24/7 | Messaging: ISO 20022
• **SPEI (Mexico)** — Settlement: under 30 sec | Limit: no hard cap | Hours: extended (expanding) | Messaging: proprietary
• **NPP (Australia)** — Settlement: under 1 min | Limit: AUD $1,000,000 | Hours: 24/7 | Messaging: ISO 20022
• **PromptPay (Thailand)** — Settlement: seconds | Limit: no cap (bank-initiated) | Hours: 24/7 | Messaging: ISO 20022
• **NIP (Nigeria)** — Settlement: seconds | Limit: ~$6,200 (NGN 10M) | Hours: 24/7 | Messaging: ISO 8583

Two patterns stand out. First, ISO 20022 is becoming the global messaging standard — networks that haven't adopted it (Faster Payments, NIP) have migration programs underway. This convergence improves interoperability across borders. Second, transaction limits vary dramatically. UPI's ~$1,200 cap works for individual contractor payments but not bulk B2B transfers, while RTP's $1 million limit supports enterprise-scale transactions. Platforms building multi-rail payment strategies need to factor these limits into routing logic.

Real-time payment systems are domestic networks. UPI moves money between Indian banks. PIX moves money between Brazilian banks. Neither system moves money from a US business to a Brazilian freelancer on its own. Cross-border real-time payments require stitching together multiple systems.

The dominant model works in three stages. First, the sending platform initiates the payment through an API. Second, the cross-border provider handles FX conversion, compliance screening, and routing to a local partner in the destination country. Third, the local partner executes last-mile delivery using the destination country's real-time rail — PIX in Brazil, UPI in India, SPEI in Mexico. The recipient sees funds in seconds once the local leg executes, even though the end-to-end orchestration may take slightly longer.

A newer model is emerging: direct bilateral linkages between real-time systems. The BIS Innovation Hub's Project Nexus aims to connect multiple domestic real-time networks through a common gateway. Singapore-Thailand (PayNow-PromptPay) and Singapore-India (PayNow-UPI) linkages are already live. However, these remain limited in coverage, transaction size, and currency pairs. For B2B platforms, a payment orchestration platform that handles routing, FX, and compliance centrally remains more practical than waiting for bilateral linkages to scale.

For product and engineering teams, the question is not whether to support real-time rails but how. Three approaches exist. **Direct integration** with each local network gives maximum control but requires local banking relationships and per-country licensing — viable for banks, impractical for most platforms. **API-based orchestration** uses a single integration point (like Routefusion's API) to route payouts through local rails in 40+ countries, handling FX and compliance automatically. **Hybrid models** maintain direct integrations in the highest-volume corridors while using orchestration for the long tail. The build vs. buy analysis depends on your corridor concentration and engineering capacity.

Regardless of approach, four factors should drive rail selection per transaction: **speed requirements** (is instant confirmation needed?), **transaction value** (does it exceed the rail's limit?), **recipient expectations** (do recipients in this market expect instant settlement?), and **cost** (real-time rails are typically cheaper than SWIFT for the last-mile leg). Platforms building global payroll or marketplace payout products need routing logic that evaluates these factors dynamically.