1.0.0 1.0.0-rc2

2.0.0

3.0.0

‘Attn.’ (if applicable). Only applicable for B2B customers.

Customer’s country. This value overrides the purchase country if they are different. Should follow the standard of ISO 3166 alpha-2. E.g. GB, US, DE, SE.

Customers family name in UTF-8 encoding.
Cannot be only numbers, must be more than 1 character.
Allowed special characters: -'’.
More information can be found [in this link](https://docs.klarna.com/klarna-payments/in-depth-knowledge/customer-data-requirements/#details-needed-per-market)

Customers given name in UTF-8 encoding.
Cannot be only numbers, must be more than 1 character.
Allowed special characters: -'’.
More information can be found [in this link](https://docs.klarna.com/klarna-payments/in-depth-knowledge/customer-data-requirements/#details-needed-per-market)

Organization name (if applicable). Only applicable for B2B customers.

Phone number. Preferably a mobile phone number.

Customer’s postal code. Validation according to [Universal Postal Union addressing system](https://www.upu.int/en/activities/addressing/postal-addressing-systems-in-member-countries.html).
E.g. 12345, W1G OPW.

Customer’s region or state - Mandatory for US and AU market. Validations according to ISO 3166-2 format, e.g. US-OH, AU-ACT, etc.

Customer’s street address. Validation according to [Universal Postal Union addressing system](https://www.upu.int/en/activities/addressing/postal-addressing-systems-in-member-countries.html). Regional formatting is required, as follows:
UK/US/FR: 33 Cavendish Square
Rest of EU: De Ruijterkade 7

Customer’s street address. Second Line. 

Customer’s Title. Allowed values per country:
UK - "Mr", "Ms"
DE - "Herr", "Frau"
AT: "Herr, "Frau"
CH: de-CH: "Herr, "Frau" it-CH: "Sig.", "Sig.ra" fr-CH: "M", "Mme" 
BE: "Dhr.", "Mevr."
NL: "Dhr.", "Mevr."

URL of the descriptive asset. Using this dynamic asset will make sure that any copy update of Klarna will automatically be propagated.

URL of the standard asset. Using this dynamic asset will make sure that any copy update of Klarna will automatically be propagated.

The content of the extra merchant data should be presented as a string inside this property. The body should be an object containing any of the keys and sub-objects described below serialized to JSON. More information on that object can be found [here](https://docs.klarna.com/api/extra-merchant-data).

The content type of the body. It is usually represented as "application/vnd.klarna.internal.emd-v2+json"

Allow merchant to trigger auto capturing.

Provide the billing address of the customer, if you have collected already. If not, then Klarna will collect the details inside the iFrame before authorization.

Promo codes - The array could be used to define which of the configured payment options within a payment category (pay_later, pay_over_time, etc.) should be shown for this purchase. Discuss with the delivery manager to know about the promo codes that will be configured for your account. The feature could also be used to provide promotional offers to specific customers (eg: 0% financing). Please be informed that the usage of this feature can have commercial implications. 

Object to provide the details of the customer making the payment.

Pass through field to send any information about the order to be used later for reference while retrieving the order details (max 6000 characters)

Used for storing merchant's internal order number or other reference.

Used for storing merchant's internal order number or other reference. The value is available in the settlement files. (max 255 characters).

Used to send in the different merchant URLs that Klarna needs at different stages of the process.

Total amount of the order including tax and any available discounts. The value should be in non-negative minor units. Eg: 25 Euros should be 2500.

The array containing list of line items that are part of this order. Maximum of 1000 line items could be processed in a single order.

Total tax amount of the order. The value should be in non-negative minor units. Eg: 25 Euros should be 2500.

The purchase country of the customer. The billing country always overrides purchase country if the values are different. Formatted according to ISO 3166 alpha-2 standard, e.g. GB, SE, DE, US, etc.

The purchase currency of the order. Formatted according to ISO 4217 standard, e.g. USD, EUR, SEK, GBP, etc.

The shipping address of the consumer. Please note that this is not needed unless the customer has explicitly chosen to enter a separate shipping address. Otherwise the billing address will be automatically cloned.

The current status of the session. Possible values: 'complete', 'incomplete' where 'complete' is set when the order has been placed.

Customer’s date of birth. The format is ‘yyyy-mm-dd’

Customer’s gender - ‘male’ or ‘female’

Last four digits of the customer's social security number. This value is available for US customers.

The customer's national identification number. This value is available for EU customers utilizing national identification numbers.

Organization entity type. Only applicable for B2B customers.

Organization registration id. Only applicable for B2B customers.

Type of customer in the session. If nothing is added, a B2C session will be the default. If it is a b2b-session, you should enter organization to trigger a B2B session.

VAT ID. Only applicable for B2B customers.

Once the customer has provided any data, updates to this object will be ignored (without generating an error).

Information about the liable customer of the order.

Used to connect customers with payment method when it is present.

URL to redirect the customer to after placing the order. This is a Klarna URL where Klarna will place a cookie in the customer’s browser (if redirected) and redirect the customer back to the confirmation URL provided by the merchant. This is not a mandatory step but a recommended one to improve the returning customer’s experience.

Generated customer token. This token will be used to create a new order for the subscription using the Create a New order using token API.

Client token to be passed to the JS client while initializing the JS SDK in the next step.

Available payment method categories for this particular session

ID of the created session. Please use this ID to share with Klarna for identifying any issues during integration.

Mobile application return URL (app scheme with no action deeplink).
 The customer will be redirected to this URL after third party redirects or redirects to the Klarna Application.
 It is expected to open the integrating mobile application in it's last state (no state changes or deeplink navigations).

URL for receiving the authorization token when payment is completed. Used for Authorization Callback.

URL of the merchant confirmation page. The consumer will be redirected back to the confirmation page if the consumer is sent to the redirect URL after placing the order. Insert {session.id} and/or {order.id} as placeholder to connect either of those IDs to the URL(max 2000 characters).

URL for notifications on pending orders. Insert {session.id} and/or {order.id} as placeholder to connect either of those IDs to the URL (max 2000 characters).

URL that will be requested when an order is completed. Should be different than checkout and confirmation URLs. Insert {session.id} and/or {order.id} as placeholder to connect either of those IDs to the URL (max 2000 characters).

Color for the border of elements within the iFrame. Value should be a CSS hex color, e.g. "#FF9900"

Color for the border of elements within the iFrame when selected by the customer. Value should be a CSS hex color, e.g. "#FF9900"

Color for the bullet points within the iFrame. Value should be a CSS hex color, e.g. "#FF9900"

Color for the texts within the iFrame. Value should be a CSS hex color, e.g. "#FF9900"

Radius for the border of elements within the iFrame.

The payment method that Klarna has authorized the customer for.

Fraud status for the order. Either ACCEPTED or PENDING. If ACCEPTED, the order could be captured. If PENDING, please wait till you receive the notification from Klarna in the notification URL that the order has been approved. You can find additional information [here](https://docs.klarna.com/payments/after-payments/order-management/more-actions/pending-orders/).

Unique order ID of the transaction. This ID will be used for all order management processes.

URL to redirect the customer to after placing the order. This is a Klarna URL to which the merchant should redirect the customer to. Klarna will place a cookie in the customer’s browser (if redirected) and redirect the customer back to the confirmation URL provided by the merchant. This is not a mandatory step but a recommended one to improve the returning customer’s experience. It is a spontaneous step and does not harm the customer’s experience.

URL to an image that can be later embedded in communications between Klarna and the customer. (max 1024 characters).
 A minimum of 250x250 px resolution is recommended for the image to look good in the Klarna app, and below 50x50 px won't even show. We recommend using a good sized image (650x650 px or more), however the file size must not exceed 12MB.

Used for storing merchant's internal order number or other reference. Pass through field. (max 1024 characters)

Additional information identifying the order line item.

URL to the product in the merchant’s webshop that can be later used in communications between Klarna and the customer. (max 1024 characters)

Quantity of the order line item. Must be a non-negative number.

Unit used to describe the quantity, e.g. kg, pcs, etc. If defined the value has to be 1-8 characters.

Client facing article number, SKU or similar. Max length is 256 characters.

Tax rate of the order line. Non-negative value. The percentage value is represented with two implicit decimals. I.e 2000 = 20%.

Total amount of the order line. Must be defined as minor units. Includes tax and discount. Eg: 2000=20 euros
Value = (quantity x unit_price) - total_discount_amount. 
(max value: 200000000)

Non-negative minor units. Includes tax. Eg: 500=5 euros

Total tax amount of the order line. Must be within ±1 of total_amount - total_amount 10000 / (10000 + tax_rate). Negative when type is discount.

Price for a single unit of the order line. Must be defined as minor units and exclude any discount. Typically including taxes, however some countries may include specific requirements, see [Tax handling guidelines](https://docs.klarna.com/payments/web-payments/additional-resources/error-handling-and-validations/tax-handling/) for further details. (max value: 200000000)

Asset URLs for the payment method. Using this dynamic asset will make sure that any design update of Klarna will automatically be propagated.

ID of the payment method category to be used while loading the widget later.
The possible values are:<ul><li>klarna</li><li>pay_later</li><li>pay_now</li><li>pay_over_time</li><li>direct_bank_transfer</li><li>direct_debit</li></ul>

Name of the payment method category. These names are dynamic depending on what payment method is in the category. Using this dynamic asset will make sure that any copy update of Klarna will automatically be propagated, or any updates of included payment methods by you.

The product's brand name as generally recognized by consumers. If no brand is available for a product, do not supply any value.

The product's category path as used in the merchant's webshop. Include the full and most detailed category and separate the segments with ' > '

Color to be shown to the end customer (max 64 characters).

The product's Global Trade Item Number (GTIN). Common types of GTIN are EAN, ISBN or UPC. Exclude dashes and spaces, where possible

The product's Manufacturer Part Number (MPN), which - together with the brand - uniquely identifies a product. Only submit MPNs assigned by a manufacturer and use the most specific MPN possible

Size to be shown to the end customer (max 64 characters).

The acquiring channel in which the session takes place. Ecommerce is default unless specified. Any other values should be defined in the agreement.

Extra Merchant Data (additional information) required for additional risk check. The required parameters will be described in the appendix of contract agreement.

Design package to use in the session. This can only by used if a custom design has been implemented for Klarna Payments and agreed upon in the agreement. It might have a financial impact. Delivery manager will provide the value for the parameter.

Intent for the session. The field is designed to let partners inform Klarna of the purpose of the customer’s session.

Design customization options for the Klarna Payments iframe. The design options are limited to changing colors. It is not possible to change the font or other designs at the moment.

The payments API is used to create a session to offer Klarna's payment methods as part of your checkout. As soon as the purchase is completed the order should be read and handled using the [`Order Management API`](https://docs.klarna.com/api/ordermanagement).

**Note:** Examples provided in this section includes full payloads, including all supported fields, required and optionals. In order to implement a best in class request we recommend you don't include customer details when initiating a payment session. Refer to [Initiate a payment](https://docs.klarna.com/klarna-payments/integrate-with-klarna-payments/step-1-initiate-a-payment/) section for further details.

Read more on [Klarna payments](https://docs.klarna.com/klarna-payments/).

Klarna Payments API V1

Use this API call to cancel/release an authorization. If the `authorization_token` received during a Klarna Payments won’t be used to place an order immediately you could release the authorization.
Read more on **[Cancel an existing authorization](https://docs.klarna.com/klarna-payments/other-actions/cancel-an-authorization/)**.

authorizationToken

The authorization was cancelled successfully.

You were not authorized to execute this operation.

Use this API call to create a Klarna Customer Token.<br/>After having obtained an `authorization_token` for a successful authorization, this can be used to create a purchase token instead of placing the order. Creating a Klarna Customer Token results in Klarna storing customer and payment method details.
Read more on **[Generate a customer token](https://docs.klarna.com/klarna-payments/in-depth-knowledge/customer-token/)**.

body

We were unable to create a customer token with the provided data. Some field constraint was violated.

The data in the request does not match the session for the authorization.

Use this API call to create a new order. Placing an order towards Klarna means that the Klarna Payments session will be closed and that an order will be created in Klarna's system.<br/>When you have received the `authorization_token` for a successful authorization you can place the order. Among the other order details in this request, you include a URL to the confirmation page for the customer.<br/>When the Order has been successfully placed at Klarna, you need to handle it either through the Merchant Portal or using [Klarna’s Order Management API](#order-management-api).
Read more on **[Create a new order](https://docs.klarna.com/klarna-payments/integrate-with-klarna-payments/step-3-create-an-order/)**.

We were unable to create an order with the provided data. Some field constraint was violated.

Use this API call to create a Klarna Payments session.<br/>When a session is created you will receive the available `payment_method_categories` for the session, a `session_id` and a `client_token`. The `session_id` can be used to read or update the session using the REST API. The `client_token` should be passed to the browser.
Read more on **[Create a new payment session](https://docs.klarna.com/klarna-payments/integrate-with-klarna-payments/step-1-initiate-a-payment/)**.

We were unable to create a session with the provided data. Some field constraint was violated.

Use this API call to get a Klarna Payments session. You can read the Klarna Payments session at any time after it has been created, to get information about it. This will return all data that has been collected during the session.
Read more on **[Read an existing payment session](https://docs.klarna.com/klarna-payments/other-actions/check-the-details-of-a-payment-session/)**.

session_id

Use this API call to update a Klarna Payments session with new details, in case something in the order has changed and the checkout has been reloaded. Including if the consumer adds a new item to the cart or if consumer details are updated.
Read more on **[Update an existing payment session](https://docs.klarna.com/klarna-payments/other-actions/update-the-cart/)**.

We were unable to update the session with the provided data. Some field constraint was violated.