Webhooks

A webhook is a lightweight mechanism that allows an Adyen service to push event-driven messages using HTTP POST calls to an endpoint that you define. You need to accept webhooks that you receive with a 2xx HTTP status code, store the message, and process the contents of the message.

When you configure a subscription to an Adyen webhook, you are requesting to be notified when an event has occurred. With webhooks, you can avoid having to continuously poll an API endpoint, waiting for a change in status for an asynchronous process, or for updates that your account holders make.

Webhooks are great for long-running processes, where a change in a resource or its status may not occur for many seconds, minutes, hours, or days.

In this way, you can make an API call, move on to other processes, and then act upon the status change when you receive a notification from Adyen that an event has occurred.

Why you need to configure webhooks

Should you configure webhooks to integrate with Adyen services? Yes, absolutely.

Webhooks are an essential feature of a successful integration with Adyen. Here are some of the main benefits of using webhooks in your integration.

Handle asynchronous flows

Many flows in Adyen integrations are asynchronous, meaning the final status of a resource is not known immediately after you make an API request. For example, with payment methods like iDEAL, it can take time to get a confirmation that the payment was completed.

Webhooks solve this by sending you a message with the final outcome as soon as it's available. You can also tie payment events to other updates in your backend, such as for order management and inventory control. For example, if a payment is successfully authorized, you can update the order status to "paid" and start the shipping process.

State management

Use webhook notifications to confirm or update the state of a resource in your own system. Some Adyen integrations need to manage several connected resources. For example, an Adyen for Platforms integration requires you to manage account holders and their associated balance accounts, capabilities, and balances. These webhook messages contain a full object snapshot of the resource so your system can update its state accordingly.

React to external events

Some important events come from external systems and are not a direct result of an API request you made. Webhooks are the only way to be automatically notified of these events. For example:

• Onboarding verification: For Adyen for Platform integrations, receive webhook messages as Adyen verifies your users and enables capabilities, or when more information is required to complete verification.
• Dispute management: When a shopper initiates a chargeback, Adyen sends a webhook message. This allows you to start the dispute resolution process immediately by gathering evidence and submitting a defense.
• Report generation: Receive webhook messages when new reports become available, so you can download reports for accounting and reconciliation purposes.
• Relayed authorisation: For integrations using Adyen Issuing, receive a webhook message when cardholder of an Adyen-issued card makes a payment.

For a list of webhook events that Adyen supports, see Webhook structure & types.