Step 3: Create an order

The process of creating an order is different for one-time and recurring payments.

• For one-time payments, get the authorization token ready and send a request to Klarna API.
• For recurring payments, generate a customer token prior to placing the order.

To create an order for a one-time payment, send a POST request to the {apiUrl}/payments/v1/authorizations/{authorizationToken}/order endpoint and include authorization_token in the path.

For example, if the authorization_token is b4bd3423-24e3, send your request to the {apiUrl}/payments/v1/authorizations/b4bd3423-24e3/order endpoint.

{
    "purchase_country": "US",
    "purchase_currency": "USD",
    "billing_address": {
        "given_name": "John",
        "family_name": "Doe",
        "email": "john@doe.com",
        "title": "Mr",
        "street_address": "Lombard St 10",
        "street_address2": "Apt 214",

Success response

When you receive a success response, the customer gets charged and the Klarna payments session is closed.

As part of the response, you receive the following details:

• order_id, an order identifier that you can later use to capture or refund the order using the Order management API
• redirect_url, a URL to which you redirect the customer. This isn't included in the response received if you didn't include the URL when initiating a payment
• fraud_status, an indicator of whether the transaction is suspected to be legitimate or fraudulent
• authorized_payment_method, the payment method selected by your customer for this purchase

{
    "order_id": "3eaeb557-5e30-47f8-b840-b8d987f5945d",
    "redirect_url": "https://payments.klarna.com/redirect/...",
    "fraud_status": "ACCEPTED",
    "authorized_payment_method": "invoice"
}

Error response

If your request doesn't pass our validation, you'll receive an error response. The most common reasons why creating an order fails are:

• placing the order more than 60 minutes after authorization
• modifying purchase details after authorization without updating the payment session

  {
      "correlation_id": "6a9b1cb1-73a3-4936-a030-481ba4bb203b",
      "error_code": "ERROR_CODE",
      "error_messages": [
          "ERROR_MESSAGE"
      ]
  }

Here are examples of common errors with troubleshooting suggestions. You can use the value in correlation_id to find entries related to the request under Logs in the Merchant portal.

Pending fraud status

If your agreement with Klarna allows it, we can flag a suspicious transaction for an additional review instead of accepting it immediately. In such cases, fraud_status in the response will be PENDING instead of ACCEPTED. Read more about pending orders.

{
    "order_id": "3eaeb557-5e30-47f8-b840-b8d987f5945d",
    "redirect_url": "https://payments.klarna.com/redirect/...",
    "fraud_status": "PENDING",
    "authorized_payment_method":"invoice"
}

Automatic capture of created orders

If your Klarna contract allows automatic capture of the order once an order is created, set auto_capture to true when creating the order.

For recurring payments, you have to create a customer token before placing the order. This token identifies your customer and the payment method selected for the purchase. It also lets you charge the customer later, ad-hoc or at regular intervals.

For payments where you charge the customer at checkout and enable a recurring charge (intent set to buy_and_tokenize), you have to send two separate create order requests:

1. In the first request, use authorization_token to charge the customer at checkout.
2. In the second request, use customer_token for future recurring payments.

If you're not charging the customer at checkout (intent set to tokenize), you need to send only the second request to place the order and charge the customer at a later date.

If you're creating an order related to a subscription, include the subscription object in your create order request. Learn more about sharing subscription details with Klarna.

Request a customer token by sending a POST request to the {apiUrl}/payments/v1/authorizations/{authorizationToken}/customer-token endpoint.

Include the authorization token from the authorize() call as the authorizationToken path parameter.

{
    "purchase_country": "US",
    "locale": "us-US",
    "billing_address" : {
        "given_name": "Doe",
        "family_name": "John",
        "email": "john@doe.com",
        "phone": "333444555",
        "street_address": "Lombard St 10",
        "postal_code": "90210",

Success response

In response to the customer token request, Klarna sends:

• token_id, a customer token identifier that you later use to create an order
• redirect_url, a URL to which the customer is redirected after the order is placed

{
    "billing_address": {
        "city": "Beverly Hills",
        "country": "US",
        "email": "john@doe.com",
        "family_name": "Doe",
        "given_name": "John",
        "phone": "333444555",
        "postal_code": "90210",
        "region": "CA",

Error response

If Klarna can't create a customer token based on the data you sent, you'll receive an error response.

{
    "correlation_id": "6a9b1cb1-73a3-4936-a030-481ba4bb203b",
    "error_code": "ERROR_CODE",
    "error_messages": [
        "ERROR_MESSAGE"
    ]
}

Here are examples of common errors with troubleshooting suggestions. You can use the value in correlation_id to find entries related to the request under Logs in the Merchant portal.

To charge the customer at checkout, send a POST request to the {apiUrl}/payments/v1/authorizations/{authorizationToken}/order endpoint. Include the authorization token as a path parameter.

For example, if the authorization_token is b4bd3423-24e3, send your request to the {apiUrl}/payments/v1/authorizations/b4bd3423-24e3/order endpoint.

Include subscription details in the subscription object. These should match the details you previously shared with Klarna when initiating the payment session.

{
    "purchase_country": "US",
    "purchase_currency": "USD",
    "billing_address": {
        "given_name": "John",
        "family_name": "Doe",
        "email": "john@doe.com",
        "title": "Mr",
        "street_address": "Lombard St 10",
        "street_address2": "Apt 214",

Success response

In response to a create order call, you receive:

• order_id, an order identifier that you can later use to capture or refund the order using the Order management API
• redirect_url, a URL to which you redirect the customer. This isn't included in the response received if you didn't include the URL when initiating a payment
• fraud_status, an indicator of whether the transaction is suspected to be fraudulent
• authorized_payment_method, the payment method selected by your customer for this purchase

{
    "order_id": "3eaeb557-5e30-47f8-b840-b8d987f5945d",
    "redirect_url": "https://payments.klarna.com/redirect/...",
    "fraud_status": "ACCEPTED",
    "authorized_payment_method": "invoice"
}

Error response

If your request doesn't pass our validation, you'll receive an error response. The most common reasons why creating an order fails are:

• placing the order more than 60 minutes after authorization
• modifying purchase details after authorization without updating the payment session

  {
      "correlation_id": "6a9b1cb1-73a3-4936-a030-481ba4bb203b",
      "error_code": "ERROR_CODE",
      "error_messages": [
          "ERROR_MESSAGE"
      ]
  }

Here are examples of common errors with troubleshooting suggestions. You can use the value in correlation_id to find entries related to the request under Logs in the Merchant portal.

Send a POST request to the {apiUrl}/customer-token/v1/tokens/{customerToken}/order endpoint and include the customer token as a path parameter.

For example, if the token_id is 0b1d9815-165e-42e2-8867-35bc03789e00, send your request to the {apiUrl}/customer-token/v1/tokens/0b1d9815-165e-42e2-8867-35bc03789e00/order endpoint.

Make sure to also include subscription details in the subscription object. These should match the details you previously shared with Klarna when initiating the payment session.

{
    "merchant_reference1": "45aa52f387871e3a210645d4",
    "merchant_data": "optional string",
    "locale": "de-DE",
    "auto_capture": true,
    "purchase_currency": "EUR",
    "order_amount": 999,
    "order_tax_amount": 0,
    "order_lines": [{
        "type": "digital",

Success response

In response to a create order call, you receive:

• order_id, an order identifier that you can later use to capture or refund the order using the Order management API
• fraud_status, an indicator of whether the transaction is suspected to be fraudulent

{
    "order_id": "a89ec121-1276-419d-882a-c343d58fd1bc",
    "fraud_status": "ACCEPTED"
}

Error response

If your request doesn't pass our validation, you'll receive an error response.

{
    "error_code" : "ERROR_CODE",
    "error_messages" : ["Array of error messages"],
    "correlation_id" : "Unique id for this request used for troubleshooting."
}

Here are examples of common errors with troubleshooting suggestions. You can use the value in correlation_id to find entries related to the request under Logs in the Merchant portal.