“There was nothing at my door”
A photo of a parcel at a door does not say which door, nor when. With no area recorded at the shutter, it settles nothing.
Delivery and logistics · Business
“The parcel arrived broken”, “it never arrived”. Proof of delivery becomes an exhibit.
Most carriers already take a delivery photo. What is missing is what a third party can verify about it: that the time was not rewritten, that the place is the recipient’s, that the file is the original.
30 days, 100 test proofs through the API. No card. The mobile capture SDK comes with a pilot.
The problem as it is lived
One word against another, and a refund decided on the benefit of the doubt.
“The box was already crushed”
The handover photo shows a state. You still have to establish that it is the original photo, taken at that moment, and not one retouched after the complaint.
“The delivery time does not match”
The time in the file comes from the phone. It changes. A proof of delivery is worth a date a third party re-checks without taking your word.
What the proof establishes here
The same three checks as on any Evidiq proof, read in the terms of a complaint.
What it establishes
- The latest date at which the photo existed, anchored outside our servers.
- The area recorded at the shutter, and whether it matches the delivery address you stated in the request.
- The device and the app, through the attestation requested on submission, when the capture comes from an attested app.
- That the file has not changed since it was sealed.
What it does not establish
- The state of the contents of the parcel, nor who signed for it.
- What the proof is worth in your dispute. That judgement belongs to whoever receives it: customer, cargo insurer, mediator.
A photo posted through the API from your own field app is scored on a separate rubric, and the page says so: fingerprints and date of receipt established, device “Not measured”. One channel does not lend its trust to another. Understand a proof.
How it works
Three paths, depending on what your couriers hold in their hand.
The Evidiq app
On the courier’s phone, iPhone or Android. Live capture at handover, offline if need be, device attestation on submission.
Establishes: device, file, date, area.
Your app, through the API
Your field app posts the photo at handover. You receive the decision through a signed webhook and match the proof against your tracking number.
Establishes: file and date of receipt. Device “Not measured”, and the page says so.
Your app, with the SDK
The engine of our own apps inside yours: live capture, attestation, submission. On request, within a pilot.
Establishes: the same as our app.
The technical detail, with the exact code excerpt: for developers.
A real proof, as the recipient will see it
The demonstration proof, the same as on the home page. The whole card is a link to the real verification page.
What an operations manager asks
Do my couriers have to switch apps?
Not necessarily. Three paths: the Evidiq app on the courier’s phone (iPhone or Android); your own field app posting the photo through the API, in which case the verification page says the device is not attested; or, in a pilot, the mobile capture SDK that puts attested capture inside your own app.
What happens with no network at the moment of delivery?
The capture happens anyway. The proof is built on the device, waits for a connection, then goes on its own. An interrupted capture never creates two proofs nor two charges: a round through an underground car park produces no duplicate.
Can the recipient contest a proof?
They can read it, with no account, on the same page as you: the latest date, the area, the device, the file’s integrity. They cannot modify it, and neither can you. What they contest next, the state of the parcel or who signed for it, the proof does not establish: it establishes the photo, its time and its place.
The other industries: insurance, construction, property inventories.
Start with one round.
A pilot is scoped against your volume and your field app. The sandbox gives you the API right away, with no card.
Hosted in FranceWebhooks always signedOffline, resumes with no duplicateWhat proves it