Built for
Onboard drivers, riders and vehicles through one workflow.
A single operational workflow can bring together identity, driving credentials, background checks and vehicle evidence relevant to an operator's onboarding or eligibility decision.
What it does
Checks and source availability depend on the agreed scope.
One request, one record
The applicant provides consent and personal details; everything after that attaches to a single defensible record you can retrieve later.
Evidence matched to the request
Driving credentials and vehicle records can be included where the relevant source or evidence is available for the requested scope.
Recurring eligibility
Where configured and supported, schedule revalidation around licence, insurance or other expiry dates and engagement requirements.
Identity checks when required
Identity-document and liveness checks can be included in the agreed scope, with consent and purpose made clear to the applicant.
What this verifies
Evidence held together under one defensible record.
- Identity document and liveness
- Driving licence (NTSA)
- PSV badge (NTSA)
- Police Clearance Certificate
- KRA PIN and compliance
- Vehicle logbook and insurance
How it works
- Step 01
Consent and contact
Define the operational purpose and scope, then obtain applicable consent or authority before checking an individual.
- Step 02
Collect the required evidence
The applicant provides the information and documents needed for the agreed checks.
- Step 03
Payment
Relevant records and sources are reviewed where available; exceptions can be referred for clarification or analyst review.
- Step 04
Return the outcome
Provide the operator with a scoped result and available supporting evidence, including items requiring follow-up.
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
Identity, licence, PCC and KRA checks for every driver and rider.
Learn moreDatapoint Intelligence
Recurring eligibility monitoring across the fleet and portfolio-level analytics.
Learn moreDatapoint Field
Physical address and vehicle confirmation where the decision requires it.
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
DPAVerify Mobility: frequently asked questions
The scope may include identity, driving credentials, background checks, tax information and vehicle or insurance evidence, depending on the operator's requirements and source availability.
Vehicle registration, roadworthiness or insurance evidence can be included where relevant sources or supporting documents are available for the agreed scope.
Revalidation or monitoring may be configured for supported records and agreed intervals. Available indicators and update frequency depend on the source and service scope.
Discuss the expected volume and workflow with Datapoint so the appropriate operating and integration model can be confirmed.
Start a mobility verification
Onboard a driver, rider or vehicle today.
Begin a single request-verification flow for a driver, rider or vehicle — or talk to us about running this across a fleet.
