Set up your bannerConfigure Your ToolsPayments

PayPal

How to configure PayPal 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, Support marketing analytics

Overview

This guide explains how to implement different privacy configurations for PayPal on a merchant website and how to reflect them in the Consenter Manager. Processing a payment the visitor has chosen is out of scope; the guide covers where the PayPal SDK is loaded beyond that and PayPal's analytics SDK.

  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. PayPal JavaScript SDK (buttons, Pay Later messaging) and the PayPal Insights SDK.

What the service does in this scope. The JavaScript SDK renders the eligible PayPal and Pay Later buttons. PayPal and its service providers use cookies, web beacons and similar technologies when visitors interact with its services. The Insights SDK lets merchants share visitor activity on their website with PayPal, using the PayPal client ID as the analytics tag ID.

Configurations included.

ConfigurationSummary
Configuration A — Lower riskSDK loaded only in checkout once the visitor selects PayPal.
Configuration B — Medium riskSDK with Pay Later messaging on product/cart pages, loaded after consent.
Configuration C — Higher riskAs B, plus the Insights SDK sharing visitor activity with PayPal.

⚠ Recommendation. Whether loading the SDK in checkout (A) is strictly necessary for the payment the visitor requested is a legal assessment. Have your DPO confirm it before running A without a consent entry.

Step 1 — Configure PayPal

#Configuration areaWhere to configure itConfiguration A — Lower riskConfiguration B — Medium riskConfiguration C — Higher risk
1Processing purposesOperator decisionUnlock additional website featuresUnlock additional website featuresUnlock additional website features; Support marketing analytics
2SDK componentsSDK components parameterbuttons (checkout only)buttons, messagesbuttons, messages
3LoadingTheme / shop pluginOn PayPal selection in checkoutAfter Consenter consentAfter Consenter consent
4Insights SDKInsights SDK snippetOffOffOn

Step 2 — Map the configuration in the Consenter Manager

Processing location. PayPal's EU services are provided by a Luxembourg entity of a US group; list the United States.

Consenter Manager fieldConfiguration A — Lower riskConfiguration B — Medium riskConfiguration C — Higher risk
Entry neededPer DPO assessment (⚠)YesYes
Processing purposesUnlock additional website featuresUnlock additional website featuresUnlock additional website features, Support marketing analytics
Tracking methodThird party tracking (crosssession, cross-website)Third party tracking (crosssession, cross-website)Third party tracking (crosssession, cross-website)
IdentifierDevice identifiersDevice identifiersDevice identifiers
Data categoriesDevice identifiers, Device characteristics, IP address, e-commerce ActivityDevice identifiers, Device characteristics, IP address, Browsing and interaction dataDevice identifiers, Device characteristics, IP address, Browsing and interaction data, e-commerce Activity
Legal role of data recipientIndividual ControllerIndividual ControllerIndividual Controller
Personalisation modelNo personalisationNo personalisationGroup based (behaviour)
Maximum storage durationPer PayPal cookie statementPer PayPal cookie statementPer PayPal cookie statement
Processing locationEU (Luxembourg) / United StatesEU (Luxembourg) / United StatesEU (Luxembourg) / 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