Signing on Any Device

Signers receive an email with a secure signing link (/sign/:token). Tapping it opens signID’s mobile-first signer app. The flow is:

1. Review the document (scroll, pinch to zoom on mobile)
2. Draw or type a signature when prompted
3. Fill any required fields (date, name, initials, etc.)
4. Tap Finish to complete

No account, no app download. Everything happens in the browser, and the whole flow typically takes under a minute on a well-designed envelope.

The signing link contains an unguessable token that’s unique to each signer on each envelope. Anyone with the link can access the signing surface for that envelope, so treat the link as sensitive.

• Links are tied to a specific signer + envelope combination
• Links expire when the envelope is completed, cancelled, or hits its expiration date
• Opening the link is audit-logged (viewed timestamp + IP)

If you (as the sender) suspect a link was forwarded or compromised, cancel and re-send the envelope.

signID’s biggest design commitment: signers never sign up. Just tap a link and sign. Why this matters:

• Zero friction. Recipients don’t hesitate at an account-creation screen.
• Legal defensibility unaffected. Identity is asserted through the email address the sender used plus the audit trail (IP, timestamps, adopted signature).
• Mobile-first. Signers can complete envelopes without downloading an app.

The signature capture is a touch canvas: signers draw with a finger, stylus, or mouse. The canvas is optimized for mobile, meaning it feels responsive on phones and tablets.

Guidance for signers:

• Draw naturally, don’t over-perfect it. A signature should look like your signature.
• You can clear and redraw as many times as you want before confirming.
• After confirmation, the signature is stored (see “Adopt once, reuse across documents”).

If you prefer typing to drawing (say, on a laptop without a touch screen), switch to the Type tab. Enter your name and pick a signature-style font. signID renders your typed name in the chosen font as your signature.

Legal validity is the same as a drawn signature under the ESIGN Act and eIDAS-aligned regimes: what matters is intent to sign, not the visual style.

Once you’ve adopted a signature (drawn or typed), signID remembers it by email. The next time an envelope arrives for the same email address, your adopted signature is pre-loaded, so you can sign in one tap.

Where the signature is stored:

• Tied to your email address, not to a workspace or a specific sender
• Works across every workspace that ever sends you an envelope
• Can be changed anytime by tapping “Adopt a new signature” in the signing UI

The adopted signature is not shared with the sender or with any third party. It’s used only to render your signature into the documents you sign.

Before signing, signers can download the original unsigned PDF. Look for the download icon in the signing UI’s header. Tapping it triggers a browser download of the exact PDF the sender uploaded.

Why this matters:

• You can review the document in your own PDF reader if you prefer
• You have a copy for your records even if you decline to sign
• The download is audit-logged with a legal-disclosure notice

The original download is available at any time, before signing, after signing, and after the envelope is sealed.

If you don’t want to sign, tap the Decline option in the signing UI. You’ll be asked for an optional reason (visible to the sender in the envelope details).

What happens next:

• The envelope moves to status declined
• Any other signers who haven’t signed yet stop receiving reminders
• The sender is notified via email and (if configured) webhook (envelope.declined)
• Declining is terminal, no signed PDF is produced

Once every required field is filled and you tap Finish, the signing goes into an async pipeline:

1. The API returns 202 Accepted immediately, so the UI stays responsive.
2. A background worker merges your signature into the PDF using a patch-based approach.
3. For multi-signer envelopes, this happens for each signer as they finish. The final sealed PDF is assembled once after the last signer completes.
4. The SHA-256 hash of the sealed PDF is computed and recorded.

Signers see a completion screen immediately: success seal, sealed-document summary (title, signers, sealed timestamp, document SHA-256, verify link, copyable receipt ID), and a download panel for the sealed PDF (which becomes active once the async work completes).

On multi-signer envelopes, after you finish, you see a waiting screen showing:

• A live roster of all signers on the envelope
• Who has signed, who hasn’t
• A progress ring showing overall completion

You can leave this screen and come back anytime, the status updates in real time. Once the last signer completes, the sealed PDF is generated (usually within seconds) and everyone receives the sealed-receipt email with the finalized document attached and a verify link.