Skip to content

How blockchain-verified e-signatures work Upload. Sign.
Anchor. Verify.

Upload a document, add signers, place fields, and collect signatures. When the last signature lands, LedgerSign hashes the document and anchors the proof on the Hedera public blockchain.

Get Started FreeVerify a document
  1. 01

    Upload your document

    Start with the file you already have. LedgerSign accepts PDF and Word documents, and Word files convert to PDF automatically.

    • PDF and Word (.docx) supported
    • Word documents convert to PDF automatically
    • Encrypted from the moment of upload
    • Or start from a saved template
    Uploading a document to LedgerSign
  2. 02

    Add recipients and set the order

    Add everyone who needs to sign. Choose sequential signing, where each person goes after the previous one, or parallel signing, where everyone signs at once.

    • Sequential or parallel signing order
    • Automatic email invitations
    • Reminders for signers who stall
    • Per-recipient status at a glance
    Adding recipients and setting the signing order
  3. 03

    Place the fields

    Drag signature, initials, text, and date fields exactly where they belong. Fields move freely, including across page boundaries.

    • Signature, initials, text, and date fields
    • Drag fields anywhere, even across pages
    • Assign each field to a specific recipient
    • Save the layout as a template for next time
    Placing signature and text fields on a document
  4. 04

    Recipients sign from their inbox

    Each signer gets a unique, access-controlled link by email. Before anything is signed, LedgerSign captures ESIGN and UETA consent to use electronic records.

    • No signer account required
    • Typed or drawn signatures
    • ESIGN and UETA consent captured before signing
    • Works on any device with a browser
    A live signing session on a phone
  5. 05

    Everyone gets the proof

    When the last signature lands, every party receives the signed PDF and a Certificate of Completion. The document is hashed with SHA-256 and anchored on Hedera, so anyone can verify it independently.

    • Signed PDF delivered to every party
    • Certificate of Completion from the audit record
    • SHA-256 hash anchored on Hedera
    • Independent verification, no LedgerSign account needed
    A completed document with its verification certificate

Step five is the part no ordinary e-signature tool does. The anchor is a message on the Hedera Consensus Service carrying the document's SHA-256 hash, and the transaction is public on HashScan. Read how hashing and anchoring work or follow the step-by-step verification guide.

One dashboard for every agreement

Every document lives in one place with its current status: draft, sent, viewed, signed, completed. Filter by recipient, resend a stalled invitation, void a document that should not proceed, or open the audit trail. Teams that automate this use the REST API and webhooks instead; every feature is listed on the features page.

statuscompleted ✓
LedgerSign dashboard listing documents and their statuses
The Outcome

What do you get when signing completes?

Every completed signing produces three artifacts.

The signed PDF

The final document with every signature in place, delivered to all parties automatically.

Certificate of Completion

A certificate generated from the audit record: who signed, when, and from where, plus the document hash and the Hedera transaction id.

The LedgerSign Certificate of Completion
What the audit trail records

The on-chain anchor

A SHA-256 fingerprint of the document, written to the Hedera Consensus Service with a transaction id anyone can look up on HashScan.

Verify a document now

Run the five steps
on your own document

The free plan includes five documents. Send one, complete it, and open the anchor on HashScan yourself.

Get Started FreeCompare plans

No credit card required · Free plan includes 5 documents to try · Cancel anytime

Page updated September 13, 2026