Docs / Plugin guide / PrestaShop

This plugin guide should tell you exactly what to verify before PrestaShop routes a live order into Payvra settlement.

The PrestaShop integration is an installable payment module that adds Payvra as a checkout option and reconciles order state through signed webhooks. Use this page to prove the installation path, payment-state reconciliation, and the exact switches you flip when the store moves from sandbox to live.

Create free sandbox Review API reference

Treat the module like any other payment method: upload it through the module manager, confirm one full sandbox order lifecycle, and only then swap the API key and webhook secret to live values.

What this guide proves

Checkout redirect

Confirm the Payvra payment option appears at checkout, creates a payment via the API, and redirects the shopper into the hosted checkout without breaking the cart or order reference.

Signed callback

Verify the PrestaShop callback controller receives the signed Payvra webhook and updates the order only after the HMAC signature is accepted.

Refund route

Confirm the refund action from the PrestaShop order page maps back to the matching Payvra payment so operators are not forced into manual off-platform refund work.

Operator facts

Runtime model

Installable PrestaShop module uploaded through the back office module manager.

Checkout route

PrestaShop checkout -> Payvra hosted checkout -> signed callback to the store.

Store requirement

PrestaShop 8.0+, PHP 8.1+, and HTTPS on the storefront.

Live promotion

Swap the Payvra API key and webhook secret after the sandbox order path is verified.

Overview

Treat this page as an operator checklist. Each section below maps one part of the plugin path you should verify before you promote checkout traffic to live funds.

Checkout redirect

Confirm the Payvra payment option appears at checkout, creates a payment via the API, and redirects the shopper into the hosted checkout without breaking the cart or order reference.

Signed callback

Verify the PrestaShop callback controller receives the signed Payvra webhook and updates the order only after the HMAC signature is accepted.

Refund route

Confirm the refund action from the PrestaShop order page maps back to the matching Payvra payment so operators are not forced into manual off-platform refund work.

Requirements

Make sure the store, hosting, and account prerequisites are in place before you install the plugin path.

•

PrestaShop 8.0 or later.

•

PHP 8.1 or later.

•

A Payvra account with sandbox credentials.

•

HTTPS enabled on the storefront.

Setup

Get the plugin or bridge installed first. Then verify that the store can hand checkout traffic to Payvra before you spend time on live credentials.

Download the module package

Start from the packaged module zip so the install path you test is the same artifact operators deploy later in production.

Module package

1/downloads/payvra-prestashop.zip

Upload through the PrestaShop module manager

In the PrestaShop back office, go to Modules → Module Manager, click "Upload a module," and select the zip. If you prefer manual deployment, extract the payvra folder into modules/ first and then install from the module list.

Confirm the payment method appears at checkout

Open the PrestaShop checkout and verify the Payvra payment option is listed. Do this before you wire live credentials so the storefront configuration issue is separated from payment-mode issues.

Keep the first install in sandbox mode

Use the module to prove the redirect and callback flow before real funds are involved. The production cutover should only change the Payvra secret material, not the installation flow.

Configuration

Keep the runtime settings explicit so operators can tell which key, secret, and settlement target a store is using at a glance.

Enable payment method

Turn on the Payvra payment method in the module configuration only after the module is installed and the store is ready to test a checkout path.

Sandbox mode

Keep this enabled while you rehearse one complete order lifecycle. The goal is to validate store behavior, not just that the settings save correctly.

API key

Start with sk_test_.... Replace it with sk_live_... only after the signed webhook path is stable and the PrestaShop order transitions are correct.

Webhook secret

Store the Payvra signing secret in the module configuration so operators can rotate it without changing the module code or other store settings.

Settlement currency

Choose the post-payment settlement target the merchant should receive after Payvra processes the payment and any conversion behavior.

Store listing

The exact distribution surface operators reach for when they install the plugin. The card below mirrors the listing fields shoppers and merchants verify before adopting a payment path.

PrestaShop Addons marketplaceModule verified

Payvra. Distributed as a packaged module zip uploaded through the PrestaShop module manager.

Payvra Crypto Payment Module for PrestaShop 8

Operators install through the PrestaShop module manager, the same upload-and-install path PrestaShop uses for every other gateway.
The packaged zip is identical in dev and production, so the artifact tested in sandbox is the artifact promoted to live.
The module exposes a front-controller route under the existing module dispatcher, so the storefront does not need any custom rewrite rules.

Download the PrestaShop module

Listing facts

Distribution: Module zip + Addons listing
PrestaShop: 8.0 or later
Requires PHP: 8.1 or later
Module slug: payvra
Cost: Free

Webhook setup

The plugin path is only production-safe once signed delivery is verified and the store can reconcile the final payment state automatically.

Copy the store callback URL

This is the front-controller endpoint the Payvra module exposes for signed webhook delivery.

Store webhook URL

1https://yourstore.com/module/payvra/webhook

Add the endpoint in the Payvra dashboard and subscribe to the order-facing events first: payment.confirmed, payment.completed, payment.failed, payment.expired, refund.completed, and refund.failed.

Verify the callback before order mutation logic runs

The module should reject stale or unsigned requests before it changes the PrestaShop order state. If the signature is valid, the callback can safely update the order to the correct payment status.

Platform webhook quirks

PrestaShop's front-controller dispatcher and order-status hooks both intercept signed webhook delivery. These are the platform-specific gotchas that show up most often in operator rollouts.

Friendly URLs

The callback path /module/payvra/webhook only resolves with PrestaShop friendly URLs enabled. Without them the dispatcher returns 404 even though the module is installed and the module manager shows it as enabled.

Smarty cache

After install, clear the Smarty cache from Advanced Parameters. A stale Smarty cache can keep the storefront serving the old payment-method list and shoppers will not see the Payvra option even after the module is enabled.

Hook order_status_update

The order-status hook can fire before the signed webhook flips the order to Payment Accepted. Treat the signed Payvra event as the source of truth and ignore order-status notifications until the webhook has been accepted.

Multistore scope

When PrestaShop multistore is enabled, configure one Payvra webhook endpoint per shop. Otherwise the dispatcher can route the event to a different shop's order tables and the original order stays in Awaiting Payment.

Testing in sandbox

Run one full rehearsal with test credentials and confirm the checkout handoff, payment confirmation, and order update path end to end.

Payment method visibility

Place a sandbox order and confirm the Payvra payment option appears at checkout and redirects the shopper into hosted checkout.

Lifecycle rehearsal

Watch the sandbox payment progress from pending to confirmed while you compare the PrestaShop order history against the Payvra webhook delivery log.

Order resolution

The PrestaShop order should move to Payment Accepted only after the signed event is received and accepted, not before the customer returns to the store.

Promote to live

Only switch the credentials and webhook secret after the sandbox route is boring and repeatable.

Generate a live Payvra key and replace the sandbox sk_test_... value with sk_live_... in the module configuration.

Create a live webhook for the same callback URL and paste the live whsec_... value into the module settings.

Disable sandbox mode only after the redirect, callback, and order-state path are all stable in rehearsal.

Run one low-risk production order and compare the PrestaShop order history with the Payvra event log before wider rollout.

Refunds

Confirm the store-side refund action maps back to Payvra before you announce the plugin internally.

Trigger the refund from the PrestaShop order page so the store and Payvra stay on the same source-of-truth path.

Use the Payvra refund action through the module, not a manual PrestaShop-only refund, so the original payment reference and payout destination remain attached to the order.

Confirm the refund shows up in both PrestaShop order history and the Payvra dashboard before the issue is handed back to support.

Troubleshooting

Use these checks when the plugin path stalls. Each item points to the fastest place to confirm whether the problem is in storefront setup, Payvra delivery, or the operator config.

Payment method does not appear at checkout

Check that the module is installed and enabled in the module manager, the payment method is turned on in the module configuration, and the store is running over HTTPS. Also verify the PrestaShop cache has been cleared after installation.

Orders stay in Awaiting Payment after payment

This usually points to a webhook issue. Compare the Payvra webhook delivery log with the PrestaShop order history to see whether the callback URL, signing secret, or order status transition failed.

Refund action cannot find the Payvra payment

Orders created before the module was installed, or payments that were not processed through Payvra, will not have the stored payment reference required for automated refunds.

Module installs but checkout still fails

Re-check the credential mode. A common cause is a live store still using sk_test_... or a stale sandbox webhook secret after the operator believes the store has been promoted.

Ready to validate the PrestaShop module?

Prove one sandbox order from checkout redirect to signed callback, then promote the same module to live mode by switching only the Payvra credentials and webhook secret.

Get sandbox keys Back to docs

This plugin guide should tell you exactly what to verify before PrestaShop routes a live order into Payvra settlement.

Treat the module like any other payment method: upload it through the module manager, confirm one full sandbox order lifecycle, and only then swap the API key and webhook secret to live values.