BLIK, Przelewy24, Stripe or Apple Pay — which payment method to implement in your app

The question "which payment method should we implement" usually comes up once the app has already been designed and the budget calculated. That is a bad moment, because the choice of payment methods affects three things at once: conversion, margin and schedule. A poor decision does not announce itself with an outage — it shows up as abandoned carts and a commission you pay every month for years.

This text is a decision guide. It does not describe each provider in turn; it shows how to choose and in what order to implement — based on what you sell, to whom and at what scale.

If you are looking for a broader discussion of individual providers and store rules, start with the article on payments in a Polish mobile app: BLIK, Przelewy24, Stripe and Apple Pay. Here we focus on the decision itself.

Step zero: check whether you have a choice at all

Before comparing commissions, answer one question: are you selling digital content consumed in the app, or goods and services from the real world?

• Digital content in the app (a premium feature subscription, in-game currency, unlocking content) — the stores require their own purchase mechanisms. In that case the choice between BLIK and Przelewy24 is moot, because the payment is handled by the App Store or Google Play.
• The real world (food, a delivery, a ticket, an appointment, an in-person course, a service performed outside the app) — you settle through your own gateway, and then this whole article applies to you.

That boundary can be non-obvious, and it is where app releases most often fail. We break it down in detail in BLIK and the App Store and Google Play guidelines.

Methods versus providers — do not confuse two different things

The most common misunderstanding in payment discussions: putting concepts from two different levels side by side.

• Payment method — BLIK, card, bank transfer, Apple Pay, Google Pay, deferred payment.
• Provider (operator, gateway) — Przelewy24, PayU, Autopay, Tpay, Stripe. It is the provider that exposes the methods, settles the money and offers the API.

Apple Pay and Google Pay are not competitors to Przelewy24 — they are methods that Przelewy24 or Stripe make available to you. Enabling them is usually a matter of configuration plus handling the native button in the app, not a separate settlement integration. The same goes for BLIK: it is a method you get from an operator.

So the real choice looks like this: first one provider, then the set of methods enabled with them.

The criteria that actually decide

1. The market you sell in

Poland only — a Polish aggregator (Przelewy24, PayU, Autopay, Tpay) will have the full set of local methods and Polish-language support. Selling abroad or planning expansion — Stripe, with BLIK as one method for Polish customers.

2. The sales model

One-off purchase, subscription, marketplace splitting money between sellers, deferred payment. Multi-party models (marketplace, split payment) narrow the list of providers considerably and raise the cost of implementation.

3. The commission at your volume

Rates are negotiable above a certain turnover. At small scale the list price is what counts; at large scale the negotiated one. Indicative market levels in Poland:

These are market ranges, not an offer — always confirm specific rates in the current price list and contract, because they differ between providers and change over time.

4. Time and cost of implementation

The differences are large and rarely reflected in schedules:

On top of that comes something outside the developers' control: merchant verification at the operator (company KYC, a description of the business, sometimes financial documents). Usually several days to a couple of weeks, and longer for an unusual industry. It is worth starting it at the beginning of the project, not a week before launch.

5. Conversion

In Poland BLIK is the first-choice method in the mobile channel — its absence genuinely costs sales. Apple Pay and Google Pay shorten the checkout to a single gesture and make the most sense for impulse purchases. A card with a manually typed number is a fallback path today, not the main one.

6. Operating cost after launch

Refunds, complaints, reconciliation with accounting, handling failed subscription renewals, monitoring gateway outages. This is work that continues throughout the product's life and that nobody prices at the start.

The decision matrix

An implementation order that works

Do not implement everything at once. The sequence that delivers the most value earliest:

1. BLIK — the largest share of mobile payments in Poland and the simplest integration with a Polish operator.
2. Cards — coverage for customers without BLIK and for foreign payments.
3. Apple Pay and Google Pay — cheap to add, a clear conversion improvement.
4. One-click / recurring payments — once you have returning customers.
5. BNPL and niche methods — only when the data shows their absence is blocking sales.

What the price list does not show

• Refund fees — with some operators a refund costs extra, and the transaction commission is not returned.
• Payout cycle — D+1 versus weekly is a real difference in cash flow.
• Currency conversion fees when selling abroad.
• The cost of maintaining the integration — changes in providers' APIs and terms force updates.
• The cost of an outage — a contingency plan for gateway downtime (a second method, a message, queued orders).

Frequently asked questions

BLIK or Przelewy24 — which to choose? It is not an either/or. Przelewy24 is a payment operator; BLIK is a method that operator makes available. You choose the operator and enable BLIK with them.

Do I need two operators at once? Usually not at the start. A second provider makes sense as a backup at high volume, or when you enter a foreign market that your local aggregator does not cover.

Does Stripe support BLIK? Yes, BLIK is one of the methods available in Stripe for Polish customers. Confirm current availability and rates in the provider's price list.

How much does implementing payments in an app cost? We break the scope and ranges down in detail in how much BLIK payment integration costs, and the cost of a whole app in how much a mobile app costs in 2026.

Summary

Choosing payments for a mobile app comes down to three decisions in order: what you sell (which settles whether the stores impose their own mechanism), which market (which settles the provider) and at what scale (which settles the commission). For a Polish app selling the real world the answer is usually simple: one Polish operator, BLIK as the default method, cards and wallets alongside — and everything else added when the data justifies it.

At Mobilesoft we select and implement payments in mobile apps — from the first integration through to one-click and subscriptions. Write to us and we will help choose a set of methods that fits your sales model and estimate the cost of implementation.