Integrate Payment Tokenization
Create a Customer Token with Klarna while the customer is present to give consent. Choose your integration path — server-side integration, where Partners own the customer-facing experience, or hosted checkout pages and embedded elements, where you own it.
175 min read
Create a Customer Token with Klarna while the customer is present to give consent, then store it for future transactions. One decision shapes the integration — who owns the customer-facing experience, and therefore who takes the customer through the Klarna Purchase Journey:
- 1.Server-side integration — Partners own the checkout. Your backend collects the payment context from the Partner, calls authorizePayment
with a tokenization request, and returns the payment_request_urlso the Partner can redirect the customer to the Klarna Purchase Journey. - 2.Hosted checkout pages and embedded elements — you own the checkout. Your frontend presents Klarna through the Klarna web SDK, which launches the Klarna Purchase Journey itself when step-up is required, and your backend calls authorizePayment with the tokenization request.
Both paths use the same Payment Authorize API and the same webhook events. For when to choose each path and how responsibilities split between you and the Partner, see the Payment Tokenization overview.
Jump to section...