The Balance Platform sends notifications to communicate events such as payments and fund transfers. You receive these notifications through webhooks.
Since many of the events on the Balance Platform are asynchronous, handling webhooks is required for a successful integration.
The Balance Platform notifications return a different JSON object from the Adyen payments notification. If you want to reuse an existing endpoint, make sure the endpoint is able to handle the new notification structure.
To process webhooks from the Balance Platform, you need to:
Step 1. Configure a webhook endpoint
You will need to expose an endpoint that:
- Can receive a JSON object.
- Has an open TCP port for HTTPS traffic on port 443, 8443, or 8843.
- Can handle basic authentication.
Once you have an endpoint ready, reach out to your Adyen contact to configure the endpoint within the Adyen platform. We will provide a shared secret that you will use to validate HMAC signatures.
Step 2: Accept notifications
To ensure that your server is properly accepting notifications, we require you to acknowledge every notification of any type with an
If we don't receive this response within 10 seconds, for example because your server is down, all notifications to your endpoint will be queued and retried.
When your server receives a webhook:
- Verify the HMAC signature included in the notification.
This is to confirm that the notification was sent by Adyen, and was not modified during transmission.
- Store the notification in your database.
- Acknowledge the notification with the following response:
All notifications in the Balance Platform are about payments or fund transfers.
You can determine the notification by the
type, such as balancePlatform.payment.created.
Here is an example notification for an authorised payment: