FAQ

No. The plugin is free and open source. You pay Buckaroo's transaction fees on the payments you process. Licence details are on the GitHub repository.

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

Composer is the recommended method, and the one these docs cover. Manual installation is possible but makes upgrades considerably harder to manage.

Yes. Magento Open Source, Adobe Commerce and Adobe Commerce Cloud are all supported.

Yes, with an additional module. There are two: one for Hyvä Checkout and one for Hyvä React Checkout. Additional modules explains which you need.

No. Both are features of the plugin. Enable them under Stores → Configuration → Sales → Buckaroo. See Built-in features.

Yes, via the GraphQL module. Headless and GraphQL covers how to build against it.

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

Yes. Each method has allowed-countries and customer-group settings, and all configuration can be scoped per store view.

Yes. Each method has a Payment Fee setting, and the tax class applied to fees is set under the plugin's General Settings. See Payment methods.

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. These are the two current options for cards; Hosted Fields has replaced the older Client Side Encryption method.

No. The plugin sends the correct push URL with every transaction request, which overrides anything set in Plaza. You only need to make sure Buckaroo's IP addresses can reach your server. See Connect your Buckaroo account.

Refund from Magento wherever you can. It creates the credit memo and returns stock at the same time, and keeps Magento as your source of truth. If you do refund in Plaza, record it in Magento afterwards as an offline credit memo. Never refund the same order in both systems, or you risk refunding the customer twice.

Yes, for most methods. Create a credit memo for the specific items or amount.

Refund sends the refund to Buckaroo and the customer gets their money back. Refund Offline only records a credit memo in Magento and moves no money.

At invoice. Creating the invoice in Magento triggers the capture. Until then the amount is reserved but not taken. Authorisations expire, so capture as soon as you can ship.

Yes. The Store key can be set per store view. The Secret key is account-level and shared.

No. Mode is set per payment method, and each can be Off, Test or Live. Check every method before going live.

Yes. Second Chance and other scheduled tasks depend on it.

Apply patch releases promptly and review minor releases as they come. There's no fixed schedule you have to follow, but the plugin targets the three most recent Magento releases, so if you're planning a Magento upgrade, check plugin compatibility first. See Releases and upgrading.

We aim to support the three most recent Magento releases, currently 2.4.7, 2.4.8 and 2.4.9. As Adobe ships a new version, the window moves forward and the oldest drops off. Older versions may still work, but aren't guaranteed or tested against new payment methods.

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 Adobe's module best practices. If the change would benefit other merchants, consider opening a feature request on GitHub instead.

Privately, following SECURITY.md. Please don't open a public GitHub issue.