Klarna Direct

Authorize customer-initiated transactions

Authorize a Payment Transaction with Klarna when the customer is present at checkout. Choose your integration path — the Klarna Web SDK, server-side integration, or the Klarna Mobile SDK in a native app.
489 min read
Authorize a Payment Transaction with Klarna when the customer is present during checkout. One decision shapes the integration — how the customer is taken through the Klarna Purchase Journey after clicking the Klarna payment button:
  1. 1.
    Web SDK (recommended) — the Klarna Web SDK launches the Klarna Purchase Journey in a popup or modal through the initiate callback, so the customer stays on the checkout page.
  2. 2.
    Presentation API — the Partner's backend redirects the customer to the Klarna Purchase Journey and receives the Klarna Network Session Token by webhook. Use this path only when the Klarna Web SDK cannot be embedded.
  3. 3.
    Mobile SDK — the Klarna Mobile SDK, embedded in a native iOS, Android, or React Native app, presents Klarna and launches the Klarna Purchase Journey natively.
All three paths use the same API calls: createPaymentRequestAPI, retrieve the klarna_network_session_token, then authorizePaymentAPI. For when to choose each path, see the Payment Authorization overview.
Related articles
Payment Authorization overview
Integrate Payment Presentation
Set up your webhooks
Payment Authorization
Payment Request
Support
Partner support•Service Status
Cookies|Terms & Conditions|Copyright Klarna AB 2026
Jump to section...