For the complete documentation index, see llms.txt. This page is also available as Markdown.

Person Search Verification


Overview

Person search verification corroborates the identity attributes a user provides - such as name, address, and date of birth - against aggregated identity records drawn from public and commercial data sources. Rather than checking a single document against a single issuer, it looks for consistent evidence that the claimed identity exists and is associated with the details provided.

What Gets Checked

A person search typically evaluates whether the submitted attributes are corroborated across one or more record sources. Common signals include:

  • Whether the name and address appear together in established records

  • Whether the date of birth is consistent with those records

  • Whether the combination of attributes resolves to a single, coherent identity rather than conflicting or non-existent records

The check returns a corroboration outcome - for example, a match, a partial match, or no match - that can be used on its own or combined with other database checks to raise assurance.

What It Does and Doesn't Tell You

  • It confirms that the claimed identity is corroborated by independent records and is consistent across sources.

  • It does not authenticate the person in real time, and it is not a sanctions, watchlist, or credit screen - pair it with the appropriate dedicated checks where those are required.

  • Coverage and data depth vary by region and by the attributes supplied. Sparser records may return a partial or inconclusive result for legitimate users.

Person search is best used as a corroborating signal alongside document and biometric verification, not as a standalone proof of identity.

Last updated

Was this helpful?