CASP Licence
Crypto Asset Service Provider
The CASP label spans two route families in this project: MiCA-aligned EEA authorisations rendered through CASP country pages, and Turkey's local-market SPK route. Use this hub to compare both models before narrowing to a jurisdiction.
What is a CASP licence?
The CASP term appears both inside the EEA MiCA environment and in Turkey's domestic capital-markets framework. The shared label does not mean identical rights: EEA pages focus on MiCA-aligned authorisation, while Turkey is a local-market route with no EEA passporting.
- EEA CASP country pages in this project describe MiCA-aligned authorisation with potential EU/EEA passporting once the approved service scope is notified correctly.
- Turkey CASP is a separate domestic route supervised through the SPK framework and should be treated as a local-market authorisation only.
- The same acronym does not eliminate jurisdiction-specific differences in service scope, capital, substance, banking and regulator expectations.
- Use the country pages to compare whether the business needs EU/EEA reach, institutional reputation, lower cost or Turkey-only access.
- Where the business does not need EEA access, compare VASP, DASP or DAB routes rather than assuming CASP is always the right family.
CASP is not a single global licence. EEA CASP pages and Turkey CASP describe materially different regulatory outcomes.
CASP licence cost and timeline by country
CASP licence cost and timeline differ between the two families in this hub. Side-by-side comparison of EEA MiCA-aligned jurisdictions and Turkey's local-market authorisation.
Who needs a CASP licence
You need a CASP licence if you provide crypto asset services in a jurisdiction that has adopted the CASP category — either the MiCA-aligned EEA framework or Turkey’s SPK regime. The two are not interchangeable, so read the split below before picking a country.
Best for
- Businesses comparing EEA MiCA-aligned CASP jurisdictions through a CASP-focused country lens.
- Operators that want to separate EEA passporting routes from Turkey's domestic SPK route before selecting a filing strategy.
- Teams that need to compare institutional EEA positioning against non-passportable local-market access.
Not for
- Users expecting one generic CASP label to mean the same rights in every jurisdiction.
- Projects that only need non-EU registration-style routes and do not care about EEA positioning.
- Teams that have not yet separated passporting needs from single-market access needs.
Related routes
Use the dedicated MiCA hub when the primary task is EU/EEA passporting route selection rather than mixed CASP-family comparison.
Non-EU markets including UAE, Dubai, Gibraltar and offshore routes.
If Turkish CASP scope is unclear for your model, a feasibility review helps.
Frequently asked questions about CASP routes
No. The CASP label is shared, but EEA pages describe MiCA-aligned authorisation while Turkey describes a domestic SPK route. Passporting, service scope and supervisory posture differ materially.
No. Turkey CASP is a local-market route. If the business needs EU/EEA market access, use an EEA MiCA-aligned jurisdiction instead.
Because the project contains both MiCA-aligned CASP country pages and a distinct Turkey CASP page. The hub's job is to prevent topic mismatch by making that split explicit before the user clicks into a jurisdiction.
This information is for general guidance only. Jurisdiction-specific requirements, scope and passporting rights must be validated before relying on any CASP route.