Adding Klarna payments to your application is as easy as adding a view and performing a few operations on it. You can read more about the flow here.
This guide will teach you how to:
A Payment View in iOS is called a KlarnaPaymentView. Rendering a payment view consists of creating an instance of the view, passing it an event listener and, adding it to your view hierarchy.
You can initialize the KlarnaPaymentView by providing a return URL and the event listener.
Param | Type | Description |
---|---|---|
category | String | The payment method category that should be rendered in the view. It has to be the same as the one in the response object when initiating a payment. It is usually 'klarna' . |
eventListener | KlarnaPaymentEventListener | Listener that receives events during the payment process. |
The SDK will notify you of events via an event listener that you’ll need to implement. It acts like a conventional delegate on iOS, however, unlike a delegate, it’s not optional.
The payment view does not define any height internally. This is because we want to allow you to handle height changes in whichever way is most convenient to you.
The payment view instead notifies you through the event listener you provide it.
We expose six methods on the payment view that you can use to interact with the payment method it’s presenting
Before content is rendered into a payment view, it needs to be configured. You can do this by initializing the view.
After the view has been added and set up, you’ll need to call initialize() with the clientToken you received from the back-end and a returnURL.
Param | Type | Description |
---|---|---|
clientToken | String | Token that was returned when you created the session. |
returnUrl | URL | URL schema as defined in your app’s Plist to return from external applications. |
If successful, klarnaInitialized() will be called in the listener you supplied. If it’s not successful klarnaFailed() will be called instead.
Param | Type | Description |
---|---|---|
paymentView | KlarnaPaymentView | The payment view that was initialized. |
Once you’ve initialized the view and you’re ready to display the KlarnaPaymentView.
Simply call load(), supplying an optional string with updated order data to update the session. This string should be formatted as valid JSON.
Param | Type | Description |
---|---|---|
jsonData | String | An optional string with the order data to update the session. Formatted as JSON. |
If successful, klarnaLoaded() will be called in your listener. If anything went wrong, klarnaFailed() will be called. If you’ve loaded several views, you should keep track of which view your user selected to know what to authorize in the next step.
Param | Type | Description |
---|---|---|
paymentView | KlarnaPaymentView | The payment view that was loaded. |
When the payment view is loaded, and the user has confirmed that they want to pay with Klarna it’s time to authorize the session.
When you are ready to authorize the session, call authorize(). As with load, you can supply an optional string to update the session. You can also specify whether auto-finalization should be turned off; if it is, the user may need to be prompted a second time to input data.
Param | Type | Description |
---|---|---|
autoFinalize | Boolean? | An optional flag used to turn off auto-finalization for direct bank transfer. |
jsonData | String? | An optional string to update the session. Formatted as JSON. |
If successful, klarnaAuthorized() will be called in your listener. If not, klarnaFailed() will be called.
Param | Type | Description |
---|---|---|
paymentView | KlarnaPaymentView | The payment view that was authorized. |
approved | Bool | Whether the authorization was approved or not. |
authToken | String? | If the session was authorized, the token will not be null. |
finalizedRequired | Bool | Will be true if autoFinalize was false and this payment method needs a second confirmation step. |
There are cases when you might want to allow your customer to change their order after it has been authorized (e.g. in some form of order/summary view). In these cases, if the order or customer details have changed, you’ll need to reauthorize the session.
Param | Type | Description |
---|---|---|
jsonData | String? | An optional string to update the session. Formatted as JSON |
If successful, klarnaReauthorized() will be called, and if not, klarnaFailed() will be called instead.
Param | Type | Description |
---|---|---|
paymentView | KlarnaPaymentView | The payment view that was reauthorized. |
approved | Bool | Whether the reauthorization was approved or not. |
authToken | String? | If the session was previously authorized, the token will not be null. |
If the session needs to be finalized, you’ll need to perform this last step to get an authorization token.
Call finalise() in order to get the token.
While we tend to name all finalize operations “finalize” with a “z”, all classes subclassing fromNSObjectalready have a a conflictingfinalize()method. In this specific case, we use the alternative british-english spelling.
Param | Type | Description |
---|---|---|
sessionData | String? | An optional string to update the session. Formatted as JSON |
If successful, klarnaFinalized() will be called in your listener. If not successful, klarnaFailed() will be called.
Param | Type | Description |
---|---|---|
paymentView | KlarnaPaymentView | The payment view that was finalized. |
approved | Bool | Whether the user was approved on finalize or not. |
authToken | String? | If the finalization went through, the token will not be null. |
If you’d like to allow the user to review their payment after it’s authorized, this can be done in two ways:
Only specific countries are currently supported. Contact us to make sure that you can call this method.
This will load/replace the view’s content with a description of how your customer will have to perform payment.
If successful klarnaLoadedPaymentReview() will be called in your listener. If not, klarnaFailed() will be called instead.
Param | Type | Description |
---|---|---|
paymentView | KlarnaPaymentView | The payment view that dsplayed payment review. |
This will handle all the errors from the previous implementations. KlarnaPaymentError will contain the information needed to show to the user and also to handle all the states of the listener.
Param | Type | Description |
---|---|---|
paymentView | KlarnaPaymentView | The payment view that had the error. |
error | KlarnaPaymentError? | lass that contains the information (name , message , isFatal , debugDescription ) about the error. |