Requirements
PrestaShop 8.1-9.x, PHP 8.1+, cURL, JSON, HTTPS and outbound access to Przelewy24 and rwdesign.pl.
A practical guide from installation and safe testing through production configuration, maintenance and troubleshooting.
Install the unchanged package, activate the licence and begin with Sandbox.

PrestaShop 8.1-9.x, PHP 8.1+, cURL, JSON, HTTPS and outbound access to Przelewy24 and rwdesign.pl.
Open Modules → Module Manager → Upload a module and select the unchanged ZIP. The internal directory must remain przelewy24prestashop.
Open Przelewy24 in the back office, paste the RWP24PS key and activate it for the current domain.
Select Sandbox, enter one complete credential set, enable the standard method and place a controlled order.
Every value must belong to the same Przelewy24 environment.
Enter Merchant ID and POS ID exactly as shown in the P24 panel.
The CRC key creates SHA-384 signatures. Never publish it or include it in support screenshots.
The REST API key authenticates access checks, method discovery, verification and refunds.
Saved secrets are masked. An empty secret field preserves the existing value.
Keep test and live credentials strictly separated.
Uses sandbox.przelewy24.pl and test money. Complete success, failure and refund scenarios before launch.
Uses secure.przelewy24.pl. Run one low-value controlled transaction after switching.
Use the built-in API test before enabling methods for customers.
A mixed Merchant/POS/CRC/API set causes authentication or signature failures.
Enable and present each customer-facing method independently.

Standard redirect to the secure P24 method-selection page.
Visa and Mastercard can be exposed separately only after card acceptance is activated by Przelewy24 for the merchant.
A separate BLIK option uses the dedicated P24 channel and still requires account availability.
PayPo, Apple Pay and Google Pay appear only when enabled and available for the account, amount and device.
Presets and live preview affect only this module.

Choose the default, compact, outline or dark presentation as a starting point.
Colour, border, radius and spacing changes are shown before saving.
Show or hide the official Przelewy24 and supported-method logos.
Module CSS is isolated so it does not restyle other payment gateways.
An order is created before the exact transaction is registered.

A unique session links the PrestaShop cart, order and P24 transaction.
Amounts are sent as integer grosz values with the order currency.
The browser return displays the order result but is not proof of payment.
The order remains in the dedicated waiting status until verified notification processing completes.
Server-side verification is authoritative.
The notification is accepted only when its canonical payload signature matches the saved CRC key.
After signature and amount checks, the module calls transaction/verify before marking the order paid.
Repeated notifications do not duplicate payment completion or order-state changes.
Do not protect module notification routes with login, Basic Auth, bot challenges or full-page cache.
Credit slips can initiate REST refunds and track their final callback.
The module sends order ID, session ID, amount, request ID, refundsUuid and a public status URL.
The refundable total cannot exceed the remaining captured transaction amount.
ACCEPTED means queued; COMPLETED or REJECTED comes from the signed refund callback.
Check the stored refund record and P24 panel before retrying a timeout.
Keep paid, waiting and failed orders unambiguous.
A registered but unverified payment stays in the Przelewy24 waiting state.
A successfully verified transaction changes the order to the native payment-accepted state.
A failed or abandoned payment never receives a paid state.
Transaction and refund identifiers remain in dedicated module tables for diagnosis.
One purchase activates one domain for 12 months.
The RWP24PS key is entered directly in the module; no extra licence module is required.
Reset the old installation from the customer account before moving the licence.
An active licence authorises protected release metadata and package downloads.
The first production release remains version 1.0.0.
Secrets and payment state are validated on the server.
Raw card numbers and CVV are never stored by the module.
CRC, API key and licence key must be removed from shared logs and screenshots.
Checkout, returns and callbacks require a valid public HTTPS configuration.
Restrict module configuration and refunds to trusted back-office profiles.
Complete every item before enabling live customers.
Production testAccess succeeds with the complete live credential set.
Only services activated on the merchant account are enabled.
Success, failure, delayed callback and partial refund were checked end-to-end.
Backups, logs, email, stock and order-state workflows were confirmed.
Check environment, credentials, callbacks and account services in that order.
Confirm Merchant ID, POS ID and API key belong to the selected environment.
Confirm the CRC key, integer amount, currency and canonical field order.
Check callback reachability, firewall/CDN rules and transaction/verify logs.
Submit the official card activation request to Przelewy24 and wait for merchant approval.
Refund processing is asynchronous; wait for the signed result callback and inspect the P24 panel.
Copyright © RWDESIGN,
All rights reserved.
I will help you choose a solution
RWDESIGN helpdesk
Enter your contact details. The RWDESIGN team will receive the conversation history and contact you by email or phone.