E-Signature 2.0
Prepare a document, route it to multiple parties for legally binding electronic signatures, capture a draw or type signature, and receive a tamper-evident sealed PDF with a full IP + timestamp audit certificate.
Staff create an e-signature request, upload a PDF or Word document (which is automatically converted to a signed-ready PDF), add one or more signing parties in order, and send. Each party receives a unique signing link by email. When every party has signed, the platform seals the document with a SHA-256 hash and generates a separate audit certificate PDF recording every event — IP address, timestamp, user-agent, and signature image — from creation through sealing.
What you can do
Upload PDF or Word
Drag a .pdf, .doc, or .docx file onto the request. Word files are automatically converted to PDF before signing begins.
Add multiple signing parties
Add as many parties as needed — each with a name, email, and signing order. Every party signs in sequence, and each gets their own tamper-evident signing link emailed to them.
Draw signature on canvas
The public signing page presents a canvas area where signers draw their signature with a mouse or finger on any device. The captured PNG is embedded in the final sealed PDF.
Type signature in cursive
Signers who prefer to type their name instead of drawing can switch to Type mode — the name is rendered in a script font and embedded as their signature.
Full IP + timestamp audit trail
Every event — request created, sent, viewed, signed, declined, sealed — is recorded with actor, IP address, and user-agent. The detail page shows a vertical timeline; the audit PDF captures the complete log.
Sealed PDF + audit certificate
Once all parties sign, the platform seals the document and generates a separate audit certificate PDF. Both are available for download from the request detail page.
A typical workflow
- Create the request — enter a title, optional body text, signing language (EN or ES), module tag, and add at least one signing party (name + email). The order you add parties is the signing order.
- Upload the document — from the request card in the list or from the detail page, upload a PDF or Word document. Word files are auto-converted to PDF.
- Send for signing — click "Send for signing." Each party receives a personalised email with their unique signing link. The request moves to sent status.
- Parties sign (or decline) — each party opens their link, reads the embedded document, and either draws or types their signature. They enter their full name, check the consent box, and submit. They can also decline with an optional reason.
- Review the audit trail — the detail page shows a live vertical timeline of every event: created, sent, viewed, signed/declined, sealed — each with actor, IP address, and user-agent.
- Download sealed PDF + audit certificate — once all parties have signed the document is automatically sealed. Download both PDFs from the detail page.
Signing modes in detail
The signing page shows a bordered canvas panel. The signer uses a mouse on desktop or a finger on mobile (touch events are fully supported). A Clear button lets them redo the signature. On submit the canvas is captured as a PNG data URL and sent to the backend, which embeds it into the sealed PDF as a bitmap image.
The signer types their name into an input rendered in an italic serif font. A live preview shows how the typed name will look on the document. This is the preferred mode for accessibility (screen readers, keyboard-only users). The typed name is embedded as a styled text element in the sealed PDF.
The audit trail — a closer look
- created — staff member who created the request, timestamp
- sent — timestamp, actor (backend system)
- viewed — party name, IP address, user-agent, timestamp (recorded on first document open)
- signed — party name, IP address, user-agent, signature method (draw / type), signed name, timestamp
- declined — party name, IP address, decline reason (if provided), timestamp
- sealed — SHA-256 document hash, timestamp
All of the above is also embedded verbatim in the downloadable audit certificate PDF.
Bilingual support
The public signing page is fully bilingual. When staff create a request they choose English or Spanish as the signing language — the signing page is then served in that language for all parties on the request. Staff-side pages (the dashboard list and detail page) remain in English to match the rest of the staff dashboard.
A closer look
The dashboard list at
/dashboard/esign shows all requests with status pills (draft / sent / signed / declined / sealed). A request card in draft state shows an "Upload document" control and a "Send for signing" button (disabled until a document is attached). Once sealed, both the sealed PDF and audit certificate are available for download directly from the list card and from the detail page.Staff:
/dashboard/esign (list + create), /dashboard/esign/<id> (detail, upload, audit timeline). Signers: /sign/<token> — a public page, no login required; the token in the URL is the signer's credential.Works with
Documents for general document storage · Partner API for programmatic e-signature creation and webhook notifications on completion.
Seguridad y privacidad / Security & privacy
Cada enlace de firma es de un solo uso y está vinculado a una única parte. Una vez firmado o rechazado, el enlace queda inactivo. El documento fuente y el PDF sellado se almacenan en el servidor y no se exponen públicamente. El hash SHA-256 del PDF sellado permite verificar la integridad del documento en cualquier momento.
Each signing link is single-use and tied to one party. Once signed or declined the link is inactive. The source document and sealed PDF are stored on the server and are not publicly accessible. The SHA-256 hash of the sealed PDF enables integrity verification at any time.