Troubleshooting

Buckaroo checks the pair before the connection is saved, so a refusal means the pair was not accepted rather than that something is wrong in Zapier.

• Check for whitespace copied along with either key. This is the most common cause.
• Confirm the store key belongs to the store you intend to charge against.
• If your secret key was regenerated in Plaza, any connection using the old one stops working. Reconnect with the current key.

Check the action's output in the Zap history. If the step succeeded, the link is in its output and the problem is in the step that delivers it, not in the Buckaroo step.

A common cause is mapping the wrong output field into the email or SMS step. Map the field containing the redirect URL, and send a test to yourself before turning the Zap on.

This is expected if you have not built anything to receive the result. The app has no triggers, so nothing in Zapier is watching for payments on its own.

Buckaroo does not host a push endpoint, so nothing receives the result until you provide somewhere for it to go. Set the Push URL to a Zapier Webhooks catch hook and build a second Zap that starts from it, or point it at an endpoint on your own site. See Reacting to payment status.

If you already did this and still receive nothing, confirm the Push URL is publicly reachable and accepts a POST request. See Push messages.

A push message is sent for failed and cancelled payments too. If your second Zap treats every incoming push message as a success, unpaid orders will be marked paid.

Add a filter that reads the status in the push message and only continues on a successful status. See Status.

Check in this order:

1. The method is active on your Buckaroo store in Plaza. Some methods need a contract with the provider first.
2. The method is selected in the Payment Methods field of the action.
3. The method supports the currency in Amount currency. A method that does not support the currency is removed from the page without an error.

See Payment methods.

The action is still in test mode. Test mode is set per action rather than per connection, so a Zap can be live while its Buckaroo step is not.

Open the action, switch Test mode off, and run a small real payment to confirm before relying on it.

The reverse of the previous problem. Test mode is off on an action you are still testing. Switch it on, and check any other Zaps you built by copying this one, since the field is copied with the step.

Return URL and Push URL must both be complete URLs including the scheme, so https://example.com/push rather than a bare host or a path on its own. Both are required, and a malformed value fails the step rather than creating a link without it.

The amount must be a plain number of zero or higher. Values carrying a currency symbol, a thousand separator or trailing characters are rejected.

If the amount is mapped from another app, check what that app actually sends. A field displayed as 1.250,00 in a spreadsheet is often not a plain number underneath, and needs a Zapier formatting step before it reaches Buckaroo.

The Order and Invoice fields are almost certainly set to fixed text rather than mapped from the trigger. Map them from the trigger step so each payment carries its own reference.

Arriving at the Return URL does not mean a payment succeeded. Customers abandon payments, close browsers and lose connections after being redirected.

Treat the push message as the only reliable result. See Redirects.