Web SDK

Library for generating cryptograms from data received from the payment form.
You collect payment data yourself.

Your own payment form design on your page.
Collection of payment data on our side.

Mobile SDK

There are three kinds of Mobile SDKs and 3DS2 SDK:

Mobile SDK Core
Mobile SDK Forms
Mobile SDK Payment
Mobile SDK 3DS2

Mobile SDK Core

This is more of a library than an SDK. It's used to encrypt card details into seToken, that can be safely passed and saved to any system (for example, merchant server). It's a good solution for merchants that want maximum flexibility or don't want to deal with card details on theirs servers.

Payment methods supported by this SDK:

Payment Method	Supported
Bank card	Yes
Stored credential/card	Yes
Apple Pay	No need
Google Pay	No need

Mobile SDK Forms

This SDK is responsible for rendering a UI for card details. As a result seToken is generated that can be used for payment. This kind of SDK doesn't communicate with Payment Gateway. Merchant should use seToken and Payment Gateway API to create an order and complete the payment. All kind of 3DS redirects must be handled by merchant by itself.

Payment methods supported by this SDK:

Payment Method	Supported
Bank card	Yes
Stored credential/card	Yes
Apple Pay	Yes
Google Pay	Yes

Mobile SDK Payment

This SDK not just renders a UI for card details, but also communicates with Payment Gateway API. Also it handles all 3DS redirects and can use 3DS SDK as an embedded one. It's easier for merchant to integrate payments this way, but it's not as flexible as SDK Forms or SDK Core (you can't use all the features of payment API with this kind of SDK)

Be aware that SDK Payment uses Mobile SDK 3DS2 and many issuers' ACS don't work properly with Mobile SDK 3DS2.

Payment methods supported by this SDK: