MiCA Compliance for Crypto Launchpads: CASP Licenses, White Papers and Exemptions

Since 30 December 2024, the Markets in Crypto-Assets Regulation — Regulation (EU) 2023/1114, usually shortened to MiCA or MiCAR — has applied across the European Union to anyone issuing, offering, or providing services related to crypto-assets in the Union (Article 2(1)). For a launchpad or IDO platform, that reach is not abstract. MiCA compliance now shapes who can run a token sale targeting EU investors, what the project has to publish before the sale, and whether the platform itself needs a license.

This guide walks through the two separate compliance tracks MiCA creates for launchpads — CASP authorisation for the platform, and white paper obligations for the project — plus the exemptions, transitional periods, and the parts of MiCA that are still genuinely unsettled. MiCA sits alongside a broader patchwork of national and cross-border crypto rules; our overview of how regulation is reshaping crypto launchpads more generally, and our look at how the US is approaching the same problem through the SEC's framework for token sales and the proposed CLARITY Act, are useful points of comparison for a global launchpad weighing where to seek authorisation first.

What MiCA Actually Regulates

MiCA applies to natural and legal persons engaged in the issuance, offer to the public, or admission to trading of crypto-assets, and to anyone providing crypto-asset services in the Union (Article 2(1)). It does not apply to crypto-assets that qualify as financial instruments, deposits, funds (unless they qualify as e-money tokens), or to crypto-assets that are "unique and not fungible with other crypto-assets" — the regulation's attempt to carve out most NFTs (Article 2(3)–(4)). Regulation (EU) 2023/1114 entered into force in June 2023, but most of its provisions — including the launchpad-relevant Titles II and V — only started applying from 30 December 2024 (Article 149(2)); the issuer-of-stablecoin rules in Titles III and IV applied earlier, from 30 June 2024 (Article 149(3)).

Does a Launchpad Need CASP Authorisation Under MiCA?

Article 59(1) states plainly: "A person shall not provide crypto-asset services, within the Union, unless that person" is authorised as a crypto-asset service provider (CASP) under Article 63, or is a passported credit institution, investment firm, or similar entity under Article 60. The list of "crypto-asset services" in Article 3(1)(16) includes, among others, custody and administration, operating a trading platform, exchange of crypto-assets for funds, execution of orders, and — the one that matters most for launchpads — "placing of crypto-assets," defined in Article 3(1)(22) as "the marketing, on behalf of or for the account of the offeror or a party related to the offeror, of crypto-assets to purchasers."

That definition is close to a description of what a launchpad does: it markets a project's token to a pool of registered users on the issuer's behalf. If an EU-facing launchpad is doing that marketing itself — running the sale page, managing allocation, taking funds — rather than simply hosting a link to the issuer's own sale, it is a strong candidate for falling inside "placing of crypto-assets" and therefore needing a CASP license under Article 63, with a registered office and place of effective management in a Member State and at least one EU-resident director (Article 59(2)). MiCA does not include a launchpad-specific exemption from CASP authorisation — this is an interpretation of how the general service categories apply, not a dedicated launchpad article, so platform structure should be reviewed case by case with counsel and, where available, a national competent authority.

For any IDO platform, including a decentralized launchpad such as Kommunitas Launchpad, the useful exercise is to map who the counterparty is at each step, who markets the token, and who is responsible for distributing it. That mapping relies on the same records a KYC and whitelisting process is built to support, regardless of which jurisdiction's rules eventually apply to a given sale.

White Paper Obligations for Token Issuers (Title II)

The second compliance track sits with whichever party is actually running the token sale — the same party our founder's guide to IDOs and IEOs walks through when comparing launch models and their compliance overhead. Separately from the platform's own authorisation question, Title II of MiCA governs the offeror — defined in Article 3(1)(13) as "a natural or legal person, or other undertaking, or the issuer, who offers crypto-assets to the public." The offeror is not automatically the launchpad; it is whoever is actually offering the token, which in most IDOs is the project team itself, even when a launchpad executes the marketing and allocation.

Under Article 4(1), a person cannot make an offer to the public of a crypto-asset (other than an asset-referenced token or e-money token, which fall under Titles III and IV instead) in the EU unless it:

• is a legal person;
• has drawn up a crypto-asset white paper under Article 6;
• has notified that white paper to its home Member State's competent authority under Article 8, at least 20 working days before publication;
• has published the white paper under Article 9;
• has prepared any marketing communications in line with Article 7, and published them under Article 9;
• complies with the offeror conduct obligations in Article 14 (act honestly and professionally, communicate fairly, manage conflicts of interest, maintain security standards).

Article 6 sets out what the white paper has to contain: information about the offeror, the issuer (if different), the project, the token, the rights attached to it, the underlying technology, the risks, and — notably — the "principal adverse impacts on the climate" of the token's consensus mechanism. It must carry a mandated first-page disclaimer that no competent authority has approved it, and it cannot assert anything about the token's future value (Article 6(2)–(5)). Retail purchasers who buy directly from the offeror (or from a CASP placing the token on the offeror's behalf) also get a 14-calendar-day right of withdrawal with no fees or justification required (Article 13).

Exemptions From the White Paper Requirement

MiCA does not make every token sale go through the full white paper process. Article 4(2) removes the notify/publish obligations — but not the "legal person" and Article 14 conduct requirements — for three categories of offer:

A broader set of exemptions in Article 4(3) removes the whole of Title II, not just the notification/publication steps, for offers that are: (a) offered for free, (b) automatically created as a reward for maintaining the distributed ledger or validating transactions (e.g., mining/staking rewards), (c) utility tokens giving access to a good or service that already exists, or (d) tokens usable only within a limited network of merchants contracted with the offeror. The "free" exemption has a sharp edge for launchpads running airdrops or social-task campaigns: Article 4(3) explicitly states a token is not considered free if purchasers must hand over personal data in exchange for it, or if the offeror receives any fee, commission, or non-monetary benefit for it — a common structure in "complete these tasks to claim" airdrops. The limited-network exemption also requires the offeror to notify the competent authority if the offer exceeds €1,000,000 over 12 months, explaining why it still qualifies (Article 4(3), third subparagraph).

Crucially, every one of these exemptions switches off under Article 4(4) the moment the offeror (or anyone acting for them) signals an intention to seek admission to trading on an exchange — at that point the full Title II obligations apply regardless of investor count or offer size.

Transitional Periods and Grandfathering for CASPs

MiCA did not force every existing crypto-asset service provider to shut down and reapply on 30 December 2024. Under Article 143(3), providers that were already offering crypto-asset services in line with applicable national law before that date may keep operating under a transitional ("grandfathering") regime until 1 July 2026, or until they are granted or refused authorisation under Article 63, whichever comes first. Member States, however, are allowed to shorten or disapply this transitional period entirely if they judge their pre-MiCA national regime to have been less strict than MiCA (Article 143(3), second subparagraph) — so the actual grandfathering end date for any given CASP depends on which Member State licensed it, not a single EU-wide date. ESMA maintains a country-by-country list of these national transitional periods, published alongside its MiCA implementation page; a launchpad relying on a counterparty CASP's grandfathered status should confirm that specific Member State's cutoff rather than assuming the 1 July 2026 backstop applies everywhere.

For token issuers, Article 143(1) excludes white paper obligations for offers that ended before 30 December 2024. For tokens already admitted to trading before that date, Article 143(2) only requires compliance with the marketing-communication rules (Articles 7 and 9) for materials published after 30 December 2024, and gives trading-platform operators until 31 December 2027 to arrange a compliant white paper where one is required.

Reverse Solicitation: What It Does and Doesn't Cover

Non-EU launchpads frequently ask whether they can serve EU users without going through CASP authorisation. MiCA's answer is the "reverse solicitation" rule in Article 61: where an EU-based client "initiates at its own exclusive initiative" the provision of a crypto-asset service from a third-country firm, that firm does not need Article 59 authorisation for that specific client relationship.

The exemption is narrow by design. Article 61(1), second subparagraph, states that if the third-country firm — or anyone acting on its behalf or with close links to it — solicits EU clients "regardless of the means of communication used for the solicitation, promotion or advertising," that contact is not deemed client-initiated, and the carve-out does not apply. This overrides any contractual disclaimer claiming otherwise (Article 61(1), third subparagraph). It also cannot be stretched once the relationship exists: Article 61(2) specifically says a client's own initiative does not entitle the firm to market new types of crypto-assets or crypto-asset services to that same client. In short, reverse solicitation protects an unprompted, one-off inbound request — it is not a general license to run EU-facing marketing from outside the EU. ESMA was mandated to issue guidelines specifying when a third-country firm is deemed to be soliciting EU clients, and on detecting circumvention of this article (Article 61(3)).

What This Means for Non-EU Launchpads and Non-EU Retail Investors

For readers new to how these sales work at all, our complete guide to what an IDO is covers the mechanics MiCA is now layering rules on top of. For a non-EU launchpad, the practical read is: any EU-directed marketing, promotion, or advertising of the platform or a specific IDO — a targeted ad, an EU-language landing page, an EU community manager soliciting sign-ups — likely forecloses reliance on reverse solicitation and puts the platform back in CASP-authorisation territory if it is "placing" tokens for EU purchasers. A more conservative option (our analysis, not a MiCA requirement) is to exclude EU investors from a specific offer through geofencing and KYC residency checks, rather than relying on reverse solicitation as an operating model.

For a non-EU retail investor, the flip side is that MiCA's investor protections (white paper disclosure, the 14-day withdrawal right, the safeguarding-of-funds rules in Article 10) are tied to the offer being made in the Union under Title II, and to services being provided by an authorised EU CASP. An EU resident who genuinely initiates contact with a non-EU platform under Article 61 is, by the structure of that exemption, dealing with a provider MiCA does not require to hold an EU authorisation for that relationship — meaning those specific protections may not apply to that transaction the way they would with an EU-authorised CASP.

Practical Compliance Checklist

For a launchpad platform:

• Map exactly which crypto-asset services the platform performs under Article 3(1)(16) — in particular, whether it is "placing" tokens on an offeror's behalf, operating a trading venue, or merely referring users to a third-party sale.
• If EU users are served and the platform is placing/executing on an offeror's behalf, evaluate Article 59/63 CASP authorisation in a Member State, or restrict EU access and rely on a documented, unsolicited-only reverse-solicitation posture.
• Keep KYC, sanctions, and whitelisting controls auditable per IDO; the same records support the fair, clear, and conflict-managed conduct that Article 14 expects from offerors the platform works with.
• Confirm, per project, who the Article 3(1)(13) "offeror" is and who is contractually responsible for the white paper, rather than assuming the platform or the project automatically carries that role.
• If relying on any Member State's Article 143(3) transitional regime, confirm that state's specific cutoff date against ESMA's grandfathering list rather than assuming 1 July 2026 applies uniformly.

For a project/token issuer:

• Determine whether the planned raise fits an Article 4(2) exemption (under 150 EU persons per Member State, under €1,000,000/12 months, qualified investors only) or an Article 4(3) exemption (genuinely free, mining/staking reward, existing-utility token, limited network) — and document the basis, since competent authorities can challenge a limited-network claim above €1,000,000.
• If no exemption applies, budget time for Article 6 white paper drafting, Article 8 notification (20 working days before publication, to the home Member State), and Article 9 publication before any EU-facing marketing goes out.
• If running a "free" airdrop or task-based claim, check whether KYC data collection or any fee/commission removes the Article 4(3)(a) free-offer exemption.
• Avoid signalling intent to seek exchange admission before compliance work is complete — Article 4(4) revokes every exemption the moment that intent is communicated.
• Review the Article 13 withdrawal right and Article 10 fund-safeguarding duties if selling directly to EU retail holders.

Limitations: What MiCA Does Not Settle

MiCA is not a complete answer to every question a launchpad or IDO investor might have, and it is worth being explicit about where it stops.

• DeFi remains unresolved by design. Recital 22 of the regulation states that crypto-asset services "provided in a fully decentralised manner without any intermediary" fall outside MiCA's scope — but MiCA does not define how decentralised a protocol has to be to qualify, and Article 142(2)(a) requires the European Commission to produce a separate report assessing "the appropriate regulatory treatment of decentralised crypto-asset systems without an issuer or crypto-asset service provider," including whether DeFi needs its own regulation at all. A launchpad that adds governance tokens, front-end curation, or a centralized allocation mechanism to an otherwise on-chain IDO sits in exactly the gray zone this unfinished report is meant to address.
• Lending and borrowing of crypto-assets are not covered. Article 142(2)(b) tasks the Commission with assessing whether crypto lending/borrowing needs its own rules — meaning today's MiCA text simply does not regulate it.
• NFTs are excluded, but the line is fuzzy. Article 2(3) exempts crypto-assets that are "unique and not fungible," but Article 142(2)(d) flags that the Commission still needs to assess "the development of markets in unique and non-fungible crypto-assets," including whether large series or fractionalized NFTs should be regulated — an implicit admission that "unique" is not always a clean technical test.
• Whether a given launchpad's structure counts as "placing of crypto-assets" is an interpretation, not a bright line. MiCA's drafters wrote general service categories, not a launchpad-specific article; how a particular platform's allocation, custody, and marketing flow maps onto Article 3(1)(16) depends on its actual mechanics and is the kind of question that benefits from a formal opinion from a national competent authority or qualified counsel, not a generic checklist.
• Reverse solicitation's boundaries rely on guidelines, not a bright-line test in the Regulation itself. Article 61(3) left the precise definition of "soliciting" to ESMA guidelines rather than spelling it out in the text, which means supervisory practice — not the Regulation alone — determines how aggressively a given marketing activity gets treated as solicitation.

None of this is legal advice. Whether a specific launchpad needs CASP authorisation, whether a specific offer qualifies for an exemption, and how reverse solicitation applies to a specific client relationship are all fact-specific questions that should go to qualified EU legal counsel and, where relevant, the competent authority in the Member State involved before a platform launches a sale or opens itself to EU users.

Frequently Asked Questions

What is MiCA in simple terms?

MiCA (Markets in Crypto-Assets Regulation, Regulation (EU) 2023/1114) is the EU's single rulebook for crypto-assets that aren't already covered by existing financial law. It sets disclosure, authorisation, and conduct rules for anyone issuing, offering, or providing services around crypto-assets in the Union, and has applied in full since 30 December 2024 (Article 149).

Does every token sale need a MiCA white paper?

No. Article 4(2) exempts offers to fewer than 150 persons per Member State, offers under €1,000,000 over 12 months, and qualified-investor-only offers from the notification/publication steps. Article 4(3) exempts free offers, mining/staking rewards, existing-utility tokens, and limited-network tokens from Title II entirely — provided the offeror doesn't later signal intent to seek exchange listing (Article 4(4)).

Does a launchpad need a CASP license?

If the platform is "placing crypto-assets" — marketing tokens on an offeror's behalf to purchasers, per Article 3(1)(16)(f) and (22) — it is providing a crypto-asset service and needs authorisation as a CASP under Article 59/63, unless it qualifies for a Member State's Article 143(3) transitional regime. This depends on the platform's actual structure, not a generic launchpad exemption, since none exists in the text.

Can a non-EU launchpad serve EU users without a CASP license?

Only through "reverse solicitation" (Article 61) — where an EU client, with no prior solicitation, initiates the relationship at their own exclusive initiative. Any EU-directed marketing, promotion, or advertising breaks that exemption, and it cannot be used to sell new types of crypto-assets or services to an existing client (Article 61(2)).

Until when can existing crypto platforms operate without MiCA authorisation?

Under Article 143(3), providers already operating under applicable national law before 30 December 2024 can continue until 1 July 2026 or until they are authorised or refused under Article 63 — whichever happens first. Individual Member States can shorten or remove this grandfathering period, so the real deadline varies by jurisdiction.

Does MiCA regulate DeFi?

Not directly. Recital 22 excludes crypto-asset services provided in a "fully decentralised manner without any intermediary," but MiCA doesn't define that threshold, and Article 142 requires a separate Commission report assessing whether and how DeFi should be regulated — so the DeFi question is explicitly left open by the Regulation itself.

Last updated: October 2026. Sources: Regulation (EU) 2023/1114 (MiCA) via EUR-Lex; European Securities and Markets Authority (ESMA) MiCA implementation page. This article is general information, not legal advice.