Detect Mokka

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

• Script sources

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

• revoiframe.js

Establishes

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

Does not establish

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

Can PluginView detect Mokka without logging in?

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

What category is Mokka?

Mokka is classified under Payment processors, Buy now pay later in the PluginView directory.

How many fingerprint rules cover Mokka?

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

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