Prove the person is who they claim to be.
Identity checks can combine documents, biometric capture and other personal evidence where relevant to the request. Available checks and source access depend on the agreed scope.
- Any platform onboarding a person
- Compliance and risk teams
- Payment and fintech flows
- Platforms needing a defensible identity record
What it does
Document and biometric checks
Document review, face comparison or liveness may be included where configured and relevant to the stated purpose.
Source checks where available
Where the relevant source can be accessed for the check, details may be cross-checked and the source method identified in the result.
Additional evidence as needed
Phone, address or other personal information can be considered when relevant to the purpose and supported by the agreed evidence method.
A scoped verification record
The record ties findings to the request, stated purpose and checks performed.
What this verifies
Evidence held together under one defensible record.
- National ID document and MRZ
- Passport document and MRZ
- Alien ID document
- Face comparison or liveness where configured
- Phone information where relevant
- Address confirmation where required
How it works
- Step 01
Purpose, authority and scope
Define the reason for the check and establish applicable consent or other authority before personal checks proceed.
- Step 02
Document capture
The person provides relevant identity documents or details. Available source checks depend on the requested scope.
- Step 03
Additional identity checks
Face comparison or liveness is performed where configured and included in the authorised scope.
- Step 04
Attach to the record
Return findings for the request scope, including supporting evidence and any unresolved items.
Results and exceptions
What you receive
Depending on the agreed scope, the verification record may include request status, check-level findings and available supporting evidence in a report or other decision-ready output.
When evidence needs attention
Mismatches, incomplete information or unavailable sources may require clarification or review. An unresolved item should be distinguished from a confirmed result.
Verification layers used
These are shared layers of DPAVerify, combined as the request and evidence require.
Datapoint Verify
Document and identity evidence, with source checks where available.
Learn moreDatapoint Field
Physical address confirmation when the identity record needs a human visit.
Learn moreDatapoint Intelligence
Enhanced analysis where the identity sits inside a wider risk picture.
Learn moreAccess and delivery
The available route depends on the solution, request scope and agreed operating model.
Related solutions
Pair this with another DPAVerify solution.
FAQ
Identity & Personal: frequently asked questions
Available document types depend on the request and service scope. Ask Datapoint which documents and source checks are supported for your use case.
Face comparison and liveness may be included where configured and relevant to the authorised purpose. They are not necessarily required for every request.
Phone or address information may be assessed when it is relevant to the stated purpose and the appropriate evidence method is available.
The report should identify source or evidence limitations. An unavailable check should not be treated as a confirmed result.
Start an identity verification
Prove a person before you depend on them.
Define the purpose and scope, then select the identity evidence relevant to the decision.
