Please review this brief guide first to ensure you are prepared to offer this integration to your customers.

1. Prepare: Make sure you have the credentials and setup for Klarna Express Checkout.
2. Present the button: (Mobile App) Create an instance of KlarnaExpressCheckoutButton with session parameters and present in your native app.
3. Handle authorization: (Mobile App) Once the customer clicks the button and authorizes the payment, handle response from the SDK.
4. Create an order: (Server-side) Once a session is authorized, create an order with authorization token via your backend.

For a Mobile SDK integration your Payment Server and Mobile App must work together to offer one-click checkout experience:

The right placement of the Express button can significantly enhance your user experience, leading to higher conversion rates and increased sales.

Before you integrate Express checkout, check that you meet the following prerequisites:

1. Make sure to have a payment solution with Klarna. Before integrating Express checkout into your website, you need to have a merchant account with Klarna and Klarna payments or Klarna checkout integrated in your checkout.
2. Make sure to allowlist the domain of the page on which Express checkout will be integrated. If not all the domains are added to the allowlist, Express checkout will still load, however, the customer will see a "We couldn't load the next screen" error.

To allowlist the domain URLs, follow these steps:

• Log into Klarna Merchant portal. If you want to test Express checkout, log into the playground Merchant portal. If you want to build a live integration, log into the production Merchant portal.
• Once logged in, go to Payment settings > Client Identifiers. In the Allowed Origins for your integrations section, click Manage origins.
• In the Register new origin field, add your domain’s URL. Then, click Register. The registered domain is now listed in Allowed origins.

3. Generate a client identifier that will let you authenticate requests sent to Klarna:

• Log into Klarna Merchant portal.
• Once logged in, go to Payment settings > Client Identifiers.
• To generate a new client identifier, navigate to Client Identifiers for your integrations and click Generate client identifier.

If you’ve previously generated a client identifier for your store, you can use it to build your Express checkout integration.

Swift Package Manager

In Xcode, navigate to File → Swift Packages → Add Package Dependency and enter the repository URL: https://github.com/klarna/klarna-mobile-sdk-spm

In Version, Select Up to Next Major and take the default option. Then choose KlarnaMobileSDK in the Package Product column.

Cocoapods

If you’re using Cocoapods, you can add the SDK by adding the dependency to your Podfile:

pod "KlarnaMobileSDK"

Followed by performing:

pod install

You should then be able to import the KlarnaMobileSDK module in your workspace.

Carthage

If you’re using Carthage, you can add the SDK to your Cartfile as below:

 binary "https://raw.githubusercontent.com/klarna/klarna-mobile-sdk/master/KlarnaMobileSDK.json"

Followed by performing:

 carthage update --use-xcframeworks

You should be then able to add the XCFramework to your project.

Return URL

Klarna purchase flows might require authorizations in other applications (e.g. bank apps) or do a handover to the Klarna app. In such cases, a return URL to your application ensures seamless return to the flow in your app, hence setting up a return URL is required. It is expected that redirects to this URL should only open your application without any changes in the UI state, ensuring the customer can continue the flow prior to external navigation.

You can set up a Return URL app scheme to your application by configuring a custom URL scheme.

To avoid a Klarna specific app scheme, you can use a host in a common scheme for Klarna redirects, e.g. myApp://klarna-redirect , this can allow you to differentiate and handle these redirect in your handler.

Considering the return URL is a constant value in Constants.klarnaReturnUrl, you can handle redirects to your return URL as such:

Klarna App Queries

Klarna flows on mobile utilize Application Queries for Klarna app schemes to offer seamless app handover experience to customers. In order for the SDK to check availability of the Klarna app, we need you to enable querying Klarna app on the device by adding Klarna app schemes to LSApplicationQueriesSchemes.

This can be configured easily in XCode by going to your project setting and under "Info"(alternatively this is also available in your Info.plist file) you should see an entry list for Queried URL Schemes, this list should contain the klarna and klarnaconsent schemes:

Create an instance of the KlarnaExpressCheckoutButton when your cart page or product detail page is loaded. This ensures that the button is readily available for user interaction. Depending on your integration setup, you can create and initiate the Express Checkout button using either a Client-Side Session or a Server-Side Session:

• Client-Side Session: Use this method if you prefer to set a partner client ID from the Merchant Portal. This approach is typically used when the session management is handled entirely on the client side. You would need to provide the order details in this approach.

• Server-Side Session: Choose this method if you have a client token generated by the backend for the server-side session. This is suitable when you want to manage sensitive session data on the server. You do not need to provide the order details with this approach.

Once the button is created, add it to your screen. This involves adding the button to the appropriate view hierarchy in your application's user interface:

let options = KlarnaExpressCheckoutButtonOptions(
   sessionOptions: KlarnaExpressCheckoutSessionOptions.ClientSideSession(
        clientId: "myClientId",
        sessionData: mySessionData,
        autoFinalize: true,
        collectShippingAddress: true
    ),
   returnUrl: "myApp://",
   delegate: self,
   locale:"en-US",

KlarnaExpressCheckoutButton

KlarnaExpressCheckoutButtonOptions

KlarnaExpressCheckoutSessionOptions.ClientSideSession

KlarnaExpressCheckoutSessionOptions.ServerSideSession

KlarnaExpressCheckoutButtonStyleConfiguration

Once a customer clicks the Express Checkout button, the Klarna payment authorization process will begin. You must provide a delegate object when creating the button, which will handle Klarna's response. This delegate is essential for managing the payment flow and updating the UI based on the authorization result.

If the authorization is successful, you will receive an authorization token from the authorization response within the delegate object.

func onAuthorized(view: KlarnaMobileSDK.KlarnaExpressCheckoutButton, response: KlarnaMobileSDK.KlarnaExpressCheckoutButtonAuthorizationResponse) {
    if let token = response.authorizationToken, approved {
        // authorization is successful, backend may create order
    }
    
    if response.finalizeRequired {
        // finalize call is required, only applicable if you are setting autoFinalize to false
        // use response.clientToken to finalize
    }
}

Parameters

KlarnaExpressCheckoutButtonAuthorizationResponse

Error Callback

func onError(view: KlarnaMobileSDK.KlarnaExpressCheckoutButton, error: KlarnaMobileSDK.KlarnaError) {
   // Handle different failure scenarios by checking the error name
   if (error.name == KlarnaExpressCheckoutError.AuthorizationFailed) {
      // The authorization process has failed.
      showMessage(error.message)
   }                
   // ...
}

Parameters

KlarnaError

Represents an error that has occurred in the Klarna Express Checkout Button.

The table below lists all the different error names defined as constant values in the KlarnaExpressCheckoutButtonError:

If the session needs to be finalized, you’ll need to perform this last step to get an authorization token from your checkout confirmation screen. This can be done via KlarnaPaymentView, using the clientToken from KlarnaExpressCheckoutButtonAuthorizationResponse to initialize the view and calling finalize method of that view.

Once you have the authorization token, you can create an order. When creating the order, make sure the shipping address provided in the request matches the collected shipping address returned alongside the authorization token.

To continue with the purchase, you have to create an order in Klarna's system. This step takes place in the server side through the Klarna payments API.

To create an order for a one-time payment, send a POST request to the {apiUrl}/payments/v1/authorizations/{authorizationToken}/order endpoint and include authorization_token in the path.

For example, if the authorization_token is b4bd3423-24e3, send your request to the {apiUrl}/payments/v1/authorizations/b4bd3423-24e3/order endpoint.

{
"purchase_country": "US",
"purchase_currency": "USD",
"billing_address": {
"given_name": "John",
"family_name": "Doe",
"email": "john@doe.com",
"title": "Mr",
"street_address": "Lombard St 10",
"street_address2": "Apt 214",

A POST request to create an order for a one-time payment.

Success response

When you receive a success response, the customer gets charged and the Klarna payments session is closed.

As part of the response, you receive the following details:

• order_id, an order identifier that you can later use to capture or refund the order using the Order management API
• redirect_url, a URL to which you redirect the customer. This isn't included in the response received if you didn't include the URL when initiating a payment
• fraud_status, an indicator of whether the transaction is suspected to be legitimate or fraudulent
• authorized_payment_method, the payment method selected by your customer for this purchase

{
"order_id": "3eaeb557-5e30-47f8-b840-b8d987f5945d",
"redirect_url": "https://payments.klarna.com/redirect/...",
"fraud_status": "ACCEPTED",
"authorized_payment_method": "invoice"
}

A success response to the order creation request for a one-time payment.

Error response

If your request doesn't pass our validation, you'll receive an error response. The most common reasons why creating an order fails are:

• placing the order more than 60 minutes after authorization
• modifying purchase details after authorization without updating the payment session

{
"correlation_id": "6a9b1cb1-73a3-4936-a030-481ba4bb203b",
"error_code": "ERROR_CODE",
"error_messages": [
"ERROR_MESSAGE"
]
}

An error response to the order creation request for a one-time payment.

Here are examples of common errors with troubleshooting suggestions. You can use the value in correlation_id to find entries related to the request under Logs in the Merchant portal.

This section will help you customize the Express checkout button to ensure a seamless and trustworthy checkout experience, while leveraging Klarna’s strong brand to boost your conversions.

Styling the Express checkout button is crucial for integrating it into your application in a way that complements your brand and encourages user engagement. To modify the style of the button, edit the source code as explained in this guide.

The theme defines the button’s color. You can change the theme by setting the value of the theme attribute.

Apart from the default dark theme, you can apply the light theme to have the button displayed in white or choose auto mode so the theme is selected automatically based on the device’s configuration.

The button’s default theme color is dark. As the theme attribute is optional, the default theme is applied both when you set the attribute to default or if you omit it from the source code altogether.

There are three theme values available, dark (default), light and auto.

let buttonStyleConfiguration = KlarnaExpressCheckoutButtonStyleConfiguration(
    theme = KlarnaButtonTheme.dark,
    shape = …,
    style = …
)

ShapeCustomizing the shape of the button to match your application’s look and feel is a key step in creating a visually cohesive and engaging user experience. To control the button's shape, change the value of the shape attribute.

There are three shapes available with the Express checkout button: rounded_rect (default), rectangle and pill.

let buttonStyleConfiguration = KlarnaExpressCheckoutButtonStyleConfiguration(
    theme = KlarnaButtonShape.rounded_rect,
    shape = …,
    style = …
)

Use the outlined style to make the button visible on all backgrounds. To apply this style, set the KlarnaButtonStyle attribute to outlined, otherwise default value filled will be used instead.

let buttonStyleConfiguration = KlarnaExpressCheckoutButtonStyleConfiguration(
    style = KlarnaButtonStyle.outlined,
    shape = …,
    theme = …
)

The SDK will log events and errors while it’s running, which you can read in XCode console. You can set the logging level for the SDK through the loggingLevel property of integration instance.

klarnaExpressCheckoutButton.loggingLevel = .verbose

KlarnaLoggingLevel

Klarna Mobile SDK provides a full suite of mobile-first integrations, including Klarna products like:

Sign in with Klarna	On-site Messaging	Payments

• On-site Messaging: Show contextual messaging let your customers know about the available payment options in pre-checkout: click here to learn more.
• Sign in with Klarna: Seamlessly identify and let users login via their Klarna account: click here to learn more.
• Payments: Enhance your mobile app conversion with a seamless payment UX, click here to learn more.

Complete your integration with

• Order management
• Settlements
• End-to-end testing
• Prepare for go live