Who PayU is for
PayU GPO is a gateway many Polish merchants already have under contract for their retail store. In wholesale its role is usually narrower: it serves new customers with no credit limit yet, prepaid orders, small top-up purchases and a B2C channel if you run one on the same platform. Large orders from regular customers mostly go through bank transfer on payment terms or against a credit limit anyway. The platform includes those payment options as standard, with or without a gateway.
The PayU module is a paid module, like the other online payment gateways. The open-source core contains the payments layer plus bank transfer, cash on pickup and credit limit.
Payment methods and two checkout variants
The integration supports:
- BLIK, including BLIK One Click for returning buyers,
- cards through the PayU Secure Form, with the option to save a card,
- Apple Pay and Google Pay,
- pay-by-link, an instant transfer from the buyer’s own bank.
You set the checkout up in one of two ways. In the redirect variant the buyer places the order, moves to the PayU page and picks a method there. In the embedded variant the payment form is part of your own checkout. The card field is then the PayU Secure Form: a form hosted by PayU and embedded in a frame, so card details go straight to the provider and only a token comes back to the platform.
From placing the order to the “paid” status
- The buyer places the order and selects PayU. The platform creates the order on the provider’s side.
- The buyer authorises the payment: on the PayU page or in the form on your checkout.
- PayU sends a notification with the result. The module checks the signature from the OpenPayu-Signature header and changes the order status only once it is confirmed.
- The platform emits a payment settled or payment failed event, which you can pass on, for example as a webhook to your ERP.
The signature matters in practice: the notification address is public, so without verification anyone could mark an order as paid. PayU expects an HTTP 200 response and resends the notification when it does not get one, so the same notification can arrive more than once. The details are in the PayU payment lifecycle documentation.
Saved cards and BLIK One Click
Returning buyers do not re-enter payment details. For cards this relies on PayU tokens: after the first successful payment the provider issues a multi-use token, and the platform stores the token, not the card number.
BLIK One Click lets the buyer pay without copying a BLIK code from the banking app on every order. PayU does not offer this service by default: it requires meeting the provider’s conditions and going through an onboarding process with your account manager. Plan for it in the schedule, because this step does not depend on the platform.
Refunds tied to the return
A refund is not a separate operation in the gateway’s panel. It starts in the returns module: when you settle a return case with a money refund, the platform orders the refund in PayU for the payment that paid for the order. The refund and the return of goods therefore share one record.
- The amount for a line defaults to the amount paid for the returned quantity and cannot exceed it.
- PayU allows several partial refunds for one order, as long as their total does not exceed the order value. This suits returns settled line by line.
- If the PayU module is switched off, settling a return with a refund is rejected until the module is switched back on. The case does not change status in the meantime.
What to prepare on the PayU side
| Item | Why |
|---|---|
| A business account and a shop in PayU | A shop in the PayU panel has its own currency and balance, which is worth planning for when you sell in several currencies |
| A REST API point of sale (POS) | PayU generates the keys for it that the platform uses to authorise requests |
| The second key of the POS | Used to verify the signature of notifications |
| A sandbox account | PayU’s public test POS is enough for the redirect alone, while for testing refunds the provider recommends your own sandbox account |
| BLIK services configured by PayU | BLIK variants other than the redirect to the payment page require a special configuration of the POS by the provider |
You enter the keys in the admin panel. Secret fields are encrypted at rest and cannot be read back through the API. Environments and test data are listed in the PayU testing documentation.
PayU and the other gateways
You pay PayU’s own processing rate. Endora does not add an intermediary surcharge on top, the same as with Stripe and tpay.
The choice between PayU and tpay usually comes down to which one you already have a contract with and what terms you negotiated, since both cover the methods a Polish buyer expects. Stripe makes more sense when most payments are cards from customers abroad. If you sell only on invoice with payment terms, you may not need an online gateway at all: bank transfer, credit limit and KSeF invoices are enough. The full list is in the integrations catalogue.