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 webhooks?

Make sure you have registered the correct webhooks and events for your sales unit(s).

If we do not get the expected response for a webhook, that webhook will be retried. Subsequent webhooks will not be sent until we have received a success response.

Example: You have captured a payment, and then immediately cancelled it. If we send a webhook for the POST:/epayment/v1/payments/{reference}/capture, but do not receive a success response, we will not send the webhook for the POST:/epayment/v1/payments/{reference}/cancel for the same payment until we have received a success response for the first (capture) webhook.

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 webhook.


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

What should I do if I don't receive webhooks?

In the rare cases where webhooks may be delayed you should poll the relevant API to get the information you need.

Example: To get the details of a payment made with the ePayment API you can:

Can you manually re-send webhooks?

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 webhook header as Webhook-Id, so you can store and lookup your secret by webhook id.

What happens with my webhooks when there is an outage/downtime?

We will try to replay affected webhooks as quickly as possible, but delays may occur as it depends on the amount and impact of the affected webhooks.

What happens to my event if the webhook is deleted within the 7 days retry window?

This is considered as no valid webhook is present. The retry will terminate permanently for this event, and no webhooks will be sent. This is non-reversible.

Help us improve our documentation

Did you find what you were looking for?