How This Briefing Works
This dossier opens with key findings, then maps the gap between what Stripe discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection evidence underneath. BLACKOUT observes runtime browser behavior and cites the regulations that address each pattern — legal determinations are your counsel's call.
At a Glance
across 12 sites
vendor fires before consent
Briefing
While Stripe provides essential payment processing, its client-side JavaScript employs device fingerprinting, session recording, and cross-domain identity resolution that creates revenue risk beyond transactional necessity. Detection methods include defeat device tactics and consent bypass patterns.
What This Means For You
Sites embedding Stripe inherit fingerprinting and session recording liability from script load, not just checkout interaction. Distorted attribution measurement from cross-domain tracking undermines true conversion analysis. GDPR exposure exists if consent banner loads after Stripe.js initialization.
Risk Channel Breakdown
Stripe.js fingerprinting corrupts attribution by tracking users across sessions and domains, distorting measurement of organic vs. tracked conversion paths.
Device fingerprints and behavioral profiles feed Stripe's fraud network and analytics products, subsidizing competitors' customer acquisition through shared surveillance infrastructure.
Expands attack surface
Session recording and fingerprinting occur before payment interaction, creating pre-consent liability and GDPR exposure for sites embedding Stripe without explicit user authorization.
Threat Indicators
Runtime-observed (BTI-C)
Evasion infrastructure, auditor bypass
Full session replay
Identity stitching
Ignoring CMP signals
Device identification
PII deanonymization
Per-code narrative explanations of what each detected behavior means for your organization
Per-code evidence with full attribution chain, severity rankings, and consequence narratives See pricing →
Agent Runtime — MCP Options
Stripe ships a first-party MCP server. If you're deploying an LLM agent that needs to read or write to Stripe, this is the comparison set. Each option's severity reflects how a reasonable buyer should weigh it.
Claims vs. Reality
BLACKOUT analyzed Stripe's public claims against observed runtime behavior and identified 1 contradiction.
Full claim-vs-reality gap analysis with claim text, observed behavior, severity, regulatory citations (GDPR, CCPA, ePrivacy), and evidence pointers per gap See pricing →
What To Do
3 for current users · 2 for evaluators
contractual leverage points
Role-specific actions (security / legal / marketing / procurement), full negotiation brief with contractual language, and BTI-code-specific consequences See pricing →
Supply Chain & Pairings
Full supply-chain mapping (loads / loaded-by lists with vendor identities) and the undisclosed-subprocessor list with observation evidence See pricing →