Crypto Licensing Last updated:

MiCA CASP License in Poland

As of , when the Sejm failed to override the veto of the Crypto-Asset Market Act, Poland had no public-administration body designated as the competent authority for MiCA CASP authorisation and no domestic application route. The UKNF, the office of the Polish Financial Supervision Authority (KNF, Komisja Nadzoru Finansowego), published its position on the absence of a designated competent authority on .

This guide explains Poland’s regulatory position in full: the vetoed Crypto-Asset Market Act, the legacy VASP register, the transitional deadline under MiCA Article 143(3), the MiCA capital tiers and DORA obligations that will apply, the penalties for unlicensed activity, and the EU passporting routes operators use while Polish authorisation remains unavailable.

Crypto Licensing in Poland: Quick Overview
Licence TypeMiCA CASP authorisation; no domestic Polish route as of
Competent AuthorityNo Polish public-administration body designated for CASP authorisation. KNF was competent only for electronic-money-token issuers within its existing sectoral remit as of 4 September 2026
Legal FrameworkRegulation (EU) 2023/1114 (MiCA); the Polish implementing act had not entered into force as of
Application StatusNo domestic CASP application could be received or decided
TimelineNo Polish CASP authorisation timeline. Timings from other EU member states are not a Polish regulator clock
Legacy RegisterRegister of virtual currency activities (Tax Administration Chamber, Katowice); closed to new entries since
Transitional Deadline (MiCA Article 143(3))
Prudential safeguards (once operational)Article 67 safeguards: max(€50,000 / €125,000 / €150,000 class floor, 25% of previous-year fixed overheads; projected first-12-month overheads for a new firm). Qualifying own funds, insurance/comparable guarantee, or a combination.
Corporate Tax19% standard / 9% small company (CIT)
FATF StatusNot on any FATF list (never grey- or black-listed); MONEYVAL enhanced follow-up, CEPs from Dec 2025
EU PassportingNot available from Poland yet; CASPs licensed elsewhere passport in under MiCA Article 65
Best ForOperators monitoring the Polish market while authorising via an operational EU regime
DORA ApplicabilityDORA applies EU-wide from , independently of Polish implementation

Poland’s Crypto Licensing Position in 2026

Poland is a large crypto market with a legacy register of virtual currency activities. As of , the national implementing act was not in force, no public-administration body was designated as the competent authority for CASPs, and no domestic MiCA application route existed.[7][22]

Three versions have been vetoed by the President, on , , and .[25]

In short: Poland matters commercially, but as of its CASP regime was not operational. The binding fact for any operator is that the MiCA transitional period ended on : since then, a legacy register entrant without a MiCA authorisation has had no legal basis to serve EU clients. Because Poland could not grant one on that date, operators needing continuity authorise in another EU member state and passport into Poland.

A CASP authorised in another EU member state can serve Poland through MiCA Article 65 passporting. This page therefore separates the current Polish position from indicative application requirements and timings in states that have an operational regime. MiCA capital, conduct, DORA, and Travel Rule obligations apply through the actual home-state authorisation.

Largest CEE Market, Delayed Regulator

Poland’s commercial weight is genuine: a population of about 37 million,[24] a large domestic exchange sector, and a deep developer base. The contradiction is regulatory. The legacy register of virtual currency activities, maintained by the Tax Administration Chamber in Katowice, was a light-touch AML registration, not a MiCA-grade licence.[3] A substantive MiCA authorisation from Poland would need a national act that designates a competent authority, and the vetoed Crypto-Asset Market Act can no longer provide one.

Why the Act Failed

The delay is political rather than technical. The government’s bill designating the KNF as competent authority and setting supervisory fees, sanctions, and transitional rules cleared the Sejm but was vetoed three times by President Karol Nawrocki, who argued the regime was over-restrictive and over-empowered the KNF.[2] The third draft passed the Sejm in and was returned unsigned on , and on the Sejm failed to pass it again (241 votes; 266 required), so the Act has not entered into force. The result is an EU member state with no designated competent authority for CASP authorisation under MiCA.

The Working Route to the Polish Market

While no domestic CASP procedure exists, the Polish market remains fully reachable, and we scope that route in writing before introducing an independent specialist. The MiCA passport under Article 65 lets a CASP authorised in any EU or EEA member state notify its home regulator and provide services into Poland without separate Polish authorisation.[4] Operators targeting the Polish market authorise in a jurisdiction with an operational regime, such as the Czech Republic, Estonia, or Latvia, and passport in.

Under its own engagement with the client, an independent specialist introduced by Jagelski & Partners builds the licensed entity, runs the authorisation, arranges banking, and stands up ongoing compliance, with Article 65 access into Poland from the outset. Polish-resident firms on the legacy register have a clear path too: re-authorise abroad and passport back in, or relocate the business. The deadline has now passed, so this is about restoring a lawful basis, not preserving one.

International Standing

Poland is not on any FATF list and has never been grey- or black-listed; its AML framework is assessed by MONEYVAL, the Council of Europe’s FATF-style regional body. The reputational risks are the MONEYVAL Compliance Enhancing Procedures opened in December 2025 over R.5 and R.20, which are distinct from FATF listing, and the fact that Poland, like Romania, could not authorise CASPs when the transitional period ended on 1 July 2026, covered in full under International Standing below.

Regulatory Framework

Poland regulates crypto-asset service providers under the EU’s Markets in Crypto-Assets Regulation (MiCA), Regulation (EU) 2023/1114,[6] which applies directly as an EU Regulation. MiCA, however, requires each member state to designate a national competent authority and to set supervisory fees, sanctions, and transitional rules in domestic law. Poland’s attempt, the Crypto-Asset Market Act (ustawa o rynku kryptoaktywów), would have designated the KNF as competent authority, but it was vetoed and cannot enter into force.

The UKNF’s published position states that no Polish competent authority for the crypto-asset market has been designated and that, without one, domestic entities lost the ability to provide crypto-asset services after 1 July 2026 while cross-border MiCA services remain possible.[7] See the MiCA guide: framework, requirements, and timeline →

In short: MiCA applies directly, but Poland had no body able to receive or decide a CASP application on 4 September 2026. KNF remained competent for electronic-money-token issuers within its existing sectoral remit. AML supervision of the legacy register remains separate.

Definition: MiCA CASP Authorisation

MiCA CASP authorisation is the regulatory approval required to provide crypto-asset services within the European Union under Regulation (EU) 2023/1114, other than by an eligible financial entity notifying under Article 60.[6] It is granted by a competent authority formally designated by national law and confers EU-wide passporting under Article 65. Poland's vetoed bill proposed the KNF, but no Polish authority had that CASP competence as of 4 September 2026. A MiCA authorisation granted elsewhere is indefinite and carries ongoing prudential, governance, conduct-of-business, and DORA obligations.

Competent-Authority Structure

The vetoed Crypto-Asset Market Act proposed the KNF (Komisja Nadzoru Finansowego) as the competent authority for CASP authorisation and supervision, and it cannot now enter into force. The UKNF’s position confirms that no Polish public-administration body is designated for CASPs, while KNF remained competent for electronic-money-token issuers under its existing sectoral powers.[7] AML/CFT supervision and the legacy register remain separate.

Regulatory History

Poland’s crypto regulation began as an AML registration regime. The register of virtual currency activities (rejestr działalności w zakresie walut wirtualnych) was introduced under the AML Act implementing AMLD5, with the register provisions in force from , and is administered by the Tax Administration Chamber in Katowice.[3][28]

Entry was a notification-and-fit-and-proper process, not a substantive licence: there was no minimum capital and no MiCA-style prudential review.

MiCA became applicable to CASPs on . From that date, in the view of the Director of the Tax Administration Chamber in Katowice, no new entities can be entered in the register, because MiCA applies directly.[27] ESMA’s list of transitional periods shows six months for Poland, but no Polish law shortening the period entered into force, so the MiCA default applied: existing register entrants could continue to under MiCA Article 143(3), as the UKNF’s position confirms.[26][7]

The national implementing Crypto-Asset Market Act has been the obstacle. Successive government drafts were vetoed by the President in and ; a third government version, adopted by the Council of Ministers on , passed the Sejm on (241 votes to 200), cleared the Senate without amendment on , and was transmitted to the President on for signature within the 21-day constitutional window.[20][25]

The President refused to sign it on , and on the Sejm failed to pass it again by the required three-fifths majority.[22] The UKNF’s position confirms that no national act designating a competent authority is in force.[7] The vetoed text had provided that the main provisions would take effect 14 days after publication in the Journal of Laws (Dziennik Ustaw).[20]

Recent Regulatory Developments

Dates below track the Crypto-Asset Market Act and the EU-level transitional position.

  • : The President submitted a new presidential draft Act on the crypto-asset market to the Sejm; it had not been adopted as of .[29]
  • : The Sejm failed to pass the Act again over the third veto (241 votes in favour; 266 required), ending that legislative process.[22]
  • : The Director of the Tax Administration Chamber in Katowice announced that, after , a register entry no longer permits virtual-currency activity in Poland or abroad.[27]
  • : President Nawrocki vetoed the Act for the third time, returning it to the Sejm.[25]
  • : The third Crypto-Asset Market Act passed the Sejm () and cleared the Senate; transmitted to the President for signature on .[2]
  • : ESMA issued a statement confirming the end of MiCA transitional periods applied EU-wide regardless of national implementation status.[5]
  • : President Nawrocki vetoed the second version of the Act.[25]
  • : President Nawrocki vetoed the first version of the Act; the bill returned to the Sejm.[25]
  • : MiCA applicable to CASPs; Tax Administration Chamber in Katowice closed the virtual-currency register to new entries.[27]
  • : Register of virtual currency activities took effect under Poland’s AML Act (AMLD5 implementation).[28]

Regulatory Overlap

EMI/PSD2 overlap: EMT issuance and EMT payment services require separate analysis. The EBA’s non-binding June 2025 opinion treats client EMT transfers and custodial wallets enabling transfers to and from third parties as payment services, while distinguishing exchange and crypto-purchase intermediation. Where PSD2 applies, the relevant services require appropriate PSP authorisation or provision through an authorised PSP under MiCA Article 70(4).[8]

MiFID II overlap: Crypto-assets that confer equity-like rights or are negotiable on capital markets are classified as transferable securities under MiFID II, not MiCA. ESMA’s technology-neutral guidelines (applicable ) establish a substance-over-form classification test.[9]

AML supervision overlap: Even before the MiCA regime opens, register entrants remain subject to Poland’s AML Act, GIIF reporting, and the EU Transfer of Funds Regulation Recast. These obligations did not lapse on ; what lapsed was the legal basis to provide the underlying crypto-asset services.

The 1 July 2026 Transitional Deadline

Because no Polish law shortening the transitional period entered into force, the MiCA default applied. Entities entered in the register of virtual currency activities before could continue providing crypto-asset services until , or until a CASP application was decided, whichever came earlier, under MiCA Article 143(3).[1] The problem is structural: Poland cannot decide a CASP application, because no Polish competent authority has been designated. So for most Polish operators the transitional period simply expired.

In short: was a hard EU-law deadline, not a Polish administrative one. ESMA confirmed in its statement of that after this date, providing crypto-asset services to EU clients without a MiCA authorisation or eligible Article 60 status breaches Union law regardless of a member state’s implementation status.[5][6] Poland’s delayed Act does not extend it. Legacy register entrants had to obtain a MiCA authorisation (necessarily in another member state), or wind down by 1 July 2026.

Key Deadlines

MilestoneDateImpact
MiCA applicable to CASPs30 December 2024Register of virtual currency activities closed to new entries; transitional clock starts
First presidential vetoCrypto-Asset Market Act blocked; no competent authority designated
Second presidential veto12 February 2026Revised Act blocked again; KNF still cannot accept applications
ESMA transitional statement17 April 2026Confirmed 1 July 2026 deadline applied EU-wide; wind-down plans were expected
Third draft to PresidentThird Act passed the Sejm and Senate; sent for signature
Third presidential veto11 June 2026Third Act blocked; Poland passes 1 July 2026 with no CASP route
Transitional period ended1 July 2026Legacy register entrants lose the legal basis to serve EU clients
Veto override failed241 votes, 266 required; the third Act cannot enter into force

Why Poland Cannot Issue Authorisations

MiCA Article 93 requires each member state to designate a national competent authority for CASPs. Poland has not done so in law, because the Crypto-Asset Market Act, which would have made the designation, was vetoed and cannot enter into force.[22] Without a designated authority, the KNF has no statutory basis to receive applications, run completeness checks, or grant authorisations. The legacy register cannot substitute: it is an AML registration administered by a tax body, not a MiCA prudential licence. The result is that Polish-domiciled operators, like those in Romania, where no competent authority has been designated either, have had no domestic route to a MiCA CASP authorisation throughout the transitional period.

The Legacy Register

The register of virtual currency activities is maintained by the Minister of Finance, with functions performed by the Director of the Tax Administration Chamber in Katowice (Dyrektor Izby Administracji Skarbowej w Katowicach).[3] Registration required fit-and-proper directors and an AML programme, but no minimum capital, no MiCA-style own-funds test, and no substantive prudential review.

New entries have not been accepted since . Existing entries conferred the transitional right to operate only until .

Consequences for Unlicensed Operations

From , providing crypto-asset services to EU clients without a MiCA authorisation or eligible Article 60 status carries:[6]

  • Breach of EU law: unauthorised provision is prohibited directly under MiCA from the end of the transitional period, independent of Polish implementation (ESMA, )[5]
  • National criminal penalties proposed but not enacted: the vetoed Crypto-Asset Market Act proposed a fine of up to PLN 20 million or imprisonment for up to 8 years, but those sanctions never entered into force.[2][25]
  • MiCA administrative penalties under Article 111: member states must set maximum fines of at least €5,000,000 or 5% of total annual turnover for a legal person (at least €700,000 for a natural person); Poland has enacted no such penalties and has no competent authority to impose them
  • Wind-down expectation: ESMA expected unauthorised providers to have operational wind-down plans ready before the deadline, implemented without undue harm to clients[5]

The Practical Routes

Now that has passed, register entrants that lost their transitional right have the same three realistic options, set out under Poland’s Position above: authorise in another EU or EEA member state and passport into Poland under MiCA Article 65, relocate the business and client base to that state, or execute an orderly wind-down.

Waiting for Poland is not a fourth option: the vetoed Act can no longer enter into force, and any new implementing act would first have to designate a competent authority before a Polish authorisation procedure could begin.

License Types and Activities Covered

MiCA defines 10 crypto-asset services grouped into 3 classes that determine capital requirements. These classes are set by the regulation itself and will apply in Poland once a Polish competent authority is designated, with no national service categories added. The classification determines the Annex IV class floor: €50,000 for Class 1, €125,000 for Class 2, and €150,000 for Class 3. Prudential safeguards must equal at least the higher of the applicable Annex IV class floor and 25% of the previous year’s fixed overheads. A new firm uses projected fixed overheads for its first 12 months; the permitted deductions apply. Qualifying own funds, an insurance policy or comparable guarantee, or a combination may meet the requirement.

In short: The service taxonomy below is EU-wide and identical to that of every operational MiCA jurisdiction. An operator that authorises in another member state and passports into Poland selects from exactly these 10 services. Most exchange operators require Class 2 (€125,000) or Class 3 (€150,000) authorisation.

Covered Activities

ClassServiceMiCA ReferenceDescription
1Reception and transmission of ordersArt. 3(1)(23)Receiving client orders and routing them to another CASP or trading platform
1Providing advice on crypto-assetsArt. 3(1)(24)Personalised recommendations on crypto-asset transactions
1Providing portfolio managementArt. 3(1)(25)Discretionary management of client crypto-asset portfolios
1Execution of orders on behalf of clientsArt. 3(1)(21)Buying/selling crypto-assets per client instructions
1Placing of crypto-assetsArt. 3(1)(22)Marketing newly issued crypto-assets to investors
1Transfer services on behalf of clientsArt. 3(1)(26)Transferring crypto-assets between addresses on behalf of clients
2Custody and administrationArt. 3(1)(17)Safekeeping crypto-assets and private keys on behalf of clients
2Exchange of crypto-assets for fundsArt. 3(1)(19)Fiat-to-crypto and crypto-to-fiat conversion
2Exchange of crypto-assets for other crypto-assetsArt. 3(1)(20)Crypto-to-crypto conversion
3Operation of a trading platformArt. 3(1)(18)Operating an exchange matching buy/sell orders from multiple parties

What Does NOT Require CASP Authorisation

Services provided in a fully decentralised manner without any intermediary fall outside MiCA’s scope (Recital 22). Unique, non-fungible tokens (NFTs) are excluded, although fractional parts of an NFT are not treated as unique and issuance in a large series or collection is an indicator of fungibility. Crypto-assets that qualify as financial instruments under MiFID II are regulated under existing securities law, not MiCA. Central bank digital currencies (CBDCs), deposits, insurance products, pension products, and securitisation positions are excluded.

DAO, DeFi, and Regulatory Perimeter

MiCA does not explicitly cover decentralised autonomous organisations (DAOs) or DeFi protocols. ESMA has stated that decentralisation exists on a spectrum rather than as a binary classification. Partially decentralised services: such as DEXs with upgrade keys, admin-controlled smart contracts, or governance tokens concentrated among a small group, remain within MiCA’s scope if an identifiable intermediary exists. The KNF has not yet published jurisdiction-specific MiCA guidance on DAOs, DeFi, or decentralised exchanges, in part because the regime is not operational.[9] Operators with hybrid models authorising elsewhere in the EU should seek pre-application engagement with their chosen home regulator.

NFT Classification

NFTs that are unique and not fungible with other crypto-assets are excluded from MiCA under Article 2(3). Fractional parts of an NFT are not treated as unique and non-fungible, so the exclusion does not cover fractionalised units. Issuance in a large series or collection is an indicator of fungibility to be weighed, not a conclusive test, and a unique token does not lose the exclusion merely because it is traded or accumulated speculatively.

The classification is substance-based: MiCA still applies to a token that looks unique but whose actual features or uses make it fungible or not unique, and labelling a token as “NFT” does not determine its regulatory treatment. A token that qualifies as a financial instrument falls outside MiCA under Article 2(4)(a) and is regulated under securities law instead.

Tokenised securities and RWA

MiCA Article 2(4) excludes crypto-assets that qualify as financial instruments. A tokenised security (a tokenised share, bond, or fund unit) is regulated under MiFID II, the Prospectus Regulation, and the EU DLT Pilot Regime (Regulation (EU) 2022/858), supervised in Poland by the KNF, not under MiCA.

ESMA’s Guidelines on the qualification of crypto-assets as financial instruments set the boundary. The honest implication for tokenised real-world assets (RWA): a Polish MiCA CASP authorisation does not cover tokenised securities, which follow the MiFID securities regime instead.

A tokenised fund unit can be a financial instrument and may also require fund or manager permissions. See our fund licensing guide to assess those additional requirements.

Requirements

If Poland opens a domestic regime, a MiCA CASP authorisation will require a Polish corporate entity, prudential safeguards of at least the higher of the EUR 50,000/125,000/150,000 Annex IV class floor and 25% of previous-year fixed overheads (projected first-12-month overheads for a new firm), met by qualifying own funds, insurance or a comparable guarantee, or a combination, a real place of business, fit-and-proper management, and a full compliance documentation suite. These are the EU-wide MiCA requirements; the table below sets them out, flagging where Polish-specific detail depends on an implementing act and regulations. Those instruments were not in force as of .

In short: The prudential and governance bar is set by MiCA itself, so the substance (capital, fit-and-proper, own-funds formula) is known. What is not yet fixed is the Polish procedure: application forms, supervisory fees, and the precise local-presence detail, none of which is set because no implementing Act is in force. Operators authorising elsewhere in the EU meet the same MiCA substance under a regulator that can actually grant the authorisation.

The standard Polish vehicle for a regulated financial business is a spółka z ograniczoną odpowiedzialnością (sp. z o.o., a private limited company) or, for larger operations, a spółka akcyjna (S.A., a joint-stock company). MiCA does not mandate a specific entity form; it requires a legal person with a registered office in the authorising member state, its place of effective management in the EU and at least one director resident in the EU (Article 59(2)).

RequirementDetail
Entity typeSpółka z o.o. (private limited) or S.A. (joint-stock); MiCA requires a legal person with registered office in the authorising state
Annex IV class floor (Class 1)€50,000
Annex IV class floor (Class 2)€125,000
Annex IV class floor (Class 3)€150,000
Ongoing higher-of testHigher of: permanent minimum per class OR 25% of fixed overheads of the preceding year (MiCA Article 67)
Management bodyMembers of sufficiently good repute with appropriate knowledge, skills and experience, collectively able to understand the business (Article 68)
Place of businessRegistered office in the authorising member state, place of effective management in the EU, at least one EU-resident director (Article 59(2)); letterbox entities not accepted
Foreign ownership100% foreign ownership permitted under MiCA
Qualifying shareholdersAll holders of 10%+ capital/voting rights undergo fit-and-proper assessment with source-of-funds verification
Polish CASP supervisory feesNo domestic CASP fee schedule was in force as of 4 September 2026
Prudential safeguardsOwn funds, an insurance policy or a comparable guarantee, or a combination (MiCA Article 67(4)); insurance is optional

For MiCA CASPs, the amounts shown are Annex IV class floors. Prudential safeguards must equal at least the higher of the applicable Annex IV class floor and 25% of the previous year’s fixed overheads. A new firm uses projected fixed overheads for its first 12 months; the permitted deductions apply. Qualifying own funds, an insurance policy or comparable guarantee, or a combination may meet the requirement. MiCA Article 67(1)–(4).

Fit-and-Proper Assessment

MiCA requires the competent authority to assess directors, senior managers, qualifying shareholders, and key function holders against fit-and-proper criteria: professional qualifications and experience, reputation and integrity (criminal background, regulatory history), financial soundness, and the collective knowledge of the management body. Across operational MiCA jurisdictions, the most common failure point has been inability to demonstrate the legitimate origin of owners’ capital. Polish-domiciled applicants will face the same test, but only once a competent authority exists to apply it.

Local Presence and Substance

MiCA requires genuine substance: a registered office in the authorising member state, the place of effective management in the EU, at least one director resident in the EU (Article 59(2)), and an organisational structure that allows the competent authority to supervise the entity. A letterbox arrangement with management outsourced to another jurisdiction does not satisfy this. For Poland specifically, a future implementing act and the authority it designates would set the operational detail, but the underlying MiCA substance test is set by the regulation and is the same in every member state.

AML/CFT and Travel Rule

Poland’s AML framework is governed by the Act on Counteracting Money Laundering and Terrorist Financing of 1 March 2018, supervised by the GIIF.[10] The EU’s Transfer of Funds Regulation Recast (Regulation (EU) 2023/1113) applies directly. There is no de minimis threshold for CASP-to-CASP transfers: full originator and beneficiary information must accompany every crypto transfer regardless of amount. The €1,000 threshold applies only to transfers involving self-hosted wallets: above it, the CASP must assess whether its client owns or controls the unhosted address.[11]

Sanctions screening must cover EU sanctions lists (mandatory) and UN sanctions lists (implemented via EU legislation). OFAC screening is not legally mandatory in Poland but is strongly recommended given extraterritorial reach and correspondent banking expectations. Suspicious transaction reports are filed to the GIIF. These AML obligations bind register entrants now and will bind Polish CASPs once authorised.

Authorisation Process

There was no operational CASP authorisation process in Poland as of : no Polish public-administration body had been designated to receive or decide applications. The process below is therefore the standard MiCA authorisation pathway in member states with live regimes, which is the route operators targeting the Polish market use. The substantive criteria are set by MiCA, but a future Polish procedure depends on an implementing act.

In short: Under MiCA, the competent authority has 25 working days to confirm completeness and 40 working days for substantive assessment (from receipt of the complete application; suspended for up to 20 working days by a written information request made by working day 20). The realistic end-to-end timeline, including entity formation and documentation, is about 5–8 months. That timeline is why waiting for the KNF was not viable before the deadline: a fresh authorisation could not complete in the window that remained.

Where the application is filed: in the chosen home member state, through that regulator’s electronic portal, in that state’s required language. If a future implementing act designates a Polish competent authority, Polish applications would be filed with it; until then, applicants file with an operational EU regulator and rely on MiCA passporting for Polish market access.

Stage 1 2–6 weeks

Entity Formation and Prudential Safeguards

Incorporate a legal person in the authorising member state. See the European company formation guide → Put in place prudential safeguards of at least the higher of the EUR 50,000/125,000/150,000 Annex IV class floor and 25% of previous-year fixed overheads (projected first-12-month overheads for a new firm), met by qualifying own funds, insurance or a comparable guarantee, or a combination. Appoint the management body (members of good repute with the knowledge and experience MiCA Article 68 requires, at least one of them resident in the EU), a compliance officer, and an AML officer. Establish a real registered office in the authorising member state and effective management in the EU.

Stage 2 6–10 weeks

Compliance Documentation Preparation

Draft the full documentation suite required under MiCA Article 62 and Commission Delegated Regulation (EU) 2025/305. This includes the AML/CFT policy manual, enterprise-wide risk assessment, sanctions screening procedures, transaction monitoring framework, Travel Rule implementation documentation, KYC/CDD procedures, business continuity plan, DORA/ICT risk management framework, cybersecurity policies, complaints handling, conflicts of interest, and wind-down plan. Each document must be bespoke to the applicant’s business model.

Stage 3 2–4 weeks (parallel)

Banking and Payment Infrastructure Setup

Open a corporate bank account in the authorising state. Unless the CASP is itself a credit institution, e-money institution, or payment institution, MiCA Article 70(3) requires client funds other than e-money tokens to be placed with a credit institution or a central bank by the end of the following business day, in an account separately identifiable from the CASP’s own: an EMI account does not satisfy this.

Stage 4 1–2 weeks (optional)

Pre-Application Engagement

Many EU regulators offer informal pre-application engagement where prospective applicants present their business model and governance framework for preliminary feedback before the statutory clock begins. This is not mandatory but reduces later requests for information.

Stage 5 1 week

Formal Application Submission

Submit the complete application to the home competent authority with all annexes required by MiCA Article 62 and the implementing RTS. Pay the applicable national application fee.

Stage 6 Up to 25 working days

Completeness Assessment

The competent authority verifies that all required documentation has been submitted. If incomplete, it sets a deadline for the missing information; the 40-working-day assessment runs from receipt of the complete application. Poorly prepared applications stall at this stage.

Stage 7 40–60 working days

Substantive Assessment and Decision

The competent authority assesses the application against MiCA’s authorisation criteria. A written information request made by working day 20 suspends the assessment once, for up to 20 working days; later requests do not. Authorisation is published in the national CASP register and notified to ESMA for the EU-wide register, after which Article 65 passporting into Poland is available.

Required Documents

MiCA CASP documentation requirements follow MiCA Article 62 and Commission Delegated Regulation (EU) 2025/305, which standardise the application form and supporting annexes across the EU.[12] If a future implementing act designates a Polish competent authority, that authority would publish the Polish application form and any national annexes; the substantive content below is set by the regulation and applies whichever member state authorises the entity.

Corporate Documents

Certificate of incorporation from the relevant company register (in Poland, the National Court Register, Krajowy Rejestr Sądowy). Articles of association. Shareholder register. Evidence of the prudential safeguards under MiCA Article 67 (a bank statement for own funds, or the insurance policy or guarantee). LEI (Legal Entity Identifier). Proof of registered office address.

Personal Documents (All Directors, Officers, and Qualifying Shareholders)

Valid government-issued photo identification (passport or national ID). Curriculum vitae (CV) with detailed professional history. Criminal record certificates from each country of residence in the past 10 years. Declaration of good repute and absence of pending proceedings. Evidence of professional qualifications, skills, and experience relevant to the role. For qualifying shareholders (10%+): detailed source-of-funds and source-of-wealth documentation, the most scrutinised element in MiCA applications.

Compliance Documentation

The compliance documentation suite is the most heavily scrutinised component of any MiCA CASP application. Each document must be bespoke, reflecting the applicant’s specific business model, risk profile, and operational structure: generic templates adapted from other jurisdictions are a common cause of delay and rejection. The accordion below summarises the core documents required under MiCA and the implementing RTS.

The manual must set out the methodology for customer risk categorisation, enhanced due diligence triggers, PEP screening procedures, and the interface with the national financial intelligence unit’s reporting system. In Poland, AML supervision sits with the GIIF under the 2018 AML Act.

The risk assessment must cover the applicant’s client geography, product set, and delivery channels, including exposure to higher-risk flows identified in the national risk assessment. It must be dynamic and updated at least annually.

CASPs must screen against EU consolidated sanctions lists (mandatory) and UN sanctions lists (implemented via EU legislation). The procedures must specify screening frequency (real-time at onboarding, ongoing monitoring thereafter), the technical solution used, false-positive management, and the asset-freeze notification obligation to the national authority.

The framework must address on-chain analytics capability, thresholds for automated alerts, escalation procedures, and investigator workflows, integrated with the national STR filing system.

The documentation must specify the messaging protocol (IVMS101, OpenVASP/TRP, or proprietary), the process for assessing whether the client owns or controls a self-hosted address for transfers exceeding €1,000, and interoperability arrangements with counterparty CASPs. There is no de minimis threshold for CASP-to-CASP transfers.

Reports are filed to the national FIU (in Poland, the GIIF). The procedures must cover reporting deadlines, staff training, internal escalation, tipping-off prohibitions, and record retention.

The procedures must differentiate between individual and institutional clients (KYB), specify document requirements for each risk category, and address remote onboarding technology (video verification, electronic identification) consistent with the EU AML framework.

The documentation must address all five DORA pillars. DORA applies directly across the EU; the competent authority of the authorising state is the DORA enforcement authority for that CASP. See the ICT Risk Management section below for full details.

MiCA requires CASPs to establish and maintain effective complaints handling procedures. The policy must specify response timeframes, escalation procedures, and record-keeping, and must be published on the CASP’s website.

The policy must address conflicts arising from proprietary trading, employee personal dealing, related-party transactions, and incentive structures, with specific procedures for disclosure when conflicts cannot be avoided.

Business Plan and Financial Projections

Programme of operations per MiCA Article 62(2)(d): description of all crypto-asset services to be provided, target markets, client profile, marketing strategy. Three-year financial projections including revenue model, cost base, capital adequacy forecasts, and break-even analysis. Description of the governance structure and internal control mechanisms.

Technology and Operational Documentation

IT architecture documentation. Cybersecurity policy and penetration test reports. Hot/cold wallet management and key management procedures (for custody service providers). Business continuity plan and disaster recovery procedures. Third-party ICT provider register (DORA requirement). Incident response plan for major ICT incidents.

Fees and Costs

Poland did not have a domestic CASP application fee or supervisory contribution in force as of . The cost profile below is therefore the typical Year 1 cost of a MiCA CASP authorisation obtained through an operational EU regime, which is the route Polish-market operators use today, and it is split into what a regulator charges and what the work costs. The capital, documentation, personnel, and ICT components are MiCA-driven and broadly comparable across member states; only the government-fee line varies materially by jurisdiction.

Statutory Cost, Year 1 (Planning Figure)

Statutory charge (EUR)Low (Class 1)Mid (Class 2)High (Class 3)
Regulator fees at the chosen passport state (application + first-year supervision), planning figure€3,500€6,000€10,000
Statutory cost, Year 1 (planning figure)€3,500€6,000€10,000

Poland’s own numbers cannot be put in this table yet. No domestic CASP application fee or annual supervisory contribution was in force as of , so the statutory line above is our planning figure for regulator fees at the passport state an operator chooses, not a published tariff and not a Polish charge. It will be replaced only if Poland creates an operational domestic route and publishes a schedule.

Typical Build, Year 1 (Quoted Per Case)

Cost Component (EUR)Low (Class 1)Mid (Class 2)High (Class 3)
Entity formation and registration€3,000€5,000€7,000
Legal advisory (application preparation)€10,000€25,000€50,000
Compliance documentation (AML/CFT policy suite, risk assessment, Travel Rule, sanctions screening)€5,000€15,000€25,000
Technology/ICT documentation (DORA, cybersecurity, BCP)€5,000€10,000€20,000
Personnel (compliance + AML + operations, annual)€36,000€72,000€120,000
Office and operational costs (annual)€6,000€12,000€24,000
External audit (annual)€5,000€10,000€15,000
Banking setup€500€1,000€2,000
Prudential safeguards, if funded as own funds (planning assumption; held, not consumed)€50,000€125,000€150,000
Typical build, Year 1 (quoted per case, excl. own funds)~€70,500~€150,000~€263,000
Total cash outlay, Year 1 (statutory + build + own funds)~€124,000~€281,000~€423,000
Typical build, annual from Year 2 (excl. capital)~€55,000~€100,000~€170,000
[ Scope ] The statutory figure is our planning figure for what the regulator of the chosen passport state charges; published fees differ by state. The build figure is an indicative planning estimate that varies by specialist, scope and client profile, not a quotation: the partner who carries the mandate prices consultation, the application file, the compliance build and the ongoing programme per case, because every case differs. Jagelski & Partners charges the client nothing.

Note: the build figures are indicative of a MiCA CASP authorisation via an operational EU regime, not Polish pricing: no Polish CASP fee schedule existed as of 4 September 2026. No Polish annual supervisory contribution is carried in either figure, because none is set. The prudential requirement (€50,000–€150,000 by class) may be met with own funds, an insurance policy or a comparable guarantee, or a combination (MiCA Article 67(4)); held as own funds, it is retained, not consumed. The ongoing obligation is the higher of the permanent minimum or 25% of the preceding year’s fixed overheads.

No Polish CASP application or supervisory fee applied as of , because no competent authority or domestic application route had been established. The figures above describe an authorisation in another EU member state.

Timeline

No Polish CASP authorisation timeline exists. As of , no Polish body could receive or decide a CASP application. The stages below are an indicative MiCA process in another member state with an operational regime.

StageDurationCumulative
Entity formation and prudential safeguards2–6 weeks2–6 weeks
Compliance documentation preparation6–10 weeks8–16 weeks
Banking and payment infrastructure (parallel)2–4 weeksParallel with Stages 2–3
Pre-application engagement (optional)1–2 weeks9–18 weeks
Formal application submission1 week10–19 weeks
Completeness assessmentUp to 25 working days15–24 weeks
Substantive assessment40–60 working days23–36 weeks
Total (planning range)About 5–8 months23–36 weeks

The 5–8 month planning range is for a MiCA authorisation obtained through an operational EU regime; complex applications can extend to 9–12 months.

Taxation

Poland applies a standard corporate income tax (CIT) rate of 19%, with a reduced 9% rate for a small taxpayer (prior-year sales revenue up to the PLN equivalent of €2 million) or in the first year of business, provided tax-year revenue also stays within that limit (prorated by full months for a tax year longer or shorter than 12 months) and no Article 19 exclusion applies (the 9% rate does not apply to capital-gains income).[13] Individuals are taxed at a flat 19% on crypto gains (declared on form PIT-38), realised only when crypto is exchanged for fiat or used to pay for goods. Exchanging crypto-assets for traditional currency, and back, is VAT-exempt following the Court of Justice ruling in Hedqvist (C-264/14).

TaxRateCrypto Application
Corporate income tax19% (standard)All CASP profits
Small taxpayer rate9% (small taxpayer, i.e. prior-year revenue ≤ ~€2,000,000, or first year of business; tax-year revenue ≤ ~€2,000,000 in either case, prorated for a tax year that is not 12 months; Article 19 exclusions apply)Available on non-capital-gains income if the CASP qualifies as a small taxpayer
Capital gains (corporate)19% (separate capital-gains basket)Virtual-currency disposals by ordinary corporate holders; providers of the exchange, intermediation, or account services covered by AML Act Art. 2(1)(12) report these proceeds as ordinary income instead (CIT Act Art. 7b(3))
Capital gains (individual)19% (PIT-38, flat)Realised on crypto-to-fiat disposals; crypto-to-crypto swaps are not taxable events
VAT23% standard; fiat–crypto exchange VAT-exemptCrypto-to-fiat exchange exempt per Hedqvist ruling
Dividend withholding (to companies)19%Exempt if ≥10% holding for ≥2 years (EU participation exemption)
Dividend withholding (to individuals)19%Withheld at source
Interest withholding0% (EU/DTT) / 20%Depends on recipient jurisdiction and treaty
Employer social contributions~19.2%–22.4%On gross salary; band varies with the accident-insurance rate. Employee pays a further ~13.7%
Note on the corporate-tax picture: Poland’s headline 19% CIT and 9% small-taxpayer rate are unaffected by the crypto-licensing impasse: tax law and the MiCA implementing Act are separate instruments. The tax treatment of a Polish-domiciled crypto company is settled; what is unsettled is whether that company can hold a Polish CASP authorisation at all.

Tax Considerations

For an ordinary corporate holder, proceeds from disposing of virtual currency fall into the separate capital-gains basket for CIT purposes, which means losses in that basket cannot offset operating income. For individuals, only crypto-to-fiat disposals and payments for goods or services are taxable; crypto-to-crypto exchanges are not taxed at the point of swap.

The rule differs for virtual-currency service providers. Under Article 7b(3) of the CIT Act, a taxpayer carrying on the activity covered by Article 2(1)(12) of the Anti-Money Laundering Act (exchanging virtual currencies for means of payment or for other virtual currencies, intermediating in that exchange, or keeping the related accounts) treats those proceeds as ordinary income, not capital gains.[31] That classification does not by itself secure the 9% rate, which also requires small-taxpayer status (except in the year the business starts), tax-year revenue within the PLN equivalent of €2 million (prorated by full months for a tax year longer or shorter than 12 months), and no Article 19 exclusion, such as those for companies formed through a restructuring or a contribution of an existing business.

Poland also offers an Estonian-style lump-sum corporate tax (CIT estoński) that defers tax until profit is distributed, but only to a company owned solely by natural persons that holds no shares in other companies and meets staff and passive-income conditions; banks, investment firms, insurers, investment funds, and loan institutions are excluded.[30] A holding-owned CASP therefore cannot use it, and for an eligible one the interaction with its capital obligations needs case-specific analysis.

DAC8 / CARF Reporting

Poland has transposed the DAC8 Directive (Council Directive (EU) 2023/2226), which obliges crypto-asset service providers to report user transaction data to the Polish tax administration (KAS).[14][21] The Polish implementing act, the Act of amending the Act on the exchange of tax information with other countries, was published in the Journal of Laws on and entered into force the next day.[21] It treats 2026 as the first reporting period: reporting providers file 2026 data with the Head of the National Revenue Administration by , and the first automatic exchanges follow in 2027.

Providers subject to Poland’s crypto-reporting rules must request tax self-certification by from users who were their clients on . Article 8 of the implementing Act requires follow-up requests where the user does not respond. If the declaration is still missing on despite those requests, the provider must prevent reportable transactions until the declaration is supplied and its correctness and reliability are verified.[21]

DAC8 transposition runs on the EU timetable, independently of Poland’s failed MiCA implementation, which is why crypto tax-reporting obligations are advancing while CASP authorisation is not.

Pillar Two (Global Minimum Tax)

Poland transposed the EU Pillar Two Directive (the OECD Global Minimum Tax), with top-up taxation in force from .[13] The 15% minimum applies to multinational and large domestic groups with consolidated revenue of €750 million or more, a threshold unlikely to affect standalone Poland-domiciled CASPs.

Ongoing Compliance

A MiCA CASP authorisation creates a permanent compliance infrastructure obligation. The authorisation is indefinite (no renewal), but the competent authority conducts ongoing supervision through annual reporting, periodic inspections, and real-time incident reporting. These obligations are MiCA-driven and apply to a CASP authorised in another member state and passporting into Poland; they would also apply under any future Polish route.

Annual ongoing compliance costs range from roughly €55,000 for a minimal Class 1 operation to €170,000+ for a full-service Class 3 exchange.

In short: The post-authorisation compliance burden is substantial and continuous. CASPs must maintain the organisational structure, capital adequacy, and documentation quality that secured the authorisation. In Poland’s case, a Polish authority would exercise these powers once one is designated; until then, the supervising authority is whichever member state granted the authorisation.

Annual Reporting Obligations

CASPs must submit financial statements, capital-adequacy reports, and activity reports to their competent authority, with annual audited financial statements mandatory. They must also meet AML/CFT reporting to the national financial intelligence unit (in Poland, the GIIF). DAC8 reporting to the tax administration began with reportable-data collection from ; first exchanges are scheduled for 2027.

Supervision Fees

MiCA authorisation is indefinite: there is no renewal fee. Instead, CASPs pay an annual supervisory contribution set by the competent authority. Poland had no domestic CASP supervisory contribution in force as of .

Regulatory Inspections

Competent authorities conduct both scheduled and unscheduled supervisory inspections, with thematic reviews focused on AML/CFT compliance, client-asset segregation, cybersecurity, and governance. AML supervision is typically exercised separately by the national FIU, so an entity can face inspections from both the prudential regulator and the AML authority.

Enforcement

MiCA enforcement powers available to the competent authority include:

  • Administrative fines set in the home state’s law, with maximums of at least €5,000,000 or 5% of total annual turnover for a CASP (MiCA Article 111)
  • Fines for natural persons (directors, officers), with maximums of at least €700,000 set in the home state’s law
  • Public statements naming the entity and the nature of the breach
  • Withdrawal of authorisation
  • Temporary prohibition on management functions
  • Suspension or limitation of services

Advertising and Promotion Rules

MiCA’s marketing communications regime (Articles 7, 29, 53, and 66) applies directly to all CASPs.[6] All marketing must be fair, clear, and not misleading (Article 66(2)); marketing of an offer to the public, or of an admission to trading, of crypto-assets other than asset-referenced and e-money tokens must also state that no competent authority has reviewed or approved it (Article 7(1)). CASPs are accountable for third-party promotional content, including influencer and social media marketing. Google requires valid CASP authorisation for crypto advertising within the EU from , which is itself a practical barrier for Polish operators without a MiCA authorisation.

ICT Risk Management & Operational Resilience

The Digital Operational Resilience Act (DORA, Regulation (EU) 2022/2554) applies to all CASPs authorised under MiCA.[15] DORA has been applicable since and, as an EU regulation, binds directly regardless of the state of Poland’s national crypto legislation. The enforcement authority is the competent authority of the state that authorises the CASP.

DORA leaves administrative penalties to national law (Articles 50 and 51) and sets no turnover-based fine for financial entities; its only percentage cap is a periodic penalty payment of up to 1% of average daily worldwide turnover for critical ICT third-party providers.

In short: DORA creates five operational resilience pillars: ICT risk management, incident reporting, resilience testing, third-party ICT risk management, and information sharing. All CASPs must comply regardless of size, though TLPT (threat-led penetration testing) obligations apply only to entities designated as significant by their competent authority.

Incident Reporting

Major ICT-related incidents must be reported to the competent authority within strict deadlines:

ReportDeadline
Initial notificationas early as possible, within 4 hours of classification as major and normally no later than 24 hours after awareness (if classified after that window, within 4 hours of classification)
Intermediate report72 hours after initial notification
Final report1 month after latest intermediate report

Digital Resilience Testing

All CASPs must conduct general resilience testing under DORA Articles 24–25, including vulnerability assessments and penetration testing. Threat-led penetration testing (TLPT) under Articles 26–27 applies only to entities identified by the competent authority as significant, at least every 3 years. Microenterprises are explicitly excluded from TLPT. Most smaller and mid-size CASPs will not be designated for TLPT but must still conduct general testing.

Third-Party ICT Risk

CASPs must maintain a register of all ICT third-party service providers, including cloud providers, blockchain infrastructure providers, and custody technology vendors. Contractual arrangements must include audit rights, termination provisions, and data localisation specifications.

Wallet and Key Management

CASPs providing custody services must implement segregated hot/cold wallet architectures, multi-signature authorisation for material transactions, key generation in secure environments, and documented key backup and recovery procedures.

Banking

Banking access for crypto-asset businesses connected to Poland is shaped by two factors: the general caution of European banks toward the sector, and the specific problem that a Polish-domiciled operator relying on the legacy register has no MiCA authorisation to present. As that register lost effect on , banks are increasingly unwilling to maintain accounts for entities without a clear path to MiCA authorisation.

In short: The banking challenge is not access to any account but access to the right accounts under the right authorisation. For a CASP that is not itself a credit institution, e-money institution, or payment institution, MiCA Article 70(3) requires client funds other than e-money tokens to be placed with a central bank or a credit institution (not an EMI) by the end of the following business day, separately identifiable from the CASP’s own funds. An operator authorised in another EU member state can satisfy this with a credit-institution relationship there, then serve Polish clients via passporting.

For an entity authorising elsewhere in the EU, the practical structure is two-tier: an EMI account for day-to-day operational flows and a credit-institution account for client-fund safeguarding under MiCA Article 70. Credit-institution accounts are the harder of the two to obtain and typically take 2–4 months, so banking conversations should begin during application preparation rather than after authorisation.

Banking access is a binding constraint, not an afterthought: a crypto authorisation without functioning banking is of little practical use. Operators evaluating EU jurisdictions should treat the depth of the local banking and EMI ecosystem as a selection criterion in its own right, with the safeguarding account in place before resuming the services after the legacy register lapsed on 1 July 2026. Banking for licensed crypto operators →

Jagelski & Partners Banking Partner Network
90+Institutions
€14bnPlaced via the network in 2025
Pre-qualifiedBefore submission

EU EMIs for operational flows, EEA credit institutions for MiCA Article 70 safeguarding, and correspondent rails sized for passported Polish-market volume. Jagelski & Partners scopes banking options in writing and introduces an independent specialist before a licence application is filed. You contract directly with the specialist; account approval remains the financial institution's decision.

Explore Banking Solutions →

FATF Status & International Standing

Poland does not appear on any FATF list. It is absent from both the FATF list of Jurisdictions under Increased Monitoring (the “grey list”) and the list of High-Risk Jurisdictions subject to a Call for Action (the “black list”), and has never been listed under either. As an EU member state, Poland is also outside the scope of the EU list of high-risk third countries, which by definition covers non-EU jurisdictions only.

Poland’s anti-money-laundering framework is assessed by MONEYVAL, the Council of Europe’s FATF-style regional body, rather than by the FATF directly.[16] Poland’s AML legislation, the Act on Counteracting Money Laundering and Terrorist Financing of , transposed AMLD5 and underpins both the legacy register and the GIIF’s supervisory role.

Poland’s FATF and EU list standing is not the reputational risk, although MONEYVAL placed Poland in Compliance Enhancing Procedures in December 2025 over R.5 and R.20;[23] the operational risk is that as of Poland, like Romania, had no competent authority designated for CASP authorisation. That gap is itself a supervisory concern at EU level. ESMA’s statement of made clear that the deadline is not contingent on national implementation, and that competent authorities are expected to ensure orderly wind-downs of unauthorised providers.[5] Since 1 July 2026, Polish legacy registration alone has provided no basis for continuing crypto-asset services in the EU; continued operation requires an applicable MiCA authorisation or another lawful MiCA route.

MiCA Passporting and EU Market Access

MiCA passporting is the mechanism that lets operators serve the Polish market despite the absence of a Polish authorisation. Under Article 65, a CASP authorised in any EU or EEA member state notifies its home regulator of its intention to provide cross-border services or establish a branch in other states. The home regulator passes the notification to the single points of contact of the host states, to ESMA and to EBA; Poland has designated no single point of contact, but the UKNF confirms that CASPs from other member states that have notified their home authority may provide services in Poland.[7] No separate authorisation or additional capital is required from the host country, and services may start once the home regulator confirms the transmission or, at the latest, on the 15th calendar day after the notification was submitted.[4] Both routes are covered: freedom to provide services (cross-border without establishment) and right of establishment (opening a branch). Host NCAs cannot block either route except in extraordinary circumstances.[4]

The MiCA passport extends across the full EEA. EEA jurisdictions Iceland, Liechtenstein, and Norway sit inside the MiCA passport via EEA Joint Committee Decision No 41/2025 of (with supplementary RTS via JCD 138/2025 of ); non-EU/non-EEA jurisdictions in geographical Europe, such as the United Kingdom, Switzerland, and Gibraltar, sit outside the passport regime, so their own rules decide whether serving local clients needs a local licence or registration.[17]

Article 61 reverse solicitation is a narrow, third-country-only exception and is not a route for serving the Polish market: an EU-authorised CASP serving Polish clients does so under Article 65 passporting, not reverse solicitation. The ESMA Guidelines on reverse solicitation () are framed for non-EU operators serving EU clients on a strictly unsolicited basis, with any further same-type marketing confined to the context of the original transaction. See the dedicated reverse solicitation guide for the third-country compliance pattern.[18]

The ESMA Interim MiCA Register has been operational since , published as CSV files updated weekly and listing CASPs authorised across the EU.[19] As of , it listed no CASP with Poland as home member state.

Advantages and Limitations

Poland’s appeal is its market: large, crypto-literate, and underserved. Its limitations as a licensing base are, for now, decisive: there is no operational CASP regime, and the transitional clock has expired. The honest summary is that Poland is a market to serve, not yet a jurisdiction to license in.

  • ✓ Large CEE market. A population of about 37 million makes Poland a large retail market for passported CASPs.
  • ✓ Reachable via passporting. A CASP authorised in another EU state can serve Polish clients under MiCA Article 65 with no separate Polish authorisation, so the market is accessible despite the legislative impasse.
  • ✓ Settled, moderate tax regime. Tax law is unaffected by the licensing delay: 19% CIT, 9% for small taxpayers, and a flat 19% individual rate on crypto-to-fiat gains.
  • ✓ Deep talent and developer base. Poland has one of the EU’s largest pools of software and fintech engineers, attractive for building the operating entity even when it is licensed elsewhere.
  • ✓ Not FATF-listed. Poland has never been grey- or black-listed, although MONEYVAL placed it in Compliance Enhancing Procedures in December 2025.
  • ✓ MiCA framework already known. Once the regime opens, the substantive rules (capital, conduct, DORA) are the EU-standard ones, so applicants can prepare against a known target.
  • × No operational CASP regime. No Polish authority can accept applications: the Crypto-Asset Market Act was vetoed and cannot enter into force. Mitigation: Authorise in an EU member state with a live regime and passport into Poland.
  • × Expired transitional clock. Legacy register rights ended on , with no Polish route to a MiCA authorisation in time. Mitigation: Begin re-authorisation abroad now; a MiCA authorisation project, from entity formation to the regulator’s decision, takes about 5–8 months.
  • × Legislative uncertainty. Three vetoes, the most recent upheld on 4 September 2026, show the outcome is not assured; as of that date Poland, like Romania, had no competent authority designated for CASP authorisation. Mitigation: Do not make business continuity contingent on Polish enactment; treat passporting as the base case.
  • × No domestic authorisation route. MiCA Article 59 bars unauthorised service after the deadline, and no Polish authority can grant the authorisation. Mitigation: authorised status elsewhere with an Article 65 passport, or an orderly wind-down; the window closed on 1 July 2026.
  • × Banking tightening for register-only entities. Banks are wary of crypto firms lacking a MiCA authorisation. Mitigation: Pair re-authorisation abroad with a credit-institution safeguarding account in the authorising state.

How Poland Compares

As of 4 September 2026, Poland could not authorise CASPs, so the meaningful comparison is not Poland versus its peers but where a Poland-focused operator should authorise instead. The natural CEE alternatives are the Czech Republic and Estonia, both with operational MiCA regimes, with Lithuania and Latvia as the Baltic peers. Each offers the Article 65 passport back into Poland, and the Czech Republic, Estonia and Latvia are three routes covered end to end by an independent specialist introduced by this firm.

FactorPolandCzech RepublicEstoniaLithuaniaLatvia
Licence TypeMiCA CASPMiCA CASPMiCA CASPMiCA CASPMiCA CASP
RegulatorNo designated CASP competent authority as of 4 September 2026CNBFinantsinspektsioon (FSA)Bank of LithuaniaLatvijas Banka
TimelineNo Polish CASP authorisation timeline9–18 months6–12 months4–8 months6–9 months
Annex IV class floors€50,000–€150,000 (MiCA, once operational)€50,000–€150,000€50,000–€150,000€50,000–€150,000€50,000–€150,000
Year 1 all-inNot available (no regime)€232,000–€604,000€131,750–€308,500€75,925–€268,425€180,500–€440,500 (excl. capital)
Corporate Tax19% / 9% small21% / 0% holding regime0% retained / 22% distributed (22/78 of the net payout)17% / 7% small0% retained / 20% distributed (20/80 of the net payout)
Local PresenceNo Polish rules in force (4 September 2026); MiCA: registered office, EU management, one EU-resident directorCzech registered office (the CNB flags virtual addresses), EU management, one EU-resident director, MLROOffice, 2+ directors, compliance officerOperation centre, MLRO, board of 3+ and a managerOffice, EU-resident director (Latvia-resident in practice), MLRO, 2+ effective directors
EU PassportingNot available from Poland yetYesYesYesYes
FATF / MONEYVAL statusNot FATF-listed; MONEYVAL enhanced follow-up, CEPs from Dec 2025Not FATF-listed; MONEYVAL-evaluatedNot FATF-listed; MONEYVAL Enhanced Follow-UpNot FATF-listed; MONEYVAL 5th round completeNot FATF-listed; first MONEYVAL 6th-round evaluation
Best ForAs of , a market to serve through passporting, not a licensing baseCEE operators wanting a live, institutionally credible regime near PolandTech-first companies reinvesting profits (0% CIT)Cost-conscious operators; EU access; fintech ecosystemGrowth-stage CASPs wanting regulator-led pre-licensing dialogue and a low EU application fee

For MiCA CASPs, the amounts shown are Annex IV class floors. Prudential safeguards must equal at least the higher of the applicable Annex IV class floor and 25% of the previous year’s fixed overheads. A new firm uses projected fixed overheads for its first 12 months; the permitted deductions apply. Qualifying own funds, an insurance policy or comparable guarantee, or a combination may meet the requirement. MiCA Article 67(1)–(4).

Compare every crypto jurisdiction side by side →

The key difference is: Poland is the only column without a usable timeline, cost, or passport, because its regime is not operational. For a Poland-focused operator, the Czech Republic is the closest functional substitute: a live CNB regime applying MiCA capital minimums directly, in the same CEE market and timezone.

Estonia adds the 0% retained-profit tax advantage for growth-stage reinvestment, and Lithuania offers a deep EMI ecosystem. Latvia matches Estonia on retained-profit tax, applies the MiCA capital floors without a national overlay, charges a €2,500 application fee, at the low end of the EU range, and runs a pre-licensing dialogue and sandbox before the fee is paid. Its price is real local substance: applicants commonly appoint a Latvia-resident board member and hold management-body meetings in Riga, although MiCA requires only an EU-resident director.

An independent specialist introduced by Jagelski & Partners covers end-to-end crypto licensing in the Czech Republic, Estonia, and Latvia: company formation, licence application, banking introductions, and post-licensing compliance, all with Article 65 passporting into Poland. See the full Czech Republic CASP licensing guide →

Czech Republic: a Live CEE MiCA Regime

The Czech National Bank authorises CASPs under an operational MiCA regime applying capital minimums directly, in the same CEE market as Poland and with full passporting into it.

Czech Republic CASP Licensing Guide →

Not sure which column is you? Ask Emma. She compares these jurisdictions in seconds, in your language.

Common Mistakes With the Polish Position

The most damaging errors around Poland are not application errors, because no application can be filed. They are planning errors: misreading the deadline, over-relying on the Polish legislative timeline, and treating the legacy register as if it were a licence. The failure patterns below recur among operators caught by the transition.

  • Assuming the 1 July 2026 deadline depends on Polish law. Planning around a hoped-for national extension is a costly mistake: the deadline is fixed by MiCA, not by the pace of Polish legislation.
  • Treating the legacy register as a MiCA licence. The register conferred only a transitional right to operate until 1 July 2026 and cannot be converted into a CASP authorisation.
  • Waiting for a Polish regime to open before acting. Operators who wait lose continuity; on the MiCA timeline, re-authorisation abroad must begin well in advance.
  • Underestimating banking fallout. Banks increasingly decline crypto firms that hold only a register entry with no MiCA path. Leaving banking until after the deadline risked losing operational accounts at the worst moment.
  • Ignoring the wind-down obligation. ESMA expected unauthorised providers to have operational wind-down plans ready before the deadline. Operators that neither obtain a MiCA authorisation (or, if eligible, notify under Article 60) nor wind down in an orderly way are providing services in breach of MiCA.[5][6]
  • Conflating Polish tax with Polish licensing. Poland’s tax regime is settled and competitive, which can mislead. A favourable tax position does not create a licensing route: the two are governed by entirely separate instruments.

Frequently Asked Questions

Status and Authority

No domestic route existed as of . On that date the Sejm failed to override the veto of the Crypto-Asset Market Act, and the UKNF's position states that no Polish competent authority has been designated, so no Polish body can receive or decide a MiCA CASP application. Operators needing EU passporting use another member state with an operational regime.

No Polish public-administration body was designated as the competent authority for CASP authorisation as of . The vetoed Crypto-Asset Market Act proposed the KNF, and it cannot now enter into force. KNF remained competent for electronic-money-token issuers within its existing sectoral remit. AML/CFT supervision of the legacy register sits with the GIIF and the Tax Administration Chamber in Katowice.

The register of virtual currency activities (rejestr działalności w zakresie walut wirtualnych) is maintained by the Minister of Finance, with functions performed by the Director of the Tax Administration Chamber in Katowice (Dyrektor Izby Administracji Skarbowej w Katowicach). It is a registration regime under Poland’s AML law, not a substantive licensing regime. New entries have not been accepted since . The vetoed Crypto-Asset Market Act would have made the KNF the competent authority for MiCA CASP authorisation, but it cannot now enter into force.

The Deadline

was the end of the MiCA transitional period under MiCA Article 143(3) as applied in Poland. Entities entered in Poland’s legacy register of virtual currency activities before could continue providing crypto-asset services until 1 July 2026, or until their CASP application was decided, whichever came earlier.

After that date, providing crypto-asset services to EU clients without a MiCA CASP authorisation or eligible Article 60 status is a breach of EU law, as ESMA confirmed in its statement of .[5][6] ESMA expected unauthorised providers to have operational wind-down plans ready before the deadline.

The Act was not in force and the KNF was not accepting applications on , so entities relying on the Polish transitional regime lost the legal basis to provide crypto-asset services to EU clients on that date. They still cannot obtain a Polish CASP authorisation because no domestic procedure exists. The practical routes are to authorise in another EU member state and passport into Poland under MiCA Article 65, or to execute an orderly wind-down in line with ESMA’s 17 April 2026 expectations.

No. The deadline is set by MiCA Article 143(3) and confirmed by ESMA’s statement of to apply EU-wide regardless of national implementation status. Even if Poland enacts an implementing act later (the third veto was sustained on ), a competent authority would still need to be designated and stand up an authorisation procedure, and a MiCA authorisation project, from entity formation and documentation to the regulator’s decision, takes about 5 to 8 months.

A late enactment could not have delivered a Polish CASP authorisation before the transitional clock expired, so legacy register entrants seeking to resume services must authorise in another member state (or, as eligible financial entities, notify there under Article 60) and passport into Poland, not wait for Polish law.[6]

The PLN 20 million and eight-year criminal sanctions appeared only in the vetoed Crypto-Asset Market Act and never entered into force. MiCA Article 59 nevertheless bars unauthorised provision of crypto-asset services after the transition. A provider needs authorisation (or, for an eligible financial entity, an Article 60 notification) in an operational EU/EEA regime and an Article 65 passport into Poland, or must wind down.[6]

Requirements and Tax

Poland does not set its own crypto capital figures; MiCA’s prudential requirements apply directly under Article 67 and Annex IV: €50,000 for Class 1 services, €125,000 for Class 2, and €150,000 for Class 3. The ongoing requirement is the higher of the permanent minimum or one quarter of the preceding year’s fixed overheads, met with own funds, an insurance policy or a comparable guarantee, or a combination. These are the same EU-wide thresholds that apply in every member state, so an operator authorising elsewhere in the EU meets the identical capital bar.

Yes. DORA (Regulation (EU) 2022/2554) has been applicable since and applies directly across the EU, including to CASPs authorised under MiCA, independently of the state of Poland’s national implementing legislation. Any operator that obtains a MiCA CASP authorisation, whether in Poland once the regime opens or in another member state, must comply with all five DORA pillars: ICT risk management, incident reporting, resilience testing, third-party ICT risk, and information sharing.

No. MiCA Article 2(4) excludes crypto-assets that qualify as financial instruments, so a Polish MiCA CASP authorisation does not cover tokenised securities. A tokenised security (a tokenised share, bond, or fund unit) is regulated under MiFID II, the Prospectus Regulation, and the EU DLT Pilot Regime (Regulation (EU) 2022/858), supervised in Poland by the KNF, not under MiCA.

ESMA’s Guidelines on the qualification of crypto-assets as financial instruments set the boundary. The real-world-asset (RWA) label alone does not determine the regime. Classify the rights represented by the token before choosing the permission. A tokenised fund unit can be a financial instrument and may also require fund or manager permissions; those questions are not mutually exclusive.

Market Access

Yes. A CASP authorised in any EU or EEA member state can passport into Poland under MiCA Article 65 by notifying its home regulator, which passes the notification to ESMA and the host states; Poland has no designated single point of contact, but the UKNF confirms that such CASPs may provide services in Poland. No separate Polish authorisation or capital is required, and services may start at the latest on the 15th calendar day after the notification. This is why many operators targeting the Polish market authorise in jurisdictions with operational regimes such as the Czech Republic, Estonia, or Latvia and then passport their services into Poland.

Targeting Poland? We cover the working route.

Poland’s own CASP regime is not yet operational, but the Polish market is reachable through MiCA passporting from a live CEE regime such as the Czech Republic, Estonia, or Latvia. Jagelski & Partners scopes that route in writing, then introduces the independent specialist who handles entity formation, regulatory submission, banking, and ongoing compliance, with Article 65 passporting into Poland from day one. The written scope maps the structure, costs, and timeline.

Not ready to submit a brief? Ask Emma first. She answers now and can collect your written brief for a specialist introduction.

References

Show all references
  1. Regulation (EU) 2023/1114 (Markets in Crypto-Assets Regulation, MiCA), Article 143(3) (transitional measures), Official Journal of the European Union, EUR-Lex, accessed .
  2. Wózniak Legal, Poland’s MiCA deadline looms: no CASP law, no licences after 1 July 2026 (covering the Crypto-Asset Market Act, the December 2025 and February 2026 presidential vetoes, and the third 2026 draft), wozniaklegal.com, accessed .
  3. Dudkowiak & Putyra, Changes to the operation of the VASP registry in Poland (register of virtual currency activities maintained by the Director of the Tax Administration Chamber in Katowice; closed to new entries from 30 December 2024), dudkowiak.com, accessed .
  4. Regulation (EU) 2023/1114 (MiCA), Article 65 (cross-border provision of crypto-asset services), EUR-Lex, accessed .
  5. ESMA, Statement on the end of transitional periods under MiCA (ESMA75-113276571-1679), , esma.europa.eu, accessed .
  6. Regulation (EU) 2023/1114 (Markets in Crypto-Assets Regulation, MiCA), Official Journal of the European Union, EUR-Lex, accessed .
  7. Polish Financial Supervision Authority Office (UKNF), Position in connection with the absence of a designated competent authority in Poland for supervision of the crypto-assets market (announcement on knf.gov.pl dated ), knf.gov.pl, accessed .
  8. EBA, Activities on the Markets in Crypto-Assets Regulation (MiCA), including treatment of E-Money Token services under MiCA and PSD2, eba.europa.eu, accessed .
  9. ESMA, Markets in Crypto-Assets Regulation (MiCA): guidelines, interim register, and qualification of crypto-assets as financial instruments, esma.europa.eu, accessed .
  10. Act of 1 March 2018 on Counteracting Money Laundering and Terrorist Financing (Poland; AMLD5 implementation), General Inspector of Financial Information (GIIF), gov.pl, accessed .
  11. Regulation (EU) 2023/1113 (Transfer of Funds Regulation Recast), EUR-Lex, accessed .
  12. Commission Delegated Regulation (EU) 2025/305: RTS for MiCA CASP authorisation under Article 62, EUR-Lex, accessed .
  13. PwC, Poland: Corporate taxes on corporate income (19% CIT, 9% small-taxpayer rate, Pillar Two top-up tax from 1 January 2025), taxsummaries.pwc.com, accessed .
  14. EY, EU adopts DAC8 Directive introducing tax transparency rules for crypto-assets (Council Directive (EU) 2023/2226), ey.com, accessed .
  15. Regulation (EU) 2022/2554 (Digital Operational Resilience Act, DORA), EUR-Lex, accessed .
  16. MONEYVAL (Council of Europe), Poland: country page and mutual evaluation materials, coe.int, accessed .
  17. EEA Joint Committee, Decision No 41/2025 of 20 February 2025 amending Annex IX (Financial services) to the EEA Agreement (incorporation of MiCA); supplementary JCD No 138/2025 of 13 June 2025 (RTS), efta.int, accessed .
  18. ESMA, Guidelines on reverse solicitation under MiCA (ESMA35-1872330276-2030), , esma.europa.eu, accessed .
  19. ESMA, MiCA Interim Register of authorised crypto-asset service providers, esma.europa.eu, accessed .
  20. Kancelaria Prawna Skarbiec, The Crypto-Asset Market Act (ustawa o rynku kryptoaktywów z dnia 15 maja 2026 r.): adoption, transmission to the President on 22 May 2026, and 14-day post-promulgation entry into force, kancelaria-skarbiec.pl, accessed .
  21. Sejm of the Republic of Poland (ELI), Act of 13 February 2026 amending the Act on the exchange of tax information with other countries and certain other acts (Poland; DAC8 transposition, Council Directive (EU) 2023/2226), Dz.U. 2026 poz. 347, published , art. 88l(1) as added, and arts. 9, 10 and 13, api.sejm.gov.pl, accessed .
  22. Sejm of the Republic of Poland, Voting no. 15 at sitting 64 on the President’s request to reconsider the Act of 15 May 2026 on the crypto-asset market (prints 2710 and 2742), , api.sejm.gov.pl, accessed .
  23. MONEYVAL (Council of Europe), Anti-money laundering and counter-terrorist financing measures: Poland, 3rd Enhanced Follow-up Report (adopted December 2025: R.5 and R.20 remain partially compliant; Poland placed in compliance enhancing procedures), rm.coe.int, accessed .
  24. Statistics Poland (Główny Urząd Statystyczny, GUS), Socio-economic situation of the country: demographic situation of Poland in the first half of 2026 (population about 37,243 thousand at the end of June 2026, preliminary estimate), , ssgk.stat.gov.pl, accessed .
  25. Sejm of the Republic of Poland, Presidential requests to reconsider the Act on the crypto-asset market (prints 2048, 2267 and 2710, dated , and ) and Government bill on the crypto-asset market (print 2529, , art. 121: unauthorised crypto-asset services punishable by a fine of up to PLN 20,000,000, up to 8 years’ imprisonment, or both), api.sejm.gov.pl, accessed .
  26. European Securities and Markets Authority (ESMA), List of grandfathering periods decided by Member States under Article 143 of Regulation (EU) 2023/1114 (Poland listed at six months; ESMA notes that some periods were communicated by national authorities before being incorporated into national law), esma.europa.eu, accessed .
  27. Director of the Tax Administration Chamber in Katowice (Dyrektor Izby Administracji Skarbowej w Katowicach), Communiqué on the register of virtual currency activities (no new entries possible from ) and Information for clients of entities entered in the register of virtual currency activities (), gov.pl, accessed .
  28. Sejm of the Republic of Poland (ELI), Act of 30 March 2021 amending the Act on counteracting money laundering and terrorist financing and certain other acts, Dz.U. 2021 poz. 815, art. 1 point 57 (articles 129m to 129z, register of virtual currency activities) and art. 25 point 2 (in force six months after publication on ), api.sejm.gov.pl, accessed .
  29. Chancellery of the President of the Republic of Poland, Nowa inicjatywa ustawodawcza ws. rynku kryptoaktywów (new presidential draft Act on the crypto-asset market, submitted to the Sejm on ), prezydent.pl, accessed .
  30. Sejm of the Republic of Poland (ELI), Corporate Income Tax Act (ustawa o podatku dochodowym od osób prawnych), consolidated text Dz.U. 2026 poz. 554, articles 28j and 28k (lump-sum “Estonian” CIT), api.sejm.gov.pl, accessed .
  31. Sejm of the Republic of Poland (ELI), Corporate Income Tax Act (ustawa o podatku dochodowym od osób prawnych), consolidated text Dz.U. 2026 poz. 554, Article 7b(1)(6)(f) and 7b(3) (virtual-currency proceeds of taxpayers carrying on the activity in Article 2(1)(12) of the Anti-Money Laundering Act are income other than capital gains) and Article 19(1)(2) and (1a) to (1e) (conditions and exclusions for the 9% rate), eli.gov.pl; Act of 1 March 2018 on Counteracting Money Laundering and Terrorist Financing, consolidated text Dz.U. 2025 poz. 644, Article 2(1)(12), eli.gov.pl, accessed .