ISO 20022 explained: the bank messaging standard and the 'ISO 20022 coins' claim

ISO 20022 is a global standard for the messages banks send each other about payments and other financial transactions. It matters a great deal to banks, but it does not approve, certify or require any cryptocurrency, despite what you may have read online.

What ISO 20022 actually is

Every time money moves between banks, a message travels with it. That message says who is paying, who is being paid, how much, in which currency and why. ISO 20022 is a shared rulebook for writing those messages.

It was developed by the International Organization for Standardization's committee for financial services (TC 68). The standard has two main parts: a method for modeling financial business processes, and a central dictionary of business terms such as "debtor," "creditor" and "remittance information." Messages built from those models are usually expressed in XML, a structured text format that computers can read reliably.

You can think of it like a well-designed form. The older Swift MT messages it replaces were closer to a short note with limited room and loosely defined fields. ISO 20022 gives each piece of data its own clearly labeled box, with room for much more detail.

The message definitions and the catalogue of messages are published on iso20022.org, and anyone can build software that reads or writes them. In that sense the standard is open. There is no licensing body that admits some products and rejects others.

A quick look inside an ISO 20022 message

ISO 20022 messages have short codes that tell you what job they do. The prefix names the business area and the number names the specific message. A few you may see mentioned:

• pain.001: a company or person asks its bank to make a payment ("payment initiation").
• pacs.008: one bank tells another to credit a customer's account ("payments clearing and settlement").
• camt.053: a bank sends a customer a detailed account statement ("cash management").

Inside each message, data sits in labeled fields. The payer's street, town and country each get their own slot instead of sharing a single line of text. A field for remittance details can say which invoices a payment covers. That structure is what lets software process payments and checks with less manual work.

Notice what is missing: nothing in these messages chooses a settlement asset beyond naming the currency. A pacs.008 sending US dollars still moves dollars between bank accounts.

Who uses ISO 20022 today

Adoption has been gradual, spread over almost two decades. As of October 2026, these are some of the systems that matter most for US readers and global payments:

Many other high-value and instant payment systems around the world have moved to the standard as well. The direction of travel is clear: ISO 20022 is becoming the common language of bank payments.

Why banks care

For banks, the switch is mostly about data quality and automation. Three benefits come up again and again.

• Richer data. Messages can carry full names, structured addresses and detailed remittance information, such as which invoice a payment settles. The Clearing House highlighted extended remittance data as a benefit of the CHIPS move.
• Better compliance. Structured fields make sanctions screening and anti-money-laundering checks more accurate, because software can find a name or country without guessing where it sits in free text.
• More automation. When every bank uses the same well-defined fields, fewer payments need a human to fix them. The Federal Reserve describes the goal as greater end-to-end efficiency for domestic and cross-border payments.

For you as a bank customer, the change is mostly invisible. Over time it may mean fewer delayed wires and clearer information on statements, but you do not need to do anything.

Where the "ISO 20022 coins" idea came from

As the big migrations approached, a narrative spread through crypto social media, YouTube and blogs: that a short list of cryptocurrencies were "ISO 20022 compliant" and would be used by banks once the new standard took over. Lists vary, but they usually include XRP, Stellar (XLM), XDC, Algorand (ALGO), Hedera (HBAR), Quant (QNT), IOTA, and more recently Chainlink (LINK) and Canton Coin (CC).

The idea grew from a few real facts stretched too far. Ripple, the company associated with XRP, does take part in ISO 20022 governance. Some projects build software that can produce ISO 20022 messages. Several of these networks also target banks and payments. Put together and repeated often, those facts became a story that the standard picks winners. It does not.

Myths vs. facts

Myth: some coins are "ISO 20022 compliant" or "ISO 20022 approved"

Fact: ISO 20022 defines message formats. There is no certification program for cryptocurrencies, and a token is not a message. A software product can generate valid ISO 20022 messages, but so can any bank's payment system, and that capability does not transfer to a coin.

Myth: when Swift switched to ISO 20022, banks had to start using crypto

Fact: Swift's change, completed on November 22, 2025, required banks to format cross-border payment instructions in ISO 20022. Banks still settle in the same currencies as before. Fedwire's July 2025 switch was likewise a format change, not a new asset.

Myth: membership in ISO 20022 groups means endorsement

Fact: ISO 20022 is maintained by the Registration Management Group (RMG), a Technical Support Group, and Standards Evaluation Groups (SEGs) that review messages for specific business areas. Members include national standards bodies, central banks, market infrastructures and companies such as Visa, Mastercard, DTCC and Ripple. A seat means a firm takes part in the process. It is not a seal of approval for that firm's products, and it says nothing about any token.

Myth: the standard is closed, so only selected projects can use it

Fact: The message catalogue is publicly available. Any developer can map data to ISO 20022 messages, which is why "ISO 20022 support" appears in so many product brochures, crypto and non-crypto alike.

What each commonly cited project actually does

Each project below does real work and is worth understanding on its own terms. The short version for all of them: any ISO 20022 link is about software or company participation, not a status held by the token. Our coin pages go deeper.

XRP is the native asset of the XRP Ledger, a public payments ledger running since 2012. Ripple, the company, appears on the official RMG member list under a "RippleNet" delegation. That is a real governance seat held by a company, and it gives the XRP token no special standing.

Stellar (XLM) is an open payments network used to move stablecoins and tokenized funds, with XLM paying network fees. We found no ISO 20022 membership for the Stellar Development Foundation; its link is indirect, through payment companies on Stellar that use ISO 20022 in their own systems.

XDC Network is an Ethereum-compatible chain aimed at trade finance. The project markets a payments product that it says supports ISO 20022 message formats. That is a software feature described by the project, and XDC is not on the RMG roster.

Algorand (ALGO) is a proof-of-stake chain used for payments and tokenized assets. We could not find any documented ISO 20022 role, membership or bank messaging pilot; its place on these lists comes from third-party content.

Hedera (HBAR) is a public ledger governed by a council of large organizations. Some council members are banks or payment firms that use ISO 20022 in their own businesses, but Hedera itself has no documented ISO 20022 role, and we found no Swift announcement supporting claims of joint "ISO 20022 testing."

Quant (QNT) is a company that sells software connecting bank systems to blockchains. It says its tokenized deposit platform is built to work with ISO 20022, which is a sensible product choice for selling to banks. QNT is used in Quant's licensing model, and customers do not need to hold it to benefit from ISO 20022 support.

IOTA is a proof-of-stake ledger focused on trade documents, identity and data. We found no documented ISO 20022 role for the IOTA Foundation, whose trade work centers on other standards.

Chainlink (LINK) provides data and cross-chain messaging to blockchains. It has a documented series of experiments and pilots with Swift, including work where Chainlink tools produce ISO 20022 messages. That shows banks using Chainlink software alongside ISO 20022, not a rule that banks must hold LINK.

Canton Network (CC) is a privacy-focused network built for regulated finance, where Canton Coin pays for the shared coordination layer. Some institutions using Canton, such as DTCC, separately take part in ISO 20022 governance, but Canton has no ISO 20022 membership or certification of its own.

What ISO 20022 can realistically mean for crypto

There is a fair, modest version of the story. When banks all speak one detailed message language, it becomes easier for any outside system, including a blockchain platform, to connect to them. A firm that translates between bank messages and on-chain transactions has a cleaner target than it did with older formats.

That benefit is open to everyone, though. Traditional software vendors, fintechs and every blockchain project can use the same public message definitions. Whether a particular network wins bank business depends on its technology, compliance, partners and track record, not on the standard itself. And even when a bank adopts a blockchain product, it may use stablecoins, tokenized deposits or the platform's software without buying the network's native token.

How to evaluate ISO 20022 claims

When you see a post saying a coin is tied to ISO 20022, run through a few questions before you trust it.

1. Who is the source? Look for confirmation from ISO, Swift, a central bank or the project itself. A video title or a price-prediction site is not evidence.
2. What exactly is claimed? "Our software can create ISO 20022 messages" is a modest, checkable claim. "This coin is approved by ISO 20022" cannot be true.
3. Is the token needed? If a bank can use the product without buying or holding the token, ISO 20022 support does not create demand for the token. Our utility lens helps you assess this.
4. Is there real usage? Pilots, press releases and memberships are a start. Look for live, repeated use with named customers.
5. Check the roster yourself. The RMG member list is public on iso20022.org, so you can confirm or rule out membership in a minute.

If you already hold one of these assets, nothing here says the project is bad. Several do useful work with banks and payment firms. The point is simply to hold for reasons that are documented, and to size your position with the usual risk rules in mind.

Where to go next

To compare these projects side by side, browse our ISO 20022 category page, where each profile includes a plain reality check. For the bigger picture of how banks, payment networks and crypto are connecting, read our guide to bridging traditional finance and crypto. And if you are new to judging projects, our guide on how to evaluate a crypto project walks through the basics.

Updated October 4, 2026 by The Crypto Guide editorial team. Educational content, not financial, legal or tax advice. Spot an error? Request a correction.