Can PluginView detect Square Web Payments without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Square Web Payments — typically vendor endpoints. It does not bypass authentication or paywalls.

What category is Square Web Payments?

Square Web Payments is classified under Payments & Billing in the PluginView directory.

How many fingerprint rules cover Square Web Payments?

This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Square Web Payments?

Illustrative public indicators for Square Web Payments include web.squarecdn.com; squareup.com/payment-form. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Square Web Payments?

For Square Web Payments, start with: Checkout and payment forms.

Detect Square Web Payments

Payments & Billing

PluginView detects Square Web Payments, a Payments & Billing, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Square Web Payments include web.squarecdn.com, squareup.com/payment-form. The listed vendor-controlled browser component was present and active on the scanned page at scan time. Full fingerprint rules remain proprietary; this page summarizes the signal classes and example indicators used for identification.

Detection looks at vendor endpoints across 2 fingerprint rules among the site's public responses.

Websites using Square Web Payments

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for Square Web Payments

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

web.squarecdn.com
squareup.com/payment-form

What a detection means

Establishes: The listed vendor-controlled browser component was present and active on the scanned page at scan time.
Does not establish: It does not prove a sitewide installation, current commercial contract, backend-only use, exclusive use, or production transaction volume.

Minimum proof rule

Observe a live browser request, loaded script, or iframe to the listed unique vendor endpoint. Source-text-only matches do not qualify.

Best pages to check: Checkout and payment forms

How to check a site for Square Web Payments

1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Square Web Payments signals (prefer: Checkout and payment forms).
2. PluginView reads only public responses (vendor endpoints) and scores them against the Square Web Payments signature set (2 rules).
3. Review the confidence score and text explanation for Square Web Payments on the results page.

FAQ: detecting Square Web Payments

Can PluginView detect Square Web Payments without logging in?: Yes. PluginView only reads publicly accessible responses when checking for Square Web Payments — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is Square Web Payments?: Square Web Payments is classified under Payments & Billing in the PluginView directory.
How many fingerprint rules cover Square Web Payments?: This reference currently tracks 2 fingerprint rules across vendor endpoints. Individual rule bodies are proprietary and are not published.
What public signals suggest a site uses Square Web Payments?: Illustrative public indicators for Square Web Payments include web.squarecdn.com; squareup.com/payment-form. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting Square Web Payments?: For Square Web Payments, start with: Checkout and payment forms.