Skip to content
Use cases7 min read

How to Prove Vehicle Condition at Pickup and Return

Rental car damage proof rests on two live captures, one at pickup and one at return, with the same shot list. Each is sealed and dated by a third party, and both are filed under the booking reference.

By Cédric Driaux, Founder of tryVidimus

Close-up of the front headlight and bumper of a silver car, photographed at pickup

Typical disputes: “that scratch was already there”

A rental dispute almost always has the same shape. The owner says the bumper came back scratched. The renter says the scratch was there at pickup. This article belongs to our series on photo evidence use cases, and it covers vehicles and equipment.

Both sides usually have photos. The trouble is that nobody can check them:

  • The pickup photos were taken in a hurry, from two angles, and miss the part that is now in question.
  • The dates come from each phone. Neither side accepts the other's.
  • The files sit on one party's phone or servers, so the other party says they could have been edited.

The platform or the agency then has to decide between two stories. Our article on whether a photo can be used as evidence explains what gives a picture weight in that situation: its origin, its date and its integrity. A protocol at pickup and return aims at exactly those three points.

The capture protocol: angles, timing, who shoots

A good protocol is short and identical every time. Three decisions make it work.

First, the angles. Fix one shot list per type of vehicle and never leave it to the mood of the day. For a car, a list like this covers most disputes:

  1. Front, straight on, with the number plate visible.
  2. Front left and front right corners, bumper included.
  3. Left side and right side, full length.
  4. Rear left and rear right corners, then the rear straight on.
  5. The four wheels and rims.
  6. Windscreen and roof.
  7. Interior: front seats, rear seats, boot.
  8. Dashboard with the ignition on, to show the mileage and the fuel or charge level.
  9. A close-up of every mark that already exists.

Second, the timing. The pickup capture happens at handover, with the vehicle in front of both parties, not the evening before. The return capture happens when the vehicle comes back, before it is moved, washed or rented again.

Third, who shoots. In a staffed agency, the agent captures the vehicle at pickup and again at return. On a peer-to-peer platform, the owner captures at pickup and the renter captures at return, as on our use cases page. You can also ask both parties to capture at both moments: each then holds its own record.

Making the photos hard to contest

A protocol done with the phone's camera app still produces ordinary files. tryVidimus is an API that turns each capture into a sealed proof. Your rental application calls it with the booking reference and gets a capture link. The link opens a web page with your logo and your wording, and there is nothing to install.

  • Live capture only. The camera is the only source, with no import from the gallery, so a photo from last month cannot slip in.
  • Straight to storage. The files do not pass through your servers, so nobody can say you changed them.
  • A sealed proof. Each file gets a SHA-256 fingerprint, each photo is signed with a C2PA manifest, and the proof receives a qualified electronic timestamp from an independent authority.
  • Public verification. Each proof has a verification page that opens without an account, and the verifier is open source.

The two captures can then be linked. When your application creates the return capture, it names the pickup proof as its “before”. The return proof points to the pickup proof, and the capture page asks for the same shots, one by one.

The link joins two captures made by the same party under the same booking reference: the agent at pickup and the agent at return, for example. Captures made by the other party are separate proofs under that same reference. They belong to the same file without being part of the pair.

Handling a dispute with the proof file

The booking reference is what turns separate proofs into a file. Every capture carries it, and your application lists all the proofs of a booking with it. If you run several agencies, each capture can also carry a reference for the place.

When a renter contests a charge, the file for that booking can be put together in a few steps:

  1. List the proofs of the booking by its reference: pickup and return, and each party's captures if both shot.
  2. Open the linked pair and put the same shot from both moments side by side: front-left corner at pickup, front-left corner at return.
  3. Send both parties the public verification links. Each one checks the date and the integrity without asking you.
  4. Let the people in charge conclude: your support team, the insurer, or the parties themselves.

Take the scratched bumper. If the pickup proof shows a clean bumper and the return proof shows the scratch, the renter can hardly argue that your photos were swapped or redated. If the pickup proof already shows the scratch, the owner's claim stops there. In both cases, both sides look at the same record.

Proofs are kept for 24 months. The cost of a sealed proof is on the pricing page.

The equipment rental variant

Cameras, lenses, drones, tools and outdoor gear follow the same logic, with a different shot list. A missing part matters as much as a scratch.

  • The whole kit laid out, so that every part and accessory is visible in one shot.
  • The serial number or identification plate.
  • The fragile surfaces: the front glass of a lens, a screen, a blade, a propeller.
  • The item switched on, when its working state can be seen.
  • The case or the bag, open and then closed.

For a lens that comes back with a mark on the front glass, the handover proof and the return proof answer the only useful question: was the mark visible when the lens left?

The same pattern applies to anything that changes hands and comes back. Our article on property inspection photos applies it to a home, room by room. You can build the whole journey in the sandbox first, where timestamps are simulated and have no legal value; the documentation covers the calls.

Frequently asked questions

How many photos should a vehicle pickup capture include?

Enough to cover every panel once, plus the interior, the dashboard and each existing mark. For a car, that is usually the front, the rear, both sides, the four corners, the wheels, the windscreen, the roof and the cabin. Use the same list at pickup and at return, for every booking.

Who should take the photos, the owner or the renter?

Whoever is present at the handover, and ideally the same party at both moments. In an agency, the agent captures at pickup and at return, and the two proofs can be linked. On a peer-to-peer platform, the owner and the renter can each capture. All proofs stay under the same booking reference, so the file shows what each party recorded.

Can the renter upload photos taken earlier with their own camera?

Not into a sealed proof. The capture page only accepts photos taken live, and picking a file from the gallery is not possible. Older photos can still be exchanged by your usual channels, but they carry no certified date and no integrity seal.

Does the proof decide who pays for the damage?

No. The proof shows what was photographed at pickup and at return, with a certified date and an integrity seal on each capture. It does not compare the photos, measure a scratch or assign responsibility. Your support team, an insurer or the parties draw the conclusions. The proof makes sure they argue about the vehicle and not about the files.

Does rental car damage proof work the same way for vans, bikes and tools?

Yes. The capture, the sealing and the verification are identical. Only the shot list changes, and you define it in a capture template: one for cars, one for vans, one for bikes, one for each family of equipment. The booking reference ties the handover proof and the return proof together in every case.

Try it in the sandbox

Rental car damage proof is a matter of method: the same shots at pickup and at return, taken live, sealed and dated by a third party. The booking reference then brings the two proofs into one file that either party can check. You can build and test the whole protocol for free in the sandbox, without a card.

Create an account

Official sources

Cédric Driaux · Founder of tryVidimus

Cédric Driaux is the founder of tryVidimus, published by Fyher. He has been a software developer for 23 years. He also builds ScanStay, a photo proof tool for short-term rental hosts.

Related articles