# Payment Providers in Poland: Qualifying BLIK Subscriptions and PLN Payouts

A successful first purchase is an incomplete acceptance test for a subscription business comparing payment providers in Poland. The useful question is whether the PSP can also demonstrate the customer's recurring setup, the intended approval experience at renewal, and what happens when the customer's bank does not support that setup. This changes the provider comparison. A team selling one paid month with optional renewal may make a different checkout decision from a service that needs a recurring arrangement established before it activates an account.

## A numerical starting point for the provider comparison

We reviewed **18 unique historical payment offers** linked only to this country: 15 collection offers and 3 payout offers. They provide a structured starting point for comparing payment costs, access to funds and operational requirements. 187 additional offers linked to several countries are excluded from the country-only calculations below.

The source is the PayStar export dated 14 September 2026, supplied by payment gateways. We recomputed its aggregates, but did not independently verify its commercial statements. This is a historical sample, not a market survey, a count of PSPs or methods, or proof of active connections and current availability. Conditions can change weekly or more often. Independent country, currency and method associations do not establish every possible payment route. Direction counts and settlement-label charts cover all recorded currencies. Only the percentage comparison below is restricted to explicit PLN fee records.

18 unique offers linked only to this GEO, across all recorded currencies; not methods, providers or live connections. [Download SVG](https://paystar.uk/poland-payment-solutions/media/2026-10-08-v2/charts/offers-en-desktop-download.svg)

## What the recorded PLN percentage components show

We calculate the arithmetic mean of explicit percentage components stated in PLN, giving each comparable offer equal weight. A record qualifies only when its structured percentage matches one unambiguous percentage in the original fee description. Offers in another fee currency, missing percentages and ambiguous descriptions are excluded.

We also exclude bound or conditional percentages such as “from”, tiers and explicitly restricted customer categories. Exact nominal percentage components with fixed minimums or caps can remain in the sample; those minimums and caps still affect the final charge.

| Direction | n | Mean | Median | Range |
| --- | --- | --- | --- | --- |
| Collections | 5 | 6.5% | 6.5% | 5.5–8% |
| Payouts | Insufficient comparable data for a published aggregate |

Explicit PLN percentage components only. n is the comparable sample in each direction; missing fees are excluded, not zero. [Download SVG](https://paystar.uk/poland-payment-solutions/media/2026-10-08-v2/charts/fees-en-desktop-download.svg)

**These are percentage components, not all-in payment prices.** Fixed charges, FX, tax, reserves, minimums and charges for refunds or other exceptions must be assessed separately. This sample is not weighted by payment volume, contains no measured conversion rate and cannot rank provider quality. Small or insufficiently independent groups are withheld.

### A hypothetical payment calculation

Take an illustrative payment of 100 PLN; this is not a typical market ticket. Applying the rounded means shown above gives:

- Collections: 100 PLN × 6.5% = **6.5 PLN**.

Each line is a separate direction, not a combined service quote. The arithmetic shows only the percentage part. Ask for an actual quote at your ticket size, volume, business model and settlement currency before calculating net proceeds.

## When money becomes usable matters

Collection offers across all recorded currencies. T/D labels are recorded as supplied, without assuming calendar or business days. Other includes complex labels and pooled groups below 3 records. No guaranteed settlement time. [Download SVG](https://paystar.uk/poland-payment-solutions/media/2026-10-08-v2/charts/timing-en-desktop-download.svg)

A successful payment notification and money available to your business are different events. Treat recorded settlement labels as questions for a provider: what starts the clock, which cut-off applies, are weekends counted, which account is credited, and can a reserve or review delay availability?

For payouts, agree prefunding, beneficiary validation, rejection handling and how returned funds appear in your balance. An incoming-payment settlement label does not prove payout completion time.

### A cash-buffer planning example

If a business must fund 10,000 PLN of obligations per day, a one-day gap requires 10,000 PLN; a three-day gap requires 30,000 PLN. The additional buffer is 20,000 PLN. This is a hypothetical constant-flow model, excluding fees, reserves and volatility, not an observed settlement promise.

## Confirm recurring setup after the first payment

BLIK's operator documentation describes an important conditional outcome. If the bank does not support recurring payments and the documented rejection control is omitted, a positive-value setup transaction can still be presented for approval while the recurring invitation is not shown. The control can instead reject the transaction when the bank lacks support. [BLIK recurring-payment introduction](https://www.blik.com/lp/reccuring-payments/Introduction.html).




For the merchant, the decision is whether a separately paid first period is acceptable. Ask the PSP to demonstrate the resulting payment record and recurring-setup record separately. Decide what the customer should see if money is collected but future billing is not established: access for one period, another payment option, or a support route under the merchant's agreed policy.




This is a proposed acceptance test, not a claim about any PSP's current implementation. Obtain the bank-coverage list and evidence for the exact service being offered before promising automatic renewal to customers.

## Match BLIK recurring payments to the billing plan

The model affects what the customer must approve. Compare it against the actual pricing plan rather than accepting a single “recurring” tick in a proposal.




| Billing requirement | Documented BLIK model | Qualification question |
| --- | --- | --- |
| A fixed charge at a fixed interval, with an end date | Model A provides automatic authorization within those parameters | What happens after a price or billing-frequency change? |
| Variable charges with customer approval | Model M requires confirmation for each recurring transaction | How will the customer complete a pending renewal? |
| Variable charges without confirmation of each transaction | Model O permits that authorization pattern after setup | Is this merchant configured for this model? |




The operator's [Model A](https://www.blik.com/lp/reccuring-payments/Model_A.html), [Model M](https://www.blik.com/lp/reccuring-payments/Model_M.html) and [Model O](https://www.blik.com/lp/reccuring-payments/Model_O.html) guidance describes these distinctions. Model O includes merchant configuration and certification requirements; the existence of the model does not establish access through a particular PSP.




There is a practical detail for plan changes: Model A documentation says that an amount or frequency mismatch requires customer authorization rather than automatic authorization. Ask the provider to show that journey before choosing the model for a product with upgrades or additional usage charges.

## Test a paid month and a later upgrade

Consider a **hypothetical** learning service charging PLN 49 each month. One customer pays for the first month, but no recurring setup is established. Another has a confirmed Model A arrangement at PLN 49, then chooses a PLN 69 plan.




These examples require different decisions. For the first customer, operations needs to know how the next period will be purchased and what communication was agreed at checkout. For the second, the team should test the changed amount and customer approval path with the PSP before displaying “automatically renewed.” Neither case should be decided solely from the first payment's success message.




A useful demonstration includes the invoice reference, setup evidence, change request, transaction result and customer-facing status. Ask how cancellation reaches the merchant's system, how an unconfirmed charge is handled and how a refund is linked to the original payment. These are provider questions, not assumed capabilities or a promise of a particular refund deadline.

## Qualify PLN payouts as a separate service

Collections bring money into the merchant's payment operation. Payouts send money to a recipient; merchant settlement describes how the PSP remits collected funds under its agreement. A recurring BLIK collection demonstration does not answer the latter two questions.




KIR describes **Express Elixir** as a real-time PLN payment system operating around the clock. That is infrastructure context, not a commitment about a PSP's payout API, beneficiary coverage or merchant settlement schedule. [KIR: Express Elixir](https://www.kir.pl/nasza-oferta/banki/rozliczenia/express-elixir).




For a PLN payout proposal, request the receiving account requirements, funding arrangement, supported recipient banks, applicable limits and evidence of the final outcome. For settlement of collections, separately compare currency, timing, deductions and reconciliation reports. A domestic PLN system description does not establish cross-border settlement or eligibility for a foreign merchant.

## The role of PayStar

PayStar provides information for comparing payment solutions and, where agreed, a technical layer for connecting and operating them. PayStar is not a bank or payment service provider and does not accept, hold or settle customer or business funds in its own name.

You select the payment provider and enter into a direct agreement with it. The provider processes payments and performs settlement under that agreement. Local eligibility, required authorisations and commercial terms must be confirmed for your company and use case. A method described in this article is not a promise that it is available through PayStar for your business.

Information about payment options is free. Payment processing and any agreed technical services have separate commercial terms.

## Official sources and research scope

- [BLIK recurring-payment introduction](https://www.blik.com/lp/reccuring-payments/Introduction.html)
- [BLIK Model A](https://www.blik.com/lp/reccuring-payments/Model_A.html)
- [BLIK Model M](https://www.blik.com/lp/reccuring-payments/Model_M.html)
- [BLIK Model O](https://www.blik.com/lp/reccuring-payments/Model_O.html)
- [KIR: Express Elixir](https://www.kir.pl/nasza-oferta/banki/rozliczenia/express-elixir)

Research check: 8 October 2026. The export date remains 14 September 2026. Local scheme descriptions are context, not confirmation of a particular provider’s capabilities.