Download websites that use ClearSale

About ClearSale

Fraud screening runs where a shopper never sees it, in the call between a checkout and a scoring service that happens after the order button is pressed. Almost none of that exchange is visible from outside. What can be seen from a page is the small browser-side piece a fraud vendor needs in order to collect device and behaviour signals before the order is submitted, and that fragment is all a technology crawler has to match on.

ClearSale is a fraud and chargeback product from ClearSale, licensed as Proprietary and dating from 2001, which places it among the older names in commerce risk rather than in the recent wave of machine-learning entrants. Merchants integrate it to decide which orders to accept, so the presence of its signature on a storefront is evidence of a business that has chosen to hand order screening to an outside service rather than argue over each suspect order in house. The vendor sells to small and mid-market e-commerce teams as well as to larger merchants, and ships ready made plugins for the common hosted carts, so a match should not be read as a filter on company size.

As of October 2026 the signature appears on 3 sites, and honesty about that number matters more than the number itself. Server-side integrations leave no client-side trace whatsoever, so any list built from page markup undercounts a risk vendor structurally rather than accidentally. The set we can show is the part of the customer base that ships a browser component, which is not the customer base.

The question the export answers is nonetheless one a per-domain lookup cannot touch. Checking a single merchant tells you what a single merchant uses. Pulling the whole matched set and joining it against cart platform, payment scripts and the country a site trades in shows a payments or risk competitor where a rival has actually landed, which platform integrations carried it there, and which merchant profiles it has never reached. We record no version, no leading country and no dominant domain suffix for this entry, so that join has to come from the other columns of the dataset rather than from this one.

One further use is worth naming, because risk teams ask for it directly. A merchant deciding between fraud vendors wants to know which stores comparable to its own already run each candidate, and no vendor publishes that list. Assembling it from a crawl is imperfect for the reasons above, but an imperfect list of confirmed browser-side deployments beats a reference call arranged by the vendor being evaluated.