Clickwrap guides for your stack
Pick your stack and copy the files: a signup clickwrap for Next.js and Supabase, Rails, Django, Laravel and React Native, with the working code first and the explanation second.
Free plan: 10 live signatures a month and a full test mode. No card required.
The stack matrix
Every guide builds the same thing, terms and privacy acceptance at signup, with the tools your stack already has. The two columns in the middle are where the stacks differ.
| Stack | Server language | How the session is created | How the browser part is loaded | Guide |
|---|---|---|---|---|
| Next.js and Supabase | TypeScript | A server action calls esc.sessions.create from the Node SDK | @esigncomply/react hooks from npm, in a client component | 7 files |
| Rails | Ruby | A controller calls POST /v1 with Net::HTTP | Script tag in the ERB view (global EsignComply) | 8 files |
| Django | Python | A view calls POST /v1 with requests | Script tag in the template (global EsignComply) | 7 files |
| Laravel | PHP | A controller calls POST /v1 with the Http facade | Script tag in the Blade view (global EsignComply) | 8 files |
| React Native | TypeScript (an Express API) | Your API server calls esc.sessions.create from the Node SDK | Script tag in a page on your domain, shown in a WebView | 8 files |
Next.js and Supabase
Seven files put terms and privacy acceptance on your signup page: a server action creates the session, your own checkbox and button collect the acceptance, and Supabase creates the user only after your server has confirmed the record.
Get the code Ruby · 8 filesRails
Eight files put a terms and privacy checkbox on your Rails signup, call the Esign Comply API with Net::HTTP, and create the user only after the acceptance is confirmed as a sealed record.
Django
One small Django app adds a terms and privacy checkbox to your signup, calls the Esign Comply API with requests, and creates the user only after the acceptance is confirmed as a sealed record.
Laravel
Eight files put a terms and privacy checkbox on your Laravel registration, call the Esign Comply API with the Http facade, and create the user only after the acceptance is confirmed as a sealed record.
React Native
A React Native app shows its acceptance screen in a WebView that loads a page from your own domain, passes the client token in, and gets the record ID back over the message bridge before your server creates the account.
Get the codeWhat every guide builds
Four steps, in every stack. You write the screens and your server holds the key. Esign Comply supplies the rules and keeps the sealed record.
- 01Your server creates a sessionOne call with the secret key:
POST /v1with your profile, the signer and the documents. Only the short-lived client token goes to the browser./sessions - 02Your own form collects the acceptanceYour notice, your unchecked checkbox, your links and your button. The browser SDK attaches to them, reports each step from the signer's browser, and
complete()returns a record ID. - 03Your server confirms the record
GET /v1with the secret key, checked against what your server saved: status,/records /{id} livemode, signer and document versions. The account is created after that and not before. - 04Your database keeps the receiptA small
acceptancestable holds the user ID, the record ID, the document version IDs, the signed receipt and the accepted time. Esign Comply keeps the sealed record itself.
Not on the list? It is two calls from any language
The API is HTTPS and JSON. If your server can send a request with a bearer token, it can create the session and confirm the record. For Go, Elixir, .NET, Java or plain PHP, follow the Rails, Django or Laravel guide: the requests are the same.
# 1. Your server creates the session. Only client_token goes to the browser. curl "https://esigncomply.com/v1/sessions" \ -H "Authorization: Bearer $ESIGNCOMPLY_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: signup-user_7c1d-1" \ -d '{ "profile": "prof_signup_4f1a", "signer": { "external_id": "user_7c1d", "email": "dana@example.org", "class": "consumer", "country": "US", "region": "US-CA" }, "documents": [ { "document": "doc_8Hq2", "version": "current" }, { "document": "doc_Pv71", "version": "current" } ], "context": { "url": "http://localhost:3000/signup", "locale": "en-US", "purpose": "account_signup" } }' # 2. The browser SDK runs the ceremony with the client token # and returns a record ID. # 3. Your server confirms that record before it creates the account. curl "https://esigncomply.com/v1/records/rec_Z4m8" \ -H "Authorization: Bearer $ESIGNCOMPLY_API_KEY" # Require: status is recorded, timestamped or anchored, # livemode is what you expect, and signer.external_id and # documents[].version_id equal what your server saved in step 1.
Start from your AI tool or from the agreement
A stack guide is one way in. The same clickwrap also comes as a prompt for the tool you build with, and as a worked example for the agreement you need signed.
One prompt for your tool
Cursor, Claude Code, Lovable, v0, Bolt, Replit and more. Each page has the prompt to paste, the steps to run it and the files the tool writes.
Pick your AI toolBeyond the signup checkbox
NDAs, contractor agreements, consent forms, order forms and terms updates. Each page has a live demo you can sign in test mode.
See the use casesThe rules for your regions
Pick your use case, regions, signer types and stack. You get one prompt with your own document and profile IDs and the rule packs you selected.
Generate a promptQuestions about the stack guides
Which stacks can I add a clickwrap to?
Any stack with a server and a web page. The API is plain HTTPS and JSON, and the browser SDK is one script that attaches to your own checkbox and button. This site has complete guides for Next.js and Supabase, Rails, Django, Laravel and React Native, and the same two server calls work from any other language.
Is there a server SDK for Ruby, Python or PHP?
The server SDK exists for Node. Rails, Django and Laravel call the REST API with the HTTP client they already ship with: Net::HTTP, requests and the Http facade. Each guide includes that client as one short file with the bearer token, the idempotency key and the retry on a rate limit.
Is a clickwrap I build myself recognized as an electronic signature?
Yes. Electronic signatures are recognized under the U.S. ESIGN Act and state UETA laws: a signature cannot be denied legal effect just because it is electronic. What makes a clickwrap hold up is notice, an unmistakable act of assent, and a record of both. The guides build the first two into your form, and Esign Comply keeps the third as an independent, tamper-evident record.
Read the ESIGN Act checklistCan my AI coding tool write this for me?
Yes. Each guide ends with a short prompt for that stack, and the prompt generator writes a longer one with your own document IDs, profile and rule packs. Paste it into Cursor, Claude Code, v0, Lovable, Bolt or Replit and the tool builds the same files in your repository.
Pick your AI toolWhat does a signup clickwrap cost to run?
The Free plan includes 10 live signatures a month and a full test mode, with no card. Every guide runs on it. Starter is $200 per year for 2,000 live signature events and Unlimited is $1,200 per year. One event is one signer's completed signing act, so the terms and the privacy notice accepted together at signup count once.
See pricingPick your stack, copy the files, run the check.
Free plan: 10 live signatures a month and a full test mode. No card required.