Migrate Klarna from Sources

Klarna is launching a new checkout process that requires the Payment Methods API and the Payment Intents API. This guide outlines several recommended paths to migrate from using the Sources API, including a low-code option that uses Stripe Checkout.

Initiating the Klarna payment on PaymentIntents

Completing the Klarna payment on PaymentIntents

Notable differences

• Klarna product selection: You don’t need to specify the Klarna product type in your integration. Instead, customers now choose a product on the Klarna redirect page. Don’t include a separate button on your checkout site for each supported Klarna payment option. Only include a single Klarna button.
• Klarna SDK inline display isn’t supported: Customers must now redirect to the Klarna site from your payment page to authorise the payment. As a result, you don’t need to load the Klarna SDK or render any inline components.
• Payment confirmation is synchronous in all markets: Previously, confirmation of a successful payment was asynchronous in some cases. Now, you can detect whether the payment is successful immediately after your customer authorises it.

Migrate your payment flow

To migrate your Klarna integration for web payments, you need to update your server and front end to use the PaymentIntents API. There are three typical integration options:

• Redirect to Stripe Checkout for your payment flow.
• Use the Stripe Payment Element on your own payment page.
• Build your own form and use the Stripe JS SDK to complete the payment.

Use Stripe Checkout or the Payment Element to add and manage most payment methods from the Stripe Dashboard without making code changes.

Below is a high level comparison of the old integration steps with the new integrations:

curl https://api.stripe.com/v1/payment_intents \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -d "automatic_payment_methods[enabled]"=true \
  -d amount=1099 \
  -d currency=eur

curl https://api.stripe.com/v1/payment_intents \
  -u "
sk_test_4eC39HqLyjWDarjtT1zdp7dc
:" \
  -d "automatic_payment_methods[enabled]"=true \
  -d amount=1099 \
  -d currency=eur

Field mapping reference

If you use the Payment Element or your own form, you must remap the fields previously on the Source to the PaymentIntent. The table below is a mapping of the old fields to the new fields. If you sell physical goods, we recommend that you pass shipping details. All other fields are optional, and Klarna collects necessary additional information on their page.

After the purchase

The following changes are required for any integration points you have after a payment has completed.

Checking payment status

Previously, your integration should have checked both the status of the Source and the status of the Charge after each API call. You no longer need to check two statuses – you only need to check the status of the PaymentIntent or the Checkout Session after you confirm it on the front end.

Always confirm the status of the PaymentIntent by fetching it on your server or listening for the webhooks on your server. Don’t rely solely on the user returning to the return_url that’s provided when you confirm the PaymentIntent. Read more about this here.

Refunds

You can continue to call the Refunds API with a Charge that the PaymentIntent creates. The ID of the Charge is accessible on the latest_charge parameter. Alternatively, you can provide the PaymentIntent ID to the Refunds API instead of the Charge.

Error handling

Previously, you had to handle errors on the Sources were created. In PaymentIntents, you don’t need to check for errors on a Source, and instead need to check for errors on the PaymentIntent when it’s created and after the customer has authorised the payment. Most errors on the PaymentIntent are on the type field returned in an invalid request.

Webhooks

If you previously listened to Source events, you might need to update your integration to listen to new event types. Below is a reference of the new event types to listen for.