People use “electronic signature” and “digital signature” as if they meant the same thing. They don’t. One is a legal idea and the other is a cryptographic technique. Most e-signature products use both at once, which is part of why the terms get mixed up.
This post explains each term, how the EU’s three signature levels relate to them, and how to decide what your documents need. It is a technical explainer, not legal advice. For a specific document, ask your legal counsel.
Electronic signature is a legal category
An electronic signature is any electronic way a person shows they agree to a record. The US ESIGN Act defines it as “an electronic sound, symbol, or process, attached to or logically associated with a contract or other record and executed or adopted by a person with the intent to sign the record.”
The definition is about intent, not technology. A typed name, a drawn signature, a checkbox next to “I agree” and a click on a button can all qualify. What matters is that the person meant to sign and that you can show it later.
That second part is where the work is. A signature is only as good as the evidence around it: who the signer was, how they were identified, what they saw, when they signed and whether the document changed afterwards. An e-signature product exists mostly to collect and keep that evidence.
Digital signature is a cryptographic technique
A digital signature is math. The signer’s software computes a hash of the document and encrypts it with a private key. Anyone with the matching public key, usually inside a certificate, can check two things: that the signature came from the holder of that key, and that the document has not changed by a single byte since it was signed.
A digital signature says nothing on its own about intent or identity. It proves that a key signed a set of bytes. Who controls the key, and how the certificate authority checked their identity, decides how much that proof is worth.
How a typical e-signature uses both
In a typical SignatureAPI envelope, both ideas appear, at different layers.
The signer’s act is an electronic signature. At the start of the ceremony the signer consents to using electronic signatures, which most jurisdictions require. Then they review the documents, fill in any fields and add a typed or drawn signature.
The finished PDF carries a digital signature. When an envelope completes, SignatureAPI produces a deliverable: the signed documents plus an audit log that records every action in the signing process. That PDF is sealed with a cryptographic signature from a SignatureAPI certificate. Anyone can verify the seal to confirm that the file came from SignatureAPI and has not been altered since.
So the signer’s mark is not a cryptographic signature tied to the signer personally. The digital signature belongs to the platform and protects the evidence. SignatureAPI signatures are legally binding under ESIGN and UETA in the US and under eIDAS in the EU at this simple level.
The three eIDAS levels
The EU regulation on electronic identification and trust services (eIDAS, Regulation (EU) No 910/2014) defines three levels. Each adds requirements to the one before it, and this is where the two terms meet.
| Level | What it requires | Where the cryptography sits |
|---|---|---|
| Simple (SES) | Any electronic data a person uses to sign. | Optional. Often a platform seal on the result. |
| Advanced (AdES) | Uniquely linked to and identifies the signer, made with signing data under their sole control, and shows any later change. | In practice, a digital signature with a key the signer controls. |
| Qualified (QES) | An advanced signature made with a qualified certificate from a provider that verified the signer’s identity. | A digital signature with a qualified certificate in the signer’s name. |
A qualified trust service provider (QTSP) is a company that an EU supervisory body has approved to verify identities and issue qualified certificates. Under eIDAS, a QES has the same legal effect as a handwritten signature in every member state.
Under the same regulation, a court can’t reject an electronic signature only because it is electronic or not qualified. That is why a simple electronic signature covers most business documents in the EU as well as in the US.
Which one do you need?
Usually a simple electronic signature with good evidence. That covers sales contracts, offer letters, NDAs, order forms and most of what a SaaS product sends.
You need more when someone requires it:
- The law asks for a QES in place of a handwritten signature for certain documents, which some national laws do.
- A regulator asks for it, for example in some financial or public-sector procedures.
- The other party asks for it, such as a customer, partner or public tender.
Some documents are outside e-signature laws altogether. In the US, ESIGN does not apply to wills, codicils and testamentary trusts, family law matters such as adoption and divorce, and court orders and official court documents, among other exceptions. Check those cases before you automate them.
SignatureAPI supports both ends. A regular signer produces a simple electronic signature. A qualified signer produces a QES through a qualified provider that you choose and contract with. Qualified signatures are in public beta, with no extra charge during the beta.
Some countries also have their own standards that sit beside the signature level, such as NOM-151 in Mexico and ICP-Brasil in Brazil. SignatureAPI handles those with attestations, which add a preservation certificate or a trusted timestamp to the deliverable without changing who signs.
To see the evidence a simple signature collects, send a test envelope with a free test key and open the deliverable. The audit log at the end shows what evidence was recorded for each recipient.