On this page
How to use this checklist
A photo evidence API comparison is hard to make from feature pages. Every vendor writes "certified" and "verified". The words only mean something once you know who certifies and who can check.
The ten questions below are meant to be sent to every vendor, as they are. We publish tryVidimus, so each question also carries our own answer, including the cases where it is "no".
For each one, ask the vendor how you could check the answer yourself. If you want the technical background first, read our developer guide to the photo evidence API.
Questions 1 to 3: the capture
Question 1: can a photo come from the gallery? This is the first question because everything else depends on it.
If a file can be imported, it can come from another day, another object or an editing app. A timestamp then only shows that the file existed when it was stamped.
Our answer: no. tryVidimus accepts live capture only. The limit: a photo taken outside the capture page cannot be sealed afterwards.
Question 2: where does the capture run? Some products need their own app, some provide a mobile SDK, others open a web page. Each choice has a cost: an install for your users, a dependency in your app, or a camera running in a browser.
Our answer: a web page, opened from a link, in the browser or in a web view, with your logo, your color and your texts. There is nothing to install. There is also no mobile SDK: if you need a native camera component inside your app, tryVidimus does not provide one.
Question 3: do the files pass through our servers, or yours only? If your platform relays the photos, the other party can say you changed them on the way.
Our answer: the file goes from the phone straight to storage. It never passes through your servers.
Questions 4 and 5: the date and the standards
Question 4: who certifies the date? The phone's clock can be changed, and a date certified by the vendor alone is the vendor's word. Ask for the name of an independent authority, and for its status.
In the European Union, the reference is the qualified electronic timestamp. Under Article 41 of the eIDAS Regulation, it enjoys a presumption of the accuracy of the date and time it indicates and of the integrity of the data to which they are bound. Qualified providers appear on the European trusted list, which you can consult yourself.
Our answer: in production, each proof receives one qualified electronic timestamp, issued by Certigna, a French qualified trust service provider. The authority receives the fingerprint of the proof, never the photos. The "captured at" time, observed by the service, is not qualified.
Question 5: which open standards do you follow, and can you show conformance? A proprietary format ties the proof to the vendor, while open standards let other tools read it. Ask for a document, not a logo.
Our answer: SHA-256 fingerprints, RFC 3161 timestamps and a C2PA signature on each photo. tryVidimus is a C2PA conformant generator product, under a conformance letter dated 19 October 2026, at assurance level 1, for JPEG photos. Our standards page states what each standard covers, and its limits.
Questions 6 to 8: verification and scope
Question 6: can a third party verify a proof without an account, and without you? A proof that only the vendor can confirm moves the trust problem instead of solving it.
Our answer: each proof has a public verification page, open without an account. The verifier is open source, under the MIT licence, and the timestamp can be checked with OpenSSL. Keep the signed copy and the verification data of each proof, and you can check it without our servers.
Question 7: what does a proof show, and does your product decide anything? Some platforms analyse images, score risk or recommend an outcome. That can be valuable, and it makes the vendor a participant in the decision.
Our answer: tryVidimus certifies and never arbitrates. A sealed proof shows that a file existed at a certified date, has not changed since and came from a live capture. It does not say that the scene is truthful, who held the phone, or what state the item was really in.
Two limits follow. Two proofs can be linked as "before" and "after", but the product does not compare the photos and does not judge a damage.
And there is no fraud detection or image analysis. If you need those, look at a full inspection platform: our page on Truepic alternatives says when that is the better choice.
Question 8: which content is covered? Ask what is sealed today, in production, not what is on a roadmap.
Our answer: photos, and only photos, taken live on the capture page. If you must certify web pages, meetings or other kinds of content, tryVidimus is not the right tool.
Questions 9 and 10: data, integration and cost
Question 9: where is the data hosted, and how long is it kept? You need the hosting region and the retention period for your own privacy documentation. Ask, too, what the timestamp authority receives.
Our answer: tryVidimus is hosted in the European Union, and proofs are kept for 24 months. The timestamp authority receives a fingerprint, never the photos.
Question 10: how do we start, test and pay? Can your developers try the whole journey alone?
Is it clear that test proofs are worthless as evidence? Does the pricing model match your volume, or does it start with a commitment?
Our answer: you create an account and build in test mode for free, without a card. Test timestamps are simulated and have no legal value.
In production you pay per sealed proof, from a prepaid balance, without a subscription. The price is on the pricing page.
On the integration side, tryVidimus offers an API in plain JSON over HTTPS, signed webhooks, API keys with scopes, capture templates, and packages on npm.
The photo evidence API checklist in one table
Copy the first column into your request to each vendor. The second is our own answer, so you can hold us to it.
| Question | Our answer (tryVidimus) |
|---|---|
| 1. Can a photo come from the gallery? | No: live capture only |
| 2. Where does the capture run? | A branded web page. No app to install, no mobile SDK |
| 3. Where do the files go? | Straight to storage, never through your servers |
| 4. Who certifies the date? | Certigna, one qualified eIDAS timestamp per proof |
| 5. Which standards? | SHA-256, RFC 3161, C2PA conformant for JPEG photos |
| 6. Who can verify? | Public page, open-source verifier, OpenSSL |
| 7. Does the product decide? | Never. No comparison of photos, no fraud detection |
| 8. Which content? | Photos only |
| 9. Where is the data? | European Union, 24 months |
| 10. How do we start and pay? | Free test mode, then per sealed proof, prepaid |
No vendor wins on every line, and some lines will not matter to you. What matters is that each answer is specific, dated and checkable.
Frequently asked questions
What is the most important question to ask a photo evidence vendor?
Whether a photo can come from the gallery. If it can, the rest of the chain protects a file whose origin is unknown: the timestamp shows when the file was stamped, not when the scene happened. Ask next who certifies the date, and whether an outsider can verify a proof without the vendor.
Is a qualified timestamp required for photo evidence?
No rule we can cite makes it mandatory, and this is not legal advice. In the European Union, a qualified electronic timestamp benefits from a presumption of accuracy of the date under Article 41 of the eIDAS Regulation, which an ordinary timestamp does not have. Elsewhere, it remains a signed and verifiable record of the date.
Should I choose a mobile SDK or a web capture page?
It depends on your app. A mobile SDK gives a native camera inside your app, at the price of a dependency to maintain on each platform. A web capture page needs nothing installed and works from a link, in a browser or a web view. tryVidimus offers the web page only.
How do I check that a vendor's timestamps are really qualified?
Ask for the name of the timestamp authority, then look it up on the European trusted list, which is public. Then verify a real timestamp token yourself: a token that follows RFC 3161 can be checked with OpenSSL against the certificate chain of the authority. A vendor that cannot give you a token to check has not answered the question.
What does tryVidimus not do?
Several things, by design. It has no mobile SDK and accepts no import from the gallery. It seals photos and no other kind of content. It does not compare a "before" with an "after", does not detect fraud and does not decide who is right. It certifies what was captured and when, and leaves the judgment to you.
Try it in the sandbox
A photo evidence API comparison comes down to ten answers you can check yourself, from the origin of the photo to the way you pay. Send the same questions to every vendor, and keep the ones who answer with facts. To check our answers, you can build and test the whole journey for free in the sandbox, without a card.
Create an accountOfficial 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.