Klarna
How to configure Klarna 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 the Klarna Web SDK features on a merchant website and how to reflect them in the Consenter Manager. Processing a Klarna 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. Klarna Web SDK conversion features: On-site Messaging (OSM), Klarna Express Checkout (KEC) and Sign in with Klarna (SIWK).
What the service does in this scope. When integrating the Web SDK, for example for conversion boosters, partners must inform users about the tracking technologies employed. Merchants must disclose both strictly necessary technologies and any specific technologies used by the Web SDK, including name, purpose, provider, local storage use and retention period. KEC can be placed on product or cart pages and pre-fills the customer's personal details.
Configurations included.
| Configuration | Summary |
|---|---|
| Configuration A — Medium risk | Web SDK (OSM) loaded after Consenter consent; no Express Checkout or SIWK. |
| Configuration B — Higher risk | OSM plus Klarna Express Checkout and/or Sign in with Klarna on product and cart pages, after consent. |
Step 1 — Configure Klarna
| # | Configuration area | Where to configure it | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|---|---|
| 1 | Processing purposes | Operator decision | Unlock additional website features | Unlock additional website features; Support marketing analytics |
| 2 | Features | Klarna Merchant Portal / Web SDK | On-site Messaging | OSM + KEC and/or SIWK |
| 3 | Loading | js.klarna.com/web-sdk/v1/klarna.js | After Consenter consent | After Consenter consent |
Step 2 — Map the configuration in the Consenter Manager
Processing location. Klarna Bank AB is a Swedish company; check its DPA for US sub-processors and list the United States if present.
| Consenter Manager field | Configuration A — Medium risk | Configuration B — Higher risk |
|---|---|---|
| Processing purposes | Unlock additional website features | Unlock additional website features, Support marketing analytics |
| Tracking method | Third party tracking (crosssession, cross-website) | Third party tracking (crosssession, cross-website) |
| Identifier | Device identifiers | Device identifiers, Authentication-derived identifiers |
| Data categories | Device identifiers, Device characteristics, Browsing and interaction data | Device identifiers, Device characteristics, Browsing and interaction data, Authentication-derived identifiers, Direct identifier, e-commerce Activity |
| Legal role of data recipient | Individual Controller | Individual Controller |
| Personalisation model | No personalisation | No personalisation |
| Maximum storage duration | Per Klarna Web SDK disclosure | Per Klarna Web SDK disclosure |
| Processing location | Sweden / EU; per DPA | Sweden / EU; per DPA |
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