Detect LayBuy

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

• Script sources
• JavaScript globals
• DOM selectors

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

• .laybuy.com/
• wp-content/plugins/woo-laybuy/
• LaybuyHelper
• checkout.enabledpayments.laybuy: true
• laybuyEnableCart
• laybuyMoneyOverides
• wc_ga_pro.available_gateways.laybuy
• iframe, a

Establishes

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

Does not establish

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

Can PluginView detect LayBuy without logging in?

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

What category is LayBuy?

LayBuy is classified under Buy now pay later in the PluginView directory.

How many fingerprint rules cover LayBuy?

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

What public signals suggest a site uses LayBuy?

Illustrative public indicators for LayBuy include .laybuy.com/; wp-content/plugins/woo-laybuy/; LaybuyHelper. A live scan may match additional proprietary rules beyond these examples.