Capabilities
In this section, you will find a description of all the capabilities of the Unico IDCloud platform
Atualizado
Isto foi útil?
English (United States)
In this section, you will find a description of all the capabilities of the Unico IDCloud platform
Atualizado
Isto foi útil?
Below, you will find a detailed explanation of how each capability works:
When there is a need to verify if the person is real and alive at the time of the operation, it can be used either independently or in conjunction with the capabilities of Identity Verification, Behavior Alert, Risk Score, and Validation (1:1). It should always be used in conjunction with the SDKs.
The possible responses are:
YES: indicates that the user is alive at the moment the selfie is captured.
NO: indicates that the user is not alive at the moment the selfie is captured.
When there is a need to ensure that the user performing the process is who they claim to be, it is by default always used in conjunction with the Liveness capability.
The possible responses are:
YES: indicates that the face belongs to the actual holder of the CPF (Cadastro de Pessoas Físicas).
NO: indicates that the face does not belong to the actual holder of the CPF.
INCONCLUSIVE: indicates that there is insufficient evidence to determine whether the face belongs to the actual holder of the CPF.
The Behavior Alert complements the Identity Verification response by adding the behavior component, which provides certainty about a risk associated with that identity, based on previous fraudulent behavior. It can only be used in conjunction with the Identity Verification capability.
The possible responses are:
YES: indicates that the face has been involved in fraudulent identity transactions.
SUSPICIOUS: indicates that the face has had at least one occurrence in our database with a different identifier.
INCONCLUSIVE: indicates that there is insufficient evidence to suggest that the face is involved in fraudulent transactions in our database.
The Risk Score capability is being deprecated and can only be used in exceptional cases. To verify the eligibility of your case, please contact the person responsible for your account.
When there is a need to obtain a probability score about whether the user performing the process is who they claim to be, it can only be used in orchestration with the Identity Verification capability when the response is "INCONCLUSIVE."
The possible responses are:
Positive Score: can range from +10 to +100. The higher the score, the greater the probability that the face belongs to the actual holder of the CPF. (Cadastro de Pessoas Físicas).
Zero Score: indicates a registration error. We recommend a new capture be taken.
Negative Score: can range from -10 to -100. The lower the score, the greater the probability that the face does not belong to the actual holder of the CPF.
Negative
Between -40 and -100
We recommend denying the registration
Negative
Between -10 and -39
We recommend that the client assess the associated risks before making a decision
Neutral
Zero Score
We recommend denying the registration and asking the user to capture a new photo of the actual holder of the CPF
Positive
Between +10 and +49
We recommend that the client evaluate the risks involved in making a decision
Positive
Between +50 and +100
We recommend approving the registration
When there is a need to recognize if the person in the operation is the same one who completed the registration, it is by default always used in conjunction with the Liveness capability. It can only be used in cases where an Identity Verification process has already been completed.
The possible responses are:
YES: indicates that the face performing the transaction is the same as the one that completed the process used as a reference.
NO: indicates that the face performing the transaction is not the same as the one that completed the process used as a reference.
When there is a need to request, store, and reuse documents, we offer the ability to leverage users' personal documents (Passport, CIN, RG, and CNH—both digital and physical), reducing friction. If we do not have the documents in our database, it is possible to capture them.
This capability can only be used in conjunction with the Identity Verification capability. For document validation, we use the following technologies:
Typification: indicates whether the provided document is valid or not.
OCR: involves extracting data from the document based on an image.
FaceMatch: involves comparing the face in the selfie with the face on the document.
CPF Match: involves searching for a specific CPF in the provided document.
When there is a need to use biometrics to sign a document, utilize the same method of user authentication throughout the journey to finalize the operation with the contract signature.
*The electronic signature capability is only available through the by Unico integration mode in flows that involve other capabilities.
The Serpro similarity return is not a native capability of IDCloud but rather an additional feature incorporated to comply with a regulation from Dataprev concerning INSS payroll credit operations aimed at retirees and pensioners.
Since these operations require the SERPRO similarity return, the IDCloud platform has been adjusted to include this functionality as an option in the product. When using the SERPRO similarity feature, the API response will be the score of similarity.
When Serpro finds the face, it returns a score from 0-100, as in the example below:
When Serpro does not find the face, the score -1 is returned, as in the example below:
When there is an error in the integration with Serpro, the score -2 is returned, as in the example below:
To understand how you can use each of the capabilities, be sure to visit the "Integration Methods" section at the link below:
Still need help?
Didn't find something or still need help? If you're already a client or partner, you can reach out through our .
Liveness
Identity Verification
Behavior Alert
Risk Score
Validation (1:1)
Document Capture and Reuse
Electronic Signature
+Serpro similarity return