How to Tokenize Assets in Poland: Step‑by‑step Legal & Regulatory Process (2026)

Understanding how to tokenize assets in Poland requires navigating a multi‑layered regulatory framework that spans EU‑wide legislation, national securities law, and fast‑evolving supervisory guidance from the Polish Financial Supervision Authority (KNF). Tokenisation, the process of representing ownership or rights in a real‑world asset (real estate, fund shares, receivables, art, commodities) as a digital token on a distributed ledger, has moved from pilot stage to operational reality for Polish issuers during 2025–2026. This guide maps the complete tokenisation process in Poland across eight sequential stages: legal classification, token design, offering documents, regulatory filings, custody and banking onboarding, AML/KYC implementation, issuance, and post‑issuance compliance.

It is written for founders, CFOs, general counsel, and platform operators who need a concrete legal roadmap before committing capital or approaching investors.

Overview of the Tokenisation Process and Who It Applies To

Tokenization in Poland sits at the intersection of three regulatory regimes. First, the Markets in Crypto‑Assets Regulation (MiCA), Regulation (EU) 2023/1114, which provides a harmonised EU framework for crypto‑assets that do not qualify as financial instruments. Second, Polish national securities law, principally the Act on Public Offering, Conditions Governing the Introduction of Financial Instruments to Organised Trading, and Public Companies, and the Act on Trading in Financial Instruments. Third, the Polish Anti‑Money Laundering Act (ustawa o przeciwdziałaniu praniu pieniędzy), which imposes registration and customer‑due‑diligence obligations on virtual‑asset service providers. The primary regulators are the KNF for financial supervision and licensing, the Ministry of Finance (MF) for policy oversight, and the National Revenue Administration (KAS) for tax treatment.

The tokenisation process in Poland follows a workflow recognised by both the World Economic Forum’s 2025 report on asset tokenisation in financial markets and IOSCO’s 2025 framework on tokenisation of financial assets (IOSCOPD809). At its simplest, the high‑level flow comprises five stages:

1. Confirm asset suitability and transferability.
2. Complete a legal classification of the token (security, e‑money, utility, or other crypto‑asset under MiCA).
3. Design the token structure and legal wrapper (SPV, trust deed, or direct issuance).
4. Prepare offering documents, engage regulators, and onboard custody and banking providers.
5. Issue, distribute, and manage post‑issuance compliance obligations.

This article unpacks each stage into actionable real‑world asset tokenisation steps, including the documents needed for token issuance, indicative costs, and the timeline an issuer should expect.

Eligibility and Prerequisites for Tokenization in Poland

Not every asset or entity is a suitable candidate. Before engaging counsel or technical providers, issuers should evaluate the following prerequisites.

Asset suitability. The underlying asset must be legally transferable, capable of reliable valuation, and supported by clear title or ownership documentation. For real estate, this means a clean entry in the Polish land and mortgage register (księga wieczysta). For fund shares, the fund’s constitutional documents must permit fractional or token‑represented interests. For receivables, the assignment must be valid under the Polish Civil Code. The WEF’s 2025 report identifies transferability, standardisation, and verifiable provenance as the core traits that determine whether an asset is suitable for tokenisation.

Corporate standing. The issuing entity is typically a Polish spółka z ograniczoną odpowiedzialnością (sp. z o.o.) or spółka akcyjna (S.A.), or an EU‑incorporated equivalent that can passport into Poland. The entity must be properly registered in the National Court Register (KRS) and hold a current good‑standing extract.

Token classification triggers. If the token confers profit‑sharing rights, voting rights, or represents a transferable security within the meaning of MiFID II, it will be treated as a financial instrument. This triggers prospectus obligations under the Polish Public Offering Act and KNF oversight. If the token is an asset‑referenced token or e‑money token, it falls squarely under MiCA Title III or Title IV respectively. Utility tokens that do not meet either test follow the lighter MiCA Title II regime (crypto‑asset white paper requirements). Correct classification at the outset determines almost every downstream compliance obligation, and industry observers expect KNF to scrutinise classification opinions more closely during 2026.

Investor eligibility. Offerings restricted to qualified/professional investors may benefit from prospectus exemptions. Public offerings to retail investors trigger full prospectus requirements or, where the total consideration is below the applicable EU threshold, an information‑document obligation.

Foreign Applicant Eligibility

A non‑Polish company can issue tokenised assets to Polish investors, but several practical requirements apply. EU‑incorporated issuers may rely on MiCA passporting rights for crypto‑assets that are not financial instruments, provided the home‑state regulator has authorised the issuer as a crypto‑asset service provider (CASP). For security tokens, the prospectus regime requires approval by the home member state’s competent authority, after which the prospectus can be passported to Poland via KNF notification. Non‑EU issuers will generally need to establish a Polish subsidiary or branch, appoint local legal counsel, and open a local bank account to satisfy banking KYC and AML requirements. Early engagement with a Polish‑qualified adviser is essential to determine whether passporting or local incorporation is the more efficient route.

How to Tokenize Assets in Poland: Step‑by‑Step Procedure

The following numbered steps represent the core real‑world asset tokenisation steps that an issuer must complete. The timeline table below summarises who performs each step and the typical duration.

Step 1, Conduct the Legal Classification Analysis

Every tokenisation project begins with a formal legal opinion determining how the token will be treated under Polish and EU law. Counsel analyses the token’s economic substance, does it confer ownership, dividend or profit rights, voting power, or a right to repayment? If any of these features are present, the token is likely a transferable security under the Act on Trading in Financial Instruments and MiFID II, triggering prospectus and KNF reporting obligations. If the token merely provides access to a service or platform, it may qualify as a utility token under MiCA Title II. Tokens referencing a basket of assets or fiat currency engage MiCA’s asset‑referenced token or e‑money token regimes (Titles III and IV).

The classification opinion should cite the specific statutory provisions, reference the IOSCO 2025 framework on functional equivalence, and address cross‑border scenarios where the token is offered to investors in multiple EU member states.

Step 2, Design the Token Structure and Legal Wrapper

Token design is where legal architecture meets technical specification. The issuer must decide on the legal wrapper: will the token directly represent a registered security (e.g., a registered share in an S.A.), or will an SPV hold the underlying asset and issue tokens representing beneficial interests? For real estate tokenisation, a common structure is a Polish SPV (sp. z o.o.) that acquires the property via notarial deed, with the SPV’s shares or participation units then represented as tokens. The smart contract specification, including the token standard (ERC‑20, ERC‑1400, ERC‑3643, or a permissioned‑ledger equivalent), transfer restrictions, and whitelisting logic, must be drafted to mirror the legal terms of the offering.

Key decisions at this stage include selecting the distributed ledger. The choice should be driven by custody provider support, transaction finality characteristics, smart contract auditability, and regulator familiarity. Ethereum Layer 2 networks, Polygon, and permissioned DLTs are common choices. Industry observers expect KNF to increasingly favour ledgers that support deterministic finality and on‑chain identity verification, consistent with the IOSCO recommendation on operational resilience in tokenised markets.

Step 3, Prepare Offering Documents and Engage Regulators

If the token is classified as a financial instrument and the offering is public, the issuer must prepare a prospectus compliant with the EU Prospectus Regulation (Regulation (EU) 2017/1129) and file it with KNF for approval. KNF’s review period is up to 10 working days for equity securities and up to 20 working days for complex instruments, although these periods restart if KNF issues comments requiring amendments. If the offering is limited to qualified investors or falls below the applicable monetary threshold, a private placement memorandum (PPM) replaces the formal prospectus and does not require KNF approval, though it must still comply with the general anti‑fraud provisions of the Polish Public Offering Act.

For tokens that are not financial instruments but fall under MiCA, the issuer must prepare a crypto‑asset white paper meeting the requirements of MiCA Article 6. The white paper must be notified to KNF (as the designated national competent authority) and published at least 20 working days before the offering date. No prior approval is required for ordinary crypto‑assets, but asset‑referenced tokens require KNF authorisation under MiCA Article 16.

Simultaneously, if the issuer or any intermediary will provide crypto‑asset services (custody, exchange, transfer), they must obtain or verify CASP authorisation under MiCA Title V. This is a separate application to KNF with its own documentation and capital requirements. Token issuance Poland requirements therefore branch significantly depending on the classification determined in Step 1.

Step 4, Onboard Custody, Banking, and Operational Infrastructure

Token custody and banking in Poland is frequently the most time‑consuming step. The issuer must engage an institutional custodian that can hold the tokens (or the private keys controlling them) in segregated accounts and meet the custody requirements under MiCA Article 75 (for CASPs) or applicable national rules (for securities). The custodian will require the issuer to provide corporate documents, a legal opinion on the token’s classification, the smart contract audit report, and evidence of AML/KYC procedures.

Banking onboarding involves opening a fiat‑currency account for investor subscriptions and redemptions. Polish banks conducting enhanced due diligence on token issuers will typically request audited financial statements, a detailed business plan, the prospectus or PPM, and beneficial‑ownership disclosure for the issuing entity. The likely practical effect of the IOSCO 2025 guidelines is that banks will apply heightened scrutiny to token issuance accounts, extending the onboarding timeline to 4–12 weeks in many cases.

Step 5, Implement AML/KYC and Deploy the Smart Contract

Before distributing tokens, the issuer must implement a compliant AML/KYC programme under the Polish Anti‑Money Laundering Act. This includes customer identification, sanctions screening, ongoing transaction monitoring, and suspicious‑activity reporting to the General Inspector of Financial Information (GIIF). For offerings using on‑chain whitelisting (where only KYC‑verified wallet addresses can receive tokens), the smart contract’s transfer‑restriction logic must be tested and audited before deployment.

Smart contract deployment itself is typically completed within 1–7 days. The issuer should commission a third‑party security audit of the smart contract code before deployment. Following deployment, token distribution occurs according to the offering timeline, either on a fixed settlement date or on a rolling basis as investors complete subscription.

Step 6, Manage Post‑Issuance Compliance and Lifecycle Events

Post‑issuance obligations include ongoing investor reporting (financial statements, NAV calculations for fund tokens, rental income reports for real estate tokens), corporate‑action processing (dividends, redemptions, voting), and regulatory reporting to KNF where applicable. If the tokens are admitted to a secondary trading venue, the issuer must comply with market‑abuse rules and, for security tokens, with the transparency obligations under the Polish Public Offering Act. Token holders should receive quarterly or annual reports in a format consistent with the offering documents.

Required Documents and Information, RWA Tokenisation Legal Checklist

The following table consolidates the documents needed for token issuance in Poland. Issuers should treat this as a master checklist and begin assembling documentation as early as Step 1.

Timeline and Key Deadlines for the Tokenisation Process in Poland

End‑to‑end timelines vary substantially based on whether the token is classified as a security or a non‑security crypto‑asset, and whether the offering is public or private.

Scenario A, Private placement of security tokens to qualified investors. Because no KNF prospectus approval is required, this scenario compresses the regulatory step. Typical end‑to‑end duration: 10–16 weeks. The longest single phase is usually custody and banking onboarding (4–12 weeks), which should run in parallel with document preparation.

Scenario B, Public offering of security tokens requiring a KNF‑approved prospectus. The prospectus review adds 4–8 weeks (including potential comment rounds). Total duration: 16–30 weeks (approximately 4–7 months). Issuers should budget additional time if KNF requests supplementary information or if the smart contract audit reveals issues requiring code revisions.

Scenario C, Non‑security crypto‑asset under MiCA (utility token or asset‑referenced token). The white paper notification to KNF requires at least 20 working days before the offering. Asset‑referenced tokens require prior KNF authorisation, which industry observers expect to take 6–12 weeks based on early application volumes. Utility token offerings can realistically launch within 8–14 weeks if custody and banking are pre‑arranged.

Hard deadlines to track include: the 20‑working‑day white paper notification period under MiCA Article 8; prospectus validity (12 months from approval); and AML registration deadlines, which must be completed before any tokens change hands.

Costs, Fees, and Tax Considerations for Tokenization in Poland

The table below provides indicative cost ranges. All figures should be confirmed with service providers, as fees vary by deal complexity, asset class, and cross‑border elements.

Tax considerations. Polish tax treatment of tokenised assets remains an area where early professional advice is critical. Transfers of tokenised real estate may trigger civil‑law transaction tax (podatek od czynności cywilnoprawnych, PCC) at 2% of market value if the transfer is structured as a sale of the underlying property (as opposed to a sale of SPV shares, which carries a 1% PCC rate). Income from token sales is generally subject to a flat 19% PIT/CIT rate on capital gains. VAT treatment depends on whether the token constitutes a financial instrument (exempt from VAT) or a digital service (standard 23% VAT). Issuers should consider applying to KAS for an advance tax ruling to obtain certainty before launch.

What Changes in 2026: MiCA Implications and Supervisory Guidance

The 2026 regulatory environment for tokenization in Poland reflects several converging developments. MiCA’s full application, including the CASP authorisation regime under Title V and the asset‑referenced token regime under Title III, means that any entity providing custody, exchange, or transfer services for crypto‑assets in Poland must hold a KNF‑issued CASP authorisation (or benefit from a transitional grandfather provision, which is expected to expire during 2026 for most Polish operators).

IOSCO’s 2025 report on tokenisation of financial assets (IOSCOPD809) introduced a “same activity, same risk, same regulation” principle that national regulators, including KNF, are expected to incorporate into supervisory practice. The likely practical effect is that KNF will require issuers of tokens with security‑like features to engage with the regulator earlier in the process, before public marketing, and to demonstrate that custody arrangements meet the segregation and operational‑resilience standards set out in the IOSCO framework.

The World Economic Forum’s 2025 asset‑tokenisation report further emphasises interoperability standards and cross‑chain settlement risks, which early indications suggest will inform KNF’s approach to approving custody and settlement arrangements. Issuers planning a 2026 launch should complete a pre‑filing self‑assessment against these standards and be prepared to demonstrate compliance during regulator engagement.

Common Pitfalls and How to Avoid Them

• Mis‑classifying the token. Treating a security token as a utility token to avoid prospectus obligations is the single most common, and most consequential, error. Obtain a formal legal opinion before making any design or marketing decisions.
• Insufficient title verification for real estate. Failing to obtain and review a current certified extract from the księga wieczysta can result in tokenising an asset with undisclosed encumbrances. Always verify title within 90 days of issuance.
• Choosing a non‑custodial model. Self‑custody or unregulated wallet solutions will prevent banking onboarding and may breach MiCA custody requirements. Engage a licensed or authorised institutional custodian.
• Underestimating banking onboarding timelines. Banks apply enhanced due diligence to token issuers. Begin the onboarding process no later than Step 2 to avoid delaying the entire project.
• Inadequate AML/KYC controls. Non‑compliance with the Polish AML Act carries criminal penalties. Implement a full AML programme, including GIIF reporting, before any tokens are distributed.
• Ignoring tax on transfer. PCC, VAT, and income‑tax obligations arise at various points. Engage a Polish tax adviser at the structuring stage, not after issuance.
• Skipping the smart contract audit. Unaudited smart contracts expose issuers to technical exploits and regulatory objections from custodians and KNF. Commission an independent audit before deployment.
• Neglecting post‑issuance obligations. Ongoing reporting, corporate‑action processing, and market‑abuse compliance are not optional. Budget for ongoing administration from the outset.
• Failing to plan for secondary trading. If tokens are transferable, the issuer must consider whether a trading venue is required and what market‑abuse rules apply.
• Overlooking cross‑border investor restrictions. Offering tokens to investors in other EU member states or third countries triggers additional prospectus passporting, regulatory notifications, and potentially foreign AML obligations.

Sources

1. Polish Financial Supervision Authority (KNF)
2. EUR‑Lex, Markets in Crypto‑Assets (MiCA) Regulation
3. Polish Legislation Portal (ISAP)
4. IOSCO, Tokenization of Financial Assets (IOSCOPD809)
5. World Economic Forum, Asset Tokenization in Financial Markets (2025)
6. State Street Global Advisors, Tokenization of Assets
7. Polish National Revenue Administration (KAS)
8. Katten LLP, Tokenization of Real‑World Assets
9. Future Finance Poland, Digital Assets
10. Taurus, Tokenizing Real‑World Assets: Checklist for Issuers