Installation

Add the Buckaroo app to your Odoo database, then verify it before you configure anything.

Before you begin

You need:

• A Buckaroo account. Sign up here if you don't have one. You can install and test the app while your application is being reviewed.
• Odoo 19.0, Community or Enterprise.
• Odoo.sh or a self-hosted installation. Odoo Online is not supported, because it does not allow custom apps.
• The Payment and eCommerce apps installed in Odoo.
• The buckaroo-sdk Python package, which the app depends on.
• Command-line or repository access, depending on how you host.

Install

Get the app from the Odoo Apps store, or clone it from GitHub:

git clone --branch 19.0 https://github.com/buckaroo-it/Odoo.git

How you add it to your database depends on your hosting.

Odoo.sh

1. Commit the payment_buckaroo_official folder into your Odoo.sh project repository.
2. Add the contents of the app's requirements.txt to your project's own requirements.txt, so buckaroo-sdk is installed during the build.
3. Push your changes and wait for the build to finish.

Self-hosted

Copy the app into your addons path and install the Python dependency:

cp -r Odoo/payment_buckaroo_official /path/to/odoo/addons/
pip install -r Odoo/requirements.txt

Restart the Odoo service afterwards.

Activate the app

However you added it, finish in Odoo:

1. Go to Apps.
2. Select Update Apps List.
3. Search for Buckaroo and select Activate.

Verify the installation

Go to Invoicing → Configuration → Payment Providers, or Website → Configuration → Payment Providers. Buckaroo Official should appear in the list, still set to Disabled.

Upgrade

Update regularly. New payment methods, scheme-mandated changes and fixes all arrive through releases. Read the release notes before upgrading.

Replace the app folder with the new version, then upgrade it. On Odoo.sh, commit the new version and let the build run. On a self-hosted database:

./odoo-bin -d YOUR_DATABASE -u payment_buckaroo_official --stop-after-init

Your provider credentials and payment method settings are preserved. See Releases and upgrading for the full procedure.

Server configuration

Firewall and IP allowlisting

Buckaroo sends push messages to your store to confirm payment results. If a firewall, WAF or IP allowlist blocks them, payments will succeed at Buckaroo while your orders sit pending.

Allow inbound traffic from Buckaroo's push addresses and ports. See Push messages for the current list.

You don't need to configure a push URL anywhere, because the app sends it with each transaction. You do need push messages switched on for your store in Buckaroo Plaza. There is more on both in Connect your Buckaroo account.

Staging environments behind basic authentication will also reject pushes.

Apple Pay domain association

If you plan to offer Apple Pay as an inline button, Apple has to verify your domain. The app serves the association file automatically at:

/.well-known/apple-developer-merchantid-domain-association

There is nothing to upload. Open that path on your store to confirm it returns a block of text. See Payment methods.

Multi-website setups

The provider can be configured per company, each with its own Store key, while the Secret key is shared across your Buckaroo account. See Connect your Buckaroo account.

Uninstall

Uninstall Buckaroo Official from the Apps menu, then remove the app folder from your addons path or project repository. On a self-hosted database, restart the Odoo service.

Uninstalling leaves historical transaction and payment data in place.