Skip to content
Compliance · United States

ESIGN and UETA rules, built into your signing flow

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. Esign Comply gives your AI tool the ceremony rules drawn from those laws and from leading U.S. online-assent decisions, then keeps the independent record.

US-FED

What the Federal pack covers

The Federal pack covers ESIGN, the common UETA rules, federal assent decisions such as Berman v. Freedom Financial, and federal evidence procedures. It applies to every U.S. signer.

Intent and association

Direct browser ceremonies require a recorded explicit act and exact notice text. The record binds to the hash of the exact document version, reflecting the ESIGN Act's definition of a signature adopted with intent and logically associated with the record.

Notice and assent

Courts ask whether notice was reasonably conspicuous and assent unambiguous, judged on the screen shown (Berman). The SDK measures that screen and the API blocks the clearest failures.

Consumer e-consent

Built-in ESIGN consumer-consent flow: disclosures, access demonstration, withdrawal, paper-copy requests, following 15 U.S.C. § 7001(c).

Copies and retention

When we send a receipt, signers reach their retained executed copies through a link protected by a one-time code. On Starter and Unlimited, records are kept for up to ten years from signing while you are subscribed. For U.S. flows, read and export access lasts 12 months after cancellation. Statutory minimums and scoped legal holds extend retention for the affected records.

The record

Independent, tamper-evident records: hash-chained, signed with keys you do not hold, and timestamped by an outside RFC 3161 authority. Anyone you give the evidence package to can verify it offline with the open-source verifier.

On request, a named Esign Comply records custodian signs a declaration of what Esign Comply observed and recorded. The federal form is written for the procedures in Federal Rule of Evidence 803(6) and Federal Rule of Evidence 902(11), (13), and (14).

Rule packs

Federal, plus the state packs you select

Each state pack adds state-specific rules on top of Federal. Where both address the same step, the stricter rule applies. Combine California, New York, Florida, Texas, Delaware, Virginia, and Massachusetts in one profile. Each record lists the packs and the rule-set version applied.

State packs run in test mode today

Build and test against any state pack now. Each one goes live once counsel admitted in that state has reviewed it. Until then, a live session for that state applies the Federal pack and carries the warning state_pack_unavailable.

Selectable U.S. rule packs, the status of each, and what each adds
PackWhat it adds
FederalUS-FEDbaselineThe baseline for every U.S. profile: notice, intent, attribution, association with the record, retention, and copies. For consumers it adds the electronic-records disclosure, access demonstration, consent, and a withdrawal path.
CaliforniaUS-CAtest modeThe restricted basis for agreeing to transact electronically, an electronic return channel for cancellation notices, a wider exclusion list, a renewal-law style test and post-signing notices, sign-in wrap limits, employment and translation rules, and capture limits.
New YorkUS-NYtest modeESIGN plus ESRA in place of UETA, subscription disclosures, reminders and price-change steps, a New York City cancellation overlay, wage-notice acknowledgment, and a state-court certification path.
FloridaUS-FLtest modeFurther assent and attribution checks, renewal rules for service contracts, employment and contractor documents, marketing call and text consent, and added exclusions.
TexasUS-TXtest modeFurther assent and attribution checks, employment and contractor documents, marketing call and text consent, contract-clause prompts, and added exclusions.
DelawareUS-DEtest modeEntity documents under the corporate and LLC statutes, further assent and attribution checks, automatic-renewal rules, employment and contractor documents, and added exclusions.
VirginiaUS-VAtest modeAn extra rule for agreeing to transact electronically, automatic-renewal rules that also cover small businesses, marketing call and text consent, contract-clause prompts, and added exclusions.
MassachusettsUS-MAtest modeAll-in price and unavoidable disclosures, trial and negative-option disclosures with calendar dates, same-site cancellation, reminders, noncompete formalities, and the state evidence procedure.

How packs work in your code

A pack is versioned data. The session tells your code which rules applied, so you never hard-code a state.

State rules on top of Federal

A state pack holds only its differences from the Federal pack. Every Federal rule still applies. Where a state rule and a Federal rule address the same step, the more protective value wins.

You pass the signer's state

Send the signer's state as signer.region from your own data. It is never inferred from IP. A signer in a state without a pack gets the Federal pack, and the record says so.

The session returns the rules

POST /v1/sessions returns applied_jurisdictions, rules_fired, required_steps, and required_strings. Your AI tool builds from those, so adding or removing a state needs no code change to keep recording.

Pinned on every record

Each record lists the packs applied, their versions, and the rules that fired. A later pack version never changes a sealed record.

What we record, what you build, what we recommend

Every rule is split into parts, and each part belongs to exactly one class. The class decides who does the work and who holds the record.

Checked by Esign Comply

What we record

  • Our own record of the ceremony, with each field tagged observed or asserted.
  • Checks on that record. A blocking check refuses to seal a live record until the condition is met. A warning is measured and stored with the record.
  • An evidence report that states what was recorded, which packs applied, and which rules fired.
Built by you

Your obligations

  • Duties the cited law places on your company, such as renewal reminders, price-change notices, and cancellation handling.
  • The prompt lists each one with its source, so your AI tool can build it.
  • Send us a report when you perform one and we seal it beside the record.
Optional

Our recommendations

  • Practices Esign Comply suggests on top of the rules.
  • They appear under the words "Esign Comply recommends", apart from the required steps.
  • A recommendation never blocks a session, adds a required step, or returns an API error.

You build post-signing reminders, price-change notices, and cancellation handling from the prompt. Send us supplements to record what you did: free text, JSON, and files through POST /v1/supplements. We seal each one with our receipt time and list it in the evidence report as customer-supplied.

Document types the API blocks

The API refuses wills, family-law documents, official court documents, and the notices excluded from the federal ESIGN rule (15 U.S.C. § 7003). It also refuses powers of attorney, health-care directives, and documents that need a notary, a witness, or a public deed, including real-estate transfers. A blocked type returns document_type_excluded when you create the session.

Supported and blocked document types

Build the signing flow yourself. 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/united-states.md