Multi Accounts

Markdown

Part of Fraud Risk Classification

This product relies on the Multi Accounts capability, part of the 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 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.
• You need to confirm that the person performing the transaction is the account holder (1:1 verification) → look at the step-up authentication products.
• 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:

LivenessMulti Accounts

Capability	Required	Role in the flow
Liveness	Optional for API; required for Web and Native	Liveness check at capture time.
Multi Accounts	Required	Performs 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.
• Sandbox credentials — see Environments.
• SDK or Web component installed — only for Web and SDK integrations. See SDKs and Tools.
• 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

Native

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

1. Install the SDK — add the Unico SDK dependency for your platform. See the setup guide for Android, iOS or Flutter.
2. Create a process — call Create Process with the appropriate flow value and the user's identifier. The response includes the webAppToken.
3. Open the journey — open the SDK with the webAppToken. The SDK runs the journey in your app and calls onSuccess with the processId when the user finishes.
4. Query the result — call Get Process to retrieve the capability results.
5. Apply business rules — evaluate the response fields to approve, deny or escalate.

Android

Native Android SDK for in-app capture.

View overview

iOS

Native iOS SDK for in-app capture.

View overview

Flutter

Cross-platform Flutter SDK for in-app capture.

View overview

Web

Integration in the browser — Unico hosts the journey, and you open it with the Journeys SDK or by redirecting the user.

1. Create a process — call Create Process with the appropriate flow value and the user's identifier. The response includes the process id, the token and the userRedirectUrl.
2. Open the journey — open it inside your page with the Journeys SDK, passing the process id (as transactionId) and the token. This is the recommended option. If the journey can run outside your page, use Direct access instead: send the user to userRedirectUrl, and set callbackUri in Create Process so Unico knows where to send them back.
3. User completes the journey — the Journeys SDK calls onFinish. With Direct access, Unico sends the user back to your callbackUri.
4. Query the result — call Get Process to retrieve the capability results.
5. Apply business rules — evaluate the response fields to approve, deny or escalate.

Web

Journeys SDK or Direct access, in the browser.

View overview

API

Direct API integration — capture the selfie using the Unico SDK or your own UI following the Capture Standard, then send the image directly to the Unico API.

1. Capture the selfie — use the Unico SDK for your platform, or build your own UI following the Capture Standard, to obtain a selfie image that meets liveness requirements.
2. Create a process — call Create Process with the user's identifier and the selfie as imagebase64; the executed capabilities are defined by your API Key configuration.
3. Query the result — call Get Process to retrieve the capability results.
4. Apply business rules — evaluate the response fields to approve, deny or escalate.

API

Full control over the flow with back-to-back integration.

View overview