Troubleshooting

Most problems come down to one of four things: the sales channel you are looking at, a method left in test, a method not assigned to the channel, or a push message not reaching your store. Work through the symptoms below before contacting support.


Buckaroo status

If something stopped working and nothing changed on your side, check the Buckaroo status page first. An ongoing incident explains most sudden problems, and there is nothing to fix on your side.

Buckaroo Status

Loading status…

Common problems

The credentials test fails
  • Check for whitespace copied along with either key. This is the most common cause by a wide margin.
  • Confirm you are on the right sales channel. Credentials are saved per channel.
  • Confirm the store key belongs to the store you intend to charge against.
  • If the secret key was regenerated in Plaza, the old one stopped working. Paste the current one.
A payment method does not appear at checkout

Check in this order:

  1. The method is enabled on the sales channel you are testing.
  2. The method is assigned to that sales channel under Sales Channels. Shopware will not offer an unassigned method, however the extension is configured.
  3. The method is active on your Buckaroo account, since some methods need a contract with the provider first.
  4. Your cart meets any conditions the method has, such as a supported currency or country.
Everything works on one sales channel but not another

Configuration is per sales channel, and the channel selector at the top of the configuration screen is easy to overlook. Credentials, method settings, fees and express buttons are all saved against whichever channel was selected when you pressed save.

Select the other channel and check its settings rather than assuming they were inherited.

A method takes no real money

It is still in Test. A newly enabled method defaults to Test, and it appears at checkout and completes normally in that state, so nothing tells you unless you look for the payment.

Switch the method to Live, on each sales channel that offers it. See Test and go live.

Payments succeed but orders stay unpaid

Order states are driven by the push message from Buckaroo, so this usually means the push is not arriving.

Confirm your store is reachable from the internet. A local environment, a staging site behind a password, or a firewall will all produce exactly this. Buckaroo sends push messages from fixed addresses and ports, so check those are allowed. The current list is on the push messages page.

Bank Transfer is the exception and not a fault: those orders wait until the money actually arrives.

An order is authorised but no money arrived

Authorising reserves money rather than collecting it, so an authorised order needs capturing. Riverty, Billink and Wero each have an authorise option, and Klarna reserves by design.

Capture from the Buckaroo panel on the order, or enable capture on shipment for the method. See Order management.

Capture on shipment is not firing

It depends on the delivery state being updated in Shopware. If you mark orders as shipped outside Shopware, or through an integration that does not update the delivery state, nothing triggers the capture.

Capture manually from the Buckaroo panel, and check whatever updates your deliveries.

A refund did not reach the customer

Refund from the Buckaroo panel on the order rather than through Shopware's own refund handling. Shopware's own actions update your administration without telling Buckaroo, so no money moves.

Check the transactions list in the Buckaroo panel to see whether a refund was actually sent, and check Plaza if you are unsure.

The Apple Pay button does not appear

Three things to check. Your Buckaroo Guid is filled in, from My Buckaroo → General in Plaza. The button is switched on for the page you are looking at, since product, cart and checkout are separate settings and all default to off. And you are testing on a device and browser that support Apple Pay, which is the usual answer.

See Express checkout.

The Google Pay button does not appear

Check that the button is switched on for the page you are looking at, since product, cart and checkout are separate settings and all default to off.

Then check both merchant identifiers are filled in. Leaving the Buckaroo Gateway Merchant ID empty makes the extension fall back to your store key, which can make Google Pay look configured when it is not.

As with Apple Pay, the button only appears in a browser that supports Google Pay. See Express checkout.

PayPal Express is using the wrong account

There are two merchant ID fields, one live and one for the sandbox. The sandbox one is used when the method is in test mode, so a method switched to Live with only a sandbox ID filled in will not work as expected. Check both.

Customers see two card options at checkout

Both card cards are enabled. Pick one and disable the other, and note they behave differently rather than being two presentations of the same thing. See Payment methods.

Card payments redirect the customer away from my checkout

You are using Credit and debit cards, which lists schemes separately and takes the customer away to pay. Keeping card entry in your checkout means using Grouped cards, which is the Hosted Fields option.

If grouped cards is already enabled and customers are still leaving, check that its client ID and client secret are filled in. See Hosted Fields.

Something broke after an upgrade

Clear the cache with bin/console cache:clear, then check the release notes for the version you moved to. See Releases.

There is no administration rebuild step for this extension, so a stale administration is not the cause.

Didn't solve it? Contact support

Have your Shopware version, your PHP version, the order number, the sales channel and the relevant log lines ready. If a payment was attempted, the transaction key from Plaza will speed things up considerably.


Did this page help you?