Skip to content
Standards8 min read

Qualified Electronic Timestamps Under eIDAS, Explained

A qualified timestamp under eIDAS is an electronic time stamp issued by a qualified trust service provider. In the European Union, it enjoys a presumption that its date and time are accurate and that the data it covers is unchanged.

By Cédric Driaux, Founder of tryVidimus

Drawing of a document and a clock inside a ring of dots

Simple vs qualified timestamp under eIDAS

A timestamp is a signed statement that a piece of data existed at a given time. It is one of the three standards behind trustworthy photos, next to C2PA and RFC 3161. The qualified timestamp under eIDAS is the version of it that carries a defined legal effect in the European Union.

Every timestamp works the same way. You send the fingerprint of a file to a service, the service adds its own time and signs the pair. What changes between a simple and a qualified timestamp is who the service is.

CriterionSimple electronic timestampQualified electronic timestamp
Who issues itAny service, including your own serverA qualified trust service provider
Can it be refused as evidence only because it is electronic?No (Article 41)No (same article)
Presumption of accuracy of the date and integrity of the data in the EUNot providedProvided by Article 41
How a reader checks the issuerBy trusting whoever runs the serviceBy looking the provider up on the European trusted lists

Take two rental companies. The first stamps its photos with the clock of its own server, the second sends each fingerprint to a qualified provider.

In a disagreement, the first has to convince the other side that its server clock was right and untouched. The second starts from a date issued by a third party whose status anyone can look up.

What eIDAS says: Article 41

eIDAS is Regulation (EU) No 910/2014, the European framework for electronic trust services. The rule on timestamps is in Article 41, published on EUR-Lex. It says two things.

  1. An electronic time stamp cannot be refused as evidence solely because it is in electronic form.
  2. A qualified electronic time stamp 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.

The first point applies to any electronic timestamp. It does not say that a timestamp wins an argument. It says that being electronic is not, on its own, a reason to set it aside.

The second point is specific to qualified timestamps. A presumption is a starting point, not a verdict: the date and the integrity are taken as accurate unless the party that disputes them shows otherwise. The other side can still bring evidence against it.

This presumption is a rule of European Union law. It applies in the European Union only. Elsewhere, a qualified timestamp remains a signed, verifiable record of the date, without that presumption.

Qualified trust service providers

A qualified timestamp comes from a qualified trust service provider. "Qualified" is not a marketing word here. It is a status, and a reader can check it without asking the provider or its customer.

The European Commission publishes a browser of the trusted lists. It shows, country by country, the trust service providers and the services each one is qualified for. Checking a provider takes three steps.

  1. Read the name of the timestamp authority in the timestamp token, or on the verification page of the proof.
  2. Find that provider in the trusted list browser, under its country.
  3. Check that its timestamp service is listed as a qualified one.

A provider can be qualified for one service and not for another. A company qualified for electronic signatures is not automatically qualified for timestamps. What counts is the timestamp service itself.

In production, tryVidimus requests its timestamps from Certigna, a French qualified trust service provider. On the technical side, the request and the token follow RFC 3161. Our RFC 3161 guide for developers shows what the token contains and how to check it with OpenSSL.

Applying a qualified timestamp to photos

A timestamp authority never sees a photo. It receives a fingerprint, a short value computed from the data, and signs that fingerprint together with its time. Any later change to the data gives a different fingerprint, and the token no longer matches.

Here is how tryVidimus applies this to a proof:

  1. The user takes the photos live on a web capture page opened from a link. There is no import from the gallery.
  2. Each file gets a SHA-256 fingerprint, and each photo is signed with C2PA.
  3. The proof receives one qualified electronic timestamp. The authority receives the fingerprint of the proof, never the photos.
  4. The proof has a public verification page, open without an account, that shows its status and its timestamp.

One timestamp covers the whole proof. A proof with six photos of a car does not need six dates: the timestamp binds one fingerprint that depends on all six files.

Why does live capture matter so much? Because a timestamp says that data existed at the latest at a given time, not when the scene happened. Stamp an old photo today, and you prove only that the file existed today.

Capture and timestamp have to go together for the date to mean something about the scene. Our article on how to prove when a photo was taken goes through the other methods and where each one fails.

Example: a policyholder in Lyon reports a water leak and photographs the ceiling through a capture link sent by the insurer. The proof is sealed, usually within seconds, with a date issued by a qualified provider. The adjuster does not have to rely on the date displayed by a phone.

Our article on photo evidence for insurance claims covers that sector, and the use cases page shows other sectors.

The limits of a qualified timestamp

A qualified timestamp is precise about what it covers. It is just as important to know what it leaves out.

  • It certifies a date and the integrity of data. It says nothing about what a photo depicts, who held the phone, or what state an object was really in.
  • It is not an electronic signature of the parties. Nobody has agreed to anything by being photographed or by taking a photo.
  • The presumption applies in the European Union only.
  • A presumption can be challenged. It is a strong starting point, not the end of the discussion.
  • The "captured at" time shown for each file is the time observed by the service. It is not qualified: only the time certified by the timestamp authority is.

These limits are the reason we describe the product as certifying, never arbitrating. A sealed proof gives both sides a date and a file they can check; deciding what follows from them belongs to the parties, an insurer or a judge. The standards page states the same limits in full.

Frequently asked questions

What is a qualified electronic timestamp?

It is an electronic time stamp issued by a qualified trust service provider, as defined by the eIDAS Regulation. It binds the fingerprint of some data to a date and time, in a signed token. In the European Union, Article 41 gives it a presumption of accuracy of the date and time, and of integrity of the data.

What does Article 41 of eIDAS say?

Article 41 says two things. An electronic time stamp cannot be refused as evidence solely because it is in electronic form. And a qualified electronic time stamp 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. The official text is on EUR-Lex.

How can I check that a timestamp provider is qualified?

Look it up on the European trusted lists. The European Commission publishes a browser where each country lists its trust service providers and the services each one is qualified for. Find the authority named in the timestamp token, then check that its timestamp service appears as qualified. No account is needed.

Is a qualified timestamp valid outside the European Union?

The presumption of Article 41 is a rule of European Union law and applies in the EU only. Outside it, the timestamp is still a signed record that anyone can verify with standard tools, but it does not carry that presumption. Its weight then depends on local rules of evidence, so ask a lawyer for a specific case.

Does a qualified timestamp prove when a photo was taken?

Not by itself. It proves that the file existed at the latest at the certified time, and has not changed since. To say something about the moment of the scene, the photo must be captured live and sealed right away, with no import from the gallery. That is why tryVidimus combines live capture and a qualified timestamp.

Does the timestamp authority receive my photos?

No. The authority receives a fingerprint, such as a SHA-256 hash, and signs it with its time. A fingerprint cannot be turned back into the data it was computed from. With tryVidimus, the authority receives the fingerprint of the proof, never the photos, which stay in storage hosted in the European Union.

Try it in the sandbox

A qualified timestamp under eIDAS gives a photo a date issued by a third party whose status anyone can check, with a presumption of accuracy in the European Union. It does not say what the photo shows, and it only means something about the scene when the photo is captured live. You can build the whole capture journey for free in the sandbox, without a card, keeping in mind that sandbox timestamps are simulated.

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