What Is a Small Payment Institution (SPI) in Poland in 2026: KNF Limits, ERUP Registration, PSD3 Changes and Who Should Choose SPI

If you are a FinTech founder, compliance officer or legal counsel asking what is a small payment institution in Poland, 2026 is the year you need a definitive answer. Poland’s Payment Services Act (Ustawa o usługach płatniczych) was materially amended in 2023, tightening the scope and supervisory framework for Small Payment Institutions (SPIs, known in Polish as Mała Instytucja Płatnicza or MIP). At the EU level, the PSD3/PSR legislative package has reached late-stage political agreement, and national transposition work is now under way across all member states.

This guide explains the legal definition of an SPI, sets out the concrete KNF limits and ERUP registration process, maps the PSD3/PSR timeline relevant to Polish operators, and provides a practical decision framework for choosing between SPI, authorised payment institution (API) and electronic money institution (EMI) routes.

What Is a Small Payment Institution (SPI / MIP) in Poland?

Legal definition, Mała Instytucja Płatnicza

A Small Payment Institution is a category of payment service provider defined in the Polish Payment Services Act. Unlike a fully authorised payment institution (API), an SPI is entered into a register maintained by the Komisja Nadzoru Finansowego (KNF) rather than obtaining a licence through a full authorisation procedure. The SPI regime is designed to allow smaller operators to provide payment services within Poland subject to simplified prudential requirements and strict quantitative thresholds. The legal basis is the consolidated text of the Payment Services Act published in the ISAP system.

Typical services an SPI can provide

An SPI registered with KNF may offer a defined set of payment services, provided total transaction volumes remain below statutory ceilings. The services generally available to a small payment institution in Poland include:

• Payment account operations. Executing payment transactions such as transfers and direct debits linked to a payment account.
• Card-based payment transactions. Issuing payment instruments or acquiring card transactions within the Polish market.
• Payment initiation services (PIS). Initiating a payment order at the request of a user with respect to an account held at another provider.
• Account information services (AIS). Providing consolidated account information across multiple payment accounts.
• Money remittance. Domestic fund transfers where the payer or payee does not hold a payment account with the SPI.

Importantly, an SPI cannot issue electronic money, that activity is reserved for licensed electronic money institutions. Industry observers note that this restriction is the single most common reason FinTechs eventually upgrade from SPI to an EMI or API licence.

2026 Regulatory Landscape, PSD3, PSR and Polish Payment Services Act Alignment

EU-level status: PSD3 and the Payment Services Regulation

The European Commission published its legislative proposals for PSD3 and the accompanying Payment Services Regulation (PSR) as part of a broader overhaul of the EU payments framework. The package separates the rules into a directly applicable regulation (PSR) and a directive (PSD3) requiring national transposition. By late 2025, the European Parliament and Council of the European Union reached a provisional political agreement on the core texts. Throughout 2026, formal adoption steps and the transposition countdown are progressing in parallel. Member states, including Poland, are expected to begin aligning national legislation with the final PSD3 text once it is formally published in the Official Journal.

The European Parliament’s legislative-train tracker and the Council’s publicly available session documents confirm the advanced stage of negotiations. The European Banking Authority (EBA) has also begun preparatory work on the technical standards and guidelines that will flesh out PSD3/PSR obligations for all categories of payment institution.

How PSD3/PSR changes may affect SPIs

Although PSD3 largely preserves the concept of small or exempt payment institutions, early indications suggest several areas where SPI in Poland new requirements will emerge:

• Stronger customer authentication (SCA) rules. The PSR is expected to refine SCA obligations, potentially extending them to additional transaction types relevant to SPIs.
• Fraud-liability frameworks. Enhanced rules on authorised-push-payment fraud could impose new refund obligations on SPIs handling domestic transfers.
• Open-banking data access. Expanded access-to-account requirements may increase compliance costs for SPIs offering PIS or AIS.
• Supervisory reporting. The likely practical effect will be more granular reporting to KNF, aligned with EBA technical standards.

Poland’s 2023 Payment Services Act amendments

Poland’s 2023 amendments to the Payment Services Act refined several provisions governing SPIs. The changes strengthened KNF’s supervisory powers, clarified the quantitative thresholds triggering a mandatory upgrade to full API authorisation, and tightened AML/KYC record-keeping requirements for registered SPIs. These amendments are reflected in the consolidated text available via the Polish ISAP legislative database.

KNF Rules, Registration and Limits for Small Payment Institutions

Registering as an SPI in Poland, KNF register vs authorisation

The distinction between registration and authorisation is fundamental. A small payment institution in Poland is entered into a public register maintained by KNF upon submitting a complete application and satisfying fitness-and-propriety requirements. This is a lighter process than the full authorisation required for an API, which involves a detailed prudential assessment, minimum capital verification and a more extensive KNF review period. SPIs submit their applications and ongoing declarations through KNF’s electronic system. The register itself is publicly accessible, allowing customers and partners to verify an SPI’s status.

Quantitative thresholds, transaction and turnover limits

The Payment Services Act sets clear quantitative ceilings that define the boundary of SPI operations. If an SPI exceeds these thresholds, it must apply for full API authorisation or cease the relevant services. The key limits under the current framework are:

• Average monthly transaction value. The total value of payment transactions executed by the SPI (including through its agents) must not exceed a statutory monthly average, calculated over the preceding 12 months.
• Territorial restriction. An SPI may only provide payment services within the territory of Poland. Cross-border passporting is not available.
• No e-money issuance. SPIs are prohibited from issuing electronic money, which remains exclusively available to licensed EMIs.
• Threshold-breach consequence. Exceeding the volume ceiling triggers a mandatory obligation to either apply for API authorisation within a defined period or wind down the regulated activities.

The precise numerical thresholds are specified in the Payment Services Act and may be adjusted through implementing regulations. Operators should verify the current figures directly with KNF small payment institutions guidance before submitting an application.

Supervisory fees, reporting cadence and sanctions

KNF charges supervisory fees to all registered SPIs, calculated according to a formula set out in the applicable regulations. SPIs must also submit periodic reports covering transaction volumes, complaint statistics and compliance status. The reporting cadence is typically quarterly or annual, depending on the data category. KNF has the power to remove an SPI from the register, impose financial penalties or require corrective action if the entity fails to meet its obligations, including breaching transaction ceilings, neglecting AML/KYC duties or providing inaccurate reports.

ERUP Registration and Cross-Border Operation

What is ERUP and how does SPI registration work?

ERUP refers to the KNF-maintained register and electronic reporting system used for payment institutions and related entities in Poland. When an applicant seeks SPI register ERUP Poland entry, it submits the required documentation electronically through KNF’s dedicated portal. Upon successful review, the SPI is entered into the public register, which serves as the official record of all entities authorised or registered to provide payment services in Poland. This register is also linked to the EU-level databases that aggregate information about payment service providers across member states, though an SPI’s registration does not confer passporting rights.

Cross-border limits and passporting

The most significant structural limitation of the SPI regime is its territorial restriction. A small payment institution in Poland may only operate domestically, it cannot passport its services into other EU/EEA member states. This stands in stark contrast to fully authorised payment institutions (APIs) and electronic money institutions (EMIs), both of which can notify their home regulator and provide services across the single market through freedom of establishment or freedom to provide services. For FinTech operators planning to serve customers outside Poland, the SPI route is therefore not viable as a long-term licence strategy.

Regarding practical onboarding for foreign founders: a non-resident can establish a company in Poland and register it as an SPI, but the entity itself must be a Polish legal person. Opening a corporate bank account in Poland for the SPI typically requires in-person verification at a Polish bank, although some institutions now support remote onboarding for corporate clients under enhanced due-diligence procedures.

Operational Compliance Requirements for SPIs

Safeguarding of client funds

Every SPI must safeguard user funds received in connection with payment transactions. The Payment Services Act Poland provisions require that funds are either deposited in a segregated account at a credit institution or covered by an insurance policy or comparable guarantee. The safeguarding arrangement must ensure that user funds are protected from the SPI’s own creditors in the event of insolvency. KNF reviews the adequacy of safeguarding arrangements as part of the registration process and during ongoing supervision.

Capital and own-funds requirements

SPIs face lighter capital requirements than APIs. The Payment Services Act does not impose a fixed initial capital requirement on SPIs comparable to the minimum own-funds thresholds that apply to fully authorised institutions. However, KNF expects SPIs to maintain sufficient financial resources to support ongoing operations, cover operational risks and comply with their safeguarding obligations. SPIs must keep accurate accounting records and submit annual financial statements, which KNF may use as a basis for assessing continued fitness.

AML/KYC, transaction monitoring and suspicious-activity reporting

SPIs are fully subject to Poland’s Anti-Money Laundering Act (Ustawa o przeciwdziałaniu praniu pieniędzy) and the corresponding EU AML framework. This means an SPI must:

• Implement a risk-based customer due diligence (CDD) programme, including identity verification at onboarding.
• Conduct ongoing transaction monitoring and screen against sanctions lists.
• File suspicious-activity reports (SARs) with Poland’s General Inspector of Financial Information (GIIF).
• Appoint a designated AML compliance officer and maintain internal AML/KYC policies reviewed at least annually.

EBA guidance on AML/CFT risk factors provides additional supervisory expectations that KNF small payment institutions are expected to follow in practice.

Security of payments and SCA obligations

SPIs must comply with strong customer authentication (SCA) requirements under the current PSD2 framework and will need to adapt to any refinements introduced by the PSR once PSD3 Poland 2026 transposition is complete. Fraud-mitigation measures and IT security controls are reviewed by KNF during inspections.

Operational checklist, first 90 to 180 days

• Appoint a compliance officer with documented AML/KYC expertise.
• Open a segregated safeguarding account at a Polish credit institution.
• Finalise and file the AML/KYC policy with the GIIF and KNF as applicable.
• Deploy transaction-monitoring software calibrated to your product risk profile.
• Implement SCA and IT-security controls meeting PSD2/PSR standards.
• Submit the first periodic report to KNF within the required reporting window.
• Establish a complaints-handling procedure and designate a contact point for KNF correspondence.
• Train all relevant staff on AML, data-protection and payment-services obligations.

SPI vs API vs EMI: Decision Framework, Who Should Choose SPI?

Advantages of choosing SPI

The SPI route offers the lowest barrier to entry for a FinTech that wants to provide payment services in Poland. Registration is faster and procedurally simpler than API authorisation, capital requirements are lighter, and ongoing supervisory costs are lower. For early-stage start-ups testing a domestic product hypothesis, such as a peer-to-peer transfer app or a merchant-payment tool aimed exclusively at Polish users, the SPI framework delivers speed-to-market without the overhead of a full licence.

Limitations of SPI

The trade-offs are material. An SPI is confined to Polish territory, cannot passport services across the EU, and must cease or upgrade operations if transaction volumes breach statutory thresholds. The inability to issue electronic money rules out wallet-based business models that require stored-value accounts. Investors and banking partners may also view an SPI registration as less credible than a full API authorisation, which can affect fundraising and commercial partnerships. The SPI vs API Poland decision therefore depends heavily on growth ambitions.

When to pick API or EMI instead

If your FinTech plans to operate in multiple EU markets, process high transaction volumes, or issue prepaid cards or e-money wallets, an API or EMI licence is the appropriate route. The additional compliance and capital costs are justified by passporting rights, higher volume ceilings and broader permitted activities.

Step-by-Step Timeline and Checklist to Apply for SPI with KNF

Document pack

Before filing your SPI registration application with KNF, prepare the following documents:

• Certificate of incorporation and up-to-date KRS (National Court Register) extract for the Polish entity.
• Business plan covering the planned payment services, target market and projected transaction volumes.
• AML/KYC internal policy, including customer due-diligence procedures and SAR-filing protocols.
• Safeguarding agreement or insurance policy covering user funds.
• IT and operational-continuity plan, including cybersecurity measures and incident-response procedures.
• CVs and fitness-and-propriety declarations for management-board members and key function holders.
• Evidence of adequate financial resources to support operations.

Typical timeline and KNF interactions

Industry observers estimate that a well-prepared SPI registration can be completed within approximately three to six months from initial submission, depending on the completeness of documentation and any KNF queries. KNF may request supplementary information or schedule clarification meetings during the review. Once entered in the register, the SPI may begin offering payment services immediately. Ongoing interactions include periodic report submissions and responses to ad-hoc KNF information requests.

Practical Examples

Domestic payment wallet start-up. A Polish FinTech building a peer-to-peer payment app exclusively for the domestic market chose the SPI route to launch quickly with minimal capital. Within 18 months, transaction volumes approached the statutory ceiling, prompting the company to begin the API authorisation process, a planned upgrade built into its original business strategy.

SaaS merchant-payment enabler. A software company offering invoicing tools to Polish SMEs added an embedded payment feature allowing merchants to collect payments directly. Because all transactions were domestic and volumes were modest, an SPI registration provided the necessary regulatory cover without the cost of a full API licence. The company continues to operate as an SPI while monitoring whether PSD3 Poland 2026 transposition will alter its compliance obligations.

Conclusion and Recommended Next Steps

Understanding what is a small payment institution in Poland is the first step toward choosing the right regulatory pathway for your FinTech. The SPI framework offers a fast, cost-efficient route to market for domestic-only payment services, but it comes with hard limits on territory, volume and permitted activities. With PSD3/PSR transposition on the horizon and KNF supervision tightening, operators should assess their growth trajectory carefully before committing to a registration-only model. For businesses anticipating cross-border expansion or high transaction volumes, early planning for an API or EMI upgrade is essential. Seeking specialist regulatory advice before filing is the most effective way to avoid costly missteps.

Sources

1. Komisja Nadzoru Finansowego (KNF), Small Payment Institutions
2. ISAP, Payment Services Act (Ustawa o usługach płatniczych), consolidated text
3. European Commission, Payment Services (PSD3/PSR)
4. Council of the European Union, PSD3/PSR documents
5. European Parliament, Legislative Train: Payment Services Directive
6. European Banking Authority (EBA), Payment Services and Electronic Money