Axepta BNP Paribas V2 for Odoo: Payment Methods, Wero and Moving from V1

If your merchant contract is with BNP Paribas, you are probably reading this for one of two reasons: you are starting on Odoo and want to connect Axepta, or you still run a V1 integration and BNP Paribas is asking you to move to V2. Both cases are covered below.

What changes with Axepta V2

With V1, every payment request was encrypted with Blowfish and then signed with HMAC using shared keys. It works, but it is heavy to maintain, and BNP Paribas is moving its merchants to the new API. V2 changes three things for you:

• Authentication uses OAuth2 client credentials: Odoo gets a token from your Merchant ID and API key instead of encrypting each message;
• Exchanges are JSON over a REST API, with an idempotency header so that a replayed request never creates a second payment;
• Notifications arrive by webhook in real time and update the Odoo transaction even if the customer closes the browser before returning to the shop.

The module needs no external Python library: it installs like any other Odoo module, on Odoo.sh or on your own server.

Available payment methods

The module handles eight payment methods, plus a "Pay with Axepta" option that shows every method of your Merchant ID on the Axepta page. Each method is enabled separately in Odoo, provided it is also open on your BNP Paribas contract.

Two of them deserve attention. Instanea is a SEPA instant transfer: the money arrives within seconds and there is no chargeback, which matters for large baskets. Wero is the payment solution of the European banks (EPI), which BNP Paribas promotes to its customers; better to have it on your checkout before shoppers start looking for it.

For instalments, Floa Pay goes through Axepta here. If you prefer a direct contract with FLOA, we also have a dedicated module, described in FLOA Pay for Odoo.

The payment flow in Odoo

1. The customer picks a payment method on the shop, on the payment link of a quotation or on an invoice in the portal.
2. Odoo opens a payment session at Axepta and redirects the customer to the PCI DSS compliant hosted page.
3. The customer pays, with 3D Secure 2 for cards (frictionless or challenge depending on their bank), then returns to Odoo.
4. The webhook and the return URL confirm the transaction. The order is validated and the payment reconciled with the invoice.

The currency is taken from the Odoo transaction. The module covers France, Belgium, the Netherlands, Luxembourg, Germany and Austria, among the other countries Axepta serves.

Moving from Axepta V1 to V2 without downtime

V2 is a separate payment provider in Odoo, not an update of the old one. That is good news: you can prepare the switch without touching what is running. This is the order we follow with our clients.

1. Ask BNP Paribas for your V2 credentials: Merchant ID and API key, for test and for production. List the payment methods open on the contract at the same time.
2. Install the V2 module on a copy of your database and configure the provider in test mode with the demo Merchant ID.
3. Test every enabled method: accepted, refused and abandoned payments, and the webhook confirmation when the customer never comes back to the shop.
4. Go live: publish the V2 provider and unpublish V1 at the same time. Customers see no difference.
5. Keep the history: past transactions stay linked to the old provider. To refund an order paid through V1, use the Axepta back office.

If the switch coincides with an Odoo version upgrade, do it after the migration, on the new version: one project at a time, and simpler tests. Our Odoo migration page explains how we run these projects.

Technical sheet

Frequently asked questions

Is my Axepta V1 contract compatible with this module?

The commercial contract stays the same, but V2 uses different credentials (Merchant ID and API key). Ask your BNP Paribas advisor for them before you start.

Are all payment methods active by default?

No. A method only shows if it is enabled in Odoo and open on your contract. Wero, Instanea or Floa Pay usually have to be requested separately.

Does the module work on Odoo Online?

No, Odoo Online does not accept third-party modules. It installs on Odoo.sh or on your own server.

Can it be used for invoices, not only for the shop?

Yes. Invoices sent by e-mail and the customer portal offer Axepta payment, and the payment is reconciled automatically.