---
title: Multi Accounts
description: Validate the One Face, One Contract principle by cross-referencing a user's facial biometrics against your operator's registration base.
canonical: https://developer.unico.io/dual-api/products/sign-up/multi-accounts
locale: en
generated_by: markdown-export
---

- [/](/)
- [Build](/dual-api/products/)
- [Sign-up](/dual-api/products/sign-up/)
- Multi Accounts

**On this page# Multi Accounts

Part of Fraud Risk ClassificationThis product relies on the [Multi Accounts](/capabilities/multi-accounts) capability, part of the [Fraud Risk Classification](/capabilities/fraud-risk-classification) product. It is enabled in your API Key configuration during onboarding with Unico.
### What this product solves​

Detect whether a facial biometric is already associated with another active account in your operator's base — the "One Face, One Contract" principle. With a single API call, cross-reference the captured face against your registration base and block duplicate accounts at the point of action.
**Use this product when:**

The user attempts to execute an action (request the **first withdrawal, cash-out**) and you want to validate whether that biometric already belongs to another active account in your system.
You need to perform **[retroactive ingestion of a historical base](/resources/reprocessing)** of selfies to identify existing duplicates (batch mode). This is the Biometric Base Import flow.
Your business model requires each individual to have **at most one active account per operator** (or per country).
You want to reduce the load on the **manual video review desk**, replacing human analysis with an automatic and deterministic decision.

**Do not use this product when:**

You need to validate the authenticity of an identity document → look at the [onboarding products](/products/sign-up/).
You need to confirm that the person performing the transaction is the account holder (1:1 verification) → look at the [step-up authentication products](/products/step-up-authentication/).
Your product allows multiple accounts per person by design (e.g., personal and business accounts) — in that case, discuss it with your Unico contact: the search can be segmented so that those account types are not detected as duplicates.

### Capabilities involved​

Pipeline executed within a single process:
[Liveness](/capabilities/liveness)[Multi Accounts](/capabilities/multi-accounts)
CapabilityRequiredRole in the flow**Liveness**Optional for API; required for Web and NativeLiveness check at capture time.[Multi Accounts](/capabilities/multi-accounts)RequiredPerforms segmented biometric search in the operator's base, cross-referencing the received face against all records in the same segment.
### Prerequisites​

**Bearer token** — see [Authentication](/dual-api/developers/api-reference/authentication).
**Sandbox credentials** — see [Environments](/dual-api/developers/api-reference/environments).
**SDK or Web component installed** — only for Web and SDK integrations. See [SDKs and Tools](/developers/sdks-and-tools/overview).
**Multi Accounts capability enabled in your API Key.**
**`clientReference` field filled in all requests** — uniquely identifies the user in the operator's system. Must be unique in the client's database, have a maximum of 256 characters and contain no spaces. This field is the primary identifier for Multi Accounts purposes.

### Step-by-step implementation​

NativeWebAPIIntegration via native SDK — capture runs inside your app using the Unico SDK for Android, iOS or Flutter.

**Install the SDK** — add the Unico SDK dependency for your platform. See the setup guide for [Android](/developers/sdks-and-tools/android/requirements), [iOS](/developers/sdks-and-tools/ios/requirements) or [Flutter](/developers/sdks-and-tools/flutter/requirements).
**Create a process** — call [Create Process](/dual-api/developers/api-reference/web-sdk/post-process) with the appropriate `flow` value and the user's identifier. Use the returned `token` to initialize the SDK.
**Start the capture** — the SDK renders the camera UI and performs liveness detection on-device, returning the captured payload.
**Query the result** — call [Get Process](/dual-api/developers/api-reference/web-sdk/get-process) to retrieve the capability results.
**Apply business rules** — evaluate the response fields to approve, deny or escalate.

AndroidNative Android SDK for in-app capture.[View overview](/developers/sdks-and-tools/android/requirements)iOSNative iOS SDK for in-app capture.[View overview](/developers/sdks-and-tools/ios/requirements)FlutterCross-platform Flutter SDK for in-app capture.[View overview](/developers/sdks-and-tools/flutter/requirements)Integration via iFrame, Redirect or Native — Unico hosts the capture UI, and you receive the result via polling.

**Create a process** — call [Create Process](/dual-api/developers/api-reference/web-sdk/post-process) with the appropriate `flow` value and the user's identifier. The response includes a `userRedirectUrl`.
**Redirect the user** — send the user to `userRedirectUrl`. Unico renders the capture journey. Or `webAppToken` in native apps.
**User completes the journey** — after capture, the user is redirected back to your `callbackUri`.
**Query the result** — call [Get Process](/dual-api/developers/api-reference/web-sdk/get-process) to retrieve the capability results.
**Apply business rules** — evaluate the response fields to approve, deny or escalate.

WebQuick integration via browser, no installation needed.[View overview](/developers/sdks-and-tools/web)Direct API integration — capture the selfie using the [Unico SDK](/developers/sdks-and-tools/overview) or your own UI following the [Capture Standard](/developers/sdks-and-tools/capture-standard), then send the image directly to the Unico API.

**Capture the selfie** — use the [Unico SDK](/developers/sdks-and-tools/overview) for your platform, or build your own UI following the [Capture Standard](/developers/sdks-and-tools/capture-standard), to obtain a selfie image that meets liveness requirements.
**Create a process** — call [Create Process](/dual-api/developers/api-reference/api/post-processes) with the user's identifier and the selfie as `imagebase64`; the executed capabilities are defined by your API Key configuration.
**Query the result** — call [Get Process](/dual-api/developers/api-reference/api/get-process) to retrieve the capability results.
**Apply business rules** — evaluate the response fields to approve, deny or escalate.

APIFull control over the flow with back-to-back integration.[View overview](/developers/api-reference/post-processes)Last updated on Oct 8, 2026**