Every SaaS product asks users to accept something. Terms of service and privacy policies usually get a checkbox at signup. Order forms, data processing agreements and enterprise contracts usually get a signed PDF. Teams often pick one of the two by habit, and sometimes the habit is wrong in both directions: a signing flow for a document nobody will ever dispute, or a checkbox for a contract that someone will.
This post explains what each approach proves and when each one tends to hold up. It is a technical explainer, not legal advice. For any document with real stakes, ask your legal counsel.
Both are electronic signatures
Under the US ESIGN Act, an electronic signature is “an electronic sound, symbol, or process, attached to or logically associated with a contract or other record and executed or adopted by a person with the intent to sign the record.” A click on “I agree” can meet that definition. So can a typed or drawn signature in a signing ceremony.
The EU’s eIDAS regulation takes a similar view at its simple level: any electronic data a person uses to sign counts, and a court can’t reject a signature only because it is electronic.
So the question is rarely whether a click is legally an electronic signature. The question is whether you can prove, months or years later, that a specific person agreed to a specific version of the terms.
What clickwrap proves
A clickwrap agreement presents terms and asks the user to take an affirmative action, such as ticking a box or pressing a button, before they can continue. US courts generally enforce clickwrap when the user had reasonable notice of the terms and clearly showed assent. Designs that skip the affirmative action, where terms sit behind a link in the footer and use of the site is supposed to imply agreement, fare much worse.
When clickwrap fails, it usually fails on evidence. To defend it, you need to show:
- which account clicked, and how you know the person behind the account,
- which version of the terms was on screen at that moment,
- that the terms were visible or clearly linked next to the button,
- when the click happened.
That evidence lives in your own database and logs. If you store the version and timestamp for each acceptance, and you can reproduce the screen as it looked, clickwrap is strong. If the terms page has been edited in place since then, or the acceptance record is a single boolean column, it gets weak quickly.
What an e-signature adds
A signing flow produces a self-contained record. With SignatureAPI, each recipient goes through a ceremony: they consent to using electronic signatures, review the exact documents, fill in any fields and sign. When everyone has finished, SignatureAPI generates a deliverable, a PDF with the signed documents and an audit log that records every action in the signing process.
Three properties matter in a dispute:
- The document is fixed. The signer signs one specific file, and the deliverable contains that file.
- The evidence travels with the document. The audit log is part of the PDF, not a row in a database that might be migrated or deleted.
- Tampering is detectable. Every deliverable is sealed with a cryptographic signature, and anyone can verify that it has not changed since it was issued.
You can also choose how signers identify themselves: an email link, a 9-digit email code, your own authentication recorded in the audit log, or a combination.
Choosing between them
A few questions sort most documents.
Is the document the same for everyone? Terms of service, privacy policies and acceptable use policies are identical for every user and change on your schedule. Clickwrap fits them, as long as you version the text and record each acceptance.
Is the document negotiated or personalized? Order forms with custom pricing, employment offers, leases and statements of work differ per signer. A signed document records what this person agreed to, not what the template said at the time.
Will a specific individual’s identity matter? Clickwrap binds an account. If you might need to show that a named officer of a company signed, rather than whoever was logged in, a signing ceremony with authentication is the better record.
Does someone else require a signature? A customer’s procurement, finance or HR team may expect a signed PDF and a certificate of completion. Some laws or counterparties require a specific signature level, such as a qualified electronic signature in parts of the EU.
Is the document excluded from e-signature laws? In the US, ESIGN does not apply to wills, codicils and testamentary trusts, family law matters and court documents, among other exceptions. Neither clickwrap nor a standard e-signature changes that.
Using both in one product
A product can use both. One sensible split is clickwrap for platform terms at signup, then a signing flow for anything with a counterparty, a price or a person’s name on it.
If your users are already logged in, the signing flow does not need to leave your product. You can embed the SignatureAPI ceremony in an iframe or a mobile WebView, authenticate the user with your own login, and record that authentication in the audit log. The user experience stays close to a checkbox, and the record is a sealed document.
To see what that record looks like, send a test envelope with a free test key and open the deliverable. The embedded signing guide shows how to keep the flow inside your app.