Tracker · Last checked 16 November 2026

ISO 20022 Digital Asset Tracker

Digital asset and stablecoin changes to ISO 20022, tracked filing by filing.

Overview

In June 2026 a payments blockchain asked for stablecoin settlement to be written into the core bank payment messages. The committee turned it down, saying it "would prefer a broader digital asset strategy". On the securities side, changes framed in generic terms have been approved. The tracker follows nine filings, chosen from more than 50 reviewed: three approved, two rejected, three under review and one withdrawn and refiled. None is implemented yet.

Read the deep dive: ISO 20022 Is Quietly Shaping the Future of Stablecoin Payments

Featured filing

CR 1627: Tempo's request to add stablecoin settlement to bank payment messages

Filed on 1 June 2026 with input from Swift, Standard Chartered and ANZ. Rejected by the Payments SEG on 7 July 2026, which said it "would prefer a broader digital asset strategy rather than focusing on stablecoins only". The committee later described it as "rejected but expected to be resubmitted".

See the full entry

The filings

Select a filing to see what it asks for, who is behind it and how the committees responded.

Payments
CR 1627Stablecoin settlement in bank payment messagesCore · Change to existing payment messagesTempo Labs, with input from Swift, Standard Chartered and ANZRejected7 July 2026

What it asks for

Let the core payment messages describe a bank-to-bank payment that settles onchain in a stablecoin. The request adds the wallets on each side, the chain, the token and its Digital Token Identifier, the issuer and its regulator, a cap on the network fee, a new settlement method code (ONCH), the onchain amount, the transaction hash and a finality status.

Scenarios covered

  • Fiat at both ends, with a stablecoin only between the two banks
  • Wallet to wallet, in the same stablecoin throughout
  • Hybrids, with fiat on one side only

Messages affected

Eight: pain.001, pain.002, pacs.002, pacs.008, pacs.009, camt.052, camt.053 and camt.054.

What the committee said

The Payments SEG rejected it as submitted, five weeks after it was filed on 1 June 2026. It recorded four reasons:

  • the scope is too broad, touching many messages without a precise impact analysis;
  • it "would prefer a broader digital asset strategy rather than focusing on stablecoins only";
  • parts of the request duplicate existing ISO functions;
  • some members questioned whether payment messages are the right place for these changes.

What happens next

In October 2026 the Payments SEG described the request as "rejected but expected to be resubmitted". The next deadline for change requests is 1 June 2027.

Why it matters

It is the first formal attempt to write stablecoin settlement into the messages banks already use. Every wallet in its examples is held through a bank.

Source

Versions 1 (as filed) and 2 (with the decision), in the ISO 20022 catalogue of change requests. Related: RA 292.

RA 292Secure Tokenised Asset TransferCore · Proposal for new messagesDigital Transfer Solutions, supported by iso20022.plusUnder reviewWith the RMG since 23 October 2026

What it asks for

Nine new messages and a new business area for issuing and transferring tokenized currencies and securities held in non-custodial wallets. Assets move directly between holders and each transfer is notarised on a ledger. The submitter says existing messages cannot serve this because they "rely on the use of accounts".

Who is behind it

A UK company incorporated in 2023. It forecasts early adoption in 2027 and wider rollout in 2028, and names no adopters, describing them as commercially sensitive.

What the committees said

  • The Swiss community asked for message names, definitions and what "secure" means (25 September 2026).
  • The Securities SEG asked why existing messages are not suitable (2 October 2026).
  • The Payments SEG asked whether it relates to CR 1627. The submitter answered "No".

Why it matters

It is the rival model to CR 1627: self-custody, with no bank in the middle of the transfer. The register shows the next step due by 23 November 2026.

Source

Business justification, version 1.3 (Word document from iso20022.org). Related: CR 1627.

Securities
CR 003059Place of settlement for a digital cash payment systemCore · Change to existing securities messagesSMPG Digital Asset Task ForceApprovedSeptember 2025, for Standards Release 2026

What it asks for

A tokenized security can be paid for on a different ledger from the one it settles on. The request lets the settlement message say where the cash leg settles.

What the committee said

Approved, with the place of the cash settlement system added as an optional field. The group first approved a code called "E-Money Token Cash System", noted that it "does not cover CBDC and crypto currencies", and after the meeting replaced it with a generic one, "Digital Cash Settlement System".

Why it matters

It shows the same instinct the payments committee showed with CR 1627: one label for every form of digital cash, in place of one label per product.

Source

Swift Common Standards Working Group minutes for Standards Release 2026, dated 21 September 2025 and listed as CR 1519 in the ISO 20022 catalogue of change requests.

CR 003117E-money tokens as a means of payment in securities settlementCore · Change to existing securities messagesSMPG Digital Asset Task ForceApprovedSeptember 2025, for Standards Release 2026

What it asks for

Identify an e-money token used to pay for a tokenized security by its Digital Token Identifier and a quantity. The request notes that under the EU's MiCA regulation "fiat-referenced stablecoins (called e-money tokens) are explicitly treated as e-money".

What the committee said

"The SWG approved the addition of a settlement quantity of stable coin as a means of payment for securities token". It kept the traditional settlement amount mandatory: the fiat equivalent for a one-to-one e-money token, or zero for other stablecoins.

Why it matters

A stablecoin payment field was approved for securities messages months before CR 1627 was rejected in payments. The securities group kept the fiat amount mandatory, where Tempo proposed making it optional.

Source

Swift Common Standards Working Group minutes for Standards Release 2026, dated 21 September 2025 and listed as CR 1519 in the ISO 20022 catalogue of change requests.

CR 003206Balance code for digital assets held before releaseCore · Change to existing securities messagesUnited KingdomApproved24 August 2026, redefined

What it asks for

A new balance code for digital assets that are "blocked and in quarantine before becoming available", so they can be reported separately from other blocked positions.

What the committee said

Approved in principle, with the chair recording: "Avoid DLT-specific wording." The code is redefined as "Blocked pending account servicer validation".

Why it matters

The need was accepted and the digital-asset framing was removed. The working group noted that the asset "is not blocked on the DLT itself" but inside the account servicer's own systems.

Source

Swift Settlement and Reconciliation paper for Standards Release 2027, final minutes, September 2026, listed as CR 1635 in the ISO 20022 catalogue of change requests.

CR 003255Custody account and blockchain wallet on one messageCore · Change to existing securities messagesDTCCRejected27 August 2026

What it asks for

Remove a rule, introduced in 2021, that lets corporate action and settlement messages carry either a safekeeping account or a blockchain wallet, but not both. DTCC needs both for its tokenization service.

What the committee said

The working group "agreed that the business case is valid and requires further work", but the proposed solution "did not receive sufficient support". It was rejected for this cycle and sent back for wider industry discussion.

Why it matters

Swift's comment names the risk: with both identifiers present, an account servicer cannot reliably tell whether they refer to the same holder. Tokenized securities need a rule for linking wallets to accounts.

Source

Swift Common Standards Working Group paper for Standards Release 2027, version 2.0, issued 11 September 2026, in the ISO 20022 catalogue of change requests.

RA 265Primary Bond MarketsAdjacent · Proposal for new messagesICMA and SwiftUnder reviewWith the Securities SEG since 23 October 2026

What it asks for

Messages for the bond issuance workflow, from announcement and bookbuilding through to closing, built on ICMA's Bond Data Taxonomy. The filing says the taxonomy has supported DLT bond issuance since January 2024 and is being implemented "both for traditional debt securities as well as tokenised debt securities".

Who is behind it

ICMA's working group of more than 70 firms, including issuers, banks, investors and the international depositories.

What the committees said

FIX, the trading-protocol body, objected in July 2025 to an XML-only scope, since FIX already carries investor orders and allocations. A revised scope is now with the Securities SEG.

Why it matters

Tokenized bonds would use these mainstream messages with no separate token standard. That is why it is listed as adjacent: digital assets are covered, though they are not the purpose.

Source

Business justification, version 3 (Word document from iso20022.org).

Regulatory reporting
RA 258Crypto-Asset ReportingCore · Proposal for new messages · Required by EU lawESMAUnder reviewAccepted for consideration 3 December 2024

What it asks for

Three messages for the records that crypto-asset service providers must keep under the EU's Markets in Crypto-Assets Regulation: orders, transactions, and the order book of a trading platform (Articles 68 and 76). They reuse existing regulatory reporting messages where possible and add concepts for digital tokens.

Who has to use it

Every provider subject to the reporting duty, the national regulators and ESMA. Adoption follows from the regulation, not from a business case.

Status caution

The messages were due to the Registration Authority by November 2024 and the register has not moved since December 2024. For the formats in use, check ESMA's MiCA page.

Source

Business justification, version 1 (Word document from iso20022.org). Replaces part of RA 249.

RA 249Crypto-Asset data and Metadata ExchangeCore · Proposal for new messagesESMAWithdrawn11 October 2024, refiled

What it asked for

One filing covering the three MiCA messages and a metadata message for the EU's single access point for financial data. ESMA wanted the MiCA messages in JSON.

What the committee said

The Swiss community objected: ISO 20022 does not yet support JSON as a syntax, and ESMA had no fallback for its January 2026 start date. It suggested splitting the filing and using XML for MiCA.

What happened next

ESMA withdrew the filing and split it. RA 257, the metadata message, was registered and published on 23 April 2025. The MiCA messages continue as RA 258.

Source

Business justification, version 5 (Word document from iso20022.org).

Upcoming milestones

Dates come from the ISO register and the published maintenance calendar. None is a promised decision date.

  • RA 292: next step due on the ISO register.
  • Next quarterly update of this tracker.
  • ISO publishes new message versions from the 2026/2027 maintenance cycle.
  • Deadline for change requests to the 2027/2028 cycle. This is the earliest route for a resubmitted or broader version of CR 1627.
  • Swift's deferred Standards Release 2026 is scheduled to go live for securities and other non-payment messages. CR 003059 and CR 003117 were approved for that release.
  • Earliest publication of any change filed by June 2027.

Changes by quarter

Newest first. The tracker is updated every quarter.

Q4 2026
  • RA 292 returned to the RMG after the submitter answered reviewer comments.
  • RA 265 went to the Securities SEG with a revised scope.
  • The Payments SEG described CR 1627 as "rejected but expected to be resubmitted".
Q3 2026
  • Swift working-group papers recorded CR 003255 as rejected and CR 003206 as approved under a new name.
  • CR 1627 rejected by the Payments SEG.
Q2 2026
  • CR 1627 filed by Tempo Labs.
Earlier
  • CR 003059 and CR 003117 approved by the securities working group for Standards Release 2026.

How to read the statuses

A filing, an approval and a working standard are three different things. Each entry sits at one of five stages.

Submitted

Filed and logged. No committee response yet.

Under review

With a committee, or back with the submitter to develop.

Rejected

Declined by the committee responsible. It can be resubmitted.

Approved

Accepted by the committee or working group. Not yet in the published standard.

Implemented

Published in the standard. Use by banks is a further step, noted where known.

"Withdrawn" marks a filing pulled by its own submitter.

How a filing becomes a standard

There are two routes, and nothing is a standard until it is registered and published.

New messages

  1. The submitter files a business justification.
  2. The Registration Management Group (RMG) reviews it and members comment.
  3. Once approved, the submitter develops the messages.
  4. A Standards Evaluation Group (SEG) evaluates them.
  5. Approved messages are registered and published.

Changes to existing messages

  1. The submitter files a change request by 1 June.
  2. The SEG responsible approves or rejects it and records why.
  3. Approved changes are published as new message versions the following April or May.

Method and limits

Entries are taken from documents published on iso20022.org: the register of submissions, the catalogue of change requests and the Swift working-group papers filed there. Each entry was read in full at source and quotations are verbatim. "Core" means the filing exists for digital assets. "Adjacent" means a mainstream proposal that explicitly covers tokenized instruments.

The tracker covers the fifty most recent proposals for new messages, back to 2020, the change requests of the 2026/2027 maintenance cycle, and two approvals from the cycle before. Earlier filings are being added. Statuses are those shown by ISO on the last-checked date and can lag events.

Enterprise Onchain is independent and is not affiliated with ISO, the ISO 20022 Registration Authority or Swift. Spotted an error or a missing filing? Email [email protected].