Your first signature

This guide walks you through sending your first document for signature using the Chaindoc web app. The whole thing takes about five minutes.

Looking for the API version? The quick start guide covers the same flow in code. This page is specifically the click-through walkthrough. Learn more in the ESIGN Act of 2000.

What you'll need

• A Chaindoc account. sign up if you don't have one yet.
• A PDF to sign. PAdES signatures are embedded into PDF files, so other formats (Word, Excel, images) can't be signed directly. convert to PDF first using Office's built-in "Export as PDF" or any PDF tool.
• The email address of everyone who needs to sign.

Upload the document

1. 1
   Go to DocumentsClick Documents in the sidebar.
2. 2
   Click New DocumentThe button is in the top-right of the documents list. A four-step wizard opens (Upload → Details → Access → Review).
3. 3
   Upload your filePick a file from disk or drag it into the upload zone. The upload API accepts files up to 250 MB, but compressed PDFs render faster for signers.
4. 4
   Fill in the detailsGive the document a clear name (e.g. "Q2 2026 Consulting Agreement. Acme"), an optional description, and hashtags for filtering later.
5. 5
   Set the access typeThe Access step defaults to Private (only you). If colleagues need to see it, switch to Public (anyone in your workspace) or Restricted (specific emails or team roles). You can always change this later.
6. 6
   Review and createThe final step is a summary. confirm, and the document lands in your Documents list.

Create the signature request

Open the document you just uploaded and start a signature request from the document page. The request builder walks through recipients, deadline, and message.

1. 1
   Add recipientsType in the email addresses of every signer. All signers on a Chaindoc request are invited in parallel. there's no sequential or conditional order.
2. 2
   Set a deadlinePick a date (and optionally a time). 7–14 days is typical for most contracts. Chaindoc sends automatic reminders at fixed intervals as the deadline approaches. you don't configure those.
3. 3
   Write a messageThe text goes into the signing email. A single sentence of context ("Please review and sign our Q2 consulting agreement") massively improves response rates.
4. 4
   Place signature fields (optional)If you need signatures at specific coordinates on specific pages (for example the last page of a multi-page contract) you can place them in the visual editor before sending. Otherwise Chaindoc uses a default signing page.
5. 5
   Turn on KYC if you need itFor high-value agreements where you need verified identity, tick the Require KYC checkbox. Signers will go through Sumsub's KYC flow inside the signing UI before they can sign.

Review and send

Double-check the recipient emails before hitting Send. Typos in email addresses are the single most common reason a signature request "doesn't arrive". Once you send, each recipient gets an email with a signing link. no Chaindoc account required on their side.

What your signers see

It helps to know the other side of the flow. For an external signer using the email link:

1. 1
   Email with signing linkThey get a message with a "Review and Sign" button. Opening it takes them into the Chaindoc signing UI in their browser.
2. 2
   Email OTPChaindoc sends a one-time code to the signer's email address. They paste the code to prove they own the address. If KYC is enabled, they complete identity verification in the same flow.
3. 3
   Document reviewThe PDF opens in an embedded viewer. They can scroll, zoom, and read before committing.
4. 4
   Apply the signatureThree options: draw on a canvas, upload an image of their handwritten signature, or reuse a saved signature from a previous Chaindoc session.
5. 5
   DoneChaindoc generates a PAdES-signed PDF with the signer's ECDSA certificate embedded and emails them a copy of the signed document.

For more on what PAdES gives you and how the two integrity layers (PDF signature + blockchain anchor) fit together, see the signatures page.

Track progress

Go to the document or signature request page and you'll see each signer's status: pending, signed, or (after the deadline) expired. The activity log shows key events (request sent, signer signed, request completed) with timestamps. There's no per-email "opened" tracking and no IP/device fingerprinting shown in the UI.

If someone's dragging their feet, the fastest move is a human nudge (Slack or direct email). Automatic reminders already go out at 7, 3, and 1 days before the deadline.

After everyone signs

Once the last signer completes, two things happen:

• The signed PDF is finalised with all PAdES signatures embedded. Every party gets a copy by email.
• A background job hashes the signed PDF and anchors the hash to the SKALE Calypso blockchain. The transactionHash and chainId appear on the document's verification record.

You can re-download the signed PDF from the document page at any time, and anyone can verify the blockchain record later at chaindoc.io/pdf-verify. just upload the PDF and Chaindoc re-hashes it and compares against the on-chain record.

Common questions

What if a signer doesn't get the email?

Ask them to check spam/junk. corporate filters sometimes block signing emails. If the email address is wrong, cancel the request and start a new one with the correct address. Allowlisting *@chaindoc.io with the recipient's IT team fixes the common corporate-filter case.

Can I cancel a request I already sent?

Yes. open the signature request and use the Cancel action. Any signers who already signed keep their signatures (they're part of a partial signing state); pending signers simply can't sign the cancelled request anymore.

What happens when the deadline passes?

The request moves to an expired state and can't be signed. Create a new request on the same document if you still need the signatures. the original request stays in history for reference.

Are Chaindoc signatures legally binding?

Yes. signatures are PAdES-BES (Advanced Electronic Signatures under Article 26 of eIDAS), which also meets the ESIGN Act and UETA in the US. The blockchain anchor adds independent integrity evidence on top.

What to do next

• Signatures. how PAdES + blockchain give you two integrity layers
• Documents. versioning, access control, and the meta/hashtag system
• Teams. invite colleagues and use role-based document access
• API integration. automate the same flow from your backend
• Quick start. the code path from upload to signed document