VibeFox Paysera for PrestaShop — Help

Requirements

PrestaShop: 8.0 to 9.x.

PHP: 8.0 or later. The module refuses to install on older PHP versions.

Paysera project: you need the project ID and the project password (sign key) of your Paysera project. The payment methods the customer sees are the ones enabled in this project. Nothing has to be configured in Paysera for the callback: its URL is sent with every payment request.

Reachable shop: orders are created by the Paysera callback, so your shop must be reachable from the internet, not behind a login, basic authentication or a firewall. The callback itself works while the shop is in maintenance mode.

VibeFox license key: bought on vibefox.net. One key works on one domain.

Installation

1. In the back office go to Modules > Module Manager and click Upload a module. Choose the module ZIP file.

2. When the upload finishes, click Configure, or find VibeFox Paysera Payment in the module list later and click Configure.

3. Paste your VibeFox license key into License key in the license block at the top of the Configure page and click Activate (see License key).

4. Enter the Project ID and the Project password from your Paysera account (see Configuration).

5. Optional: enable Allow test payments in the Paysera project and Test payments in the module to try the flow without charging money. Turn it off before selling.

6. Turn on Enable/Disable and click Save.

On install the module creates two order statuses, Awaiting Paysera payment and Paysera payment on hold. PrestaShop offers a new payment module for all currencies, countries and customer groups. You can limit them in Payment > Preferences.

Configuration

All settings are on the module page: Modules > Module Manager > VibeFox Paysera Payment > Configure. Each section has its own Save button, which saves the whole page. Above the fields the page shows Paysera is hidden at checkout until the project ID and the project password are entered. while one of them is missing, and Test mode is on: customers are not charged. Turn off "Test payments" and select "Production" before accepting real orders. while test payments or the sandbox are on.

Paysera

Enable/Disable: Enable Paysera Payment turns the payment method on or off. Default: off.

Title: the payment method name customers see at checkout. It is also the payment method name stored in the order. Default: Paysera. Required.

Description: the text shown under the payment method at checkout. Default: Pay securely via Paysera.

Paysera project

Find the project ID and the project password in your Paysera account under Projects and activities, your project, General project settings.

Callback URL: the address Paysera uses to confirm every payment. With friendly URLs it looks like https://your-shop/module/wcp_paysera_payment/callback, possibly with a language code. It is sent with each payment automatically, so nothing has to be configured in Paysera, but it must be reachable from the internet. Orders are created only by these signed callbacks.

Project ID: the numeric ID of your Paysera project. Only digits are accepted: any other value gives the error Project ID must be a number: the numeric ID of your Paysera project. and nothing is saved.

Project password: the project password (sign key). It signs payment requests and verifies Paysera callbacks. The saved password is never shown again. The field stays empty and shows Saved — leave empty to keep it. Type a new value only to change it.

Clear saved password: tick Project password and click Save to remove the saved password. An empty field keeps the saved value.

Testing

Test payments: sends payments in test mode, so no money is charged. Paysera returns a successful test payment without charging the customer. Enable Allow test payments in the Paysera project settings first. While this option is on, test payments mark orders as paid; when it is off, a test payment puts the order on hold. Default: off. While it is on, customers see TEST MODE — no money will be charged. under the payment method.

Environment: where the customer is sent. Keep Production for a normal Paysera project, also for test payments. Default: Production.

Advanced

Debug log: writes payment events to logs/wc_psr_debug.log.php in the module folder. The file cannot be opened from the web. Errors and warnings are always written; the other steps only while this option is on. Passwords and customer data are never written. Default: off.

Log: shows the size and the latest entries of the log. Click Clear log to empty it.

Delete data: when on, uninstalling the module removes the module settings and the log. Order data (orders, Paysera payment records, order statuses) is always kept. Default: off.

Checkout

At the payment step the customer chooses the payment method (by default Paysera) and confirms the order. The module builds a signed payment request with the cart total in the minor unit of the cart currency, the customer's name, e-mail and billing address, and the language of the shop page (Lithuanian, Latvian, Estonian, Russian, German, Polish, otherwise English). The customer is sent to the Paysera payment window and chooses a bank, card or other method there. No order exists yet at this point.

Paysera confirms the payment with a server-to-server callback. The order is marked paid only after Paysera confirms it with a signed callback; the customer's return to the shop never creates or pays an order. When the customer comes back after the callback, the standard order confirmation page is shown. If the bank has accepted the payment order but not executed it yet, the order is created in Awaiting Paysera payment and the page shows Paysera is confirming your payment. You will receive an e-mail as soon as it is confirmed — there is no need to pay again. For an order on hold the page shows Your payment is being reviewed. We will contact you if anything else is needed.

If the customer comes back before the callback, a Payment confirmation page explains that the order will be created as soon as Paysera confirms the payment and offers Check again and Back to checkout.

If the customer cancels in the Paysera window, the customer is back at checkout with The Paysera payment was cancelled. You can try again or choose another payment method. If Paysera reports that the payment was not executed, the message is The payment was not completed. You can try again or choose another payment method. The cart is kept in both cases. If the cart already has an order, a new attempt goes straight to the order confirmation instead of a second payment.

If the payment cannot be started, the customer stays at checkout with Paysera payments are temporarily unavailable. Please choose another payment method. or, for an invalid order total, This order cannot be paid via Paysera. The reason is written to the log.

The callback works while the shop is in maintenance mode and is not blocked by the country restriction of your shop.

The module has no refunds from the back office, no choice of bank or payment method on the checkout page, no subscriptions, no saved cards and no Paysera delivery or courier services.

Orders

Order statuses

No order yet: the customer was sent to Paysera and the callback has not arrived yet, or the customer cancelled. Only the cart exists.

Payment accepted: Paysera confirmed the payment with the matching amount and currency. The payment is recorded with the Paysera request ID as the transaction ID, and a note shows the request and the payment method, marked (TEST — no money charged) for test payments.

Awaiting Paysera payment: Paysera accepted the payment order, but the bank has not executed it yet. The order moves to Payment accepted when Paysera confirms the payment.

Paysera payment on hold: the payment needs a manual review. The paid amount or currency differs from the cart or order total, a TEST payment arrived while Test payments is off (no money was charged), or the payment was confirmed after the customer had cancelled it. The payment is not recorded. The note explains it, and the Paysera block asks you to check the payment in your Paysera account, then set the order to Payment accepted or cancel it and refund the payment in Paysera.

Cancelled: a payment confirmed later for a cancelled order does not change its status. A note asks you to restore the order (set it to Payment accepted) or refund the payment in Paysera. A later TEST payment or amount mismatch for a cancelled order also adds only a note.

If another successful payment arrives for an order that is already paid, the order is not changed, and a note asks you to refund the duplicate in your Paysera account. Other Paysera statuses (payment not executed, additional information) only add a note.

Paysera payment block

The order page shows a Paysera payment block with the Paysera order ID (the cart number and the attempt), the Paysera request ID, the environment and a TEST payment mark, the payment status, the requested and paid amounts, the payment method and the module's notes.

Refunds

Refunds from the back office are not supported: the Paysera payment window protocol has no refund API. Make refunds in your Paysera account. When Paysera reports a refund, a note with the refunded amount is added to the order, and the order status is not changed. Record the refund in PrestaShop manually if needed.

License key

The module works with a VibeFox license key from vibefox.net. The license block License — VibeFox Paysera Payment is the first block on Modules > Module Manager > VibeFox Paysera Payment > Configure, above the settings. Paste the key into License key and click Activate. After that the block shows the key masked, the status (for example the date the license is active until and your domain) and the buttons Check now to check the status again, Change key to enter another key and Remove key to remove the key from this shop. Below them are the line Product: presta-payment-paysera and the link Manage licenses and domains in your account, which opens your vibefox.net account. Only employees with the Configure permission for the module can change the key. The texts of the block follow the back office language (English and Russian are included).

If the key is not accepted, the block says why, for example Key not found, This key belongs to another product, Domain limit reached or License expired on a date. After the shop address changes, or after you free a domain slot in your account, click Check now. If the license server cannot be reached, the module keeps working on the last known status.

One key works on one domain: the domain of the main shop, also in a multistore setup. Removing the key from the shop does not free its domain slot. Free the slot in your vibefox.net account.

Without an active key, Paysera is not shown to customers at checkout. If a payment is started anyway, the customer sees This payment method is not available. Please choose another one. The PrestaShop storefront does not know that you are logged in to the back office, so the payment method is hidden for you too: you can set up the module before you buy a key, but not test it at checkout. A reminder appears in Modules > Module Manager on the Alerts tab. Existing orders are not affected: payments already started are still confirmed by the callback.

When a license expires, the module keeps working, but updates and support need a renewal. The status is checked again automatically while you work in the back office: once a day for the first 14 days after the key is entered, then once a week. No cron job is needed. Uninstalling or resetting the module always removes the license key and license status.

Troubleshooting

Paysera does not appear at checkout: check that the license is active, Enable/Disable is on and both Project ID and Project password are entered. The settings page shows a warning while they are missing. In Payment > Preferences check that the module is allowed for the cart currency, the customer's country and the customer's group.

The payment went through, but no order was created: the order is created by the Paysera callback, not by the customer's return. Check that your shop is reachable from the internet at the Callback URL shown in the settings (not behind a login, basic authentication or firewall), and look at the Log field on the module page.

Callback answers Invalid signature: the Project password does not match the project, or the callback is not from Paysera. Copy the project password again. If you changed the project or the password, payments started before the change can no longer be verified.

Callback answers Project ID mismatch: the Project ID in the settings differs from the project that made the payment.

Callback answers Order not found: the cart in the callback has no Paysera payment in this shop, for example the payment was started in another shop with the same project.

Callback answers Gateway not configured, Busy or Temporary error: the project ID or password is empty, another callback for the same cart is still running, or the order could not be created (for example, the module is disabled). Paysera retries the callback. Turn on Debug log to see the reason.

Paysera rejects the payment window or says the project does not exist: check Environment. A normal Paysera project works only with Production; Sandbox needs a project created in the Paysera sandbox environment.

The test payment does not pay the order: a TEST payment pays an order only while Test payments is on. Otherwise the order is put on hold with a note that no money was charged. Also enable Allow test payments in the Paysera project.

An order is Paysera payment on hold with a note about an amount/currency mismatch: Paysera confirmed a payment whose amount or currency differs from the cart total, for example the cart was changed in another tab after the customer started paying. Compare the payment in your Paysera account and accept the order or refund the payment manually. A later correct payment for the same order marks it paid.

The customer sees Paysera payments are temporarily unavailable: look at the Log field. The project ID or password may be empty, or one of the shop addresses sent to Paysera is longer than 255 characters.

Uninstall

Go to Modules > Module Manager, open the menu next to VibeFox Paysera Payment and choose Uninstall. The license key and license status of this module are always removed. If Delete data is on, the module settings and the log are removed. If it is off, all settings are kept for a later re-install. The Paysera payment records and the order statuses Awaiting Paysera payment and Paysera payment on hold are always kept. Existing orders keep their payment notes and transaction IDs.

Paysera is a trademark of its respective owner. This module is not affiliated with or endorsed by Paysera.