Skip to main content
Smart revalidation

Re-authenticates users in transactions post registration, allowing the authentication methods to vary by the desired experience and flow criticality.

Markdown

How it works​

Smart revalidation confirms that whoever makes a transaction is the same user who registered before. Unico's engine runs two assessments: one with network intelligence, which analyzes the user's behavior, and one on session security. Based on them, it sets the friction needed: a silent validation, with no action from the user, or a facial biometric (facematch plus liveness) when the risk calls for it.

You choose who operates the authentication experience. In both methods, the engine is the same.

Method 1: Smart revalidation, default modeMethod 2: Smart revalidation, silent mode
How it worksUnico operates the authentication experience: it runs the engine and, when needed, the facial biometric. You receive only the final answer.The engine tells whether Unico is confident it is the expected user, without asking anything from them. You operate the authentication experience, and your risk tree decides the next step.
You receiveYES or NOYES or NO
Who operates the authentication experienceUnicoYou
Step-upRun by Unico.We recommend Unico facial biometrics: besides having the best liveness on the market, it feeds the engine, which sustains Unico's standard accuracy and unlocks more silent validations.

Method 1: default mode

Method 2: silent mode

What this product solves​

Use this product when:

  • Periodic revalidation (e.g., passwordless login, weekly re-check).
  • Financial transfers
  • Account management (e.g., password or limit changes)
  • Service subscriptions
  • New device registration
  • Financial operations (investments, loans, cashout), among others.

Capabilities involved​

Single adaptive capability:

CapabilityRequirementRole in the flow
Smart RevalidationRequiredOrchestrates metadata and biometric data adaptively to verify whether the user matches the reference process.

Prerequisites​

  • Bearer token — see Authentication.
  • Sandbox credentials — see Environments.
  • SDK or Web component installed — only for Web and SDK integrations. See SDKs and Tools.
  • Reference biometric — the user must have previously completed an onboarding or biometric registration process. Pass it via the references array in Create Process: each item requires referenceType (REFERENCE_TYPE_PROCESS_ID, REFERENCE_TYPE_IMAGE_BASE64 or REFERENCE_TYPE_HUMAN_TOKEN) and referenceContent (the process UUID, base64-encoded image or humanToken returned by Human Token).
  • useCase value — required when creating the process. See Smart Revalidation for the full list of valid values and their behavior.

Step-by-step implementation​

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. Use the returned token to initialize the SDK.
  3. Start the capture — the SDK renders the camera UI and performs liveness detection on-device, returning the captured payload.
  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.

iOS

Native iOS SDK for in-app capture.

Flutter

Cross-platform Flutter SDK for in-app capture.