When the issuer and the platform are related: what to do first
A related issuer and platform do not automatically block a token launch. What changes is the disclosure burden and the conflict-of-interest control that must sit behind it. Map the relationship first — ownership, common directors, shared staff, contractual control — before any white paper or listing decision goes ahead. Everything else follows from that map.
The legal basis
Two pieces of EU law govern this situation directly. Regulation (EU) 2023/1114 (MiCA) sets the conduct and disclosure standards for issuers of crypto-assets and for the crypto-asset service providers that run the trading venue where those assets are admitted. It structures obligations differently depending on the type of token involved and on whether the platform itself is authorised as a crypto-asset service provider, but in every configuration it assumes the market will know who stands behind the token and who stands behind the venue.
Regulation (EU) 2023/1113 (TFR) works alongside it. It governs the information that must accompany a transfer of crypto-assets between the parties involved, and it applies regardless of whether those parties are related. A transfer from the issuer's wallet to the platform's own account does not become exempt from that information requirement simply because the two sides share ownership.
Neither instrument prohibits an issuer and a platform sharing management or equity. Both instruments assume the relationship will be disclosed, managed, and recorded — not hidden and not left implicit in a corporate chart nobody outside the group has seen.
What this changes in practice
Once the relationship exists, three things move from optional to mandatory. The white paper required under Regulation (EU) 2023/1114 (MiCA) must describe the relationship in terms an investor can act on, not as a footnote buried in a risk-factors section. The platform's conflict-of-interest arrangements must name this specific issuer and this specific token, not just describe a general policy that could apply to anyone. And every transfer of the token between the issuer and the platform still carries the originator and beneficiary information required by Regulation (EU) 2023/1113 (TFR) — the relationship does not create an exemption from that record.
The underlying concern is straightforward: a platform that lists its own affiliate's token has an incentive to be generous about admission and quiet about risk. Regulators do not assume bad faith, but they do expect the incentive to be written down, addressed, and checked, rather than argued away in conversation once questions start.
What to do first
Work through the list in order. Each step depends on the one before it, and skipping ahead usually means redoing work later.
| Step | Action | Who does it |
|---|---|---|
| 1 | Map every link between the issuer and the platform: equity, directors, staff, contracts, shared premises | Compliance lead, with legal sign-off |
| 2 | Draft or update the conflict-of-interest policy, naming this specific relationship rather than a generic category | Platform's compliance function |
| 3 | Revise the white paper to disclose the relationship in plain, investor-readable terms | Legal counsel |
| 4 | Separate the people who approve issuance from those who approve listing, where headcount allows it | Board or senior management |
| 5 | Confirm that transfer records between the two entities still carry full originator and beneficiary data | Operations, under Regulation (EU) 2023/1113 (TFR) |
| 6 | Keep the mapping, the policy, and the disclosure text on file, dated and version-controlled | Compliance lead |
The mapping in step one is not a formality. A policy that names "affiliated platforms" in general, without naming the actual counterparty, tends to fail the first time anyone reads it against the corporate register. Write down the specific names, the specific stakes, and the specific people who sit on both sides.
Who decides
No single authority pre-approves the relationship itself. The national competent authority responsible for crypto-asset markets reviews the white paper once it is notified, and it can act on a disclosure it finds inadequate, usually by requesting a correction before any more formal step follows. Ongoing conduct — whether the conflict is actually managed, not just documented — sits with the platform's own governance and is tested after the fact, on the paper trail the steps above produce.
That is worth stating plainly: there is rarely a single moment where a regulator signs off on the relationship and the matter is closed. The file has to hold up on its own, on any date it is asked to.
If your situation differs
If the platform is itself authorised as a crypto-asset service provider and the issuer holds equity in it, the conflict-of-interest policy has to name that stake specifically, and the disclosure has to travel into the white paper in the same terms.
If the link is a services contract only, with no ownership and no shared staff, the disclosure can be lighter, but it still has to exist. A contract alone is a relationship for this purpose, even without a single share changing hands.
If tokens are already trading and the relationship was never disclosed, the priority changes. Fix the disclosure gap first, then rebuild the conflict-of-interest file behind it, and expect the correction itself to draw more attention than silence would have.
What this page does not cover
This page sets out the sequence, not the substance of any single jurisdiction's paperwork. Where the issuer or the platform operates through a Netherlands-registered entity, a separate check on the counterparty itself is usually the next practical step: Counterparty report netherlands.
Where the white paper or the conflict policy references specific corporate documents — articles, board resolutions, shareholder registers — those documents need independent verification before anyone relies on them: Document report netherlands.
Where the open question is which authority actually has jurisdiction over the platform's conduct, that depends on where the entity is established and registered, and it is answered separately: Jurisdiction in Netherlands: what can be established.
Verified
Checked against the current text of Regulation (EU) 2023/1114 (MiCA) and Regulation (EU) 2023/1113 (TFR) on 3 March 2025. The people who maintain this methodology are listed here: The people behind the reports.
Related situations
A related question in the same cluster: When a token gives voting rights.
If the relationship is already in place and the white paper is due, get the conflict-of-interest file reviewed before publication rather than after a query from the regulator.
FAQ
What is the first step when the issuer and the platform are related?
Map the relationship in writing — ownership, directors, staff, contracts — before drafting or revising any disclosure. Every later step depends on that map being complete and accurate.
Which deadline is already running?
None starts from the relationship on its own. The clock starts once the white paper is notified under Regulation (EU) 2023/1114 (MiCA), or once a transfer between the parties takes place under Regulation (EU) 2023/1113 (TFR). The relationship itself does not trigger a separate deadline.
Who decides, and on what evidence?
The national competent authority reviews the white paper on the disclosure it contains. Day to day, the platform's own governance decides whether the conflict is actually managed, and it is judged on the mapping, the policy, and the transfer records kept under the steps set out above.