Skip to content

Digital Identity & Security

WPsigner goes beyond simple e-signatures by supporting digital identity verification, cryptographic timestamping, and tamper-proof audit trails. These features strengthen the legal validity of your signed documents and help you meet compliance requirements across jurisdictions.


GuideDescription
Digital ID (.p12)Import or generate PKI certificates to embed a digital identity into every signed PDF
Timestamping (TSA)Add RFC 3161 timestamps from a trusted authority to prove exactly when a document was signed
Audit TrailsAutomatic logging of every action — IP addresses, device info, timestamps, and geolocation

Electronic signatures are legally valid in most jurisdictions, but the strength of that validity depends on the evidence you can provide. WPsigner’s digital identity features create multiple layers of proof:

LayerWhat It ProvesTechnology
Digital CertificateWho signed (identity bound to a certificate)X.509 PKI, .p12/.pfx
TimestampWhen they signed (independently verified time)RFC 3161 TSA
Audit TrailWhat happened (complete event history)SHA-256 hashed log entries
Document HashThe document wasn’t altered after signingSHA-256 integrity check

Together, these layers satisfy the requirements of ESIGN, UETA, eIDAS (SES/AES), and other electronic signature regulations.


Signer Opens Document
Identity Verified (Digital Certificate applied)
Signature Captured (drawn, typed, or uploaded)
Timestamp Requested (TSA server certifies the time)
Audit Trail Updated (action logged with IP, device, hash)
PDF Sealed (certificate + timestamp embedded in the file)

The final PDF contains the digital certificate, the timestamp token, and a reference to the full audit trail — all embedded directly in the file for independent verification.


  • Start with Digital ID if you want to embed cryptographic identity into your signed PDFs. You can use a self-generated certificate or import one from a Certificate Authority.
  • Add Timestamping to prove the exact signing time through an independent third party. WPsigner supports any RFC 3161-compliant TSA.
  • Review Audit Trails to understand what WPsigner logs automatically and how to access the trail for compliance or disputes.