by Unico vs by Client
When to use each model
Ideal when you want to outsource the complete validation journey.
Ideal when you need greater visual control and user experience.
You only send the user's identification document number; Unico handles the interface, data capture, UX flow and security.
You already capture selfie / data on the client (app/web) or via SDK.
Overview and Comparison
It is possible to integrate with the Unico IDCloud platform through two integration methods: by Unico and by Client. Understand below the main differences between them.
User journey
Managed by Unico.
Managed by the client (local UI or Unico SDK).
Input data
You create the process only with the number of the user's identification document+ flow with capabilities that it will use.
You create the process with the user's identification document number + selfie in base64 (or in JWT if you use Unico's SDK).
Output data
The service returns a link in the API response, which can be sent to the user via WhatsApp/SMS OR rendered in your application.
The service returns in the response the payload of the performed validation.
Response type
Validation is asynchronous, that is, when generating the link and making it available to the end user, it is necessary to wait for them to complete the journey, then, fetch through a GET endpoint the process response.
Validation is synchronous for almost all capabilities - except for the Risk Score (if there is a derivation to the Risk Score, it will be necessary to use the GET endpoint to obtain the final response).
Available Capabilities
Identity Verification
Risk Score
Behavior Alert
Liveness
Validation (1:1)
Smart Revalidation
Reuse and Document Capture
Electric Signature
Serpro similarity return
Last updated
Was this helpful?