Set up your bannerConfigure Your ToolsPayments

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.

  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. 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.

ConfigurationSummary
Configuration A — Medium riskWeb SDK (OSM) loaded after Consenter consent; no Express Checkout or SIWK.
Configuration B — Higher riskOSM plus Klarna Express Checkout and/or Sign in with Klarna on product and cart pages, after consent.

Step 1 — Configure Klarna

#Configuration areaWhere to configure itConfiguration A — Medium riskConfiguration B — Higher risk
1Processing purposesOperator decisionUnlock additional website featuresUnlock additional website features; Support marketing analytics
2FeaturesKlarna Merchant Portal / Web SDKOn-site MessagingOSM + KEC and/or SIWK
3Loadingjs.klarna.com/web-sdk/v1/klarna.jsAfter Consenter consentAfter 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 fieldConfiguration A — Medium riskConfiguration B — Higher risk
Processing purposesUnlock additional website featuresUnlock additional website features, Support marketing analytics
Tracking methodThird party tracking (crosssession, cross-website)Third party tracking (crosssession, cross-website)
IdentifierDevice identifiersDevice identifiers, Authentication-derived identifiers
Data categoriesDevice identifiers, Device characteristics, Browsing and interaction dataDevice identifiers, Device characteristics, Browsing and interaction data, Authentication-derived identifiers, Direct identifier, e-commerce Activity
Legal role of data recipientIndividual ControllerIndividual Controller
Personalisation modelNo personalisationNo personalisation
Maximum storage durationPer Klarna Web SDK disclosurePer Klarna Web SDK disclosure
Processing locationSweden / EU; per DPASweden / 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

On this page