Multi Accounts
Multi Accounts asks "does this face already exist somewhere else in the operator's base?".
Multi Accounts is a capability of the Fraud Risk Classification product. It is not contracted separately: it is enabled in your API Key configuration during onboarding with Unico.
What it does
Performs a segmented 1:N biometric search in the operator's base, cross-referencing the received face against all records associated with the same clientReferenceSegment. Detects whether the biometric is already linked to a different clientReference — indicating that the same person has created, or is attempting to create, multiple accounts with the same operator.
Inputs
- The user's selfie — in API integrations you send it as
imageBase64(PNG, JPEG, or WebP; minimum 640×480; maximum 800 KB); in Web integrations the capture is performed by Unico. clientReference(subject.clientReferencein API) — required. Unique identifier of the user in the operator's system: unique in your base, maximum of 256 characters, no spaces.
Possible responses
| Response | Meaning |
|---|---|
YES | Multi-account detected. The facial biometric is already linked to a different clientReference within the same segment. |
NO | Multi-account not detected. The person was identified and the face is not linked to any other clientReference within the same segment. |
INCONCLUSIVE | The evaluation could not reach a conclusion — for example, the person could not be identified or the selfie did not pass the liveness check. It does not mean that no duplicate exists. |
This table represents the individual response of the capability.
INCONCLUSIVE is not an approvalAn INCONCLUSIVE result means the evaluation could not reach a conclusion. It does not confirm that the person has no other accounts — handle it according to your risk policy.
Availability
| Integration components required |
|---|
| API Web or SDK |
On every surface the capability requires the user's clientReference in the request and enablement in your API Key.
In the Web & Native contract response, authenticationInfo.accountFarmingResult reports the multi-account (account farming) evaluation when the capability is enabled for the client:
TRUST_RESULT_YES: other accounts were found for the same person.TRUST_RESULT_NO: the person was identified and no other accounts were found.TRUST_RESULT_INCONCLUSIVE: the evaluation could not reach a conclusion, for example because the person could not be identified or the selfie did not pass the liveness check. This is not an approval, and it does not mean that no duplicate exists. Handle it according to your risk policy.TRUST_RESULT_UNSPECIFIED: no evaluation was performed for this process, for instance when the process ended before the authentication step.
It is a dedicated field — it is not combined with authenticationInfo.identityFraudstersResult, which corresponds to a different Fraud Risk Classification evaluation.
In API integrations, Liveness is optional. If you send images without a liveness check, the 1:N search runs over an unverified capture (for example, a photo of a photo) and the result inherits that risk. We recommend enabling Liveness in the same process, or capturing with the Unico SDK following the Capture Standard.
Search scope
The search scope is controlled by the clientReferenceSegment field, configured by Unico in your API Key during onboarding — it is not a field you send in the request. Distinct segments can coexist within a single operator without triggering false positives (useful for B2B sub-clients or models with personal and business accounts); if your operation needs to segment the search, discuss it with your Unico contact.