Overview
Database verification cross-checks the data captured during identity proofing against authoritative and third-party record sources - issuing authorities, government registries, and identity-data providers. Instead of judging a document by its appearance alone, the platform asks the systems of record whether the identity actually exists and whether the submitted details match.
It is a passive, back-end check: in most cases the user does nothing beyond the capture they have already completed. The result is a strong corroboration signal that complements document authentication and biometric matching.
Why It Matters
Document scanning and liveness confirm that a real, unaltered document is being presented by a live person. Database verification answers a different question: does this identity exist in an authoritative source, and does the submitted data match the record on file?
A document can be genuine in appearance yet not correspond to any valid record - or it can be a real document tied to a different person. Checking against the source of record closes that gap and raises overall assurance.
Methods Covered
AAMVA Verification
Do US driver's licenses and state IDs match the issuing state's DMV record?
None (passive)
Aadhaar Verification
Does the Aadhaar number correspond to a valid record, and do the holder's details match?
Low (consent / OTP)
Person Search Verification
Do aggregated identity records corroborate the name, address, and other attributes the user provided?
None (passive)
Combining Database Checks
Database verification is most powerful in combination. A document scan with face match establishes that a real person holds a real document; layering AAMVA, Aadhaar, or person search on top confirms that the underlying identity is recognized by authoritative and independent sources. Higher-assurance flows generally enable one or more database checks as required steps, while lower-risk flows may run them as advisory signals or omit them entirely.
Last updated
Was this helpful?