Accept a Klarna payment
Learn how to accept Klarna, a global buy now, pay later payment method.
Unified line items with Klarna
To optimize approval rates when you integrate with Klarna, include line_
data to represent what’s in a shopper’s cart. For early access, see Payments line items.
When a customer accepts Klarna in your app, a webview for a customer to authenticate their payment appears. The customer then returns to your app, and you can immediately confirm whether the payment succeeded or failed.
Remarque
Before you start the integration, make sure your account is eligible for Klarna by navigating to your Payment methods settings.
Set up StripeServer-sideClient-side
First, you need a Stripe account. Register now.
Server-side 
This integration requires endpoints on your server that talk to the Stripe API. Use the official libraries for access to the Stripe API from your server:
Client-side 
The Stripe iOS SDK is open source, fully documented, and compatible with apps supporting iOS 13 or above.
Remarque
For details on the latest SDK release and past versions, see the Releases page on GitHub. To receive notifications when a new release is published, watch releases for the repository.
Configure the SDK with your Stripe publishable key on app start. This enables your app to make requests to the Stripe API.
Create a PaymentIntentServer-sideClient-side
A PaymentIntent is an object that represents your intent to collect payment from a customer and tracks the lifecycle of the payment process through each stage.
Server-side 
First, create a PaymentIntent
on your server and specify the amount to collect and the currency. If you already have an integration using the Payment Intents API, add klarna
to the list of payment method types for your PaymentIntent
.
Client-side 
Included in the returned PaymentIntent is a client secret, that the client side can use to securely complete the payment process instead of passing the entire PaymentIntent object. On the client, request a PaymentIntent from your server and store its client secret.
Submit the payment to StripeClient-side
Retrieve the client secret from the PaymentIntent you created in step 2 and call the STPPaymentHandler confirmPayment: method. This presents a webview where the customer can complete the payment, which initiates a call to the completion block with the result of the payment.
Test Klarna integration
Below, we have specially selected test data for the currently supported customer countries. In a sandbox, Klarna approves or denies a transaction based on the supplied email address.
Two-step authentication
Any six digit number is a valid two-step authentication code. Use 999999
for authentication to fail.
Repayment method
Inside the Klarna flow, you can use the following test values to try various repayment types:
Type | Value |
---|---|
Direct Debit | DE11520513735120710131 |
Bank transfer | Demo Bank |
Credit Card |
|
Debit Card |
|
Failed payments 
Klarna takes into account multiple factors when deciding to accept or decline a transaction (for example, length of time buyer has been using Klarna, outstanding amount customer has to repay, value of the current order).
When the customer selects a deferred payment method, Klarna performs a risk assessment before accepting the transaction. Klarna might decline the transaction due to unsatisfactory risk assessment result, the transaction amount involved, or the customer having a large outstanding debt. As such, we recommend that you present additional payment options such as card
in your checkout flow. In these cases, the PaymentMethod is detached and the PaymentIntent object’s status automatically transitions to requires_
.
Customers are expected to complete the payment within 48 hours after they’re redirected to the Klarna site. If no action is taken after 48 hours, the PaymentMethod is detached and the PaymentIntent object’s status automatically transitions from requires_
to requires_
.
In these cases, inform your customer to try again with a different payment option presented in your checkout flow.
Klarna rate limits
API requests to Klarna are subject to additional rate limits beyond Stripe’s API-wide rate limits. These limits can differ depending on the shape of the API requests that you make. In general, if you make more than around 360 requests per minute, you may see some rate limiting in the form of responses with HTTP status code 400
or 402
. Please contact us for more details if you’re concerned that your usage may reach these levels, as Klarna may be able to increase these limits on a case by case basis.
Error messaging
Failed Klarna payments normally return one of the following failure codes. These codes show in the last_payment_error API object.
Mise en garde
Before the 2023-08-16
API version, every Klarna error reported as payment_intent_authentication_failure. Make sure your API version is up to date to see the detailed errors listed below.
Failure code | Explanation |
---|---|
payment_method_customer_decline | The customer cancelled the checkout on Klarna’s page |
payment_method_provider_decline | Klarna declined the customer’s payment |
payment_intent_payment_attempt_expired | The customer never completed the checkout on Klarna’s page, and the payment session has expired |
payment_method_not_available | An unexpected error occurred when trying to use Klarna |