Online banking is highly popular in Poland, and Przelewy24 makes it even more convenient.

Przelewy24, often known as P24, collaborates with over 165 banks, simplifying the payment process. Shoppers choose their issuing bank and complete payments on the bank’s platform, without the need for manual transfer details, which speeds up the process.

Merchants can quickly get started without the need for a separate P24 account.

How to use Przelewy24

The process unfolds as follows:

1. The customer initiates the payment process by selecting P24 as their preferred payment method at the merchant’s checkout page.
2. Following that, they are guided to the dedicated P24 payment page, where they can select their bank.
3. From there, they are redirected to their respective bank’s online banking portal.
4. To validate the transaction, the customer securely logs in to their online banking account.
5. After confirmation, they are swiftly returned to the merchant’s website for payment confirmation.

How it works

Below, please review the essential steps required to integrate the Przelewy24 payment method.

Step 1: Create the Order

Step 2: Get the Payment Link

Step 3: Get the Payment Status

Step 1: Create the Order

Make sure to create the order request with Przelewy24 (“PY24”) as the chosen payment method  (transaction.paymentMethod) and set the customer language preference in customerInfo.customerLanguage.

Step 2: Get the Payment Link

Proceed to obtain the payment link, outlined below, to redirect the customer to a secure payment page for authentication and payment authorization.

Please be aware that the request below requires an Authorization Header containing the transactionSignature obtained on the previous step.

Endpoints:

Ensure that you include these essential elements as specified:

Header parameters:

Request parameters:

Here’s an example of how to obtain the payment link:

{
 "userAcceptanceIndicator": true,
 "gatewayId": "giropay",
 "info": {
 "deviceInfo": {
 "browserAcceptHeader": "application/json, text/plain, */*",
 "browserJavaEnabled": "false",
 "browserLanguage": "en",
 "browserColorDepth": "24",
 "browserScreenHeight": "1080",
 "browserScreenWidth": "1920",
 "browserTZ": "-60",
 "browserUserAgent": "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36",
 "geoLocalization": "Lat: 38.7350528 | Long: -9.2143616",
 "systemFamily": "Windows",
 "systemVersion": "Windows",
 "deviceID": "498bfd4c3a3645b38667a7037b616c18",
 "applicationName": "Chrome",
 "applicationVersion": "106"
 },
 "customerInfo": [
 {
 "key": "customerName",
 "value": "Test Name"
 },
 {
 "key": "customerEmail",
 "value": "email@provider.com"
 }
 ],
 "accountInfo": {
 "holderName": "Test Name",
 "customerCountry": "DE"
 }
 },
 "merchant": {
 "merchantURL": "https://egadget2.azurewebsites.net/#/returns?id={{transactionId}}"
 }
}

After successfully completing the operation, a ‘pending’ paymentStatus is received.

The user is then redirected to a payment confirmation environment before being seamlessly returned to the merchant’s URL.

Step 3: Get the Payment Status

You can perform a “Get Status” operation to check the status at any time.

The Authorization HTTP header is set to the Bearer token as it was used in the initial Checkout.

GET {transactionID}/status

Request URL:

https://stargate-cer.qly.site1.sibs.pt/api/v1/payments/{transactionID}/status

Request Headers:

Authorization: ‘Bearer <AuthToken>’
X-IBM-Client-Id: ‘<ClientId>’
Content-Type: application/json

A successful technical response comprises of an HTTP-200 status and a returnStatus.statusCode=”000″.

Here are some examples of the possible result codes: