When a token is classified differently than expected: what to do first
A token that turns out to be classified differently than expected under Regulation (EU) 2023/1114 (MiCA) does not sit in limbo while you argue about labels. Treat the new category as operative immediately, stop any communication that assumes the old one, and open a file that tracks every date already running under the revised regime.
Basis
Regulation (EU) 2023/1114 (MiCA) sorts crypto-assets into distinct categories, each carrying its own chapter of duties. A token built for one category can end up matching another once its actual rights, redemption mechanics, or reserve structure are reviewed against the text. The category is not a label the issuer chooses once and keeps; it follows from how the token actually works.
Where the token moves, or is transferred between wallets, information duties under Regulation (EU) 2023/1113 (TFR) attach depending on that same classification. A shift in category can therefore change two things at once: the authorisation route and the information that must travel with each transfer.
What changes in practice
Reclassification is not a formality. It resets which chapter of Regulation (EU) 2023/1114 (MiCA) applies, which in turn resets the notification or authorisation route, the content of the whitepaper, and, for some categories, the reserve and safeguarding duties attached to the token.
Any marketing material, pitch deck, or investor letter drafted for the old category becomes a liability the moment the new category is confirmed. It describes a regime that no longer applies to the asset in the reader's hands.
What to do first
- Legal lead: pull every public communication and disclosure issued under the assumed category and mark which ones describe rights, redemption, or reserve mechanics tied to that category.
- Compliance officer: confirm, in writing, which chapter of Regulation (EU) 2023/1114 (MiCA) now applies to the token as reclassified, and log the date of that confirmation.
- Operations lead: suspend marketing and onboarding material built on the old category until the notification or authorisation for the new one is filed.
- Legal lead: check whether transfer information duties under Regulation (EU) 2023/1113 (TFR) now attach differently, given the new category.
- Compliance officer: file the notification or authorisation package with the competent national authority for the corrected category.
- Where the file being assembled holds personal data on holders or counterparties, run that check in parallel with the Legitimate interest assessment and the deadline, rather than after the notification is already filed.
Who decides
The decision on classification, and on any dispute about it, sits with a defined authority. The table below sets out who rules on what, and through which route.
| Question | Decision-maker | Route |
|---|---|---|
| Final classification of the token | National competent authority for crypto-asset markets | Notification or authorisation file |
| Dispute over the classification reached | Same authority, then national courts on appeal | Administrative review, then judicial appeal |
| Transfer information duties attaching to the token | Same authority, alongside the AML supervisor | Ongoing compliance review, not a one-off filing |
If your case differs
The right next step depends on which direction the reclassification runs.
If the token moves from a general crypto-asset category to one backed by a reserve of assets, then the whitepaper and the reserve evidencing duties attach from the point the new category is confirmed, not from the token's original launch date.
If the token moves toward a category tied to a claim on funds, then the issuer's authorisation status needs checking before any further token is issued or sold.
If a counterparty disputes the reclassification, then the dispute is resolved by the same authority that confirmed the category, not by private negotiation between the parties.
Sources and limit
This page sets out the sequence and the decision-maker. It does not run the classification test itself, and it does not verify facts about a specific counterparty, document, or jurisdiction — that is a separate factual check, not a legal opinion.
Where the open question is whether a named counterparty actually holds the status it claims, that is answered by the Counterparty report estonia, not by this page.
Where the open question is whether a filed document says what it is claimed to say, that is answered by the Document report estonia.
Where the open question concerns the jurisdiction itself, and what can and cannot be established within it, see Jurisdiction in Estonia and its limits.
Verified against the current text of Regulation (EU) 2023/1114 (MiCA) and Regulation (EU) 2023/1113 (TFR) at the time of publication.
Related reading
A related question that follows the same pattern is covered separately: When reserves must be evidenced.
If the category attached to your token has shifted, get the new classification confirmed in writing before the next investor update goes out.
FAQ
What is the first step when a token is classified differently than expected?
Stop any public communication that relies on the old category, and confirm the new one with the competent authority before publishing anything further.
Which deadline is already running?
A notification or authorisation clock starts running from the point the token is offered to the public or admitted to trading under the new category. The exact number of days is fixed by the regulation and confirmed by the authority for the specific filing, not assumed in advance.
Who decides, and on what evidence?
The national competent authority for crypto-asset markets decides, based on the token's actual structure, the rights it grants, and the documentation already filed under Regulation (EU) 2023/1114 (MiCA).