What is Adyen Webhook?
Adyen sends HTTP POST webhooks for events that a payment integration cannot safely infer from a browser return or an immediate API response. Standard webhooks cover payment state changes, while other webhook families report events for platforms, disputes, reports, or issuing. The endpoint and subscriptions are configured in the Adyen Customer Area.
Endpoint authentication and message integrity are separate checks. Adyen supports OAuth 2.0 for supported webhook types and Basic authentication over HTTPS. It also recommends HMAC verification. Standard webhooks put hmacSignature in additionalData; some other webhook types send the signature in the hmacsignature header and identify the algorithm in protocol.
A receiver verifies the event, stores it durably, and returns a 200 or 202 response within 10 seconds. Adyen places unacknowledged events in its retry queue. Business processing should happen after acknowledgment, and duplicate handling should use the event details such as eventCode and pspReference rather than assuming one delivery.
Adyen Webhook is a payment-system callback to a URL the merchant configured. Public page content is outside this workflow, so the request has no AI search or training effect. Robots.txt is not consulted for webhook delivery.
