> For the complete documentation index, see [llms.txt](https://help.checkoutchamp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.checkoutchamp.com/crm/gateway-setup/gateway-integrations/adyen-v2/klarna-on-adyenv2.md).

# Klarna on AdyenV2

<figure><img src="/files/i7YYSTAyRC7POiPROOZ1" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
This document is for a direct API integration with CheckoutChamp. If you are using CheckoutChamp hosted pages then follow these [instructions](/crm/gateway-setup/gateway-integrations/klarna.md).
{% endhint %}

{% hint style="danger" %}
**Disclaimers:**

No card details are stored for merchants using Klarna’s Payment Gateway

Klarna will work for one-time purchases and rebills.

Klarna works with landers that connect to CheckoutChamp via Direct API. Klarna is not available with form-code or via Order Entry.
{% endhint %}

{% hint style="warning" %}
Make sure Klarna is enabled on your Adyen Account
{% endhint %}

&#x20;

**STEP 1**

Set up your Adyen V2 gateway. Follow instructions [here ](/crm/gateway-setup/gateway-integrations/adyen-v2.md)for setup.

Note the ID of the gateway on the gateway list page for use in Step 2.\ <br>

**STEP 2**

The checkout page must be secure HTTPS. A non-secured call to Klarna will be rejected. Pass the following parameters on the Import Order or Import Upsale API call

* paySource = PREPAID
* prepaidType = KLARNA
* forceMerchantId = the AdyenV2 id from Step 1

&#x20;

{% hint style="info" %}
Your checkout pages must support standard merchant redirect handling

[Basic 3DS Instructions](/crm/gateway-setup/direct-api-3ds-instructions.md)
{% endhint %}

{% hint style="info" %}
For more info on the api call, please refer to our [API Documentation](https://apidocs.checkoutchamp.com/).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.checkoutchamp.com/crm/gateway-setup/gateway-integrations/adyen-v2/klarna-on-adyenv2.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.