Skip to main content
This agent lets you run a full identity verification inside WhatsApp via WebView, combining photo liveness, document validation, and facial comparison. The experience opens from a unique link in the chat and uses guided capture with immediate feedback.
For liveness and document check, WebView uses guided capture with on-screen feedback; the user stays in the chat.

Prerequisites

✅ Checklist to start without blockers

  • You must have a verified WhatsApp account.
  • You must have the Terms and Conditions PDF (public URL) to configure in the agent. This is mandatory.
  • The user must be able to take photos from the chat (camera permissions enabled on the device).
  • Location permissions are also requested so data can be collected for better audit and traceability of the biometric process.

How does it work?

In under one minute, the user completes these steps:
1

Access via a unique link

The user receives a unique WhatsApp link to start the session. The link contains a non-reusable session id and the associated flow information.
2

Take a photo

The user captures a live photo from the camera, with visual guides for a correct shot.
3

Capture their ID document

Front and back images of the document are requested, with visual assistance to validate validity and authenticity.
4

Automatic facial comparison

The system compares the photo to the face extracted from the document and computes the similarity level. This version does not yet include facematch against government entities.

How to connect the integration?

How to connect the Biometrics integration

1

Open the platform

Use the Agent to create a biometrics flow, or select the Identity validation template. To start a flow from scratch, click Brain Studio in the sidebar.
2

Select Biometrics

In the toolbar you will see the Biometrics option. Click Connect.
3

Connect the integration

Once connected, you will see the Biometrics node, where you can configure retries, experience, and additional validations.
4

Configure outputs

This agent has 1 success output and 3 error outputs. Each can route to:
  • Text input with a custom message.
  • Connect, only if you have this module.
5

Run tests

With the configuration you just set, run tests with the Test button.

Configuration

Success

Confirms that biometric verification succeeded.Variable: approvedDescription: Biometrics approvedResponse structure (JSON):
Important fields:
  • document_response: ID document information
  • liveness_response: Photo used for liveness
  • facematch_response: Facial comparison result
  • reporte_de_biometria: Report URLs (web and PDF)
  • device_info: Device and location data (audit and traceability)
  • gov_entity_data: Government entity data (if applicable)
JSON response variable definitions:
  • document_response: document_check (result, verified_fields, secondary_fields, details, status_fields, image_quality_details, images_extracted, gov_entity_fields), document_image_front_url, document_image_back_url, document_face_image_url
  • liveness_response: result, url_selfie_image
  • facematch_response: facematch_result (approved/decline), facematch_confidence
  • reporte_de_biometria: report, report_pdf
  • device_info: userAgent, browser, operatingSystem, platform, language, timezone, screenResolution, colorDepth, timestamp, ipAddress, location (latitude, longitude; only if location permission), deviceId, deviceName
  • gov_entity_data: government entity data for the country (fields vary by country)

Errors

The user left the process before completing it.Variable: incompleteDescription: Process abandoned
Biometric verification failed or was rejected.Variable: rejectDescription: Biometrics rejected
Error while running the biometric process.Variable: errorDescription: Process error

Report

By default a report is generated with the following fields:
The biometric report can be downloaded as PDF for audit or internal backup.
Location in the report: Latitude and longitude depend on permission granted by the user. If the user denies location access or location is disabled on the device, these fields will not appear in the report.

How to customize the experience?

When you click the Biometrics node on the canvas, a side panel opens with three configuration tabs.
Configure the number of retries allowed per stage of the biometric process.Variable: Maximum liveness attemptsDescription: Defines how many times the user can retry the facial capture before the process fails.Input: 1, 2, or 3
Variable: Maximum document verification attemptsDescription: Defines how many times the user can retry the document capture.Input: 1, 2, or 3
Customize the appearance of the WebView the end user will see. Use the Preview button to view the mockup of each screen before publishing.Variable: ColorsDescription: Use Jelou colors (default) or define custom colors for buttons, steppers, spinners, background, and text.Input: Color code in HEX format (e.g. #1E7A4C)
Variable: Experience languageDescription: Defines the default UI language the user sees when the process starts.Input: Spanish, English, or Portuguese
Variable: Language toggleDescription: A button is enabled in the user interface that lets the user change the language.Input: Enabled / Disabled.
Define the minimum validation levels the user must pass for the process to be considered successful.

Document verification

Controls how strict the ID document analysis is. Choose from three levels:
The document type and origin and expiry date variables cannot be disabled under any selected level.
In populations with a high share of old or worn documents, the Advanced level may increase the rate of cases sent to manual review (HIL). Assess the typical document quality of your user base before enabling it.

Facial comparison

Variable: Facial comparison (facematch)Description: Defines the minimum similarity percentage accepted between the liveness selfie and the face extracted from the document.Input: Low (65%), Standard (80%), or Strict (90%). The threshold is 100% configurable per company; the default value is 70%.
A higher facematch threshold reduces impersonation risk but may increase false rejection of legitimate users. Adjust it to the risk level your operation can accept.

Terms and conditions URL

Variable: Terms and conditions URLDescription: The user must accept the terms on the initial screen before starting the process.Input: Public URL (the link must be publicly accessible)
This configuration is global for your company: any changes will apply to all flows using WebView biometrics.

FAQ

Photos of the ID document on both sides: front and back.
WebView opens a dedicated link with guided capture; the report includes device data (browser, OS, resolution, timezone, IP, device ID) and location if the user grants permission. You can adjust colors (background, text, buttons, stepper), UI language, and security options described in the customization guide; capture widgets are not editable. Conversational uses video in chat; Flows uses photo inside WhatsApp Flows with its own gallery rules and native UI.
Yes: background, text, button, and stepper colors; UI language (Spanish/English) and, when enabled, a user-facing language selector. Stepper color also applies to widgets. Face and document capture widgets are not customizable.
1 success output (Biometrics approved) and 3 error outputs (Process abandoned, Biometrics rejected, Process error). Each can route to a custom text message or Connect.