Webhooks

Webhook notifications allow you to efficiently track payments states, and enable you to automate communication internally or with your customers

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.

🚧

Limitations

Due to nature of the webhook technology, we cannot guarantee delivery for every event, nor that duplicate events may not occur.

Supported events

These are the payment events for which you can subscribe to.

EventDescription
IncomingPaymentProcessedOne of your accounts is successfully funded (this also includes internal credit transfers)
OutgoingPaymentRejectedOne of your outgoing payments is rejected
OutgoingPaymentProcessedOne of your outgoing payments is successfully processed (this also includes internal debit transfers)
MissingFundingOne of your outgoing payments cannot be executed due to insufficient balance. The payment will be automatically executed when there are sufficient funds, or rejected after 2 days
ReversedOne of your outgoing payments is reversed

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.

Example where multiple event types covering one company are subscribed to a single URL

Example where multiple event types covering one company are subscribed to a single URL

Example where each event type covering a subset of bank accounts is subscribed to a unique URL

Example where each event type covering a subset of bank accounts is subscribed to a unique URL