MiCA Crypto Licence in Latvia
Latvia is a Bank of Latvia-supervised MiCA CASP authorisation route for teams that need EU/EEA passporting and regulated crypto-asset service operations, while accepting real substance, governance, AML, audit and banking-readiness obligations.
Regulatory status should be confirmed by local counsel before relying on this route.
What is Latvia MiCA CASP authorisation?
Latvia MiCA CASP authorisation is the Bank of Latvia-supervised route for crypto-asset service providers under the EU MiCA framework. It is an EU regulated operating route for CASPs, not a fast offshore registration or a low-substance shortcut.
- Jurisdiction
- Latvia
- Regulator
- Bank of Latvia
- Regime
- MICA
- Legal basis
- Regime: MiCA CASP authorisation for crypto-asset service providers.
Country-specific regulatory statements should be checked against current regulator guidance before relying on this route.
EU/EEA passporting from Latvia
Latvia can support EU/EEA passporting for approved MiCA CASP services, but passporting is not a blanket marketing claim. The applicant should define target countries, requested services and notification steps before presenting Latvia as a cross-border EU route.
Exchange
IncludedExchange operations fit within the permitted activities of this route.
Exchange
Exchange operations fit within the permitted activities of this route.
IncludedCustody
ConditionalCustody may require separate review or additional controls.
Custody
Custody may require separate review or additional controls.
ConditionalBrokerage
IncludedBrokerage or OTC activity typically fits within scope.
Brokerage
Brokerage or OTC activity typically fits within scope.
IncludedWallet provider
IncludedExchange operations fit within the permitted activities of this route.
Wallet provider
Exchange operations fit within the permitted activities of this route.
IncludedEU market
IncludedEU/EEA passporting available.
EU market
EU/EEA passporting available.
IncludedStartups
ExcludedHigh setup complexity means significant budget is needed.
Startups
High setup complexity means significant budget is needed.
Excluded
Fees, timelines and capital figures are indicative and may vary by business model, regulator feedback, application scope and third-party costs.
Latvia as a MiCA home member state
Latvia fits teams that want a Baltic EU base, Bank of Latvia supervision and a moderate-cost MiCA route without pretending that setup is light. The CSV profile points to medium reputation, medium risk, medium maintenance cost and medium-to-high setup complexity.
Regulatory track record
PositiveHigh
Regulatory track record
High
PositiveBanking access for crypto firms
NegativeMedium to high
Banking access for crypto firms
Medium to high
NegativeRegulatory risk
CautionLow to medium
Regulatory risk
Low to medium
Caution
Fees, timelines and capital figures are indicative and may vary by business model, regulator feedback, application scope and third-party costs.
Latvia MiCA application bottlenecks
The main bottlenecks are usually operating-model issues, not only document collection. Latvia becomes harder when the applicant cannot connect costs, timeline, substance, service scope, passporting and banking assumptions into one coherent file.
- High
Unclear CASP service perimeter or EU/EEA passporting plan
- High
Local staff or office model that does not support real decision-making
- High
Weak custody, safeguarding, wallet, reconciliation or technology-resilience evidence
- High
Template AML, sanctions or travel-rule policies that do not match clients, tokens and fiat flows
- High
Banking, EMI, PI or PSP package prepared too late
- High
Timeline sold as exactly 6 months instead of from 6 months with regulator-question buffers
- High
Payment, staking, DeFi or securities-like features added without perimeter analysis
Fees, timelines and capital figures are indicative and may vary by business model, regulator feedback, application scope and third-party costs.
Activity fit for this route
Review which crypto activities fit within the scope of this route.
Exchange operations fit within the permitted activities of this route.
Custody may require separate review or additional controls.
Brokerage or OTC activity typically fits within scope.
Exchange operations fit within the permitted activities of this route.
EU/EEA passporting available.
High setup complexity means significant budget is needed.
Not sure if your model fits? Request a licensing assessment
Is Latvia MiCA authorisation right for your project?
Best for
- EU passporting and regulated CASP operations
- EU/EEA market access
Not suitable for
- Low-budget or fast offshore setup
- Projects without a prepared banking strategy
Banking difficulty is high for this route. Prepare a banking strategy before committing to the Latvia route.
Core requirements
Use this section to check the main regulatory and operational requirements before committing to a jurisdiction.
Fees, timelines and capital figures are indicative and may vary by business model, regulator feedback, application scope and third-party costs.
Local substance, office, audit and governance in Latvia
The CSV facts mark local staff, physical office and audit as required. Treat these as operating obligations that affect regulator confidence, banking readiness and maintenance cost, not as a simple incorporation checklist.
Local staff
RequiredRequired
At least one locally-accountable staff member or director is expected.
Physical office
RequiredRequired
A genuine office presence is expected, not a nominal registered address.
Audit
RequiredRequired
External audit is required for ongoing supervision compliance.
Planning notes
- Define Latvia-based decision-making, compliance ownership and regulator-facing accountability before submission.
- Document which functions remain local and which are outsourced to group, compliance or technology providers.
- Budget staff, office, audit, annual supervision from 3000 EUR and ongoing compliance separately from the 19 300 EUR application service price.
Fees, timelines and capital figures are indicative and may vary by business model, regulator feedback, application scope and third-party costs.
Cost breakdown
Budget for service price, regulatory fees, share capital and ongoing costs separately.
Fees, timelines and capital figures are indicative and may vary by business model, regulator feedback, application scope and third-party costs.
Cost breakdown — Latvia
Budget for service price, regulatory fees, share capital and ongoing costs separately.
| Cost item | Amount |
|---|---|
| Service priceApplication preparation and professional services. | €19,300 |
| State fee | €2,500 |
| Required share capitalMust be held, not an expenditure. | €50,000 |
Summary
- One-off costs
- €71,800
- Annual (year 1)
- €0
- Total year 1
- €71,800
Adjust to convert to your base currency.
Fees, timelines and capital figures are indicative and may vary by business model, regulator feedback, application scope and third-party costs.
Application process
The sequence below shows the usual project flow. Exact steps depend on the regulator, business model and application scope. Latvia — From 6 months.
Pre-assessment and scope review
1–3 weeksDefine the activity scope, governance model and target markets before formal preparation.
Company setup in Latvia
2–6 weeksEstablish legal entity, appoint local staff and set up local operating structure.
Documentation and compliance packBottleneck risk
3–8 weeksPrepare AML/CFT policies, governance documents, controls framework and application materials.
Application submission to Bank of Latvia
1–2 weeksSubmit complete application with all required documentation.
Regulator reviewBottleneck risk
From 6 monthsRegulator reviews the application. May request clarifications. Incomplete files extend this phase.
Depends on: File quality and completeness
Authorisation or registration confirmation
1–4 weeksRegulator confirms authorisation or registration. Commence operations.
Fees, timelines and capital figures are indicative and may vary by business model, regulator feedback, application scope and third-party costs.
What can delay or increase cost
These factors are most likely to affect timelines and budgets for this route.
Setup complexity is rated high for Latvia. Company setup, governance and documentation take longer than average.
Banking difficulty is rated high. Opening accounts for crypto businesses in Latvia requires extensive documentation.
Ongoing supervision, audit and compliance costs are above average. Budget for these separately from the application fee.
Incomplete files are the most common cause of delay. Regulator queries extend review by weeks or months.
Fees, timelines and capital figures are indicative and may vary by business model, regulator feedback, application scope and third-party costs.
Banking and PSP readiness in Latvia
The CSV profile rates crypto banking as medium to high and PSP availability as medium. A Bank of Latvia MiCA application can support the compliance story, but it does not remove bank, EMI, PI or PSP due diligence.
Reflects how challenging it is to open and maintain business bank accounts in this jurisdiction.
Reflects availability of payment service providers willing to onboard crypto-licensed entities.
A licence or registration does not guarantee bank account or payment provider approval. Banking feasibility should be reviewed before the application strategy is finalized.
Preparation checklist
- Prepare ownership, source-of-funds, flow-of-funds, client geography, token admission and transaction monitoring evidence early.
- Explain fiat settlement, safeguarding, reconciliation and custody flows before approaching banks, EMIs, PIs or PSPs.
- Expect stronger due diligence for exchange, custody, cross-border fiat flows and higher-risk client geographies.
When Latvia MiCA is not the right route
Latvia should not be selected only because it appears smaller or cheaper than premium EU jurisdictions. It is still a regulated MiCA CASP authorisation route with local substance, audit, capital, governance and ongoing maintenance expectations.
The project primarily wants a low-budget or fast offshore setup.
The team cannot fund local staff, physical office, audit, share capital and recurring supervision fees.
The target customers are outside the EU/EEA and passporting has limited commercial value.
The product is mainly DeFi, staking, payment, e-money token or securities-token related and needs a different regulatory analysis first.
Consider instead
- Lithuania MICA — Nearby Baltic MiCA comparison route under the Bank of Lithuania
- Estonia MICA — Digital-first Baltic EU positioning for regulated CASP teams
- Malta MICA — More established EU crypto regulator profile
Country-specific regulatory statements should be checked against current regulator guidance before relying on this route.
Business model fit — Latvia
Assess how well this route covers your planned activities.
Fit score
- Good fit
- 3/6
- Partial fit
- 3/6
- Poor fit
- 0/6
Latvia covers some but not all planned activities
Some activities need additional licensing or separate review before committing.
Bank of Latvia profile for crypto firms
Bank of Latvia
The Latvia file should be written as a regulated financial-services application. The Bank of Latvia profile makes the route more credible than an offshore registration, but it also means the applicant must explain service scope, governance, AML ownership, safeguarding, outsourcing and technology controls.
- Define who controls Latvia-based compliance, risk, AML, technology oversight and regulator-facing decisions.
- Exchange and custody-heavy models need stronger evidence than a narrow brokerage, wallet or advisory model.
- Avoid generic policy packs unless they are adapted to the applicant's clients, tokens, jurisdictions, fiat flows and outsourced systems.
Strong international recognition and established supervision track record.
Reflects documentation depth, governance requirements and expected review friction.
Reflects likelihood of delays, additional information requests or policy uncertainty.
Country-specific regulatory statements should be checked against current regulator guidance before relying on this route.
Compliance documentation
Most crypto licensing routes require a documented compliance framework before submission, not only after approval.
- RequiredAML/CFT policy and risk assessmentDocument your customer risk model and control framework.
- RequiredCustomer due diligence (CDD) procedures
- RequiredEnhanced due diligence (EDD) proceduresFor high-risk clients and jurisdictions.
- RequiredTransaction monitoring system and rules
- RequiredSanctions screening procedures
- RequiredSuspicious activity reporting (SAR) process
- RequiredMLRO / Compliance officer appointmentLocal accountability may be required.
- RecommendedBoard-approved governance charter
- ConditionalOutsourcing policy and monitoringRequired if functions are outsourced.
- RecommendedICT / cybersecurity policy
- RequiredComplaints handling procedure
- RequiredAnnual external audit engagementRequired for ongoing supervision compliance.
Country-specific regulatory statements should be checked against current regulator guidance before relying on this route.
Documents to prepare
Preparing these materials before filing reduces regulator questions and helps with banking or payment provider onboarding.
Corporate documents
AML and compliance
Operational
Fees, timelines and capital figures are indicative and may vary by business model, regulator feedback, application scope and third-party costs.
Risk assessment
Main risk dimensions for the Latvia route.
Route risk rating — banking difficulty: Medium to high. Authorisation does not guarantee bank account opening.
Mitigation: Start banking outreach and compliance preparation before the application.
Route risk rating — setup complexity: Medium to high.
Route risk rating — maintenance cost: High. Budget for ongoing compliance, fees and supervision separately.
Route risk rating — regulatory reputation: High.
Route risk rating — regulatory risk: Low to medium. Weak compliance, vague scope or insufficient controls increase review risk.
Mitigation: Prepare an evidence-based compliance file before submission.
This content is for general orientation only. Crypto regulation changes quickly and the final scope should be confirmed through a jurisdiction-specific legal review before filing or incorporation.
Latvia vs other MiCA and VASP routes
Compare Latvia with Lithuania and Estonia for nearby Baltic EU routes, Malta for a more established crypto regulator profile, Germany for a premium banking and reputation narrative, and Dubai VASP or other non-EU routes when EU/EEA passporting is not the commercial driver.
Latvia
MICA
- Price
- 19 300 EUR
- Timeline
- From 6 months
- Passporting
- EU/EEA
- Banking
- Medium to high
- Reputation
- High
Lithuania
MICA
- Price
- 17 300 EUR
- Timeline
- From 6 months
- Passporting
- EU/EEA
- Banking
- Medium to high
- Reputation
- Medium
+ Nearby Baltic MiCA comparison route under the Bank of Lithuania
− Route choice still depends on service scope, substance and banking evidence
View routeEstonia
MICA
- Price
- 18 400 EUR
- Timeline
- From 6 months
- Passporting
- EU/EEA
- Banking
- Medium to high
- Reputation
- Medium
+ Digital-first Baltic EU positioning for regulated CASP teams
− Not a low-substance route and may carry similar banking friction
View routeMalta
MICA
- Price
- 20 700 EUR
- Timeline
- From 6 months
- Passporting
- EU/EEA
- Banking
- Medium to high
- Reputation
- High
+ More established EU crypto regulator profile
− Usually heavier and more expensive than Latvia
View routeDubai (VASP)
VASP
- Price
- 22 300 EUR
- Timeline
- From 6 months
- Passporting
- No EU/EEA passporting
- Banking
- Medium
- Reputation
- High
+ Non-EU option when UAE operations are the commercial driver
− Does not replace MiCA passporting for EU/EEA markets
View routeFees, timelines and capital figures are indicative and may vary by business model, regulator feedback, application scope and third-party costs.
Latvia vs other MiCA jurisdictions
Compare key parameters across MiCA-authorised jurisdictions.
Check your readiness for Latvia MiCA authorisation
Documented AML/CFT policies, risk assessment, compliance officer.
From 50 000 EUR minimum capital required.
Documented AML/CFT policies, risk assessment, compliance officer.
Board, management, accountability chain defined.
Banking strategy and identified partners.
Local staff and office in Latvia.
Readiness status
Answer the criteria on the left to see your readiness status.
Frequently asked questions
No. Latvia should not be treated as a low-budget or fast offshore setup. The CSV facts show local staff, physical office, audit, share capital from 50 000 EUR, a 2,500 EUR state fee, annual supervision from 3000 EUR and medium-to-high setup complexity.
It can support EU/EEA passporting for approved CASP services, subject to the required notification process. Passporting should be tied to the authorised service scope, target markets and operating model, not treated as automatic coverage for every future activity.
Exchange, brokerage and wallet services are the clearest fits in this content model. Custody, advisory, staking and payment-adjacent models need scope review, while DeFi is not a clean standard CASP fit without separate legal analysis.
The main friction points are unclear CASP service scope, weak local substance, generic AML policies, underdeveloped safeguarding or custody controls, late banking preparation and payment, staking or DeFi features that have not been scoped legally.
No. Banks, EMIs, PIs and PSPs still assess ownership, source of funds, client geography, fiat flows, token policy, AML controls, safeguarding and risk appetite. Banking and PSP preparation should start before submission.
The page is not legal advice and should not be relied on as a substitute for advice from qualified counsel in the relevant jurisdiction.
Your dedicated specialists

Enrico

Rein

Jurata

Andrej

Marta

Katrin

Inga
Request a Latvia MiCA assessment
Share your planned activities, target markets and timeline. We will review which crypto licensing route is likely to fit.