Mitek SDK: integration experience
PreviousUserflow integration as an onboarding and customer feedback toolNextUsing Web Workers in React Applications: Performance Optimization and Resource Management
Last updated
Last updated
The Mitek SDK would be a set of tools, libraries, and documentation that developers can use to integrate Mitek's technology into their own applications. This may include features such as capturing images of documents (like ID cards, driver's licenses, or checks) using a mobile device's camera, extracting information from those documents, and verifying the authenticity of the documents.
We integrated the Mitek SDK into our application to enhance the speed and security of diverse cryptocurrency transactions. To confirm different actions, we employed two types of verification:
Face verification through the camera.
Voice verification utilizing the microphone.
Additionally, we implemented a sequential process combining face and voice verification for added security.
The Mitek SDK encompasses numerous functions crucial for installation and verification processes. Let's break down the key actions involved in establishing verification using the SDK:
Initialization of Mitek SDK
Granting/Receiving Browser or Device Access for Camera Usage. Ensure the application obtains the necessary permissions or grants access to the camera on the device or browser, enabling the capture of images.
Capturing a Face Photo According to Recommendations. Prompt the user to capture a photo of their face following Mitek's recommendations for optimal verification.
Confirmation and Saving in the Event of a Successful Image on the Mitek Side.
To successfully complete the verification process, the following steps need to be undertaken:
Initialization of mitek SDK.
Grant Access to the Camera.
Capture a Picture According to Recommendations. Prompt the user to capture a photo following recommended guidelines for optimal verification.
Comparison of Pictures on the mitek Side.
Processing the Result of Comparing Two Pictures.
These sequential actions constitute the essential steps to navigate through the verification process, from initializing mitek SDK to processing the final result of comparing two pictures, which we receive from mitek side.
In general, I can attest that integrating with Mitek is a straightforward process, with comprehensive details readily available in the company's provided documentation.
However, one nuance emerged during our implementation. The SDK's functionality primarily targets mobile devices, as advised by the company itself. Our initial design, on the other hand, was crafted to incorporate both voice and face recognition functionalities on desktops as well. The aim was to achieve a unified implementation across all device types.
Face validation presented no challenges, as we effortlessly supplied the container ID (indicating the location of the camera element) to a dedicated function.
For voice recognition, a minor obstacle arose as we couldn't directly pass the container ID. Consequently, the microphone ID was initialized for the entire screen. Given our project's use of the React framework, the camera container was positioned outside the root element.
Fortunately, a straightforward solution was identified. We consistently employ modal windows for all device installations or verifications, ensuring they are centered both vertically and horizontally on the screen. Applying the same approach to the microphone container involved centering it, applying styles, and incorporating indents based on the modal content.
It's important to note that while effective for our specific circumstances, this solution may not be universally applicable.
Book a quick sync up with our CTO if you need a helping hand or visit our website:
