When a top-up is triggered in your platform, Adyen sends two kinds of webhooks:
- Standard webhooks, which inform your server of a direct debit from your merchant account. When the sweep triggers a direct debit, Adyen sends an AUTHORISATION webhook to your server.
- Transfer webhooks, which inform your server that an incoming transfer to a balance account in your platform.
To keep track of events related to top-ups in your platform, make sure that:
- Your server can receive and accept webhooks.
- You subscribed to the Transfer webhooks in your Balance Platform Customer Area.
You can identify transfer webhooks triggered by events related to top-ups by the following values:
| Parameter | Description | Value |
|---|---|---|
| category | Specifies the category of the transfer. | platformPayment |
| direction | The direction of the transfer based on the balance account. | incoming |
| type | Specifies the type of the transfer. | capture |
Top-up initiated
When an incoming transfer request is received to credit funds to your user's balance account, Adyen sends a balancePlatform.transfer.created webhook with status received and direction incoming. The webhook provides information about the transfer, such as the amount and which user and balance account is credited with the funds.
Top-up authorised
When the incoming transfer request is authorised, Adyen sends a balancePlatform.transfer.updated webhook with status authorised.
Top-up captured
When the funds are credited to your user's balance account, Adyen sends a balancePlatform.transfer.updated webhook with status captured and the transactionId.