Detect HiPay

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

• Script sources
• JavaScript globals

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

• .hipay.com/
• HiPay

Establishes

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

Does not establish

A sitewide install of HiPay, an active vendor contract, exclusive use, or that HiPay 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 HiPay signals.
2. 2. PluginView reads only public responses (script sources, javascript globals) and scores them against the HiPay signature set (2 rules).
3. 3. Review the confidence score and text explanation for HiPay on the results page.

Can PluginView detect HiPay without logging in?

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

What category is HiPay?

HiPay is classified under Payment processors in the PluginView directory.

How many fingerprint rules cover HiPay?

This reference currently tracks 2 fingerprint rules across script sources, javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses HiPay?

Illustrative public indicators for HiPay include .hipay.com/; HiPay. A live scan may match additional proprietary rules beyond these examples.