ISO 20022 Crypto Explained: Which Coins Are Actually Connected to the Standard?

A website called qfsredemptionvault.com is currently selling people on a Quantum Financial System reset, and its proof is a list of ISO 20022-compliant coins. That includes XRP, XLM, and XDC. I found it while researching for this piece, and it’s a good snapshot of how much noise surrounds this topic.

Right now, no cryptocurrency is officially ISO 20022 compliant, because that certification doesn’t exist for tokens. SWIFT’s own ISO 20022 FAQ doesn’t mention crypto at all, not even a single time. What does exist is a small number of projects with real, traceable ties to the standard, buried under a much larger pile of copy-pasted compliant coins lists that cite nothing.

In this post, I’ll explain ISO 20022 in more detail.

Key Takeaways

• ISO 20022 is a messaging standard, not a blockchain feature. It defines how banks and payment systems format financial data. 
• SWIFT completed its own migration on November 22, 2025, and 97% of payment instructions switched over within a day. 
• Only a handful of crypto projects have documented ties to the standard. Ripple, Stellar, XDC-linked XinFin, and Quant Network have public, checkable evidence.
• Ripple’s own CTO has said the XRP token itself is not ISO 20022 compliant, even though RippleNet’s infrastructure supports ISO 20022 messaging.

What Is ISO 20022?

ISO 20022 is an international standard, maintained by the International Organization for Standardization, that defines a common data format for financial messages. Banks, payment networks, and market infrastructures currently use it to exchange information about payments, securities trades, and account details. But in a structured, machine-readable way.

Before it, most cross-border payments ran on SWIFT’s older MT format. It was a rigid, character-limited message type built in the 1970s. ISO 20022 replaces that with a richer, XML-based structure that carries more data (full names, addresses, purpose codes) instead of truncating it into free-text fields.

This isn’t a future rollout anymore. 

During SWIFT’s coexistence period, banks had the option to choose between MT or the ISO 20022 format to send messages. And that officially came to an end on November 22, 2025. And right after the transition weekend, SWIFT reported that 97% of payment instructions were already using the new format. That means the ISO 20022 network is now connecting more than 11,500 institutions in over 200 countries.

What Does “ISO 20022 Crypto” Actually Mean?

There’s no such thing as an ISO 20022 certificate for a token. The standard governs how financial institutions format messages to each other, not how blockchains validate transactions. So, when people say ISO 20022 crypto, they’re usually pointing at one of 3 different things.

• Network-level messaging support: A company builds infrastructure around a blockchain that can send or receive ISO 20022-formatted messages. This is real and checkable, but it describes the infrastructure, not the coin itself.
• Documented standards-body involvement: A company or foundation is a named participant in ISO 20022 crypto governance or working groups. This is much harder to verify independently, since the ISO doesn’t publish a simple public list of company members.
• Narrative with no source: A coin gets added to list after list because it was on a previous list, with no link back to anything a reader could check. This is most of what’s out there.

The clearest case study for why this distinction matters is Ripple. 

RippleNet, the company’s payment network, does support ISO 20022 crypto messaging for the banks that use it. But when confusion peaked around the SWIFT cutover, Ripple’s own CTO, David Schwartz, said that ISO 20022 is a messaging format for banks and doesn’t apply to cryptocurrencies. The network can be built to speak the standard. The token that settles value on that network is a separate thing, and it isn’t what gets certified.

ISO 20022 Coins List: Which Cryptos Are Connected to the Standard?

Currently, only four projects have public, traceable evidence of a real ISO 20022 crypto connection: XRP, XLM, XDC, and QNT. A second group, including HBAR, ALGO, and IOTA, shows technical compatibility or partnership language without the same level of documentation. So, here’s how they break down.

XRP (Ripple)

XRP is the coin most associated with ISO 20022 crypto, and it’s also the clearest example of the network-versus-token confusion. RippleNet, Ripple’s payment infrastructure, is built to send and receive ISO 20022-formatted messages for the banks on it. That part’s real. What isn’t real is the idea that the XRP token carries some kind of certification. 

Ripple CTO David Schwartz addressed this directly, confirming the standard applies to bank messaging, not to cryptocurrencies. 

XLM (Stellar)

Stellar’s ISO 20022 crypto connection has a specific, dated origin point. In 2023, blockchain infrastructure firm BP Ventures announced it had built ISO 20022 message support for the Stellar network. Just by mapping the structured payment data onto Stellar transactions while preserving the original fields. 

It’s also a third-party company’s product running on Stellar, not a certification issued to the network or the XLM token by ISO itself.

XDC Network

XDC Network’s tie to ISO 20022 crypto runs through Impel, a division of its founding company XinFin. Impel built and markets an ISO 20022 financial messaging API meant to bridge trade finance systems onto the XDC blockchain. 

That’s a product for a genuine use case, since trade finance messaging is exactly where ISO 20022 crypto gets used. It’s still a company-built bridge product, not blanket certification of the network.

HBAR, ALGO, and IOTA

Hedera, Algorand, and IOTA show up on nearly every ISO 20022 coins list, usually with vague language like enterprise-grade alignment or designed for CBDCs. 

Hedera’s Consensus Service could technically log ISO 20022-formatted messages. And its governance council includes financial firms, but till now, no bank has published a live ISO 20022 crypto workflow running on it. 

Algorand’s architecture is well suited to message mapping, in theory. IOTA is positioned around IoT and financial data. None of the three has a sourced case study like Stellar’s or Quant’s.

Are ISO 20022 Coins Officially “Compliant” or Certified?

SWIFT’s own ISO 20022 FAQ doesn’t mention cryptocurrency, and ISO doesn’t issue compliance certificates to tokens. Since the standard was built for how institutions message each other, not for how a blockchain settles value. Even Tangem’s own coin roundup, one of the more widely shared “compliant coins” lists, includes the disclaimer that cryptocurrencies have no official ISO body certification, right before listing nine coins as compliant anyway.

That contradiction is the whole problem. 

The phrase “ISO 20022-compliant coins” spread because it’s convenient, and because a wave of crypto commentary tied coin price predictions to the SWIFT migration deadline. 

But when the deadline came and went in November 2025 without the price event some had predicted, the phrase didn’t just disappear; it just kept getting reused.

What buyers usually mean when they say “ISO 20022-compliant coin” is closer to a coin whose team has some documented connection to financial-messaging infrastructure. That’s a fair thing to research. It’s just not the same claim as certification. And treating it as a certification is how misinformation like the qfsredemptionvault.com list gets taken seriously.

Why ISO 20022 Matters for Crypto and Cross-Border Payments

Set the certification myth aside for a second, because there’s a real reason crypto projects want a documented tie to ISO 20022, and that’s the distribution part. SWIFT’s network reaches more than 11,500 banks and institutions across over 200 countries. A year before the 2025 cutover, SWIFT was already routing more than 1 million ISO 20022-formatted messages a day. 

So, if a blockchain network can genuinely speak that same message format, it lowers the integration cost for a bank or payment provider that wants to settle value on it. Instead of building a custom bridge, the bank’s existing ISO 20022 crypto systems can, in theory, talk to the blockchain layer with less custom engineering. That’s the actual business case behind Quant’s involvement in the UK’s tokenized sterling deposits project with Barclays, HSBC, Lloyds, NatWest, Nationwide, and Santander.

Richer data is also what matters. 

The ISO 20022 crypto messages carry structured fields instead of the truncated free text older formats used. But for the compliance teams running sanctions screening or AML checks, that structured data is easier to automate against.

None of this guarantees any specific coin’s price, adoption, or survival. A documented messaging tie is an infrastructure signal. Plenty of blockchains with zero ISO 20022 involvement still move real settlement volume, and plenty of aligned projects haven’t even integrated the system yet.

How to Verify Whether a Coin Is ISO 20022-Ready

Here’s the process I used for this article. It takes about ten minutes per coin.

1. Search the project’s own newsroom or developer docs, not a listicle. If a company built real ISO 20022 crypto infrastructure, they usually announced it themselves, with specifics: a partner name, a pilot, a product page.
2. Look for a named partner or institution, not just banks. Quant’s UK deposit project names 6 specific banks. That’s checkable. But working with global financial institutions isn’t.
3. Separate the network claim from the token claim. Ask whether the sentence is about infrastructure a company built, or about the coin you’d buy on an exchange.
4. Check the date. Anything written about ISO 20022 as a future migration, rather than a completed one, was likely written before November 2025 and may be stale on other facts too.
5. Ignore lists that cite no sources. If you can’t click through to a primary announcement, treat the entry as unverified, not confirmed.

But here’s a catch. 

None of this is investment research. A verified ISO 20022 crypto connection tells you a project built with real infrastructure. But it doesn’t tell you whether that infrastructure gets used at scale, whether the token captures any value from it, or whether the project survives long enough to matter.

Final Thoughts

A documented ISO 20022 connection is a signal of intent, not a guarantee of anything. It tells you a team built real infrastructure and got at least one institution interested enough to name them in a press release. That’s worth more than a mention on an unsourced list, but it’s still a long way from adoption, and further still from a price outcome.

The SWIFT migration is done. Banks are running on ISO 20022 today, not someday. That makes this a good moment to stop asking which coins are ISO 20022 crypto-compliant and start asking which of these documented claims actually have a bank’s name attached to it. Most don’t. A few do. Now you know which is which.

For more info on crypto and all things Web3, visit Blockverse.

FAQs