Skip to main content

General Information

Website: Klarna
Software type: Solution as a Software (Saas)
Geography: 🌎 Worldwide

​
Introduction

Klarna is a global payment provider offering buy now, pay later and card payments to online and in-store merchants. It settles the merchant’s sales through periodic payouts. The connector reads the Settlements API: the payouts made to the merchant and the transactions they are made of.

​
Activate Klarna

​
Partner keys

No partner keys and no approval: the connector is ready to use.

Activate Klarna in your Chift account

One click in Connectors, then create connections straight away.

​
Connector settings

Environment selects which Klarna environment the connections of this connector talk to.
  • Production (default): the merchant’s live Klarna account.
  • Playground: Klarna’s test environment.
Use Playground while you test the integration, then switch back to Production before your end users connect. API credentials belong to one environment: Playground credentials are refused on Production, and the other way round.

​
Test Klarna

​
Vendor fees

No vendor fees, for you or your end users.

​
Connect Klarna

Klarna setup guide for end users

The full step-by-step, with screenshots.
Before they start, your end users need:
  • an active Klarna merchant account
  • admin rights on the Klarna Merchant Portal, to create API credentials
To connect, they:
  • generate an API credential in the Merchant Portal, under Settings › Klarna API credentials
  • select the Region of their merchant account: Europe, North America or Oceania
  • enter the credential’s Username and Password in the connection form

​
Rate limits

Klarna applies a rate limit per API operation. The category of each operation is documented in its description, and background traffic can be routed to a separate quota. When the limit is exceeded, Klarna returns HTTP 429 Too Many Requests, with X-RateLimit headers giving the remaining quota. Chift automatically manages these limits to optimize performance and prevent interruptions. However, once the API rate limit is reached, Chift cannot bypass these limitations. See Klarna’s rate limit documentation.

​
Limitations & specificities

  • Transactions are read from Klarna’s settlement data. With a date filter, a transaction is returned once Klarna has included it in a payout, which happens after the merchant’s payout delay. Transactions not yet paid out are only returned by a call without dates.
  • Klarna gives no identifier to a settlement transaction. Chift builds a stable one from the transaction’s content: order, type, capture or refund, amount and sale date.
  • The starting_from and balance_id filters are not supported and are refused.
  • The invoice accounting category has no equivalent at Klarna and returns an empty list.
  • The VAT Klarna charges on its fees is included in the fee transaction’s amount, so the transactions of a payout add up to the payout amount.
  • A payout’s fee is the sum of Klarna’s fees and the VAT on them, minus fee corrections and fee refunds.
  • Every payout is also returned as a transaction with the payout accounting category.
  • Klarna only reports paid payouts: the status is always paid, the type always bank account.
Payments, refunds and balances are not available yet: the Settlements API only exposes settled amounts, and how to map them is under analysis. Locations do not exist at Klarna.

​
Coverage