Detect Stripe
Stripe offers online payment processing for internet businesses as well as fraud prevention, invoicing and subscription management.
Detection looks at cookies, script sources, javascript globals, dom selectors, html markup, dns records across 12 fingerprint rules among the site's public responses.
Websites using Stripe
Loading website list…
Signal classes
PluginView evaluates public page signals in these classes when identifying Stripe. Individual fingerprint rule bodies are proprietary and are not published.
- Cookies
- Script sources
- JavaScript globals
- DOM selectors
- HTML markup
- DNS records
Example public indicators for Stripe
Illustrative indicators derived from public catalog metadata for Stripe. A live scan may match additional proprietary rules beyond these examples.
- __stripe_mid
- __stripe_sid
- js.stripe.com
- Stripe.version: .
- __NEXT_DATA__.props.pageProps.appSettings.STRIPE_API_PUBLIC_KEY
- checkout.enabledpayments.stripe: true
- stripePublicKey
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, pricing, signup, billing
How to check a site for Stripe
- 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Stripe signals (prefer: Checkout, pricing, signup, billing).
- 2. PluginView reads only public responses (cookies, script sources, javascript globals) and scores them against the Stripe signature set (12 rules).
- 3. Review the confidence score and text explanation for Stripe on the results page.
FAQ: detecting Stripe
- Can PluginView detect Stripe without logging in?
- Yes. PluginView only reads publicly accessible responses when checking for Stripe — typically cookies, script sources, javascript globals, dom selectors. It does not bypass authentication or paywalls.
- What category is Stripe?
- Stripe is classified under Payment processors, Payments & Billing in the PluginView directory.
- How many fingerprint rules cover Stripe?
- This reference currently tracks 12 fingerprint rules across cookies, script sources, javascript globals, dom selectors, html markup, dns records. Individual rule bodies are proprietary and are not published.
- What public signals suggest a site uses Stripe?
- Illustrative public indicators for Stripe include __stripe_mid; __stripe_sid; js.stripe.com. A live scan may match additional proprietary rules beyond these examples.
- Which pages are best for detecting Stripe?
- For Stripe, start with: Checkout, pricing, signup, billing.
