FAQ

The extension is free to install and use. Your Buckaroo agreement covers what you pay for processing payments.

The supported Shopware, PHP and Composer versions are listed on the repository and with each release, since they change as new versions arrive.

Composer is recommended, because updating becomes a single command. The Store route works if you would rather not use the command line. See Installation.

No. The extension ships pre-built administration assets, so there is no build command to run.

That depends which card method you enabled. Grouped cards uses Hosted Fields, so details are entered in your own checkout. Credit and debit cards takes the customer away to complete the payment. Other methods redirect where the method itself requires it. See Payment methods.

Usually because it has not been assigned to that sales channel under Sales Channels. Shopware will not offer an unassigned method however the extension is configured. See Troubleshooting.

Yes. Credentials, method settings, fees and express buttons are all saved per sales channel. This is useful when channels should behave differently, and it is the most common cause of something working in one place and not another.

Yes, as a fixed amount or a percentage, set per method. Check that a surcharge is permitted for the methods you use before switching this on. See Payment methods.

Grouped cards is the Hosted Fields option: one card field in your own checkout, with the scheme detected from the number, and it needs a client ID and client secret. Credit and debit cards lists each scheme separately and takes the customer away to pay. Enable one, not both.

Yes, from the Buckaroo panel on the order: the grand total, a custom amount, or selected line items. Use that panel rather than Shopware's own refund handling, which updates your administration without telling Buckaroo. See Order management.

Yes, up to the amount originally paid.

The money is reserved rather than collected. Nothing reaches your account until the payment is captured, either manually from the order or automatically when you mark the delivery as shipped. An authorised order is not a paid order.

Yes. Create paylink in the Buckaroo panel produces a link for that order, which suits phone orders or a payment that failed the first time.

It follows the language setting, which defaults to the customer's browser language. You can also base it on their billing country, use the sales channel default, or fix it to one language. See Configuration.

Yes, for Apple Pay, Google Pay and PayPal Express. Each can appear on the product, cart and checkout pages, and every placement is off by default. See Express checkout.

Most often because the browser or device does not support Apple Pay. Otherwise, check your Buckaroo Guid is filled in and that the button is switched on for the page you are looking at.

No. Updating the extension keeps your configuration. Uninstalling is different, and removes it.

No. The extension handles this. Your store does need to be reachable from the internet, and if it sits behind a firewall, Buckaroo's push addresses need to be allowed. See Push messages.

As an issue on the GitHub repository, with your Shopware, extension and PHP versions plus the relevant log lines. For anything affecting live payments, contact support instead. See Contact us.