How do I set up webhooks?

Why are webhooks useful?

Using webhooks keeps you updated and lets you automate order management or report downloads.

Webhooks update you on:

• Payment statuses changes
• Events such as chargebacks
• New available reports

How webhooks work

Webhooks are sent as HTTP callbacks. For a successful integration, your endpoint needs to respond:

• within 10 seconds to our request.
• with [accepted].
• with 200 as a status code.

Whenever your endpoint fails to respond with the above criteria, it’ll enter Troubleshoot mode and all notifications to this endpoint will be queued. The first notification stuck in the queue will be retried following these time intervals:

• 2 minutes
• 5 minutes
• 10 minutes
• 15 minutes
• 30 minutes
• 1 hour
• 2 hours
• 4 hours

Once the first webhook get’s the accepted response back from your server, all stuck notifications will be released.

Event codes

Webhooks are split up in different event codes, which you can turn on or off from your Customer Area when configuring the specific endpoint. Each webhook event contains an eventCode specifying which type of event triggered the webhook (eg. AUTHORISATION).

In Standard events, default event codes are turned on without additional configuration. Non-default event codes are turned off by default and require additional configuration by either you or support.

Tip: View which event codes are enabled by default when you set up a standard webhooks entry.

Tip: To process and accept events follow our webhooks guide.