When the last signer completes, IUSign generates a Certificate of Completion — a standalone PDF that consolidates every piece of evidence proving the document's validity.
Upon the final signature, the system compiles all envelope metadata, signer records, and audit events.
A Certificate of Completion PDF is generated with the organization's branding (if white-labeled).
The certificate includes: envelope ID, document name, all signer details, consent timestamps, IP addresses, SHA-256 hashes, and compliance declarations.
An evidence package JSON is also generated — machine-readable version of the same data.
Both files are attached to the completion email sent to all parties.
Certificate generated via reportlab (Python PDF library) with configurable branding.
Includes certificate_hash = SHA-256(all_audit_events concatenated) for integrity verification.
Compliance markers reference specific statutes: ESIGN Act (15 U.S.C. §7001), UETA (§7-§8), eIDAS (EU 910/2014 Art. 25).
Evidence package JSON schema: { envelope, document, signers[], audit_trail[], hash_chain, compliance, generated_at }.
Envelope ID and name. Document name and SHA-256 hash. For each signer: name, email, consent timestamp, IP address, user agent, device fingerprint, signature image hash, signing timestamp. Full audit trail with event types and timestamps. SHA-256 hash chain summary. Compliance declarations.
For technical users who need programmatic access to the audit data, the evidence package JSON contains the same information as the certificate in a machine-readable format.
Create your free account and send your first document in under 3 minutes.
Get Started Free