This plugin integrates the Paysera payment gateway with WooCommerce stores. Customers can pay using credit/debit cards and bank payment methods across Europe through a single gateway agreement.
The plugin supports both WooCommerce checkout experiences:
Default log level is Error. Logs can be viewed and downloaded from the plugin’s Extra Settings page. Downloading the zip archive requires the PHP zip extension. Log files can also be deleted from WooCommerce Status Logs. Available logging levels:
Fees for the Paysera Checkout service are listed on the Paysera website:
Paysera Checkout fees >
Paysera client support is available in English 24/7 at +44 20 80996963 or support@paysera.com. Additional languages are available during business hours. For more information visit paysera.com.
This plugin connects to the following Paysera services. All requests are made over HTTPS and only when the corresponding feature is used.
The plugin sends order data (amount, currency, order identifier, customer billing details, return URLs) to the Paysera Checkout API to create payment orders, retrieve available payment methods and process payment status callbacks. This is the core service of the plugin: without it the gateway cannot operate. Requests are made when a customer initiates a payment at checkout, when the merchant configures the gateway in the admin and when Paysera notifies the store about a status change.
The plugin retrieves translation files for payment method names and gateway labels from Paysera’s translation proxy (translation-proxy.paysera.net). The request contains only the plugin translation namespace and locale. No order or customer data is sent. The request is performed by the diagnostic “Translation Proxy Connectivity” check and during translation refresh.
The plugin downloads Paysera’s public key from https://paysera.com/download/public.key to verify the signature of payment status callbacks and to test that the server can establish modern TLS connections to Paysera. The request contains no store, order or customer data. It is performed during the diagnostic “TLS Versions Support Check” and when verifying callback signatures.