The future of onboarding – a comprehensive application integrated into the partner’s system
12/09/2024
Customer onboarding and the process experience – how can UX prevent process abandonment?
12/11/2024
Web and mobile onboarding SDK – the basis for simple integration with partner applications
Digital Gateways opens up a wide range of possibilities for its partners regarding the onboarding of customers and the signing of contracts with them. Our solutions are easily integrated into the companies' mobile and web applications, so that their users can go through one consistent process without feeling like they are using separate tools. A consistent user experience when completing paperwork online influences whether they choose to continue working with a business. This is all made possible by using integration with the mobile and web SDK for different operating systems.
What is an SDK?
SDKs (Software Development Kits) are tools that enable the development of applications for a specific platform or integration with a specific system. SDK libraries extend the capabilities available in companies' applications with additional services - for example, the payment function in web shop applications. In the case of DG, they allow solutions to be used to verify identities, sign contracts and carry out other processes directly in partners' existing applications. This implementation approach comes with many benefits for companies opting for onboarding components. To fully understand its benefits, it is worth taking a look at what mobile and web SDK integration entails.
Mobile and Web SDK – characteristics
The choice between mobile and web SDK depends on the characteristics of the application and the needs of the company and end customers. So how do the two solutions differ? Let's see what distinguishes them.
Mobile SDK
- Integrates directly with native applications and those created with multiplatform frameworks.
- Allows full access to device features such as the camera or NFC.
- Opens up multiple avenues for securing applications - code obfuscation (obfuscation) for third parties, monitoring of code changes, support for native authentication mechanisms (Face ID, Touch ID for iOS, biometric authentication for Android, as well as code change control and requirements for user consent to grant access to the camera or microphone, among others).
Web SDK
- The library is embedded directly on the partner's website.
- This allows quick integration with web applications without the need to install separate mobile apps.
- Provides easy access to tools, albeit with limited access to native device capabilities. Does not offer as wide a range of features as the mobile SDK.
Integration of the Mobile SDK and Web SDK
The Mobile SDK and Web SDK integration processes have been designed with simplicity and efficiency in mind. These solutions provide all the necessary tools for the user to go through the entire onboarding process without leaving the application, and for the company to easily connect our services to its system. What does this look like in practice?
Mobile SDK for iOS
Step 1. Loading Package Specs
Requires uploading podspecs files to a private pod repository.
Step 2. Adding Private Repository Source
Requires adding private repository source to the Podfile.
Step 3. Adding Precompiled Pod
Requires adding precompiled KYC.precompiled pod to the Podfile.
Step 4. Installing Dependencies Using CocoaPods
After the Podfile configuration, it is needed to install all the dependencies, including the KYC framework, coming from your private repository.
Mobile SDK for Android
Step 1. Embedding the SDK
The relevant SDK package must be embedded in the project, which means importing the library into the project. This requires indicating the access data to the repository.
Step 2. SDK initialisation
After importing the SDK library, initialise the SDK in the application using the initializeSdk method.
Step 3. Generation of the authorisation code
The mobile app will initiate the verification process by sending an authorisation code (authCode) generated by the partner's backend to the verification server, which authorises the session and starts the video verification.
Step 4. Sending verification results
Once the process is complete, the application will receive the verification result in the form of a push notification. The SDK will automatically inform the partner's app that the session is complete, allowing the system to move on to the next steps, such as confirming the identity or directing the user to another part of the app.
Web SDK
Step 1. Importing the script
Initiation of the process will start with the import of the SDK script into the website.
Step 2. Preparing the HTML block
Next, the HTML element in which the SDK will place the video-verification component should be prepared. This block can be placed anywhere on the page. Our SDK is fully flexible and allows you to match the colour scheme, style and graphical elements to the design of your partner's site, so that the integration is consistent and fits in with the look of the site.
Step 3. Generation of the authorisation code
The partner backend generates a one-time authorisation code (authCode), which it will pass on to the site. This will initiate video verification. Importantly, the SDK library automatically recognises whether it has been run on a mobile device or on a desktop. If run on a desktop, the user will be prompted to continue the process on the mobile device, as smartphone cameras typically offer better image quality, which is crucial for video verification.
Step 4. Sending verification results
Once the video verification is complete, the SDK closes the process and the verification result is passed as a callback to the partner's system, allowing further action on the site.
Onboarding without SDK
Integration by Web and Mobile SDK enables onboarding solutions to be embedded directly into a company's system. This is used in situations where the business only wants to extend the capabilities of the tool used so far. In some cases, on the other hand, an application form for specific processes or even dedicated applications needs to be created from scratch.
What are the benefits of this approach?
- For such solutions, SDK integration is not required. Our onboarding services are part of them from the start.
- Partners get a ready-made tool with verification functionalities prepared according to their needs.
- In this case, the development team has more opportunities related to the optimisation of the application.
- It eliminates even the smallest system delays caused by data transfer between the system and external onboarding services.
Summary
Digital Gateways offers flexible and comprehensive onboarding solutions, enabling companies to easily integrate with mobile and web applications. Customers can choose to integrate via the Mobile SDK or Web SDK, depending on their needs. In both cases, the video verification process is seamless, without the need to leave the app or website. Importantly, DG gives businesses complete freedom of choice. Businesses can use SDK integration to extend the capabilities of their existing applications, or use off-the-shelf verification tools without integration. This allows each business to choose the optimal solution, tailored to its processes and needs.
