Skip to content

Integrating Klarna

Auth: API key · Partner program: not required · Setup time: about 15 minutes · Last verified: 2026-05-15

BNPL leader across EMEA + US — Pay Now, Pay in 30, Pay in 4, and Financing. Klarna routes API traffic to regional clusters (api.klarna.com, api-na.klarna.com, api-oc.klarna.com), each with its own playground host. Pick the region your Merchant Portal API keys belong to.

raw is opt-in. The upstream payload is withheld unless an operator enables data_store.raw_payload.payments in Admin → Settings → Data store. It is off by default because across the payments adapters it declares bank account numbers, IBANs and card numbers the canonical schema does not expose.

HTTP Basic, username + password from the Klarna Merchant Portal under Settings → API credentials. Submit via the Connect Link form along with the region.

  • Installments live outside the canonical schema. Klarna’s order carries the full instalment schedule + APR; the canonical Charge.amount exposes the principal only. Consumers who need instalments must drop down to Charge.raw.
  • No bulk-list endpoint. Klarna doesn’t expose GET /orders over its merchant API. The adapter surfaces orders via webhooks plus getCharge by order_id.
  • Partial captures map to Charge.status = 'partially_refunded' (the canonical schema lacks a dedicated partially_captured state).

Configure under Push notification URLs on each merchant ID. HMAC-SHA-256 of the raw body keyed with the shared secret, hex-encoded in Klarna-Signature.