Electronic Timestamps and Long-Term Validation (LTV)

A standard digital signature is verifiable only while the signing certificate is valid (typically 1-5 years). After expiry, you cannot confirm whether the signature was created during validity — unless a trusted timestamp proves it.

LTV embeds all validation data within the signature: the signing certificate, its chain, revocation data (CRL/OCSP), and the timestamp. This allows verification even after the certificate expires — because the embedded data proves everything was valid at signing time.

Level B: basic signature. T: adds trusted timestamp. LT: adds validation data (certificates, revocation). LTA: adds periodic re-timestamping for indefinite validity. For contracts and regulatory documents, LT or LTA is recommended.

Many regulations require document retention for years (employment: 2-7 years, financial: 5-10 years, medical: up to 30 years). Without LTV, signatures on archived documents may become unverifiable. LTV ensures the evidence remains valid for the entire retention period.

Qualified timestamps must come from a Time Stamping Authority accredited under eIDAS Article 40 (EU) or equivalent national framework. The timestamp token must conform to RFC 3161 (Time-Stamp Protocol). TSA certificate validity is typically 4-6 years; timestamps must be renewed before certificate expiry for continued validation.

Qualified timestamp pricing: $0.01-0.05 per timestamp at volume (100K+/month), $0.10-0.50 per timestamp at low volume. Some QTSPs bundle timestamps with QES subscriptions at no additional cost. Annual TSA service contracts start at $2,000-5,000/year for enterprise usage.

B-LT embeds revocation data (CRL/OCSP) at signing time, adding 10-50 KB per signature. B-LTA adds archival timestamps, growing the document by 5-15 KB per re-timestamp. For a 100-signature approval chain over 10 years, B-LTA storage reaches 5-8 MB — significant for high-volume archival systems.

A TSAlite (non-qualified) timestamp provides evidence of existence but does not receive the presumption of validity under eIDAS Article 41. In EU litigation, only qualified timestamps receive the same evidentiary presumption as QES. Outside the EU, courts evaluate timestamp weight case-by-case regardless of qualification status.

EU MiCA (Markets in Crypto-Assets Regulation): requires timestamped records for crypto-asset transactions. FDA 21 CFR Part 11.50: requires date and time stamps for all electronic signature manifestations. China's Electronic Signature Law: timestamps strengthen evidence of signing time but are not mandatory. Singapore MAS guidelines: financial transaction records should include trusted timestamps for audit trails.

In contract disputes, the critical question is often "when was this signed?" A qualified timestamp from an accredited TSA provides presumption of accuracy under eIDAS Article 41. Without a trusted timestamp, the signing time relies on platform server logs — which are less convincing in court. For cross-border agreements where parties are in different time zones, UTC timestamps with timezone conversion records prevent ambiguity.

For documents requiring decades of verifiability (real estate, patents, government records), PAdES B-LTA archival timestamps must be renewed before each timestamp certificate expires. This creates a chain of timestamps proving the document existed at each point in time. eSign.AI's archival system automates this renewal process, ensuring signatures remain verifiable for the full retention period required by law.