What counts as proof of delivery in a chargeback
When a cardholder files an item not received dispute (Visa calls it dispute condition 13.1), the bank asks the merchant for evidence the goods reached the agreed destination. What carries weight is specific: the delivery date, and the full delivery address matching the order, not just a city and postal code. Merchant documentation is blunt about the weak spots: a tracking link showing a partial address is not accepted, and a delivered status alone does not establish who received the package. A signature from the cardholder or an authorized person, or delivery evidence tied clearly to the address and the time, is what completes the file. Visa's own public guidance adds a habit worth copying: request acknowledgement from the customer once the goods are delivered or the service is completed.
One correction to a widespread belief: Visa Compelling Evidence 3.0 does not cover item not received disputes. CE 3.0 applies to card absent fraud disputes (condition 10.4) and works through prior undisputed transactions from the same cardholder. For a not received case, your defense is the delivery file itself, which is why the quality of what you capture at the doorstep decides the outcome months before any dispute exists.
For merchants, couriers and field teams: building the file before the dispute
The chargeback is lost or won at delivery time, not at response time. If your courier's photo shows a package on an anonymous doormat, cropped so no door number is visible, with a date that lives only in the courier's own system, the bank sees exactly what the cardholder's lawyer would point out: a photo that could be any doorstep, any day. The same logic applies to field service: an after photo of a repaired unit proves little if nothing fixes where and when it was taken.
Build the file so each delivery or job produces one record with four properties: the goods or the completed work visible, the place identifiable (door number, meter serial, site reference in frame), a date that comes from a system the driver cannot edit, and a format you can hand to the bank as is. Do that consistently and most disputes die at the first representment, because the cardholder's claim of nothing arrived now contradicts a dated, located, verifiable photo of their own doorstep.
For customers: the package is marked delivered but nothing arrived
Before filing a dispute, work the short checklist. Check around the property and with neighbors or a building concierge, because drivers often leave packages out of sight. Ask the carrier for the proof of delivery, including the delivery photo and GPS scan if they have one; a photo of someone else's doorstep is itself evidence in your favor. Then contact the merchant in writing and give them a chance to reship or refund, which is faster than a dispute and leaves a paper trail.
If that fails, open the dispute with your bank and attach what you gathered: the delivered status, the mismatched photo, your messages to the merchant. Timing matters: card network rules typically give you up to around 120 days from the expected delivery date to dispute, but your bank's own deadlines prevail, so do not sit on it. Be accurate in what you claim, because filing a dispute for goods you actually received is friendly fraud, and merchants increasingly hold delivery evidence strong enough to prove it.
Which photos, at which moment
The same table serves a parcel at a doorstep, a pallet at a dock and a finished repair at a customer site. What changes is only the subject; what makes the photo weak never changes.
| Moment | What to photograph | What makes the photo contestable |
|---|---|---|
| At handover or drop-off | The package or goods at the delivery point, with the door number, nameplate or site reference in frame | A parcel on an anonymous mat could be any address; nothing links the photo to this order |
| On completion of field work | The finished work next to an identifier: meter serial, equipment tag, order number on a slip | An after photo with no reference proves work was done somewhere, not at this customer's site |
| When the customer is present | Handover with acknowledgement: signature, or the customer's own confirmation message | A verbal okay leaves nothing for the bank; months later it is one word against another |
| When a dispute arrives | Nothing new to shoot: export the original record with its date and address intact | A photo reconstructed or edited after the fact is worse than none if the alteration shows |
Sealing the delivery photo instead of defending it
Every weakness above is the same one: an ordinary photo does not prove its date, its place, or that it has not been touched. Danaya seals the photo at the moment it is taken. The driver or technician opens a capture link, the photo is shot live in the browser camera, nothing can come from the gallery, and the file is sealed with a cryptographic fingerprint, the GPS position and a server timestamp. The result is one verifiable report per order or per job in your dashboard, checkable by anyone on a public page, including the bank analyst reading your representment.
Delivery and field operations run at volume, which is why this is also an API use case: create a capture link per order from your own system and collect the sealed report back automatically. The honest limits: a sealed photo makes your delivery evidence verifiable, it does not guarantee the chargeback outcome, which stays with the card network rules and the bank.