E-signature guides and compliance checklists for developers
You're building your own signing flow or clickwrap with an AI coding tool. These articles cover the parts a prompt leaves out: what the screen has to say, what to store when someone agrees, and what the ESIGN Act, UETA and eIDAS ask for. Each one comes with code or a checklist you can paste into your project.
Three articles on building e-signature and clickwrap flows
Written for the person who is prompting the signing page into existence. Each article answers one question in full, with working code.
Pre-checked boxes, notices that name nothing, links to terms that change, and four more. Each one as code, with the fix.
- Each mistake as the code a tool writes, next to the corrected version.
- The statute or court decision behind every rule.
- One command that finds the mistakes on your own page.
The Postgres schema, the insert and the query for who has not accepted the current version. Then what that table cannot show anyone else.
- Two tables and a view, for Postgres and Supabase.
- The insert, and the query for who still has to accept.
- Four things your own table cannot show, and the two columns that fix them.
The three patterns with a code example of each, how courts have treated them, and which one to build.
- Browsewrap, sign-in wrap and clickwrap as markup.
- How U.S. courts have treated each one, with the decisions.
- A clickwrap to paste in, with the server and browser code.
Two compliance checklists, one for each side of the Atlantic
Every requirement as a row: the source, linked, then the implementation task in plain engineering terms, then the rule or SDK step that covers it. Copy either one as Markdown into an issue or your AI coding tool.
Each U.S. requirement with its source, the implementation task, and the rule or SDK step that covers it.
- Intent, consent, association, attribution, retention and copies.
- The consumer e-consent steps, and when they apply.
- The notice and assent rules from the leading U.S. decisions.
eIDAS checklist for developers
Simple electronic signatures for EU signers, with the UK and Switzerland where their rule packs differ.
- The explicit act, the frozen document and the signature level.
- National form rules, the EU online-contract rules and GDPR.
- Where the UK and Swiss rule packs differ.
The rule packs behind them: U.S. Federal and seven states, the EU, the UK and Switzerland, and the document types each pack blocks.
Where to start, by what you are building
Three common builds, and the order to read in. Every screen is yours to build in each of them.
A terms checkbox or a clickwrap
Read the three patterns and build clickwrap. Then set up the table that stores each acceptance, and the query that finds who has to accept again after you change the terms.
An NDA, a contract or a consent form
A document someone signs takes a typed name, a notice that says they are signing electronically, and a record tied to the exact version. Start with what tools get wrong, then check your flow against the law for your signers.
Your own DocuSign-style app
Upload, field placement, signer links, reminders and the sender dashboard are yours to build with your AI tool. Esign Comply supplies the rules for each signing screen and keeps one sealed record per signer.
More to read on building your own signing flow
The reasoning, the build guides and the comparisons, one link each.
- Why a third party keeps the record The argument for vibe coding every screen and handing off two parts: the rules and the record.
- Build your own e-signature app Your own DocuSign-style app or clickwrap, with a copy-paste prompt for each AI coding tool.
- Stack guides Clickwrap in Next.js and Supabase, Rails, Django, Laravel and React Native, step by step.
- Use cases with live demos NDAs, contractor agreements, consent forms, order forms and terms updates, each with the prompt and a demo that runs on the page.
- DocuSign alternative for developers For when you want the signing flow inside your own interface, built with your own AI tool.
- E-signature APIs compared Send, embed or build your own: the three models an e-signature API follows, and which products use which.
Questions about building your own e-signature flow
Can I build my own e-signature flow?
Yes. Electronic signatures are recognized under the U.S. ESIGN Act and state UETA laws, and neither law requires a particular vendor or technology. You build the signing screen in your own app. What it needs is notice of the terms, an unmistakable act of assent, and a record of both.
The ESIGN Act and UETA checklistWhere do I start if I only need a terms of service checkbox?
Start with the clickwrap article for the pattern to build: an unchecked box whose label names the documents and the button. Then read the storage article for the Postgres schema and the query that finds users who have not accepted the current version. Both come with code you can paste.
Clickwrap vs browsewrap vs sign-in wrapWhich laws apply to a signing flow I build myself?
For U.S. signers: the ESIGN Act, state UETA laws and the court decisions on online assent. For signers in the EU: eIDAS, the EU consumer and e-commerce rules and GDPR, with separate rules in the UK and Switzerland. The two checklists turn each requirement into an implementation task with its source.
The eIDAS checklistDo these articles work without Esign Comply?
Yes. The schema, the clickwrap markup and the checklists are complete as they stand. Esign Comply adds the two parts you cannot build inside your own stack: the rules as one prompt for your AI coding tool, and an independent, tamper-evident record of every signature.
Why a third party keeps the recordRead the rules once. Then let your AI tool build to them.
Free plan: 10 live signatures a month and a full test mode. No card required.