Legal validity
Are electronic signatures legal?
A general overview of the laws that give electronic signatures legal effect, ESIGN and UETA in the US and eIDAS in the EU, with the SES, AES and QES levels.
In most countries, yes. Laws in the United States, the European Union and many other places say that a signature can’t be denied legal effect only because it’s electronic. This page gives a general overview of the main laws and the levels of electronic signature they describe, with links to the primary sources.
United States: ESIGN and UETA
Two laws work together in the US:
- ESIGN, the Electronic Signatures in Global and National Commerce Act of 2000 (15 U.S.C. § 7001 and following), is federal law. In transactions affecting interstate or foreign commerce, a signature, contract or record can’t be denied legal effect solely because it’s in electronic form.
- UETA, the Uniform Electronic Transactions Act, is a model law published by the Uniform Law Commission in 1999. Most states have adopted it, and it sets the same rule for state law.
ESIGN defines an electronic signature broadly: an electronic sound, symbol or process attached to a record and adopted by a person with the intent to sign it. A typed name, a drawn signature or a click on “I agree” can all qualify.
Both laws expect some conditions to be met, among them:
- Intent to sign. The person meant to sign.
- Consent to do business electronically. ESIGN adds specific disclosure and consent rules before a consumer receives required information electronically.
- Association with the record. The signature is attached to, or logically linked with, what was signed.
- Record retention. The signed record can be kept and reproduced accurately later.
ESIGN also lists documents it doesn’t cover, such as wills, many family-law matters and certain court documents and notices (15 U.S.C. § 7003). Other laws decide those.
European Union: eIDAS
eIDAS, the regulation on electronic identification and trust services (Regulation (EU) No 910/2014), applies directly in every EU member state. It was amended by Regulation (EU) 2024/1183. Article 25 sets the basic rules:
- An electronic signature can’t be denied legal effect or admissibility as evidence in court solely because it’s electronic or doesn’t meet the requirements for qualified signatures.
- A qualified electronic signature has the same legal effect as a handwritten signature.
- A qualified signature based on a qualified certificate issued in one member state is recognized as qualified in all the others.
eIDAS defines three levels, each building on the one before:
| Level | What it is |
|---|---|
| Simple (SES) | Data in electronic form that a person uses to sign: a typed name, a drawn signature, a click. |
| Advanced (AES) | Uniquely linked to the signer, capable of identifying them, created with data under their sole control, and linked to the document so any later change is detectable. See Advanced electronic signature. |
| Qualified (QES) | An advanced signature created with a qualified signature creation device and based on a qualified certificate from a qualified trust service provider (QTSP). See Qualified electronic signature. |
National law decides where a specific level is required, for example for some property, family or public-sector documents.
Other countries
Many other countries have electronic signature laws, often based on the UNCITRAL Model Law on Electronic Commerce and Model Law on Electronic Signatures. Some add country-specific standards, such as NOM-151 in Mexico or ICP-Brasil in Brazil, which SignatureAPI supports as attestations.
What SignatureAPI gives you
SignatureAPI produces two of the three eIDAS levels:
- Simple electronic signatures, for every recipient type except qualified signers. The recipient agrees to use electronic records and signatures before signing, and the audit trail records who signed, how they were authenticated, what they agreed to and when. The deliverable is sealed so any later change is detectable.
- Qualified electronic signatures, through a qualified signer and the QTSP you choose. Qualified signatures are in public beta, at no extra charge during the beta. See What are qualified signatures?
SignatureAPI doesn’t produce advanced electronic signatures.
The eIDAS signature levels SignatureAPI produces
| Item | Simple (SES) | Qualified (QES) |
|---|---|---|
| What it is | Any electronic data a person uses to sign: a typed name, a drawn signature, a click | An advanced signature made with a qualified certificate, from a provider that verified the signer's identity |
| Legal effect in the EU | A court can't reject it only because it's electronic or not qualified | The same legal effect as a handwritten signature in every EU member state |
| SignatureAPI recipient type | signer and every other type except qualified_signer | qualified_signer |
| Signer identity | Recorded by the ceremony's authentication | Verified by the QTSP |
| Signing certificate issued to the signer | No | Yes |
| Routing | Sequential or parallel | Sequential only |
| Deliverable | Configurable | One PDF with every document, no audit log |
| Availability | Every account | Public beta, bring your own QTSP |
SignatureAPI operates at the SES level for all recipient types except qualified signers.
SignatureAPI doesn't produce advanced electronic signatures (AdES). An AdES is uniquely linked to the signer and identifies them, is made with signing data under their sole control, and shows any later change to the document.
A simple electronic signature covers most business documents. Ask your legal counsel which level each document needs.
Test envelopes carry a “non-binding test document” watermark and have no legal value. Only envelopes created with a live API key produce signed documents.
Related
- Audit trail: what the evidence contains.
- Verify a deliverable: check the seal on a signed PDF.
- Compliance: SOC 2, GDPR, HIPAA and CCPA.
- Glossary: other terms.