Accepting BLIK in Poland

BLIK is Poland’s domestic mobile payment scheme, used through the consumer’s own banking app and confirmed with a six-digit code. It has become a default expectation in Polish checkouts, and any merchant selling into Poland without it is competing on inconvenience.

Set-up

How to accept BLIK as a merchant

You do not contract with BLIK. Acceptance runs through a Polish acquirer or a PSP connected to the scheme. The customer generates a code in their banking app, enters it at checkout and confirms in the app. It is account-based rather than card-based, and it settles in real time.

BLIK against Przelewy24 and cards

Poland is a genuinely mixed market. BLIK competes with aggregated bank transfer through providers such as Przelewy24 and with cards, and the mix varies by demographic and basket value. Offering all three without measuring which converts and what each costs is common and expensive. The interaction between your average order value and each method’s fee structure is what determines whether Poland is efficient for you.

Authentication

The six-digit code is strong customer authentication, and that is worth a number

The BLIK flow looks like a convenience feature. In law it is the authentication step itself, which is why nothing else has to be bolted on around it.

Article 97(1) of Directive (EU) 2015/2366 requires a payment service provider to apply strong customer authentication where the payer accesses its payment account online, initiates an electronic payment transaction, or carries out any action through a remote channel which may imply a risk of payment fraud or other abuses. For remote payments, Article 5(1) of Delegated Regulation (EU) 2018/389 adds dynamic linking: the payer is made aware of the amount of the payment transaction and of the payee, the authentication code generated is specific to the amount and the payee agreed to by the payer when initiating the transaction, the code accepted corresponds to that original amount and to the identity of the payee agreed to by the payer, and any change to the amount or the payee results in the invalidation of the authentication code generated.

Read the BLIK flow against that list and it matches item by item, inside the customer’s own banking app, in a single confirmation. There is no second authentication layer to configure, no exemption policy to run and no soft decline to recover, because the rail does not have those failure modes. So the comparison against cards is not only a fee comparison. Put it in euros: on 4 million euros of Polish card revenue, an authentication step that costs two percentage points of completion is 80,000 euros of orders that never arrive. That number appears on no invoice, which is precisely why it gets left out of the method comparison.

EuroPA

BLIK has joined the EuroPA alliance

BLIK has joined EuroPA, the alliance founded by Bancomat, Bizum and MB WAY through SIBS, whose members now exceed 100 million users across ten European countries. Interoperability between the three founding solutions has been live since March 2025, and the alliance signed a Memorandum of Understanding with EPI Company on 2 February 2026 to build a central interoperability hub, targeting cross-border person-to-person payments in 2026 and e-commerce and point-of-sale payments in 2027. For a merchant this is the direction to watch: domestic schemes are becoming cross-border without merchants having to integrate each one separately.

Which payment provider supports BLIK for merchants in Poland?

PayU, Autopay and tpay in Poland, alongside Global Payments, all document BLIK, among others, as do most gateways serving central Europe. The useful questions are what BLIK costs you per transaction against Przelewy24 and cards on your actual basket distribution, whether the line is visible separately on your statement, and which method your Polish customers pick when all are offered.

Mix

Three methods, one Polish checkout, and the two numbers nobody has

A Polish checkout carrying BLIK, aggregated bank transfer and cards is correctly built. What is usually missing is the pair of numbers that tells you what that mix is doing to you.

Those numbers are cost per method and completion per method, on your own traffic, over the same period. Neither is difficult and both are usually absent, because the payments report groups by provider, the analytics report groups by session, and nobody owns the join. Until that join exists, every argument about the Polish mix is an argument about opinions.

Make it concrete. On 5 million euros of Polish revenue, suppose BLIK carries 45 per cent, bank transfer 35 per cent and cards 20 per cent, at effective rates of 0.9, 1.1 and 1.5 per cent. That is 20,250 plus 19,250 plus 15,000, so 54,500 euros. Move ten points of volume from cards to BLIK by putting BLIK first and preselected, and 500,000 euros crosses from 1.5 to 0.9 per cent, saving 3,000 euros. Now assume BLIK also completes two points better than cards on that volume: another 10,000 euros of revenue that used to disappear. The order of three logos is worth more than the rate conversation most merchants have instead of it, and unlike the rate conversation you can run it this week.

Reviewing your Polish payment costs

What you pay is set in your agreement, not by the scheme. Start by establishing whether you are overpaying your PSP, or move straight to cutting your PSP costs, because a cheap method priced badly still costs more than it should.

Relevant markets: Poland