How Crypto Got Into ISO 20022 Through the Back Office

• ISO’s FAQ says no cryptocurrency is inherently ISO 20022 compliant, and no certification authority exists.
• Tokens enter ISO 20022 messages as ISO 24165 Digital Token Identifiers.
• Standards Release 2025 added ledger and token identifiers for places of settlement and safekeeping, a 140-character blockchain cash wallet field and a smart contract price source to securities messages.
• The digital cash settlement and e-money token fields approved for Standards Release 2026 now go live on 12 June 2027.
• Pontes, live since 21 September 2026, moves euros between T2 and its DLT cash wallets with pacs.010, pacs.002 and pacs.009 messages.

ISO settles the “ISO 20022 coin” question in its own FAQ. “Cryptocurrencies are not inherently ISO 20022 compliant,” the page reads, and it adds that they “are not managed and not registered by ISO 20022.” The same FAQ says the standard has no official certification authority. There is no register for a token to appear on and no stamp for a project to earn.

Crypto vocabulary has entered the standard anyway, through the securities back office. Since 2024, the working groups that maintain settlement and custody messages have approved fields for Digital Ledger Identifiers, blockchain wallet addresses, smart contract price sources, e-money token payments and network fees. The latest requests came from the Securities Market Practice Group’s Digital Asset Task Force, and they serve custodians settling tokenized bonds against cash that sits on a second ledger.

A token reaches ISO 20022 as an identifier, an address or a quantity inside a message between regulated institutions, and the ledger does the moving. The Eurosystem’s Pontes service, live since 21 September 2026, funds its DLT cash wallets with the same pacs messages T2 already processes. None of this work involves the coins sold to retail buyers as ISO 20022 compliant.

The future of finance is here. Trade crypto and more

What ISO 20022 standardizes and who maintains it

ISO 20022 is a modeling methodology and a repository built under TC 68, ISO’s financial services committee. Business areas, transactions and message flows are captured “in a syntax-independent way,” stored in a data dictionary and a business process catalog, and turned into message definitions. Design rules then generate XML or ASN.1 schemas from those definitions. The pacs, camt, sese and semt messages that banks and custodians exchange are registered definitions, each describing a business event such as a credit transfer, a statement or a settlement instruction.

Governance runs through registration bodies. ISO TC 68/SC 9 oversees the standard, the Registration Management Group supervises registration, and Standards Evaluation Groups for payments, securities, cards, FX, trade finance and API resources validate new message definitions from a business perspective. Ripple announced in June 2020 that it had joined the RMG as its first member focused on distributed ledger technology. ISO’s membership criteria ask an applicant to show it brings together a community of users. Membership gives Ripple a voice in how messages are registered, and XRP’s standing in ISO 20022 is the same as every other cryptocurrency’s.

The FAQ confirms that cryptocurrencies “can be transported as data content in the ISO 20022 messages but are not validated.” Fiat currencies are checked against ISO 4217 codes, and a crypto ticker in the same position passes through as text the receiver has to interpret. Exchanges and payment processors can implement ISO 20022 for their dealings with banks, and the FAQ allows that a blockchain company can be compliant on those terms. That compliance belongs to the company’s message formatting and extends to no token it lists.

ISO 20022 migration in CHAPS, CHIPS, Fedwire and CBPR+

The Bank of England moved CHAPS to ISO 20022 on 19 June 2023. CHIPS switched on 8 April 2024 and released 555,345 payments worth $1.81 trillion on its first day. The Federal Reserve implemented the format for the Fedwire Funds Service on 14 July 2025. Swift ended CBPR+ coexistence on 22 November 2025, the date set for FIN to stop delivering MT payment instructions between financial institutions.

For a tokenization platform in Britain, a sterling redemption through CHAPS now arrives as ISO 20022. A dollar redemption in the United States does the same, whether it clears through CHIPS or settles on Fedwire. Data alignment continues on top of the format. The CPMI updated its harmonized data requirements for cross-border payments on 26 February 2026 and gives adopters flexibility until the end of 2027.

Digital Token Identifiers under ISO 24165

Tokens take their identifiers from ISO 24165-1, whose second edition was published on 5 May 2025. It defines a random, unique, fixed-length identifier for digital tokens, assigned in response to a registration request. The DTI Foundation, a non-profit division of Etrading Software, is the registration authority. Each DTI pairs a nine-character alphanumeric codewith reference data on the ledger the token is deployed on and its technical attributes, such as address and name. The foundation pitched that record to the Basel Committee in January 2024, responding to its consultation on cryptoasset exposure disclosures, as golden source reference data for identifying tokens.

The code identifies a token on a ledger, and whether that token is a security, an e-money token or another crypto-asset is settled by the law that governs it.

The implementing regulation on MiCA white paper templates, adopted on 29 November 2024, includes a field for the ISO 24165 DTI of each crypto-asset “where available.” A second field takes the functionally fungible group DTI, and LEI fields cover offerors, issuers and operators. Under MiCA, the same DTI fields appear in the templates for asset-referenced tokens and e-money tokens.

A tokenized bond ends up with several identifiers, and a custodian needs all of them linked in its master data. An LEI names the issuer, an ISIN names the instrument, a DTI names each token representation, a ledger identifier names the platform used as place of settlement, and a contract address tells the gateway where to send the transaction. A bond issued on two ledgers would carry one ISIN and a DTI for each deployment, and the functionally fungible group DTI exists to tie such deployments together.

Buy bitcoin and stocks. Signup to Coinbase today

Standards Release 2025 changes for ledgers, wallets and oracle prices

The first DLT fields came through the Standards Release 2025 cycle. The discussion paper and minutes, finalized on 31 October 2024, record the decisions for the MT messages and their ISO 20022 equivalents.

CR 002137 created new data types for place of settlement and place of safekeeping. A settlement instruction that used to name a central securities depository can now name a ledger or a token, with DLID and DTID proposed as the codes. The change reaches MT 508, 524, 535 to 548, 578 and 586, semt.002 and semt.003, the sese.020 to sese.040 range and the corporate action messages, and it covers private permissioned platforms and public chains.

CR 002154 dealt with field length. Cash account fields held 35 characters, and the working group noted that “an Ethereum address has 42 characters.” The approved Block Chain Cash Wallet option, BCCW in field 97D, holds 140.

CR 002142 added SCAS, the Smart Contract Automated Pricing System, as a price source, again with room for a 140-character blockchain address. The code now sits in the price source list for MT 535, the statement of holdings, and the change was flagged for semt.002, semt.003 and semt.017 on the ISO 20022 side. A fourth request, CR 002150, proposed a DLTP place code for ledger platforms and was withdrawn, since CR 002137 already covered it.

Standards Release 2026 changes for digital cash settlement

Both change requests came from the Digital Asset Task Force. The first covers delivery of a tokenized asset where the cash settles on a different DLT platform from the security, the use case set out in the working group’s July 2025 paper. The second covers payment in e-money tokens, and the paper grounds it in MiCA, under which fiat-referenced stablecoins issued as e-money tokens are treated as e-money.

CR 003059 adds a place of settlement for that cash. The working group first drafted a code for an E-Money Token Cash System, EMCS, then chose a generic one. The minutes dated 21 September 2025 record approval of DCSS, the Digital Cash Settlement System, identified by a DLI, a BIC or an LEI. The scope covers MT 540 to 548 and related statements, semt.017 to semt.019, sese.020 to sese.040 and a long list of setr fund order messages.

CR 003117 identifies the e-money token used as payment, by DTI, together with its quantity. The group made the payment sequence repeatable up to twice. One occurrence can carry the e-money token amount and the other the network fee. When the token is an EMT, the minutes say, “the equivalent fiat cash amount will be included as the ratio is 1 to 1 with the FIAT currency.” The format assumes par. A token trading below its peg leaves the custodian reconciling a fiat amount the market is no longer paying.

Corporate action messages stayed out of CR 003117 until a firm requirement appears, although the minutes acknowledge that a holder of securities tokens could receive dividends and interest in digital assets. Discussion of the collateral messages, MT 504, 505, 507, 527, 558 and 569 and colr.020, moved to Standards Release 2027.

The 2026 changes were scheduled for November. Swift postponed the November release in late August 2026 and decoupled the securities changes from payments. Clearstream confirmed on 1 October that the securities and funds changes go live on 12 June 2027. The EU, UK and Swiss T+1 bodies called the move a technical scheduling adjustmenton 22 September and kept their transition date of 11 October 2027.

The future of finance is here. Trade crypto and more

ISO 20022 message families mapped to token workflows

Most of the token lifecycle in regulated markets maps onto messages that already exist. The table pairs each family with the workflow it can carry and the step a ledger or gateway still performs.

The mapping holds when the token represents something the messages already describe, such as a bond, a fund unit or a deposit. Staking rewards, slashing, liquidity pool positions and protocol governance votes have no counterpart in sese or seev. A custodian that forces them into settlement or corporate action fields gets messages that pass schema validation and carry no agreed meaning.

Swift and Pontes connect bank messaging to ledgers

In a trial completed in January 2026, Swift worked with BNP Paribas Securities Services, Intesa Sanpaolo and Société Générale on delivery-versus-payment settlement, interest payouts and redemption of tokenized bonds, settling in fiat and in stablecoins. SG-FORGE, the bank’s digital asset subsidiary, supplied the bond and its EURCV stablecoin, and the other two banks acted as paying agents and custodians. Swift said the trial “showcased the integration of ISO 20022 messaging standards with blockchain-native platforms.”

Swift is building a ledger of its own as well, first announced at Sibos in September 2025 and designed with more than 30 banks. It completed the design phase in March 2026. The ledger runs on Hyperledger Besu, an open-source EVM-compatible platform, and builds on existing bank payment applications and Swift standards. In July, Swift reported seventeen early adopter institutions preparing to pilot live transactions. The first use case is cross-border payments in tokenized deposits, which Swift chose as a familiar, regulated form of commercial bank money.

The Eurosystem launched Pontes on 21 September 2026 to settle wholesale tokenized asset transactions in central bank money. It builds on the Eurosystem’s 2024 exploratory work, in which 64 participants ran more than 50 trials and experiments between May and November. Thirteen institutions completed onboarding for the start, including Deutsche Bank, Santander, Société Générale, KfW and the European Investment Bank, alongside four DLT operators, Axiology, Cashlink, Clearstream and SWIAT. The ECB expects full implementation by 2028.

The ECB’s technical briefing on the initial launch shows where ISO 20022 sits. A participant requests funding for its Dedicated Cash Wallet on the Eurosystem’s permissioned ledger. A pacs.010 direct debit draws on its RTGS dedicated cash account in T2, and T2 returns a pacs.002 status. A pacs.009 credit transfer then moves the amount to a technical account, and cash tokens are issued to the wallet. Defunding runs the sequence in reverse. The cash tokens are intraday only, and the service runs from 08:00 to 16:00 on opening days.

For transactions that must complete on both sides or not at all, Pontes relies on the Hash-Link protocol. Market DLT platforms have to be able to lock an asset transfer conditionally until a secret key is provided. The atomicity lives in that lock. The pacs messages handle the euro’s trip from T2 onto the Eurosystem ledger and back.

A tokenized bond that trades around the clock can settle against Pontes cash for eight hours on an opening day.

Running a gateway between ISO 20022 and a ledger

Any institution connecting bank messaging to a chain runs a gateway, and its records decide whether reconciliation works. One ISO 20022 instruction can produce several ledger transactions, such as a token approval, the transfer and a fee payment. One batched ledger transaction can also settle many economic transfers. The correlation record has to tie the business message identifier to the trade, every transaction hash, the contract events and the custody booking, in both directions.

Buy bitcoin and stocks. Signup to Coinbase today

Quantities need two representations. A token contract stores integer base units with a decimals setting, and a message carries a business quantity. The gateway converts between them against the contract’s metadata, and a wrong decimals value moves an amount by orders of magnitude.

A 140-character BCCW field holds the string. Whether the address is self-hosted, held by a custodian, governed by a multisignature scheme or a smart contract, and who controls it, sits in master data the message never carries. Message authorization and transaction signing need separate approvers, and HSM or MPC key policies stay outside ISO 20022.

Status needs a written policy. A ledger transaction moves from broadcast to inclusion in a block to protocol finality, and the gateway has to decide which state triggers a sese.024 status update and which releases the sese.025 confirmation.

Settlement finality, Travel Rule data and legal classification

A settlement confirmation reports a state the infrastructure’s rules define. CPMI-IOSCO Principle 8 requires an FMI to provide “clear and certain final settlement, at a minimum by the end of the value date,” and to identify the point after which unsettled payments can no longer be revoked. On a public chain, the rulebook has to tie the gateway’s chosen ledger state to that legal point. A sese.025 confirmation issued before the mapped point reports a settlement the law has yet to recognize.

The EU’s Transfer of Funds Regulation, applicable since 30 December 2024, requires the originator’s CASP to send the originator’s name, distributed ledger address, address or identification details and LEI where one exists. The beneficiary’s name and ledger address travel with them. Between VASPs, the common data model for that information is IVMS 101, first released in May 2020 and maintained by the interVASP Standards Working Group since April 2023. Travel Rule checks have to clear before a transfer is signed, since a public chain offers no recall once it is broadcast.

FATF’s seventh targeted update, published on 16 July 2026, still flags the misuse of stablecoins, peer-to-peer transfers through unhosted wallets, offshore VASPs and DeFi arrangements as risk areas.

Staff of three SEC divisions said on 28 January 2026 that “the format in which a security is issued or the methods by which holders are recorded (e.g., onchain vs. offchain) does not affect application of the federal securities laws.” A token that maps neatly into sese.023 is a security, an e-money token or something else under the law that governs it, and the mapping decides none of it.

Open items through June 2027

Swift’s early adopters are due to run live tokenized deposit transactions during 2026, the timeline Swift set in March. Pontes adds features and longer operating hours on the way to full implementation in 2028, and the Eurosystem’s longer-term track, Appia, is due to deliver a blueprint by the same year. On 12 June 2027 the digital cash settlement fields go live, and a custodian can settle a tokenized bond against an e-money token in a standard message.

Several pieces stay open after that date. Collateral messages wait for the 2027 cycle, corporate actions paid in digital cash wait for a firm requirement, and legal finality for a public chain transaction stays with each infrastructure’s rulebook and governing law. ISO’s blockchain committee, TC 307, published ISO/TS 23516 in March 2026, a framework for interoperability between DLT systems and between a ledger and entities outside it. It sits in a different catalog from the financial messages, maintained by a different committee.

The future of finance is here. Trade crypto and more