Overview
Discover every way to present Klarna in your checkout with Solidgate — Klarna Web SDK or Payment Presentation API, orchestrated by you or by Solidgate, plus Solidgate's hosted and embedded checkout alternatives.
2 min read
There are several ways to add Klarna to a checkout you build on top of Solidgate. The right one for you depends on two things:
- 1.The customer experience you want — an in-page Klarna pop-up, or a full-page redirect to Klarna's hosted page.
- 2.Who runs the Klarna lifecycle server-side — you, or Solidgate.
Pick your combination below; each variant links to its dedicated end-to-end walkthrough.
How Klarna shows up to your customer
- In-page pop-up — only available with the Klarna Web SDK. The Klarna Purchase Journey opens in an overlay inside your checkout.
- Full-page redirect to Klarna's hosted page — used with the Klarna Payment Presentation API (no SDK). When step-up is required, the customer is redirected to Klarna's hosted page to complete the Klarna Purchase Journey.
Build your own checkout form
Klarna Web SDK (in-page pop-up)
The Klarna Web SDK runs client-side in your checkout, renders Klarna in your payment selector, and opens the Klarna Purchase Journey as an in-page pop-up.
- Partner-orchestrated — you call Klarna's Payment Request API directly and subscribe to the completion webhook yourself. Most control, full Klarna feature surface.
- Solidgate-orchestrated — you forward the
klarna_to Solidgate; Solidgate calls Klarna's Payment Request API on your behalf and returns anetwork_ session_ token payment_back to the SDK when step-up is required. No webhook subscription on your side.request_ id
Klarna Payment Presentation API (full-page redirect)
You call Klarna's Payment Presentation API server-side, render Klarna in your own payment selector, and the Klarna Purchase Journey ends in a full-page redirect to Klarna's hosted page. No SDK.
- Partner-orchestrated — you also call Klarna's Payment Request API directly and subscribe to the completion webhook yourself. Server-side equivalent of the Web SDK partner-orchestrated path.
- Solidgate-orchestrated — you only call Klarna's Payment Presentation API; Solidgate handles authorization and returns a
payment_for the redirect. No webhook subscription on your side.request_ url
If you don't build your own checkout form
Two further options on the Solidgate side, with no Klarna-specific work for you:
- Solidgate's hosted payment page — Klarna shows up by default once it's enabled with Solidgate.
- Solidgate's embedded payment form (when Solidgate offers one) — drop Solidgate's payment-form components into your own checkout and Klarna is rendered inside them.
For the configuration of either, follow Solidgate's product documentation.
Jump to section...