Przelewy24, PayU and BLIK in Shopware 6: Localized Payments Done Right

Payment is one of the largest friction points in e-commerce - more than 70% of B2B carts are abandoned before purchase, and the wrong checkout is a big reason why. For the Polish market, "the wrong checkout" usually means missing BLIK, no pay-by-link bank transfers, or no installment option. This guide covers how to add Przelewy24, PayU, and BLIK to Shopware 6 the right way, so shoppers pay the way they expect and your orders stay reliable.

Why localized payments matter

Polish shoppers have strong payment habits: BLIK for fast mobile payments, online bank transfers (pay-by-link) for everything else, cards, and increasingly buy-now-pay-later installments for larger baskets. A checkout that only offers cards leaves conversions on the table. Offering the local methods is one of the highest-return changes you can make to a Polish store.

The methods your checkout should offer

Przelewy24 (P24)

• Online bank transfers (pay-by-link)
• BLIK
• Cards (Visa / Mastercard)
• Refunds from the Shopware admin

PayU

• BLIK
• Online bank transfers
• Cards
• PayU Raty (installments / buy-now-pay-later)
• Refunds from the admin

Both cover the essentials. PayU adds Raty installments out of the box; Przelewy24 is a very common default for Polish bank transfers and BLIK. Many stores run one as the primary provider; some offer both. We also integrate BLIK and Tpay where they fit your audience.

How the integration works

• Payment plugin over the provider REST API - Przelewy24 or PayU (PayU using OAuth), wired into the Shopware checkout.
• Signature generation and verification - every request and notification is signed and verified, so nothing can be tampered with.
• Webhook-driven, idempotent status updates - the provider notifies the shop when a payment succeeds or fails, and each notification can be processed safely even if it arrives more than once.
• Mapping to Shopware order and payment states - so paid, pending, and failed payments map cleanly to the right order status.
• Sandbox and production configuration - fully tested in sandbox before going live.

The pitfalls that matter most

• Double charges and duplicate orders - the number one risk. The fix is idempotent webhook handling: a retried notification must never create a second order or a second charge. We build this in by default.
• Stuck "pending" orders - when a webhook is missed, orders can hang. Reliable, verified webhook processing (with a fallback status check) keeps order states accurate.
• Refunds - merchants need to refund from the Shopware admin without logging into the provider panel. We wire refunds into the admin.
• BLIK timing - BLIK has its own confirmation flow; the checkout has to handle the short confirmation window cleanly.

Which provider should you choose?

If you mainly need BLIK, bank transfers, and cards for a Polish audience, Przelewy24 is a strong, conventional choice. If installments (PayU Raty) are important for your basket sizes, PayU covers that natively. The decision usually comes down to fees, your existing provider relationships, and whether you need BNPL - and there is no rule against offering more than one. We can help you pick based on your real order profile.

Ready to localize your Shopware checkout?

We tune Shopware checkout for the Polish market - reliable, webhook-driven payment status, idempotent handling so there are no double charges or duplicate orders, and full sandbox-to-production testing. See our Przelewy24 and PayU integration services, or contact us to discuss your project.