Detect WEBXPAY

PluginView evaluates public page signals in these classes when identifying WEBXPAY. Individual fingerprint rule bodies are proprietary and are not published.

• JavaScript globals

Illustrative indicators derived from public catalog metadata for WEBXPAY. A live scan may match additional proprietary rules beyond these examples.

• WEBXPAY

Establishes

One or more public signals on the scanned page matched a known WEBXPAY signature (1 rules) at the time of the scan.

Does not establish

A sitewide install of WEBXPAY, an active vendor contract, exclusive use, or that WEBXPAY is still in place today.

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest WEBXPAY signals.
2. 2. PluginView reads only public responses (javascript globals) and scores them against the WEBXPAY signature set (1 rules).
3. 3. Review the confidence score and text explanation for WEBXPAY on the results page.

Can PluginView detect WEBXPAY without logging in?

Yes. PluginView only reads publicly accessible responses when checking for WEBXPAY — typically javascript globals. It does not bypass authentication or paywalls.

What category is WEBXPAY?

WEBXPAY is classified under Payment processors in the PluginView directory.

How many fingerprint rules cover WEBXPAY?

This reference currently tracks 1 fingerprint rule across javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses WEBXPAY?

Illustrative public indicators for WEBXPAY include WEBXPAY. A live scan may match additional proprietary rules beyond these examples.