Integrate Payment Tokenization
Create a customer token with Klarna while the customer is present to give consent. Choose your integration path — the Klarna Web SDK, embedded in the checkout, or server-side integration, driven from the backend.
448 min read
Create a
customer_ with Klarna while the customer is present to give consent, then store it for future transactions. One decision shapes the integration — how the customer is taken through the Klarna Purchase Journey to grant consent:- 1.Web SDK — the Klarna Web SDK presents Klarna in the payment selector and launches the Klarna Purchase Journey in a popup or modal, while the Partner's backend creates the Payment Request with
request_.customer_ token - 2.Presentation API — the Partner's backend creates the Payment Request with
request_and redirects the customer to the Klarna Purchase Journey through thecustomer_ token payment_.request_ url
Both paths use the same createPaymentRequest
and authorizePayment calls and the same webhook events. For tokenization scenarios, token scopes, and how each path works, see the Payment Tokenization overview.
and authorizePayment calls and the same webhook events. For tokenization scenarios, token scopes, and how each path works, see the Payment Tokenization overview.Jump to section...