Test Buckaroo payments in Odoo

Verify your integration in test mode, then work through the checklist before you take real payments.

Testing

Enable test mode

The Buckaroo app sets mode on the provider, not per payment method. Open Buckaroo Official and set the state to Test mode. Every enabled method now runs against the Buckaroo test environment.

Select Test Connection to confirm your keys are accepted in that mode.

Test transactions use the same Store key and Secret key as live transactions. Nothing else changes, which is exactly why you need to check every method again before launch.

Use a staging database where you can, especially before an upgrade. Test transactions in your live database leave real orders behind.

Test data

Buckaroo provides test credentials and simulated outcomes for each payment method. See Test transactions for the full set, including test card numbers and how to trigger specific results.

For most redirect methods, the test payment page lets you choose the outcome directly: success, failure, cancellation or pending.

What to test

Test the paths that break, not just the happy path.

Scenario	What you're checking
Successful payment	Transaction reaches Done, payment record created, confirmation email sent
Failed payment	Order is left unpaid and the customer sees a usable error
Customer cancels at the bank	Transaction is cancelled, cart is intact
Customer closes the browser mid-payment	Push still arrives and updates the transaction
Full refund	Credit note posted, refund visible in Plaza
Partial refund	Correct amount refunded, remaining balance still correct
Authorise then capture	Reservation at checkout, capture from the transaction
Cancel an authorisation	Reservation released
Payment fee	Fee line added, correct VAT, replaced when the method changes
Amount limits	Method hidden above and below its range
Guest checkout	Works identically to a logged-in customer
Each language	Correct translations in checkout and on the payment page
Mobile	Especially for wallet and app-based methods

The "customer closes the browser mid-payment" test is the important one. It's the only test that proves your push endpoint works independently of the browser redirect, and broken push is the single most common production problem.

Methods that behave differently

Express checkout

Test on a real device, not just a desktop browser. Apple Pay needs Safari on a supported Apple device; Google Pay needs Chrome with a card saved to the Google account.

Check the button on the product page and in the cart, confirm the delivery methods offered inside the wallet sheet match your delivery settings, and confirm the amount charged matches the order total.

Apple Pay domain verification

If you use inline mode, open this path on your store:

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

It should return a block of text. A 404 means Apple can't verify your domain and the button will not appear.

Buy Now Pay Later

Klarna, In3, Billink and Riverty ask for extra customer details. Test with a contact that has those fields empty, so you see the checkout prompt, and again with a contact that already has them filled in.

Riverty refunds from Odoo must be for the full amount, so test that path rather than assuming a partial refund will work.

Bank Transfer and PayPerEmail

Both leave the transaction pending on purpose. Confirm the order is created, the bank details or the payment link reach the customer, and the transaction moves to done once the payment is completed in the test environment.

Giftcards

Test a giftcard that doesn't cover the order total, so you exercise the partial-payment path: the balance is drawn, the customer is returned to the payment step, and the remainder is paid with another method.

Penny tests

Test mode proves the integration works. It doesn't prove your live configuration works, because live keys, your live contract and settlement are all different things.

Once the provider is set to Enabled, place a real order for the smallest amount you can and pay for it yourself. Do this for every method you're able to use personally, not just one.

For each method, check that:

the transaction reaches Done and the payment record is created
the sale order and invoice look as expected
the transaction appears in Plaza under your live account, with the same amount and status
refunding from the credit note returns the money

Then refund it. You get the amount back minus any transaction fee, which is a small price for knowing the full loop works: payment, push, invoice, refund, settlement.

You won't be able to test everything yourself. Buy Now Pay Later methods, or methods tied to a country where you don't hold an account, will have to rely on test mode. Cover what you can.

Go-live checklist

Run through this before switching the store to live traffic.

Credentials and connection

Live Store key and Secret key entered, and Test Connection succeeds
Push messages are enabled for your store in Plaza, under Settings → Stores → Push settings
Buckaroo's push IPs and ports are allowlisted on your firewall or WAF. See Push messages for the current list
Store is publicly reachable over HTTPS with a valid certificate
Store is not behind basic authentication
Optional: push failure emails in Plaza (Settings → Stores → Push settings → E-mail push failure). Useful for the first days after launch, though it also emails on failures that later succeed on retry

Payment methods

Provider state is Enabled, not Test mode
Every method you intend to offer is added to the provider
Every enabled method is active on your Buckaroo contract
Method-specific onboarding is complete: Apple Pay domain verification, Google Merchant ID, PayPal onboarding, BNPL provider onboarding
Method order matches how your customers actually pay
Titles are translated for every language you serve

Configuration

Transaction description is set and recognisable on a bank statement
Refund description is set and recognisable on a bank statement
Amount limits set as intended
Optional: payment fees, if used, are on the right methods and taxed correctly

Store health

App is on the latest version
buckaroo-sdk is installed in the environment that runs Odoo
Penny tests done for every method you can pay with yourself, including a refund afterwards
Buy Now Pay Later customer fields tested, if you offer BNPL

After go-live

Watch the first day of orders for anything stuck in pending
Confirm settlement appears as expected in Plaza
Optional: subscribe to Buckaroo status updates for incidents and maintenance
Optional: subscribe to app releases on GitHub. Open the repository, select Watch → Custom, tick Releases and save. See Releases and upgrading

Test transactions

Test credentials for every payment method.

Troubleshooting

Something not working as expected?

Order management

Running your shop day to day.