Web SDK
There are two kinds of Web SDK:
Web SDK Core
Library for generating cryptograms from data received from the payment form. You collect payment data yourself.
Web SDK Payment
Your own payment form design on your page. Collection of payment data is performed on our side.
Read more about Web SDK Payment
Mobile SDK
There are three kinds of Mobile SDK:
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 |
Read more about Mobile SDK Core
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:
| Payment Method | Supported |
|---|---|
| Bank card | Yes |
| Stored credential/card | Yes |
| Apple Pay | Yes |
| Google Pay | Yes |
Mobile SDK 3DS2
Mobile SDK 3DS2 is the mobile-device-side component of EMV 3-D Secure.
Be aware that many ACS systems don't work properly with Mobile SDK 3DS2.
Read more about Mobile SDK 3DS2
Mobile SDK Source
iOS
Requirements: iOS 10.0 or newer
Android
Requirements: Android 5.0 or newer
Server Side SDK
Server Side SDK is a wrapper for our API and is intended for running API requests (refer to API Reference).
Read more about Server Side SDK