Face Match V1 vs V2 Comparison


In V1, Face Match compares two user images and shows detailed result screens that combine multiple signals, such as liveness success or failure and whether the user exists. This can sometimes introduce extra complexity about what the final result actually means.

In V2, Face Match focuses on clarity. By default, users only see whether the faces match or not. Supporting signals like liveness or user existence are handled in the background and surfaced only when needed, resulting in a simpler, more direct experience.


V1 is a face match experience that presents multiple result signals together, which may result confusing to users.


V2 is a simplified face match experience focused on clarity, showing users only whether the faces match or not, while handling supporting signals like liveness and user existence in the background.




Feature Comparison

Functional capabilities of the module (objective features only; no UX or performance differences).


CapabilitiesV1V2Notes
Face-to-face comparisonCore functionality unchanged.
Shows user images✅ / OptionalV2 offers Compact Mode, which hides the user images.
Compact ModeV2 is the only version that supports this mode.
Match / No match resultCore functionality unchanged.
Liveness and Existing User Checks✅ / OptionalV2 handles this in the background and offers the option to show this result to the user.
Error StatesBoth versions cover general error cases that users can encounter.
Customization optionsV1 provides limited customization options, while V2 allows full control over text, colors, buttons, illustrations, and behavior.
Documentation completenessV2 provides complete, standardized documentation coverage.



Behavior Differences

How the module behaves during runtime.


BehaviorV1V2Notes
Matching faces stateAlways shows the user imagesUser images can be shown or hidden in Compact ModeV2 offers more customization opportunities.
Result screensShows Liveness and Existing User results. It also adds a colored overlay over user images depending on result.Simplifies the default result screens by only showing if the faces match or not. Can be configured.V2 focuses on clarity so users can understand results and quickly recover from errors.
State transitionsDefault transitionsSpecifically designed screen-by-screen transitions for smoothnessV2 includes transition guidelines as part of the module documentation package.



Customization Overview

Customization in V2 is significantly simpler and more consistent across modules.

Customizing the experience to match your brand is simpler in V2


Instead of having isolated configuration options per screen or component, V2 uses a unified token-based system that allows developers to control visuals, behaviors, and experience patterns with fewer parameters and predictable outcomes.

This means:

  • Less engineering work to override UI elements
  • Consistent branding across modules
  • Predictable behavior when changing settings
  • Reduced risk of breaking flows
  • Clear separation between visual tokens and experience configuration

V2 also centralizes all customization options under a single structure, so developers always know where to look and what they can modify.

For full details, visit the Customization tab of this module.