FAQ

The Buckaroo provider that ships with Odoo is maintained by Odoo, not by Buckaroo. It is built on our legacy HTML gateway, and its payment method list still contains methods that have since been discontinued, so you can enable a method that no longer processes.

Buckaroo Official is built on our current JSON API and is maintained by us alongside the platform.

Yes. Both can be installed at the same time while you move across, because Buckaroo Official registers as a separate payment provider.

1. Install Buckaroo Official and set its status to Test Mode.
2. Enter your credentials, enable the payment methods you want to offer, and place test orders.
3. Set Buckaroo Official to Enabled and set the old Buckaroo provider to Disabled in the same sitting.

While both providers are enabled, the same payment method can appear twice in your checkout. Set the old provider to Disabled rather than uninstalling it, so its existing transactions stay available for reporting and refunds.

The plugin requires Odoo 19 with the eCommerce and Invoicing apps.

It also needs the buckaroo-sdk Python package, version 1.0.0, available in the Odoo environment:

• Odoo.sh: add buckaroo-sdk==1.0.0 to your project's requirements.txt and rebuild the branch.
• Self-hosted: run pip install buckaroo-sdk==1.0.0 in the Python environment that runs Odoo, then restart the service.

Pin the exact version, because the plugin is built against 1.0.0.

English, Dutch, German and French. The plugin follows the language of the Odoo user or the webshop visitor.

More than 30, including iDEAL, Bancontact, credit cards, PayPal, Apple Pay, Google Pay, Klarna, in3, Billink, Riverty, giftcards and Pay Per Email. See Payment methods for the full list.

A method being visible in Odoo does not mean you can accept it yet. It also needs to be active on your Buckaroo contract.

Yes. Every Buckaroo payment method has a Buckaroo Min Amount and a Buckaroo Max Amount. Leave a field empty for no limit.

When the order total falls outside the range, the method is not shown in your checkout. Odoo's payment availability report on the checkout page reports the reason as the amount being outside the Buckaroo limits.

Enter plain positive numbers such as 100.00. The maximum has to be higher than the minimum, otherwise the settings cannot be saved.

Yes. Every Buckaroo payment method has a Payment fee field. It accepts a fixed amount such as 1.50 or a percentage such as 1%. Leave it empty or enter 0 for no fee.

When a fee applies, the payment method label in your checkout shows the surcharge and a surcharge line is added to the order.

The fee is applied in the order currency exactly as you entered it, without currency conversion. Review your amounts if you sell in more than one currency.

These Buy Now, Pay Later methods run their own acceptance check, so they need more customer information than a regular payment. Klarna and Pay Per Email also ask for a salutation, which is required for those transactions.

Complete and accurate billing details reduce the number of rejected payments on these methods.

Express checkout lets your customer pay straight from a wallet button, without filling in the full checkout form first. Apple Pay, Google Pay and PayPal Express are supported, and the delivery address comes from the wallet.

Apple Pay, Google Pay and PayPal each have separate settings for the product page, the cart and the checkout page, so you can enable exactly the placements you want. Apple Pay and Google Pay also let you choose a button style.

Yes. The address from the wallet is used to look up your available delivery methods, and the shipping cost is updated in the wallet before the customer confirms the payment.

Odoo confirms the order once the transaction reaches a successful status. The plugin keeps the transaction and the order in sync through our push message, so the order is still completed correctly when your customer closes the browser before returning to your webshop.

With an authorization the amount is reserved during checkout and collected later, usually when you ship. You then Capture or Cancel the authorization from the order.

No, the plugin captures the full authorized amount only. If you ship part of an order, capture the full amount and refund the difference, or split the order before the authorization is created.

Yes, both full and partial refunds. Open the customer invoice that belongs to the Buckaroo payment and use the Buckaroo refund action. The plugin sends the refund to Buckaroo and creates the matching refund transaction in Odoo.

The plugin handles that as well. When we push the Plaza refund, the plugin recognises it and creates the matching refund transaction in Odoo automatically. The same applies to a capture that you perform in Plaza on an authorized transaction. Please note that the PUSH for refunds should be enabled in the Buckaroo Plaza settings with the correct PUSH URL.

A giftcard can cover part of an order. When the balance does not cover the full total, the plugin splits the payment: the giftcard is processed first and your customer pays the remainder with another payment method. A summary shows how much has already been paid, so the outstanding amount is clear. The full amount will be displayed in the Buckaroo dashboard as a informational type known as a "Group transaction".

Pending usually means Odoo has not received or accepted our push message. Check the following, in order:

1. Is your Odoo environment reachable from the internet? A push cannot be delivered to localhost or to a private staging URL.
   Please also make sure that the IP's and ports where Buckaroo is sending the PUSH messages from is added to your allow list to prevent them being blocked. You can find our IP's listed on this page.
2. Is the base URL of your Odoo environment correct? The plugin builds the push and return URLs from it, so an outdated base URL sends the push to the wrong address.
3. Do your Store Key and Secret Key match the environment? A live key on a provider in Test Mode, or the other way around, makes the push validation fail.
4. Check your Odoo server log. Rejected pushes are logged, including whether the signature was missing or invalid.

Some statuses are genuinely still pending on our side and resolve by themselves, for example a payment awaiting your customer or awaiting approval. Bank Transfer stays pending until the transfer actually arrives, which can take several days.

For the full list, see Status codes.

The plugin validates every push before it processes it, and rejects anything that does not validate. That is expected for a push with a missing or incorrect signature, or one signed with a different Secret Key.

Check that the Secret Key in Odoo matches the Secret Key in Buckaroo Plaza → Settings → API Keys for the same environment.

No. The plugin sends the return URL and the push URL with every transaction, so there is nothing to set up in your Plaza push settings.

What does matter is that your Odoo environment is reachable from the internet and that its base URL is correct, because the plugin builds these URLs from it.

In the case you want to do refunds from the Buckaroo dashboard and want those to trigger in the Odoo environment, then a PUSH URL needs to be configured. But most merchants will do it the other way around, so handle everything from Odoo's environment instead. In that case there is no PUSH URL configuration needed.

This is almost always the missing Python package. Check that buckaroo-sdk==1.0.0 is installed in the Python environment that runs Odoo, and that Odoo has been restarted since.