Skip to main content

Frequently asked questions

How can I replace a webhook?

To replace a webhook, you can register a new webhook for the same event type: POST:/webhooks/v1/webhooks.

After registration, the new webhook will receive the same traffic as the webhook you want to replace.

You can now verify that the subscription works as expected before deleting the old one with DELETE:/webhooks/v1/webhooks/{id}.

Please note: Do not let an obsolete webhook return an error (like HTTP 404 Not Found), since that may be misclassified a real incident on our side, requiring us to investigate the problem, contact you to find out what goes wrong, etc.

Why don't I get any callbacks?

We require TLS 1.2 for the HTTPS connection to the webhooks you have registered. If you do not support TLS 1.2, we will not be able to establish the connection, and we are unable to send the callback.

Please note: TLS 1.1 was deprecated in RFC 8996 in 2021. See Transport Layer Security for more details.

Can you manually re-send callbacks?

No. The Webhooks API works as documented, and we can not manually override or make special requests.

Are webhooks also sent for manual changes done on


Example: If a payment is manually refunded on, the Webhooks API will make a request exactly as if the refund was done using the ePayment API.

I maintain multiple webhooks that all use the same URL, how can I find the right secret?

We include the id of the source webhook in the callback header as Webhook-Id, so you can store and lookup your secret by webhook id.

Help us improve our documentation

Did you find what you were looking for?