General usage recommendations
Always communicate through a server
Your mobile/web app must always talk to your own server and never directly with the Assure API.
Subscribe to Assure Events
It is recommended to subscribe to Assure Events to be notified when the result is available (either successfully or not). For more information, see Assure Events.
Save useful information and clean up afterwards
After an identity verification result is obtained, save any information that is useful for you on your side (check the Service details section for auxiliary services that help you do that).
If the verification was accepted, you can even download a Zip file containing the full result.
Also, when you are finished using a process/dossier (and kept the important information on your side), delete the process and/or the dossier.
The information in the Assure API will be deleted after a period of time, regardless you explicitly requested for it to be deleted or not. Please refer to the Signicat Identity Verification privacy statement for details.
Recommended paths for electronic identity document verification (eIDV)
The following flow chart presents all possible paths to integrate with the Assure API.
Assure flow
Here are some recommended paths:
Full control and flexibility
The recommended integration path is A > B > C > D1 > E > F. Only this path allows you to integrate with any provider in any environment. Also, since the provider's SDK is used to capture and upload the images, it is more likely you will obtain a better quality of the final result.
No frontend
An alternative path is A > B > C > D2 > E > F. The advantage is that you do not have to integrate with the provider's SDK. However, this option is only available to use with Onfido and PictureID. Since the ID images are not captured using the provider's SDK, the verification result may suffer.
Easy integration using hosted Javascript SDK
Another alternative path is A > G > F. This path uses the Assure API's Start capture flow service which encapsulates the providers' JS SDKs. This means the images are captured using the provider's SDK, which may lead to a better quality of the final result.
Read more about paths
For more detailed information about specific paths, see