Understand · Concept

Simple Signature Recipe

Overview

A simple electronic signature (SES) has two jobs: record evidence of who signed and that they agreed (an email link or one-time code, plus an audit trail), and show that the document has not changed since and that the signing date is trustworthy. This recipe goes through the essential steps for each job, then the options for the date and integrity part, and the risks to address.

What a digital signature is

A digital signature is a cryptographic seal computed over the document with a private key held by the signer. The signer’s certificate, which carries the public key and is issued to a named identity, lets anyone check the seal. If a single byte of the document changes after signing, the check fails. That is the integrity part of the recipe.

See it in practice. The Acrobat worked example creates a Digital ID, signs a PDF, adds a timestamp, and shows the validity check Acrobat displays. It is an illustration, not a production setup.

Chain 1: identity and consent

An SES does not prove identity cryptographically. It gives procedural evidence: control of an email address or phone, consent, and a trace of the session. Keep that evidence, because it is what you will show if the signature is contested.

  1. Identify the signer. Use a verifiable channel, typically a one-time code (OTP) sent by email. Decide who performs the identity check and what evidence you keep.

  2. Obtain consent. Make the signer accept the terms explicitly before they sign.

  3. Show the document. The signer must be able to read the content before signing.

  4. Collect an explicit signature. A deliberate action, not a passive one. A scanned handwritten signature is not an electronic signature.

  5. Keep a recap and a copy. Give the signer a summary and a downloadable copy, and keep the traces (timestamps, IP, OTP events) for later proof.

Chain 2: integrity and date

  1. Fix the signing date with a trusted timestamp. An RFC 3161 timestamp from a qualified timestamp authority (TSA) gives a presumption of accuracy for the date (eIDAS, Articles 41 and 42).

  2. Make tampering detectable. An electronic seal on the document shows that it has not changed after sealing and which certificate sealed it. A seal from your own certificate authority identifies your organisation only to validators that trust your root. A seal from a trust service provider is trusted by default.

  3. Keep the proof file. Store the signed document, the timestamp token and the evidence together.

Timestamp scenarios

Scenario Advantages Drawbacks

1. Timestamp the PDF at each step

Simple. Verifiable in Adobe Acrobat alone.

One timestamp per step. Many tokens to keep.

2. Detached timestamp token

Lightweight. Does not change the document.

Verification needs the original file and the token, outside Acrobat.

3. ASiC-E envelope sealing all documents with a timestamp

One proof for the whole set of documents, with a single timestamp.

Not verifiable in Acrobat alone. Needs a dedicated verification tool.

4. PDF seal per signer (PDF-BT)

Each signer seals the document, so tampering is visible in the PDF.

Depends on the signer’s seal and certificate chain.

Recommendation

Combine an ASiC-E envelope with an electronic seal, if your legal context accepts it. Otherwise, add timestamps at the key steps (signing, final version). Choose the scenario according to who must verify the proof and with which tools.

Where to go next

The recipe is the model. The tutorials apply it.

Recipe chain DocuSeal setup Acrobat worked example

Chain 1: identity and consent

Step 6, consent and step 7, email identification

Not covered. Acrobat signs with a certificate, it does not identify a signer by email.

Chain 2: integrity and date

Step 4, seal, step 5, timestamp and step 9, verify

Part A, sign and part B, timestamp

To compare your options, use choose your setup. Before you use a setup for real documents, read the evidence file checklist and running it for real.

Are you looking to strengthen the evidential value of your electronic signatures?

Tell us more