Sumsub’s MobileSDK (Software Development Kit for mobile applications) is a set of tools that helps you integrate specific features into your mobile application with minimal coding. Without MobileSDK, the integration process becomes much harder, as you need to manually build and test each step separately for iOS and Android. Instead of creating required tools from scratch, you can configure our MobileSDK to fit your particular workflow.

How Sumsub MobileSDK works

Our MobileSDK allows you to verify applicants directly through your mobile application using a built-in Sumsub widget that you can customize based on your preferences.

Applicants go through all verification steps in your app on their mobile device, while Sumsub handles every stage by collecting, processing, and verifying all the provided data and documents. Once the verification is complete, you receive a final status update on the process. The MobileSDK also configures interaction with device hardware components, managing access to the camera, microphone, geolocation, and more.

With Sumsub MobileSDK solution, you can optimize conversion rates and enjoy effortless integration, with attention to every detail on our part.

MobileSDK configuration

You can configure our MobileSDK solution for the following:

• Native applications (MobileSDK for iOS, Android) — if you have separate versions of your app for iOS and Android, the MobileSDK is integrated for each platform individually.
• Cross-platform applications (MobileSDK via a framework) — if you have a single codebase for your app that works on both iOS and Android (built using a cross-platform framework), the MobileSDK is integrated through a one mobile plugin for both platforms.

📘

Note

Make sure to review our MobileSDK updates policy to keep your integration up to date.

Get started with MobileSDK

To get started with the MobileSDK integration:

1. Set up a verification level.
2. Generate an access token associated with:
   1. userId— a user identifier in your system.
   2. levelName — the verification level name that you set in Step 1. This restricts access to a specific applicant and informs the SDK what verification level will be used for the process.
3. Choose a platform—iOS SDK or Android SDK—or use mobile frameworks, such as Cordova plugin, React native module, and Flutter plugin.