Serpro Similarity ReturnCapability specific to payroll loans (INSS) and operations that require comparison against the Serpro database. Returns a similarity score between the captured selfie and the photo on file at Serpro.
What it does
The capability triggers a comparison between the session selfie and the Serpro photo associated with the provided CPF. Returns a score from 0 to 100 when the comparison is possible, or special codes (-1, -2) when Serpro can't find the face or the integration with Serpro fails.
Inputs
- A capture session opened via
POST /v1/processwith a flow that includes Serpro Similarity. - The user's CPF.
- Prior tenant enablement for the Serpro capability (negotiated with the Unico Onboarding team).
Possible responses
| Response | Meaning |
|---|---|
| Score 0–100 | When Serpro finds the face. The higher the score, the higher the similarity. |
| Score -1 | Serpro could not find a face associated with the CPF. |
| Score -2 | Integration error with Serpro — the score could not be obtained. |
They are signal codes for distinct scenarios. Treating them as if they were a zero score leads to wrong decisions.
Availability
| Surface | Supported |
|---|---|
| SDK (Android, iOS, Flutter) | ✅ |
| Web (iFrame, Redirect) | ✅ |
| API (headless, no SDK) | ✅ |
Even on the supported surfaces, the tenant needs to be enabled for the Serpro capability. Contact Unico's Onboarding team if your operation does not yet have access.
Valid combinations
Serpro Similarity appears in flows that include serpro or are specific to payroll loans:
idcheckserpro, idcheckserprodocs, idcheckserprodocssign, idunicoserprodocssign, creditoconsignado.
For the full matrix, see Available flows.
Use cases that use this capability
Behavior inside creditoconsignado
The creditoconsignado flow branches the journey based on Serpro's return:
- Serpro positive → goes straight to electronic signature.
- Serpro negative (-1, or low similarity) → requests documents for facematch.
- Facematch positive → proceeds to signature.
- Facematch negative → the journey ends without signature.
This conditional behavior is part of the flow — it does not require orchestration on your back-end.