Promptwatch Logo

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.
Adyen
Webhook

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.

Not relevant for AI search

Is Adyen Webhook relevant for AI search?

No. Adyen Webhook is not part of AI search or training, so allowing or blocking it does not change your AI visibility.

Adyen Webhook is not a crawler. It delivers webhook notifications to endpoints you registered, so it never fetches public content for an AI product. Robots.txt does not apply, and allowing or blocking it has no effect on AI search or training.

How to handle Adyen Webhook

Keep the configured endpoint public, direct, and available if Adyen events drive payment state. Require the OAuth 2.0 or Basic authentication selected in the Customer Area, then verify the event's HMAC with the matching test or live key. Use Adyen's validator library where available because Standard and non-Standard webhook types place the signature in different locations.

Reject an event that fails authentication or HMAC verification. For a valid event, save it to a queue or database, return 200 or 202 within 10 seconds, and process it idempotently afterward. Account for duplicate events and use the latest event details when Adyen sends more than one update for the same payment.

If the integration has ended, disable the webhook in the Adyen Customer Area before closing the route. Do not create a robots.txt rule for it, and do not use a guessed user-agent string as evidence that a payment event is genuine.

Examples

  • An `AUTHORISATION` event reaches a merchant after checkout, and the receiver verifies its `additionalData.hmacSignature` before updating the order.
  • A chargeback notification is stored and acknowledged with 202, then a separate worker opens the merchant's dispute workflow.
  • A non-Standard webhook arrives with `hmacsignature` and `protocol` headers, so the receiver verifies the raw body rather than applying the Standard field algorithm.
  • The endpoint misses Adyen's acknowledgment window, and a later retry is ignored because the `eventCode` and `pspReference` were already recorded.

Frequently asked questions about Adyen Webhook

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

Standard webhooks include `hmacSignature` in `additionalData`. Some other webhook types put it in the `hmacsignature` request header.

Be the brand AI recommends

Monitor your brand's visibility across ChatGPT, Claude, Perplexity, and Gemini. Get actionable insights and create content that gets cited by AI search engines.

Promptwatch Dashboard