Signature Validity and the Trusted Seal

Once a contract is signed, anyone you send it to needs to trust that the PDF is genuine and has not been altered since. A signature that shows up as “unknown” or “unverified” when someone opens the file undercuts that trust, even when the signing was real.

A contract signed with Pactly e-Sign carries a trusted digital seal. The signed PDF is sealed at execution, so a standard PDF reader can confirm on its own that the document is authentic and untouched, with no extra step from you or the recipient.

Open a Pactly-signed contract in Adobe Acrobat or Adobe Reader and the signature panel verifies automatically, showing:

• A green checkmark, Adobe’s signal that the signatures are valid and the document is trusted.
• The signer identity, shown as Pactly Private Limited, the authority that sealed the document.
• Tamper evidence, a statement that the document has not been modified since it was signed. If anyone changes so much as a character after signing, the reader flags it.
• An embedded timestamp, recording when the document was sealed, carried inside the file itself.

Sealing a document does not send it anywhere. Pactly uses only a cryptographic fingerprint of the file, a short unique value computed from its contents, to create the seal. The contract itself never leaves Pactly, so you get third-party-verifiable signatures without handing the document to an outside service.

• E-Signatures overview
• Create and Send a Signature Request
• Complete a Signature Request
• Fully Signed vs Partially Signed