When the buyer of a token is not the rights owner: what to do first
When the token you bought does not carry the right you expected, treat this as a provenance failure, not a technical glitch. Freeze the wallet interaction, preserve the transaction record, and identify who issued the white paper behind the token. The first few days decide whether a claim against the issuer, the platform, or both stays realistically open.
What actually governs this
The duty to disclose what a token confers sits in Regulation (EU) 2023/1114 (MiCA). It requires an issuer or offeror to state, in the white paper, what rights the token actually attaches to the buyer — and a token that delivers less than the white paper describes is a disclosure problem under that regulation, not a private misunderstanding between two traders.
Regulation (EU) 2023/1113 (TFR) governs the information that must travel with a transfer of crypto-assets. That information is what lets you trace a token back through the chain of custody to the entity that issued it, or to the platform that last controlled it. Without that trail, establishing who owed you the right in the first place becomes much harder.
What changes once the mismatch is confirmed
If the white paper's description of rights does not match what your wallet actually holds, the crypto-asset service provider that processed your purchase has a compliance question to answer under MiCA, independent of any private dispute with the seller. If the transfer that brought you the token lacked the originator and beneficiary information TFR requires, that gap is itself evidence — it shows where the traceability chain broke, and often points to the party who should have caught the mismatch before you did.
What to do, in order
- You, immediately: preserve the wallet address, the transaction hash, and the exact version of the white paper you relied on when buying.
- Your counsel, within days: request the transfer record from the crypto-asset service provider that executed the purchase, citing the TFR information duty.
- A technical adviser: compare the white paper's stated rights against what the token contract actually delivers on-chain.
- Your counsel: notify the issuer or offeror in writing that the token does not match its disclosed rights, and request a correction or a remedy.
- Your counsel: flag the transaction to the platform's compliance desk separately if the TFR-required information is missing or incomplete.
- You, with counsel: decide whether to pursue the issuer, the platform, or both, once the first two responses arrive.
Who decides, and where
A disclosure breach under MiCA is first a matter for the issuer's own compliance function, then for the competent authority responsible for supervising that issuer in its home member state. A traceability gap under TFR is first a matter for the crypto-asset service provider's internal dispute process, since that provider holds the transfer records the authority would otherwise have to request.
| Scenario | Governing rule | Who resolves it first |
|---|---|---|
| White paper misdescribes the token's rights | Regulation (EU) 2023/1114 (MiCA) | Issuer's compliance function, then the competent authority |
| Transfer lacks originator or beneficiary data | Regulation (EU) 2023/1113 (TFR) | The crypto-asset service provider that processed the transfer |
| Secondary-market resale misrepresents the token | Regulation (EU) 2023/1114 (MiCA) | The platform that facilitated the resale |
If your situation differs
If the token was reclassified after issuance as a different type of crypto-asset than the one you were sold, the rights question becomes secondary to a classification question. When a token is classified differently than expected in practice sets out that sequence first, before the rights mismatch is even addressed.
If the issuer no longer exists or cannot be located, the platform's own traceability obligation under TFR becomes the more useful lever than any claim against the issuer.
If you bought on a secondary transfer rather than at original issuance, the disclosure duty for what you received sits with the platform that facilitated the resale, not with the original issuer.
A related sequence worth knowing
What to do first in this situation in practice applies almost the same order of steps when a smart contract's coded permissions disagree with the written licence behind it: freeze, compare, notify, then choose a counterparty.
What this page does not cover
This page does not establish who currently controls the underlying asset behind the token, if there is one. That question sits with a dedicated trace. Asset in Estonia and its limits explains what such a trace can and cannot show.
This page also does not establish whether the counterparty who sold you the token has anything worth pursuing. Debtor in Estonia: what can be established sets out that separate question and its boundaries.
Before commissioning either trace, a short scoping conversation usually clarifies which registries actually apply to your case. Free check overview step by step walks through that first step.
Verified
Checked on 10 March 2025. Both regulations cited above have applied since 30 December 2024. Primary sources: Regulation (EU) 2023/1114 (MiCA); Regulation (EU) 2023/1113 (TFR).
Frequently asked questions
What is the first step when the buyer of a token is not the rights owner?
Preserve the record first: the wallet address, the transaction hash, and the exact white paper version you relied on. Everything that follows depends on being able to show what the token promised against what it delivered.
Which deadline is already running?
No statutory countdown starts automatically under MiCA or TFR for this situation. The deadline that matters in practice is contractual — the limitation period in your purchase terms, and the crypto-asset service provider's own published response window for disputes.
Who decides, and on what evidence?
A disclosure mismatch is decided first by the issuer's compliance function, on the white paper text against the token's actual on-chain behaviour. A traceability gap is decided first by the crypto-asset service provider, on its own transfer records under TFR.