MiCA CASP timeline · Authorisation clock
How Long a MiCA CASP Licence Takes: The Real 2026 Timeline
Founders ask 'how long does a MiCA licence take' and hear '25 plus 40 working days'. That's the statutory clock — and it only starts after the regulator declares the file complete. The honest answer is months, and the variable is file quality.
The MiCA CASP authorisation timeline is the period from filing a crypto-asset service provider application to receiving the regulator's decision, governed by the statutory authorisation clock of Regulation (EU) 2023/1114 — a 25-working-day completeness check followed by a 40-working-day assessment of a complete application — with the real-world duration extended by the pre-completeness phase, information requests, and supervisory dialogue.
Quick facts
| Parameter | Value |
|---|---|
| Legal basis | MiCA Regulation (EU) 2023/1114, the statutory authorisation clock — assessment of the application |
| Completeness check | Within 25 working days of receiving an application, the regulator assesses whether it is complete (the statutory authorisation clock) |
| Substantive assessment | Within 40 working days of receiving a complete application, the regulator adopts a fully reasoned decision granting or refusing authorisation |
| Information requests | The regulator may request more information during assessment, generally no later than the 20th working day; the formal clock is not paused but completeness can be re-tested |
| Decision notification | The regulator notifies the applicant of the decision within five working days of taking it |
| Statutory total | Roughly 25 + 40 working days once the file is complete — about three months of formal clock |
| Real-world timeline (practitioner-reported) | Commonly 4-8 months filing-to-decision, driven by the pre-completeness phase and the quality of the documentation |
The question with a misleading easy answer
“How long does a MiCA CASP licence take?” is the first question almost every founder asks. The easy answer — “25 plus 40 working days” — is technically a real number from the Regulation, and practically misleading. It describes a clock that only starts after a milestone most applicants underestimate: the regulator declaring the file complete.
Understanding the difference between the statutory clock and the real timeline is the difference between a realistic launch plan and a plan that slips by months.
How the statutory clock works
MiCA’s statutory authorisation clock sets the formal procedure for assessing a CASP application:
| Stage | The statutory authorisation clock rule |
|---|---|
| Completeness check | Within 25 working days of receiving the application, the regulator assesses whether it is complete |
| Substantive assessment | Within 40 working days of receiving a complete application, the regulator adopts a fully reasoned decision granting or refusing authorisation |
| Information requests | The regulator may request further information during assessment, generally no later than the 20th working day |
| Decision notification | The applicant is notified of the decision within 5 working days of it being taken |
Two features matter most:
-
The 40-day assessment clock starts on completeness, not on filing. The completeness check is a separate, earlier 25-working-day window. If the file is not complete, the regulator does not start the 40-day clock — it goes back to the applicant.
-
The formal 40-day clock is not paused by information requests. During the assessment the regulator can ask for more information, generally by the 20th working day, without formally stopping the clock — though in practice the completeness determination is where most iteration happens.
Add it up and the statutory clock for a complete file is roughly 65 working days — about three months.
Why the real timeline is longer
The statutory three months assumes a complete, well-evidenced file arriving at the regulator. The real timeline — practitioner-reported commonly at 4 to 8 months filing-to-decision — is longer because of three factors the statutory numbers do not capture.
1. The pre-completeness phase
This is where most calendar time goes. Before the 40-day clock starts, the file has to be complete. A file that arrives thin triggers a cycle: the regulator identifies gaps, the applicant fills them, the regulator re-checks. Each cycle is weeks. A strong file clears completeness fast; a weak one can spend months there.
2. Information-request turnaround
During the assessment, the regulator can request further information. The clock may not formally pause, but the applicant’s response speed is entirely within the applicant’s control — and it directly drives total time. A firm that answers each request in days keeps things moving; a firm that takes weeks per response stretches the real timeline well beyond the formal clock.
3. Supervisory pace by jurisdiction
The statutory clock is EU-wide. Supervisory practice is not. Different national competent authorities move at different real-world speeds on clean files, depending on their CASP caseload and capacity. The clock is the same; the experience is not.
Cited expert
In addition, [ESMA](/glossary/esma/) is actively contributing to MiCA's effective implementation, in close cooperation with the European Banking Authority and National Competent Authorities, including through intense supervisory convergence efforts, information sharing, and guidelines.
What actually makes an application fast
The single biggest determinant of timeline is file quality at filing. The fastest applications are not the ones filed earliest — they are the ones filed complete. Specifically:
-
A genuinely complete file — all the documentary set MiCA requires, populated with the firm’s own specifics rather than templates, so the completeness check passes quickly.
-
Pre-application engagement — where the regulator offers pre-application dialogue, using it surfaces gating issues (substance, business model, governance) before the formal review rather than during it.
-
Fast, complete information-request responses — a prepared applicant with its documentation organised answers requests in days, not weeks.
-
Realistic jurisdiction choice — choosing a home regulator on the basis of the firm’s actual readiness and the regulator’s real practice, not on an advertised “fastest” claim.
A realistic planning model
For planning purposes, a sensible model is:
- Preparation — 2 to 4 months to build a genuinely complete, well-evidenced file (this is work, and rushing it costs more time later than it saves)
- Completeness phase — weeks if the file is strong, longer if it is thin
- Formal assessment — the ~40-working-day statutory window once complete
- Decision and notification — within 5 working days of the decision
The honest headline for a founder: plan for the better part of a year from “we decide to do this” to “we hold the licence”, with the preparation phase being the part you most control.
Working with counsel on the timeline
The diagnostic for counsel: ask not “how fast can you file” but “how do you get a file to complete without multiple completeness cycles” — and whether they use pre-application engagement. Counsel that promises a fast timeline by filing quickly has the incentive backwards. The firms in our index with documented multi-file CASP experience are listed below.
Pitfalls and nuances
1 Confusing the statutory clock with the real timeline
The 25 + 40 working day figures describe the formal procedure once the file is complete. They are not the answer to 'how long from when we start'. The pre-completeness phase — where the regulator and applicant iterate toward a complete file — is where most of the calendar time goes and is not captured in the statutory numbers.
2 Filing thin to start the clock early
Filing an incomplete application in the hope of 'getting in the queue' backfires. The completeness check simply returns the file or extends the pre-clock dialogue. A month spent preparing a complete file beats three months iterating a thin one through completeness.
3 Underestimating information-request turnaround
During assessment the regulator can request further information. The applicant's own response speed materially affects total time. A firm that takes weeks to answer each request stretches a three-month formal clock into a much longer real timeline.
4 Ignoring jurisdiction-specific pace
The statutory clock is EU-wide, but supervisory pace is not. Some regulators move faster on clean files than others. Choosing a jurisdiction purely on advertised speed, without accounting for that regulator's actual practice and the firm's own readiness, leads to timeline surprises.
5 No pre-application engagement
Several regulators offer pre-application dialogue. Skipping it means gating issues — substance, business model, governance gaps — surface during the formal review instead of before it, extending the timeline. Pre-engagement front-loads the friction.
Frequently asked questions
How long does a MiCA CASP licence take?
The statutory clock is 25 working days for completeness plus 40 for assessment — about three months. Real-world filing-to-decision is commonly 4-8 months, because the clock starts only once the file is complete.
When does the 40-working-day assessment clock start?
Only once the regulator declares the application complete. The 25-working-day completeness check comes first, and weak files spend extra time in that pre-clock phase.
Can the regulator pause the assessment clock?
Under the statutory authorisation clock the formal 40-working-day assessment clock is not paused by information requests, but the regulator can request information during the assessment, generally no later than the 20th working day.
What makes a MiCA application faster or slower?
File quality. A complete, well-evidenced file moves through completeness fast and clears assessment with few information requests. A thin file spends months in pre-completeness dialogue.
Get matched
Working through a crypto-licensing decision?
Get an editorial shortlist of firms matched to your business — customer market, model, jurisdiction, and stage. Free, and not influenced by sponsorship.
Get a firm shortlist →Sources cited
- Regulation (EU) 2023/1114 (MiCA), Article 63 — regulation
- ESMA MiCA implementation page — regulator
- ESMA Supervisory Briefing on the authorisation of crypto-asset service providers — official document