How Signing a Document Works
A four-step walkthrough of sending a document for signature, from upload to a completed document — no account required for signers.
Read more →Resources
Guides from the SequrSign team on how electronic signing actually works, what a tamper-evident audit trail does and does not prove, and what is shipped in the platform today. Written to be read before you commit to a signing tool, not after.
How SequrSign Verifies Document Integrity
How our tamper-evident audit trail works, and an honest look at what it does and doesn't guarantee.
Read more →What SequrSign Does
An overview of what's actually shipped in the platform today: sending for signature, self-signing, identity verification, and the API.
Read more →Where to start
New to electronic signing? How Signing a Document Works first. It follows one signature request from upload to finished file and is the shortest way to understand what your signers will actually see when the email lands. What SequrSign Does is the inventory: the capabilities that are shipped today, and a short and deliberate list of what the platform does not do.
How SequrSign Verifies Document Integrity is the one to read before you sign anything that matters. It covers what a SHA-256 fingerprint proves, what the audit trail records alongside it, and why that is a different guarantee from a certificate-based signature embedded in the PDF itself. If a counterparty has asked whether your signed files will validate in Acrobat, the answer is in there.
Looking for something else?
The FAQ covers supported file formats, multi-recipient signing, credit costs and account questions. The API documentation covers authenticating with an API key and triggering a signature request from your own systems. Plans and credit packs are on the pricing page, and anything not covered by those can go to our contact form.
These guides describe the platform as it works today rather than a roadmap, and new ones go up as features ship.