Skip to content
Compliance · United States

ESIGN Act and UETA checklist for developers

Electronic signatures are recognized under the U.S. ESIGN Act and state UETA laws. The two laws ask six things of yours: the signer meant to sign, agreed to do it electronically, signed that exact document and can be tied to the act, and you kept the record and gave them a copy. This checklist turns each requirement, and the notice and assent rules from the leading court decisions, into an implementation task with its source.

Is a DIY e-signature legally valid?

Yes. Electronic signatures are recognized under the U.S. ESIGN Act and state UETA laws. A signature, contract or record cannot be denied legal effect just because it is electronic (15 U.S.C. § 7001(a)).

Neither law names a vendor or a technology. An electronic signature is any sound, symbol or process attached to or logically associated with a record and adopted with intent to sign (§ 7006(5)), and states that adopt their own rules cannot favor one technology over another (§ 7002). A checkbox you coded yourself is an electronic signature in the same sense as a name drawn on a hosted signing page. The method changes how strong your evidence is, not whether the signature counts.

The Acts remove one objection: that the signature is electronic. Whether an agreement was formed is still decided by ordinary contract law, which is where the notice and assent rules in part 4 come from.

What makes one hold up

  • Notice. The signer was shown what they were agreeing to and which act means yes.
  • An unmistakable act of assent. Their own tick, click or typed name, on a control that started empty.
  • A record of both. Kept so that it can be produced later, unchanged, with the exact document.

You build the first two in your own interface. Esign Comply gives your AI tool the rules for them and keeps the third: an independent, tamper-evident record.

Block ruleThe API refuses to seal a live record until it is met.
Warn ruleMeasured and reported with a fix. The record is still sealed.
Esign Comply does thisDone for every record, with nothing for you to build.
You build thisYour screen, your wording or your process.
Part 1 of 5

A valid electronic signature: intent, consent, association and attribution

These six apply to every signature and every acceptance, whatever the document. Each row gives the requirement and its source, the task in engineering terms, and the rule or SDK step that covers it.

A valid electronic signature: requirement, implementation task and coverage
Requirement and sourceImplementation taskHow Esign Comply covers it
01
Intent to signAn electronic signature is a sound, symbol or process "executed or adopted by a person with the intent to sign the record".15 U.S.C. § 7006(5)UETA § 2(8)
Implementation task
Require an explicit act for every signature: a checkbox plus a button, a button with a matching notice, a typed name, a drawn signature or a passkey. Store the exact notice text that was on screen. Never infer signing from a login, scrolling or a page load.
How Esign Comply covers it
Block ruleUS-01CR-01
A record cannot be sealed without the intent action and the notice text. observeAssent() records both, and complete() sends the signing act.
02
Consent to do business electronicallyUETA applies only between parties who have agreed to transact electronically, and that agreement is read from the context and the parties' conduct. ESIGN does not require anyone to agree to use electronic records or signatures.UETA § 5(b), (c)15 U.S.C. § 7001(b)(2)
Implementation task
For a terms acceptance, the context supplies it: the user is signing up online. For a document someone signs, say it in the notice ("you agree to sign this agreement electronically") and give the signer a way to decline.
How Esign Comply covers it
Warn ruleUS-04CR-12
On signature profiles the check looks for the electronic-signing statement in the notice. ceremony.cancel() backs your decline control.
03
The signature is associated with the recordThe signature has to be "attached to or logically associated with" the contract or record it signs.15 U.S.C. § 7006(5)
Implementation task
Publish each document as an immutable version, hash it, and bind every signature to that hash. Link the signer to that exact version, never to a page that changes.
How Esign Comply covers it
Block ruleUS-02CR-08
You register versions through the API. Every record pins each version by SHA-256, and presentDocument() checks that your page served the registered text.
04
Attribution to a personA signature is attributable to a person when it was that person's act. That can be shown in any manner, including by showing that a security procedure worked.UETA § 9
Implementation task
Record how the signer was tied to the act: your user ID, the sign-in or verification method and its result, the address a code was sent to, the IP address, the user agent and the session. Pick a stronger step for higher-stakes documents.
How Esign Comply covers it
Esign Comply does thisBlock ruleUS-34US-36CR-17
Every record states those facts and its assurance level: L1 (your own session), L2 (an email or SMS one-time code confirmed by Esign Comply) or L3 (a passkey). An L2 or L3 ceremony cannot complete until the verification is done.
05
A chance to review and correctIn an automated transaction, a person can avoid the effect of a record that resulted from their own error when the system gave them no opportunity to prevent or correct it.UETA § 10(2)
Implementation task
Show a review step before the final act in signature and purchase flows, with a way to go back and fix an input.
How Esign Comply covers it
Warn ruleUS-05CR-13
reviewPresented() records that the summary was shown and whether it was correctable. The check warns when it is missing.
06
Automations and AI agentsA contract cannot be denied effect solely because an electronic agent took part in forming it, as long as the agent's action is legally attributable to the person bound.15 U.S.C. § 7001(h)UETA § 14
Implementation task
When a script or an AI agent performs the act, record that it was an agent, who operates it and under what authority. Never let it pass as a person's click.
How Esign Comply covers it
Block ruleUS-06
Create the session with signer.actor_type: "electronic_agent", signer.operator and signer.authority_reference. Profiles for people reject a click that did not come from a real user event.
Part 2 of 5

Consumer e-consent under 15 U.S.C. § 7001(c), and when it applies

This part applies in one situation: a statute or regulation requires you to give a consumer information in writing, and you want to give it electronically instead.

Consumer financial disclosures under Regulation Z and Regulation E are the common case. An ordinary terms of service acceptance at signup is not one of those cases, so items 7 to 11 do not apply to it. Where they do apply, the three steps run in a fixed order before the documents and the assent control: disclosure, access demonstration, consent. Switch them on with consumer_econsent: true on the profile and read required_steps from the session.

Consumer consent to electronic records: requirement, implementation task and coverage
Requirement and sourceImplementation taskHow Esign Comply covers it
07
Pre-consent disclosureBefore consenting, the consumer gets a clear and conspicuous statement of: any right to a paper copy, the right to withdraw consent and what follows from it, whether the consent covers one transaction or categories of records, how to withdraw and update contact details, and how to get a paper copy and any fee.15 U.S.C. § 7001(c)(1)(A), (B)
Implementation task
Write the disclosure for your own practice and show it before the consent control, under the fixed headings the session returns in required_strings.
How Esign Comply covers it
Block ruleYou build thisUS-21
The API rejects a consent event when the registered disclosure lacks an element. presentDisclosure() records a hash of the text as shown. The wording under each heading is yours.
08
Hardware and software statementThe disclosure states the hardware and software the consumer needs to access and retain the records.15 U.S.C. § 7001(c)(1)(C)(i)
Implementation task
State what a consumer needs to open and keep your records, for example a current browser and a PDF reader, under its own heading.
How Esign Comply covers it
Block ruleYou build thisUS-22
Checked as a required element of the disclosure. Keeping the statement accurate is yours.
09
Access demonstrationThe consumer consents, or confirms consent, electronically in a way that reasonably demonstrates they can access the format you will use.15 U.S.C. § 7001(c)(1)(C)(ii)
Implementation task
Show access before consent: present a sample in the delivery format and have the consumer do something only a person who opened it can do.
How Esign Comply covers it
Block ruleUS-23
accessSample() returns a sample that contains a six-digit code. demonstrateAccess({ code }) records the step when the code matches.
10
Affirmative consentThe consumer has affirmatively consented to electronic records and has not withdrawn that consent.15 U.S.C. § 7001(c)(1)(A)
Implementation task
Collect consent on its own unchecked control, after the disclosure and the access step, and store it with the disclosure version.
How Esign Comply covers it
Block ruleUS-24CR-16
giveEConsent({ checkbox }) records the control's label, its state at load and whether a real user event changed it. A record that is missing any of the three steps is blocked.
11
Withdrawal, paper copies and changed requirementsThe consumer can withdraw consent and can ask for a paper copy. When hardware or software requirements change in a way that puts access at risk, the consumer gets the revised statement and the right to withdraw without a fee.15 U.S.C. § 7001(c)(1)(B), (D)
Implementation task
Build a withdrawal control and stop relying on electronic delivery for a consumer who uses it. Fulfil paper-copy requests at the fee you disclosed. After a material change, show the revised statement and run the access step again.
How Esign Comply covers it
Esign Comply does thisYou build thisUS-25US-26US-27
Every receipt email carries a withdrawal link, and POST /v1/signers/{id}/consents/withdraw reports one you received yourself. Esign Comply timestamps it and sends the consent.withdrawn webhook. Paper copies and delivery after a withdrawal are yours.
Build the consumer e-consent screen
Part 3 of 5

Record retention, accurate reproduction and copies for the signer

A signature you cannot produce later, unchanged and with its document, does not help you. These two cover what you keep and what the signer gets to keep.

Retention and copies: requirement, implementation task and coverage
Requirement and sourceImplementation taskHow Esign Comply covers it
12
Retention and accurate reproductionA law that requires a record to be kept is met by an electronic record that accurately reflects the information and stays accessible to everyone entitled to it, in a form that can be accurately reproduced later.15 U.S.C. § 7001(d)(1)UETA § 12
Implementation task
Keep the executed record and the exact document version, unchanged and retrievable, for as long as the law that governs your records requires. Keep your own export.
How Esign Comply covers it
Esign Comply does thisYou build thisUS-03US-30US-31US-32
Document versions are immutable. Records are append-only, hash-chained and kept for the configured period, and stay exportable for 12 months after you cancel. Where another law sets a retention period, holding a copy for that period is yours.
13
A copy the signer can keepA record is not enforceable against a recipient whose ability to store or print it was inhibited by the sender. Where a law requires a written contract, the electronic version has to be in a form every party can retain and reproduce.UETA § 8(a), (c)15 U.S.C. § 7001(e)
Implementation task
Let every signer download and print the document before they agree and the executed record afterward. Never block selecting, saving or printing.
How Esign Comply covers it
Esign Comply does thisYou build thisUS-29
Esign Comply emails the signer a receipt that links to their own record and the executed copy, with a download. presentDocument() records whether download and print controls were offered before assent.
Part 4 of 5

Notice and assent rules from the online-assent cases

ESIGN and UETA say an electronic signature counts. Courts decide whether the user agreed, and they decide it on the screen the user saw: reasonably conspicuous notice, and an action that unambiguously shows assent.

Notice and assent rules from the cases: requirement, implementation task and coverage
Requirement and sourceImplementation taskHow Esign Comply covers it
14
Assent is an affirmative actA pre-checked box, continued browsing or a page load is not assent.Nguyen v. Barnes & NobleSpecht v. NetscapeKauders v. Uber
Implementation task
Render every checkbox unchecked and every typed-name field empty. Never call .click() or set .checked for the user.
How Esign Comply covers it
Block ruleUS-08CR-01
The SDK records the state of the control at load and whether a real user event changed it.
15
The notice names the action and the agreementA click shows assent only when the user is explicitly told that it will. The button's label has to match the notice, and the label alone is not the notice.Berman v. Freedom FinancialChabolla v. ClassPassGodun v. JustAnswer
Implementation task
Write: "By checking the box and clicking Create account, you agree to the Terms of Service." Use the exact button label and every document title. Leave out "by continuing".
How Esign Comply covers it
Block ruleWarn ruleUS-09CR-02CR-03
A notice that is missing, or that omits a document title, blocks the record. A notice that does not name the button, or uses a vague phrase, is reported.
16
The notice and the control are on screen togetherThe notice sits above or directly beside the control, visible without scrolling at the moment of assent.Specht v. NetscapeMeyer v. UberCruz v. Tapestry
Implementation task
Put the notice directly above the button, in the same container. Test at 390 by 844.
How Esign Comply covers it
Block ruleUS-10CR-04
The SDK records both bounding boxes and the viewport size. The record is blocked when they cannot be seen together, and a notice below the button is reported.
17
Links and notice text are legibleLinks to the terms look like links, and the notice is not fine print.Berman v. Freedom FinancialCullinane v. UberMeyer v. Uber
Implementation task
Underline document links and give them a colour that differs from the sentence by 3 to 1. Set the notice at body size, at least 12 px, with contrast of 4.5 to 1 against its background.
How Esign Comply covers it
The SDK records the computed styles, and the check reports the measured contrast and font size. Courts name no pixel values: these are the thresholds the rule set measures.
18
One primary action"If everything on the screen is written with conspicuous features, then nothing is conspicuous."Cullinane v. Uber
Implementation task
Keep one primary button in the assent container. Give social sign-in its own container, its own notice and its own session.
How Esign Comply covers it
Warn ruleUS-13CR-07
The SDK counts the primary buttons in the assent region and the competing ones in the viewport.
19
The terms link works and serves the exact textThe Ninth Circuit found no mutual assent where the link to the terms did not open.9th Cir. No. 25-328 (unpublished)
Implementation task
Serve each document at a stable page on your own domain that renders the registered version by its ID.
How Esign Comply covers it
Block ruleUS-14CR-08
During the ceremony the SDK fetches the page behind the link, and the API compares its hash with the registered version. A mismatch is refused with render_mismatch.
20
The screen the user saw is capturedCourts judge the screen from the user's side, so you need to be able to show what this user was presented with.Meyer v. UberDawson v. Target
Implementation task
Capture the assent region as it rendered: markup, computed styles and layout, with the device class, browser, viewport and locale.
How Esign Comply covers it
Esign Comply does thisUS-15US-16
Esign Comply captures it, hashes it and seals it with the record. The check also replays your page at 390 by 844, 768 by 1024 and 1440 by 900.
21
Changed terms get a new actGood v. Uber enforced updated terms that were presented on a blocking screen with a checkbox and a confirm button.Good v. Uber
Implementation task
When you publish a material change, tell users in advance, then stop signed-in users at a screen with an unchecked box and a confirm button.
How Esign Comply covers it
Esign Comply does thisYou build thisUS-18
GET /v1/signers/{id}/status lists what each signer has outstanding, and a webhook fires for each affected signer when you publish. Earlier acceptances stay on record. The screen is yours.
Part 5 of 5

Document types excluded under 15 U.S.C. § 7003, and documents with state formalities

The Act does not reach every document. Section 7003 takes the types in item 22 out of ESIGN. The types in item 23 stay inside it, and state law adds a formality, such as a notary, that a generic signing flow does not supply.

Excluded document types: requirement, implementation task and coverage
Requirement and sourceImplementation taskHow Esign Comply covers it
22
Document types the ESIGN Act excludesWills, codicils and testamentary trusts. Adoption, divorce and other family law. Court orders, notices and official court documents. Notices that cancel utility service. Notices of default, foreclosure or eviction for a primary residence. Cancellation of health or life insurance. Product recalls. Documents that accompany hazardous materials. Most records governed by the Uniform Commercial Code.15 U.S.C. § 7003
Implementation task
Know the category of every document you send for signature, and keep these out of your electronic flow.
How Esign Comply covers it
Block rule
Send context.facts.document_category when you create the session. A blocked category is refused with document_type_excluded before any ceremony starts.
23
Documents with state formalitiesESIGN lets a notary sign electronically and leaves notarization itself to state law. Notarized documents, powers of attorney and health-care directives follow state formality rules, and New York's ESRA excludes further types.15 U.S.C. § 7001(g)N.Y. State Tech. Law § 307
Implementation task
Route these to a notary or to the process your state prescribes.
How Esign Comply covers it
Block ruleUS-44
The same screen blocks them at session creation, so they never reach a generic ceremony.

The screen runs when your server creates the session, before the signer sees anything. Send the category of the document, and a blocked one comes back as an error your code can show to the sender.

Every blocked document type
An excluded category, refused at session creation
POST /v1/sessions
{ "profile": "prof_signup_4f1a", "signer": { "external_id": "user_7c1d" },
  "documents": [{ "document": "doc_8Hq2" }],
  "context": { "facts": { "document_category": "will" } } }

422 Unprocessable Entity
{
  "error": {
    "type": "ceremony_error",
    "code": "document_type_excluded",
    "message": "This document category is outside the generic ceremony: Wills, codicils, testamentary trusts.",
    "rule": "US-FED/wills",
    "exclusion": "US-FED/wills",
    "pack": "US-FED",
    "reason": "Wills, codicils, testamentary trusts",
    "doc_url": "https://esigncomply.com/docs/api/errors#document_type_excluded",
    "request_id": "req_8Yb2kQ0x"
  }
}

The whole checklist on one page

All items with their sources and what covers them. Copy it as Markdown into an issue, a pull request or your AI coding tool, and tick the boxes as you go.

esign-ueta-checklist.md
ESIGN Act and UETA checklist for developers: every item with its source and what covers it
RequirementSourceCovered by
A valid electronic signature
01Intent to sign15 U.S.C. § 7006(5); UETA § 2(8)US-01, CR-01 (Block rule)
02Consent to do business electronicallyUETA § 5(b), (c); 15 U.S.C. § 7001(b)(2)US-04, CR-12 (Warn rule)
03The signature is associated with the record15 U.S.C. § 7006(5)US-02, CR-08 (Block rule)
04Attribution to a personUETA § 9US-34, US-36, CR-17 (Esign Comply does this + Block rule)
05A chance to review and correctUETA § 10(2)US-05, CR-13 (Warn rule)
06Automations and AI agents15 U.S.C. § 7001(h); UETA § 14US-06 (Block rule)
Consumer consent to electronic records
07Pre-consent disclosure15 U.S.C. § 7001(c)(1)(A), (B)US-21 (Block rule + You build this)
08Hardware and software statement15 U.S.C. § 7001(c)(1)(C)(i)US-22 (Block rule + You build this)
09Access demonstration15 U.S.C. § 7001(c)(1)(C)(ii)US-23 (Block rule)
10Affirmative consent15 U.S.C. § 7001(c)(1)(A)US-24, CR-16 (Block rule)
11Withdrawal, paper copies and changed requirements15 U.S.C. § 7001(c)(1)(B), (D)US-25, US-26, US-27 (Esign Comply does this + You build this)
Retention and copies
12Retention and accurate reproduction15 U.S.C. § 7001(d)(1); UETA § 12US-03, US-30, US-31, US-32 (Esign Comply does this + You build this)
13A copy the signer can keepUETA § 8(a), (c); 15 U.S.C. § 7001(e)US-29 (Esign Comply does this + You build this)
Notice and assent rules from the cases
14Assent is an affirmative actNguyen v. Barnes & Noble; Specht v. Netscape; Kauders v. UberUS-08, CR-01 (Block rule)
15The notice names the action and the agreementBerman v. Freedom Financial; Chabolla v. ClassPass; Godun v. JustAnswerUS-09, CR-02, CR-03 (Block rule + Warn rule)
16The notice and the control are on screen togetherSpecht v. Netscape; Meyer v. Uber; Cruz v. TapestryUS-10, CR-04 (Block rule)
17Links and notice text are legibleBerman v. Freedom Financial; Cullinane v. Uber; Meyer v. UberUS-11, US-12, CR-05, CR-06 (Warn rule)
18One primary actionCullinane v. UberUS-13, CR-07 (Warn rule)
19The terms link works and serves the exact text9th Cir. No. 25-328 (unpublished)US-14, CR-08 (Block rule)
20The screen the user saw is capturedMeyer v. Uber; Dawson v. TargetUS-15, US-16 (Esign Comply does this)
21Changed terms get a new actGood v. UberUS-18 (Esign Comply does this + You build this)
Excluded and special-form documents
22Document types the ESIGN Act excludes15 U.S.C. § 7003Block rule
23Documents with state formalities15 U.S.C. § 7001(g); N.Y. State Tech. Law § 307US-44 (Block rule)

State rules on top of the Federal baseline

Everything above is the Federal rule pack, US-FED, which applies to every U.S. signer. States change the details. UETA is enacted in 49 states, the District of Columbia, Puerto Rico and the U.S. Virgin Islands, and the enactments are not identical. New York has not adopted it and uses its Electronic Signatures and Records Act alongside federal ESIGN.

Esign Comply has state rule packs for California, New York, Florida, Texas, Delaware, Virginia and Massachusetts. Each adds only what that state changes: renewal disclosures, cancellation steps, wider exclusion lists, employment documents. Send the signer's state as signer.region and the session returns the rules and wording that apply.

Hand the checklist to your AI tool

The prompt generator turns the rows that apply to your flow into one prompt for Cursor, Claude Code, v0, Lovable, Bolt or Replit. The conformance check then measures the page your tool built against the same rule IDs.

Questions about the ESIGN Act and UETA

Is a DIY e-signature legally valid?

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, and neither law requires a particular vendor or technology. What makes one hold up is notice, an unmistakable act of assent, and a record of both.

What is the difference between the ESIGN Act and UETA?

The ESIGN Act is federal law for transactions in or affecting interstate commerce. UETA is a uniform state law enacted in 49 states, the District of Columbia, Puerto Rico and the U.S. Virgin Islands. New York uses its own Electronic Signatures and Records Act. Both give electronic signatures and records legal effect. UETA adds rules on agreeing to transact electronically, attribution and error correction, and ESIGN adds the consumer consent rules.

Do I need the ESIGN consumer consent disclosure for a terms of service checkbox?

No, for an ordinary terms acceptance. The consumer disclosure and access demonstration in 15 U.S.C. § 7001(c) apply when a statute or regulation requires you to give a consumer information in writing and you deliver it electronically instead, for example consumer financial disclosures under Regulation Z or Regulation E.

Read the consumer e-consent guide

Which documents cannot be signed electronically under the ESIGN Act?

15 U.S.C. § 7003 excludes wills, codicils and testamentary trusts, adoption, divorce and other family-law documents, court orders and official court documents, notices that cancel utility service, notices of default, foreclosure or eviction for a primary residence, cancellation of health or life insurance, product recalls, hazardous-materials documents, and most records governed by the Uniform Commercial Code.

Every blocked document type

Does the ESIGN Act require a specific e-signature provider or technology?

No. The Act defines an electronic signature as any sound, symbol or process attached to or logically associated with a record and adopted with intent to sign. A checkbox, a click, a typed name, a drawn signature and a passkey all fit that definition. The method you choose changes how strong your evidence is, not whether the signature counts.

Build the signing flow to the checklist. Leave the record to us.

Free plan: 10 live signatures a month and a full test mode. No card required.

Working with an AI tool? This page is also available as Markdown: /compliance/esign-act-checklist.md