Evidence

PAdES seals and RFC 3161 timestamps, explained plainly

What PAdES seals, RFC 3161 timestamps and AATL certificates are, what each one proves about a signed PDF, and how AccordSeal uses each one.

By the AccordSeal team · Updated · 6 min read

E-signature vendors use a lot of abbreviations. Three of them describe what happens to your PDF at the end of signing, and they are worth understanding because they determine what you can prove later.

PAdES: a seal inside the PDF

PAdES stands for PDF Advanced Electronic Signatures. It is a standard for placing a cryptographic signature inside a PDF file. The signature covers the content of the file, so if anything in the file changes afterwards, the signature no longer validates and a PDF reader will say so.

When a platform applies this on its own behalf at the end of a workflow, it is usually called a seal: the platform is certifying “this is the document as completed”.

PAdES comes in levels, each adding to the last:

LevelWhat it addsAccordSeal
B-BThe basic signature over the document.Included
B-TA trusted timestamp proving when the signature existed.Included
B-LTEmbedded validation data (certificates and revocation information), so the signature can be checked later without contacting anyone.Included
B-LTAArchive timestamps that can be renewed, keeping the signature verifiable for decades.Included

AccordSeal seals every final PDF and every certificate of completion with PAdES, using a detached CAdES signature and a DocMDP setting that marks the document as certified. Long-term validation (LT and LTA) is supported.

RFC 3161: a timestamp from someone else

RFC 3161 is the internet standard for trusted timestamps. The platform sends the hash of the data — never the document itself — to a timestamp authority. The authority signs a token saying “this hash existed at this time” and sends it back.

The value is independence. The time comes from a third party whose business is keeping accurate time and protecting its signing keys, not from the system that holds your document.

AccordSeal uses DigiCert's timestamp authority in two places:

  • On each seal, which is what the B-T level adds.
  • On the audit chain. At regular intervals the current head of the hash-chained audit log is timestamped. This anchors the entire history up to that point: to rewrite an old event, someone would have to forge a timestamp from an independent authority.

AATL: whether the reader trusts the seal

A seal is made with a certificate, and a certificate is only as meaningful as whoever issued it. The Adobe Approved Trust List is a list of certificate authorities whose certificates Adobe Acrobat and Reader trust automatically. A seal made with an AATL certificate shows a green tick with no extra steps.

AccordSeal seals are made with an AATL document-signing certificate.

In practice, that means:

  • The seal detects any change to the PDF.
  • The timestamp is issued by an independent authority.
  • Adobe Acrobat and other AATL-aware readers show the seal as trusted, with no manual steps.
  • Anyone can also confirm a document is genuine on the public verification portal.

Which of this do you need?

For most commercial agreements, the practical questions are whether the document has changed and when it was completed. A B-T seal and an independent timestamp answer both. If you must keep documents verifiable for many years without relying on any online service, look for LT or LTA support, which AccordSeal includes. If your counterparties expect the green tick in Acrobat, the AATL certificate is what provides it.

Run your next agreement from draft to proof.

Start with the Free plan, or ask us to walk your team through AccordSeal with your own documents.