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.
- Configure the third-party service.
- Map the selected configuration in the Consenter Manager.
- 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.
| Configuration | Summary |
|---|---|
| Configuration A — Lower risk | Stripe.js loaded only on checkout; advanced fraud signals disabled. |
| Configuration B — Medium risk | Stripe.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 area | Where to configure it | Configuration A — Lower risk | Configuration B — Medium risk | Configuration C — Higher risk (default configuration) |
|---|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Unlock additional website features | Unlock additional website features | Unlock additional website features |
| 2 | Loading scope | Theme / front-end | Checkout pages only | Checkout pages only | All pages |
| 3 | Advanced fraud signals | advancedFraudSignals / setLoadParameters | Disabled | Enabled | Enabled |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Stripe is a US enterprise; list the United States.
| Consenter Manager field | Configuration A — Lower risk | Configuration B — Medium risk | Configuration C — Higher risk (default configuration) |
|---|---|---|---|
| Entry needed | Per DPO assessment | Per DPO assessment (⚠) | Yes |
| Processing purposes | Unlock additional website features | Unlock additional website features | Unlock additional website features |
| Tracking method | Third party tracking (single session, cross-website) | Third party tracking (crosssession, cross-website) | Third party tracking (crosssession, cross-website) |
| Identifier | No identifier | Device identifiers, Probabilistic identifiers | Device identifiers, Probabilistic identifiers |
| Data categories | Device characteristics, IP address | Device characteristics, Device identifiers, Browsing and interaction data, IP address | Device characteristics, Device identifiers, Browsing and interaction data, IP address |
| Legal role of data recipient | Individual Controller | Individual Controller | Individual Controller |
| Personalisation model | No personalisation | No personalisation | No personalisation |
| Maximum storage duration | Per Stripe cookie policy | Per Stripe cookie policy | Per Stripe cookie policy |
| Processing location | EU / United States | EU / United States | EU / 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