CASP Authorisation in Poland
Poland is a Central and Eastern EU CASP route for teams that want KNF-supervised MiCA authorisation and a cost-conscious EU base, while still accepting substance, governance, AML, audit and banking-readiness obligations.
Confirm current Polish implementing legislation, KNF competence, application process, fees and transitional rules before using this page for client advice.
Regulatory status should be confirmed by local counsel before relying on this route.
What is Poland CASP authorisation?
Poland CASP authorisation is the Polish MiCA route for crypto-asset service providers supervised by the Polish Financial Supervision Authority (KNF). It is positioned as a Central and Eastern EU option for regulated CASP operations, not as a light offshore registration.
- Jurisdiction
- Poland
- Regulator
- Polish Financial Supervision Authority (KNF)
- Regime
- CASP
- Legal basis
- Legal basis: MiCA CASP authorisation under the Polish/KNF supervisory framework, subject to current implementing rules.
Country-specific regulatory statements should be checked against current regulator guidance before relying on this route.
CASP service scope in Poland
The Polish file should start with a precise MiCA CASP service perimeter. Exchange, custody, brokerage, wallet, advisory and payment-adjacent models may be relevant, but each changes the governance, safeguarding, AML and technology evidence expected from the applicant.
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 Poland
Poland can be used as an EU home member state route for MiCA CASP authorisation, but passporting should be described carefully. The practical passporting plan depends on the authorised services, target markets, branch or cross-border model, and required notifications.
Define target EU/EEA markets and client categories before filing.
Map each proposed passporting market to the exact CASP services requested in Poland.
Avoid language that suggests one Polish approval automatically covers future services, tokens or markets.
Country-specific regulatory statements should be checked against current regulator guidance before relying on this route.
Capital, governance and audit expectations
Poland is more cost-conscious than premium EU routes, but it remains a regulated MiCA authorisation. The CSV snapshot indicates share capital from 50,000 EUR, a 4,500 EUR state fee, no annual fee, 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, outsourcing, incident management, reporting and AML operations should be budgeted as recurring obligations.highAudit, outsourcing, incident management, reporting and AML operations 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.
Poland CASP application bottlenecks
The main blockers are operating-model issues, not form filling. Poland works best when the team resolves service scope, local substance, governance, AML, audit and banking before treating the application as a simple cost comparison.
- High
Unclear CASP service perimeter or passporting plan
- High
Weak local 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 Poland 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 Poland 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 Poland
Local staff and physical office are not cosmetic requirements. The operating model needs to explain which decisions, controls and regulator-facing functions sit in Poland and which functions are outsourced or handled by a wider group.
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 KNF-facing accountability before submission.
- Document outsourced technology, custody, customer support or group functions with oversight controls.
- 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 — Poland
Budget for service price, regulatory fees, share capital and ongoing costs separately.
| Cost item | Amount |
|---|---|
| Service priceApplication preparation and professional services. | €16,900 |
| State fee | €4,500 |
| Required share capitalMust be held, not an expenditure. | €50,000 |
Summary
- One-off costs
- €71,400
- Annual (year 1)
- €0
- Total year 1
- €71,400
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. Poland — 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 Poland
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 Polish Financial Supervision Authority
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 Poland. Company setup, governance and documentation take longer than average.
Banking difficulty is rated high. Opening accounts for crypto businesses in Poland 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
Poland has a high regulatory reputation, but banking difficulty is still medium to high. Bank and PSP 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 and fiat rails before approaching banks or PSPs.
- Do not assume KNF authorisation or EU passporting will automatically solve account opening.
Business model fit — Poland
Assess how well this route covers your planned activities.
Fit score
- Good fit
- 0/6
- Partial fit
- 6/6
- Poor fit
- 0/6
Poland may not cover your primary activities
Consider an alternative route that better matches your activity profile.
KNF application profile
Polish Financial Supervision Authority (KNF)
The KNF-facing file should read like a regulated financial-services application: precise activities, accountable governance, local substance, AML controls, safeguarding, technology resilience and a banking plan that can survive due diligence.
Official regulator website- Poland is strongest for teams that want EU regulatory reputation without the highest-cost EU positioning.
- Custody, exchange and cross-border fiat flows need deeper controls than narrow brokerage or advisory models.
- AML, sanctions, travel rule, transaction monitoring, outsourcing and cybersecurity materials should be product-specific.
- Polish legal implementation and KNF 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 Poland 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.
Poland CASP vs alternatives
Compare Poland with Czech Republic CASP and Lithuania CASP for other cost-conscious EU routes, Germany CASP for a premium EU reputation and banking narrative, and Turkey CASP for a non-EU local-market route without EU/EEA passporting.
Poland
CASP
- Price
- 16 900 EUR
- Timeline
- From 6 months
- Passporting
- EU/EEA
- Banking
- Medium to high
- Reputation
- High
Czech Republic (CASP)
CASP
- Passporting
- EU/EEA
- Banking
- Medium to high
- Reputation
- Medium to high
+ Another Central European CASP route for EU-focused operators
− Still requires MiCA-level governance, AML and operating substance
View routeLithuania (CASP)
CASP
- Passporting
- EU/EEA
- Banking
- Medium
- Reputation
- Medium
+ Often compared for lower-cost EU entry and fintech familiarity
− Not automatically easier for exchange, custody or fiat-heavy models
View routeGermany (CASP)
CASP
- Passporting
- EU/EEA
- Banking
- Low to medium
- Reputation
- Very high
+ Premium EU reputation and stronger banking narrative
− Higher cost, heavier governance expectations and stricter execution burden
View routeTurkey (CASP)
CASP
- Price
- 52 800 EUR
- Timeline
- From 3 months
- Passporting
- No passporting
- Banking
- High
- Reputation
- Medium
+ Local-market CASP route for Turkey-facing operations
− No EU/EEA passporting and materially different regulator profile
View routeFees, timelines and capital figures are indicative and may vary by business model, regulator feedback, application scope and third-party costs.
Poland vs other CASP routes
Compare key parameters across CASP authorisation routes.
Check your readiness for Poland 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 Poland.
Readiness status
Answer the criteria on the left to see your readiness status.
Frequently asked questions
Poland CASP authorisation under MiCA can support EU/EEA passporting for approved services, but it should not be described as automatic access. The passporting plan must match the authorised service scope and required notification process.
No. Poland may be cost-conscious compared with premium EU routes, but it is still a regulated EU CASP route with local substance, governance, AML, audit, capital and banking-readiness expectations.
A credible file should define the CASP services, management and compliance ownership, local substance, AML and sanctions controls, safeguarding, technology resilience, outsourcing oversight and banking or PSP strategy.
Poland 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 Czech Republic CASP and Lithuania CASP for other Central or Eastern EU options, Germany CASP for a premium EU route, and Turkey CASP when the business is Turkey-market led and does not need EU/EEA passporting.
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 Poland CASP assessment
Share your planned activities, target markets and timeline. We will review which crypto licensing route is likely to fit.