This guide provides technical instructions for viewing and verifying the integrity of a finalized, cryptographically signed PDF document.
Prerequisites
- Successful completion of a document transaction.
- Access to the IUSign portal or the "Execution Confirmed" email notification.
- A PDF viewer with support for ISO 32000-1 digital signature standards.
Strategic Overview
The finalized Signed PDF is the authoritative legal record of a digital transaction. Unlike a standard PDF, an IUSign-executed document contains multiple layers of cryptographic metadata, including embedded digital signatures, an IUSign corporate seal, and a unique document hash. Proper visualization and verification are essential to ensure that the document has not been tampered with post-execution and that all signatures are legally valid.
Implementation Sequence
1. Accessing the Finalized Asset
Authorized parties can access the signed document through three primary channels:
- The Completion Notification: All recipients receive an automated email containing a secure link to download the finalized assets.
- The IUSign Repository: Authenticated users can locate the document in the Completed folder of their Document List.
- The Recipient Portal: Immediately after selecting "Finish," the recipient is presented with a direct download option.
2. High-Fidelity Visualization
When viewing the signed PDF, the following elements should be visible:
- Signature Burn-ins: High-resolution representations of the signatures and initials placed by recipients.
- Data Inputs: All text fields, checkboxes, and dates filled by the participants.
- IUSign Security Footer: A unique Envelope ID and tracking number typically appended to the bottom of each page for forensic cross-referencing.
3. Verification of the Digital Seal
Open the document in a standard validator (e.g., Adobe Acrobat) to verify the cryptographic seal:
- Signature Panel: Locate the "Signatures" or "Digital Seal" panel.
- Integrity Status: The validator should indicate: "Signed and all signatures are valid. The document has not been modified since this signature was applied."
- Certificate Authority: Verify that the seal was issued by the IUSign Root CA.
Forensic Metadata Analysis
| Component | Forensic Purpose |
|---|---|
| SHA-256 Hash | A unique "digital fingerprint" that changes if even one pixel of the document is altered. |
| PAdES Compatibility | Ensures the digital signature is "embedded" within the PDF itself for offline verification. |
| Envelope ID | The unique primary key used to retrieve the associated Audit Trail. |
Strategic Considerations for Document Integrity
- Long-Term Archival: IUSign documents are finalized using PDF/A-compliant standards, ensuring they remain readable and verifiable for decades.
- Non-Repudiation: The combination of the visual signature, the digital seal, and the associated audit trail provides an irrefutable proof of execution.
- Offline Verification: Because IUSign utilizes standard PKI technology, the document can be verified even without access to the IUSign servers, using any standard PDF validation tool.
Diagnostic and Resolution Protocols
| System Exception | Probable Cause | Resolution Protocol |
|---|---|---|
| Signature says "Invalid" | Post-execution edit | Ensure you haven't "Saved As" the document in an editor that breaks the cryptographic seal. Re-download the original. |
| Missing signature images | Rendering delay | In rare cases of high server load, allow 60 seconds for the asset synthesis to complete. |
| Cannot open file | Corrupted download | Verify your internet connection and re-attempt the download from the IUSign portal. |