Set up your bannerConfigure Your ToolsPayments

Stripe

How to configure Stripe at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Unlock additional website features

Overview

This guide explains how to implement different privacy configurations for Stripe.js and its advanced fraud detection signals and how to reflect them in the Consenter Manager. Processing a payment the visitor has chosen is out of scope.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. Stripe.js (Elements, Checkout) on the merchant website.

What the service does in this scope. Stripe.js provides advanced fraud detection based on signals about device characteristics and user activity; collection is disclosed in Stripe's privacy and cookie policies. The signals are sent to Stripe via periodic requests to m.stripe.com. Merchants can disable them with the advancedFraudSignals parameter (or setLoadParameters in the module), which increases fraud risk such as card testing. Stripe states these signals are used only for security and anti-fraud and are not shared or sold to advertisers.

Configurations included.

ConfigurationSummary
Configuration A — Lower riskStripe.js loaded only on checkout; advanced fraud signals disabled.
Configuration B — Medium riskStripe.js loaded only on checkout; advanced fraud signals enabled.
Configuration C — Higher risk (default configuration)Stripe.js loaded on every page with advanced fraud signals enabled.

⚠ Recommendation. Fraud-prevention signals during a payment the visitor requested may be strictly necessary; collection on pages without a payment flow (C) is harder to justify. Have your DPO confirm whether B needs a consent entry and whether C requires consent.

Step 1 — Configure Stripe

#Configuration areaWhere to configure itConfiguration A — Lower riskConfiguration B — Medium riskConfiguration C — Higher risk (default configuration)
1Processing purposesOperator decisionUnlock additional website featuresUnlock additional website featuresUnlock additional website features
2Loading scopeTheme / front-endCheckout pages onlyCheckout pages onlyAll pages
3Advanced fraud signalsadvancedFraudSignals / setLoadParametersDisabledEnabledEnabled

Step 2 — Map the configuration in the Consenter Manager

Processing location. Stripe is a US enterprise; list the United States.

Consenter Manager fieldConfiguration A — Lower riskConfiguration B — Medium riskConfiguration C — Higher risk (default configuration)
Entry neededPer DPO assessmentPer DPO assessment (⚠)Yes
Processing purposesUnlock additional website featuresUnlock additional website featuresUnlock additional website features
Tracking methodThird party tracking (single session, cross-website)Third party tracking (crosssession, cross-website)Third party tracking (crosssession, cross-website)
IdentifierNo identifierDevice identifiers, Probabilistic identifiersDevice identifiers, Probabilistic identifiers
Data categoriesDevice characteristics, IP addressDevice characteristics, Device identifiers, Browsing and interaction data, IP addressDevice characteristics, Device identifiers, Browsing and interaction data, IP address
Legal role of data recipientIndividual ControllerIndividual ControllerIndividual Controller
Personalisation modelNo personalisationNo personalisationNo personalisation
Maximum storage durationPer Stripe cookie policyPer Stripe cookie policyPer Stripe cookie policy
Processing locationEU / United StatesEU / United StatesEU / United States

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page