Connect your account

Link your Odoo database to Buckaroo with your API keys, enable push messages, and make sure your server can receive them.

Get your API keys

You need two values from Buckaroo Plaza → Settings → API Keys:

KeyScopeNotes
Store keyOne per store in your Buckaroo accountAlso referred to as the website key. Use a separate Store key per store if you want transactions reported separately.
Secret keyOne for your entire Buckaroo accountUsed to sign requests and to verify incoming push messages. Treat it like a password.
🔐

Never commit your Secret key to version control or share it in a support ticket. If it leaks, regenerate it in Plaza. Regenerating invalidates the old key immediately for every store using it.


Enter the keys in Odoo

  1. Go to Invoicing → Configuration → Payment Providers, or Website → Configuration → Payment Providers.
  2. Open Buckaroo Official.
  3. Fill in Store Key and Secret Key.
  4. Save.
  5. Select Test Connection to confirm the keys are valid.

Test Connection checks your keys against Buckaroo without placing an order, so it's the quickest way to rule credentials in or out before you go any further.

Test mode and live mode

Unlike some of our other plugins, the Buckaroo app for Odoo sets mode on the provider, not per payment method. Every enabled method follows the provider's state.

StateBehaviour
DisabledThe provider is inactive and does not appear in checkout.
Test modeThe provider is active and sends transactions to the Buckaroo test environment.
EnabledThe provider is active and processes live transactions.

Start in Test mode, work through Test and go live, and switch to Enabled when you're ready.

⚠️

Test and live transactions use the same Store key and Secret key. The only thing separating them is the provider state. Before going live, confirm the provider is set to Enabled rather than Test mode.

Multi-website configuration

The provider is scoped to a company, so a group running more than one webshop can add a Buckaroo Official provider per company and give each one its own Store key. The Secret key is account-level and shared.


Push messages

A push message is Buckaroo's server-to-server notification that a payment has reached a final status. Your store uses it to update the transaction and the order. The customer's browser may never come back: they close the tab, their connection drops, or the method settles hours later. That makes the push the authoritative source, not the redirect.

You don't need to configure a push URL. The app sends the correct push URL with every transaction request, which overrides whatever is configured in Plaza for that store. There is no URL to enter, in Plaza or in Odoo.

Odoo receives the result at:

https://your-odoo-domain/payment/buckaroo_official/webhook

There are two things you do need: push messages switched on for the store in Plaza, and a server that will accept the incoming request.

Enable push messages for your store

Push messages are enabled per store in Buckaroo Plaza, under Settings → Stores → Push settings. Switch them on for the store whose Store key you entered in Odoo.

This is separate from the push URL. The app supplies the URL; what Plaza controls is whether pushes are sent for that store at all. If they aren't, payments will succeed at Buckaroo and your transactions will stay pending, with no push attempts recorded against the transaction in Plaza.

Allow Buckaroo's IP addresses and ports

If your store sits behind a firewall, WAF or IP allowlist, push messages will be blocked and your orders will never leave pending.

Allow inbound traffic from Buckaroo's push addresses on the supported ports. The current list is maintained on the Push messages page. Always take the values from there rather than from a copy, since they can change.

📘

This allowlist is for traffic from Buckaroo to your store. Don't confuse it with traffic in the other direction. The addresses your store sends requests to are dynamic and should not be allowlisted by IP.

Other things that block pushes

Your push endpoint must also be:

  • Publicly reachable over HTTPS with a valid certificate. Self-signed certificates will fail.
  • Not behind basic authentication. Staging environments protected with HTTP auth will reject pushes.
  • Returning HTTP 200. Buckaroo treats any other status code as a failed push.

Retries

If a push fails, Buckaroo retries automatically over a period of hours, and keeps trying for up to three days before giving up. See Push messages for the exact schedule.

What this means in practice: a firewall rule fixed the same day will usually let orders reconcile themselves without any manual work. It's a generous window, but not unlimited, so don't leave a broken endpoint over a long weekend.

Plaza can optionally email you when pushes fail, under Settings → Stores → Push settings → E-mail push failure. Bear in mind it warns on the first failed attempt, so a push that fails once and succeeds on retry still triggers an email. On a busy store that adds up, so it suits a launch period or an active investigation better than permanent use.


Test the connection

Place a test order using Wero with the provider in test mode and choose the "success" outcome on the test page. Within a few seconds the transaction in Odoo should move to Done. If it doesn't:

  1. Check the Logs tab in Buckaroo Plaza for the transaction. It shows every push attempt and any error returned by your server, which usually identifies the problem immediately. No push attempts at all usually means push messages aren't enabled for that store.
  2. Check the Odoo server log. The app logs the full push payload it receives, so if nothing is logged the request never arrived.

If Plaza shows the push failing with a connection error or timeout, it's a firewall or network problem. If Plaza shows the push succeeding but Odoo didn't act on it, it's a signature or configuration problem, most often a Secret key mismatch. See Troubleshooting.

📘

You can resend a push manually from Plaza: open the transaction and use Actions. To resend many at once, use Transactions → Overview → Filters → Actions → Bulk Push. This is how you recover a batch of orders after fixing a blocked firewall.


Did this page help you?