Skip to main content
Przelewy24 (P24) is an online payment method in Poland. Customers choose their bank on the Przelewy24 page and confirm the payment in their own online banking. Payrails processes Przelewy24 through two payment service providers (PSPs). The flow is the same with each one, but the required request fields and the supported workflows differ. Pick a PSP below for its setup steps and request examples.

​
How a Przelewy24 payment works

Przelewy24 is a bank redirect payment method:
  1. The customer selects Przelewy24 at checkout.
  2. Payrails returns a redirect URL from the PSP, and the customer goes to the Przelewy24 page.
  3. The customer chooses their bank and confirms the payment.
  4. The customer returns to your returnInfo URL.
  5. Payrails receives the final result from the PSP and updates the payment.
Each payment is single-use: the customer confirms every payment on its own. Payrails captures Przelewy24 payments immediately, so a successful payment is final. To return funds, refund the payment. Refunds work with Checkout.com only.

​
Supported currencies and countries

Przelewy24 supports PLN (Polish złoty) with both PSPs. Checkout.com also supports EUR (euro).

​
Integrate Przelewy24

Choose the PSP that processes Przelewy24 for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

Checkout.com

Przelewy24 via Checkout.com

Worldpay

Przelewy24 via Worldpay

​
Compare PSPs

Save Instruments and merchant-initiated transactions (MIT) aren’t available for Przelewy24 with either PSP.

​
Ways to integrate Przelewy24

  • Payrails SDK: the Web SDK shows Przelewy24 when your workflow returns it as a payment option, and redirects the customer to the Przelewy24 page. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with przelewy24 as the paymentMethodCode. Each PSP guide lists the meta fields that PSP requires.
In both cases, confirm the final result through webhook notifications or the execution status. Don’t treat the customer’s return to your success URL as proof of payment.
Last modified on October 2, 2026