SWIFT Just Rewrote the Rules for Cross-Border Retail Payments. Here's What Bangladeshi Banks Need to Do Next.

Something significant happened in the cross-border payments world last September, and it didn't get nearly enough airtime in Bangladesh's banking circles.

At Sibos 2025 in Brussels, SWIFT announced its Payments Scheme — a set of enforceable rules (not guidelines, not best practices — rules) governing how retail and SME cross-border payments should work across its network. By March 2026, over 50 of the world's largest banks had signed on, and the first live corridors across 11 countries are set to go active by mid-year.

Bangladesh is one of those 11 launch markets. City Bank is already confirmed as a participant. And this is not a pilot — it's a production rollout with contractual commitments and go-live deadlines.

At SSCL, we've been studying the scheme architecture, the API requirements, and the Bangladesh-specific integration challenges closely. This post is our attempt to lay out what we've learned — both for banks evaluating participation and for the technology teams who'll need to build it.

What the scheme actually changes

If you've worked with SWIFT GPI, you already know the trajectory. GPI brought tracking and speed to wholesale payments — roughly 75% of GPI transactions now reach the beneficiary bank within 10 minutes. SWIFT Go added a no-deduct fee model for low-value payments under $10,000. Both were meaningful improvements.

But they were voluntary frameworks, which created a fundamental scaling problem. Swift Go alone required 620+ bilateral agreements between banks. Every new corridor meant new paperwork, new commercial negotiations, new technical integrations.

The Payments Scheme replaces this bilateral web with centralized, enforceable rules. You sign the terms and conditions once. You commit to a defined set of capabilities. And then you're in — connected to every other participating bank through the scheme's governance rather than through individual bilateral arrangements.

The shift in a [long] sentence:

The practical commitments for participating banks include upfront fee and FX transparency visible to the sender before initiating the payment, guaranteed full-value delivery with no intermediary deductions, near-instant processing leveraging domestic instant payment rails, end-to-end traceability from originator to beneficiary, round-the-clock availability, and structured dispute resolution with stop-and-recall capabilities.

For anyone who's spent time explaining to customers why their $500 remittance arrived as $487 three days later — this is the problem being solved.

The Gateway Intermediary — and why it matters for Bangladesh

The scheme introduces a role called the Gateway Intermediary (GI). This is the most important concept in the entire framework for receiving-country banks.

A Gateway Intermediary is the bridge between the SWIFT cross-border leg and the domestic payment infrastructure. When a bank in London sends a scheme payment to Bangladesh, the GI is the institution that receives that SWIFT message, converts it into a domestic clearing instruction, pushes it through NPSB or RTGS, and confirms back to SWIFT's Tracker that the beneficiary's account has been credited — all in near-real-time, 24/7.

Think of it as becoming the default routing point for all scheme-compliant inbound payments to a market. Every participating bank globally that sends money to Bangladesh under the scheme routes through the GI. That's not just a technology project — it's a strategic position in the payments value chain.

The GI business model is clean. Under the no-deduct principle, the GI charges a fixed per-transaction fee to the sending bank, invoiced monthly — completely separate from the payment flow. The remitted amount arrives at the beneficiary untouched. This replaces the opaque SHA/BEN/OUR charging codes that have caused confusion in correspondent banking for decades.

The numbers that matter

Bangladesh received a record $30.04 billion in formal inward remittances in FY 2024–25 — a 25.5% year-over-year increase. Over 50 banks have signed up for the scheme globally as of March 2026. And Bangladesh is one of just 11 launch markets selected for the initial rollout.

Why Bangladesh is a high-priority market

Bangladesh's selection as one of just 11 initial launch markets isn't accidental. Remittances represent roughly 6.6% of GDP and fund nearly half of all import payments. The government's 2.5% cash incentive on formal-channel wage remittances, combined with post-July 2024 enforcement against informal hundi networks, has driven record volumes through the banking system. For SWIFT, this makes Bangladesh one of the most attractive receiving markets in the world — a large, growing, policy-supported remittance corridor with clear demand for faster, more transparent payment experiences.

Equally important: NPSB is scheme-ready. Bangladesh's National Payment Switch has operated 24/7 since its launch, including holidays, with real-time settlement for current and savings accounts. Transaction limits of BDT 300,000 for individuals and BDT 500,000 for corporates cover the scheme's typical retail and SME payment sizes comfortably. NPSB also supports MFS interoperability — meaning a GI could potentially route remittance funds directly to bKash or Rocket wallets as the final delivery mechanism.

Not every scheme market has this advantage. Some countries will need to build or upgrade domestic instant payment infrastructure to meet the scheme's 24/7 near-instant requirement. Bangladesh already has it.

Who else is in the room

The participant list reads like a roster of global correspondent banking heavyweights. JP Morgan, Bank of America, Citi, BNY, HSBC, Deutsche Bank, BNP Paribas, Standard Chartered — they're all signed on as originating banks.

More relevant for the Bangladesh corridor: all four major Indian banks — ICICI, HDFC, Axis Bank, and State Bank of India — are scheme participants. India-to-Bangladesh is one of the highest-volume remittance corridors in South Asia. Having these banks as originators, combined with a Bangladeshi GI, creates a ready-made high-throughput payment route from day one.

From the region, Bank Negara Indonesia, KASIKORNBANK (Thailand), OCBC and UOB (Singapore), Bank of the Philippine Islands, and of course City Bank from Bangladesh have all joined. The Gulf corridor — critical for Bangladeshi workers in Saudi Arabia, UAE, Qatar, and Oman — is represented through Emirates NBD and Saudi Awwal Bank.

What it takes to become a Gateway Intermediary

Having reviewed the scheme requirements in detail, here's our assessment of the key technical and operational capabilities a Bangladesh-based bank needs to deliver.

GPI API readiness means integration with SWIFT's API layer using OAuth 2.0 (JWT-Bearer per RFC 7523) for real-time transaction status updates and tracker connectivity.

24/7 operations isn't just systems uptime — it requires staffed exception handling, real-time monitoring, and continuous domestic rail connectivity. NPSB supports this; BD-RTGS does not operate on weekends or holidays.

Near-instant processing demands an automated STP pipeline: sanctions screening, FX conversion, NPSB routing, and account crediting with minimal manual intervention.

The no-deduct fee model requires a separate billing system that invoices sending banks monthly. Payment principal flows through untouched — no deductions from the remitted amount.

Network Interoperability API bridges SWIFT ISO 20022 messages (pacs.008) into NPSB-compatible domestic clearing instructions. This is SWIFT's "One-Leg-Out" model in action.

Confirmation on behalf means an automated confirmation back to SWIFT Tracker when the beneficiary account is credited. The core banking system must generate real-time credit events.

UETR propagation — the Unique End-to-End Transaction Reference must carry through from the SWIFT leg into the domestic NPSB leg, maintaining traceability across the entire payment chain.

The SR2026 standards release (November 2026) adds another layer: structured postal addresses become mandatory, and unstructured formats will be rejected. Any implementation project needs to account for this data quality requirement alongside the core scheme capabilities.

The timeline is tight but clear

The scheme was announced in September 2025 at Sibos, with a coalition of 30+ banks co-designing rules. By March 2026, 50+ banks had signed on with 25+ committed to a June go-live. The June 2026 initial go-live will activate corridors across 11 countries, with City Bank expected to be live for Bangladesh. November 2026 brings the SR2026 deadline mandating structured addresses. And by December 2026, expanded market coverage and second-wave GI activations are expected.

For any bank targeting a December 2026 go-live as a Gateway Intermediary, we're looking at roughly nine months of implementation from where we stand today. That's tight, but it's achievable — particularly if the bank already runs a modern core banking platform with existing SWIFT connectivity and can leverage NPSB's existing 24/7 infrastructure rather than building new domestic rails.

The competitive picture — and what's at stake

SWIFT isn't doing this in a vacuum. Ripple has processed over $100 billion in cumulative volume with 3–5 second settlement. Visa Direct and Mastercard Cross-Border Services offer near-real-time consumer payment experiences. Wise and similar fintechs have set a consumer expectation bar that traditional correspondent banking has struggled to match.

Regionally, China's CIPS system has doubled its transaction volume since 2020, and the BIS's Project Nexus aims to interlink national instant payment systems multilaterally by 2027.

The Payments Scheme is SWIFT's answer. And its moat is formidable — 11,500+ connected institutions, 4 billion reachable accounts, and decades of embedded infrastructure that no competitor can replicate quickly. For Bangladesh's banks, the question isn't whether cross-border payments will get faster and more transparent. The question is whether you'll be the infrastructure that delivers that experience, or the institution that gets routed around.

Our perspective at SSCL

We've been working at the intersection of SWIFT integration, domestic payment rails, interoperation instant payment system rails like Mojaloop, and banking middleware for long enough to know that projects like this are won or lost in the plumbing — the message translation layer between ISO 20022 and NPSB, the real-time event architecture that triggers confirmations, the 24/7 monitoring stack that catches exceptions before they become settlement failures.

The scheme's requirements are well-defined and achievable. NPSB gives Bangladesh a structural advantage that many other markets lack. And for a bank with the right correspondent relationships, existing SWIFT connectivity, and a modern core platform, the Gateway Intermediary role is a strategic opportunity — not just a technology project.

We're currently deep in the technical architecture of what a GI implementation looks like for a Bangladeshi bank: the API integration patterns, the NPSB connectivity layer, the automated STP pipeline, and the 24/7 operational model. If your institution is evaluating this opportunity, we'd welcome the conversation.

Dr. Faizul Bari is the founder of SSCL, working on payments infrastructure, banking technology, and digital transformation for financial institutions in Bangladesh and beyond.