Accept a Klarna payment

Learn how to accept Klarna, a global buy now, pay later payment method.

Web

Mobile

When a customer chooses Klarna in your app, a webview for them to authenticate their payment appears. After the customer is redirected back to your app, you can immediately confirm whether the payment succeeded or failed.

Note

Before starting your integration, check that your account is eligible for Klarna on the Payment methods settings.

Set up Stripe
Server-side
Client-side

Server-side

This integration requires endpoints on your server that talk to the Stripe API. Use our official libraries for access to the Stripe API from your server:

Client-side

The React Native SDK is open source and fully documented. Internally, it uses the native iOS and Android SDKs. To install Stripe’s React Native SDK, run one of the following commands in your project’s directory (depending on which package manager you use):

Command Line
yarn add @stripe/stripe-react-native

Next, install some other necessary dependencies:

For iOS, go to the ios directory and run pod install to ensure that you also install the required native dependencies.
For Android, there are no more dependencies to install.

Note

We recommend following the official TypeScript guide to add TypeScript support.

Stripe initialization

To initialize Stripe in your React Native app, either wrap your payment screen with the StripeProvider component, or use the initStripe initialization method. Only the API publishable key in publishableKey is required. The following example shows how to initialize Stripe using the StripeProvider component.

import { useState, useEffect } from 'react';
import { StripeProvider } from '@stripe/stripe-react-native';

function App() {
  const [publishableKey, setPublishableKey] = useState('');

  const fetchPublishableKey = async () => {
    const key = await fetchKey(); // fetch key from your server here
    setPublishableKey(key);
  };

  useEffect(() => {
    fetchPublishableKey();
  }, []);

  return (
    <StripeProvider
      publishableKey={publishableKey}
      merchantIdentifier="merchant.identifier" // required for Apple Pay
      urlScheme="your-url-scheme" // required for 3D Secure and bank redirects
    >
      {/* Your app code here */}
    </StripeProvider>
  );
}

Note

Use your API test keys while you test and develop, and your live mode keys when you publish your app.

Create a PaymentIntent
Server-side
Client-side

Stripe uses a PaymentIntent object to represent your intent to collect payment from a customer, tracking your charge attempts and payment state changes throughout the payment process.

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

A PaymentIntent includes a client secret. You can use the client secret in your React Native app to securely complete the payment process instead of passing back the entire PaymentIntent object. In your app, request a PaymentIntent from your server and store its client secret.

function PaymentScreen() {
  // ...

  const fetchPaymentIntentClientSecret = async () => {
    const response = await fetch(`${API_URL}/create-payment-intent`, {
      method: 'POST',
      headers: {
        'Content-Type': 'application/json',
      },
      body: JSON.stringify({
        currency: 'eur',
      }),
    });
    const {clientSecret} = await response.json();

    return clientSecret;
  };

  return <View>...</View>;
}

Submit the payment to Stripe
Client-side

Submitting the payment to Stripe requires the client secret from the PaymentIntent that you created. Include it in your call to confirmPayment:

import {Picker} from '@react-native-picker/picker';
import {confirmPayment} from '@stripe/stripe-react-native';

export default function MyPaymentScreen() {

  const handlePayPress = async () => {
    // Fetch the intent client secret from the backend.
    // See `fetchPaymentIntentClientSecret()`'s implementation above.
    const clientSecret = await fetchPaymentIntentClientSecret();

    const {error, paymentIntent} = await confirmPayment(clientSecret, {
      paymentMethodType: 'Klarna'
      },
    });

    if (error) {
      console.log('Payment confirmation error', error.message);
      // Update UI to prompt user to retry payment (and possibly another payment method)
    } else if (paymentIntent) {
      Alert.alert('Success', `The payment was confirmed successfully!`);
    }
  };

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.

	Approved	Denied
Date of Birth	10-07-1970	03-05-1994
First Name	Test	John
Last Name	Person-au	snow
Street	Wharf St	Silverwater Rd
House number	4	1-5
Postal Code	4877	2128
City	Port Douglas	Silverwater
Region	QLD	NSW
Phone	+61473752244	+61473763254
Email	customer@email.au	customer+denied@email.au

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	Number: 4111 1111 1111 1111 CVV: 123 Expiration: any valid date in the future
Debit Card	Number: 4012 8888 8888 1881 CVV: 123 Expiration: any valid date in the future

OptionalSeparate authorization and capture

Klarna supports separate authorization and capture. If there’s a delay between the payment and delivering the goods to your customer, authorize the payment first and capture it later. At the point of capture, Klarna sends a statement to the customer and initiates the due dates on any subsequent payments that they must make. An authorized Klarna payment must be captured within 28 days of the authorization. Otherwise, the authorization automatically cancels and you can no longer capture the payment.

Tell Stripe to authorize only
To indicate that you want separate authorization and capture, set capture_method to manual when creating the PaymentIntent. This parameter instructs Stripe to only authorize the amount on the customer’s Klarna account.
Command Line
Select a language
cURL
Stripe CLI
Ruby
Python
PHP
Java
Node.js
Go
.NET
No results
curl https://api.stripe.com/v1/payment_intents \ -u "sk_test_BQokikJOvBiI2HlWgH4olfQ2 :" \ -d "payment_method_types[]"=klarna \ -d amount=1099 \ -d currency=eur \ -d capture_method=manual
Capture the funds
After the authorization succeeds, the PaymentIntent status transitions to requires_capture. To capture the authorized funds, make a PaymentIntent capture request. The total authorized amount is captured by default—you can’t capture more than this, but you can capture less.
Command Line
Select a language
cURL
Stripe CLI
Ruby
Python
PHP
Java
Node.js
Go
.NET
No results
curl https://api.stripe.com/v1/payment_intents/{{PAYMENT_INTENT_ID}} /capture \ -u "sk_test_BQokikJOvBiI2HlWgH4olfQ2 :" \ -d amount_to_capture=750
Optional Cancel the authorization
Klarna counts any authorized payments against the customer’s total purchasing power within Klarna. Make sure that you actively cancel any authorized payments that you can’t fulfill (for example, the goods can’t be shipped) as soon as this becomes apparent.
Command Line
Select a language
cURL
Stripe CLI
Ruby
Python
PHP
Java
Node.js
Go
.NET
No results
curl https://api.stripe.com/v1/payment_intents/{{PAYMENT_INTENT_ID}} /cancel \ -u "sk_test_BQokikJOvBiI2HlWgH4olfQ2 :" \ -d cancellation_reason=abandoned

OptionalHandle post-payment events

Stripe sends a payment_intent.succeeded event when the payment completes. Use the Dashboard, a custom webhook, or a partner solution to receive these events and run actions, like sending an order confirmation email to your customer, logging the sale in a database, or starting a shipping workflow.

Listen for these events rather than waiting on a callback from the client. On the client, the customer could close the browser window or quit the app before the callback executes, and malicious clients could manipulate the response. Setting up your integration to listen for asynchronous events also helps you accept more payment methods in the future. Learn about the differences between all supported payment methods.

Handle events manually in the Dashboard
Use the Dashboard to View your test payments in the Dashboard, send email receipts, handle payouts, or retry failed payments.
Build a custom webhook
Build a custom webhook handler to listen for events and build custom asynchronous payment flows. Test and debug your webhook integration locally with the Stripe CLI.
Integrate a prebuilt app
Handle common business events, such as automation or marketing and sales, by integrating a partner application.

OptionalCustomize the Klarna payment page

Prefill the Klarna form

When the customer chooses to pay Klarna with a deferred payment option (pay later, installments, and financing), Klarna collects enough information for risk assessment and approval. The type of information depends on the country of the customer. For most countries in Europe, it’s the full billing details and date of birth. You can pass this information through the API, and the form will be prefilled when your customer arrives on the page.

Screenshot of a Klarna payment page prefilled with billing details from the API and customized to render in English

A Klarna payment page prefilled with billing details from the API and customized to render in English for a customer in Germany

OptionalAdd line items to the PaymentIntent

Unified line items with Klarna

To optimize approval rates when you integrate with Klarna, include line_items data to represent what’s in a shopper’s cart. For early access, see Payments line items.

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_payment_method.

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_action to requires_payment_method.

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.

Caution

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

Accept a Klarna payment

Learn how to accept Klarna, a global buy now, pay later payment method.

Note

Set up StripeServer-sideClient-side

Server-side

Client-side

Note

Stripe initialization

Note

Create a PaymentIntentServer-sideClient-side

Server-side

Client-side

Submit the payment to StripeClient-side

Test Klarna integration

Two-step authentication

Repayment method

OptionalSeparate authorization and capture

OptionalHandle post-payment events

OptionalCustomize the Klarna payment page

OptionalAdd line items to the PaymentIntent

Unified line items with Klarna

Failed payments

Klarna rate limits

Error messaging

Caution

Set up Stripe
Server-side
Client-side

Create a PaymentIntent
Server-side
Client-side

Submit the payment to Stripe
Client-side