Small Payment Institution (MIP) in Poland: the “lighter” way to run payment services (and the limits you can’t ignore)

A Small Payment Institution (MIP) lets you offer payment services in Poland with a KNF register entry instead of a full KNF license - but only within strict transaction and client-funds limits. Here’s what it is, what it can do, and when it stops being enough.

In Poland’s payments world, there’s a tempting middle lane.

On one side, you have full-scale regulated players - national payment institutions (KIP) with heavier licensing expectations. On the other, you have startups that want to test a payment idea without building a regulatory “space program” from day one.

That’s where the Small Payment Institution (in Polish: Mała Instytucja Płatnicza, or MIP) comes in. It’s a regulated setup that can let you provide certain payment services under more limited requirements - including, importantly, without applying for a full KNF authorization - as long as you stay inside clearly defined boundaries.

This article explains what an MIP is, what it can do, what it cannot do, and why the limits matter more than most founders expect.

What an MIP is (in plain English)

A Small Payment Institution (MIP) is a legally recognized form of providing payment services in Poland. It can be run by:

• an individual,
• a legal entity (like a company), or
• another organizational unit that has legal capacity under Polish law.

But the key point is this: an MIP must be entered into the KNF register of payment service providers and electronic money issuers. In practice, it’s considered a regulated activity under the Polish Entrepreneurs’ Law (Prawo przedsiębiorców, 6 March 2018). That means you can’t just “start operating” and hope for the best - the activity begins on the date you are entered into the register.

Also important: an MIP can operate only in Poland. You can do business across the country, including via an agent network or a branch - but you don’t get passporting rights like bigger EU-regulated institutions.

The one number you must remember: 1.5 million EUR per month

The biggest structural limitation is volume.

The average monthly total value of payment transactions executed by the MIP over the previous 12 months (including transactions executed through agents) cannot exceed the equivalent of 1,500,000 EUR per month.

This is not “a soft target.” It’s a legal ceiling based on a rolling 12-month average. And the conversion into PLN should use the average exchange rate published by the National Bank of Poland (NBP) on the last day of the month preceding the month in which the threshold is exceeded.

In other words: if your business model can scale quickly, you should treat the MIP as a stage - not a final destination.

What payment services an MIP can provide

An MIP can provide a wide range of mainstream payment services in Poland, including:

1. Cash deposits and cash withdrawals from a payment accountThis also includes the operational actions necessary to maintain the account.
2. Executing payment transactions, including transferring funds to payment accountsThis can happen through:

• direct debits (including one-off direct debits),
• card payments or similar payment instruments,
• credit transfers (including standing orders).

1. Executing payment transactions financed by creditIn other words, the MIP can execute the transactions listed above using funds made available to the user as credit.
2. Issuing payment instrumentsFor example, issuing cards or similar instruments (depending on structure and partnerships).
3. Acquiring (acceptance of payment instruments)This includes enabling merchants to accept payment instruments and processing transactions initiated by the payer’s instrument - especially authorization handling and sending payment orders to the issuer or payment systems - while excluding settlement and clearing activities within a payment system (as understood under Polish settlement finality rules).
4. Money remittanceA classic “send money” service model.

What an MIP cannot do (and what founders often miss)

The definition itself excludes two modern categories:

• payment initiation services (PIS),
• account information services (AIS).

So if your product roadmap is built around open banking features like initiating bank transfers from user accounts or aggregating account data, an MIP structure may not match the scope you want.

Another practical limitation: operating territory. An MIP is allowed to operate exclusively in Poland, even if your app is global and your marketing is in English. If you need cross-border expansion under a single authorization, you’ll likely outgrow this model.

Holding customer funds: the 2,000 EUR cap per user

If the MIP provides the service related to cash deposits/withdrawals from a payment account (the first category above), it may hold users’ funds on users’ payment accounts - but with a strict cap:

At any time, the total amount accepted for one user cannot exceed the equivalent of 2,000 EUR in PLN (using the relevant NBP average exchange rate rule).

For many fintech products, this single limit becomes the real bottleneck. If your users need to keep larger balances (even temporarily), you should plan early how you will handle that - whether through product design (limits, sweeping, faster payouts) or through a longer-term regulatory upgrade path.

Extra activities: FX, safeguarding-related services, and “hybrid” business models

An MIP isn’t forced to be “payments only.”

Besides payment services, it may also provide closely related ancillary services, such as:

• currency exchange (FX),
• secure storage of funds transferred for executing a payment transaction,
• data storage and data processing services.

And an MIP may run other business activities too. When it does, it’s often described as a “hybrid MIP” - a structure where payment services are part of a broader commercial offering.

This is useful for startups that want payments as a feature, not the whole product.

Agents and branches: how an MIP can scale inside Poland

Even though an MIP is limited to Poland, it can still build distribution.

It may provide services via agents - individuals or entities acting in the name and on behalf of the MIP, exclusively within the scope of payment services.

It may also create branches (again, only in Poland). A branch here means an organizationally separated part of the business that performs services outside the registered seat or main place of business.

For teams thinking about merchant networks, field sales, or a regional rollout, this is a real advantage: the MIP model doesn’t force you into a single-office operation.

Who is the MIP model for?

In practical terms, MIP often fits:

• early-stage fintechs testing a payments use case in Poland,
• platforms that need basic payment flows, money remittance, or local acquiring,
• businesses that can live with tight user balance limits,
• teams that want a regulated route without jumping straight into a full licensing process.

And it’s often not ideal for:

• fast-scaling models that will exceed the 1.5M EUR monthly average,
• products built around AIS/PIS (open banking) features,
• businesses needing cross-border EU operations under one permission,
• models where customers regularly hold more than 2,000 EUR.

A quick reality check before you commit

If you’re considering an MIP, ask yourself three questions early:

1. Will our expected transaction volume stay under 1.5M EUR/month on a rolling average?
2. Can our product work if each user’s stored funds are capped at 2,000 EUR (where applicable)?
3. Is Poland-only coverage acceptable for the next 12–24 months?

If you can answer “yes” to all three, MIP can be a smart, pragmatic starting point. If not, it may still be useful - but only as a short stage on the way to a broader regulatory setup.

Disclaimer: This article is for general informational purposes and does not constitute legal advice. If you’re building a regulated payments product, speak with a qualified professional to confirm the right structure for your exact model.