Download websites that use WorldPay

About WorldPay

WorldPay is older than the web it now takes payments on. The brand dates from 1989, when card processing meant terminals, phone lines and overnight settlement files, and the online checkout arrived later as a layer over infrastructure that already existed. The history is still visible in how the product is deployed, because the part a website exposes is a thin front end over a much larger clearing and settlement business.

Our records list the owner as Global Payments, and the value is worth checking against the vendor's own site before anyone leans on it. Payment brands change hands, and the processing brand a merchant knows is frequently not the legal entity that owns it in any given year. Anyone joining a merchant list to corporate data should expect the mapping between brand and owner to shift underneath them, and should date every join accordingly.

As of October 2026 we detect the fingerprint on 89 sites. Payments is one of the areas where a web scan sees least of what is really there. Checkout often happens on a domain the processor owns, or inside an iframe, or after a redirect that a crawler walking public pages never triggers, and a large share of merchants reach the processor through a gateway or a shopping cart that carries its own name instead. The count should be read as sites exposing the marker on a page we can fetch, not as a merchant count.

The limitation still leaves a useful list, provided the question matches it. Competing processors prospect it directly. Risk and fraud researchers use it to map which merchants sit behind which processor, which is otherwise very hard to observe from outside. Analysts use it to estimate presence by vertical and by domain suffix without relying on press releases. Due diligence teams use it to check what a portfolio company actually runs rather than what its deck claims.

A per domain lookup answers one merchant. The export answers movement, which is where the money is in this category, because a change of processor is a rare event, a slow decision and a strong buying signal, and it is only observable by comparing the whole set against itself over time.

The product is Proprietary, which in payments is unremarkable and also convenient for a researcher. There is no self hosted variant to muddy the reading, so every detection points at a live commercial relationship rather than at somebody running a copy of the code long after the vendor stopped hearing from them.