--- title: Fraud Risk Level Detection description: Validates that a real person is performing the registration by combining Liveness with Behavioral Alert — no document capture or government identifier required. canonical: https://developer.unico.io/products/sign-up/fraud-risk-level-detection/index locale: en generated_by: markdown-export --- - [/](/) - [Build](/products/) - [Sign-up](/products/sign-up/) - Fraud Risk Level Detection **On this pageFraud Risk Level DetectionValidates that a real person is performing the registration by combining Liveness with Behavioral Alert — no document capture or government identifier required. ### 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](/products/sign-up/onboarding/index). You only need to know if this face is the same one that completed onboarding → use [1:1 Validation](/capabilities/1-1-validation). ### Capabilities involved​ Pipeline executed within a single process: [Liveness](/capabilities/liveness)[Fraud Risk Classification](/capabilities/fraud-risk-classification) CapabilityRole 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](/developers/start/authentication). **APIKEY enabled** — Key configured for V3 with behavioral analysis permission. See [Environments](/developers/start/environments). **Primary key (`subject.code`)** — The identifier performing the transaction: document number, email, or phone number. Maximize Risk Level accuracyIt 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​ 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 with the appropriate `flow` value and the user's identifier. The response includes the `webAppToken`. **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. **Query the result** — call 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 in the browser — Unico hosts the journey, and you open it with the Journeys SDK or by redirecting the user. **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`. **Open the journey** — open it inside your page with the [Journeys SDK](/developers/sdks-and-tools/web), 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](/developers/api-reference/post-processes) so Unico knows where to send them back. **User completes the journey** — the Journeys SDK calls `onFinish`. With Direct access, Unico sends the user back to your `callbackUri`. **Query the result** — call Get Process to retrieve the capability results. **Apply business rules** — evaluate the response fields to approve, deny or escalate. WebJourneys SDK or Direct access, in the browser.[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](/developers/api-reference/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](/developers/api-reference/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)### Error Handling​ CodeDescription`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.Last updated on Oct 8, 2026**