Fraud Risk Level Detection

Validates that a real person is performing the registration by combining Liveness with Behavioral Alert — no document capture or government identifier required.

Markdown

What this product solves

Fraud Risk Level Detection addresses the challenge of validating that a real person is performing the registration, without requiring document capture or identity verification through a government identifier — all within a single process.

By combining Liveness with Behavioral Alert, the pipeline confirms the presence of a real person in front of the camera and, simultaneously, checks whether that face carries risk signals in the Unico network. The result is an onboarding decision based on behavioral trust, not just documentary data.

Use this product when:

• Your operation suffers from fraud where the identity is legitimate but the intention is criminal.
• You need to identify and block identity fraud attempts where users open accounts with synthetic identities.
• You need to identify and block Mule Account attacks, where users open multiple accounts across different institutions to launder money.
• You want to mitigate Bust-out Fraud by detecting users who generate sudden hyperactivity in the network.
• Your business model requires that each individual holds at most one active account per operator (or per country).

Do not use this product when:

• You only need to validate the static integrity of a document against a government database → use Onboarding.
• You only need to know if this face is the same one that completed onboarding → use 1:1 Validation.

Capabilities involved

Pipeline executed within a single process:

LivenessFraud Risk Classification

Capability	Role in the flow
Liveness (Optional)	Confirms that the selfie belongs to a living person, mitigating deepfake or injection attacks. Ensures input integrity before behavioral analysis.
Fraud Risk Classification	Cross-references transaction data (face, code, history) with the global network history. Applies statistical models to generate the final risk level for that transaction.

Prerequisites

• Bearer token — OAuth2 authentication via Client Credentials. See Authentication.
• APIKEY enabled — Key configured for V3 with behavioral analysis permission. See Environments.
• Primary key (subject.code) — The identifier performing the transaction: document number, email, or phone number.

Maximize Risk Level accuracy

It is highly recommended to send metadata and context alongside the request. This includes registration data (name, date of birth, gender, and other information), email, phone, and clientReference. Using our Liveness solution also enriches the analysis with device risk, location, and additional behavioral signals.

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

Error Handling

Code	Description
20807	Image outside HD standard (minimum 640×480).
20506	Base64 file exceeds the maximum supported limit (800 KB).
20507	The subject.code field is invalid.
20510	The clientReference field is invalid.
10201	The APIKEY header is invalid or the credential does not have permission for the Risk layer.