Klarna Docs - Overview & Concepts

Overview & Concepts

The Mobile SDK offers a broad selection of integration options (and more are coming up!). If you’re familiar with Klarna’s products, you can head directly to each platform’s getting started guide. If not, we’ve got a few guides below to introduce you to all our options and how they work.

Klarna Mobile SDK is a must-have when using Klarna products (Klarna Payments, Klarna Checkout, On-site Messaging etc.) in mobile applications. This is mainly due to the limitations of the WebViews in both iOS and Android. The SDK lets Klarna components overcome those issues with a communication between web and native environments.

Some examples of common and critical issues when Klarna products are used in mobile apps without the SDK include:

  • Some external webpages, such as certain banks blocking WebViews, can block the purchase flow and the application as they can't be loaded at all.
  • Cookies in WebViews are handled differently compared to normal browsers and this causes additional friction during checkout. Mobile SDK provides secure and consistent returning user optimisation for these scenarios.
  • Navigation to third-party applications for authorization and authentication isn't handled out of the box with WebViews. Mobile SDK provides redirect to these applications along with redirecting the user back to the purchase flow from there when supported.

These are some of the most common issues. However, there are other issues in integrations that don't use the SDK and aren't limited to certain regions or payment methods. Thus, integrating the SDK is absolutely necessary for mobile integrations.

Aforementioned Mobile SDK benefits apply to all integrations, including payment integrations done via payment service providers(PSP), mobile applications should still prefer the SDK. For these integrations, if the PSP is providing Hosted Payment Page(HPP) solutions Hybrid integration and if it is providing inline payment solution then the Standalone Payment integration of the Mobile SDK should be preferred.


Depending on how you build your app, you might prefer a standalone or hybrid integration.

This guide will explain what these mean so you can choose the most suitable approach for your app.

Read more about standalone and hybrid integrations here.

If you’re adding Klarna Payments natively to your app, this is the guide for you.

This guide gives you an overview of how Klarna Payments works and provides a step-by-step to understand what you can do with our SDK.

Get a step-by-step for Klarna Payments here.

Our SDK makes performing a hybrid integration as easy as possible.

This guide gives you a step-by-step so you can add Klarna to your web view-based app.

Read about performing a hybrid integration here.

To provide the best possible experience to your customers, your app will need to perform certain full-screen transitions.

Here we explain what this means and provide several approaches to make your users’ experiences as amazing as possible.

Read more about how fullscreen works here.

If you are using Klarna On-Site Messaging to let your user know which payment options are available with a tailored message, this guide is for you. This guide gives you an overview of how Klarna On-Site Messaging works and how you can integrate it into your native application.

Read more about Klarna On-Site Messaging native integration.