5 key takeaways
- KNF (Komisja Nadzoru Finansowego) is Poland’s financial regulator and the licensing authority for payment institutions, electronic money institutions, investment firms, banks and – once implementing legislation is in place – crypto-asset service providers
- The most common licences for fintechs are: KIP (payment institution), EMI (electronic money institution), and CASP (crypto-asset service provider under MiCA)
- KNF authorisation is entity-specific – it is granted to a Polish legal entity with specific governance, capital, AML/CFT and IT security requirements; it cannot be shared or sublicensed
- The most common causes of delay are: incomplete AML/CFT framework, inadequate governance documentation, and weak business plan financial projections
- KNF’s Innovation Hub provides pre-application dialogue for innovative business models – engaging it early significantly reduces timeline and uncertainty
I regularly advise fintech companies on obtaining KNF authorisation and managing their ongoing regulatory relationship with the Polish financial regulator. KNF licensing in Poland is more demanding than many founders and in-house teams expect – and preparation quality has a direct impact on timeline. This post explains what is required, how long it takes, and what most commonly goes wrong.
For more on choosing the right fintech lawyer for your KNF process, see Fintech Legal Advice in Poland: What to Look for in a Fintech Lawyer.
KNF Licensing Poland Fintech: Which Licence Do You Need?
The answer depends entirely on your business model. Specifically:
| Business model | Licence required | Capital requirement |
|---|---|---|
| Payment initiation, money remittance, card-based payments | KIP (krajowa instytucja płatnicza) | €20,000–€125,000 |
| Digital wallets, stored value, e-money issuance + payments | EMI (instytucja pieniądza elektronicznego) | €350,000 |
| Crypto-asset services (custody, exchange, trading, advice) | CASP (under MiCA) | €50,000–€150,000 |
| Investment services | Dom maklerski / agent firmy inwestycyjnej | Varies |
| Early-stage, Poland only, volume cap | Small payment institution (mała instytucja płatnicza) | None |
For a detailed comparison of KIP and EMI licences, see EMI vs KIP – Which Payment Licence Do You Need in Poland?. For CASP licensing and the current legislative situation, see Poland CASP Licence After the Presidential Veto.
KNF Licensing Poland Fintech: What KNF Looks for
KNF’s authorisation review covers five core areas. Understanding what KNF expects in each area before you submit significantly reduces the risk of questions, supplementation requests and delays.
1. Governance and management
KNF conducts a fit and proper assessment of every member of the management board. Specifically, this covers:
- Professional qualifications and experience relevant to the regulated activity
- Reputation and absence of criminal convictions or regulatory sanctions
- Availability – KNF expects management to be genuinely active in the entity, not nominal
- For non-Polish nationals: understanding of Polish regulatory requirements
Common gap: appointing management board members who have strong business credentials but limited regulated financial services experience. KNF expects management to understand the regulatory framework, not just run the business.
2. AML/CFT framework
AML/CFT is consistently the area where KNF scrutinises applications most carefully. Furthermore, it is the most common cause of supplementation requests and delays. Specifically, KNF expects:
- A documented AML/CFT policy tailored to the entity’s specific products and customer base – not a generic template
- A designated AML officer (AMLCO) physically present in Poland with relevant EU AML expertise
- KYC procedures appropriate to the entity’s customer onboarding process
- Transaction monitoring methodology and escalation procedures
- GIIF reporting procedures
Common gap: AML/CFT documentation that is comprehensive in theory but not operationally realistic – KNF reads policies against the actual business model and asks how they work in practice.
3. Business plan and financial projections
KNF requires a detailed business plan covering the entity’s strategy, revenue model, customer acquisition approach and financial projections. Specifically, projections must demonstrate a realistic path to financial viability – KNF will not authorise a business it does not believe can sustain itself.
Common gap: overly optimistic revenue projections without supporting assumptions, or financial models that do not account for compliance costs, capital requirements and operational overhead in a realistic way.
4. IT security and operational resilience
KNF requires an IT security assessment covering the entity’s systems, infrastructure, data security measures and business continuity arrangements. Additionally, for entities subject to DORA, the IT security framework must align with DORA’s ICT risk management requirements.
Common gap: IT security documentation prepared by the IT team without legal review – missing regulatory requirements or framed in technical language that does not address KNF’s assessment criteria.
5. Safeguarding arrangements
Payment institutions and EMIs must safeguard customer funds – either through segregation in a dedicated account at an EU credit institution or through insurance/guarantee. Specifically, KNF requires documentary evidence of the safeguarding arrangement before authorisation.
Common gap: assuming a Polish bank account is automatically suitable for safeguarding – banks have their own criteria for accepting payment institution safeguarding arrangements and may decline.
KNF Licensing Poland Fintech: The Timeline
| Stage | Typical duration |
|---|---|
| Preparation – governance, AML/CFT, business plan, IT | 2-4 months |
| Application submission | 1 day |
| KNF completeness check | 2–4 weeks |
| KNF substantive review | Up to 3 months (statutory) |
| KNF supplementation requests (if any) | Suspends statutory clock – typically 1–3 months additional |
| KNF decision | Within statutory period from complete file |
| Total typical timeline | 10–14 months from preparation start |
The statutory decision period of 3 months runs from receipt of a complete application. Consequently, the most effective way to shorten the overall timeline is to submit a complete, well-prepared application that generates few or no supplementation requests.
What Happens After Authorisation
Obtaining the licence is the beginning, not the end. Specifically, ongoing KNF obligations for authorised entities include:
- Quarterly and annual reporting to KNF
- Notification of material changes to the business model, governance or shareholding structure
- Maintenance of capital requirements on an ongoing basis
- AML/CFT audits and KNF supervisory inspections
- DORA compliance
- Incident reporting to KNF
Additionally, KNF conducts supervisory inspections of licensed entities – typically focused on AML/CFT compliance, governance and IT security. Consequently, maintaining the quality of your compliance documentation after authorisation is as important as preparing it for the initial application.
If you have questions about KNF licensing or the authorisation process in Poland, get in touch. For more on fintech regulation in Poland, see the FinTech, Banking & Financial Regulation practice area page.
Related posts:
- EMI vs KIP — Which Payment Licence Do You Need in Poland?
- Poland CASP Licence After the Presidential Veto
- DORA Compliance Poland KNF
- Fintech Legal Advice in Poland: What to Look for in a Fintech Lawyer
- Fintech, AI Act and NIS2 Lawyer in Poland
Katarzyna Szczudlik is a Partner at Schoenherr in Warsaw, ranked by Chambers & Partners among Poland’s top FinTech lawyers. She advises fintech companies on KNF licensing, MiCA, DORA and EU regulatory compliance. Get in touch.
