Sign the data, not the PDF.
A stapled e-signature locks a picture of a page. onSign signs the deal itself: the exact order, the terms it pins, and every choice you made. The thing you sign and the thing that governs the deal are the same thing. The result is a verifiable record anyone can check, for free.
There is no document to drift
Most e-signature tools take a PDF and add a picture of your signature to the last page. What gets signed is a rendering. If someone later edits the terms, reflows the layout, or swaps a clause, the visible signature still sits there looking valid. The signature and the content it was meant to lock are only loosely tied.
onSign works the other way around. It signs the order as data: the pinned terms, the modules it incorporates, and every choice you made. There is no separate file that can wander away from what you agreed. Bind it once, and what governs the deal cannot quietly change underneath you.
- Captures exactly what was agreed: which terms, which version, which choices, signed by whom.
- Any later change to that agreed content is detectable. You do not have to trust a vendor's word.
- Anyone with the record can confirm it later, for free, without an account and without calling us.
Bound to the exact terms, by content hash
When you sign, onSign binds the precise terms in front of you. Each version is pinned by a content hash, so there is no ambiguity about what was agreed. Not "the latest template", not "whatever the file said". This version, these choices, this counterparty.
A human clicks to sign
When both sides are ready to commit, you sign the order. One click executes the exact deal in front of you and produces a single record covering that order. Reading, verifying, and assembling stay free. Signing is the moment a deal goes live.
An agent accepts, within bounds
An agent can accept an order on your behalf, but only under a scoped mandate that you, the principal, signed. The agent cannot author its own authority. Inside the envelope you set it moves fast. Outside it, nothing happens.
How mandates workHow this differs from a signed PDF
Because the signed thing is the data, an onSign record plugs straight into the rest of onTerms. See how anyone can confirm an order.
Match the assurance to the deal
A signature is only as good as your confidence in who actually signed. onSign offers three identity tiers. The record states which tier was used, so a counterparty can see the level of identity assurance at a glance.
Standard
The signer is authenticated through their onTerms sign-in. The right level for everyday B2B orders, routine renewals, and deals where the parties already know each other.
KYC
The signer's real-world identity is verified before they sign. Use it for higher-value orders, a brand-new counterparty, or when your own policy requires documented identity.
Qualified (QES)
The highest assurance tier, carrying the strongest legal recognition under frameworks such as the EU's eIDAS. Reserve it for deals where a specific law or counterparty demands the top tier.
For agent-signed orders, the minimum tier is part of the signing controls in the mandate you signed, so an agent cannot complete a deal at a weaker tier than you allow.
Every signed order earns the Verified badge
An onSign record is content-addressed, so anyone can confirm it without an account, without calling us, and without us staying online. That same check powers the onTerms Verified badge: proof that an order matches the standard and has not changed since it was signed.
See the Verified badgeFree to check
Verification costs nothing and needs no account.
Independent
The check holds whether or not onTerms is online.
Tamper-evident
Any change to the signed order is detectable.
Sign the deal, not a picture of it.
A human clicks, or an agent accepts under a mandate you control. Either way you get one verifiable record that anyone can check for free.