Your project is progressing, and you possess all the keys to comfortably establish a comparison between the different providers of automated identity verification solutions on the market? If it is not already the case, you can cast an eye over our article “How to properly choose your automated identity verification service?”.
Some preferences might now take shape as for your solution provider selection, but
- what will happen once your choice is made?
- How will the tool be implemented into your applications?
- How much time will this integration require?
- How is the implementation organised?
The various steps mentioned below will help you in obtaining more details about the proceeding of the solution integration into your products and services. To obtain a clearer view, or simply to deepen your understanding of familiar concepts, discover the 6 steps to implement ID verification solution.
Implement ID Verification Solution – Steps Overview
- Project launch: the Kick-Off
- Technical documentation sharing
- POC (Proof Of Concepts) integration and the test phase
- Integration of the final Identity Verification solution
- Production launch
- Continuous optimisation of the solution
Whether you are part of a regulated sector or wish to improve your processes (user onboarding, fraud prevention…) having an Identity Verification Solution embedded in your web or mobile app is a must have.
How can you get the most out of your ID&V provider?
Follow these steps for an efficient integration and make your settings successfull.
Estimate time frame: 50 days
Project launch: The kick-off
The kick-off is an essential step since it is the relationship entry point with the different provider representatives, as well as the project scope definition. The kick-off consists in discussing in greater depth your expectations regarding the identity verification solution, to better adapt the latter to your needs.
This scoping phase include three principal concerns:
-Define the representatives and their role in the project deployment.
– Ensure the quality of the project implementation via a shared and precise description of the solution expected.
– Understand and adapt to the functional specificities and limit the risks.
To do so, various representatives assist you:
– a sales representative, with whom you have already discussed the expected services,
– a dedicated Customer Success Manager,
– as well as a Product Owner when needed.
Each of them, within the framework of its competences, will go along the project with you. This is in sight of refining your expectations and directing your decisions regarding the characteristics of the solution.
The Customer Success Manager takes care of the business needs, the technical integration of the solution into your applications as well as its smooth operation.
The Product Owner is available to illustrate the product characteristics and express its vision in terms of forecast development linked to the product roadmap. This will lead to the collection of potential future needs that could be integrated into your solution.
Ultimately, the Sales Representative typically remains your preferred intermediary and is primarily by your side for contractual aspects. You are therefore in relation with a multidisciplinary team, purposely allowing you to have a clearer and more complete vision of the solution.
ID Verification provider – Technical documentation
Following the precise definition of the project framework, let us now get to the heart of the matter. We mentioned in our previous article “How to choose an identity verification service” that the technical aspect of a solution is fundamental, and this is still accurate!
SDK, API, Liveness or even NFC cheap reading, the technical documentation provides you with essential information to integrate the identity verification solution.
More specifically, it explains:
– the recognized documents,
– the languages available,
– the documents control points,
– the onboarding process, etc.
A quick tip for the developers: do not hesitate to ask for Postman collections as a support for the implementation.
The documentation also explains the different additional services provided with the solution, such as the personalisation, the possible integrations or the data processing.
Apart from the technical documentation, which provides theoretical knowledge, you can access a non-personalised test account of the solution. This account allows you to have a vision on the practicality of the tool, in addition to the theoretical information.
In order to achieve this, you simply have to provide a group of authentics and fraudulent documents that will be verified by the tool. You will thereby have a concrete vision of the solution and obtain the fraud detection ratio and the rate of document information extraction. They both enable the measure of the service reliability and performance.
In this way, you possess all the technical information necessary to refine and adapt your demand, allowing you to take the next step.
POC (Proof Of Concept) integration and Test phase
The POC step is one of the most important in the process of the identity verification solution integration. Indeed, it allows you to implement a first version of the solution, according to what you defined during the definition of the project scope.
This version can then be continuously adjusted until the final integration, and even after.
With this POC, you access an intermediary step called the “AB testing”.
It consists precisely in making the access to the solution available to a limited number of current service users, thanks to the integration of a POC.
From the choice of colors to the desired functionalities, going through the order of the steps, this version is entirely configured according to the predefined needs.
The purpose of this test phase is to try in real conditions the solution with your users, without integrating it to your entire activity. It allows you to anticipate and avoid potential unpleasant surprises.
You are accompanied by your CSM along the step, to define the best workflow for the services use. After this POC, the results of the solution can also be analysed.
This step allows for some adjustments or irregularities corrections, related to the business or the technical aspect. It is somehow the key to success for an optimal and successful final integration.
It takes around 2 weeks to perform this step. The POC integration accounts for 5 days and the testing time is traditionally done afterwards, in around ten days.
Implementation of the Final Solution
Once the test phase is done, and the results are in coherence with your expectations, it is now time to integrate the final solution into your applications.
To do so, various means are available:
– native integration into applications,
– cross-platforms frameworks Cordova,
– iOnic, or Flutter,
– or even direct integration of REST APIs.
You select the more adapted language according to your processes and infrastructures.
Keep in mind that if you choose to integrate a document capture tool, also named SDK (Software Development Kit), the integration is not the same. Indeed, the SDK requires a front end integration, which is the visible part of the web or mobile application, in addition to the back end integration on a server.
Unlike the API, which requires a unique integration on the back end, the SDK integration is slightly more complex.
No problem, the technical teams support you during all the integrations and guarantee an optimal implementation into your applications. Moreover, a consequent panel of documentation as well as code specificities in many languages are at your disposal.
On top of that, this integration step represents the opportunity to answer to your exigences in terms of security.
Plan a week to perform this final integration.
That’s it! We are approaching the end of the process, your identity verification solution is (nearly) ready!
You scoped your expectations and specific needs with the provider, you performed the A/B testing and then, you integrated the solution into your applications.
Once all the necessary steps are finalised, the provider has to perform what is called the production.
This stage consists in configuring the solution by creating your account in the production infrastructure. This is the ultimate step to implement your solution in its final hosting place.
The launch of the production is composed of two principals challenges:
– Make a stable solution that meets the expectations.
– Accompany the users to take the solution in hand and appropriate the tool.
It is indeed a technical step which simply means that the solution is functional and ready to be used, and that it will be permanently controlled by the provider.
This production launch is usually done in a week, to enable the rapid activation of the solution.
In cases you diagnose a problem or incoherences during the beginning of the service use, your CSM is at your disposal to remedy it and make the solution work in the best possible conditions for your final users.
Continuous Optimisation of the Solution
Ultimate step of the process, which is not really a step as it is merely maintaining the smooth operation of the identity verification solution.
The provider will ensure the solution is working correctly on a technical aspect and will provide you with a personalised support. You will benefit from frequent meetings to exchange about the operation of the solution as well as its potential evolutions.
This step is composed of three essential concerns:
– Make the most of a functional and technical assistance.
– Benefit from new functionalities.
– Make the tool evolve according to the needs and expectations.
In the capacity of a solution user, you also benefit from reporting that allows you to follow the activity of the solution. Various key performance indicators, more commonly called KPIs, offer you the possibility to measure the use of the identity verification service.
These various indicators include the following points:
– Amount of analysis performed
– Acceptance percentage on the total amount of analysis
– The average time of analysis
– Customer completion rate, which is in short an indicator to know if the solution allows an increase in your conversion rate.
These KPIs can be established during the launch of the production and then be adapted according to the uses of the service.
In addition, think about checking the SLA (Service Level Agreement) of the provider.
The latter represents the commitment of the provider toward your company, and it will provide you with the availability rate of the solution for the final users.
For example, you could find a commitment of 99,5% of availability, meaning that the provider agrees on a margin of 0,5% of unavailability to set up updates and patches (Indeed, there is unfortunately no such a thing as zero risk!).
Do not hesitate to ask your provider for the Business Continuity Planning to know the processes implemented when facing a critical situation.
Ultimately, the product owner is also included in the monitoring process of your project. His main role is to present the product news and the production planning. If you are interested in the new functionalities, you can review your contract and add them to your personalised solution.
In this way, you benefit from both technical and functional support, from the beginning of the project to the routine use.
So, ready to implement your ID verification solution?
After having read this article, you understand the integration of an identity verification solution incorporates various fundamental steps.
From the expression of your needs, to the integration, going through the test phase, the process can seem lengthy, but it is necessary for the smooth integration of the solution. To ensure the solution is integrated in the best way, you benefit from genuine support from the first step to the final one, with the common goal of assuring your satisfaction.
If you are planning on implementing an identity verification solution, please contact us. It is with pleasure that we will exchange on your project and the expectations you have.