Customer initiated Payment Authorization
Authorize a Payment Transaction with Klarna when the customer is present at checkout. 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.
163 min read
Authorize a Payment Transaction with Klarna when the customer is present during checkout. One decision shapes the integration — who owns the customer-facing experience, and therefore who launches the Klarna Purchase Journey when Klarna returns
STEP_UP_REQUIRED:- 1.Server-side integration — Partners own the checkout. Your backend collects the payment context from the Partner, calls authorizePayment
, and returns the outcome — including the step-up details — for the Partner to act on. - 2.Hosted checkout pages and embedded elements — you own the checkout. Your backend calls authorizePayment and your frontend launches the Klarna Purchase Journey through the Klarna web SDK when step-up is required.
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 Authorization overview.
Jump to section...