Built for
Verify sender, recipient and the parcel chain.
A workflow for associating relevant sender, recipient, rider and parcel-handover evidence with a delivery.
What it does
The verification scope depends on the delivery process and available evidence.
Sender and recipient identity
Where individuals are checked, state the purpose and scope and obtain applicable consent or other authority before checks proceed.
Rider linked to operator records
The operator can associate the assigned rider with its onboarding record, subject to the integration and information available.
Handover evidence
Handover details can be recorded against the parcel reference using the evidence methods agreed for the workflow.
Dispute pack on demand
A delivery record can help review disputes when relevant handover events and supporting evidence have been captured.
What this verifies
Evidence held together under one defensible record.
- Sender identity and consent
- Recipient identity and consent
- Rider identity and credentials
- Parcel handover evidence
- Address and location confirmation
- Chain-of-custody timeline
How it works
- Step 01
Request on dispatch
Define which parties and parcel events require evidence and how the request is initiated.
- Step 02
Rider match
Associate the assigned rider with the operator's relevant onboarding record where the workflow supports it.
- Step 03
Handover capture
Capture the agreed parcel and handover information and attach it to the delivery record.
- Step 04
Export when needed
The captured record can support later review; available evidence and export options depend on the configured workflow.
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 and consent capture for sender, recipient and rider.
Learn moreDatapoint Field
Address and premises confirmation for high-value or sensitive deliveries.
Learn moreDatapoint Intelligence
Pattern analytics across the parcel network — recurring senders, recipients and risk signals.
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 Courier: frequently asked questions
Depending on the workflow, the record may include sender, recipient or rider evidence, parcel reference and handover information.
The configured workflow determines how each party is invited and how evidence is recorded. Applicable consent or other authority should be established before checking individuals.
Analysis of recurring delivery patterns depends on the data and monitoring features configured for the service.
Field verification can be scoped to an address or premises where the delivery decision requires physical evidence.
Start a courier verification
Put evidence between the parcel and the dispute.
Run a single sender-recipient-rider verification, or talk to us about integrating this across your delivery network.
