Skip to main content
Klarna is a buy now, pay later (BNPL) payment method that offers flexible payment options and supports recurring payments through merchant-initiated transactions (MIT).

Setup

A Klarna account can be requested from the Klarna Business Portal.

Credentials

To connect a Klarna account, obtain the following credentials from the Klarna Business Portal.
  • Username: An API username which can be generated by navigating to PreferencesSettingsManage Klarna API Credentials
  • Password: An API password which can be generated by navigating to PreferencesSettingsManage Klarna API Credentials
  • Region: The region of the Klarna account. Enter EU for Europe, NA for North America, or OC for Oceania
  • Client ID (optional): Required only for Express Checkout. Obtain from your Klarna Business Portal and enter it here so Gr4vy can return it via the Create Session API to initialize the Klarna Payments Buttons SDK.

Capabilities

Supported countries

Supported currencies

Integration

For Klarna, the default integration uses a redirect to the Klarna hosted payments page. A direct integration using the Klarna JavaScript SDK or mobile SDKs is also supported.

Redirect integration

Start by creating a new transaction with the following required fields.
After the transaction is created, the API response includes payment_method.approval_url and the buyer_approval_pending status.
Redirect the buyer to the approval_url to complete the Klarna approval flow. Once approved, the transaction moves to authorization_succeeded.

Direct integration

Gr4vy supports direct integration with Klarna using the Klarna Payments SDK or mobile SDKs, allowing you to embed the payment UI directly in your app while using Gr4vy to manage the transaction lifecycle. Two modes are supported: Standard Checkout (session-based) and Express Checkout (button-based, no session required).

Standard Checkout

To initiate Standard Checkout, create a transaction with integration_client set to web, ios, or android. For mobile, use your app deep link for redirect_url (for example, yourapp://). After the transaction is created, the API response includes a session_token which can be used to get the session data for that transaction.
Use the client_token from the session data to initialize the Klarna SDK. Refer to the Klarna SDK documentation for web integration. Web
iOS (Swift) — See the iOS SDK guide.
Android (Kotlin) — See the Android SDK guide.
Complete the transaction After the customer authorizes the payment through the Klarna SDK, Klarna returns an authorization_token. To finalize the transaction, send this token to Gr4vy as a query parameter on the default_completion_url returned in the session response.
Terminal
Once the request completes successfully, the transaction moves to authorization_succeeded. It can then be captured, voided, or refunded through Gr4vy.

Express Checkout

Klarna Express Checkout embeds the Klarna payment button directly in your page using the Klarna Payments Buttons SDK. The buyer authorizes the payment inside the SDK widget — no redirect to a hosted page is required. After authorization, your backend creates the Gr4vy transaction in a single call using the authorization_token returned by the SDK. Get the client ID The Klarna Payments Buttons SDK requires a client_id to initialize. You can obtain this in one of two ways:
  • Via the Gr4vy API — Call the Create Payment Service Session endpoint for your Klarna connection. Gr4vy returns a clientId from the connector credentials without making any Klarna API call.
    Terminal
    Response
  • Hardcoded — Copy the client_id from your Klarna Business Portal and embed it directly in your frontend. This is suitable when the client ID does not change per session.
Embed the Express Checkout button Load the Klarna SDK and render the Express Checkout button. The klarnaAsyncCallback function must be defined before the SDK script tag so it is available when the SDK initializes.
Mobile For mobile applications, use the Klarna Mobile SDK. The SDK is initialized with a client_id and renders a KlarnaExpressCheckoutButton. iOS (Swift) — See the iOS integration guide.
Android (Kotlin) — See the Android integration guide.
React Native — See the React Native integration guide.
Create the transaction Once your server receives the authorization_token, create a Gr4vy transaction and pass the token in connection_options under the klarna-klarna key. Gr4vy forwards the token to Klarna to place the order directly — the transaction moves to authorization_succeeded without any redirect.
The authorization_token returned by the Klarna SDK expires within approximately 60 minutes. Create the Gr4vy transaction immediately after receiving it.

Subscriptions (MIT)

Klarna supports storing the buyer’s payment method during the first (customer-present) payment and charging future renewals as merchant-initiated transactions (MIT) using the saved payment method, typically with no redirect.
Webhooks must be configured for the Klarna payment service. After the buyer approves the payment, Klarna sends an authorization_token via webhook which Gr4vy uses to create the reusable customer token. Without this webhook, store: true will not work.

First payment

Set store to true to save the Klarna payment method for the buyer.

Subsequent payment

After the payment method is saved, use the payment method ID to charge future renewals.
  • Set payment_method.method to id and pass the saved payment method ID.
  • Set payment_source to recurring.
  • Set merchant_initiated and is_subsequent_payment to true.