PrestaShop gives you full control of your storefront, but payments usually arrive one module at a time: one for cards, one for instalments, one for invoice, each with its own settings, its own order flow and its own upgrade to test on every PrestaShop release.
Briqpay for PrestaShop replaces that stack with a single, open source module. Shoppers see every payment method inside the native PrestaShop checkout, you capture, refund and cancel from the order page you already use, and which methods appear in which market is a rule in the Briqpay portal rather than another module install.
PrestaShop merchants tend to hit the same four payment problems as they grow:
Briqpay solves this.
One PrestaShop module gives you a payment layer you control. Connect the providers you want, decide which methods each shopper sees, and manage every order from PrestaShop. Adding a provider later is configuration in the Briqpay portal, not a new module.
The module renders Briqpay as a normal PrestaShop payment option, so personal information, addresses and shipping stay exactly as they are. At the payment step the Briqpay iframe presents every method you have enabled and the purchase completes inside it. No redirect, no separate checkout page, and your theme is untouched.
Validation happens server-side at Briqpay's decision step, the pause after the shopper presses pay but before any money moves. The module checks that terms are accepted and that the cart total still matches, and rejects with a reason shown in the iframe if not. Because the check runs on your server it cannot be bypassed by editing the page. The Briqpay session is kept in step with the cart automatically, and only updated when something has actually changed.
Customer type is detected automatically: a company name on the billing address means a B2B session with invoice and payment terms available; no company name means a consumer session. You can also force either mode.
Capture, refund and cancel are available from a Briqpay panel on the PrestaShop order page, for the full amount or a partial one. They also follow PrestaShop's own workflow when you want them to:
| PrestaShop action | Briqpay operation |
|---|---|
| Order set to Shipped or Delivered | Capture |
| Order set to Refunded | Full refund |
| Credit slip issued | Partial refund |
| Order set to Cancelled | Cancel authorisation |
Every operation is guarded: you cannot capture more than the order total, refund more than was captured, or cancel an order that has already been captured. Webhooks keep PrestaShop in sync with capture and refund status changes made anywhere, and if a shopper pays but never returns to the shop, the order is created for them.
Taking an order by phone or email? Create it in the back office as usual, open the Briqpay panel and click Create payment link. The customer gets a hosted payment page, and when they pay, the existing order moves to its paid state. Three flows are included: consumer, business with payment methods only, and a full B2B checkout with company lookup. A link cannot be regenerated once the order is paid, so a customer is never charged twice.
The module is free, open source (Academic Free License 3.0) and published on GitHub with a test suite and CI:
Install in four steps:
Country, currency and locale are read from PrestaShop, so there is nothing extra to configure per market. Twelve hooks (before session create, at the decision step, after order creation, around capture, refund and cancel, and around payment links) let your developers adjust payloads without forking the module. Logs are written to PrestaShop's own log with secrets, emails and phone numbers redacted.
View the module on GitHub · Read the module documentation · Briqpay API documentation
Upgrading from the 1.x module is automatic: install 2.0 over it and PrestaShop runs the upgrade script, which moves checkout into the native flow and carries your existing payment records across.
For the thinking behind the module, read payment orchestration on PrestaShop: how to add more payment methods without adding more plugins. Running another platform as well? The same Briqpay payment layer sits behind our WooCommerce, Magento 2 and commercetools integrations, and every method in our payment method library is available through it.
Cards, invoice, direct bank, wallets, BNPL and B2B payment terms from the providers you choose, all through a single PrestaShop module. Adding a provider later is configuration, not another install.
Briqpay appears as a standard payment option. Addresses and shipping stay in PrestaShop, and every payment method renders inside the checkout with no redirect and no change to your theme.
Rules in the Briqpay portal decide which methods each shopper sees, and in what order, by country, currency, cart value, category or customer type. Localize and optimize without a PrestaShop release.
A company name on the billing address opens a business session with invoice and payment terms. Consumers get cards, wallets and instalments. Both run from the same checkout.
Full or partial, from the order page or automatically on Shipped, Refunded, credit slip and Cancelled. Guarded so you can never over-capture or double refund. Webhooks keep status in sync.
Send hosted payment pages for phone and email orders, in consumer or B2B flows. The module is free, published under AFL 3.0 on GitHub, with a test suite, CI and twelve developer hooks.
STEP 01
Download the zip from the latest GitHub release, upload it in Module Manager, enter your merchant ID and shared secret, and click Test connection. PrestaShop 1.7.6 to 9.x, PHP 7.2 to 8.3.
STEP 02
Sign directly with the payment providers you want. Briqpay connects them behind the one module you already installed, so nothing changes in PrestaShop when a provider is added.
STEP 03
In the Briqpay portal, decide which methods appear per country, currency, cart value and customer type. Country, currency and locale are read from PrestaShop automatically.
STEP 04
Complete a playground purchase, switch Live mode on, and manage orders from PrestaShop. Add markets and methods as you grow, without new integrations.
Whether you’re integrating for the first time or switching providers, Briqpay helps you go live quickly, stay in control, and scale smarter across markets
Free and open source. Get the latest release from GitHub and be live in your PrestaShop checkout in an afternoon. Download from GitHub
Settings, order management, payment links, webhooks and developer hooks are documented in the module README. The Briqpay API docs cover everything behind it.
Get expert help tailored to your needs, from payment strategy to technical setup. Contact us at integrations@briqpay.com
PrestaShop 1.7.6 through 8.x and 9.x, on PHP 7.2 to 8.3 with the curl and json extensions. Each release is tested in CI, and the module includes upgrade scripts so you can move between versions without reinstalling.
Yes. Briqpay for PrestaShop is open source under the Academic Free License 3.0 and free to download from GitHub. You need a Briqpay merchant account to use it; commercial terms for Briqpay's platform and for your payment providers are separate from the module.
Card, invoice, direct bank transfer, digital wallets, buy now pay later and B2B payment terms, from any provider connected to Briqpay. Which methods a shopper sees depends on the country, currency and language of the session and the rules you set in the Briqpay portal. See our payment method library for what is available per market.
No. Personal information, addresses and shipping stay in PrestaShop's native checkout. Briqpay appears as a payment option, and at the payment step the Briqpay iframe presents your enabled methods and completes the purchase. There is no redirect and no separate checkout page.
Yes. The module detects customer type automatically: a company name on the billing address opens a business session with invoice and payment terms, otherwise the shopper gets consumer methods. You can also force B2B or B2C for the whole store.
From the Briqpay panel on the PrestaShop order page, for full or partial amounts, or automatically: capture when an order is set to Shipped or Delivered, refund on the Refunded status or a credit slip, and cancel the authorisation when an order is cancelled. Each can be switched off in the module settings.
Yes. Create the order in the back office, open the Briqpay panel and click Create payment link. The customer pays on a hosted page and the existing order moves to paid. Consumer and B2B flows are available, and a link cannot be regenerated once the order is paid.
You sign directly with your chosen payment providers, while Briqpay provides the integration and orchestration platform. Briqpay does not handle funds or financial agreements, so you keep the commercial terms and can add or switch providers without a new integration.
Connect any payment provider. Optimize your payment flow. Scale without limitations - with Briqpay’s Payment Integration Platform.
