WorldPay is a bot in the webhook senders category, operated by WorldPay.
Payment confirmation callbacks to ecommerce backends
Webhook senders call your endpoints to deliver events from payment, messaging and SaaS platforms. Blocking them breaks integrations. Allow them on the webhook paths they need and nowhere else.
WorldPay identifies itself with this user agent string:
WJHRO/1.0 (WorldPay Java HTTP Request Object)Anyone can copy a user agent string. Transfon Security also checks where each request comes from, so a request that claims to be a known crawler but comes from the wrong network is treated as a fake, not as the real crawler.
We have not confirmed whether WorldPay follows robots.txt. Add a rule, then check your logs to see that it stopped. robots.txt is a plain text file at the root of your domain, such as https://example.com/robots.txt.
User-agent: WJHRO Disallow: /
User-agent: WJHRO Disallow: /private/ Disallow: /search
User-agent: WJHRO Allow: /blog/ Disallow: /
User-agent: WJHRO Allow: / User-agent: * Disallow: /
User-agent: WJHRO group, WorldPay ignores your User-agent: * rules, so repeat any that should still apply.WJHRO from WorldPay's user agent; check WorldPay's own documentation if it publishes a different robots.txt name.Treat robots.txt as a statement of your policy, and enforce it where requests arrive.
Allow WorldPay if it is a service you use, and keep its visits out of page views and ad requests either way.
Transfon Security for publishersWorldPay is not a person. Exclude it from campaign and conversion data so reports reflect real visitors.
Transfon Security for advertisersAllow WorldPay only if it works for your store, and keep it away from cart and checkout.
Transfon Security for e-commerceIf WorldPay is a service you use, allow it on the endpoints it needs and block it elsewhere.
Transfon Security for SaaS and APIsrobots.txt is a request, not an enforcement. Transfon Security shows WorldPay by name in the Top Bots report, so you can see how often it visits and which pages it reads. Block or allow it with a User Agent rule, or slow it down with a rate limit decision rule.
Transfon Security
WorldPay is a bot in the webhook senders category, operated by WorldPay. Payment confirmation callbacks to ecommerce backends
We have not confirmed whether WorldPay follows robots.txt. Add a robots.txt rule, then check your logs to see that it stopped, and block it by user agent if it did not.
Add "User-agent: WJHRO" followed by "Disallow: /" to the robots.txt file at the root of your site. To enforce it, block requests whose user agent contains "WJHRO/" at your WAF. In Transfon Security that is one User Agent block rule.
No. robots.txt is voluntary, so WorldPay may not follow it, and anyone can send WorldPay's user agent, so a fake WorldPay ignores your rule. Enforce the rule where requests arrive, at your WAF, and check the source network.
Webhook senders call your endpoints to deliver events from payment, messaging and SaaS platforms. Blocking them breaks integrations. Allow them on the webhook paths they need and nowhere else.
Transfon Security identifies every bot in this directory in your traffic reports, flags fake search crawlers, and lets you allow, block or rate limit each bot.
Privacy, security, monetization, and performance insights. A few emails a month, no spam.