Step-by-step process to obtain a MiCA license in Germany
The normal path to a MiCA License in Germany starts with perimeter review and ends with post-approval operational readiness. A realistic timeline for a well-prepared file is often 3-6+ months, but complex models or weak submissions can take longer.
1. Pre-application perimeter review
Start by defining the exact service scope, token classification, target markets, custody model, and outsourcing structure. This stage usually takes 1-2 weeks for internal scoping and longer if the model touches MiFID II, eWpG, or payment services perimeter questions.
2. Incorporation and substance build-out
Set up the German entity, office, governance structure, key hires, and banking strategy. A GmbH can often be incorporated within 1-4 weeks depending on founder readiness, notarization, and bank/account setup. This is a corporate law step, not the license itself.
3. Dossier preparation
This is usually the most work-intensive phase and often takes 6-10 weeks. The file should include the program of operations, governance map, AML framework, safeguarding design, ICT documentation, financial projections, and all fit-and-proper materials.
4. Filing and completeness review
Once filed, the authority typically performs a completeness check. The legal benchmark under MiCA is commonly referenced as up to 25 working days for completeness review. If the file is incomplete, the clock may not progress cleanly and further requests may follow.
5. Substantive assessment and RFIs
After the file is considered complete, the substantive review period is commonly referenced at up to 40 working days, subject to pauses, extensions, and additional information requests. In practice, this is where most timing variance occurs. BaFin may ask for clarifications on safeguarding, AML design, outsourcing chains, governance, or financial assumptions.
6. Approval and go-live readiness
Authorization is not the same as operational launch. Before go-live, the company should finalize banking, client disclosures, Travel Rule workflow, vendor contracts, reconciliation routines, and incident escalation processes.
What usually delays approval:
- weak or inconsistent perimeter memo;
- thin local substance or unclear decision-making location;
- generic AML documents not tied to actual transaction flows;
- unclear safeguarding and wallet governance;
- outsourcing of critical functions without credible oversight;
- financial projections that do not match staffing and vendor costs;
- slow or incomplete responses to BaFin RFIs.
RUE manages the process as a controlled project with legal, compliance, corporate, and banking workstreams running in parallel. That is usually the fastest way to a file BaFin can actually review.