Private betaVerified 2026-08-17
Identity Verification
Understand DeFlow identity verification, wallet screening, readiness controls, and the current provider environment.
DeFlow uses third-party services for identity verification and wallet screening before a participant can perform protected actions. The current provider integration runs in a sandbox environment.
What happens
- The verification provider collects the information required by its sandbox flow.
- The provider processes that information outside the DeFlow application database.
- DeFlow receives and stores workflow identifiers, status, timestamps, and readiness results needed to control product access.
- Wallet screening and policy checks may run again when a deal reaches a protected action.
The current verification workflow must not be described as certified regulatory compliance. External legal review of DeFlow's public KYC, AML, privacy, and custody terminology is still pending.
If verification does not complete
- Confirm that pop-ups and required third-party cookies are not blocked for the verification window.
- Return to the DeFlow tab and refresh the status after completing the provider flow.
- Do not repeatedly submit different identity information.
- Contact support with the workflow time and visible status, but do not email identity documents.
See Data privacy and minimisation for the application's current data-handling boundary.