Skip to content
Team EditSign

Certificate of completion

When the last signer finishes, the service produces the signed PDF: the original document with every field filled in, form fields flattened so they can’t be changed, and one or more Certificate of Completion pages added at the end.

What the certificate contains

Section titled “What the certificate contains”

All times are in UTC.

The document

  • Document title and Envelope ID
  • Number of pages (plus the certificate)
  • Original SHA-256: the fingerprint of the PDF as it was sent
  • Sent by (name and email), when it was sent, when it was completed
  • Signing order: Sequential or Any order

Each recipient

  • Name and email, and role: Signer or Receives a copy
  • For signers: when they viewed it, when they signed, their IP address and browser, their signature image, and Agreed to sign electronically

The consent text every signer agreed to:

I agree to use electronic records and signatures, and I intend my electronic signature to have the same legal effect as a handwritten signature.

Checking a signed PDF hasn’t changed

Section titled “Checking a signed PDF hasn’t changed”

The Signed SHA-256 of the final file is shown on the request’s page under Signing, and recorded in the activity log when the request completes. (It can’t be printed inside the file itself, since adding it would change the file.) To check a copy, compute its SHA-256 and compare:

Terminal window
Get-FileHash -Algorithm SHA256 "Contract (signed).pdf"

If the values match, the file is exactly the one the service produced. Any change, even re-saving it in another program, gives a different value. The same check works for the original with Original SHA-256.