Webhooks

Webhook notifications allow you to efficiently track payments states, and enable you to automate communication internally or with your customers. They are push notifications sent as webhook message to URLs you define. We do not recommend using webhooks as a replacement for reconciliation purposes, here we refer you to our Reconciliation report.

You can subscribe to several payment events. When one of these events is triggered, we send a HTTP POST request to a URL of your choice in a JSON format. Along with the event, data about the payment is included, which we refer to as the payload.

📘

Webhook SLA

Our webhook capabilities guarantee a 100% sending rate. However, successful receipt depends on the client endpoint being available and properly configured. If your system is temporarily unavailable or misconfigured, some webhook events may not be received.

Additionally, duplicate events may occur, so we recommend implementing idempotency checks where necessary.

If client-side errors occur, our retry mechanism will automatically attempt to resend the webhook. For more information, please see Webhook retry strategy .

Supported events

These are the payment events for which you can subscribe to. You can refer to the Payment lifecycle for additional context on how payments change from status to another.

Subscriptions and subscription events

Our setup is flexible: you can create one subscription for all (or some) event types or you can create separate subscriptions specific to an event type. You can also setup subscriptions at a company level or on a bank account level. Here are two examples to illustrate the different setups.