Beyond a basic e-signature: Advanced Electronic Signature via WhatsApp.
Paid accounts can require a WhatsApp-verified, PIN-protected signing link — designed to meet the EU eIDAS criteria for an Advanced Electronic Signature (AES).
The problem
A simple electronic signature (SES) — the industry default, including Docracy's free plan — proves what was signed and when, but not who physically signed. Anyone with the link can sign as the named party.
The Docracy way
Docracy's WhatsApp-verified signing (paid accounts) binds the link to a specific phone number, requires a PIN unique to that signer, and records Meta's delivery/read receipts — evidence intended to meet the EU eIDAS AES bar: unique linkage, signatory identification, sole control, and tamper-evidence.
Features
Uniquely linked & identifying
The signing link only reaches the phone number tied to that signer's own WhatsApp account.
Sole control via a mandatory PIN
A PIN set by the preparer is required before signing — phone possession alone isn't enough.
Tamper-evident by default
Every document already carries a SHA-256 hash of the signed PDF at each step, independent of channel.
Delivery & read evidence
Meta's delivery/read receipts are stamped into the audit trail.
10 included per month, $0.50 per extra
Bundled into every paid plan — 10 AES-track signers per month, then $0.50 each. Enterprise gets 50/month fair-use.
Use cases
- Higher-stakes contracts that want more than SES
- Cross-border agreements under EU eIDAS
- Compliance-conscious teams not ready for a full QES/QTSP provider
- Client-facing agreements where identity assurance matters
Trust & security (SES vs AES disclosure) · Try WhatsApp signing
Free to start — no account needed to send or sign.
See paid plans