RWDESIGN / TECHNICAL DOCUMENTATION

Przelewy24 PrestaShop

A practical guide from installation and safe testing through production configuration, maintenance and troubleshooting.

01 / 13

Installation and first launch

Install the unchanged package, activate the licence and begin with Sandbox.

Przelewy24 PrestaShop module and payment configuration.
Przelewy24 PrestaShop module and payment configuration.

Requirements

PrestaShop 8.1-9.x, PHP 8.1+, cURL, JSON, HTTPS and outbound access to Przelewy24 and rwdesign.pl.

Install

Open Modules → Module Manager → Upload a module and select the unchanged ZIP. The internal directory must remain przelewy24prestashop.

Activate the licence

Open Przelewy24 in the back office, paste the RWP24PS key and activate it for the current domain.

First test

Select Sandbox, enter one complete credential set, enable the standard method and place a controlled order.

02 / 13

Merchant account and credentials

Every value must belong to the same Przelewy24 environment.

Merchant and POS

Enter Merchant ID and POS ID exactly as shown in the P24 panel.

CRC key

The CRC key creates SHA-384 signatures. Never publish it or include it in support screenshots.

API/report key

The REST API key authenticates access checks, method discovery, verification and refunds.

Protected fields

Saved secrets are masked. An empty secret field preserves the existing value.

03 / 13

Sandbox and production

Keep test and live credentials strictly separated.

Sandbox

Uses sandbox.przelewy24.pl and test money. Complete success, failure and refund scenarios before launch.

Production

Uses secure.przelewy24.pl. Run one low-value controlled transaction after switching.

Access test

Use the built-in API test before enabling methods for customers.

Do not mix keys

A mixed Merchant/POS/CRC/API set causes authentication or signature failures.

04 / 13

Payment methods

Enable and present each customer-facing method independently.

Separate Przelewy24 payment methods in checkout.
Separate Przelewy24 payment methods in checkout.

Przelewy24

Standard redirect to the secure P24 method-selection page.

Cards

Visa and Mastercard can be exposed separately only after card acceptance is activated by Przelewy24 for the merchant.

BLIK

A separate BLIK option uses the dedicated P24 channel and still requires account availability.

PayPo and wallets

PayPo, Apple Pay and Google Pay appear only when enabled and available for the account, amount and device.

05 / 13

Checkout appearance editor

Presets and live preview affect only this module.

Checkout presentation controlled by the module.
Checkout presentation controlled by the module.

Presets

Choose the default, compact, outline or dark presentation as a starting point.

Live preview

Colour, border, radius and spacing changes are shown before saving.

Logotypes

Show or hide the official Przelewy24 and supported-method logos.

Scoped styles

Module CSS is isolated so it does not restyle other payment gateways.

06 / 13

Registration and customer return

An order is created before the exact transaction is registered.

Transaction configuration and secure verification flow.
Transaction configuration and secure verification flow.

Session ID

A unique session links the PrestaShop cart, order and P24 transaction.

Amount

Amounts are sent as integer grosz values with the order currency.

Return URL

The browser return displays the order result but is not proof of payment.

Waiting state

The order remains in the dedicated waiting status until verified notification processing completes.

07 / 13

Signed notifications and verification

Server-side verification is authoritative.

SHA-384 signature

The notification is accepted only when its canonical payload signature matches the saved CRC key.

Transaction verify

After signature and amount checks, the module calls transaction/verify before marking the order paid.

Idempotency

Repeated notifications do not duplicate payment completion or order-state changes.

Public endpoint

Do not protect module notification routes with login, Basic Auth, bot challenges or full-page cache.

08 / 13

Full and partial refunds

Credit slips can initiate REST refunds and track their final callback.

Request

The module sends order ID, session ID, amount, request ID, refundsUuid and a public status URL.

Partial refund

The refundable total cannot exceed the remaining captured transaction amount.

Asynchronous result

ACCEPTED means queued; COMPLETED or REJECTED comes from the signed refund callback.

Safe retry

Check the stored refund record and P24 panel before retrying a timeout.

09 / 13

Order states and operations

Keep paid, waiting and failed orders unambiguous.

Waiting

A registered but unverified payment stays in the Przelewy24 waiting state.

Paid

A successfully verified transaction changes the order to the native payment-accepted state.

Failure

A failed or abandoned payment never receives a paid state.

Audit

Transaction and refund identifiers remain in dedicated module tables for diagnosis.

10 / 13

Licence and private updates

One purchase activates one domain for 12 months.

Activation

The RWP24PS key is entered directly in the module; no extra licence module is required.

Domain reset

Reset the old installation from the customer account before moving the licence.

Updates

An active licence authorises protected release metadata and package downloads.

Version

The first production release remains version 1.0.0.

11 / 13

Security and data handling

Secrets and payment state are validated on the server.

No card data

Raw card numbers and CVV are never stored by the module.

Secret handling

CRC, API key and licence key must be removed from shared logs and screenshots.

HTTPS

Checkout, returns and callbacks require a valid public HTTPS configuration.

Permissions

Restrict module configuration and refunds to trusted back-office profiles.

12 / 13

Production checklist

Complete every item before enabling live customers.

API access

Production testAccess succeeds with the complete live credential set.

Methods

Only services activated on the merchant account are enabled.

Lifecycle

Success, failure, delayed callback and partial refund were checked end-to-end.

Operations

Backups, logs, email, stock and order-state workflows were confirmed.

13 / 13

Troubleshooting

Check environment, credentials, callbacks and account services in that order.

Authentication error

Confirm Merchant ID, POS ID and API key belong to the selected environment.

Invalid signature

Confirm the CRC key, integer amount, currency and canonical field order.

Order remains waiting

Check callback reachability, firewall/CDN rules and transaction/verify logs.

Card method unavailable

Submit the official card activation request to Przelewy24 and wait for merchant approval.

Refund remains accepted

Refund processing is asynchronous; wait for the signed result callback and inspect the P24 panel.

Copyright © RWDESIGN,
All rights reserved.