Set up your bannerConfigure Your ToolsPayments

Amazon Pay

How to configure Amazon Pay 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 the Amazon Pay button on a merchant website 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. Amazon Pay Checkout v2 (checkout.js).

What the service does in this scope. The checkout.js script renders the Amazon Pay button; Amazon recommends placing the Express button wherever checkout starts, such as the mini cart, cart page or checkout page, or in the payment selection at the end of checkout. Amazon Payments uses cookies to recognise the browser or device. Shop modules document loading all Amazon Pay scripts only after consent through a CMP.

Configurations included.

ConfigurationSummary
Configuration A — Lower riskAmazon Pay offered only in the payment selection at the end of checkout; script loaded when selected.
Configuration B — Medium riskExpress button on mini cart / cart pages; script loaded after Consenter consent.

⚠ Recommendation. Whether loading checkout.js in 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 Amazon Pay

#Configuration areaWhere to configure itConfiguration A — Lower riskConfiguration B — Medium risk
1Processing purposesOperator decisionUnlock additional website featuresUnlock additional website features
2Button placementShop integrationPayment selection at end of checkoutMini cart / cart / product pages
3LoadingShop template / CMPOn selectionAfter Consenter consent

Step 2 — Map the configuration in the Consenter Manager

Processing location. Amazon Payments Europe operates from Luxembourg as part of a US group; list the United States.

Consenter Manager fieldConfiguration A — Lower riskConfiguration B — Medium risk
Entry neededPer DPO assessment (⚠)Yes
Processing purposesUnlock additional website featuresUnlock additional website features
Tracking methodThird party tracking (crosssession, cross-website)Third party tracking (crosssession, cross-website)
IdentifierDevice identifiers, Authentication-derived identifiersDevice identifiers, Authentication-derived identifiers
Data categoriesDevice identifiers, Device characteristics, Authentication-derived identifiers, e-commerce ActivityDevice identifiers, Device characteristics, Authentication-derived identifiers, Browsing and interaction data, e-commerce Activity
Legal role of data recipientIndividual ControllerIndividual Controller
Personalisation modelNo personalisationNo personalisation
Maximum storage durationPer Amazon Payments cookie noticePer Amazon Payments cookie notice
Processing locationEU (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