Plan your MiCA authorisation route for serving Poland. A Polish CASP filing depends on the statutory designation of a competent authority and an operational application procedure; KNF-facing preparation must not be presented as an already available licence. RUE supports regulatory scoping, documentation and assessment of lawful EU market-entry options.
Prepared by RUE editorial team · Reviewed by Milana · Updated 12 May 2026
Book Licensing CallA MiCA license in Poland is, in practice, a question of obtaining CASP authorization under Regulation (EU) 2023/1114 and aligning with the Polish supervisory framework in 2026. RUE helps founders, legal teams, and compliance leads structure the entity, define regulatory perimeter, prepare the application pack, and build the operating controls expected by the KNF, GIIF, banking partners, and counterpart CASPs across the EU.
"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."
Regulated United Europe (RUE) provides end-to-end support for a CASP license in Poland: perimeter analysis, company setup, governance design, AML/CFT framework, DORA and Travel Rule readiness, application drafting, and regulator-facing responses.
We also support banking strategy, tax coordination, outsourcing documentation, and post-authorization controls so the business is not only licensable on paper, but operationally defensible after launch.
CASP authorization in Poland is built on directly applicable EU law under MiCA, with access to passporting across the EU after authorization and notification.
Poland offers mature company law, deep professional services capacity, KRS-based corporate formalities, and a large domestic talent pool for compliance, legal, and operations.
Banking is never automatic for crypto, but a well-structured Polish entity with credible AML, source-of-funds evidence, and real operations is often more bankable than a paper-only setup.
Poland is suitable for teams willing to implement real AML/KYC, Travel Rule, safeguarding, complaints handling, outsourcing oversight, and DORA-grade ICT governance.
A MiCA license in Poland requires more than filing forms. The KNF will assess whether the applicant can operate as a real crypto-asset service provider with adequate capital, governance, internal controls, safeguarding arrangements, and credible management. The legal baseline comes from Regulation (EU) 2023/1114 (MiCA), while AML/CFT obligations are reinforced by the Polish AML Act of 1 March 2018, GIIF practice, and the Transfer of Funds Regulation (EU) 2023/1113.
Founders should separate four layers from day one: EU law already applicable, Polish implementing mechanics, KNF supervisory expectations, and market constraints such as banking, staffing, and vendor due diligence. In our experience, applications fail less often because of one missing document and more often because the business model, policy suite, financial forecasts, and governance map do not fit together.
Under Article 67 MiCA, a CASP must maintain prudential safeguards at least equal to the higher of the applicable Annex IV minimum (€50,000, €125,000 or €150,000) and one quarter of the preceding year’s fixed overheads. A provider operating for less than one year uses projected fixed overheads for its first 12 months. The safeguards may consist of qualifying own funds, an insurance policy or comparable guarantee meeting Article 67, or a combination of these.
Class 1 (€50,000): execution, placing, transfers, reception/transmission, advice and portfolio management. Class 2 (€125,000): Class 1 services plus custody or exchange against funds or other crypto-assets. Class 3 (€150,000): Class 2 services plus operation of a trading platform. The highest applicable class determines the Annex IV minimum.
Capital must be demonstrably available in fiat, with clear source-of-funds evidence. Founders should budget beyond the legal minimum using a practical formula: initial funding = minimum own funds + 12 months operating burn + compliance tooling + legal reserve + banking contingency.
You need a Polish legal entity capable of being supervised and evidenced through local corporate records such as KRS, NIP, and REGON. In most cases, founders use a sp. z o.o.; more complex capital-raising structures may consider S.A. depending on the business model and investor profile.
The KNF and banking counterparties will expect genuine substance rather than a mailbox structure. Practical substance usually includes:
Remote ownership is possible, but “remote everything” is not a robust licensing strategy. If founders are non-resident, the governance file should clearly show who makes decisions, where records are held, and how the Polish entity controls outsourced functions.
The management body, significant shareholders, and UBOs must be transparent, reputable, and competent. The regulator will look beyond formal CVs and ask whether the team can actually run a regulated crypto business with AML, safeguarding, ICT, and complaints obligations.
A recurring weak point in applications is appointing nominal directors with no operational authority. KNF-facing governance should show who owns AML escalation, who approves outsourcing, who oversees ICT incidents, and who signs off on safeguarding reconciliations.
A Polish CASP must implement a business-specific AML/CFT framework aligned with the Polish AML Act, FATF logic, and the practical realities of crypto onboarding and transaction monitoring. Generic templates are easy for regulators and banks to detect.
GIIF reporting is process-driven, not a simplistic “report everything above X” exercise. The stronger setup includes documented alert rationales, blockchain analytics integration, wallet attribution logic, and evidence trails that can survive both regulator review and banking due diligence.
MiCA readiness without Travel Rule and DORA readiness is incomplete. For transfers of crypto-assets, applicants should be prepared to comply with Regulation (EU) 2023/1113, including originator/beneficiary data handling, counterparty CASP checks, self-hosted wallet risk controls, and audit logging.
On the ICT side, DORA requires a structured governance layer, not just “strong cybersecurity.” Practical artefacts usually include:
A frequent blind spot is vendor concentration risk. If one cloud, custody, KYC, or blockchain analytics vendor becomes critical, the applicant should document fallback logic and contractual oversight.
The application pack must include a coherent business plan and realistic financial projections, usually for at least 3 years. The regulator will test whether your revenue assumptions, staffing plan, compliance burden, and service scope are internally consistent.
One practical nuance often missed by founders: if your forecast assumes high transaction volume in the first year, your AML staffing, KYT tooling, complaints handling, and support capacity must scale accordingly. Forecasts that ignore operational load are a red flag.
If your model includes custody or administration of crypto-assets on behalf of clients, safeguarding is a central licensing issue. The applicant should document how client assets are segregated, reconciled, protected, and recoverable.
Where personal data is processed in onboarding, wallet monitoring, or complaints handling, the governance file should also align with GDPR and Polish data protection expectations, including access controls, retention logic, and processor oversight.
A Poland MiCA license is materially easier to operate with credible banking and payment arrangements, but authorization does not guarantee bank acceptance. Banks and EMIs will independently assess ownership, AML maturity, expected flows, sanctions exposure, and the jurisdictions you serve.
Applicants should prepare:
RUE typically advises clients to treat banking as a parallel workstream from week one, not as a post-license afterthought. In practice, bankability can delay launch more than the legal filing itself.
Compare Poland with other jurisdictions by key conditions for obtaining and operating a MiCA/CASP license: regulator, review period, fees, capital, local substance, and passporting.
5 jurisdictions in this table
* This table focuses on MiCA/CASP authorization conditions. Use the settings icon to customize countries and parameters.
Poland does not market itself as a low-tax crypto jurisdiction, but it can be a commercially workable base for a regulated CASP when founders value legal infrastructure, workforce depth, and EU access over aggressive tax positioning. For most operating companies, the main tax question is not “Is crypto taxed differently?” but how the specific revenue stream is characterized: brokerage, custody, software, advisory, token-related income, treasury gains, or cross-border service fees.
The headline corporate income tax rate is generally 19%. A reduced 9% CIT rate may be available for certain small taxpayers and start-up situations, subject to statutory conditions and turnover thresholds. VAT treatment is more nuanced: some crypto exchange activities may fall within financial-services logic, while advisory, SaaS, implementation, or support services may be taxable at the standard 23% VAT rate. The exact treatment depends on service characterization, contractual structure, and place-of-supply rules.
RUE usually coordinates licensing and tax workstreams together because weak accounting architecture often creates regulatory problems later, especially around safeguarding evidence, source-of-funds review, and audit readiness. For accounting support in Poland, see
A Poland CASP license is not a one-off filing. After authorization, the firm must maintain evidence-based compliance across AML, safeguarding, ICT, governance, complaints, outsourcing, and cross-border activity.
MiCA is directly applicable EU law, but the practical route to a CASP license in Poland still depends on the Polish supervisory framework, local procedural mechanics, and KNF practice. This is the core point most market summaries get wrong.
In practice, most searches for a MiCA license in Poland refer to obtaining authorization as a Crypto-Asset Service Provider (CASP). That is correct for exchanges, custody providers, brokers, trading venues, transfer services, portfolio managers, and crypto advisers. It is not the full answer for every token business. Issuers of ARTs and EMTs, and projects whose tokens may qualify as financial instruments under MiFID II, can fall into different or additional regulatory tracks.
This page is written from a due-diligence perspective. It does not assume that every crypto model fits neatly inside MiCA, and it does not treat every Polish procedural point as fully settled where the answer depends on the final wording of national law or KNF practice in 2026.
Answer a few quick questions to find out if this jurisdiction suits your crypto business
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
Map the business model against MiCA, MiFID II, EMT/ART, AML, and payment-services boundaries. Define the exact CASP service scope and capital bucket before incorporation or drafting begins. Typical duration: 1-3 weeks.
Incorporate the Polish entity, complete KRS-related formalities, obtain NIP and REGON, arrange office and governance basics, and prepare ownership and source-of-funds files. Typical duration: 2-5 weeks.
Prepare the business plan, financial model, governance map, AML/CFT framework, Travel Rule procedures, DORA artefacts, safeguarding controls, and outsourcing register. Typical duration: 4-10 weeks depending on complexity.
Run an internal gap analysis covering bankability, staffing, vendor contracts, disclosures, and document consistency. This stage often prevents avoidable regulator questions later. Typical duration: 1-2 weeks.
Before filing in Poland, confirm that a national law has designated the competent CASP authority and that the application procedure is operational. UKNF has stated that proceedings cannot be initiated or completed without that statutory designation. Preparing a dossier does not itself open a filing route or permit regulated activity.
MiCA provides 25 working days from receipt for the completeness check and 40 working days from receipt of a complete application for the authorisation decision. A request for further information made no later than working day 20 of the assessment can suspend that assessment for up to 20 working days; subsequent requests do not suspend it. Preparation and completion of missing documentation add to the overall project timeline. These EU deadlines do not create a Polish filing route before a competent authority has been designated under national law.
After approval, complete final operational conditions, activate banking and vendor arrangements, train staff, finalize control evidence, and prepare passporting notifications if cross-border EU services are planned.
Open the key issues founders, compliance teams and legal leads usually need to confirm before launch.
Yes, in most cases a crypto exchange operating in or from Poland will need CASP authorization under MiCA. The exact services may include exchange of crypto-assets for funds, exchange of crypto-assets for other crypto-assets, execution of orders, or operation of a trading platform. The correct scope depends on how the platform matches orders, holds assets, and interacts with clients.
No, an old Polish virtual-currency registration alone no longer permits continued CASP activity after 1 July 2026. MiCA’s maximum grandfathering period has ended and cannot be extended by Polish legislation or a KNF decision. A provider must have a valid MiCA basis for the relevant services, such as authorisation in an EU home state followed by the required notification for services into Poland. A pending application does not extend the transition.
Class 1 (€50,000) covers execution, placing, reception and transmission of orders, advice, portfolio management and transfer services. Class 2 (€125,000) adds custody and exchange of crypto-assets for funds or other crypto-assets. Class 3 (€150,000) adds operation of a trading platform. For combined services, use the highest applicable Annex IV class. Under Article 67 MiCA, a CASP must maintain prudential safeguards at least equal to the higher of the applicable Annex IV minimum (€50,000, €125,000 or €150,000) and one quarter of the preceding year’s fixed overheads. A provider operating for less than one year uses projected fixed overheads for its first 12 months. The safeguards may consist of qualifying own funds, an insurance policy or comparable guarantee meeting Article 67, or a combination of these.
Yes, foreign ownership is generally possible. What matters is transparency of the ownership chain, source-of-funds evidence, sanctions screening, and the credibility of the management and governance setup. Foreign ownership does not remove the need for a Polish-supervisable entity with real substance and effective control over outsourced functions.
A real operational presence is strongly advisable and often practically necessary. A pure mailbox approach is weak for both licensing and banking. The stronger setup includes a genuine registered office, documented management presence, secure record-keeping, and clear evidence of where operational and governance functions are performed.
A reliable Polish filing-to-decision timetable cannot be offered without confirming that the competent authority and application procedure are legally operational. Once an application can validly be received, MiCA sets the review stages: 25 working days for completeness and 40 working days from receipt of a complete application for a decision, with the limited suspension permitted by Article 63(12). Preparation and missing-document remediation are additional.
Yes, MiCA authorization can support passporting across the EU after the required notification process. Authorization in Poland does not mean instant unnotified activity everywhere. The firm should notify the relevant cross-border services and target states through the proper mechanism, and still comply with local consumer, tax, and marketing rules where applicable.
Not as a simple yes-or-no category. Crypto lending, yield, and earn products require a separate perimeter analysis because the structure may raise MiCA, consumer-law, MiFID II, payment-services, e-money, or even banking-law issues depending on how funds, tokens, returns, and counterparty risk are arranged. Blanket statements that MiCA “allows crypto lending” are legally unsafe.
The old regime was lighter and AML-focused; MiCA CASP authorization is a full prudential and conduct framework. Under MiCA, the applicant must address own funds, governance, safeguarding, complaints, outsourcing, Travel Rule, and ICT resilience. The old Polish virtual-currency registration model should not be treated as equivalent to a MiCA CASP license.
Directors usually need a detailed CV, identification documents, criminal record certificate, integrity and conflict declarations, and evidence of relevant experience. The regulator may also expect questionnaires, time-commitment information, and explanations of the director’s actual role in governance. Stronger files show not only qualifications, but clear responsibility for risk, AML, ICT, or operations oversight.
Yes. RUE supports not only the authorization phase, but also bankability strategy, Polish accounting coordination, AML/CFT implementation, Travel Rule and DORA documentation, outsourcing controls, and post-license governance. Related services include crypto business bank account support, accounting in Poland, and legal services in Poland.
Start with a jurisdiction-by-jurisdiction MiCA comparison rather than generic rankings. Poland can be strong for teams needing substance, local talent, and a credible operating base, but Lithuania, Czech Republic, Malta, or the Netherlands may fit other models better. See our broader MiCA license in Europe hub and country pages such as Lithuania, Czech Republic, and Malta.
