Regulated United Europe OÜ
Registration number: 14153440
Anno: 16.11.2016
Phone: +372 56 966 260
Email: [email protected]
Address: Laeva 2, Tallinn, 10111, Estonia
MiCA License in Estonia 2026
Obtain MiCA-compliant CASP authorization in Estonia with RUE. Structured support for exchanges, custody providers, brokers, and crypto platforms targeting EU market access.
Schedule Free Consultation
Regulator
FI
Timeframe
4-8 months
Cost
from €19,900
Capital
€50k-€150k
Depends on authorized services, governance model, and operational substance.
Why Estonia for a MiCA License
Estonia remains a credible EU base for crypto businesses that want substance, legal clarity, and disciplined compliance. RUE helps founders structure the Estonian entity, map MiCA service scope, prepare the application file, and build a regulator-ready operating model.
As your point of contact, I help coordinate the licensing process end-to-end, keep communication clear, and move your application forward without unnecessary delays.
At Regulated United Europe, we support MiCA license in Estonia projects end-to-end: service mapping, company setup, governance design, document drafting, capital planning, regulator-facing submissions, and post-authorization compliance implementation.
We also coordinate adjacent workstreams that many firms ignore until too late: banking strategy, Travel Rule tooling, DORA readiness, tax structuring, accounting setup, and internal controls for custody or exchange operations.
Recognized EU Framework
Authorization is built around MiCA, with supervision by Finantsinspektsioon and access to EU passporting after notification.
Strong Local Infrastructure
Estonia offers efficient company administration, mature digital public services, and a legal ecosystem familiar with fintech and crypto compliance.
Substance Over Fiction
The jurisdiction favors applicants with real governance, documented source of funds, credible AML controls, and operational readiness.
Scalable Compliance Base
Estonia is well suited for businesses that want to combine MiCA authorization with DORA, AML, GDPR, accounting, and banking workstreams in one project.
Mica Licence in Estonia
Package includes (8)
- Preparation of necessary documents for registration of a new company in Estonia 2026
- Translation of a certificate of no criminal record through a sworn translator
- Payment of state fees related to company registration
- Payment of notary fees related to company registration
- Preparation of compliance documents for MiCA application
- Preparation of a business plan
- Submission of the necessary documents to FI
- Recruitment of local MLRO/Compliance officer
MiCA Class Comparison for Mica Licence in Estonia
Compare MiCA Class 1, Class 2 and Class 3 by permitted activities and baseline requirements.
Mica Class 1 - 50 000 EUR
CapitalFrom EUR 50,000
TimeCountry-specific
Swipe left/right to switch license type
Reception and transmission of client orders
Execution of orders on behalf of clients
Placement and advisory services
Portfolio management
No custody of client crypto-assets
Target Models
Advisory firms
Introducing brokers
Portfolio advisory setups
Mica Class 2 - 125 000 EUR
CapitalFrom EUR 125,000
TimeCountry-specific
Swipe left/right to switch license type
All Class 1 services
Crypto-fiat and crypto-crypto exchange
Custody and administration of client assets
Transfer services for crypto-assets
Higher organizational and AML requirements
Target Models
Exchanges
Custody providers
Broker-dealer operations
Mica Class 3 - 150 000 EUR
CapitalFrom EUR 150,000
TimeCountry-specific
Swipe left/right to switch license type
All Class 2 services
Operation of crypto-asset trading platform
Enhanced governance and internal controls
Advanced risk management and reporting
Typical for full-scale marketplace operators
Target Models
Trading venues
Multi-service CASP groups
Institutional-grade operators
MiCA Class Comparison (Class 1, Class 2, Class 3)
| Activity / Option | Mica Class 1 - 50 000 EUR | Mica Class 2 - 125 000 EUR | Mica Class 3 - 150 000 EUR |
|---|---|---|---|
| Reception and transmission of orders | V | V | V |
| Execution of orders on behalf of clients | V | V | V |
| Advisory and portfolio management | V | V | V |
| Crypto-fiat and crypto-crypto exchange | X | V | V |
| Custody and administration of crypto-assets | X | V | V |
| Operation of a trading platform | X | X | V |
Comprehensive Requirements for Estonia MiCA License
An Estonia MiCA license is, in legal terms, an authorization as a crypto-asset service provider (CASP) under Regulation (EU) 2023/1114. In practice, Finantsinspektsioon reviews whether the applicant is not only legally incorporated, but operationally capable of providing the requested services on a compliant basis.
The review is not limited to forms. The regulator will test your governance, prudential setup, AML/CFT controls, ICT resilience, outsourcing model, safeguarding logic, and the credibility of your management team. This is why a successful application must read like an operating blueprint, not a marketing deck.
Below are the core requirements that matter in real CASP authorization projects in Estonia in 2026.
Correct MiCA Service Scope and Capital Mapping +
You must first identify which MiCA service categories your business model actually triggers. This is the point where many applications go wrong. A wallet app may in fact involve custody and administration; an OTC desk may involve exchange, execution of orders, or reception and transmission of orders; a launch platform may trigger placing of crypto-assets rather than pure software activity.
- Typical initial capital bands under MiCA: €50,000, €125,000, or €150,000, depending on the authorized services;
- Initial capital is not the same as own funds and not the same as your total launch budget;
- Own funds must generally be maintained on an ongoing basis at the higher of the applicable minimum threshold or a prudential measure linked to fixed overheads where relevant;
- Capital must be demonstrably funded from lawful, traceable sources and supported by source-of-funds documentation.
A recurring market error is to quote outdated VASP-era figures or to confuse capital thresholds with operating budget. Finantsinspektsioon will expect a service-by-service legal analysis, not a generic statement that you are “an exchange”.
Estonian Company, Registered Office and Real Substance +
You need an Estonian legal entity, typically an OÜ, with a registered office and genuine operational substance. Estonia is not a viable jurisdiction for a pure letterbox structure if you are applying for a CASP authorization.
- A registered office is mandatory, but a mailing address alone is not enough for a serious application;
- The regulator will look at effective management, decision-making, access to records, and where key control functions are actually performed;
- Board meetings, policy ownership, outsourcing oversight, and incident escalation should be anchored in a credible EU management structure;
- Substance is assessed holistically: office, personnel, governance, vendors, banking, and operational accountability.
In practice, applicants with no realistic local or EU management footprint, no credible staffing plan, and no evidence of day-to-day control over critical functions face immediate credibility problems.
Management Body and Fit-and-Proper Assessment +
The management body must be fit and proper on both an initial and ongoing basis. In Estonia, a CASP application is heavily influenced by the quality of the people behind it.
- Applicants should plan for at least two board members as a practical governance baseline for segregation and continuity;
- Key persons must demonstrate relevant experience in financial services, crypto operations, compliance, risk, technology, or custody infrastructure, depending on the model;
- Finantsinspektsioon will review CVs, education, professional history, criminal record extracts, reputation, conflicts of interest, and time commitment;
- Shareholders and UBOs are also scrutinized, especially where there are complex holding chains, high-risk jurisdictions, nominee structures, or unclear wealth origin.
A common hidden issue is over-concentration of roles. If the same individual is effectively founder, board, AML lead, risk owner, and technology approver, the governance model usually looks immature.
AML/CFT, KYC and Sanctions Control Framework +
You must implement a business-specific AML/CFT framework aligned with Estonian AML law, EU requirements, and the operational realities of crypto transfers. A template manual is not enough.
- Required elements usually include a business-wide risk assessment, customer risk scoring, CDD/EDD procedures, PEP and sanctions screening, transaction monitoring, suspicious transaction reporting, and record retention;
- The framework must explain how you handle blockchain analytics, wallet screening, high-risk geographies, mixers, privacy-enhancing tools, and source-of-wealth/source-of-funds reviews;
- Travel Rule compliance under Regulation (EU) 2023/1113 must be operationalized, not merely referenced;
- The Estonian FIU remains relevant for suspicious transaction reporting even though CASP authorization sits with Finantsinspektsioon.
Strong applicants show alert logic, escalation routes, case management, and governance over false positives. Weak applicants only describe onboarding and ignore ongoing monitoring.
ICT Risk Management and DORA Readiness +
A CASP in Estonia must be prepared to operate under the broader EU operational resilience framework, including DORA where applicable to its regulated status and ICT environment. This means your technology stack must be governable, auditable, and resilient.
- You should maintain an ICT risk management framework covering asset inventory, access control, change management, patching, vulnerability handling, logging, backup, and recovery;
- Critical or important ICT third-party providers must be mapped, contractually governed, and monitored through an outsourcing register and vendor oversight process;
- Business continuity and disaster recovery should define practical metrics such as RTO and RPO rather than generic promises;
- Incident classification, escalation, and regulatory reporting routes must be documented before launch.
For custody models, the regulator will expect more than cloud diagrams. It will want to understand key management, wallet segregation, reconciliation, privileged access, and failover logic.
Business Plan, Financial Model and Source of Funds +
Your application must include a coherent business plan and financial projections, typically with a two-year planning horizon as a practical minimum. The regulator is testing viability, not just ambition.
- The business plan should explain services, target markets, client types, onboarding channels, revenue model, outsourcing, complaints handling, and risk controls;
- Financial projections should include realistic assumptions on client acquisition, transaction volumes, fee income, staffing, compliance costs, ICT spend, and capital buffers;
- Capital injections, shareholder loans, and investor funds must be fully documented with lawful source-of-funds evidence;
- Banking and fiat rails should be addressed early, because a CASP with no credible payment or safeguarding strategy often looks incomplete.
One overlooked point: the regulator will compare your stated business model against your financial model. If you describe an institutional exchange but budget only for one junior compliance employee and minimal security tooling, the file becomes internally inconsistent.
Safeguarding, Custody Controls and Client Asset Protection +
If your scope includes custody and administration of crypto-assets on behalf of clients, safeguarding becomes one of the central authorization themes. The regulator will expect a control environment, not a slogan about cold wallets.
- Client assets must be clearly segregated from proprietary assets in both wallet architecture and accounting records;
- You should document wallet typology: cold, warm, and hot storage, together with transfer approval flows and access rights;
- Daily or near-real-time reconciliation, exception handling, and audit trails are expected in serious custody models;
- Institutional controls may include MPC, HSM-backed key storage, dual control, key ceremony records, withdrawal limits, and emergency recovery procedures.
Proof-of-reserves may be commercially useful, but it is not a substitute for statutory accounting, safeguarding governance, or regulatory reporting.
Application File and Regulator-Facing Documentation +
A complete application file usually includes corporate documents, governance papers, policies, financials, and technical documentation. The quality of the file materially affects review speed.
- Core documents typically include: constitutional documents, ownership chart, UBO disclosures, business plan, program of operations, financial projections, governance map, AML/CFT policies, risk framework, ICT/security documents, outsourcing register, and safeguarding procedures where relevant;
- Key individuals should provide CVs, questionnaires, certificates, and reputation evidence;
- Documents must be internally consistent across names, dates, roles, service descriptions, and financial assumptions;
- Where documents originate abroad, apostille, notarization, or sworn translation may be needed depending on the document type and issuing jurisdiction.
At RUE, we treat the application file as a controlled evidence pack. That approach reduces contradictory statements, which are one of the most common causes of follow-up questions and review delays.
Jurisdiction Comparison
Compare Mica Licence in Estonia with other jurisdictions by key conditions for obtaining and operating a MiCA/CASP license: regulator, review period, fees, capital, local substance, and passporting.
* This table focuses on MiCA/CASP authorization conditions. Use the settings icon to customize countries and parameters.
💰 Licensing Cost Estimator
Get an approximate cost estimate for your crypto license based on your business needs
Configure Your Licensing Package
Select options below to see estimated costs
Estimated Cost
€0
Estimated Timeframe
Country-specific
Capital Requirement
€0
* This calculator provides approximate estimates only. Actual costs may vary based on your specific situation. Contact us for a detailed personalized quote.
Taxation of CASPs in Estonia in 2026
Estonia remains tax-efficient for growth-stage regulated businesses because corporate income tax is generally triggered on profit distributions rather than on retained earnings. For a MiCA license in Estonia project, this matters because early-stage compliance-heavy businesses often reinvest cash into staffing, security, and regulatory infrastructure instead of distributing profits.
How the Estonian Corporate Tax Model Works
As a rule, retained and reinvested corporate profits are not taxed immediately, while distributions are taxed at the corporate level. For 2026, founders should verify the current applicable corporate tax rate on distributed profits with the Estonian Tax and Customs Board (Maksu- ja Tolliamet) and local tax counsel before launch, because tax rates and implementing rules can change.
- Retained earnings: generally not subject to immediate corporate income tax;
- Distributed profits: taxed upon distribution under the Estonian corporate tax model;
- Payroll taxes: salaries trigger employment tax and social tax obligations;
- VAT: treatment depends on the exact service qualification and customer profile.
For crypto businesses, the VAT analysis is often misunderstood. Not every crypto-related service is exempt, and not every wallet or platform fee is taxable in the same way. Exchange services may follow principles developed in EU case law, including CJEU Hedqvist, but custody, technology access, platform fees, advisory, SaaS layers, and bundled services require separate classification.
Practical Tax Caveats for Estonian CASPs
Tax treatment depends on the legal and economic design of the service. A brokerage-style fee, a spread-based exchange margin, a custody fee, and a listing fee may each produce different VAT and accounting consequences. Cross-border operations can also create local tax registration or permanent establishment questions in other EU states if the business develops local presence, staff, or consumer-facing infrastructure there.
Regulatory and Operating Cost Layer
Tax is only one part of the budget. A realistic Estonia MiCA license budget should also include:
Corporate Income Tax
Triggered mainly on distributed profits
verify current rate
Corporate Income Tax
Triggered mainly on distributed profits
Estonia generally taxes corporate profits upon distribution rather than when profits are earned and retained. This is attractive for regulated businesses that need to reinvest in compliance, security, and growth. The exact applicable rate in 2026 should be confirmed against the current rules of the Estonian Tax and Customs Board and your ownership structure.
Value Added Tax (VAT)
Depends on exact service classification
0% / 22%*
Value Added Tax (VAT)
Depends on exact service classification
VAT treatment is highly service-specific. Certain exchange transactions may be exempt under EU financial services principles, but custody, software access, advisory, platform subscriptions, and ancillary services may be taxable. Do not assume that all crypto services are exempt or that all crypto companies must register for VAT immediately. A transaction-by-transaction analysis is often required.
*Standard VAT rate shown for orientation; actual treatment depends on the service.
Payroll Taxes
Applies to local staff and management remuneration
variable
Payroll Taxes
Applies to local staff and management remuneration
If you employ staff in Estonia, salaries trigger payroll-related obligations, including social tax and withholding mechanics. This becomes material in substance-heavy CASP models with local compliance, management, operations, or support staff.
Withholding and Cross-Border Structuring
Depends on shareholder and payment flows
case-specific
Withholding and Cross-Border Structuring
Depends on shareholder and payment flows
Dividend and cross-border payment treatment depends on the shareholder profile, treaty access, and the nature of the payment. International founders should coordinate Estonian tax planning with home-jurisdiction advice to avoid mismatches and double taxation issues.
State Fee for Authorization
Official fee must be checked before filing
official schedule
State Fee for Authorization
Official fee must be checked before filing
The state fee for a CASP application should always be verified against the current official Estonian schedule before submission. Market articles often repeat outdated or contradictory figures. We recommend treating unofficial fee claims as unreliable unless cross-checked against current official sources.
Annual Audit and Accounting
Mandatory statutory and operational cost layer
€8,000-€40,000+
Annual Audit and Accounting
Mandatory statutory and operational cost layer
Most CASP structures should budget for annual accounting, statutory reporting, and audit-related work depending on size and complexity. Costs increase materially for custody models, multi-entity structures, or businesses with high transaction volumes and wallet-to-ledger reconciliation demands.
Compliance and Control Functions
Recurring cost of staying authorized
€60,000-€300,000+
Compliance and Control Functions
Recurring cost of staying authorized
Ongoing costs usually include AML/CFT oversight, compliance support, board governance, risk management, policy maintenance, sanctions screening, Travel Rule tooling, and periodic control reviews. These are not optional overheads; they are part of the cost of remaining licensed.
ICT, Security and DORA Readiness
Technology governance and resilience spend
€20,000-€150,000+
ICT, Security and DORA Readiness
Technology governance and resilience spend
Budget for hosting, logging, monitoring, penetration testing, backup systems, privileged access management, vendor oversight, and incident response capabilities. Custody and exchange models sit at the higher end of the range because they require stronger controls and more extensive evidence.
Compliance and Ongoing Obligations After Authorization
A MiCA Licence in Estonia is not a one-time filing event. After authorization, the CASP must maintain prudential, governance, AML, ICT, and conduct controls on a continuous basis.
Regulatory Reporting and Governance
- Maintain ongoing own funds and capital adequacy monitoring
- Submit regulatory reports and audited financial statements as required
- Notify Finantsinspektsioon of material changes in ownership, management, or services
- Keep governance documents, board minutes, and control evidence up to date
- Review fit-and-proper suitability on an ongoing basis
AML, KYC and Travel Rule
- Perform CDD and EDD according to customer and transaction risk
- Run sanctions, PEP, and adverse media screening
- Monitor transactions and blockchain exposure continuously
- File suspicious transaction reports to the Estonian FIU where required
- Operationalize Travel Rule data exchange for in-scope crypto transfers
ICT, Security and DORA Controls
- Maintain ICT asset inventory, access control, logging, and change management
- Test backup, recovery, and business continuity arrangements periodically
- Classify incidents and escalate major ICT events through defined channels
- Govern outsourced critical ICT providers through contracts and oversight
- Document vulnerability management and security testing cadence
Client Protection and Conduct of Business
- Segregate client assets and maintain reconciliation controls where relevant
- Operate complaints handling and client communication procedures
- Manage conflicts of interest and disclose them where required
- Keep fee disclosures, terms, and marketing communications compliant
- Monitor outsourcing, execution flows, and safeguarding arrangements continuously
RUE handles compliance for you. Our team provides ongoing compliance support, including AML officer services, regulatory reporting, and policy updates. We ensure your license stays in good standing year after year.
Contact us for compliance support →
What a MiCA License in Estonia Actually Means
What a MiCA License in Estonia Actually Means
A MiCA license in Estonia is market shorthand for an authorization as a crypto-asset service provider (CASP) under Regulation (EU) 2023/1114. This distinction matters because the legal analysis starts with the service you perform, not with the marketing label you use.
- Stablecoin-related MiCA rules started applying from 30 June 2024
- CASP rules under MiCA started applying from 30 December 2024
- In Estonia, the old VASP regime does not convert automatically into a CASP authorization
- The transition period for legacy VASP operators runs until 1 July 2026
This means that a business searching for an Estonia MiCA license in 2026 usually needs one of three separate legal analyses:
- CASP authorization for services such as custody, exchange, execution, advice, or platform operation
- Token issuance / white paper analysis for public offerings or admission to trading of crypto-assets
- EMT / ART regime analysis for e-money tokens or asset-referenced tokens, which follow stricter rules and may trigger additional authorization questions
RUE structures projects around the correct regulatory track from day one. That avoids a common mistake: trying to solve an issuance or stablecoin problem with a pure CASP application.
📝 Check Your Eligibility
Answer a few quick questions to find out if this jurisdiction suits your crypto business
Step 1 of 5
What type of crypto services will you provide?
Exchange (fiat ↔ crypto)
Custody & Wallet Services
Transfer & Payment Services
Advisory / Portfolio Management
Multiple / All of the Above
Step 2 of 5
What is your target market?
European Union only
EU + Global markets
Global (non-EU priority)
Step 3 of 5
Do you already have a registered company in the EU?
Yes, in this jurisdiction
Yes, in another EU country
No, I need to register one
Step 4 of 5
What is your available budget range?
Under €20,000
€20,000 – €50,000
€50,000 – €100,000
Over €100,000
Step 5 of 5
When do you plan to launch?
As soon as possible (1–3 months)
Within 6 months
Within a year
Just exploring options
This Jurisdiction Is a Great Fit!
Based on your answers, this jurisdiction matches your business requirements well. Here's a quick summary:
Recommended License
CASP License
Estimated Budget
€24,000 – €35,000
Estimated Timeframe
4–6 months
EU Passporting
Available
Step-by-Step CASP Authorization Process
Step 1
Scope and Feasibility
Map the exact MiCA services, identify whether token issuance, EMT/ART, PSD2, or other parallel regimes are relevant, and test whether Estonia is the right jurisdiction. Duration: 1-2 weeks.
Step 2
Company Setup
Incorporate the Estonian entity, prepare ownership disclosures, arrange registered office, and structure governance and substance. Begin banking and staffing workstreams early. Duration: 1-3 weeks.
Step 3
Governance Design
Appoint board and key function holders, define reporting lines, segregation of duties, outsourcing model, and fit-and-proper evidence pack. Duration: 2-4 weeks.
Step 4
Documentation Drafting
Prepare the application file: business plan, program of operations, financial projections, AML/CFT framework, ICT and security documents, safeguarding policies, and source-of-funds package. Duration: 4-8+ weeks.
Step 5
Pre-Filing Review
Run a gap analysis to remove contradictions, verify service mapping, align financial assumptions with staffing and controls, and finalize the evidence pack for submission. Duration: 1-2 weeks.
Step 6
Application Submission
Submit the file to Finantsinspektsioon and pay the applicable official state fee. The regulator begins its completeness and substantive review process. Duration: 1 week.
Step 7
Regulator Review
Statutory review includes a completeness check of up to 25 working days and an assessment period of up to 40 working days, with possible suspension or extension where information is missing. Real timing depends heavily on file quality.
Step 8
Approval and Go-Live
After authorization, complete final operational conditions: banking, vendor onboarding, Travel Rule connectivity, staff training, reporting setup, and passporting notifications where relevant. Typical total project timeline: 4-8 months+, sometimes longer for complex models.
Frequently Asked Questions
Main Services
Terms of Cooperation
Regulated United Europe
