Bot intelligence record
Adyen
Usually allowAdyen is a webhook callback used for webhook delivery, payment notifications, service callbacks; it appears in server logs as `Adyen`.
User-Agent Pattern
AdyenAdyen
User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.
Robots.txt Snippet
Click snippet to copyUser-agent: Adyen
Disallow: /Click the snippet to copy it, or highlight the text manually.
Handling Guidance
NoThis bot is usually safe to allow when the request source is verified and the traffic matches your site policy.
Adyen is used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
Record Details
Structured data- Operator
- Adyen
- Family
- Adyen
- Type
- Webhook
- Purpose
- Webhook
- Identity type
- Verified Bot
- Confidence
- Medium
- Last verified
- 2026-04-01
- Last checked
- 2026-06-23
- Source type
- Documented
- Verification
- Verify Adyen by matching `Adyen` to documented crawler-pattern evidence, then checking reverse DNS, IP ownership, request behavior, and crawl consistency.
- Spoofing risk
- Adyen has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Notes
- Adyen is a webhook callback used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
- Its primary user-agent pattern is
Adyen; a representative HTTP user-agent isAdyen HttpClient 1.0. - Adyen is verified with Medium confidence. The identity type is Verified Bot, and the evidence basis is documented crawler-pattern evidence.
- Adyen does not have confirmed robots.txt behavior in the available public evidence.
- Adyen can usually be allowed after confirming the source and monitoring request volume.
Evidence and Source
- Verify Adyen by matching `Adyen` to documented crawler-pattern evidence, then checking reverse DNS, IP ownership, request behavior, and crawl consistency.
- Adyen traffic is primarily detected by the `Adyen` user-agent pattern; a representative HTTP user-agent is `Adyen HttpClient 1.0`. Compare source IPs, reverse DNS, request paths, and crawl cadence before trusting the traffic.
- Adyen is used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
- Adyen has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, identify related datacenter activity, and create allow, block, rate-limit, or log rules across connected sites.