How much does implementing BLIK payments in an app cost

The cost of BLIK payments in a mobile app consists of three separate things that get confused regularly in budget conversations: the one-off cost of integration, the commission on every transaction and the cost of maintenance. You pay the first to your team, the second to the payment operator, and the third you carry for the product's whole life — and over a few years it is usually the largest of the three.

Below we break each layer down into its components, with indicative ranges and worked examples.

The amounts and rates quoted are indicative market levels as at mid-2026. Operators' price lists change, and rates above a certain volume are negotiable — always confirm the specific terms in the current offer and contract.

1. The cost of integration — your team's work

This is a one-off cost, measured in days of work. The ranges below assume an app that already has a backend and an order model — if those are being built from scratch, the payment cost has to be counted together with them.

What that work consists of — because "BLIK integration" is not a single endpoint:

• Payment backend — initiating transactions, idempotency keys, handling the webhook with signature verification, the status model, refunds.
• Mobile layer — the method selection screen, the code field, the validity countdown, error screens, resumption after returning from the banking app.
• Panel and operations — a transaction overview, manual refunds, reconciliation against the operator's report.
• Testing — sandbox, production tests on small amounts, negative scenarios (rejection, insufficient funds, timeout, dropped network).
• Security — a review of the flow, securing the webhook, verifying that only the backend sets the amount.

The single biggest consumer of time is not the happy path but handling uncertain states: a transaction we do not know succeeded, because the webhook never arrived and the user closed the app. Teams that skip this save a few days on implementation and lose many times more on handling complaints.

2. Commissions — the cost of every transaction

The BLIK commission in Poland typically falls in the range of about 1–2% of transaction value, usually with no fixed fee or with a fee of a few grosz. For comparison, in the same calculation:

That last row matters most here. If your product qualifies for settlement through your own gateway, the difference between 1.5% and 30% is the difference between having a margin and not having one. If, on the other hand, you sell digital content consumed in the app, the stores require their own mechanisms and that difference cannot be "optimised" away — attempting to work around it ends in a rejected update. We describe exactly where the boundary runs in BLIK and the App Store and Google Play guidelines.

Beyond the headline commission, check the operator's price list for:

• the refund fee — with some providers a refund costs extra, and the commission already charged is not returned,
• a monthly or activation fee — sometimes zero, but not always,
• the payout cycle and threshold — D+1 versus weekly is a real liquidity difference,
• rates for non-EEA and commercial cards — usually higher,
• currency conversion costs when selling abroad.

3. Maintenance — the cost nobody remembers

Budget several to a dozen or so thousand zloty per year for maintaining the payment layer in a typical app:

• updates after changes to the operator's API and SDK,
• changes forced by App Store and Google Play guidelines,
• extending reporting and reconciliation,
• monitoring failed transactions and reacting to gateway outages,
• handling complaints and refunds on the team's side.

What it really costs — three scenarios

Assume a BLIK commission of 1.5% and compare the one-off cost with annual commissions.

The practical conclusion: at small scale optimise the cost of implementation, at large scale the commission. The point at which serious negotiation starts to pay usually arrives somewhere around a few hundred thousand zloty of monthly turnover.

What drives the cost of integration up

• No existing order backend — payments cannot sensibly be implemented without an order model, statuses and history.
• Many methods at once at launch — each method brings its own error states and its own testing.
• Subscriptions — renewals, failed charges, plan changes, proration, cancellations. That is a separate module, not "one more button".
• Marketplace — splitting funds, seller balances, payouts, tax reporting.
• Partial refunds and document corrections.
• Accounting requirements — integration with the finance system, numbering, daily reports.
• An app in a regulated sector — additional security requirements and audits; see mobile app for fintech.

How to reduce the cost sensibly

1. Start with one method. BLIK covers most mobile payments in Poland. Add cards and wallets in the next iteration.
2. Choose an operator with a good mobile SDK. A few days saved on integration usually outweighs the difference in commission at small scale.
3. Do not build your own panel at the start. The operator's panel is enough for the first months of handling refunds.
4. Negotiate on data. After a few months you have real volume and a real method mix — a stronger argument than a forecast.
5. Design reconciliation straight away. The hours later spent hunting discrepancies by hand cost more than building the report at the start.

Frequently asked questions

How much does the BLIK integration itself cost? For an app with an existing backend: indicatively PLN 12,000 – 25,000 net for a native six-digit code implementation, less with a simple redirect, more for a full checkout with several methods.

What is the BLIK commission? Usually around 1–2% of transaction value, depending on the operator, the industry and your volume. Above a certain turnover the rates are negotiable.

Is BLIK cheaper than a card? Usually yes, especially on low-value transactions, because there is more often no fixed fee. On larger baskets the percentage difference narrows.

Do you have to pay to maintain payments? Directly to the operator, usually not (beyond transaction fees), but on your team's side yes — updates, monitoring and refund handling are an ongoing cost.

How long does it take to go live with payments? The development work is usually several days to a couple of weeks, but the real deadline is set by merchant verification at the operator. It is worth starting that at the beginning of the project. We describe the implementation details in the article BLIK integration in a mobile app.

Summary

Implementing BLIK in a mobile app costs indicatively from a dozen to several tens of thousands of zloty one-off, around 1–2% of every transaction, and a small ongoing maintenance cost. At small scale the implementation cost decides; at large scale the negotiated commission does. The most expensive items, however, are two things absent from every price list: badly handled uncertain states and the lack of reconciliation.

At Mobilesoft we implement payments in mobile apps and help estimate the full cost — including commissions and maintenance, not just developer time. Get in touch and we will prepare a quote for your case.