- ⚠️ The signature covers the flattened fields and the certificate, because signing happens last. One applied before the certificate was appended would either be invalidated by appending it or — worse — stay technically valid while covering only part of what a reader sees.
- ⚠️ A live seal is a PAdES signature with long-term validation and an RFC 3161 timestamp — everything needed to verify it is inside the file, and verifying it never asks us anything. It is not yet trusted, though: our AATL certificate has not arrived, so we sign with one this organisation issued to itself, and Adobe Reader reports “signature validity unknown” on it. That is correct — no public trust store carries the issuer — and your recipients will see the yellow bar. The seal is intact and the audit trail proves who signed independently of the certificate, but we would rather you heard this from us than from a customer. Swapping in the AATL certificate is configuration on our side, not a release of this product; documents sealed before the swap keep the certificate they were sealed with. The swap moves the live certificate only: the sandbox seals under separate configuration of its own, so nothing you rehearse against the sandbox changes on the day the AATL certificate arrives.
- ⚠️ A sandbox seal is a real seal by a certificate that is not our binding one. Every page is watermarked, the seal covers the watermark, and your PDF reader will report the signature as intact and its issuer as untrusted — which is exactly the case your verification code needs to handle and the one you would otherwise never get to rehearse. The certificate itself names a sandbox authority, so a verifier reading nothing but the signature panel can tell a test document from a real one. Which of the two you get is decided by the credential that created the envelope, and is never inferred later.
-
The certificate says how each party who acts — a signer or an approver — was authenticated,
and only what the audit trail proves. It states a one-time code only where the audit trail
records the code being entered, and says nothing about one otherwise
(how to ask for a code). A party copied in acts on
nothing and is issued no link, and the certificate says that too:
Where the audit trail records a one-time code being entered, the line goes on to say so — for example “Email link with expiring token, plus a one-time code by email to j•••@example.com, entered 01 Oct 2026, 12:02:11”. A mobile code names the way it actually went: “Email link with expiring token, plus a one-time code sent on WhatsApp to +27 •• ••• •567, entered 01 Oct 2026, 12:02:11”, “Email link with expiring token, plus a one-time code by SMS to +27 •• ••• •567, entered 01 Oct 2026, 12:02:11”, or, when WhatsApp could not reach the signer in time and the same code was texted, “Email link with expiring token, plus a one-time code sent on WhatsApp, then by SMS, to +27 •• ••• •567, entered 01 Oct 2026, 12:02:11”; and where the audit trail cannot say which of the two carried it, “Email link with expiring token, plus a one-time code sent on WhatsApp or by SMS to +27 •• ••• •567, entered 01 Oct 2026, 12:02:11”. On a test document, whose code is shown on screen rather than sent, it reads “Email link with expiring token, plus a one-time code shown on screen (test document: nothing was sent), entered 01 Oct 2026, 12:02:11”.
- A sealed document is not recallable. Rehearse with a test key.
Roles left out of an envelope
When a template role is optional and an envelope is sent without anybody for it, the certificate says so. It says what the envelope held, not that no such person exists. See Roles and recipients. After the parties, the certificate lists each optional role the envelope was sent without, one line each, in the template’s order. The time is when the envelope was sent, in UTC:Surety: not on this envelope. Left out by the sender when it was sent, 18 Oct 2026, 08:00:00. Witness 2 (witness): not on this envelope. Left out by the sender when it was sent, 18 Oct 2026, 08:00:00.
Who this form is about
When a form is about people who may or may not be on it, such as a co-tenant or a surety, the certificate says who was on this form and how that was decided, by the sender or by a signer on the page. Like the line above, it says what the envelope held, not that no such person exists. See Subjects. After the parties, a section headed “Who this form is about” has one line for each person the form is about, in the form’s order. It says whether they are on this form and how that was decided, and it lists every declaration about them, oldest first. An answer quotes the question the signer was shown. Times are in UTC. For example:Tenant: on this form. Always: the form is about them. Co-tenant: not on this form. Asked “Co-tenant: is there one on this form?”; Jane Dlamini answered No, 18 Oct 2026, 10:02:00. Surety: on this form. Included by the sender; not changed. Sibling 3: on this form. Asked “Sibling 1–3: how many are on this form?”; Jane Dlamini answered 2, 18 Oct 2026, 10:02:00; changed on the page by Jane Dlamini to Yes, 18 Oct 2026, 10:09:00. Guarantor 2: not on this form. Left out, because nobody signing holds this section, 18 Oct 2026, 08:00:00. Co-applicant: on this form. Included, because they sign this envelope, 18 Oct 2026, 08:00:00.