Can PluginView detect Afterpay / Clearpay without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Afterpay / Clearpay — typically vendor endpoints. It does not bypass authentication or paywalls.

What category is Afterpay / Clearpay?

Afterpay / Clearpay is classified under Payments & Billing in the PluginView directory.

How many fingerprint rules cover Afterpay / Clearpay?

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 Afterpay / Clearpay?

Illustrative public indicators for Afterpay / Clearpay include static.afterpay.com; portal.afterpay.com. A live scan may match additional proprietary rules beyond these examples.

Which pages are best for detecting Afterpay / Clearpay?

For Afterpay / Clearpay, start with: Product, cart, checkout.

Detect Afterpay / Clearpay

Payments & Billing

PluginView detects Afterpay / Clearpay, a Payments & Billing, by evaluating vendor endpoints on publicly reachable pages. Illustrative public indicators associated with Afterpay / Clearpay include static.afterpay.com, portal.afterpay.com. 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 Afterpay / Clearpay

Loading website list…

Signal classes

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

Vendor endpoints

Example public indicators for Afterpay / Clearpay

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

static.afterpay.com
portal.afterpay.com

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: Product, cart, checkout

How to check a site for Afterpay / Clearpay

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

FAQ: detecting Afterpay / Clearpay

Can PluginView detect Afterpay / Clearpay without logging in?: Yes. PluginView only reads publicly accessible responses when checking for Afterpay / Clearpay — typically vendor endpoints. It does not bypass authentication or paywalls.
What category is Afterpay / Clearpay?: Afterpay / Clearpay is classified under Payments & Billing in the PluginView directory.
How many fingerprint rules cover Afterpay / Clearpay?: 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 Afterpay / Clearpay?: Illustrative public indicators for Afterpay / Clearpay include static.afterpay.com; portal.afterpay.com. A live scan may match additional proprietary rules beyond these examples.
Which pages are best for detecting Afterpay / Clearpay?: For Afterpay / Clearpay, start with: Product, cart, checkout.