BLIK payment

BLIK payment for Polish traffic — a 6-digit code, one API.

topropay surfaces BLIK — Poland's instant-payment method — as a first-class method inside the same unified API as cards, wallets, SEPA and BNPL. The buyer generates a 6-digit code in their bank app and confirms the payment inside it; the merchant gets a normalised webhook back in seconds.

Book a BLIK integration review Read the API docs
topropay.com/checkout/ · BLIK

189,00 zł

Enter the 6-digit BLIK code from your bank app

Code valid · 1:42 remaining

Routed through topropay · bank-side SCA

Instant
real-time BLIK settlement
PLN
Polish domestic rail
6-digit
one-time code from the bank app
1 API
with card, wallet, BNPL

Key benefits

Why orchestrated blik payment integration wins on Polish traffic

Four outcomes that show up consistently once BLIK sits next to card and wallet on the same orchestration layer rather than in a separate Polish console.

  1. 01

    BLIK is the rail Polish buyers expect

    BLIK powers a sizable share of Polish e-commerce checkouts — the 6-digit one-time code is a familiar pattern, generated inside the buyer's bank app (PKO BP, Pekao, mBank, ING, Santander, Millennium and others). Surfacing BLIK alongside cards on a Polish checkout lifts conversion measurably vs a card-only form.

  2. 02

    One API across BLIK, cards and the rest of the method matrix

    BLIK, cards, SEPA, Apple Pay / Google Pay, BNPL and (via partner gateways) crypto all live behind the same unified REST API. The merchant doesn't pick a different SDK per method — the same authorise endpoint, the same webhook stream, the same vault model.

  3. 03

    Real-time confirmation, lower landed cost than card

    BLIK clears in real time and carries a flat per-transaction fee that's typically lower than card interchange for the same PLN amount. For high-volume Polish merchants, surfacing BLIK alongside card is a meaningful landed-cost lever.

  4. 04

    One reconciliation feed for PLN traffic

    BLIK receipts, card settlements, wallet captures and bank-rail debits roll into one ledger keyed off vault tokens. Finance closes the month from one export rather than a CSV-per-method merge — PLN traffic shows up alongside EUR / GBP traffic from the rest of the merchant's markets.

How it works

From BLIK code to a normalised ledger row in five stages

What happens between the buyer generating the 6-digit code and the row settling into the reconciliation export. Five concrete stages, most of them measured in seconds.

  1. 01

    Buyer picks BLIK at checkout

    On the merchant's checkout the buyer selects BLIK as the payment method. topropay's hosted page or embedded SDK renders the BLIK code input — a 6-digit one-time code field.

  2. 02

    Buyer fetches the 6-digit code from their bank app

    The buyer opens their Polish bank app (PKO BP, Pekao, mBank, ING, Santander and so on), taps the BLIK button, and the bank app generates a 6-digit code valid for around two minutes.

  3. 03

    Buyer enters the code, bank confirms in the app

    The buyer types the 6-digit code into the merchant's BLIK input. The bank app shows the merchant and amount; the buyer confirms (often with biometric authentication). The connected provider relays the bank's authorisation back to topropay.

  4. 04

    topropay fires a normalised webhook

    Same shape as a card authorised event — authorised / declined / failed — with BLIK-specific metadata (bank ID, end-to-end reference) on the row. The merchant's webhook handler treats it like any other authorisation.

  5. 05

    Reconcile alongside PLN card traffic

    BLIK receipts settle to the merchant's PLN settlement account on a configurable cycle. The reconciliation feed shows BLIK rows next to PLN card rows under one method-tagged ledger.

Main use cases

Where blik payment earns its keep

Six merchant shapes that route PLN traffic through BLIK inside the same orchestration as card and wallet — same platform, different policy mix.

  • DTC PL

    Polish DTC brands and e-commerce

    Polish DTC merchants surface BLIK as a top-of-list method for PLN traffic — typically as the default behind cards. The 6-digit BLIK flow is faster than a card form for the buyer and lower-cost for the merchant.

  • Cross-border

    Cross-border merchants selling into Poland

    An EU, UK or global merchant selling into Poland enables BLIK via the same payment-gateway integration that already powers cards, BNPL and SEPA. No second integration, no second reconciliation pipeline.

  • SaaS

    Subscriptions with BLIK first-charge

    BLIK captures the first charge for a Polish subscriber; card-on-file (or BLIK-recurring where the connected provider supports it) handles renewals. Both run through the same recurring engine, with vault tokens identifying the customer.

  • Travel

    Travel and ticketing for Polish buyers

    High-ticket bookings benefit from BLIK's real-time clearance — the seat or room is held the moment the bank confirms, not pending a card-clearing window. Refund flows are merchant-initiated via the same API.

  • Marketplace

    Marketplaces with Polish buyers

    Per-seller payouts in EUR / PLN, BLIK on the buyer side for PLN transactions, cards elsewhere. Split-payment routing preserves the per-seller ledger across rails.

  • B2B

    B2B invoicing into Polish counterparties

    Invoices to Polish B2B counterparties paid via BLIK clear in real time. The invoice and the BLIK receipt share one record in the reconciliation feed.

Platform features

Capabilities behind the blik payment system integration

What the platform actually ships for BLIK — beyond the general orchestration features shared with card and other methods.

  • Unified BLIK payment integration

    One REST API call surfaces BLIK as a method alongside card, wallet, SEPA and BNPL — same authorise endpoint, same webhook stream.

  • 6-digit code input

    Hosted page or embedded field for the BLIK 6-digit code; matched to the buyer's bank-app session by the connected provider.

  • Bank-side authentication

    Strong customer authentication happens in the buyer's bank app — biometric or PIN, depending on the bank — outside the merchant's checkout.

  • Refund API

    Merchant-initiated refunds via the same /v1/payments/:id/refund endpoint as card; BLIK refunds clear back to the originating bank account in real time.

  • Webhook event model

    Signed, replay-safe webhook events — authorised / failed / refunded — with BLIK-specific metadata (bank ID, end-to-end reference).

  • Operator portal

    BLIK authorisations, refunds and reconciliation in the same dashboard as the merchant's card traffic, with a BLIK-specific column set.

  • Settlement currency policy

    BLIK settles in PLN by default; non-PLN merchants can configure conversion-on-receipt to their settlement currency.

  • BLIK-recurring (where supported)

    Where the connected provider exposes recurring-BLIK, the platform surfaces it through the recurring-payment engine alongside card recurring.

  • Audit log

    Operator actions, refund events and reconciliation exports logged with timestamp and actor identity.

  • Sandbox parity

    Sandbox tenant supports the full BLIK flow — code generation, simulated bank confirmation, webhook replay, refund testing.

  • Multi-method routing

    BLIK sits next to cards on the same checkout; the routing engine handles card-side cascade while BLIK runs single-rail per its bank-side flow.

  • Polish bank coverage

    Coverage across the major Polish issuing banks — PKO BP, Pekao, mBank, ING, Santander, Millennium, Alior and others — through the connected provider.

Trust & compliance

Compliance posture for blik payment processing

BLIK is delivered through a licensed Polish connection; the rest of the posture is inherited from the platform's audited environment.

BLIK via licensed connectivity
BLIK is delivered through a connected provider with the relevant Polish payment-institution licensing; topropay routes and reconciles around it.
PCI DSS Level 1 (card side)
PCI DSS Level 1 posture covers the card traffic that BLIK sits next to; BLIK itself does not touch card data.
SCA via the bank app
Strong customer authentication for BLIK happens inside the buyer's bank app — outside the merchant's surface — so the merchant inherits the bank-side SCA posture.
AML & sanctions screening
Sanctions screening on onboarding; AML monitoring tuned per merchant vertical and Polish-specific risk patterns.
Data residency for PL
Polish-resident traffic stays in-region by default where the merchant requires it; GDPR-aligned handling for the BLIK side.
Licensed verticals only
Licensed gaming, regulated financial services and other compliance-bound verticals supported only where current operating licences exist. Grey and black-market verticals are out of scope regardless of rail.

Ready to switch on BLIK

BLIK next to card on the same checkout, same API.

A 30-minute BLIK review covers the connected provider, settlement-currency policy for non-PLN merchants, the BLIK code surface, and a sandbox to test against before any commercial commitment.

Book a BLIK integration review Read the API docs

Frequently asked

Buyer questions about blik payment on topropay

Questions buyers ask before committing — what BLIK is, how the integration looks, UK / Deutschland acceptance shapes, recurring billing, refunds and sandbox parity.

  1. 01

    What is BLIK and how does it work?

    BLIK is Poland's domestic instant-payment method. The buyer generates a 6-digit one-time code inside their Polish bank app (PKO BP, Pekao, mBank, ING, Santander, Millennium, Alior and others), enters it on the merchant's BLIK input, and confirms the payment inside the bank app. The transaction clears in real time. From a merchant perspective BLIK is one of the highest-converting non-card rails on Polish checkouts.

  2. 02

    What's the typical blik payment method flow from the buyer's perspective?

    The buyer picks BLIK on the merchant's checkout, opens their bank app, taps the BLIK button to generate a 6-digit code, types the code into the checkout, confirms the amount and merchant inside the bank app (often with biometric authentication), and the merchant gets a webhook confirmation back inside seconds. No card form, no 3DS step-up, no overnight clearing.

  3. 03

    What does blik payment app refer to?

    Blik payment app refers to the bank app where the buyer generates the BLIK code — any of the participating Polish banks (PKO BP IKO, Pekao PeoPay, mBank, ING Moje ING, Santander mobile, Millennium, Alior, BNP Paribas GOmobile, Credit Agricole and others). topropay does not require the merchant to install a separate BLIK app; BLIK is exposed as a method inside the unified payments API.

  4. 04

    Is blik payment system Polish-only, or does it work in other markets?

    BLIK is primarily a Polish domestic rail — the BLIK system clears on PSP infrastructure inside Polish banking. There are initiatives to extend BLIK acceptance into other European markets through bank-app integration partnerships, but the dominant use case remains Polish buyers paying Polish merchants (and Polish buyers paying foreign merchants who've enabled BLIK).

  5. 05

    Does blik payment uk acceptance exist for UK merchants?

    BLIK payment uk acceptance is the pattern where a UK-domiciled merchant accepts BLIK from Polish buyers visiting the UK checkout. topropay supports that flow — the UK merchant integrates BLIK as one method on the unified API; the buyer scans / enters the BLIK code from their Polish bank app; settlement converts on receipt to the merchant's GBP settlement account. The underlying BLIK rails are still Polish.

  6. 06

    What about blik payment deutschland — does the German market accept BLIK?

    Blik payment deutschland follows the same cross-border pattern — German-domiciled merchants accept BLIK from Polish buyers visiting their checkout. Direct German-domestic BLIK adoption (German banks generating BLIK codes) is limited and depends on individual bank participation; topropay handles whatever the connected provider exposes. For pan-EU traffic the standard pattern is still: BLIK for PL buyers, SEPA / cards / iDEAL for buyers from other EU markets.

  7. 07

    Is there a blik payment system specific to recurring billing?

    A blik payment system shape for recurring uses one of two patterns: BLIK first-charge with card-on-file for renewals (most common), or BLIK-recurring where the connected provider exposes it (less common but growing). The merchant doesn't need to choose up front — both run through topropay's recurring-payment engine with one API.

  8. 08

    How are BLIK refunds handled?

    BLIK refunds are merchant-initiated via the same refund endpoint as card. The connected provider initiates a return BLIK to the originating bank account on Polish bank rails — the refund clears in real time. Partial refunds are supported. Refund operations log the operator identity, reason code and end-to-end reference for audit.

  9. 09

    What's the typical BLIK fee?

    BLIK carries a per-transaction fee from the underlying provider, plus topropay's per-authorisation platform fee — both pass through transparently on the invoice. The combined cost is meaningfully lower than card for the same PLN amount, especially on smaller tickets.

  10. 10

    How does BLIK compare to card on a Polish checkout?

    BLIK and card sit next to each other on a Polish checkout. BLIK typically wins on conversion (the bank-app flow is faster than a card form) and on landed cost (flat per-transaction fee vs percentage-based card interchange). Card still has roles to play — saved-card recurring, international cards from buyers visiting a Polish checkout, premium / commercial cards where the interchange story differs.

  11. 11

    Are there chargebacks on BLIK?

    BLIK clears in real time and does not carry a card-style chargeback window. The buyer authorised the transfer inside their bank app (typically with biometric authentication), so unilateral dispute initiation by the buyer doesn't apply in the same way card does. Refunds are merchant-initiated. Fraud and AML concerns still apply, with the bank-side authentication and topropay's sanctions screening as the primary defences.

  12. 12

    What if the BLIK code expires before the buyer types it in?

    BLIK codes are valid for roughly two minutes. If the buyer doesn't enter the code in time, the checkout shows an expiry message and the buyer generates a new code from the bank app. topropay's hosted checkout handles this gracefully — no merchant-side code change required.

  13. 13

    Does the platform support BLIK-Mobile / proximity payments?

    BLIK on the platform covers the standard 6-digit code flow for e-commerce. BLIK-Mobile / NFC-style proximity flows (for in-store POS) depend on the connected provider's coverage; where supported, they surface through the same authorisation engine with a different entry mode.

  14. 14

    What does the sandbox cover for BLIK testing?

    The sandbox supports the full BLIK flow: code generation, simulated bank-confirmation outcomes (success, expired, declined, failed), webhook replay, refund-flow testing. The error model is identical to production; merchants build the full integration against the sandbox before any commercial commitment.

  15. 15

    How does the platform handle non-PLN merchants accepting BLIK?

    Non-PLN merchants accept BLIK through topropay's connected provider; the underlying Polish rails clear in PLN, and the platform converts on receipt to the merchant's settlement currency at the rail's quote. Settlement currency is a policy choice — hold PLN, or convert on receipt to EUR / GBP / USD.

Related

Related on the topropay platform