CASP Authorisation in Hungary
Hungary is an MNB-supervised Central EU CASP route for teams that need MiCA authorisation, EU/EEA market planning and a practical cost profile, while still accepting full substance, governance, AML, audit and banking requirements.
Confirm current MNB MiCA/CASP application process, service categories, fees, transitional rules and supervisory guidance before using this page for client advice.
Regulatory status should be confirmed by local counsel before relying on this route.
What is Hungary CASP authorisation?
Hungary CASP authorisation is the MNB-supervised route for crypto-asset service providers under MiCA. It is a Central EU option for teams that want regulated EU operations and a practical cost profile, not a low-budget offshore registration.
- Jurisdiction
- Hungary
- Regulator
- Magyar Nemzeti Bank (MNB)
- Regime
- CASP
- Legal basis
- Legal basis: MiCA CASP authorisation supervised by Magyar Nemzeti Bank.
Country-specific regulatory statements should be checked against current regulator guidance before relying on this route.
CASP service scope in Hungary
The Hungarian application should begin with a precise MiCA service perimeter. Exchange, custody, brokerage, wallet, advisory, staking-adjacent and payment-related models can each change the required governance, safeguarding, AML and technology evidence.
Exchange
ConditionalExchange activity may require additional scope or separate licensing.
Exchange
Exchange activity may require additional scope or separate licensing.
ConditionalCustody
ConditionalCustody may require separate review or additional controls.
Custody
Custody may require separate review or additional controls.
ConditionalBrokerage
ConditionalBrokerage or OTC activity typically fits within scope.
Brokerage
Brokerage or OTC activity typically fits within scope.
ConditionalWallet provider
ConditionalExchange activity may require additional scope or separate licensing.
Wallet provider
Exchange activity may require additional scope or separate licensing.
ConditionalEU 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.
EU/EEA passporting from Hungary
Hungary is an EU route, so authorised MiCA/CASP services can be positioned for EU/EEA passporting. The practical passporting plan should be tied to the approved service scope, target countries and notification process rather than described as automatic market access.
Define target EU/EEA markets, client categories and service classes before filing.
Map passporting to each requested CASP service instead of assuming one approval covers every future product, token or market.
Keep non-EU expansion, payment services and investment-services triggers outside the CASP passporting claim unless separately reviewed.
Country-specific regulatory statements should be checked against current regulator guidance before relying on this route.
Capital, governance and audit expectations
Hungary has a practical cost profile compared with some premium EU routes, but it remains a high-complexity MiCA authorisation. The CSV snapshot indicates share capital from 50,000 EUR, approximate state fee of 3,000 EUR, approximate annual supervision fee of 2,000 EUR, local staff, physical office and audit.
- Board, senior management, compliance, AML and technology responsibility should be named and credible.highBoard, senior management, compliance, AML and technology responsibility should be named and credible.high
- Capital planning should match the service class and risk profile, especially for exchange, custody and fiat-heavy models.highCapital planning should match the service class and risk profile, especially for exchange, custody and fiat-heavy models.high
- Audit, reporting, outsourcing, safeguarding and incident-management workflows should be budgeted as recurring obligations.highAudit, reporting, outsourcing, safeguarding and incident-management workflows should be budgeted as recurring obligations.high
Fees, timelines and capital figures are indicative and may vary by business model, regulator feedback, application scope and third-party costs.
Hungary CASP application bottlenecks
Typical blockers are operating-model issues rather than simple form filling. Hungary works best when the team resolves service scope, local substance, governance, AML, audit and banking before treating the route as a cost-only choice.
- High
Unclear CASP service perimeter or EU/EEA passporting plan
- High
Weak Hungarian governance, staffing or board accountability
- High
Custody, safeguarding, wallet or technology-control evidence that does not match the product
- High
Generic AML policies that do not reflect client geography, tokens and fiat flows
- High
Banking or PSP package prepared too late
- High
Route selection driven only by price rather than a maintainable EU operating model
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 activity may require additional scope or separate licensing.
Custody may require separate review or additional controls.
Brokerage or OTC activity typically fits within scope.
Exchange activity may require additional scope or separate licensing.
EU/EEA passporting available.
High setup complexity means significant budget is needed.
Not sure if your model fits? Request a licensing assessment
Is Hungary CASP 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 Hungary 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 in Hungary
Local staff and a physical office should be planned as operating requirements. A nominal Hungarian footprint is weak if key decisions, compliance accountability and technology oversight are controlled elsewhere without a defensible model.
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
- Plan local compliance ownership and MNB-facing accountability before submission.
- Document which functions are controlled in Hungary and which are outsourced to group entities or technology providers.
- Budget office, staff, audit and ongoing compliance separately from application advisory fees.
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 — Hungary
Budget for service price, regulatory fees, share capital and ongoing costs separately.
| Cost item | Amount |
|---|---|
| Service priceApplication preparation and professional services. | €17,200 |
| State fee | €0 |
| Required share capitalMust be held, not an expenditure. | €50,000 |
Summary
- One-off costs
- €67,200
- Annual (year 1)
- €0
- Total year 1
- €67,200
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. Hungary — 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 Hungary
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 Magyar Nemzeti Bank
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 Hungary. Company setup, governance and documentation take longer than average.
Banking difficulty is rated high. Opening accounts for crypto businesses in Hungary 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 strategy
Hungary has a high regulatory reputation, but banking difficulty remains medium to high and PSP availability is medium. Bank and payment-provider readiness should run in parallel with authorisation planning, especially for exchange, custody and fiat-heavy businesses.
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 and token policy evidence early.
- Explain safeguarding, transaction monitoring, fiat rails and outsourcing before approaching banks or PSPs.
- Do not assume MNB authorisation or EU passporting will automatically solve account opening.
Business model fit — Hungary
Assess how well this route covers your planned activities.
Fit score
- Good fit
- 0/6
- Partial fit
- 6/6
- Poor fit
- 0/6
Hungary may not cover your primary activities
Consider an alternative route that better matches your activity profile.
MNB application profile
Magyar Nemzeti Bank (MNB)
An MNB-facing CASP file should read like a regulated financial-services application: precise services, accountable management, Hungarian substance, product-specific AML controls, safeguarding, technology resilience and a banking strategy that can survive due diligence.
- Hungary is strongest for teams that want a Central EU base with high regulatory reputation and controlled setup cost.
- The practical fee profile should not be confused with a light-touch authorisation.
- AML, sanctions, travel rule, transaction monitoring, outsourcing and cybersecurity evidence should match the actual product, clients and token policy.
- Hungarian legal implementation and MNB practice should be checked before relying on filing mechanics, fees or timing.
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 Hungary 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: 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.
Hungary CASP vs alternatives
Compare Hungary with Austria CASP for DACH positioning, Slovakia CASP for another pragmatic Central EU route, Romania CASP for regional EU positioning, and Poland CASP for a larger Central/Eastern EU market signal.
Hungary
CASP
- Price
- 17 200 EUR
- Timeline
- From 6 months
- Passporting
- EU/EEA
- Banking
- Medium to high
- Reputation
- High
Austria (CASP)
CASP
- Price
- 26 400 EUR
- Timeline
- From 6 months
- Passporting
- EU/EEA
- Banking
- Medium to high
- Reputation
- High
+ German-speaking EU route with strong DACH positioning
− Usually more expensive and less Central Europe cost-led than Hungary
View routeSlovakia (CASP)
CASP
- Price
- 16 600 EUR
- Timeline
- From 6 months
- Passporting
- EU/EEA
- Banking
- Medium to high
- Reputation
- High
+ Comparable pragmatic Central EU MiCA/CASP route
− Different supervisor, fee profile and local substance planning
View routeRomania (CASP)
CASP
- Passporting
- EU/EEA
- Banking
- Medium to high
- Reputation
- Medium to high
+ Regional EU option for Central and Eastern Europe positioning
− Current Romanian CASP process, fees and regulator practice need separate validation
View routePoland (CASP)
CASP
- Price
- 16 900 EUR
- Timeline
- From 6 months
- Passporting
- EU/EEA
- Banking
- Medium to high
- Reputation
- High
+ Large Central/Eastern EU market with KNF-supervised MiCA positioning
− May involve heavier local operating and supervisory expectations
View routeFees, timelines and capital figures are indicative and may vary by business model, regulator feedback, application scope and third-party costs.
Hungary vs other CASP routes
Compare key parameters across CASP authorisation routes.
Check your readiness for Hungary CASP 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 Hungary.
Readiness status
Answer the criteria on the left to see your readiness status.
Frequently asked questions
Hungary CASP authorisation under MiCA can support EU/EEA passporting for approved services, subject to the required notification process. It should not be described as automatic access for every current or future activity.
No. Hungary has a practical cost profile compared with some EU alternatives, but CASP authorisation still requires local staff, office, audit, governance, AML, capital and banking readiness.
Check the requested CASP services, MNB filing process, current fees, share capital, local substance, audit, AML controls, safeguarding, technology resilience, banking and PSP readiness.
Hungary is usually not suitable for low-budget launches, teams seeking a fast offshore setup, or businesses that cannot maintain local staff, office, audit, governance and ongoing compliance.
Compare Austria for DACH positioning, Slovakia for another pragmatic Central EU route, Romania for regional EU positioning, and Poland for a larger Central/Eastern EU market signal. Each alternative still needs a separate legal and banking review.
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 Hungary CASP assessment
Share your planned activities, target markets and timeline. We will review which crypto licensing route is likely to fit.