Home /

ISO 20022 Payment APIs and pacs.crypto: Bridging Bank Messages to Blockchain

Quick answer: ISO 20022 is the international standard for financial messaging, and its pacs (Payments Clearing and Settlement) messages, like pacs.008 and pacs.009, are now the language banks use for cross-border payments after SWIFT retired the old MT formats in November 2025. pacs.crypto is a separate, experimental open specification by a former SWIFT standards expert that maps those same ISO 20022 data models onto blockchain payments. It is a community proposal, not an official ISO standard.

Updated 07/17/2026. By Jake Claver. Educational content, not investment advice.

Two payment worlds have grown up speaking different languages. Banks standardised on ISO 20022, a rich, structured messaging format. Blockchain networks built their own transaction formats. The interesting work now is at the seam between them, where people are trying to make the two interoperate without a fragile translation layer in the middle. This is a standards-and-plumbing story, not a signal about any token.

What ISO 20022 and pacs messages are

ISO 20022 is a universal information model for financial messaging, formally the standard for a financial-industry information model and taxonomy. Within it, the pacs family carries interbank payment instructions. The two that matter most for cross-border payments:

  • pacs.008: the financial-institution-to-financial-institution customer credit transfer. It is the ISO 20022 replacement for the old MT103 wire message.
  • pacs.009: the bank-to-bank credit transfer used for the cover leg in correspondent banking, replacing MT202 and MT202COV.

The shift is not theoretical. On the SWIFT network, the coexistence period ended and legacy MT payment messages like MT103 and MT202 were retired in favour of their pacs equivalents in November 2025. ISO 20022 is now the working standard for interbank cross-border payments, which is why the data model behind it has become the reference point for anyone building payment systems, including on blockchain.

Why the model beats the message

ISO 20022’s value is not the file format, it is the shared vocabulary: precise fields for parties, amounts, purpose codes, remittance information, and regulatory data. That richness is what lets a payment carry structured context instead of a cramped free-text line. The ISO 20022 and Web APIs white paper, published in 2025 by the standard’s Technical Support and Registration Management Groups, exists precisely to help implementers define Web APIs on top of those repository models rather than reinventing them. In other words, the same semantics can drive traditional messaging and modern APIs.

What pacs.crypto is (and is not)

That idea is what the pacs.crypto project takes to blockchain. Created by Tom Alaerts, formerly of SWIFT Standards, and shared publicly under a CC0 public-domain dedication, it is a family of five OpenAPI specifications that reuse ISO 20022 field semantics for crypto flows: a Travel Rule and remittance API aligned to pacs.008, a blockchain payment instruction API for bank and corporate flows to virtual asset service providers, a camt-aligned account reporting API for wallets, an exception and investigation API aligned to camt.110/111, and a liquidity management API for own-account transfers. The stated goal is to let the two worlds stop speaking past each other by keeping ISO 20022’s data model, field meanings, and regulatory alignment while adding chain, token, and wallet-address handling.

Two honest caveats. First, pacs.crypto is explicitly an experiment, described by its author as AI-assisted standards design, and it is not an official ISO or SWIFT standard. It is a proposal to learn from, not a deployed rulebook. Second, it does not endorse any particular blockchain or token; it is format plumbing, not an investment thesis. The author’s own announcement frames it that way.

From the source

pacs.crypto GitHub repository screenshot
ISO 20022 and Web APIs best practices white paper closeup

Why this matters for market infrastructure

Interoperability is the whole game in payments. If a blockchain payment can carry the same structured data a bank expects, and satisfy the same compliance fields such as Travel Rule information, then moving value on-chain stops being a separate universe and starts being another rail the existing system can talk to. That is the practical role for distributed-ledger systems that keeps surfacing in BIS work on tokenisation and the future monetary system: not speculation, but shared, trusted, interoperable records. pacs.crypto is one early attempt to draw that bridge in the open. Whether the industry adopts anything like it is an open question.

Common questions

What is ISO 20022?

ISO 20022 is the international standard that provides a universal information model and taxonomy for financial messaging. It defines structured message types, including the pacs family for interbank payments, so systems worldwide can exchange rich, consistent payment data.

What is a pacs.008 message?

pacs.008 is the ISO 20022 financial-institution-to-financial-institution customer credit transfer, essentially the instruction one bank sends another to move a customer’s money, such as an international wire. It replaced the legacy MT103 message on SWIFT.

Is pacs.crypto an official standard?

No. pacs.crypto is an experimental, open-source proposal by Tom Alaerts, a former SWIFT standards expert, released under a CC0 public-domain dedication. It maps ISO 20022 data models onto blockchain payments but is not endorsed by ISO or SWIFT.

Did banks really retire the old MT payment messages?

Yes. The coexistence period for cross-border payments ended and legacy MT messages like MT103 and MT202 were retired in favour of their ISO 20022 pacs equivalents in November 2025, making ISO 20022 the working standard for interbank cross-border payments.

Does this mean a specific crypto token will be adopted by banks?

No. This is about messaging standards and interoperability, not about any token’s value or adoption. It is not investment advice and does not favor any blockchain or asset.

This content is educational only. It is not tax, legal, or investment advice. Check primary sources and speak with a qualified professional before making financial decisions.


Sources

    Jake Claver

    Written by

    Jake Claver

    Family office professional working on how substantial holdings are held, structured and passed on. Qualified Family Office Professional. Finance degree, University of North Texas. Board member, Arkansas Blockchain Council. Author of Wealth in Numbers and Infinite Banking for Crypto Investors.