Bot intelligence record
WorldPay
Usually allowWorldPay is a webhook callback used for webhook delivery, payment notifications, service callbacks; it appears in server logs as `WJHRO/1.0`.
User-Agent Pattern
WorldPayWJHRO/1.0
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: WJHRO/1.0
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.
WorldPay is used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
Record Details
Structured data- Operator
- WorldPay
- Family
- WorldPay
- Type
- Webhook
- Purpose
- Webhook
- Identity type
- Observed
- Confidence
- Low
- Last verified
- 2026-04-01
- Last checked
- 2026-06-23
- Source type
- Observed
- Verification
- Verify WorldPay by matching `WJHRO/1.0` to observed traffic patterns and user-agent evidence, then checking reverse DNS, IP ownership, request behavior, and crawl consistency.
- Spoofing risk
- WorldPay has high spoofing risk because the pattern is low-confidence or observation-based; do not trust the user-agent by itself.
Notes
- WorldPay is a webhook callback used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
- Its primary user-agent pattern is
WJHRO/1.0; a representative HTTP user-agent isWJHRO/1.0 (WorldPay Java HTTP Request Object). - WorldPay is not independently verified with Low confidence. The identity type is Observed, and the evidence basis is observed traffic patterns and user-agent evidence.
- WorldPay does not have confirmed robots.txt behavior in the available public evidence.
- WorldPay can usually be allowed after confirming the source and monitoring request volume.
Evidence and Source
- Verify WorldPay by matching `WJHRO/1.0` to observed traffic patterns and user-agent evidence, then checking reverse DNS, IP ownership, request behavior, and crawl consistency.
- WorldPay traffic is primarily detected by the `WJHRO/1.0` user-agent pattern; a representative HTTP user-agent is `WJHRO/1.0 (WorldPay Java HTTP Request Object)`. Compare source IPs, reverse DNS, request paths, and crawl cadence before trusting the traffic.
- WorldPay is used for webhook delivery, payment notifications, service callbacks, and server-to-server integration events.
- WorldPay has high spoofing risk because the pattern is low-confidence or observation-based; do not trust the user-agent by itself.
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.