When a token claims to carry a licence: what to do first
A marketing claim that a token "carries" a licence is not evidence of anything. It is a sentence written by someone with an interest in the sale closing. The first task is to separate the token record from the underlying right and check that right's origin before any payment moves, not after.
Scope varies sharply by registry and jurisdiction, and the sequence below assumes you already know roughly which one applies. A quick view of that scope is set out in the Coverage map overview in detail, which is worth a look before you commit time to a specific check.
What the claim actually rests on
Two EU instruments frame this situation directly. Regulation (EU) 2023/1114 (MiCA) governs the issuance and marketing of crypto-assets and sets out which entities need authorisation before they offer them to the public. Regulation (EU) 2023/1113 (TFR) governs the information that must accompany a transfer of crypto-assets, which is what makes a token's origin traceable rather than assumed on trust.
Neither instrument turns a token into a licence. Authorisation under MiCA concerns the issuer and the service provider that moves the asset, not the content of the right the token is said to represent. An issuer can be fully authorised and still misdescribe, or overstate, what is actually attached to the token it sells.
This gap between authorisation status and licence content is exactly where disputed claims tend to sit. A token can pass every regulatory check on the issuer side and still fail on the substance of the right.
What changes once the claim is made
Once a seller states that a licence is attached, the buyer's position shifts from an ordinary purchase to reliance on a representation. That representation carries consequences if it turns out to be wrong, and those consequences do not wait for the buyer to notice.
Any limitation period tied to a defective sale usually starts running from the point the buyer had, or reasonably should have had, the means to discover the defect. In practice that is often the moment the claim was first checked, not the moment of purchase. Delay in checking is therefore a risk in itself, separate from whether the licence turns out to be genuine.
What to do first
- Request the licence document itself from the issuer, addressed to the issuer directly rather than to the seller or the marketplace listing it.
- Confirm whether the issuer appears among entities authorised for the relevant activity under MiCA, using the issuer's own registration reference rather than a badge on a website.
- Trace the transfer information that should accompany the crypto-asset under TFR, to establish who actually moved the token, and when, independent of the seller's account.
- Instruct counsel to compare the token's smart contract terms against the scope of the licence document, clause by clause, not summary against summary.
- Hold payment or route it through escrow until the licence document and the token's on-chain terms are reconciled in writing.
- Record every discrepancy you find before raising it with the counterparty, so the record predates the dispute rather than following it.
Signals and what they actually mean
| Signal | What it actually means | Immediate step |
|---|---|---|
| Seller states the token "carries" a licence | A marketing description, not a verified fact | Request the licence document from the issuer |
| Token is listed on a secondary marketplace | The marketplace is not the issuer and cannot confirm the licence | Verify authorisation status with the issuer directly |
| No verifiable issuer identity is available | Provenance cannot be established from the record alone | Stop payment and escrow the price |
| Licence wording differs from the smart contract terms | Two documents, not one right, and they may not agree | Have counsel reconcile both before paying the balance |
Who decides, and on what evidence
A dispute over the underlying right is usually resolved by whichever forum the licence agreement itself names, where one exists. Absent such a clause, jurisdiction typically follows the issuer's registered seat rather than the buyer's location, which matters if the issuer sits in a different member state.
Evidence turns on the licence document, the transfer record required under TFR, and the smart contract terms, read together. The marketing description that started the transaction carries little weight once a dispute is formally raised, because it was never the operative document.
If your situation differs
If the issuer is properly authorised under MiCA but the licence document itself does not match the token's contract terms, treat this as a contractual dispute about scope, not a regulatory failure requiring a supervisory complaint.
If the token was issued directly under an offering document and the accuracy of that document is itself in question, that is a separate line of inquiry: see When the offering document is questioned in practice.
If no issuer can be identified at all, treat the transaction as unresolved provenance and do not complete payment regardless of price pressure from the seller or the deadline they quote.
What this page does not cover
This page sets out the sequence, not the outcome for a named counterparty. It does not tell you what a specific debtor or asset actually holds today.
Confirming what a specific asset actually holds, and how exposed it already is, needs a dedicated check rather than a general sequence: see Asset in Lithuania and its limits.
Confirming exposure tied to a specific debtor calls for the equivalent check on the other side of the transaction: see Debtor in Lithuania: sources, route and limits.
Verified
Checked against Regulation (EU) 2023/1114 (MiCA) and Regulation (EU) 2023/1113 (TFR) as published on EUR-Lex. Both instruments apply from 30 December 2024. This page does not rely on any national implementing measure, case law, or supervisory decision beyond these two instruments, and it does not state a fee, a deadline in days, or a specific forum name, because none of those is confirmed for this situation.
Related situations
A closely related question arises when the person selling the token is not the rights owner at all, which changes the first step considerably: see What to do first in this situation in practice.
If you are holding a token with a disputed licence claim and payment has not yet cleared, a partner responds within minutes during business hours to set out next steps. A written quote for the underlying check follows within one business day.
FAQ
What is the first step when a token claims to carry a licence?
Separate the claim from the record. Request the licence document from the issuer directly and hold payment until it is produced and checked against the token's own contract terms, rather than against the seller's summary of it.
Which deadline is already running?
No fixed number of days is confirmed for this situation. What is confirmed is the mechanism: a limitation period tied to a defective sale typically starts from the point the defect could reasonably have been discovered, which argues for checking early rather than waiting for a formal dispute to force the issue.
Who decides, and on what evidence?
The forum named in the licence agreement decides, where one exists. Absent such a clause, the issuer's registered seat usually governs. The decision turns on the licence document, the transfer record, and the contract terms read together, not on the marketing claim that started the sale.