Swift's Sibos Move: A Blockchain Ledger + A Retail Scheme

Swift just confirmed two big steps:
* a blockchain‑based shared ledger co‑designed with 30+ banks (prototype with Consensys), initially targeting real‑time, 24/7 cross‑border payments; and
* a new retail "scheme" that sets rules for fee/FX transparency, full‑value delivery, end‑to‑end tracking and "instant where available."
How to read this: Scheme = the promise layer; Ledger = the execution layer. The scheme codifies the customer experience (price/speed predictability); the ledger is a coordination layer (ordering/validation/finality semantics) that could make "instant" outcomes consistent across borders, if corridors have 24/7 FX and dependable last‑mile rails.

Context that matters: Swift's own data says ~75% of cross‑border payments already reach the beneficiary bank within 10 minutes, yet ~80% of total time is lost in the domestic last mile (local rails, PoP/FX approvals, cut‑offs, manual checks). That's exactly where the scheme+ledger combo aims to compress latency.

Why customers should care: End‑to‑end STP is still low (~26% globally) and ~14% of payments incur extra bank charges; every repair/return averages ~$12, costs and churn that better pre‑validation + richer, structured ISO 20022 data can reduce. Strengthening standing settlement instruction (SSI) quality and using pre‑validation are near‑term wins regardless of the rail.

What I'm watching next (signals of real progress):
1. First live corridors & weekend behavior (do we see true 24/7 posting?).
2. Enforcement mechanics for the retail scheme: KPIs, corridor‑level SLAs, and remedies for misses.
3. FX liquidity models (tokenised deposits/MM facilities/market‑maker connectors) to guarantee round‑the‑clock convertibility.
4. Interoperability mapping: how "on‑ledger states" map to ISO 20022/gpi/Tracker statuses for unambiguous customer visibility.
5. Governance: validator set, change management, dispute resolution, and fallbacks. (Industry coverage lists a broad coalition, from JPM, HSBC, Deutsche, MUFG to Santander and Wells Fargo; so governance will be key.)
Bottom line: This is coexistence, not rip‑and‑replace. If Swift can pair the scheme's promises with a ledger‑backed execution layer, and line it up with domestic instant rails and 24/7 FX, "as fast as domestic" stops being marketing and starts being measurable reality.

Topics: ISO 20022, SSI, Payments, SWIFT, Tokenization