One signing engine, the paperwork you already send
There is no industry edition of Signattio. Every kind of paperwork below goes through the same five stages — send, identify, sign, seal, verify — and comes back with the same evidence: a PAdES-sealed PDF, an RFC 3161 timestamp and a hash-chained audit trail. What changes per use case is who signs, how they verify, and which proof you need to keep.
What every envelope proves
Each stage leaves evidence you can point at — in the audit trail and in the sealed PDF. The stages never change; the paperwork does.
The document goes out as an envelope, with signers in a defined order.
Each signer verifies with a one-time code; IP and user agent are captured.
Signers draw or type in a browser signing ceremony.
A PAdES baseline long-term seal per ETSI EN 319 142-1, RFC 3161-timestamped.
Anyone with the document re-checks the evidence publicly — no account.
The hash-chained audit trail stays verifiable for the years files are kept.
Employment contracts, onboarding packs and policy updates for small teams.
Send the employment contract as an envelope; each signer verifies with a one-time code tied to their own email or phone and signs in the browser. The sealed PDF that comes back carries the signer's identity evidence and a hash-chained audit trail, so the employee file holds the proof, not just the signature image.
The same envelope covers onboarding paperwork and policy acknowledgements. Because the seal is PAdES baseline long-term, the evidence stays verifiable for the years a labour file is normally kept.
Agency mandates, listing authorisations and tenant paperwork.
In property paperwork, when each party signed is part of the record. The RFC 3161 timestamp is applied inside the signing ceremony, so the sealed PDF proves the moment of signing, not just the fact of it.
The audit chain makes later alteration detectable: every row of the audit trail is hashed into the chain, and the chain can be re-checked by anyone with the evidence pack — no account, no tooling.
Quotes, purchase authorisations, NDAs and order sign-off.
Signing links are single-use and expire on a short timer, so an unsigned draft does not keep circulating by email after the deal has moved on. Reissue takes seconds; the old link simply stops working.
Where several people must approve, the envelope can be routed so parties sign in parallel — both free to sign at any time — or in a fixed order when the flow demands it.
Business contracts signed without printing, scanning or posting.
Under eIDAS Article 25, an electronic signature cannot be denied legal effect solely because it is electronic or not qualified. The guides below set out what that means in practice — and where a wet-ink signature still earns its keep.
The flow is the same five stages as every envelope here: send, identify, sign, seal, verify. The evidence pack is what turns 'we agreed by email' into a record that survives scrutiny.
Any PDF that needs a signature and a verifiable record of it.
Upload the final PDF, add signers, send. What returns is a sealed document whose signature conforms to ETSI EN 319 142-1 — the PAdES profile — with the audit trail attached.
Before relying on a signed PDF — yours or one you were sent — check it: the verifier runs account-free, and the guide walks through what a validator actually inspects.
Sending by hand or by API
Every flow above works from the dashboard and from the REST API — the API is the same engine the dashboard uses. If the paperwork originates in your own system, start with the API documentation; if you send a handful of envelopes a week, the free trial needs no sales call.
Ready when your paperwork is
Ten envelopes free. Setup in 30 seconds. No sales call.