DocuSeal: What It Powers Behind the Scenes

Loyva's entire eSignature stack: fields, signing UI, completion webhooks, audit trails - runs on DocuSeal. You won't interact with DocuSeal directly, but understanding what it does helps when troubleshooting.

What DocuSeal handles

  • Field placement (signature, initial, date, text, checkbox, radio).

  • Sequential and parallel signer routing.

  • The signing UI shown to recipients at /sign/s/<slug>.

  • Per-field audit (IP, timestamp, geolocation if allowed).

  • Completion webhooks that fire back into Loyva.

What Loyva wraps around it

  • Branded email delivery via Resend (not DocuSeal's default mailer).

  • eSign consent: mandatory and shown before the DocuSeal widget loads.

  • Internal routing: /sign/s/<slug> enforces consent before redirecting to DocuSeal.

  • Vaulting the completed PDF as an Authoritative Copy on completion.

  • CC delivery of completed PDFs through Resend.

  • Notification fan-out to org admins on every signing event.

API key dependency

Note: Live signer status and unmasked field prefill both require a valid DocuSeal API key. Without it, the app falls back to local cache and masks sensitive fields.

Supported formats

DocuSeal accepts PDF, PNG, and JPG only. Word documents (.doc, .docx) must be exported to PDF before upload.