Search

Are you looking for test card numbers?

Would you like to contact support?

Issuin icon

Payment stages

Learn about the payment stages and when funds are added to or deducted from the balance account.

Each payment on the Balance Platform goes through a series of events. Most of the events are triggered by the processing merchant, the business that processed the card payment. These events then result to funds being deducted from or added to the balance account. We inform you of these events through notification webhooks.

This page provides information about payment stages and how these affect funds in the balance account. When you're already familiar with payment stages, you can refer to Payment-related events for specific webhook types and examples.

Authorisation

When a user pays with an Adyen-issued card, the processing merchant sends a payment authorisation request to the card issuer (Adyen). Adyen approves or declines the payment based on your relayed authorisation decision, the outcome of transaction rules, and other validations. Adyen triggers a balancePlatform.payment.created webhook to inform your server of the payment authorisation request and of the result.

When the payment is approved and authorised, the payment amount is reserved but not yet deducted from the balance account. When you check the balance account details, the payment amount is reflected as a reserved amount.

The processing merchant can then proceed to capture the payment, cancel the payment, or let the authorisation expire.

Authorisation expired

A payment authorisation expires when the processing merchant fails to capture the payment after the set expiry period. In your balance account, the previously reserved amount is added back to the available amount.

Adyen triggers a balancePlatform.payment.updated webhook to inform your server of this event.

Authorisation cancelled

The processing merchant can still cancel a payment authorisation as long as the funds have not been captured. In your balance account, the previously reserved amount is added back to the available amount.

Adyen triggers a balancePlatform.payment.updated webhook to inform your server of this event.

Captures

The processing merchant can capture the authorised amount in full or in parts (partial captures). This is when the authorised amount is deducted from the balance account. In case of partial captures, the remaining authorised amount can still expire or be cancelled because it hasn't been captured yet.

In your balance account, the payment amount previously reflected as a reserved amount is now deducted from the balance.

Adyen triggers a balancePlatform.outgoingTransfer.created webhook to inform your server of this event. In case of multiple partial captures, Adyen also sends multiple webhooks—one for each capture request.

Refunds

Refunds can only occur when the funds have already settled to the processing merchant, and the card user asks to get their funds back. When the processing merchant initiates a refund, they can request for the full captured amount or for a part of the captured amount (partial refunds).

Adyen triggers a balancePlatform.payment.created webhook to inform your server of the refund request.

Pending refund

The refund has been processed but the funds have not yet settled to the balance account.

Adyen triggers a balancePlatform.incomingTransfer.created webhook to inform your server of the pending refund.

Refunded

Adyen has received the funds and the funds have settled to the balance account. The refunded amount is added to the balance amount.

Adyen triggers a balancePlatform.incomingTransfer.updated webhook to inform your server of the completed refund.

Next steps