Licensing
VASP / CASP onboarding & licensing
End-to-end support to get your virtual asset or crypto-asset service provider licensed under MiCA, the FCA regime or FINMA | from authorisation file to regulator sign-off.
What it is
What does VASP/CASP licensing support cover?
Getting licensed as a virtual asset or crypto-asset service provider means building a file that satisfies a regulator's governance, financial, operational and AML/CTF expectations simultaneously. We manage that file from the ground up: classifying your activities correctly, drafting the required policies, structuring your governance model, and preparing the evidence pack an examiner will actually test.
This isn't a document mill. Every file is built around your real product and operating model, so it survives scrutiny rather than triggering a round of clarification requests.
The process
How a licensing engagement runs
STAGE 01
Scoping & classification
We map your activities against MiCA/FCA/FINMA categories, identify the correct licence type, and flag structural issues early.
STAGE 02
File build
Governance documentation, AML/CTF policy, programme of operations, business continuity plan and financial resourcing evidence.
STAGE 03
Submission & follow-up
Filing, responding to regulator clarification requests, and steering the file through to authorisation.
Free resource
Not ready to engage yet? Start with our free MiCA CASP tracker
All 42 documents a CASP file needs, mapped to MiCA articles, with status tracking built in.
Packages
Choose the level of support you need
Self-Filing
Advisory
You file, we build the file and advise at each stage.
Get started- ✓Activity classification & gap review
- ✓AML/CTF policy drafting
- ✓Governance documentation templates
- ✓Full file assembly
- ✓Regulator correspondence handling
- ✓Post-licence obligations support
Guided
Full Licensing
We build and submit the complete file, and manage the regulator relationship through to authorisation.
Get started- ✓Activity classification & gap review
- ✓AML/CTF policy drafting
- ✓Full governance & operations file
- ✓Full file assembly & submission
- ✓Regulator correspondence handling
- ✓Ongoing post-licence compliance
Licence + Ongoing
Licence & Run
Full licensing support plus ongoing compliance once you're authorised.
Get started- ✓Everything in Full Licensing
- ✓Post-licence obligations management
- ✓Ongoing AML/KYC oversight
- ✓Periodic regulatory reporting
- ✓Annual policy review cycle
In detail
What's inside the service
Activity & licence classification
Correctly mapping your product against MiCA CASP categories, FCA registration routes, or FINMA membership requirements.
AML/CTF policy & risk assessment
A policy and business-wide risk assessment built around your actual customer base and transaction flows.
Governance & fit-and-proper file
Board structure, accountability mapping and fit-and-proper documentation for key function holders.
Programme of operations
The operational narrative regulators expect: what you do, how, and what controls sit around it.
Business continuity & wind-down planning
Contingency documentation covering operational disruption and orderly wind-down scenarios.
Regulator liaison
Managing clarification requests and follow-up correspondence so the file keeps moving.
FAQ
Frequently asked questions
How long does VASP/CASP authorisation take?+
Timelines vary by regulator and file quality, but a well-prepared MiCA CASP file typically takes three to six months from submission to authorisation. FCA registration and FINMA membership timelines follow a similar range, longer for more complex business models.
Do you handle the regulator relationship directly?+
On the Full Licensing package, yes | we act as your point of contact for clarification requests and manage the submission process. On the Advisory package, we prepare the file and you retain the direct regulator relationship.
Can you support multi-jurisdiction applications?+
Yes. We regularly structure parallel or sequential applications across MiCA, FCA and FINMA for clients serving more than one of these markets, flagging where requirements diverge.