Swift’s blockchain ledger is ready for use

Of all the phrases to come out of the payments industry, “digital islands” might be the prettiest. 

It conjures crystal-blue waters, gently swaying palm trees, white sandy beaches made of granulated data… 

It’s also the nicest possible way to say “fragmentation.” 

As digital assets — stablecoins, tokenized deposits, central bank digital currencies — move from experiment to real-world use, they’re being built on different technologies: Corda, Quorum, private ledgers, public blockchains. None of them naturally talk to each other. Left alone, we end up with a scattering of disconnected “digital islands”.  

146 jurisdictions, representing 98% of global GDP, are exploring a central bank digital currency, each built around its own national priorities. 

What connects these islands is shared standards. Without them, all this new technology does is take the friction out of correspondent banking and rebuild it elsewhere. 

Is ISO 20022 that shared language?

Swift’s role is evolving

Recognizing this shift, Swift’s first response has been to act as a connector rather than to issue digital money itself. On 9th July 2026, the payments network announced its own blockchain-based ledger, working with 17 banks across the globe to pilot 24/7 cross-border payments via tokenized deposits. This demonstrates the speed at which regulated payment infrastructure is evolving. And how Swift is adapting to meet these changes. 

It is, after all, air traffic control for global payments. Swift doesn’t own the aircraft or the airports, but ensures everything moves safely, predictably, and at scale. 

So, through industry-wide sandbox work, Swift has explored how to coordinate transactions across multiple networks. This aligned messaging, settlement, compliance, and timing, while allowing assets and funds to remain on their original ledgers. 

This connector model has already been used to coordinate: 

• CBDC‑to‑CBDC transactions 

• CBDC and fiat payments 

• Tokenized asset settlement 

• Atomic delivery‑versus‑payment (DvP) and payment‑versus‑payment (PvP) flows 

All without forcing the industry onto a single blockchain or a single digital currency design. 

The ledger was built with Consensys and designed to record, sequence, and validate transactions and to enforce rules through smart contracts. 

By early 2026, that work had moved from concept into a live build, beginning with interoperability between banks’ tokenized deposits. It means the network long associated with messaging for money is now also helping to move it. 

The move is easy to understand. While instant payment systems offer real-time, 24/7 settlement in many domestic markets, their cross-border reach and interoperability remains limited. Stablecoins, by contrast, enable continuous settlement across borders and currencies, including weekends and bank holidays. Addressing a gap that corporate treasurers continue to face.  

A shifting industry

Business-to-business stablecoin payments have grown rapidly, reaching an estimated $226 billion a year. Despite what some enthusiastic advocates suggest, the technology is not about to solve everything. But it is very useful for cross-border settlement. 

And Swift isn’t alone. In mid-2026, JPMorgan, Citi, Bank of America, Wells Fargo and more than a dozen other banks announced a shared Tokenized Deposit Network through The Clearing House, targeting a first-half 2027 launch. Its aim is to settle regulated bank deposits on-chain around the clock. Around the same time, Visa and Mastercard, along with Stripe, were reported to be exploring a joint stablecoin platform, with Coinbase weighing whether to join. 

Some of this is still early-stage, and parts of it remain unconfirmed. Several institutions are involved in multiple initiatives, helping to shape Swift’s ledger while also backing a competing bank network. 

But it shows that the big players are not waiting for the future of digital settlements. They are racing to build it, but using several different paths at once. 

So, can ISO 20022 be the common language for digital money?

It’s the best candidate we have. ISO 20022 offers the structured, globally understood language that could let traditional payments, instant rails, stablecoins, tokenized deposits, and CBDCs coexist and interoperate. Used consistently, it would let digital money slot into the compliance processes, treasury systems, FX workflows, and settlement infrastructure that already exist. 

Of course, it’s not simple. None of the new rails — tokenized deposits, stablecoin platforms, Swift’s ledger, sovereign CBDCs — automatically speaks ISO 20022. They can. We don’t yet know whether they will. Without a shared standard, digital money fragments into well-funded islands. But with one, the archipelago has a chance to become a continent. 

Which is why ISO 20022 is far from complete. It is the foundation for the next phase of competition in payments, and the institutions that benefit most will be the ones that turn structured data into speed, transparency, and insight. 

The Bank for International Settlements has been blunt about what that takes. Its Committee on Payments and Market Infrastructures, which refreshed its harmonized ISO 20022 data requirements as recently as February 2026, has made the point that everyone has to use the data the same way, or the benefits cancel out. The requirements are maintained until at least the end of 2027, because it’s consistency, not adoption, that unlocks the value. 

Most institutions aren’t there yet. For many, the end of coexistence became an exercise in minimum viable compliance. Translation tools and quick fixes have been bolted onto core systems that were never modernized. But translation is temporary. It bridges old and new formats while stripping out the richer data that ISO 20022 exists to carry. Domestic adoption is patchy too, with major rails still working out how to use the new messages. 

The Financial Stability Board’s 2025 progress report on the G20 Roadmap suggests the policy milestones are largely in place, but end users aren’t feeling the benefits, and the 2027 deadline looks unlikely. The bottleneck has moved from policy to implementation, which means the work is now firmly in institutions’ own hands. 

The gap between knowing and doing

Almost everyone now recognizes the value of structured data. The hard part — the part that actually turns it into an advantage — happens under the hood: refining data quality, realigning operating models, modernizing the core. It’s unglamorous, and it’s exactly where the real benefit sits. 

That gap, between knowing and doing, is what will separate the institutions that lead from those that merely keep up. Because the rails for digital money are being laid right now, by Swift, by the big banks, by the card networks, along several competing paths at once. Nobody knows which will win. But whoever has done the deep data work will be ready to connect to whichever one does. Being interoperable is not the same as being competitive. 

Need help with your ISO 20022 migration?

At RedCompass, we help institutions move beyond ISO 20022 compliance and turn structured data into strategic advantage — across traditional payments, instant rails, and emerging digital‑asset ecosystems. As the rails for digital money take shape, and the contest over which data standard connects them plays out – that work is increasingly about being ready to participate, not just ready to comply. 

If you’d like to work with us, get in touch.