Security News
ESLint is Now Language-Agnostic: Linting JSON, Markdown, and Beyond
ESLint has added JSON and Markdown linting support with new officially-supported plugins, expanding its versatility beyond JavaScript.
react-native-klarna-inapp-sdk
Advanced tools
This library wraps Klarna's In-App SDK and exposes its functionality as React Native components. It currently supports Klarna Payments via a Payment View component.
This repository also includes a test application that you can use to see how it works.
$ npm install react-native-klarna-inapp-sdk --save
$ react-native link react-native-klarna-inapp-sdk
Libraries
➜ Add Files to [your project's name]
node_modules
➜ react-native-klarna-inapp-sdk
and add KlarnaPaymentView.xcodeproj
libKlarnaPaymentView.a
to your project's Build Phases
➜ Link Binary With Libraries
Cmd+R
)<android/app/src/main/java/[...]/MainApplication.java
import com.klarna.KlarnaPaymentViewPackage;
to the imports at the top of the filenew KlarnaPaymentViewPackage()
to the list returned by the getPackages()
methodandroid/settings.gradle
:
include ':react-native-klarna-inapp-sdk'
project(':react-native-klarna-inapp-sdk').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-klarna-inapp-sdk/android')
android/app/build.gradle
:
compile project(':react-native-klarna-inapp-sdk')
Both the iOS and Android integrations depend on the native SDK.
We've experienced issues with React Native 59 and above where 3rd party Gradle repositories won't
be recognized in the Android project's build.gradle
. To address this, you'll need to add a
reference to the repository in your own app's build.gradle
.
You can do it by adding the lines between the comments below:
allprojects {
repositories {
mavenLocal()
google()
jcenter()
maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
url "$rootDir/../node_modules/react-native/android"
}
// Add the lines below vvv
maven {
url 'https://x.klarnacdn.net/mobile-sdk/'
}
// Add the lines above ^^^
}
}
You can import the KlarnaPaymentView
from the library. You'll then be able to add it as a
component to your app. This component exposes callbacks as props and methods you can call via the
compoent's ref.
The view will self-size height-wise and grow it fill it containing view's width.
It has the following props:
Name | Type | Description |
---|---|---|
category | String | The payment method category you want to render in your view. |
onInitialized | () => {} | The initialize call succeeded. |
onLoaded | () => {} | The load call succeeded. |
onLoadedPaymentReview | () => {} | The load payment review call succeeded. |
onAuthorized | ({}) => {} | The authorize call succeeded. |
onReauthorized | ({}) => {} | The reauthorize call succeeded. |
onFinalized | ({}) => {} | The finalize call succeeded. |
onError | ({}) => {} | An error occurred. |
The onAuthorized
, onReauthorized
, onFinalized
and onError
will provide an object (via
nativeEvent
) with the following parameters:
Boolean
Determines whether the previous operation was successful and yielded an authorization token.
onAuthorized
onReauthorized
onFinalized
String | undefined
If authorize()
, reauthorize()
or finalize()
succeeded, they will return a token you can submit
to your backend.
onAuthorized
onReauthorized
onFinalized
--
Boolean | undefined
If authorize()
requires that you additionally call finalize()
, .
onAuthorized
Object | undefined
If a method failed, onError()
will let you know via an error object.
onError
Each payment view exposes a set of methods via a view's ref. You can see in the test app or in the below example how these can be called. The methods are the following:
Initializes the view with a session token. You have to have added the view to your application and supplied a payment method category.
Name | Type | Description |
---|---|---|
sessionToken | String | The session token you get from Klarna. |
returnUrl | String | An app-defined URL scheme the component uses to return customers to your app. |
You can read more about how the return URL works and how to add it tou your iOS application here and for your Android application here.
Loads the view. This will render content in the view.
Name | Type | Description |
---|---|---|
sessionData | `String | undefined` |
Renders a description of the payment terms your customer has agreed to.
Once a session is authorized, you can then either render a payment review in the existing
payment view or initialize()
a new payment view with the same session token and call this method.
This only works with specific payment methods and countries.
Authorizes the payment session.
Name | Type | Description |
---|---|---|
autoFinalize | `String | undefined` |
sessionData | `String | undefined` |
If the details of the session (e.g. cart contents, customer data) have changed, call this to update the session and get a new authorization token.
Name | Type | Description |
---|---|---|
sessionData | `String | undefined` |
If a specific payment method needs you to trigger a second authorization, call finalize when you're ready.
Name | Type | Description |
---|---|---|
sessionData | `String | undefined` |
You can read more about refs and how they're used here. If you'd like to understand what each method does, you can read about it on Klarna Developers.
In addition to the test app in /TestApp
, the you can see an abridged version below.
import KlarnaPaymentView from 'react-native-klarna-payment-view';
class MyCheckoutView extends React.Component {
constructor(props) {
super(props);
this.state = {
paymentViewLoaded: false
};
}
componentDidMount() {
// To initialize the component, you'll need call the component's initialize method with your
// backend's session token and a return URL for your application.
//
// This should occur at some point when the payment view is added to your application's view,
// but it should only be repeated if initialization fails.
this.refs['my_ref'].initialize('my_session_token', 'my_apps_return_url')
}
onInitialized = () => {
// Once the view is initialized, you can render content into it.
this.refs['my_ref'].load()
}
onLoaded = () => {
// Once the view is loaded, the user should be able to see the payment method. They can then
// choose to use it (it's up to you to determine how that is recognized) and tap a "buy-like"
// button.
this.setState({paymentViewLoaded: true})
}
buyButtonPressed = () => {
// When the button is tapped, call authorize() on the view.
this.refs['my_ref'].authorize()
}
onAuthorized = (event) => {
// If successfully authorized, the authorization token can be used by your backend to create
// an order.
//
// You can also load a payment review view to allow the user to evaluate their
// payment choice.
let params = event.nativeEvent
if (params.authorized) {
submitAuthToken(params.authToken)
}
}
render() {
return(
// Other parts of the view
// ...
// The payment view
<KlarnaPaymentView
category={'pay_later'}
ref={'my_ref'}
onInitialized={this.onInitialized}
onLoaded={this.onLoaded}
onAuthorized={this.onAuthorized} />
// ...
// Your buy button
<Button
disabled={!this.state.paymentViewLoaded}
onPress={this.buyButtonPressed} />
);
}
}
[1.0.10] - 2020-03-04
No such property: username for class: java.lang.String
build issue for Android.FAQs
This library wraps Klarna Mobile SDK and exposes its functionality as React Native components.
We found that react-native-klarna-inapp-sdk demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
ESLint has added JSON and Markdown linting support with new officially-supported plugins, expanding its versatility beyond JavaScript.
Security News
Members Hub is conducting large-scale campaigns to artificially boost Discord server metrics, undermining community trust and platform integrity.
Security News
NIST has failed to meet its self-imposed deadline of clearing the NVD's backlog by the end of the fiscal year. Meanwhile, CVE's awaiting analysis have increased by 33% since June.