Tokenized payments overview
A brief overview of Klarna tokenized payments in your Solidgate checkout — customer-initiated and partner-initiated transactions, and the token creation and charge integration variants.
3 min read
Klarna tokenized payments save a customer's Klarna payment method as a secure Klarna Customer Token. The token is created once — with the customer present and consenting — and then charged whenever a payment is due.
Customer-initiated vs partner-initiated
- Customer-initiated (CIT) — the customer is at checkout and completes an on-demand charge in one click from their saved Klarna option. Klarna may require a step-up through the Klarna Purchase Journey.
- Partner-initiated (PIT) — a scheduled or recurring charge (for example a subscription renewal) that you run server-side, with no customer present and no step-up.
Match one-time payment integration
Keep the same integration type as your one-time Klarna payments. Match both the orchestration model and the presentation method across the token lifecycle:
- Orchestration — if you orchestrate one-time payments yourself with Klarna's
createPaymentRequestendpoint, orchestrate the token creation and the follow-up token charges the same way. If instead Solidgate's API orchestrates your one-time payments, follow that same pattern for the token creation and token charges. - Presentation — use the same presentation method (Klarna Web SDK or Klarna Payment Presentation API) for one-time payments, token creation, and customer-initiated token charges, wherever a payment form is displayed.
Create a token
Save the customer's Klarna payment method while they are present and consenting. There are two variants, depending on who requests the token:
- Partner-orchestrated — you request the token yourself by calling Klarna's
Create Payment Requestendpoint. You are the token owner, but the token can only be used within Solidgate's context. Create a Klarna Customer Token (Partner orchestrated) → - Solidgate-orchestrated — Solidgate requests the token and shares it back to you, so you can present the saved Klarna option for customer-initiated charges. Create a Klarna Customer Token (Solidgate orchestrated) →
Charge a returning customer (customer-initiated)
The Klarna Customer Token is always required to present the customer's saved option.
- Klarna Web SDK (in-page pop-up) — Partner orchestrated · Solidgate orchestrated
- Klarna Payment Presentation API (full-page redirect) — Partner orchestrated · Solidgate orchestrated
Integration requirement
Solidgate does not provide a hosted or embedded payment form for the returning-customer experience — you always build the payment form yourself.
Customer not present charge (partner-initiated)
A single server-side charge against the stored token — customer not present, no form, no step-up. The response is always
APPROVED or DECLINED.- Partner-orchestrated — Charge a partner-initiated transaction (Partner orchestrated) →
- Solidgate-orchestrated — Charge a partner-initiated transaction (Solidgate orchestrated) →
Jump to section...