Poland VASP Redomiciliation: A Compliance Officer's Guide to Post-MiCA Migration

If you are a compliance officer at a Polish VASP, you already know the deadline. 1 July 2026. What you may not yet have a clean answer to is what to do about it, because the standard "apply to your national regulator for a CASP licence" playbook does not currently work in Poland.

This guide is for compliance officers, MLROs, and licensing leads who need to make a defensible recommendation to the board in the next few weeks. We cover the legal position as of May 2026, why redomiciliation has become the realistic primary option for many Polish VASPs, what credible alternative jurisdictions look like, and the operational work that needs to start now.

A quick note on what we are. Fiat Republic is a regulated payments and EMI provider for crypto platforms across the UK and the Netherlands. We are not a Polish law firm, and nothing here is legal advice. What we do see every day is what compliance teams need to put in place to keep their fiat infrastructure running through a licensing migration. That operational view is what this piece adds to the legal picture.

The legal position in May 2026

There are three facts that frame everything else.

First, MiCA Article 143(3) sets a hard transitional backstop of 1 July 2026 for VASPs that were lawfully providing services before 30 December 2024. That date is fixed by EU regulation. It cannot be extended by Polish national law or by a KNF decision.

Second, Poland still lacks a national act implementing MiCA. The Crypto-Asset Market Act (Bill 2064 in its most recent form) has been vetoed twice by President Karol Nawrocki, most recently on 12 February 2026. An attempt by the Sejm to override that veto on 18 April 2026 failed by 20 votes (243 in favour, 263 needed). As of May 2026, Poland is the only EU member state without operational domestic MiCA implementing legislation.

Third, because of point two, KNF has not been formally designated as the competent authority and cannot accept or process CASP licence applications. There is currently no domestic licensing pathway in Poland.

The KNF itself has publicly confirmed this position. In its February 2026 communication, it set out four points that compliance teams should treat as the working baseline:

1. The 1 July 2026 deadline applies regardless of the state of Polish national legislation.
2. Polish VASPs operating under the transitional regime will lose the right to provide crypto-asset services domestically on that date unless they hold a CASP authorisation.
3. CASP authorisation proceedings in Poland cannot begin until a competent authority is designated by national law.
4. CASPs authorised in other EU member states will continue to be able to serve Polish clients via MiCA passporting.

Read together, those points say something quite stark. If you hold only a Polish VASP registration, and Polish national legislation has not been adopted before 1 July 2026, you cannot obtain a Polish CASP licence in time. Your domestic authorisation simply expires.

Why redomiciliation is now the primary option

In a normal MiCA transition, a VASP would file a CASP application with its home regulator, work through the Article 63 timetable (5-day acknowledgement, 25-day completeness check, ~40 working-day decision after the file is deemed complete), and either be authorised before the deadline or, if not, accept a brief operational gap.

That route is closed in Poland. Compliance officers are therefore choosing between four practical options.

Option one: passport in from another EU member state.

Obtain a CASP licence in a jurisdiction with an operational regime, then notify KNF and serve Polish clients on a cross-border basis. This is the route KNF itself has signalled. It works, but it requires you to establish substance and effective management in the new jurisdiction.

Option two: full redomiciliation.

Move the operating entity, including effective management and an EU-resident director, to a member state with an open CASP pathway. This is more involved than passporting alone but produces a cleaner long-term structure for firms whose centre of gravity is no longer naturally in Poland.

Option three: acquire a CASP-ready vehicle.

Acquire an authorised entity, or a near-authorised entity in another member state, and migrate operations into it. Faster on paper, but introduces M&A risk and KNF (or new home regulator) fit and proper review of the change of control.

Option four: wind down EU operations.

For firms whose Polish VASP was their only EU foothold and whose redomiciliation costs do not justify the size of the EU customer book, an orderly exit may be the right answer. This needs to be planned, not improvised.

For most of the firms we speak to, options one and two are the realistic shortlist. Acquisition only makes sense for firms with capital to deploy and a clear acquisition target. Wind-down is a board-level decision that should be made consciously rather than by default.

Choosing a destination jurisdiction

The shortlist that comes up most often in compliance conversations is Lithuania, Ireland, the Netherlands, Estonia, France, Germany, and Malta. The right answer depends on your business model, where your team actually sits, and how much substance you can credibly stand up. A few observations.

Lithuania has historically been the most accessible MiCA pathway and has processed CASP authorisations relatively quickly. It is well understood by crypto firms, and the local advisory ecosystem is mature. Substance requirements are real but achievable.

Ireland offers strong banking access and a familiar common-law framework, which can matter for firms with US or UK parentage. The Central Bank of Ireland scrutiny is rigorous; preparation timelines should be planned accordingly.

The Netherlands combines a credible regulator (DNB and AFM), strong fiat banking infrastructure, and a clear MiCA pathway. Fiat Republic operates here, which is one reason we see the operational picture clearly.

Estonia has worked through its own regulatory tightening cycle and now offers a more selective but well-understood pathway. Good for firms that can meet the substance and capital bar comfortably.

France, Germany, and Malta are credible but tend to involve longer timelines or higher cost bases. For firms with strong local ties to those markets, they make sense; as a generic redomiciliation destination, they are often a second-tier choice.

The trade-offs are not purely about regulatory speed. They include local banking access, the cost and availability of qualified compliance staff, language and translation requirements, supervisory fee structures, and the practical question of whether you can put a credible EU-resident director and effective management in place. A jurisdiction that authorises you in 60 days, but where you cannot open a fiat account in 180 days, is not actually the fast option.

What to prepare now

If your board has not yet picked a path, the work below applies regardless of which option you choose. None of it is wasted effort.

Your authorisation dossier.

Programme of operations, governance structure, AML/CFT framework, KYC procedures, risk management, complaints handling, business continuity, and conflicts of interest. Whichever member state you file in, the substantive content is broadly the same because MiCA Level 2 is harmonised.

Capital and own funds calculations.

Class 1 services (reception/transmission, advice, portfolio management, placement) require €50,000 in own funds. Class 2 (custody, exchange of crypto-assets for fiat or other crypto, execution, transfer) requires €125,000. Class 3 (operation of a trading platform) requires €150,000. On top of that, you need at least 25% of the prior year's fixed overheads. Compliance officers should ensure that finance has a clean, defensible calculation ready.

DORA readiness.

ICT risk management framework, third-party risk register, incident reporting procedures, and a documented testing programme. Most CASP applications are now expected to demonstrate DORA alignment in the file rather than as a follow-up workstream.

Travel Rule infrastructure.

A working Travel Rule solution with documented coverage, fallback procedures, and a clear position on counterparties using non-compatible protocols. This is increasingly being raised in completeness reviews.

Substance.

EU-resident director, effective management in the relevant member state, a real office, and locally based key function holders. This is the single most common reason files stall in the completeness phase.

Fiat infrastructure continuity.

This is the part that disproportionately catches firms by surprise. Banking and EMI relationships do not always survive a redomiciliation cleanly, and onboarding new fiat partners typically takes 60 to 120 days. If your migration plan does not include a tested fiat continuity plan, you have a gap.

A realistic timeline

Working backwards from 1 July 2026, with today being early May 2026, the calendar is tight but workable for firms that move now.

By the end of May, the board needs to have chosen a destination jurisdiction and a path (passporting from a new entity, full redomiciliation, acquisition, or wind-down). Any later than that, and the substance build-out starts to compress.

Through June, the focus should be on substance, banking, and the authorisation file. A complete file lodged in a jurisdiction with an operational regime can realistically be acknowledged within five working days and assessed for completeness within 25.

The 40-working-day decision clock under Article 63 starts only once the file is deemed complete, and questions from the regulator pause it. This is why front-loaded preparation matters more than filing speed: a thin file refiled three times is slower than a thorough file filed once.

Firms that cannot complete authorisation by 1 July 2026 must have a clearly documented contingency. That may mean an orderly suspension of services to Polish-domiciled clients, a reliance on existing CASP-licensed counterparties to continue serving end users, or an interim wind-down. All of these need to be papered now, not in late June.

What this looks like at the fiat layer

A practical observation from the operational side. Most Polish VASPs we speak to underestimate the lead time on fiat infrastructure during a migration. The legal entity changes, the regulatory home changes, and counterparty banks reassess. Even where the underlying compliance posture is strong, KYC refreshes on the bank side commonly take 8 to 16 weeks.

A few things help. Aggregated banking and EMI access through a single provider reduces the number of relationships you have to re-paper. Virtual IBANs that sit under a regulated provider's umbrella can shorten time-to-live in the new entity. Documented compliance-first onboarding reduces the friction in correspondent bank reviews. None of this is unique to redomiciliation, but it matters more under a deadline.

Whether you work with another regulated provider or us, the question to include in your migration plan is the same: how many fiat counterparties do we need to re-onboard, and do we have realistic dates for each?

Frequently asked questions

Can a Polish VASP simply apply for a CASP licence in another member state and continue operating in Poland? Yes, in principle. Once you hold a CASP authorisation from another EU member state, you can passport into Poland by notifying the home regulator. KNF has confirmed that cross-border CASP service provision into Poland will continue to function via MiCA passporting.

Does the Polish VASP entity need to be wound down if we redomicile? Not necessarily. The entity can continue to exist for tax, contractual, or operational reasons. What changes is its regulated activity. Many firms keep the Polish entity as a non-regulated operating subsidiary while the regulated activity sits in the new home jurisdiction.

What happens to existing Polish clients on 1 July 2026 if we have not completed the migration? Without authorisation in another member state, you lose the right to provide crypto-asset services to Polish clients on that date. There is no automatic grace period beyond the MiCA backstop. The board-level decision is whether to suspend services, refer clients to a CASP-authorised counterparty, or wind down.

Will the Polish CASP framework be operational before 1 July 2026? Based on the position as of May 2026, this looks unlikely. The bill has been vetoed twice, and the most recent override attempt failed. Even if a revised bill is introduced and signed, KNF would still need to be designated, and a licensing process would need to be stood up. Compliance teams should plan on the assumption that Poland will not have an operational domestic regime by the deadline and treat any subsequent developments as upside.

Does redomiciliation reset the regulatory clock? For MiCA purposes, the relevant clock is the CASP authorisation in the new home member state. Your Polish VASP history is a relevant background for fit-and-proper purposes, but it does not confer any forward grandfathering rights outside Poland.

Where to go next

If you are at the stage of needing to recommend a path to your board, the most useful thing you can do this week is two things: get a clear written legal position from a firm that practises in your destination jurisdiction, and map your current fiat counterparties against that destination to identify continuity risk.

We work with crypto platforms across the EU and UK on the fiat infrastructure side of MiCA migrations. If you want to talk through what redomiciliation looks like at the payments and EMI layer, get in touch below.