MiCA Marketing Rules: Bitpanda's €70,000 Sanction
Bitpanda's €70,000 sanction shows why a required white paper must precede marketing. Follow the applicable MiCA sequence and avoid blanket assumptions.
Bitpanda's €70,000 sanction illustrates why marketing cannot run ahead of a white paper when MiCA requires one. A white paper is the public document explaining the project, the token holder's rights and obligations, and the risks.
Before launching a token offer, establish which rules apply, then align notification, publication and communications with them.
The Austrian FMA announcement of 14 August 2026 describes a final penalty concerning white-paper timing and marketing. It includes missing required statements and contact information, not simply a failure to file an optional administrative document.
Begin by identifying the offer
MiCA is the EU Markets in Crypto-Assets Regulation. The title II rules discussed here concern crypto-assets other than asset-referenced tokens and electronic-money tokens.
Article 4 sets conditions for public offers and also contains exemptions. Establish whether those rules apply before assigning the same launch checklist to every token.
A digital product passport that provides care information does not become a regulated investment merely because software calls its record a token. Conversely, attaching a product identifier to a financial or redemption arrangement does not settle its legal classification. The rights, transferability and services matter.
Keep the sequence clear
For the relevant white paper, article 8 requires notification and the prescribed explanation at least 20 working days before publication. Under this procedure, notification is not prior approval.
Article 7 governs the marketing itself. Where a white paper is required, marketing must not be disseminated before it is published. The communications must also carry the required information and remain consistent with the white paper.
Article 9 then addresses publication before the offer or admission to trading begins. A team should be able to follow the versions and dates across that sequence, not just point to a current page after the event.
A fictional launch that needs a hold
Consider a fictional company preparing an in-scope public offer for which a white paper is required. Its marketing team has scheduled a campaign, but the white paper is still being revised.
The useful response is to hold the dependent campaign until the applicable sequence is satisfied. Changing the campaign label to “community update” would not answer whether its substance is marketing.
The person responsible for the offer should identify the relevant document version, evidence of notification, publication date and matching communication. If the promised rights change, the team needs to assess the change under the applicable rules before reusing an earlier version.
This is a proposed operating example, not a description of Bitpanda's internal process or a classification of a real luxury offer.
Make the customer's information consistent
A buyer should not receive one promise in an advertisement and another in the document defining the offer. Review the stated rights, risks, issuer and contact route together.
The practical deliverable is a coherent public explanation with the required sequence behind it. A folder of documents cannot compensate for misleading claims, and a standards logo does not establish legal permission.
Frequently asked questions
What did the FMA's Bitpanda sanction concern?
The FMA's 14 August 2026 announcement describes a final €70,000 penalty for MiCA breaches concerning white-paper timing and marketing, including omitted required information.
Does notification mean that the regulator approves the white paper?
Under the title II procedure in MiCA article 8, notification is not prior approval. Do not extend that statement to every category of crypto-asset or imply official endorsement of the offer.
Does every digital product passport need a MiCA white paper?
No. Establish the rights, transferability and applicable regime first. A product-data record, an excluded crypto-asset and an in-scope public offer are not automatically subject to the same requirements.
Our MiCA transition guide explains the broader scoping questions. Use the Galileo documentation when those choices are clear enough to design the supporting product records.