SWIFT & ISO 20022
SWIFT is the standards layer behind most bank-to-bank cross-border. These essays cover gpi, ISO 20022, correspondent banking and what product teams must know to ship on it.
Shipped in this domain.
Field notes for this hub.
SWIFT Messaging Formats: MT vs MX (and Why It Matters Now)
MT was a printer-line format. MX is structured data. The difference is the entire next decade of cross-border product.
SWIFT and Cryptocurrency: The Honest Take
Stablecoins solve a real cross-border problem in specific corridors. They do not solve every cross-border problem in every corridor.
How to Track a SWIFT Payment Step by Step
If your bank cannot tell you where the payment is, the bank does not have the system. The system exists.
SWIFT in 2026: ISO 20022, Instant Rails, and the Pressure on Correspondent Banking
ISO 20022 is the past-tense story by 2026. The future-tense story is interoperability with instant domestic rails.
SWIFT Payment Delays: What Actually Causes Them
Most SWIFT 'delays' are not network delays. They are compliance reviews, cut-offs, or bad data.
Project Pangea Shows Stablecoin FX Needs PvP, Not Hype
More than 50 banks holding over $10 trillion in assets are testing whether FX can move from T+2 to T+0 without losing the controls the delay quietly buys. Project Pangea's PvP design, on Swift and ISO 20022, is the part worth reading.
SWIFT Fees, FX, and the True Cost of a Cross-Border Payment
The sticker fee is the smallest part of the cost. The FX margin is most of it. The product decisions decide both.
Swift's November 2026 Address Cutoff Is a Product Problem
In April, 61% of cross-border payments still carried unstructured debtor addresses. After 14 November 2026 Swift rejects them, and no mapper can recover data the origination screen never captured. This is a capture problem, not a standards footnote.
Correspondent Banking and the Reality of Emerging-Market Corridors
De-risking did not reduce risk. It moved the risk to the corridors that need access most.
SWIFT vs Card Rails vs Local Wallets: When to Use What
There is no universal best rail. There is the best rail for this corridor, this amount, this customer, this use case.
mBridge Is Not a SWIFT Killer. It Is a Settlement Warning Shot
mBridge matters less as a headline about replacing SWIFT and more as a practical warning: cross-border product teams now need to design for multiple settlement regimes, not one universal rail.
SWIFT, AML/CFT, and Sanctions Screening in Practice
Sanctions screening is where compliance theory meets throughput reality. The product decisions live in the list overlay, the matcher, and the review queue.
SWIFT gpi, Tracking, and the End of Payment Uncertainty
Before gpi, a cross-border payment was send-and-hope. After gpi, it is send-and-track.
ISO 20022 Migration: What Payment Product Teams Must Know
MT messages truncated reality to fit a 1980s field length. MX (ISO 20022) finally gives payments room to be structured.
SWIFT Payment vs Wire Transfer: Key Differences
'Wire transfer' is the outcome. 'SWIFT' is one way to instruct it. The two are not the same thing.
How SWIFT Payment Works: A Complete Overview
SWIFT is messaging, not movement. Understand the difference and most cross-border problems become legible.