Poland entered the post-transition period with approximately 1,229 entities still recorded in its former Virtual Currency Activities Register. These businesses represented Poland’s established crypto market — but the register itself was not a MiCA authorisation.
Poland Crypto Licensing:
Team in Warsaw. Licence in the EU.
Poland has the talent, customers, and crypto infrastructure to support a serious digital-asset business. But its domestic MiCA licensing route is still unavailable.
Protegra helps Warsaw-based businesses keep their Polish team and operations while placing regulated CASP services inside an authorised EU entity.
We map your services, select the right EU route, structure the relationship between the Polish and authorised entities, and prepare the business for passporting into Poland.
Keep Warsaw for operations. Build the licence where it can work.
Poland remains subject to MiCA, but a domestic CASP authorisation route is not currently operational. An EU-authorised CASP may provide permitted services in Poland after the relevant MiCA notification process.
Built for Crypto — Not Adapted to It
A Poland MiCA project is not a normal licence application. The challenge is connecting the Polish business, the former VASP registration, the crypto product, and an alternative EU authorisation into one structure that can actually operate.
We turn Poland’s regulatory gap into a workable Warsaw-to-EU operating model.
Start your Poland assessment ⟶Schedule a regulatory strategy call ⟶One clear regulatory position
We assess your crypto services and customer flows, your existing Polish registration, your Polish and EU customer targeting, your custody, exchange, transfer, brokerage, and advisory activity, the EU CASP authorisation route, and the passporting, payments, AML/CFT, and tax structure. You receive a practical answer: what can continue, what must change, and what requires authorisation — not conflicting advice from separate providers.
Keep Warsaw. Move the permission.
Your Polish company and team may continue handling technology, operations, product, support, or commercial functions while the authorised EU entity provides the regulated CASP services. We define which entity contracts with customers, which entity holds the authorisation, which functions are outsourced, who owns compliance and MLRO responsibility, and how customer, wallet, data, and reporting flows are controlled. The result is a real group structure, not a foreign licence attached to an unchanged Polish operation.
We manage the transition
For an existing business, we help move from the former Polish registration to a compliant operating model. That may involve reviewing current services and customers, restricting activities that cannot continue, selecting an EU licensing jurisdiction, preparing the CASP application, migrating customers and contracts, reviewing Polish marketing and onboarding, setting up passporting, banking, and payment arrangements, and supporting an orderly wind-down where required.
Your Warsaw team can remain in place. The regulated activity needs to sit within an EU structure that can actually be authorised, supervised, and operated.
Keep the team.
Move the permission.
Poland at a Glance
By the end of the transition period, Poland had issued no domestic MiCA CASP authorisations. The market therefore had a large existing crypto base but no functioning Polish route for a new operator to obtain the authorisation locally.
A CASP authorised in another EU Member State can potentially provide its permitted services in Poland after the MiCA cross-border notification process — and use the same authorisation to access the other EU and EEA markets within its approved scope.
- Category
- What it means for your business
- MiCA status
- MiCA applies directly in Poland, but a Polish company currently has no functioning domestic application route for a new CASP authorisation.
- Home-state authorisation
- The regulated EU entity must be authorised in an EU Member State with an operational MiCA supervisory process.
- Warsaw operating company
- Your Polish company may continue providing permitted technology, operations, customer-support, administrative, or commercial functions, subject to the group structure and regulatory perimeter.
- Regulated entity
- The authorised EU CASP must retain genuine responsibility for the regulated services, including governance, compliance, risk management, customer protection, and regulatory reporting.
- Outsourcing from Poland
- Polish staff and service providers may support the CASP under documented outsourcing arrangements, with oversight, access rights, risk controls, and clear accountability.
- Customer contracts
- The entity providing the regulated service should be clearly identified in customer agreements, terms, disclosures, complaints procedures, and privacy documentation.
- Polish customers
- Customers in Poland may potentially be served by an EU-authorised CASP after the required MiCA cross-border notification, subject to the authorised scope and Polish marketing and consumer rules.
- Website and marketing
- A foreign CASP structure does not automatically make existing Polish advertising compliant. Websites, campaigns, onboarding, and customer communications must be reviewed as part of the transition.
- Existing customers
- Legacy customers may need to be migrated to the authorised EU entity, re-contracted, re-onboarded, or restricted depending on the service model and legal assessment.
- Payment services
- Fiat settlement, e-money-token transfers, payment accounts, and payment processing may require a separate payment-institution or e-money analysis.
- Tax and employment
- The EU licensing structure does not eliminate Polish tax, payroll, employment, transfer-pricing, social-security, or permanent-establishment questions for the Warsaw operation.
- Current position
- Poland’s situation remains politically and legally fluid. The page should be reviewed whenever new national legislation, supervisory guidance, or EU-level enforcement guidance is published.
Put the Permission Where It Works
The EU route is not about abandoning Poland. It is about separating the location of your team from the location of the entity that must hold the regulated authorisation.
Licence
- Holds the MiCA authorisation and contracts with customers for regulated services.
- Owns the regulated policies and controls, and directs compliance and risk management.
- Controls or supervises custody arrangements and maintains regulatory capital.
- Reports to its home-state regulator and manages passporting notifications.
Team
- Software development, product and engineering.
- Customer support, administration, and operational assistance.
- Data and analytics, and marketing support subject to review.
- Non-regulated commercial services.
Structure
- Services agreements, outsourcing, and cost allocation.
- Data access, technology ownership, and incident reporting.
- Customer communications and compliance escalation.
- Management reporting and regulatory access.
The exact allocation depends on the business model, outsourcing arrangements, employment structure, tax position, data flows, and the requirements of the chosen EU regulator.
Keep Warsaw for the operating team. Build the regulated entity around the supervisor that can authorise it.
Assess your group structure ⟶

