ESIGN Act vs UETA: what's the difference?
The ESIGN Act and UETA are the two laws that make electronic signatures legally valid in the United States, and they work together rather than competing: the ESIGN Act of 2000 is a federal law, while the UETA (Uniform Electronic Transactions Act) is a model law that individual states adopt on their own. The short version: UETA governs most day-to-day transactions within a state that has adopted it, and ESIGN acts as a federal backstop that applies nationwide, including in transactions that cross state lines.
Why there are two laws instead of one
In the US, contract law is primarily a matter of state law, not federal law. When electronic transactions started becoming common in the late 1990s, lawmakers faced a choice: pass a single federal law covering everything, or let states adopt their own rules under a shared model. They ended up doing both. The UETA, drafted by the Uniform Law Commission in 1999, gave states a ready-made law to adopt for transactions within their own borders. The ESIGN Act (Electronic Signatures in Global and National Commerce Act), passed by Congress in 2000, became the federal law ensuring validity for interstate and international transactions, and for states that hadn't adopted UETA.
Where they overlap
Both laws rest on the same core principle: a signature, contract, or record can't be denied legal effect solely because it's in electronic form. Both require that the parties have reasonably consented to transact electronically, that there's a record of the signer's intent, and that the record can be retained and reproduced accurately. If you're looking for the plain-language breakdown of what the ESIGN Act specifically requires, see What is an electronic signature? for the broader picture.
Where they differ
|
ESIGN Act |
UETA |
| Level |
Federal |
State (adopted individually by each state) |
| Scope |
Interstate and international commerce, and any state that hasn't adopted an equivalent law |
Transactions within the adopting state |
| Adoption |
Applies automatically nationwide |
Each state legislature votes to adopt it, sometimes with modifications |
| Consumer disclosures |
Includes specific additional disclosure requirements for consumer transactions |
Generally defers to state consumer protection law |
| Relationship to state law |
Preempts (overrides) inconsistent state law, but defers to state UETA adoption where consistent |
Operates as ordinary state law once adopted |
The practical effect is that most states today have an electronic transactions law — their own version of UETA — that handles most contracts signed within that state, while the ESIGN Act fills in the gaps for interstate deals and acts as a nationwide floor that state law can't undercut.
A practical example
If a business in Texas sends a contract to a customer also in Texas, and Texas has adopted UETA (it has), that transaction is primarily governed by Texas's UETA. If that same business sends a contract to a customer in another state, the ESIGN Act's federal protection ensures the signature is still valid regardless of which state's rules might otherwise apply. In practice, for most everyday business use, you don't need to figure out which specific law governs a given signature — both frameworks exist precisely so that this question rarely matters to the outcome.
Do both apply to the same document at once?
Often, yes. A transaction between two parties in the same UETA-adopting state is typically covered by both: the state's UETA governs it directly, and the ESIGN Act provides a federal baseline that state law can't fall below. Neither law requires you to pick one over the other — the practical effect of having both is that there's very little gap where an electronic signature in the US would be left without legal footing.
New York and a handful of other states
A small number of states, including New York, didn't adopt the model UETA text exactly as written — some adopted their own electronic signatures law with similar principles but different specifics. In these states, the ESIGN Act's federal protection becomes more directly relevant for electronic transactions, since the state-level framework may differ in its exact scope or exceptions. If your business regularly signs documents involving parties in a state with a non-standard adoption, it's worth confirming how that state's law is structured.
Does either law require specific technology?
No. Neither the ESIGN Act nor UETA mandates a particular signing technology, visual style, or vendor. Both focus on the process — consent, intent, and a retrievable, accurate record — rather than on how the signature looks. That's part of why electronic signature platforms built decades after these laws were passed are still covered by them without needing new legislation.
What "reasonably consented to transact electronically" actually means
Both laws condition validity on the parties having agreed to do business electronically in the first place, but neither requires a separate, formal consent document signed in ink before you're allowed to use e-signatures. In practice, consent is usually established by context: a business sending a contract through a signing platform, with the recipient then opening the link and completing the signature fields, is itself conduct that demonstrates agreement to transact electronically. The disclosure requirements get more specific for consumer transactions, where ESIGN requires that consumers be given a clear way to opt out of electronic records in favor of paper ones, and the business must retain the ability to actually provide the paper alternative if asked.
How this differs from the EU's approach
It's worth contrasting the US model with the European Union's eIDAS Regulation (EU) No 910/2014, since businesses operating in both markets sometimes assume the frameworks map onto each other directly. They don't: ESIGN and UETA take a largely technology-neutral, single-tier approach — a signature is valid or it isn't, without a formal classification system. eIDAS instead defines tiers (simple, advanced, qualified) with different formal requirements for different use cases. See eIDAS: simple, advanced and qualified signatures if you also operate in the EU and need to know which tier applies to a given document.
Why this distinction rarely changes what you actually do day to day
For the overwhelming majority of US businesses, the ESIGN/UETA distinction is background legal architecture rather than something that changes daily practice. You don't choose which law to invoke when sending a contract, and a compliant signing process under one is, in practice, compliant under the other given how closely their substantive requirements overlap. The distinction mainly matters if a signature is ever challenged and a court needs to identify precisely which statute governs the transaction — which is a question for the specific facts of that case, not something to resolve in advance for routine business documents.
Build on a compliant process
Whether a signature falls primarily under ESIGN, a state's UETA, or both, what actually matters for validity is the underlying process. Esignapi's REST API captures signer identification, explicit consent, and a hash-chained audit trail automatically for every signature request, so that evidence is already in place if it's ever needed.
Frequently asked questions
If my state has adopted UETA, do I still need to worry about the ESIGN Act?
Not usually for day-to-day transactions — your state's UETA likely covers most of what you need. The ESIGN Act mainly matters for transactions crossing state lines or when a party is in a state with a non-standard electronic transactions law.
Has every US state adopted UETA?
The vast majority have, though a few states (including New York) use their own state-specific electronic signatures law instead of adopting the uniform UETA text directly. The underlying principles are generally similar either way.
Which law is newer, ESIGN or UETA?
UETA was drafted first, in 1999, as a model law for states to adopt. The ESIGN Act followed in 2000 as the federal law.
Does the ESIGN Act override state law?
The ESIGN Act preempts inconsistent state law, but it explicitly allows states to use UETA (or an equivalent law) instead, so in states that adopted UETA, state law and federal law generally work in harmony rather than in conflict.
Do international transactions fall under ESIGN or UETA?
Neither law was designed as an international framework by itself, though the ESIGN Act's title explicitly references global commerce and gives US-based transactions a baseline of validity even when a counterparty is abroad. International deals may also need to account for the other party's own local law, such as eIDAS in the European Union.