Skip to content
Use cases8 min read

Verified Photos for Insurance Claims: What a Sealed Capture Proves

A sealed, live capture tells the claims handler three things about insurance claim photos: they came from the camera at that moment, when they were sealed, and that they have not changed since. It does not assess the damage.

By Cédric Driaux, Founder of tryVidimus

A water-stained ceiling, photographed in a wide shot for a claim

The problem with insurance claim photos: nobody can tell where they come from

Most claims now start with photos. The policyholder takes a few pictures of the ceiling, the bumper or the roof and sends them by email, through a form or in a messaging app. This article is part of our overview of photo evidence use cases by industry, and it looks at that first step.

The claims handler who opens those files sees a picture of damage. Three questions stay open every time:

  • Where does the photo come from? A file attached to an email can come from the phone's camera, from the gallery, from another person or from a website.
  • When was it taken? The date stored in the file is written by the phone and can be edited afterwards. The date of the email only says when the file was sent.
  • Has it changed? A crop, a retouch or a generated image can look exactly like an untouched photo. Our article on how to prove a photo was not edited explains why looking at the picture is not enough.

Take a water leak. The policyholder says the leak stained the ceiling on the third of the month and sends two photos. The insurer can answer, fairly, that nothing shows these photos were taken that day. An honest policyholder has no way to show it.

Where a sealed, live capture fits in the claim

The change happens at one precise point: the moment the policyholder shows the damage. The policyholder no longer attaches files. They open a link and photograph the damage live, on a capture page, with no way to pick a file from the gallery.

tryVidimus is an API built for that step. Your claims application calls it with the claim number, and gets back a capture link to send to the policyholder. The page opens in the phone's browser, with your logo, your colours and your wording. There is nothing to install.

Once the photos are taken, the proof is sealed. Each file gets a SHA-256 fingerprint, each photo is signed with a C2PA manifest, and the proof receives a qualified electronic timestamp. Our guide to the qualified timestamp under eIDAS explains what that timestamp is and who issues it.

The handler's questionWith an emailed photoWith a sealed, live capture
Where does it come from?Unknown: camera, gallery, another person or the web.From the camera, on the capture page. Gallery import is not possible.
When does it date from?The phone's clock or the date of the email.A qualified timestamp, issued by an independent authority when the proof is sealed.
Has it changed?No way to tell from the file.Any change breaks the fingerprint and the signature, and anyone can check.
Who can check?Nobody outside the two parties.Anyone with the link to the public verification page, without an account.

A remote assessment workflow, step by step

  1. The policyholder reports the claim, by phone, in your app or on your website. Your system opens the claim file and gives it a number.
  2. Your application creates a capture for that claim number, with a shot list suited to the type of claim: for water damage, a wide shot of the room, the stained area, then a close-up.
  3. You send the capture link by text message or email, or you open it inside your own app. The policyholder follows the list and takes each photo live.
  4. The files go straight to storage. They do not pass through your servers, so nobody can say you altered them.
  5. The proof is sealed, and a signed webhook tells your system that it is ready. Your claims tool attaches the proof to the file.
  6. The handler opens the proof from the claim file. They see the photos, the timestamp and the result of the integrity checks, and they decide what happens next.

One detail matters for the record. The proof carries two times. The capture time is the time observed by the service, and it is not qualified. The qualified time is the one set by the timestamp authority when the proof is sealed. The two are usually seconds apart, but only the second one carries the legal presumption.

What changes for claims handlers and loss adjusters

  • The origin question is answered before the file is opened. The handler knows the photos were taken live, on the capture page, for this claim number.
  • The date is set by a third party. Neither the policyholder nor the insurer wrote it, so neither can be suspected of moving it.
  • The adjuster can check alone. The verification page is public, and the open-source verifier checks a proof without relying on our servers.

The limits are just as clear. A sealed capture does not say that the leak happened that day: it says that the ceiling looked like this when the proof was sealed. The capture removes the doubts about the file, so that the handler's attention goes to the facts: our position is to certify, never to arbitrate.

Integration options for a claims application

The capture is a web page, so it fits wherever a link fits. There is no mobile SDK to embed and no app for the policyholder to download.

  • A link in a message. Your system creates the capture and sends the link by text message or email, right after the claim is reported.
  • A webview in your app. If the policyholder already uses your mobile app, the same page opens inside it.
  • A shot list per type of claim. Capture templates set the photos to take and the texts shown to the policyholder: one for water damage, one for storm damage, one for vehicle damage.
  • A webhook to your claims tool. The signed proof.sealed event tells your system when the proof is ready, so the file updates on its own.

The claim number is the thread. Every capture created for a claim carries your reference, and your application lists the proofs of that claim with it.

The timestamp authority receives the fingerprint of the proof, never the photos. Hosting is in the European Union. Proofs are kept for 24 months.

You can build the whole journey in the sandbox first: its timestamps are simulated and have no legal value. The use cases page shows the claim capture next to the other journeys, and the documentation covers the calls. The price per sealed proof is on the pricing page.

Frequently asked questions

Does a sealed photo prove that the damage is real?

No. A sealed photo shows that a file came from a live capture, existed at a certified date and has not changed since. It does not say that the scene is truthful, what caused the damage or who held the phone. The claims handler and the loss adjuster still assess the claim. What they no longer have to question is the file itself.

Does tryVidimus detect insurance fraud?

No. tryVidimus does not score photos, compare them or flag suspicious claims. It attests three things: the origin of the photos (a live capture, with no gallery import), the date of the proof (a qualified timestamp) and its integrity (a fingerprint and a signature). Deciding whether a claim is honest remains the insurer's job, with its own tools and its own people.

Can a policyholder send a photo taken earlier?

Not through the capture page. The camera is the only source, and picking a file from the gallery is not possible. If the damage happened days ago, the capture shows its state on the day of the capture, with that date. Earlier photos can still be sent by your usual channels, but they are not sealed and do not carry the same assurance.

Who can verify insurance claim photos once they are sealed?

Anyone who has the link. Each proof has a public verification page that opens without an account: the claims handler, the loss adjuster, the policyholder or a lawyer sees the same result. The verifier is open source, and the timestamp can also be checked with OpenSSL, so the check does not depend on trusting us.

What legal weight does the timestamp carry?

In the European Union, a qualified electronic time stamp enjoys a presumption of accuracy of its date and time and of integrity of the data it is bound to, under Article 41 of the eIDAS Regulation. That concerns the date and the file, not what the photo depicts. Elsewhere, it remains a signed, verifiable record. This is not legal advice.

Try it in the sandbox

Insurance claim photos are useful when the handler can check where they come from, when they were sealed and that nothing changed. A sealed, live capture answers those three questions and leaves the assessment of the damage to the people whose job it is. You can build and test the whole claim capture 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