ISO 20022 - what it really is

If you arrived here from a video or a social media thread, you probably heard that a handful of cryptocurrencies are "ISO 20022 compliant", that banks will soon be forced to use them, or that a standards body has approved them. Almost none of that survives contact with the primary documents. The standard is real, the migration of the world's payment systems to it is real, and it is genuinely important. The connection to any specific coin is a different, much weaker thing, and this page separates the two.

What ISO 20022 actually is

ISO 20022 is a standard for the electronic messages that financial institutions send each other. The Reserve Bank of Australia describes it as "an open and general purpose global financial electronic communications standard", introduced in 2004 by the International Organization for Standardization (ISO). ^[4] The standard is developed under ISO Technical Committee 68, Financial services, which is "responsible for creating global standards for the financial services industry", covering core banking, capital markets, payments and card processing, with a subcommittee dedicated to information exchange. ^[5]

The easiest analogy is a shared form. When your bank wires money abroad, it does not send a free-text email. It fills in a structured message with agreed fields: who pays, who receives, how much, in which currency, which bank identifiers, what the payment is for. ISO 20022 defines the dictionary of those fields (the "business components") and the rules for assembling them into complete messages. The RBA notes that the components are independent of the underlying data language, although XML is the syntax most commonly used in practice. ^[4]

Three ideas follow from this and matter for the rest of the page:

• ISO 20022 is about messages between institutions, not about money or ledgers. It describes how a payment instruction is written, not how value moves or settles.
• It is syntax-agnostic. The same business content can be expressed in XML or in other formats, so "we can produce ISO 20022 messages" is a statement about software, not about a network's architecture.
• It is a library, not a product. There is a repository of definitions that payment systems pick from and adapt through "usage guidelines" such as Swift's CBPR+ and the high-value payment systems' HVPS+. ^[4]

The Registration Authority and the message catalogue

ISO publishes the standard itself (ISO 20022-1 and its companion parts), but the living catalogue of message definitions is maintained by a Registration Authority, which operates the iso20022.org website and publishes the message repository. That role is held by Swift, the Belgian cooperative that also runs the interbank messaging network most banks use for cross-border payments. ^[1][28] Around the Registration Authority sit volunteer governance bodies: a Registration Management Group (RMG) that oversees the standard, Standards Evaluation Groups (SEGs) that review proposed messages in each business area, and a Technical Support Group (TSG). Membership of these bodies is by application, and the existing members decide on new applicants. ^[3]

The catalogue is organised in families whose four-letter prefixes you will meet in every migration document:

Notice what the table does not contain: no field says "which blockchain to use", and no message carries a cryptocurrency. A pacs.008 is a description of a payment between two banks' customers. How the two banks settle the obligation between themselves, through a central bank account, a correspondent relationship or anything else, is outside the message.

Not a certification, and ISO endorses no cryptocurrency

This is the heart of the misunderstanding. ISO publishes documents. It does not test, certify or approve products against ISO 20022, and neither does the Registration Authority. There is no "ISO 20022 compliant" stamp that a company, a network or a token can earn. A Cardano community member replying in a forum thread in May 2021 wrote that any such certification "will be applied to payment applications, not the blockchains & currencies themselves." ^[17] In November 2025, a crypto news site reported, citing a social-media post and a screenshot, that the ISO 20022 website states that no cryptocurrency meets any form of ISO 20022 compliance and that ISO does not administer or certify compliance for assets such as XRP, XLM, ADA or Quant. ^[16] We could not confirm that wording on the primary page.

What can a project honestly say? It can say that a specific piece of software, for example a gateway, a payment platform or an API, is able to produce or consume ISO 20022 messages. That is a real and useful property, and banks ask vendors for it. It is also unremarkable: thousands of banking software products do the same. Compare it to a courier whose shipping labels follow the postal service's address format. Compatible, yes. Endorsed by the post office, no. And the parcel itself, the token, is not what the format describes.

So when you read "coin X is ISO 20022 compliant", translate it as: "a company associated with coin X says that some software it builds can speak the bank message format". Then ask which software, which message, and who besides the company says so.

Where the "ISO 20022 coins" story came from

The narrative has a traceable history. In an article dated 11 June 2020, Ripple, the company, said it is part of the ISO 20022 Registration Management Group and described itself as the first member focused on distributed ledger technology. Its own article talks about RippleNet, its payment network for banks, being "aligned with ISO 20022 standards from the start". The article does not mention the XRP token at all. ^[11]

From there the story spread through list articles. In December 2021 an InvestorPlace piece named five "compliant" coins (XRP, XLM, XDC, IOTA, ALGO) and three "rumored" ones (HBAR, QNT, ADA), and asserted that Stellar was a member of the standards body "through IBM". ^[12] By 2024-2026 a hardware-wallet vendor's explainer listed eight coins (XRP, XLM, XDC, ALGO, IOTA, HBAR, QNT, ADA) as "compliant", while conceding in the same text that "Cryptocurrencies have no official ISO body certification". ^[13] CoinMarketCap maintains a category page titled "Top ISO 20022 Tokens" with fifteen entries and the one-line description "Listed below are the top crypto coins and tokens used for ISO 20022"; the page gives no criteria for inclusion. ^[14] On 10 November 2025, twelve days before Swift's coexistence deadline, Cardano founder Charles Hoskinson posted that "ISO 20022 support is essential to open banking" and that ADA "is glad to be holding the line with XRP, HBAR, ALGO, and others". ^[15]

Claim vs reality for the eight projects

The table applies one test to each project: what does a primary source actually show at the time of writing? "Narrative" means the only sources are list articles and social media. "Self-declared" means the project itself says it, with no third-party record. "Verified" means we found the primary document.

A few of these deserve a sentence more.

XRP and Ripple. The one verifiable organisational link in the whole list belongs to a company, Ripple, not to a token. Sitting on the RMG means taking part in discussions about message definitions. It confers no right, priority or obligation on banks regarding XRP, and Ripple's own announcement is careful to talk about RippleNet. ^[11] The coin page covers what Ripple's payment products actually do: /coins/xrp.

XLM and Stellar. The "through IBM" story appears to originate from IBM's use of Stellar in a payments product and was never backed by a membership record. The January 2026 article by the Stellar Development Foundation's CEO is a strategy piece about interoperability with bank messaging; the coverage we could access describes a plan, and the Foundation's original post was not reachable with our tools. ^[12][20] See /coins/xlm.

QNT and TC 307. ISO/TC 307 is ISO's committee for blockchain and distributed ledger technologies. Helping to initiate it is a genuine credential, and it is accurately described in Quant's history. It is simply a different thing from ISO 20022, which belongs to TC 68. Conflating the two is the most common error in this narrative. ^[22][5] See /coins/qnt.

XDC. XDC's documentation uses the word "Compatible", and its 2025 release says the network is "designed to be compliant". These are the project's own descriptions of its software; no bank, regulator or standards body is quoted confirming them. ^[18][19] See /coins/xdc.

For the remaining four, /coins/algo, /coins/hbar, /coins/iota and /coins/ada, we found no primary document that connects the network to ISO 20022 in any formal way. Each coin page has a chapter "The ISO 20022 connection" that repeats this check with the project's own sources.

The Swift CBPR+ migration and the end of coexistence

Swift's programme for moving cross-border payments to ISO 20022 is called CBPR+ (Cross-Border Payments and Reporting Plus). During a coexistence period, banks could send the old MT messages or the new ISO 20022 (MX) messages. That period ended on 22 November 2025. From that date, bank-to-bank payment instructions on Swift are delivered only in ISO 20022. ^[6][7]

What actually happened at the deadline, as far as the industry documents available to us show, is that the switch took place as scheduled. A July 2026 review states that "the coexistence period formally ended" on 22 November 2025, that the MT 1xx, 2xx and 9xx families no longer meet CBPR+ requirements for payments, and that MT103 was replaced by pacs.008, MT202 and MT205 by pacs.009, and the MT940, MT941 and MT942 statements by camt.052, camt.053 and camt.054. Other MT categories (3xx, 4xx, 5xx, 6xx, used for treasury, collections and securities) remain active. ^[6] Swift kept a safety net: an in-flow conversion of a few legacy payment messages (MT103, MT103 STP, MT200, MT202, MT202 COV) into ISO 20022, with senders charged for this contingency processing from 1 January 2026. Reporting and investigation messages (camt) continue to be supported. ^[7]

The migration is part of a wider, coordinated effort. The Bank for International Settlements' Committee on Payments and Market Infrastructures published harmonised ISO 20022 data requirements for cross-border payments in October 2023 and asked market participants to align with them "by end-2027 at the latest". ^[8] None of these documents mentions a cryptocurrency, and the deadline that the narrative pointed to for years passed without any mechanism that would route bank payments through a public blockchain.

Fedwire and other payment systems

The United States took the same step for its high-value system. The Federal Reserve's Fedwire Funds Service moved to ISO 20022 on 14 July 2025, after the original March 2025 date was pushed back to give participants and vendors more time. On the implementation date, the proprietary FAIM message format was retired and replaced by ISO 20022 messages in a single-day cutover. ^[9][10]

Fedwire is not an outlier. The RBA's 2020 review lists live ISO 20022 systems such as Australia's New Payments Platform, Singapore's FAST and Sweden's Swish, and planned migrations of high-value systems in the United Kingdom, the euro area, Canada, Singapore, New Zealand and Hong Kong. ^[4] Most of the world's large-value payment infrastructure now speaks the same message language. That is the real significance of ISO 20022: richer, structured data for compliance screening, reconciliation and automation. It is a story about banks' plumbing, and it would be equally true if no cryptocurrency existed.

ISO 24165 and the Digital Token Identifier

There is one place where crypto tokens genuinely appear in ISO's financial standards, and it is worth understanding precisely because it is often misread as an endorsement. ISO 24165, published in 2021, defines the Digital Token Identifier (DTI). The Registration Authority is Etrading Software, which issues DTIs through a non-profit division, the Digital Token Identifier Foundation (DTIF). ^[24][26]

A DTI is "a random, unique combination of nine alphanumeric characters allocated to a digital token", plus a record of reference data about the token: the ledger it lives on, its technical attributes, addresses and names. The standard covers "all fungible digital assets which use distributed ledger technology", and the Foundation describes its mission as providing "golden source reference data" on a non-profit, open-data basis. ^[27] ISO's own committee page notes that the Foundation was set up to provide reference data under ISO 24165, which is maintained by TC 68's reference data subcommittee. ^[26]

Why is having a DTI not an endorsement? Look at the allocation rules. The registry and application process "is open to all". Before allocating a code, the Foundation checks that the token exists and is eligible, and that it has not already been assigned a DTI. ^[25] That is the whole test: existence and uniqueness. There is no assessment of quality, security, legal status or adoption. The analogy is the ISBN on a book. Every book can get one; it tells a library catalogue which book you mean, and nothing about whether the book is any good.

The DTI matters for a different reason: regulators are starting to use it as the standard way to name tokens in reports. The Foundation has proposed DTIs for the Basel Committee's bank disclosure templates on crypto-asset exposures, and secondary coverage reports that DTIs can be referenced for digital tokens in ISO 20022 messages (not verified from a primary ISO 20022 document). ^[27] So the true link between crypto and ISO 20022 is this: a token can be named inside a bank message through its DTI. The message does not move the token, and the standard does not pick winners.

How to read any "ISO 20022 coin" claim

Before you accept a claim that a project is "ISO 20022 compliant", run it through five questions:

1. Which software? The standard describes messages that software produces. Name the product (a gateway, an API, a payment network). If the answer is "the blockchain", the claim is not well formed.
2. Which messages? Compliance with a message standard means producing specific message types (for example pacs.008) that validate against a usage guideline such as CBPR+. A project that cannot name one has not done the work.
3. Who says so, besides the project? A bank that runs it in production, a market infrastructure document, a regulator. Membership of a working group is not a third-party confirmation. ^[3]
4. Is this about the token or about a company? Ripple's RMG seat belongs to Ripple. Verdian's role in TC 307 belongs to a person and a different standard. Neither statement is about a coin. ^[11][22]
5. Would the claim matter even if true? Thousands of bank software products handle ISO 20022 messages. The ability to format a message is not interoperability with banks, and it is not adoption. Adoption is measured in the chapter "Real adoption" of each coin page and in the evaluation rubric.

The short version: ISO 20022 is a dictionary and grammar for bank messages, maintained by Swift as Registration Authority under an ISO committee. The world's payment systems finished migrating to it in 2025 on schedule. No coin was certified, approved or chosen in the process, because the standard has no mechanism to do that. The one real intersection, the DTI, is a catalogue number that any token can obtain. Everything beyond that is a narrative, and the evidence for the eight projects is laid out above so you can judge it yourself.