> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# Klarna

> Accept Klarna buy now, pay later payments, where customers pay now, pay later or spread the cost on a Klarna page after a redirect from your checkout.

<picture noZoom>
  ![Klarna logo](https://assets.payrails.io/img/logos/klarna/logo-full-bleed.svg)
</picture>

Klarna is a buy now, pay later (BNPL) payment method. Customers pay now, pay later or spread the cost over time, and Klarna selects the options it offers each customer.

Payrails processes Klarna directly with Klarna, and through Adyen and Stripe. The flow is the same with each one, but the required request fields, the payment method codes, and the supported workflows differ. Pick a PSP below for its setup steps and request examples.

## How a Klarna payment works

Klarna is a redirect payment method:

1. The customer selects Klarna at checkout.
2. Payrails returns a redirect URL from the PSP, and the customer goes to a Klarna page.
3. The customer signs in to Klarna, picks how to pay, and confirms the purchase.
4. Klarna sends the customer back to your `returnInfo` URL.
5. Payrails receives the result from the PSP and updates the payment.

Klarna supports delayed capture with every PSP. Authorize the payment when the customer checks out, then [capture it](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-a-payment.md) when you ship the order, or [cancel it](https://docs.payrails.com/docs/orchestration/payment-acceptance/cancel-a-payment.md) if you don't. To return funds after capture, [refund the payment](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md).

## Supported currencies and countries

Klarna supports several currencies, and the currency must match the customer's country. Through Stripe, Payrails accepts Klarna only in a fixed list of currencies. See the [Stripe guide](https://docs.payrails.com/docs/integrations/payment-methods/klarna/stripe.md).

Klarna is available to customers based in:

<table>
  <thead>
    <tr><th>Regions</th><th>Countries</th></tr>
  </thead>

  <tbody>
    <tr><td>**Asia Pacific**</td><td>🇦🇺 Australia🇳🇿 New Zealand</td></tr>
    <tr><td>**Europe**</td><td>🇦🇹 Austria🇧🇪 Belgium🇨🇿 Czech Republic🇩🇰 Denmark🇫🇮 Finland🇫🇷 France🇩🇪 Germany🇬🇷 Greece🇮🇪 Ireland🇮🇹 Italy🇳🇱 Netherlands🇳🇴 Norway🇵🇱 Poland🇵🇹 Portugal🇪🇸 Spain🇸🇪 Sweden🇨🇭 Switzerland🇬🇧 United Kingdom</td></tr>
    <tr><td>**North America**</td><td>🇨🇦 Canada🇺🇸 United States</td></tr>
  </tbody>
</table>

## Integrate Klarna

Choose the PSP that processes Klarna for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

> [card]
>
> Adyen logo
>
> AdyenKlarna via Adyen
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/klarna/adyen.md)

> [card]
>
> Klarna logo
>
> KlarnaDirect Klarna connection
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/klarna/klarna.md)

> [card]
>
> Stripe logo
>
> StripeKlarna via Stripe
>
> [Open](https://docs.payrails.com/docs/integrations/payment-methods/klarna/stripe.md)

## Check PSPs

<table>
  <thead>
    <tr><th>Workflow</th><th>[Adyen](https://docs.payrails.com/docs/integrations/payment-methods/klarna/adyen.md)</th><th>[Klarna](https://docs.payrails.com/docs/integrations/payment-methods/klarna/klarna.md)</th><th>[Stripe](https://docs.payrails.com/docs/integrations/payment-methods/klarna/stripe.md)</th></tr>
  </thead>

  <tbody>
    <tr><td>Payrails SDK</td><td>✔</td><td>✔</td><td>✔</td></tr>
    <tr><td>Payrails API</td><td>✔</td><td>✔</td><td>✔</td></tr>
    <tr><td>[Delayed / Manual Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✔</td><td>✔</td><td>✔</td></tr>
    <tr><td>[Instant Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✔</td><td>✔</td><td>✔</td></tr>
    <tr><td>[Cancel / Void](https://docs.payrails.com/docs/orchestration/payment-acceptance/cancel-a-payment.md)</td><td>✔</td><td>✔</td><td>✔</td></tr>
    <tr><td>[Refund / Reverse](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md)</td><td>✔</td><td>✔</td><td>✔</td></tr>
    <tr><td>[Save Instruments](https://docs.payrails.com/docs/resources/manage-instruments.md)</td><td>✔</td><td>✖</td><td>✔</td></tr>
    <tr><td>[Merchant Initiated Transaction (MIT)](https://docs.payrails.com/docs/resources/payments/authorization-flags.md)</td><td>✔</td><td>✖</td><td>✔</td></tr>
  </tbody>
</table>

Save Instruments and merchant-initiated transactions (MIT) work with Adyen and Stripe. The PSP returns a reference for the saved Klarna agreement, and Payrails charges later MIT payments against it without a redirect.

## Ways to integrate Klarna

* **Payrails SDK:** the [Web SDK](https://docs.payrails.com/docs/sdks/web.md) shows Klarna when your workflow returns it as a payment option, and redirects the customer to Klarna. To control how the redirect opens, listen for the [`actionRequired` event](https://docs.payrails.com/docs/sdks/web/guides/action-required-event).
* **Payrails API:** call [lookup payment options](https://docs.payrails.com/docs/orchestration/payment-acceptance/lookup-payment-options.md), then authorize with the payment method code for your PSP. The direct Klarna connection and Stripe use `klarna` with `hpp` as the `integrationType`. Adyen uses `klarnaPayLater`, `klarnaPayNow` or `klarnaPayOverTime` with `api`. Each PSP guide lists the `meta` fields that PSP requires.

In both cases, confirm the final result through [webhook notifications](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) or the execution status. Don't treat the customer's return to your `success` URL as proof of payment.


## Related topics

- [Klarna](https://docs.payrails.com/docs/integrations/dispute-providers/klarna.md)
- [Klarna via the direct Klarna connection](https://docs.payrails.com/docs/integrations/payment-methods/klarna/klarna.md)
- [Klarna via Adyen](https://docs.payrails.com/docs/integrations/payment-methods/klarna/adyen.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.