Government Record Verification V1 vs V2 Comparison
In V1, Government Record Verification performs a background check against the corresponding government entity but provides no explicit reference to the source during the verification wait. The loading state is basic, result screens are minimal, and UI elements are not tokenized, which makes customization difficult and limits the ability to align the experience with your brand.
In V2, Government Record Verification focuses on transparency and clarity. The loading state explicitly informs the user their information is being checked against government records, result screens are cleaner and more refined, and customization follows a unified token-based system — resulting in a more trustworthy and consistent experience.
V1 is a basic upload experience with limited guidance and no tokenized customization.
V2 is a refined upload experience with clear per-side validation, inline error feedback, image quality hints, and full token-based customization.
Feature Comparison
Functional capabilities of the module (objective features only; no UX or performance differences).
| Capabilities | V1 | V2 | Notes |
|---|---|---|---|
| Government record validation | ✅ | ✅ | Both versions compare OCR-extracted identity data against the corresponding government entity records. |
| Loading state | ✅ | ✅ | Both versions display a processing state while the verification request is completed. |
| Success state | ✅ | ✅ | Both versions confirm identity verification with a success screen when the record is found and matched. |
| Error states | ✅ | ✅ | Both versions cover general error cases that users can encounter. |
| Government source attribution in UI | ❌ | ✅ | V2 explicitly informs the user that their information is being checked against government records, both in the loading copy and the footer. |
| 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. |
Behavior Differences
How the module behaves during runtime.
| Behavior | V1 | V2 | Notes |
|---|---|---|---|
| Loading state | Basic loading indicator with no reference to the verification source | Refined loading screen that explicitly informs the user their information is being checked against government records | V2 keeps users informed during the verification wait, reducing uncertainty and drop-off. |
| Result presentation | Basic success and error states with no source attribution | Clearly differentiated success and error screens with the government source referenced in the footer | V2 makes it immediately clear to the user what entity validated their identity. |
| State transitions | Default transitions | Specifically designed screen-by-screen transitions for smoothness | V2 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. This includes loading indicator styles, text content, result screen colors, and status icon styling — making it straightforward to align the module with your brand without affecting the underlying government verification logic.
Updated about 3 hours ago