Explainer

What Is Identity Verification?

Identity verification is the process of establishing that a person is who they claim to be. It combines evidence, checks and risk decisions to help organizations prevent fraud, meet obligations and provide services safely.

Identity verification, often shortened to IDV, is the process an organization uses to establish whether a person is who they claim to be. It typically compares information supplied by the person with evidence from identity documents, trusted data sources or other signals.

People encounter IDV when opening a bank account, signing up to drive for a delivery platform, trading cryptoassets or accessing age restricted goods online. The process can be quick and largely automated, or it can involve a human review when the evidence is unclear or the risk is higher.

Identity verification in plain terms

At its core, IDV answers a specific question: does this real person match the identity they are presenting? That question has several parts. An organization may need to know whether a document appears genuine, whether the document belongs to the person submitting it, and whether that identity is acceptable for the requested service.

Verification does not guarantee that someone will never commit fraud. A genuine person can still misuse an account, and criminals can sometimes obtain genuine documents or stolen personal data. Instead, IDV reduces uncertainty and helps a business apply controls proportionate to the risk.

Identification, verification and authentication

These related terms are often used interchangeably, but they describe different steps in managing an identity.

  • Identification is the act of stating or collecting an identity. Entering a name, email address or account number identifies the person or account being presented.
  • Verification is checking whether that stated identity is supported by reliable evidence. For example, a bank may compare a customer’s details with a government issued ID and external records.
  • Authentication is confirming that a returning user is the authorized holder of an account or credential. A password, passkey, security key or one time code can authenticate a user after an account has been created.
  • Authorization is a separate, subsequent decision about what an authenticated user may do, such as transferring funds or viewing sensitive records.

A service may use all of these concepts in one customer journey. It identifies an applicant from their submitted details, verifies them before opening the account, and later authenticates them at sign in. It may ask for stronger authentication before a high value payment.

Why businesses verify identity

Fraud prevention is a central reason. Verification can make it harder to create accounts with fabricated identities, use stolen identities, take over accounts or exploit promotions and payment systems. It can also support investigations by creating an auditable record of the evidence and checks used.

Legal and regulatory obligations are another major driver. Financial institutions and many cryptoasset businesses commonly conduct know your customer, or KYC, checks. KYC is a set of customer due diligence measures intended to help prevent money laundering, terrorist financing and other financial crime. Requirements vary by product, customer risk and jurisdiction. In the United States, obligations arise from frameworks including the Bank Secrecy Act. In the European Union, anti money laundering rules and national implementations set related expectations.

Businesses also verify to establish trust and protect users. A marketplace may verify sellers to reduce scams. A gig platform may check that a worker is eligible to perform a role. An online community may use age assurance to limit access to material intended for adults. These uses should be balanced with privacy, accessibility and the risk of excluding people who cannot easily provide standard documents.

The basic flow: collect, check, decide

Most IDV systems follow a three stage pattern, although the details differ by sector and risk level.

  • Collect: The organization asks for information and evidence, such as a legal name, address, date of birth, government ID, selfie, phone number or tax identifier. It should collect only what is necessary for the purpose.
  • Check: Software and, where needed, trained reviewers assess the evidence. Document checks can look for signs of alteration and read machine readable features. Database checks can compare submitted data with authoritative or reputable sources. A selfie video or photo may be compared with an ID portrait, often with liveness detection intended to determine whether a real person is present rather than a replay or mask.
  • Decide: The organization approves, rejects or refers the case for further review. A decision may reflect confidence in the identity evidence, fraud signals, legal rules and the level of risk associated with the service.

Good processes provide a route for people to correct errors or submit alternative evidence. They also explain what data is collected, how long it is retained and who receives it. In the EU, processing personal data must have a lawful basis and comply with the General Data Protection Regulation. US privacy requirements are more sectoral and state based, but transparency and reasonable safeguards remain important.

Where people commonly encounter IDV

Banks and payment providers may verify customers before providing accounts, credit or money movement services. Cryptoasset exchanges and other regulated providers may use similar onboarding checks. Gig work and marketplace platforms may verify workers, merchants or sellers to deter impersonation and satisfy safety or regulatory requirements.

Age gates are another common case, but they are not all equivalent. A simple self declared date of birth is an age screen, not strong identity verification. Higher assurance age verification may check a document, a trusted age attribute or another method that establishes whether someone meets an age threshold. The appropriate approach depends on the law, the harm being addressed and the privacy impact.

Online and in person verification

Online verification is conducted remotely, usually through a website or mobile app. A person may photograph an ID, capture a selfie or complete a video step. Its advantages are speed, reach and availability outside business hours. Its challenges include manipulated images, deepfakes, device fraud, unequal access to smartphones and false rejections caused by image quality or mismatched records.

In person verification involves an employee, agent or automated kiosk examining evidence while the person is physically present. It can support stronger checks in some settings because an inspector can handle a document and observe the holder. However, it is slower, more costly and still depends on staff training, document knowledge and secure processes.

Neither model is inherently sufficient for every situation. Organizations commonly combine methods and apply additional checks when a transaction is high risk. The goal is not to collect the most data possible, but to obtain enough reliable evidence for a fair, lawful and proportionate decision.