# Adyen Webhooks Webhooks are an essential feature of the Adyen platform. They deliver events like payment outcome, new chargebacks, availability of a report, updates on merchant onboarding, and so on, and therefore it is important to ensure they can be received, consumed and tested during the development of your specific Adyen integration. This collection contains several examples of the webhooks delivered by Adyen. ## How to use it ### Fork Fork the collection in your own private workspace ### Config Define the collection variables: - `baseUrl`: url of the webhook handler (i.e localhost:8080) - `path`: path of the webhoon handler (i.e. /api/webhooks/notifications) - `YOUR_MERCHANT_ACCOUNT`: your merchant account (if applicable) - `YOUR_BALANCE_PLATFORM`: your balance platform (if applicable) - `YOUR_LEGAL_ENTITY`: your legal entity (if applicable) - `HMAC_KEY`: HMAC key to sign the payload Ignore the Collection variable `HMAC_SIGNATURE` (it is calculated when sending the request) ### Send Send the requests to your application ## Report an issue Let us know about problems or improvements by creating a [GitHub](https://github.com/adyen/adyen-postman) issue. ## References [Webhooks](https://docs.adyen.com/development-resources/webhooks) on Adyen docs Consuming webhooks [blog](https://www.adyen.com/blog/consuming-webhooks) and [video](https://www.youtube.com/watch?v=pwR4A4KLVuI&t=447s)

Versori has established itself as the third generation of Integration Platform as a Service (iPaaS). Versori builds custom integrations for its customers using an intuitive visual user interface.

Versori’s connector engine means there is no dependency on an existing library of apps, all you need to start is the documentation of the app or system you want to integrate to.