Detect PayWhirl

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

• JavaScript globals

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

• paywhirlForShopifySettings

Establishes

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

Does not establish

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

Can PluginView detect PayWhirl without logging in?

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

What category is PayWhirl?

PayWhirl is classified under Payment processors in the PluginView directory.

How many fingerprint rules cover PayWhirl?

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 PayWhirl?

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