# eKYC V1 vs V2 Comparison

In V1, **eKYC** Verification presents a functional but generic credentials form experience. The screen focuses on collecting user information with standard input fields and minimal contextual structure. Processing and success states are simple and isolated, with little continuity between steps. The experience feels transactional, with basic feedback once the form is submitted.

In V2, **eKYC** Verification introduces a more structured, branded and guided experience. The interface is organized into clear sections, improving readability and reducing cognitive load. Processing and success states feel more cohesive with smoother visual transitions and clearer confirmation messaging, making the flow feel complete and intentional.

<Image align="center" caption="V1 is a basic eKYC experience with limited guidance." src="https://files.readme.io/4036637fcd29b2141c6aacd1bc11c188533480508e1b18c41176465387b0e02d-v1.png" />

<br />

<Image align="center" caption="V2 delivers a more structured, guided, and branded eKYC" src="https://files.readme.io/9d693f3c85824c1a611aaea458ac40847de6c4570c25110c8b1a4915e43d363d-v2.png" />

<br />

***

<br />

## Feature Comparison

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

| Capabilities               | V1 | V2 | Notes                                                                                                                            |
| -------------------------- | -- | -- | -------------------------------------------------------------------------------------------------------------------------------- |
| eKYC exprience             | ✅  | ✅  | Core functionality present in both versions.                                                                                     |
| Customization options      | ❌  | ✅  | V1 provides limited customization options, while V2 allows full control over text, colors, buttons, illustrations, and behavior. |
| Documentation completeness | ❌  | ✅  | V2 provides complete, standardized documentation coverage.                                                                       |

<br />

***

<br />

## Behavior Differences

How the module behaves during runtime.

| Behavior            | V1                       | V2                                                                | Notes                                                                          |
| ------------------- | ------------------------ | ----------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| State transitions   | Default transitions      | Specifically designed screen-by-screen transitions for smoothness | V2 includes transition guidelines as part of the module documentation package. |
| Processing behavior | Static processing screen | Branded processing state with consistent loading behavior         | V2 aligns loading behavior with the overall system patterns                    |

<br />

***

<br />

## **Customization Overview**

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

<Image align="center" caption="Customizing the experience to match your brand is simpler in V2" src="https://files.readme.io/f343997854c7531892a57fe20987c5954b23eba3c3316825a13f645914893e5e-gifekyc.gif" />

<br />

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.

<br />

<br />