ISO 20022 is a messaging standard for financial institutions. Here is what it is, who has to use it, and why there is no official “compliant coin” list.
What ISO 20022 is
ISO 20022 is a multi-part international standard for financial messaging, prepared by ISO Technical Committee 68 (financial services). It works as a framework with three parts: a methodology for modelling financial business areas and message flows without tying them to a particular syntax; a central data dictionary of common business items; and design rules for turning those models into XML or, where preferred, ASN.1 schemas. Its catalogue covers payments, securities, trade finance, cards and foreign exchange, and communities of users can define their own message sets on top of it.
In plain terms, it is a shared language for the messages that financial institutions send each other, such as “pay this amount from this party to that party for this purpose”. It is not a network, a coin or a regulation.
Why banks are moving to it
The older message formats used by many payment systems were short and terse. ISO 20022 messages carry richer, structured data, which lets payments be processed, screened and reconciled with less manual work. That is the practical reason banks and market infrastructures have been migrating, and why the change has been scheduled, tested and announced by the networks themselves.
One industry page we read gave 14 July 2025 as the Fedwire migration date (moved from April 2025) and said the coexistence period for many older SWIFT payment messages was due to end on 22 November 2025. Both dates have now passed, and each network’s own notices remain the authority.
Where ledgers fit
Three layers that often get mixed up
One way a ledger can sit behind ISO 20022 messages
The standard sits at the messaging layer. A ledger sits underneath, recording who owns what. They are different layers, which is why the idea of a coin being “compliant” does not parse: there is nothing about a token that a messaging standard can certify.
But the layers can be connected. In South Africa’s Project Khokha, the Reserve Bank’s report records that test payments used the ISO 20022 message format on a Quorum-based ledger. That shows a ledger can be designed to accept and return these messages, usually through a gateway or adapter that translates between formats.
Claims you may see, and what supports them
The table sets four common claims against what we could verify. We rely on the ISO page for the definition, a bank-industry page for the dates and the South African Reserve Bank for the Khokha example. The claim that no certification or registry exists for compliant coins comes from a crypto-industry explainer, so we treat it as a secondary source.
| Claim you may see | What the sources support | Our reading |
|---|---|---|
| “This coin is ISO 20022 compliant” | ISO describes a messaging standard for financial institutions. One explainer says there is no certification process, registry or approved list for compliant coins | Not a meaningful label for a token. Ask which messages, which systems and who certified what |
| “Banks must use these coins because of ISO 20022” | Banks and payment networks have been migrating message formats. Nothing we read requires any bank to use a particular token | Unsupported by the sources we read |
| “The deadline forces everyone onto these coins” | The dates we found concern payment messages: Fedwire’s migration in July 2025 and the planned end of coexistence for many SWIFT payment messages in November 2025 | The deadlines applied to messages, not tokens, and have passed |
| “A ledger cannot carry ISO 20022 data” | The South African Reserve Bank reported that Project Khokha’s payments used the ISO 20022 message format on a Quorum ledger | Not true in general. It depends on the design |
The same explainer notes that a project building technical compatibility with the standard’s data formats is a real but modest engineering achievement, not an endorsement, and that a bank using the standard does not mean banks will buy a particular token.
A better set of questions
When someone says an asset is tied to ISO 20022, you can ask which messages it handles, in which payment system, run by which institution, and who has tested it. You can ask whether the claim is about the token or about a company that happens to participate in standards work. And you can ask what the token is actually used for in the flow, since the message standard works the same with or without it.
For a wider checklist, see our seven questions for crypto projects, and for the consensus designs behind several ledgers often named in these lists, see our consensus comparison.
Sources
- About ISO 20022. ISO 20022 Registration Authority, accessed October 2026.
- ISO 20022: end of formats coexistence for payment messages. Société Générale Securities Services, accessed October 2026.
- What is ISO 20022? The banking standard behind the XRP, XLM and ALGO hype. crypto.news (secondary source), accessed October 2026.
- Project Khokha: Exploring the Use of DLT for Interbank Payments. South African Reserve Bank, with ConsenSys and PwC, June 2018.
This article is our own summary and commentary. The reports remain the property of their authors and publishers; read the originals for full detail. Spotted an error? Tell us. See our editorial policy.