Webhooks

When an internal transfer is triggered between balance accounts in your platform, Adyen sends two kinds of webhooks:

• balancePlatform.transfer.created, which informs your server that funds will be transferred between balance accounts in your platform.
• balancePlatform.transfer.updated, which informs your server of the transfer status changes.

We send these webhooks for both (source and target) balance accounts involved in the transfer.

To keep track of internal transfer-related events 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 internal transfer events by the following values:

Parameter	Description	Value
category	Specifies the category of the transfer.	internal
direction	The direction of the transfer based on the balance account.	Source account: outgoing Target account: incoming
type	Specifies the type of the transfer.	internalTransfer

The following sections contain examples of the webhooks you would receive for the following transfer request:

Internal transfer initiated

After a scheduled or manual transfer is triggered, Adyen sends a balancePlatform.transfer.created webhook to inform your server that funds will be transferred between balance accounts in your platform. The webhook provides information about the transfer, such as the amount, the transfer and beneficiary references, information on the account holder involved in the transfer, and which are the source and target balance accounts.

Internal transfer authorised

When the internal transfer is authorised, Adyen sends a balancePlatform.transfer.updated webhooks to inform your server that the transfer amount has been reserved on the balance accounts.

Internal transfer booked

When the funds are booked, Adyen sends balancePlatform.transfer.updated webhooks with status booked and the transactionId for both balance accounts.