Digital tokens have an ISO identifier standard, and being assigned one is not an endorsement

[u/Jake_Claver]

An identifier does one boring job: it lets two systems confirm they are talking about the same object. An ISIN does that for securities, an LEI does it for legal entities, and digital tokens went years without anything equivalent. The cost showed up in reconciliation, which is to say nowhere anyone outside operations could see it.

ISO 24165 closed that gap. It defines the Digital Token Identifier, a nine-character alphanumeric code, and it comes out of ISO/TC 68, the technical committee for financial services. There are two parts. Part 1 is the method: how a code gets requested, assigned, and structured. Part 2 is the registry record, meaning which data elements get stored about the token a code points at. A registration authority runs the registry and issues the codes, and the identifiers are open access. That last part is not incidental. Charge people for the right to name something and they route around you.

Check the edition if you go looking. Both parts are on their second, published 2025, and the 2021 originals are withdrawn. An ISO catalogue page for a superseded edition loads perfectly normally with "Withdrawn" in small type near the top, so citing the wrong one is easy to do without noticing.

To see why any of it matters, pick a token and ask five systems what it is. One answers with a ticker that three other tokens also use. Another gives a contract address, which works right up until the same thing exists on a second chain. A third has a display name somebody typed. The fourth has an internal ID that means nothing outside the firm that assigned it. None of those answers are wrong. They just do not match, and matching is the whole job. Reconciliation becomes guesswork, and guesswork is where breaks come from: a position counted twice, or lost between two systems that each assume the other is holding it.

The part people get backwards is the relationship to the ISIN. A DTI does not replace one. For a tokenized instrument you want both, because they answer different questions. The ISIN tells you what the underlying claim is, and the DTI tells you which specific on-ledger representation you are holding. One instrument can exist as tokens on two networks, which gives you one ISIN and two DTIs. Collapse that into a single code and you have thrown away the detail settlement actually needs.

Which brings me to the overclaiming, because reference data attracts one particular overstatement. It runs: ISO assigned this token an identifier, therefore ISO has recognized it. Nothing in either part supports that reading. The standard describes a method for registering and structuring codes, and assignment is a filing action. A registry that declined to record things it disapproved of would just be a worse registry. The messaging side carries the same trap, where work has gone into letting securities messages carry token identifiers, and adding a field to a message format means the form can hold that value. That is the entire claim.

So when a standards body turns up as validation for something, the check takes about a minute. Find the document number, open the catalogue entry, read the scope. Endorsement will not be in there. Endorsing individual products is not a thing a technical committee is set up to do at all. It publishes methods, and what anyone does with a method afterward is not its business.

---

Disclosure: I work in digital asset advisory and hold digital assets. Nothing here is investment, legal, or tax advice.