Mojo Verify shieldMojo Verify

Identity-bound document signing

DocuSign,
done right.

Don’t just collect a signature. Verify the signer’s government ID, prove they are live, match them to that identity, and preserve the complete trail around the signed document.

Identity before signature

Know who is signing before they sign.

A signing request can require liveness before the customer reaches the signature step. Combined with Mojo Verify identity proofing, the workflow connects the document to a verified person—not merely to whoever opened a link.

  • Capture a high-quality government identity document
  • Prove the signer is physically present and live
  • Match the live face to the portrait on the ID
  • Sign only after the required identity gate passes
IDENTITY-BOUND AGREEMENTAlex MorganSigned
IDENTITY VERIFIEDLive face matched
  1. Government ID verified
  2. Liveness passed
  3. Face matched to ID
  4. Signature captured
  5. Signed PDF sealed

01 / Identity trail

A proper record of who did what, and when.

Meaningful signing activity becomes an append-only event trail instead of a single completed timestamp.

CREATED

Request context

Customer, document template and version, expiration, notification method, and the required liveness gate.

VIEWED

Access context

When the customer opened the request, including IP address, geolocation, user agent, and event metadata.

VERIFIED

Liveness proof

Liveness started, passed, or failed before the signing process is allowed to continue.

SIGNING

Signer actions

Signing started, signature captured, and signature hash metadata recorded in sequence.

SEALED

Document integrity

Signed PDF generation, encrypted vault storage, and SHA-256 integrity metadata.

SHARED

Controlled access

Downloads and secure share activity, including revocation, expiry, password, and view-limit controls.

02 / Protected artifact

The proof does not end when the pen lifts.

The completed PDF is encrypted at rest. Downloads are watermarked and recorded. Secure links can be password-protected, time-limited, view-limited, and revoked.

Build a verified signing flow ↗
Encrypted

Signed PDFs stored in FileVault.

Integrity

SHA-256 hash stored with the artifact.

Watermarked

Traceable download label and timestamp.

Controlled

Expiring and revocable secure shares.

03 / API

Make identity a signing requirement.

Create the request with a known customer and set the liveness gate. The response returns a secure signing link and request record.

Read the signing quickstart
verified-signing.json
POST /api/docsign/request/create
Authorization: apikey mvp-••••••••

{
  "customer_id": 42,
  "template_id": 10,
  "require_liveness": true,
  "expires_hours": 168
}
identity_required → signing → completedappend-only events

Identity before agreement

A signature tied to a real person.

Give high-value agreements the identity proof and evidence trail they deserve.

Talk to Mojo Verify ↗

DocuSign is a trademark of DocuSign, Inc. Mojo Verify is an independent product and is not affiliated with DocuSign.