Asteria-APP/Pods/KlarnaMobileSDK

Klarna In-App SDK for iOS & Android

The Klarna In-App SDK allows merchants to integrate Klarna's products into their apps natively. This means that you can add services like Klarna Payments to your app and let your customers pay with our payment methods.

Are you looking for Klarna Checkout? Check out the Klarna Checkout SDK repo instead.

Requirements

• iOS 10 or later.
• Android 4.4 or later.

Developer Documentation

• Overview
• iOS
• Android

API Documentation

• iOS
• Android

What Does Klarna In-App SDK Offer?

Klarna In-App SDK offers two integration approaches: Native integration and Hybrid integration.

Native integration allows fully native apps to add views with Klarna content to their app. We currently support Klarna Payments, allowing you to add payment views to your checkout and authorizing a session to create an order natively.

Hybrid integration will enhance your customers' experience if your app renders in a web view that presents content from Klarna.

Why should you use the SDK?

The SDK removes any possible friction in your app's checkout flow by leveraging native functionality in iOS and Android. Some of the things the SDK does are:

• Plays nicely with 3rd-party apps. Many customers complete their purchase through their banking application or other 3rd-party apps. We make this experience seamless not just by opening these apps but also automatically returning your users when they're done.
• Safeguards your users' identity. The SDK adds an extra layer of security, lowering the risk of fraudulent purchases. It also ensures that your customer doesn't have to write in any redundant info. (e.g., address or credentials) on successive purchases.
• Improves 3D Secure flow. If certain payment methods require opening banking pages, we'll display an in-app browser. Your customer can safely authenticate with their bank without ever leaving your app.
• Open links without making your customers leave your app. As with 3D Secure, we open most resources in an in-app browser or a fullscreen overlay. This ensures that your customer doesn't ever have to leave your app.

Overview

Native Integration

As previously mentioned, Klarna Payments supports native integration. The main idea behind Klarna Payments is to give merchants the ability to offer Klarna's payment methods to customers. Because Klarna doesn't own the entire checkout flow, a check must be performed before an order is created. Our goal with this integration is to offer you the same simple development experience as you have on the web. As such, integrating Klarna Payments consists of four steps:

1. Creating a session.
2. Rendering the payment view.
3. Authorizing the session.
4. Creating an order.

Hybrid Integration

Our iOS and Android SDKs hold weak references to your web views, don't override any part of your implementation or modify your web views in any way. Because of this, we ask you to perform some minor integration work to make your users' experience as pleasant as possible. This consists of four steps:

1. Initialization.
2. Adding web views to the SDK.
3. Notifying the SDK when something occurs in the web view.
4. Handling events from the SDK.

iOS Integration

These are our iOS-specific guides for the In-App SDK. We currently have guides to get you started, to integrate Klarna Payments, and to perform a hybrid integration.

Getting Started and Integration Guides

Android Integration

These are our Android-specific guides for the In-App SDK. We currently have guides to get you started, to integrate Klarna Payments, and to perform a hybrid integration.

Getting Started and Integration Guides

React Native Integration

Guide for React Native

Demo Apps

Native Integration

• iOS Demo App

• Android Demo App

Hybrid Integration

• iOS Demo App

• Android Demo App

Changelog

See full changelog

Deprecated Integration Guides

If you are using an older version of the SDK (<2.0.0), you should refer to these integration guides, and if you want to migrate to 2.0.0 or above, you can use the Migration Guide to see what has changed.

iOS

• Native Integration Guide
• API Documentation

Android

• Android Native Integration Guide
• API Documentation

Library Binaries

AAR Files

AAR files for the Android SDK can be found publicly on our CDN. These files are structured for each version hence in order to get the files url path needs to be changed with the version number.

• https://x.klarnacdn.net/mobile-sdk/com/klarna/mobile/sdk/version/sdk-version.aar
• https://x.klarnacdn.net/mobile-sdk/com/klarna/mobile/sdk-full/version/sdk-full-version.aar

E.g. for Android SDK version 2.0.24 it is https://x.klarnacdn.net/mobile-sdk/com/klarna/mobile/sdk/2.0.24/sdk-2.0.24.aar

Contributing

Support

If you are having any issues using the SDK in your project or if you think that something is wrong with the SDK itself, please create an issue on Github or report a bug by following the guidelines in the next section.

How can I contribute?

Thank you for reading this and taking the time to contribute to Klarna In-App SDK! Below is a set of guidelines to help you contribute whether you want to report a bug, come with suggestions or modify code.

Reporting Bugs

This section will guide you through submitting a bug report for Klarna In-App SDK.

Before submitting a bug report, please check that the issue hasn't been reported before. If you find a Closed issue that seems to describe an issue that is similar to what you want to report, open a new issue and link to the original issue in the new one. When you have checked that the issue hasn't been reported before, please fill out the required template which will help us resolve the issue faster.

Submitting a Bug Report

Submitted bugs are tracked as GitHub issues. To report a bug, create an issue and use the template to provide information about the bug. Explain the problem thoroughly and include any additional information that you think might help the maintainers reproduce the issue. When creating the GitHub issue please make sure that you:

• Use a clear and descriptive title for the issue.
• Describe the exact steps which reproduce the problem with as many details as possible. It's generally better to provide too much than too little information.
• Describe the behavior you observed after following the steps and explain precisely what the problem is with that behavior.
• Explain which behavior you expected instead and why.
• Provide screenshots and/or screen recordings that might help explain the issue you are facing. To screen record a phone connected to Android Studio or an emulator, follow the steps here. To screen record on iOS, follow the steps described here.
• Include relevant logs in the bug report by putting it in a code block, a file attachment or in a gist and provide a link to that gist.
• Tell how recently you started having the issue. When was the first time you experienced the issue and was it after updating the SDK version? Or has it always been a problem?
• If the problem started happening recently, can you reproduce it in an older version of the SDK? What's the most recent version in which the problem doesn't happen?
• Can you reliably reproduce the issue? If not, explain how often it occurs and under what conditions it usually happens. For example, in what environment you are running.

Include details about the device/emulator/simulator you are experiencing the issue on:

• Which version of the SDK are you using?
• Which OS is this a problem in, iOS, Android or both? What version(s)? Also, add the appropriate label to the issue.
• Did you experience the issue in simulator/emulator or on real device(s)?

Contributing to Code

Before contributing, please read through the Klarna In-App SDK documentation.

Branching

Prefix the branch you are going to work on depending on what you are working on (bug fix or feature). Use the following prefixes when creating a new branch:

• feature/ if the branch contains a new feature, for example: feature/my-shiny-feature.
• bugfix/ if the branch contains a bug fix, for example: bugfix/my-bug-fix.

Pull Requests

When creating a PR, please include as much information as possible about the type of enhancement, whether if it's a bugfix, new functionality, or any other change. There's a template for you to fill out, which will make the review process for the maintainers faster. When creating a PR do it against the master branch. The PR should include:

• A clear and descriptive title.
• Description of the issue if you are fixing a bug together with a link to the relevant issue or background for introducing a new feature.

License

Copyright 2018 Klarna Bank AB

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.