Klarna is a payment provider allowing consumers to pay using their payment methods saved to their Klarna account. This section is intended to help you implement Klarna based on your preferred integration workflow.

Services and compatibility

Gateway-specific information

Klarna does not support merchant-initiated transactions for a subscription or payment plan. For that feature, you must integrate with PayPal (with Braintree).

However, Klarna does support Pay Later messaging, which acts like a subscription or payment plan from the customer point of view. For details, see the Pay Later messaging topic.

Nexio supports the following countries and regions for the customer's billing country with Klarna:

• Australia (AU)
• Austria (AT)
• Canada (CA)
• Denmark (DK)
• Finland (FI)
• Germany (DE)
• Great Britain (GB)
• The Netherlands (NL)
• New Zealand (NZ)
• Norway (NO)
• Sweden (SE)
• Switzerland (CH)
• United States (US)

🚧

Important

Klarna has to enable each individual billing country in order for the merchant to accept payments from that country.

The merchant needs to go through Klarna’s underwriting process and the merchant needs to contract with Klarna directly for the merchant to provision a production merchant ID (MID) with the payment methods for the region that the merchant wants to process. Only the payment methods approved and contracted with Klarna and the merchant will be the ones available at checkout for the consumer.

You can display the payment popup page to the customer in a supported language. To do so, the values for the data.locale, data.currency, and data.customer.billToCountry must match. For information about how they need to match, see the Purchase country, locale, and currency page in the Klarna documentation.

Configuration

Apart from working with Integrations Support to add Klarna as a payment method, you do not need to do any other configuration steps. In order to add Klarna, Integrations Support needs your Klarna username, password, and clientID.

If you want to add Pay Later messaging to the merchant site, see the Pay Later messaging topic.

Required fields

The following table shows the required and optional fields for Klarna transactions in the Create APM one-time-use token request.

Example requests

The following are example one-time-use token requests for Klarna for the iframe integration methods:

curl -X POST https://api.nexiopaysandbox.com/apm/v3/token \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -H 'Authorization: Basic [Base64_encoded_login]'
  -d '{
  "data": {
    "amount": 4.00,
    "currency": "USD",
    "locale": "en-US",
    "customer": {
      "orderNumber": "12345678",
      "firstName": "John",
      "lastName": "Doe",
      "email": "[email protected]",
      "billToCountry": "US"
      "billToAddressOne": "2147 West Silverlake Drive",
      "billToCity": "Scranton",
      "billToState": "PA"
      "billToPostal": "18503",
      "billToPhone": "1555555555"
    },
    "cart": {
      "items": [
        {
          "item": "E200",
          "description": "Platinum set",
          "quantity": 2,
          "price": 2,
          "type": "sale",
          "imageUrl": "http://www.example.com/images/e200.gif",
          "productUrl: "http://www.example.com/products/e200.html"
        }
      ]
    },
    "paymentMethod": "klarnaPayments"
  }
}'

curl -X POST https://api.nexiopaysandbox.com/apm/v3/token \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -H 'Authorization: Basic [Base64_encoded_login]'
  -d '{
  "data": {
    "amount": 4.00,
    "currency": "USD",
    "locale": "en-US",
    "customer": {
      "orderNumber": "12345678",
      "firstName": "John",
      "lastName": "Doe",
      "email": "[email protected]",
      "billToCountry": "US"
    },
    "cart": {
      "items": [
        {
          "item": "E200",
          "description": "Platinum set",
          "quantity": 2,
          "price": 2,
          "type": "sale",
          "imageUrl": "http://www.example.com/images/e200.gif",
          "productUrl: "http://www.example.com/products/e200.html"
        }
      ]
    },
    "paymentMethod": "klarnaCheckout"
  }
}'

{
  "expiration": "2018-09-18T15:43:05.664Z",
  "token": "830d36f6-a5e3-4455-9600-3a55b63e2fc2",
  "asyncTraceId": "830d36f6-a5e3-4455-9600-3a55b63e2fc2",
  "expressIFrameUrl": "https://www.api.nexiopaysandbox.com/v3?token=830d36f6-a5e3-4455-9600-3a55b63e2fc2",
  "redirectUrls": [],
  "buttonIFrameUrls": [
    {
      "paymentMethod": "klarnaCheckout",
      "url": "https://api.nexiopaysandbox.com/apm/v3?token=830d36f6-a5e3-4455-9600-3a55b63e2fc2&paymentMethod=klarnaCheckout"
    },
    {
      "paymentMethod": "braintreePayPal",
      "url": "https://api.nexiopaysandbox.com/apm/v3?token=830d36f6-a5e3-4455-9600-3a55b63e2fc2&paymentMethod=braintreePayPal"
    }
  ]
}

For the multi iframe integration method: You use the expressIFrameUrl value in the steps for the transaction.

For the individual iframe option: You use the buttonIFrameUrls.url of the appropriate Klarna APM for the transaction.

Transaction types and integration methods

Regardless of the integration method workflow you implement, consumers are redirected to Klarna to complete their transactions.

Nexio supports the following transaction types for Klarna:

• Auth Only
• Sale
  • In an iframe that displays all payment methods available to the customer (based on the customer’s location and the merchant’s configured payment methods)
    
  • In an individual iframe
    
• Capture
• Refund

Klarna also supports Pay Later messaging. For details, see the Pay Later messaging topic.

Testing data

For testing data, see Klarna’s Testing Environment page.

Response handling

In the one-time-use token request, Klarna gets returned in the paymentMethod parameter as klarnaPayments or klarnaCheckout.

Nexio responds with transaction results in one of the following ways, depending on your integration workflow:

• Event messages: This applies to integrations that do not pass a customerRedirectUrl in the request.
• Response fields in the URL: This applies to integrations that do provide a customerRedirectUrl in the request.

In addition to one of the above, if your merchant account is configured to receive webhooks, Nexio provides responses to the webhook URLs that have been registered. For further explanation of the webhook event types, see the webhook Event types table.

For Klarna, these are the possible webhook event types:

• TRANSACTION_AUTHORIZED
• TRANSACTION_CAPTURED
• TRANSACTION_REFUNDED
• TRANSACTION_SETTLED

For information about how to run each of the integration workflows, see Transaction types and integration methods above.

Status workflows

The status of a successful transaction with Klarna varies, depending on the options you choose.

*Pending status displays as "authorized" or "AUTHORIZED" in the Nexio Dashboard; it displays as 10, meaning "authorized", in the response when querying transactions (for more information about transactionStatus, see the table).

Next steps

Now, you are ready to get started with running transactions:

• Run a sale transaction

If you have any additional questions or feedback, see Contact us.