One EU framework
Once authorised, a Lithuanian CASP can generally use MiCA passporting to provide covered services across the European Union, subject to notification procedures and local conduct expectations.
A practical guide for founders, compliance officers and legal teams preparing a Lithuanian CASP application under the EU Markets in Crypto-Assets Regulation.
MiCA creates a harmonised EU framework for crypto-asset services. In Lithuania, applicants that are not already authorised financial institutions generally need CASP authorisation from the Bank of Lithuania before providing regulated crypto-asset services.
Legacy virtual asset service provider models were mainly AML-focused. They confirmed that a company was known to the authorities and had basic anti-money laundering procedures, but they did not always test prudential resilience, governance depth, client-asset controls or operational continuity.
CASP authorisation is broader. The regulator examines the business model, service scope, own funds, management suitability, ICT resilience, outsourcing, complaints handling, conflicts of interest, market conduct and safeguarding of client assets and funds.
Once authorised, a Lithuanian CASP can generally use MiCA passporting to provide covered services across the European Union, subject to notification procedures and local conduct expectations.
A paper company is unlikely to be persuasive. Decision-making, compliance oversight, records, risk ownership and operational capacity should be demonstrable and proportionate to the service model.
For a more specific legal-service perspective, review this guide to the MiCA licence in Lithuania and compare it with your planned service perimeter.
The licence question starts with service mapping. A company may be in scope even if it does not call itself an exchange or custodian. The substance of the service is more important than the marketing label.
Platforms converting crypto-assets into funds, funds into crypto-assets, or one crypto-asset into another should review whether they perform exchange, execution, order reception or transmission services.
Businesses safeguarding private keys, administering client crypto-assets or controlling transfer infrastructure usually face higher expectations around segregation, access control, reconciliation and incident response.
Order-book venues, matching systems, transfer service providers and infrastructure products may need authorisation where they provide regulated services to third parties rather than purely internal technology.
A strong file connects legal analysis with operational evidence. Policies are necessary, but they should match the real product, staffing plan, technology stack, client journey and risk profile.
| Area | Regulatory expectation | Practical evidence |
|---|---|---|
| Service perimeter | Clear identification of each MiCA service and crypto-asset type covered by the business model. | Service matrix, product diagrams, client journey maps, legal classification memo. |
| Own funds | Minimum capital and ongoing prudential resources proportionate to the authorised services and risk profile. | Capital calculation, financial forecasts, evidence of paid-in capital, wind-down funding assumptions. |
| Management suitability | Managers and key function holders must be fit, proper, experienced and collectively suitable. | CVs, criminal record checks, reputation declarations, organisational chart, governance charters. |
| ICT and security | Secure, resilient technology with access controls, incident handling, business continuity and outsourcing governance. | Architecture diagrams, penetration testing plan, access matrix, disaster recovery plan, vendor register. |
| Client protection | Safeguarding of crypto-assets and funds, clear disclosures, complaint handling and conflict management. | Custody procedure, reconciliation policy, client terms, disclosure pack, complaints register template. |
| AML/CTF | Risk-based anti-money laundering framework aligned with Lithuanian and EU expectations. | AML risk assessment, KYC rules, transaction monitoring scenarios, sanctions screening, MLRO appointment. |
The process is easiest when handled as a regulatory project rather than a document-writing exercise. Each step should produce evidence that can survive supervisory questions.
Map every planned service against MiCA categories. Separate regulated CASP services from unregulated technology, marketing, treasury or group support functions.
Decide which functions sit in Lithuania, which are outsourced, who makes decisions, how compliance escalations work and how records will be kept for supervisory review.
Prepare policies, but also configure real controls: onboarding rules, transaction monitoring, sanctions screening, wallet risk tools, incident logs, access management and vendor oversight.
Compile corporate documents, business plan, financial forecasts, own-funds evidence, management files, outsourcing documentation, safeguarding procedures and client-facing disclosures.
After submission, expect follow-up questions. The response process should be controlled, consistent and evidence-based. Weak answers often reveal gaps between policy wording and actual operations.
Authorisation is not the endpoint. CASPs need monitoring, reporting, periodic reviews, incident notification procedures, complaint tracking, AML testing and board-level risk reporting.
Crypto compliance requires evidence that the firm understands blockchain transaction risk, wallet exposure, cross-border clients, sanctions evasion typologies and the operational risks of custody or transfer services.
The exact file depends on the service scope, corporate structure and risk profile. The checklist below is a practical working base for a Lithuanian CASP readiness review.
These answers are intended as practical orientation. They are not legal advice and should be checked against the exact business model before filing.
MiCA is designed as an EU framework. After authorisation and the required passporting steps, a Lithuanian CASP can generally provide covered crypto-asset services in other EU member states without obtaining a separate full licence in each state.
Foreign ownership is not the main obstacle. The stronger question is whether the applicant has credible governance, management suitability, operational capacity, AML controls and a Lithuanian operating model that matches the proposed services.
Timing depends on file quality, service complexity, ownership structure and regulator questions. A realistic plan should include time for pre-application scoping, document drafting, control implementation, submission review and follow-up responses.
The common weakness is inconsistency. For example, the business plan says custody is outsourced, the ICT policy assumes internal custody, the AML risk assessment ignores high-risk jurisdictions, and the financial forecast does not fund the compliance team described in the governance chart.
No. MiCA adds a crypto-asset services authorisation framework, but AML/CTF obligations remain central. Lithuanian applicants need both MiCA-ready governance and a robust AML programme suitable for crypto-specific risks.
Yes, but they must be operationally credible. The regulator may expect evidence that the controls described in the policies can actually be implemented, tested and monitored before launch.
Use this demo form to request a structured review of service perimeter, required policies, management files, AML controls, ICT evidence and launch readiness. The form runs entirely in the browser and does not send data to a backend.