Which gateway is cheapest?

It depends on your agreement, volume and payment methods, so we do not copy fees. We compare features; you check prices in the operators' lists or the offer they make you.

Can I run two gateways at once?

Yes. We build a shared payment layer with a connector for each gateway, so an order looks the same whichever gateway took the payment.

Who signs with the gateway?

You do, as the merchant. We only need the keys for the test and production environments.

Does switching gateways mean rewriting the store?

Not if payments sit behind a shared layer. Then a switch is a new connector and tests.

Can I take Apple Pay and Google Pay?

Yes. Wallets run through the same gateways as BLIK and cards, usually after some extra domain or account setup. We check it for the chosen gateway and set it up before launch.

What if the customer closes the page right after paying?

Nothing is lost. Only a checked notification from the gateway or a query to the gateway changes the order status, never the customer coming back to the page.

Can a repeated notification ship goods twice?

No. Every gateway retries notifications, so we check and record each one in a way that a second copy never ships goods or activates a service twice.

How much does an integration cost?

Integrations are quoted individually, under our API and integrations service. The figure depends on how many systems we connect, which data flows where and what should happen on an error. We give it after a short call, and the quote is free and comes back within an hour.

Will the integration code be mine?

Yes. Once the work is accepted and paid in full, the economic copyright in the code passes to you and you get the repository with run instructions. Open source libraries keep their own licences.

Online payments: BLIK, PayU, Tpay, Paynow and Stripe

We help you pick a payment gateway for how you sell and integrate it in your store, app or platform. We compare features and integration style; you check fees in the operators' price lists.

Integrations

A store's payment settings: Przelewy24, Stripe and PayU as adapters of one payment layer, and shared order statuses

The gateways we integrate

Each has its own page with the payment flow and what we watch for when integrating it.

Przelewy24

The history of a paid order

BLIK by code and in a remembered store, payments for many sellers.

Przelewy24

PayU

Payments waiting to be captured

Saved cards, recurring BLIK, capture after a stock check.

PayU

Tpay

A payment split between sellers

BLIK on your page and in one click, payments for many sellers.

Tpay

Paynow

Two payment attempts for one order

Signed payments, BLIK and cards on your page.

Paynow

Stripe

A subscription after a failed renewal

Subscriptions, Connect, BLIK, customers abroad.

Stripe

BLIK

BLIK charges without the customer

Code, remembered store, recurring payments.

BLIK

Gateways compared from the integration side

The features that shape the integration. No fees, as those depend on your agreement with the operator.

	Przelewy24	PayU	Tpay	Paynow	Stripe
BLIK without a redirect	Yes	Yes	Yes	Yes	Yes
Notification protection	Yes	Yes	Yes	Yes	Yes
Recurring payments	Yes, with a condition	Yes, with a condition	Yes	Yes, with a condition	Yes
Multiple sellers	Yes, with a condition	Yes, with a condition	Yes, with a condition	Yes, with a condition	Yes, with a condition
Test environment	Yes, with a condition	Yes	Yes	Yes	Yes

Recurring payments (Przelewy24): a separate service
Recurring payments (PayU): cards and BLIK, BLIK after an annex
Recurring payments (Tpay): recurring BLIK
Recurring payments (Paynow): per agreement
Recurring payments (Stripe): Stripe Billing and BLIK mandates
Multiple sellers (Przelewy24): Marketplace service
Multiple sellers (PayU): Marketplace service
Multiple sellers (Tpay): marketplace within the Partner Programme
Multiple sellers (Paynow): a marketplace solution
Multiple sellers (Stripe): Connect
Test environment (Przelewy24): once the live account is open

YesYes, with a conditionNo

Which services your account gets depends on your agreement with the operator, so we confirm it before quoting. The next section shows each gateway's mechanism.

The pattern every gateway shares

Details differ, but every sound integration goes through the same stages.

Each gateway says "paid" its own way

Przelewy24the transaction confirmed in Przelewy24a checksum and transaction confirmation
PayUthe COMPLETED statusa signature checked with the second key
Tpaythe paid notificationTpay's digital signature
Paynowthe CONFIRMED statusa signature with a secret key
Stripea paid invoicea signature checked with a key from the Stripe dashboard

One payment layer

connector: Przelewy24, PayU, Tpay, Paynow, Stripe

Check

the signature
the amount
the currency
the order id

No repeats: a second identical notification does not change the result.

Order status

Paid

fulfilment and a sales document

Mismatch or rejected

stop and a message

Orders matched with the gateways

With a shared layer you get one place for the payment statuses of every gateway. This is the report of a store that takes payments through two gateways.

A store's payments report for 1-8 October 2026: paid orders a day from Przelewy24 and Stripe, the match with the gateways and the payment methods

Two gateways in one report
The store takes payments through Przelewy24 and the monthly plan through Stripe. The report counts them together, because an order has the same statuses whatever the gateway.
Orders matched with confirmations
Every paid order has its confirmation on the gateway's side: a confirmed transaction in Przelewy24 or a paid invoice in Stripe. A mismatch holds the order until it is explained.
Payment methods
BLIK, transfer and card go through the store's gateway. Apple Pay and Google Pay run through the same gateways, usually after some extra domain or account setup.

How we match a gateway

The questions we start the conversation with. The answers usually narrow the choice by themselves.

A ready platform or your own code?
One seller or many?
One-off or by subscription?
Customers in Poland or abroad too?

A ready platform or your own code?

a platformThe gateway's pluginE-commerce platforms
own code
One seller or many?
- manyA marketplace or ConnectWeb Platforms
- one
  One-off or by subscription?
  - one-off
    Customers in Poland or abroad too?
    in PolandA Polish gateway with BLIKBLIK
    abroad tooOther countries' currencies and methodsStripe
  - subscriptionRecurring paymentsStripe
  - both
    Two gateways, one layer

a platformThe gateway's pluginE-commerce platforms
own code
- manyA marketplace or ConnectWeb Platforms
- one
  - one-off
    in PolandA Polish gateway with BLIKBLIK
    abroad tooOther countries' currencies and methodsStripe
  - subscriptionRecurring paymentsStripe
  - both
    Two gateways, one layer

Common questions about online payments

Answers about fees, two gateways at once, wallets, notifications and switching gateways.

VulCode Support

Online

Click a question on the left to start a conversation

Not sure which gateway to pick?

Tell us what you sell, to whom and how often. We will reply within an hour with a gateway suggestion and a quote.

Online payments: BLIK, PayU, Tpay, Paynow and Stripe

The gateways we integrate

Przelewy24

PayU

Tpay

Paynow

Stripe

BLIK

Gateways compared from the integration side

The pattern every gateway shares

Orders matched with the gateways

Two gateways in one report

Orders matched with confirmations

Payment methods

How we match a gateway

A ready platform or your own code?

One seller or many?

One-off or by subscription?

Customers in Poland or abroad too?

Common questions about online payments

Read next

Not sure which gateway to pick?