Qualified timestamp (eIDAS)
Your first qualified timestamp is free. After that, €6 per file or from €1.50 in packs.
You get the timestamp (.tsr) and the certificate of the authority that signs it, both issued by the FNMT-RCM. It is issued in seconds.
It is checked with OpenSSL or any RFC 3161 validator, without relying on Sellat.
You need a free account. In the tool the timestamp arrives already ticked: you choose the file and it is issued when the proof is created.
See timestamp packs → I already have a timestamp: I want to verify it →Before you pay
Every Sellat proof carries the public anchor, free. The qualified timestamp is a layer added on top when the situation calls for it.
| Situation | What fits | Why |
|---|---|---|
| A private dispute where the other side can check the proof (a deposit, a delivery to a client, the priority of an idea) | Free anchor | Anyone can verify the technical proof, it does not expire and it costs nothing. |
| Court or administrative proceedings, or a third party that requires a recognised timestamp | Qualified timestamp | Presumption of accuracy and integrity (art. 41.2 eIDAS): it does not depend on an expert explaining the blockchain. |
| You do not know where it will end up | Both | The timestamp costs €6 and cannot be backdated: requesting it later carries the later date. |
They are two different dates and are always shown separately: the public anchor’s and the qualified timestamp’s. If you request the timestamp later, it carries the date of the day you request it.
What it is
It adds to your proof a qualified timestamp issued by the FNMT-RCM (Fábrica Nacional de Moneda y Timbre), a qualified trust service provider under Regulation (EU) 910/2014 (eIDAS).
A qualified electronic timestamp enjoys the presumption of the accuracy of the date and time it indicates and of the integrity of the data to which it is bound (art. 41.2 of Regulation (EU) 910/2014), across the European Union. The presumption can be rebutted, but it is whoever disputes it who has to do so.
The timestamp is issued over your file’s SHA-256 fingerprint and is included in your proof; anyone can verify it with standard tools (RFC 3161) against the European Union trusted list, without relying on Sellat.
Sellat obtains the timestamp through an authorised distributor of the FNMT-RCM time-stamping service. Sellat is not the authority: the FNMT-RCM issues the timestamp and Sellat requests it, checks it and keeps it inside your proof.
The timestamp does not establish who the author or owner of the file is, nor the content of any agreement: it establishes that this exact file existed at that moment.
Inside the package
Not a promise and not a screenshot: the real list of files Sellat puts in your ZIP. What you see here is generated by the same module that builds the package.
original/<archivo> If the original is kept The exact photo you sealed, in a folder of its own so no other file in the package can be mistaken for it. It travels inside when the original is available: the upload that created the proof, or custody.
certificado-<id>.pdf Always The PDF you show a person or attach to a filing. It is an informative document: what actually gets checked is the file, not the PDF. If the file carried Content Credentials (C2PA), the certificate records them too — who signed, with which tool and whether they declare AI use — exactly as your browser read them when you protected it.
proof.json Once the batch is anchored Your file fingerprint, its Merkle leaf and inclusion path, the batch root and the public transaction that records it. This is the piece that lets anyone check everything without Sellat.
sello-cualificado-<id>.tsr With a qualified seal The RFC 3161 response from the qualified timestamping authority, exactly as it was issued. This is the file that fixes the date under eIDAS.
autoridad-sellado.pem With a qualified seal That authority signing certificate, with its SHA-256 written into the README. It travels inside so the check works offline and nobody has to go looking for it.
anclaje-bitcoin.ots Once the batch is anchored The OpenTimestamps proof of the batch root. It may still be waiting for a block: it is a valid file and whoever receives it can upgrade it themselves.
LEEME.txt / README.txt Always What each file is, what it proves and what it does not, and the exact commands to check it. In Spanish and English, so an expert or a lawyer never has to ask you anything.
With the seal and the authority certificate inside the ZIP, the date is verified with standard tools on the machine of whoever receives it. If Sellat disappeared tomorrow, your package would still check out.
The package proves that this exact file existed on that date and has not been modified. It does not prove who created it, who took the photo, or what happened in front of the camera.
How it works
The timestamp is issued in seconds, as soon as the payment is confirmed.
In the tool, Sellat creates the proof with its SHA-256 fingerprint and the public anchor. This is free.
With a free account, on the same screen, or later from that file’s certificate. You pay once, for that file.
The certificate gives you the .tsr, the .tst token and the authority’s certificate. The evidence package carries them inside.
Sellat only calls a timestamp “qualified” when the authority that signed it appears as a qualified, granted service on the EU trusted list, checked at the moment of issue.
What you get
Everything someone else needs to check the timestamp on their own.
The authority’s complete response under RFC 3161: the status of the request and the signed token.
The CMS token on its own, for validators that only accept that format.
The certificate the timestamp was signed with, which is what is needed to verify it offline.
The readable document with the file, the date, the authority, the serial number and the fingerprint.
The file you protected together with all of the above and the instructions to check it.
The proof in an open format, verifiable with the open-source verifier sellat-verify.
Scope
That this exact file existed on the date and at the time the timestamp indicates, with the legal presumption the Regulation grants a qualified timestamp across the European Union.
It does not establish who the author or owner of the file is, nor that what its content says is true, nor who is right in a dispute. Nor does it replace any public register.
Price
No subscription and no mandatory pack: €6 per timestamp. Your first qualified timestamp is free. One per account, on the proof you choose. After that, €6 per timestamp. If you need volume, Pricing has packs of timestamps.
Add a qualified timestampFrequently asked questions
Any electronic timestamp counts as evidence and cannot be dismissed solely for being digital (art. 41.1). The qualified one, issued by a provider on the EU trusted list, adds the legal presumption of the accuracy of the date and of the integrity of the data (art. 41.2): whoever disputes it has to prove otherwise.
The Fábrica Nacional de Moneda y Timbre - Real Casa de la Moneda is a Spanish qualified trust service provider. The trusted list is the register each Member State publishes of its qualified providers and services; Sellat checks the signing certificate against a dated copy of that list before calling anything “qualified”.
The presumption of article 41.2 is recognised in the 27 Member States of the European Union. Outside the EU the timestamp can still be verified technically with standard tools, but that specific presumption is European.
With the .tsr, the file and the authority’s certificate, using OpenSSL or any RFC 3161 tool. They can also do it from the browser in this site’s timestamp validator, which tells them point by point what holds and what does not.
To create the proof, no: your email is enough. For the qualified timestamp a free account is needed, because the order, the invoice and the proof have to be linkable to a person.
The timestamp is added to one proof at a time. If you need volume, Pricing has packs of timestamps, and the API lets you integrate it into your own systems.
There are, and they are useful: a free RFC 3161 timestamp proves the same thing technically. What they do not give is the legal presumption of article 41.2, which only a timestamp issued by a qualified provider carries. If what you want is a checkable date, Sellat’s public anchor is free; if you want the presumption, this is the timestamp you pay for.
You are not charged for a timestamp that does not exist: if issuance fails after payment, the amount is refunded. Sellat does not mark a proof as qualified until it has verified the timestamp against the trusted list.
In the tool the timestamp arrives already ticked: you choose the file and it is issued in seconds.
Add a qualified timestamp