FAQ

No. The plugin is free and open source. You pay Buckaroo's transaction fees on the payments you process. It's available from the WordPress plugin directory and GitHub.

You can install the plugin without one, but you need an account and API keys to process any transaction, including test transactions. Request an account. You can start testing while your application is reviewed.

WordPress 5.3.18 to 7.0, WooCommerce 5.0 to 11.0, and PHP 8.0 or higher. See Releases and upgrading.

Yes. The plugin supports both the classic checkout and the Cart & Checkout Blocks, and declares that compatibility to WooCommerce so it isn't listed as an incompatible extension. There's nothing to switch on.

Yes. Order data goes through the WooCommerce order API rather than post meta. If you switch an existing store to HPOS, the plugin migrates its older order data in the background automatically.

Yes. Use Auto-configure on the General Settings page. It reads which methods are active on your Buckaroo contract and enables the matching ones for you, in Live mode. See Connect your Buckaroo account.

Contact your account manager or Buckaroo support. Some methods, such as PayPal and the Buy Now Pay Later providers, require separate onboarding with the provider.

Yes. Each method has a Payment fee setting that takes a fixed amount or a percentage. The tax class applied to fees, and whether the fee shows including or excluding VAT, are set once under Configuration.

Pay by Bank is the exception; it doesn't support fees.

Whether you're allowed to charge a fee, and how much, depends on the payment method and the rules that apply to your business. That's yours to check.

Yes. Each method has a minimum and maximum order amount. Zero or empty means no limit. Riverty additionally has separate limits for B2B orders.

Yes. The Credit and debit cards method has a Show separate in checkout setting that promotes chosen brands to their own entry in the payment list. Use it for brands that carry recognition in your market rather than for all of them.

Not with Hosted Fields or the redirect flow. In both cases card data goes directly to Buckaroo and never touches your server, which keeps you out of the heavier PCI scope. Hosted Fields does require HTTPS on your checkout.

Yes, with iDIN, which verifies identity and age through the customer's own bank. You can limit it to specific product categories so only age-restricted orders trigger it. See Configuration.

No. The plugin sends the correct push URL with every transaction request, which overrides anything set in Plaza, so there is no URL to enter anywhere.

Two things do need doing: enable push messages for your store in Plaza under Settings → Stores → Push settings, and make sure Buckaroo's IP addresses can reach your server. See Connect your Buckaroo account.

Refund from WooCommerce wherever you can, using Refund via Buckaroo on the order screen. It records the refund against the order and its line items and keeps WooCommerce as your source of truth.

If you do refund in Plaza, record it in WooCommerce afterwards as a manual refund. Never refund the same order in both systems, or you risk refunding the customer twice.

Refund via Buckaroo sends the refund to Buckaroo and the customer gets their money back. A manual refund only records it in WooCommerce and moves no money.

Yes, for most methods. Refund specific line items or a custom amount, and repeat until the original transaction total is used up.

When you capture, from the order screen. Until then the amount is reserved but not taken. Authorisations expire, so capture as soon as you can ship.

Yes. Create the order in the WordPress admin, then use the PayPerEmail or PayLink action on the order screen. PayPerEmail has Buckaroo email the link; PayLink gives you a link to send yourself. See Order management.

Because the payment method was in Test mode when the order was placed, so no real money moved. The warning exists so nobody ships it by mistake. Mode is set per method, so check them all.

No. Mode is set per payment method, and each can be Test or Live. That lets you go live with one method while still testing another, but it means you must check every method before launch. The Payment Methods list shows the status of each one.

By default it follows the customer's browser language, falling back to English. You can force it to English, Dutch, French or German instead under Configuration.

Dutch, German, French and Spanish, alongside English.

Under Buckaroo Settings → Reports, without needing server access. Switch on Debug mode under Advanced Settings first, and switch it off again when you're done. Entries are pruned after 14 days.

Apply patch releases promptly and review minor releases as they come. Check plugin compatibility before you upgrade WooCommerce itself, not after. See Releases and upgrading.

Yes, for merchants with a Buckaroo account. Contact [email protected] or +31 (0)30 711 50 50.

It's open source, so yes, though customisation makes upgrades harder to manage. Keep a record of your changes and follow WordPress's guidance on extending plugins rather than editing them in place. If the change would benefit other merchants, consider opening a feature request on GitHub instead.

Privately, to [email protected], rather than in a public GitHub issue.