In this section, you will find a description of all the capabilities of the Unico IDCloud platform
Below, you will find a detailed explanation of how each capability works:
hen there is a need to verify that a person is real and alive at the time of the operation, this capability can be used either in isolation or in conjunction with the capabilities of Identity Verification, Fraud Profile Detection, Risk Scoring, and Validation (1:1). It should always be used alongside the SDKs. The possible responses are:
YES: indicates that the user is alive at the time of the selfie capture.
NO: indicates that the user is not alive at the time of the selfie capture.
Commonly referred to as IDLive or Smartlive/Liveness with Interaction.
When there is a need to ensure that the user performing the process is who they claim to be, this capability is typically used in conjunction with the Proof of Life capability. The possible responses are:
YES: indicates that the face matches the actual holder of the CPF (Cadastro de Pessoas Físicas).
NO: indicates that the face does not match the actual holder of the CPF.
INCONCLUSIVE: indicates that there is insufficient evidence to determine whether the face matches the actual holder of the CPF.
Commonly referred to as IDUnico.
Fraud Profile Detection complements the Identity Verification response by adding a behavioral component that provides certainty regarding the 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.
INCONCLUSIVE: indicates that there is insufficient evidence to determine whether the face has been involved in fraudulent transactions in our database.
Commonly referred to as Trust or IDTrust.
When there is a need to obtain a probability score regarding whether the user performing the process is who they claim to be, this capability can only be used in orchestration with the Identity Verification capability when its 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 matches the actual holder of the CPF (Cadastro de Pessoas Físicas).
Zero Score: indicates that there is an error in the registration. A new capture is recommended.
Negative Score: can range from -10 to -100. The lower the score, the greater the probability that the face does not match the actual holder of the CPF.
Commonly referred to as Check or Unico Check.
When there is a need to recognize whether the person in the operation is the same one who completed the registration, this capability is typically used in conjunction with the Proof of Life capability.
It can only be used in cases where an Identity Verification process has already been performed. The possible responses are:
YES: indicates that the face performing the transaction is the same as the one that completed the registration.
NO: indicates that the face performing the transaction is not the same as the one that completed the registration.
Commonly referred to as Biometric Token or Transactional Token.
When there is a need to request, store, and reuse documents, we offer the ability to leverage users' personal documents (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.
Commonly referred to as IDDOCS.
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. See more in the Possible Flows section.
Commonly referred to as SIGN or IDSIGN.
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 as follows:
Commonly referred to as IDSerpro.
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 Help Center.
| Classification | Score | Recommendation |
|---|---|---|
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
Liveness
Identity Verification
Fraud Profile Detection
Risk Scoring
Validation (1:1)
Document capture and reuse
Electronic signature
+Serpro similarity return