How it works
Initial verification
The user completes a standard KYC process (ID Verification + facial recognition). Verification data is encrypted and stored in the user’s Didit ID, compliant with eIDAS2.
Reuse at a new application
When the user encounters another Didit-integrated application, they select the option to reuse their existing KYC. A quick facial recognition check confirms their identity, and they consent to share specific data.
Key Benefits
| For Users | For Businesses | For Compliance |
|---|---|---|
| Verify once, use anywhere | Faster user onboarding | Maintains regulatory standards |
| Control over data sharing | Reduced drop-off rates | Complete audit trail |
| Seconds instead of minutes | Higher conversion rates | Cross-jurisdiction support |
Security and Compliance
| Area | Details |
|---|---|
| Encryption | End-to-end encryption for all stored and transferred data |
| Biometric re-auth | Facial recognition required for every reuse |
| Regulatory | eIDAS2 compliant, supports AML/KYC requirements |
| Cross-border | Works across jurisdictions |
