Detect CitrusPay

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

• Script sources

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

• checkout-static.citruspay.com/

Establishes

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

Does not establish

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

Can PluginView detect CitrusPay without logging in?

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

What category is CitrusPay?

CitrusPay is classified under Payment processors in the PluginView directory.

How many fingerprint rules cover CitrusPay?

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

What public signals suggest a site uses CitrusPay?

Illustrative public indicators for CitrusPay include checkout-static.citruspay.com/. A live scan may match additional proprietary rules beyond these examples.