eIDAS checklist for developers: simple electronic signatures
A ticked box, a typed name or a click is a simple electronic signature under eIDAS when a person uses it to sign an exact document. Article 25(1) says it cannot be denied legal effect just because it is electronic. This checklist turns eIDAS, the EU online-contract rules and GDPR into implementation tasks for a signing flow you build yourself, each with its source, and notes where the UK and Switzerland differ.
Is a simple electronic signature valid under eIDAS?
Yes. An electronic signature cannot be denied legal effect or admissibility as evidence solely because it is electronic (eIDAS Article 25(1)).
eIDAS defines an electronic signature as data in electronic form, attached to or logically associated with other electronic data, which the signatory uses to sign (Article 3(10)). No certificate, device or vendor is part of that definition. That is the simple level, and it is the level Esign Comply records: every signing act at assurance level L1, L2 or L3 is sealed with signature_level: "simple".
What simple electronic signatures are used for. Agreements the parties can make in any form: terms of service and clickwrap, NDAs, contractor and commercial agreements, order forms, consents and policy acknowledgments.
eIDAS leaves national rules on form in place (Article 2(3)) and treats only its highest signature level as equal to a handwritten signature (Article 25(2)). Where a national law demands handwriting, a notary or a named signature level for a document type, that law decides. Part 2 lists those types, and the API keeps them out of your flow.
What gives one its weight
- An explicit act. The signer's own tick, click or typed name, on a control labelled as agreeing or signing.
- The exact document. One frozen version, named by its hash.
- Independent evidence. A record of both, kept by someone who is not a party, with an outside timestamp.
You build the first in your own interface. Esign Comply gives your AI tool the rules for it, pins the second by hash and keeps the third.
A simple electronic signature under eIDAS: the act, the document and the evidence
These four apply to every signing act. Each row gives the requirement and its source, the task in engineering terms, and the rule or SDK step that covers it.
| Requirement and source | Implementation task | How Esign Comply covers it |
|---|---|---|
01 An explicit act of signingAn electronic signature is data "which is used by the signatory to sign". A login, a page view or a pre-ticked box is not signing.eIDAS Art. 3(9) to (12), 25French Civil Code Art. 1367 | Implementation task Give every signature its own control, labelled as agreeing or signing. Render boxes unchecked and name fields empty. Never call .click() or set .checked for the user. | How Esign Comply covers it |
02 One frozen version of the documentThe signature is "attached to or logically associated with" the data it signs, so that data has to be fixed.eIDAS Art. 3(10) | Implementation task Publish each document as an immutable version and link the signer to that exact version. Changed text is a new version. | How Esign Comply covers it Block ruleEU-01 You register versions through the API. Each session pins its versions when it is created, and the record names each one by SHA-256 hash. |
03 The record states its level and how the signer was tied to the actArticle 25(1) keeps a simple signature from being refused for its form. Its weight rests on the evidence, so the record has to say exactly what was shown and who observed it.eIDAS Arts. 3, 25, 26Golden Ocean v Salgaocar | Implementation task Pick the assurance level per profile by what is at stake. Repeat signature_level unchanged in your interface and PDFs. Never let an administrator or a shared account sign for the signer. | How Esign Comply covers it |
04 An outside timestamp, a provider seal and evidence that verifies laterAn electronic time stamp binds data to a time and cannot be denied effect as evidence solely because it is electronic. A seal shows the origin and integrity of data. It is a different thing from a person's signature.eIDAS Arts. 32 to 42Implementing Regulation 2025/1929Implementing Regulation 2025/1946RFC 3161 | Implementation task Store the time from the confirmed record, never from the browser. Keep the receipt in your own row, and export the evidence package for the records you rely on. | How Esign Comply covers it |
National form rules: where a simple electronic signature does not fit
eIDAS says an electronic signature counts. National law decides which documents need more. The form screen keeps those out before a signer sees anything.
| Requirement and source | Implementation task | How Esign Comply covers it |
|---|---|---|
05 Jurisdiction, signer and document type are confirmedeIDAS leaves national rules on the form of a contract in place. National law reserves some documents for handwriting, a notary or a named signature level: German employment terminations, Italian Civil Code Art. 1350 contracts, Spanish public-document acts, Irish wills and dispositions of real property, family-law documents and public deeds.eIDAS Art. 2(3)E-Commerce Directive Art. 9BGB § 623Italy: CAD Art. 21Spanish Civil Code Arts. 1278 to 1280Ireland: Electronic Commerce Act 2000French Civil Code Art. 1175BGB § 311b | Implementation task Send signer.country, signer.class and context.facts.document_category from your own data. Never guess the country from an IP address. Route reserved documents to the form the law prescribes. | How Esign Comply covers it |
06 United Kingdom: deedsIn England and Wales a deed signed by an individual needs a witness who is physically present and attests the signature, and the deed has to be delivered. Companies have their own execution routes.Law of Property (Miscellaneous Provisions) Act 1989, s.1Companies Act 2006, s.44Law Commission report | Implementation task Send document_category: "deed" for anything executed as a deed and run it through a witnessed process. Handle Scottish and Northern Irish special forms in your own process. | How Esign Comply covers it The UK pack blocks deeds in the generic flow. Other UK signing acts are recorded as simple electronic signatures. |
07 Switzerland: statutory written formWhere Swiss law requires written form, the Code of Obligations accepts one electronic equivalent of a handwritten signature: a signature and timestamp from a provider recognised under the Swiss signature act, ZertES. A recognition in the EU does not carry over.Swiss Code of Obligations Arts. 11, 14 and 216Swiss Federal Office of Communications | Implementation task Send document_category: "statutory_written_form" for any contract Swiss law requires in writing, and keep it out of your click-to-sign flow. | How Esign Comply covers it Block ruleEU-20 The Swiss pack blocks statutory written-form contracts and public deeds. Contracts with no form requirement are recorded as simple electronic signatures. |
Send the signer's country and the category of the document when your server creates the session. A blocked combination comes back as an error your code can show to the sender. The same category passes for a signer in a country with no such rule.
Every blocked document typePOST /v1/sessions
{
"profile": "prof_nda_9c2e",
"signer": { "external_id": "user_7c1d", "country": "DE" },
"documents": [{ "document": "doc_Nd55" }],
"context": {
"facts": { "document_category": "employment_termination" }
}
}
422 Unprocessable Entity
{
"error": {
"type": "ceremony_error",
"code": "document_type_excluded",
"message": "This document category is outside the generic ceremony: Germany: termination of employment.",
"rule": "EU-08",
"exclusion": "EU/de-employment-termination",
"pack": "EU",
"reason": "Germany: termination of employment",
"doc_url": "https://esigncomply.com/docs/api/errors#document_type_excluded",
"request_id": "req_8Yb2kQ0x"
}
}Contracts concluded online: the EU consumer and e-commerce rules
Items 8 and 11 cover any order placed on a website. Items 9 and 10 apply when the signer is a consumer. For an NDA between two companies, go to part 4.
| Requirement and source | Implementation task | How Esign Comply covers it |
|---|---|---|
08 Terms the customer can keep, and a way to fix mistakesBefore the order, the customer gets a technical means to find and correct input errors, and the terms in a form they can store and reproduce. After it, an acknowledgment by electronic means without undue delay.E-Commerce Directive Arts. 10 to 11Unfair Contract Terms Directive Arts. 3, 5, 6 | Implementation task Show a review step labelled "Review or correct your details". Put "Download or print the exact terms" beside the pinned version, before the assent control. Email an order acknowledgment. | How Esign Comply covers it |
09 The order button says the order costs moneyWhere an order obliges a consumer to pay, the main characteristics, total price, duration and minimum commitment are shown directly before the order. The button carries only the words "order with obligation to pay" or an equally clear formulation.Consumer Rights Directive Art. 8(2)Directive 2024/825Fuhrmann-2, C-249/21Conny, C-400/22 | Implementation task Label the final button "Order with obligation to pay", or "Zahlungspflichtig bestellen" in German. Put the order information directly above it. | How Esign Comply covers it |
10 Durable confirmation and an online withdrawal functionThe consumer gets confirmation of the contract on a durable medium, at the latest on delivery or before the service begins. A bare link to your website does not count. From 19 June 2026, contracts concluded through an online interface also need a withdrawal function that stays available for the whole withdrawal period.Consumer Rights Directive Arts. 8(7), 11aDirective 2023/2673Content Services, C-49/11BAWAG, C-375/15German BGB § 356a | Implementation task Email the contract as text or as an attachment the consumer keeps. Build the two-step withdrawal function with the labels the session returns: "Withdraw from contract here", then "Confirm withdrawal". Acknowledge each withdrawal by email. | How Esign Comply covers it |
11 Offered languages and plain wordingThe languages offered for concluding the contract are stated before the order, and consumer terms are written in plain, intelligible language. Member states are free to add language requirements.E-Commerce Directive Art. 10(1)(d)Unfair Contract Terms Directive Art. 5Consumer Rights Directive Art. 6(7) | Implementation task List the languages you offer in context.facts.offered_languages, register a document version for each, and let the signer choose. | How Esign Comply covers it |
Personal data in the evidence: GDPR and ePrivacy
A record of who signed is personal data. These two rows keep what is captured small and put the processing terms in place before your first live signature.
| Requirement and source | Implementation task | How Esign Comply covers it |
|---|---|---|
12 Minimal capture and privacy informationPersonal data is limited to what the purpose needs, by default. Reading or storing information on a user's device needs consent unless it is strictly necessary. The person is told what is collected, why and by whom.GDPR Arts. 5, 6, 25GDPR Arts. 7, 13 to 14ePrivacy Directive Art. 5(3) | Implementation task Keep fingerprinting and session replay off the signing page. Render the sentence the session returns in required_strings: "{Company} uses Esign Comply to record this event on its behalf. See {Company}'s Privacy Notice for purposes and roles." | How Esign Comply covers it |
13 Processor terms, retention, erasure and transfersA processor works under a contract that meets Article 28. Identifiable data is kept no longer than necessary and erased when the law requires it. A transfer outside the EU needs a basis under Chapter V.GDPR Arts. 28, 32 to 36GDPR Arts. 5, 17 to 18GDPR Arts. 44 to 46 | Implementation task Accept the Data Processing Agreement once, at sign-up. Set a retention period for each class of data, and handle erasure requests for the copies in your own database. | How Esign Comply covers it Live keys are issued once the Data Processing Agreement is accepted. You choose the US or EU data region when you register your domain, and the subprocessor list names each vendor and its regions. |
The whole eIDAS 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.
| Requirement | Source | Covered by |
|---|---|---|
| Signature and evidence | ||
| 01An explicit act of signing | eIDAS Art. 3(9) to (12), 25; French Civil Code Art. 1367 | EU-01, CR-01 (Block rule) |
| 02One frozen version of the document | eIDAS Art. 3(10) | EU-01 (Block rule) |
| 03The record states its level and how the signer was tied to the act | eIDAS Arts. 3, 25, 26; Golden Ocean v Salgaocar | EU-02, EU-03, EU-04, CR-17 (Esign Comply does this + Block rule) |
| 04An outside timestamp, a provider seal and evidence that verifies later | eIDAS Arts. 32 to 42; Implementing Regulation 2025/1929; Implementing Regulation 2025/1946; RFC 3161 | EU-05, EU-06, EU-07 (Esign Comply does this) |
| National form rules | ||
| 05Jurisdiction, signer and document type are confirmed | eIDAS Art. 2(3); E-Commerce Directive Art. 9; BGB § 623; Italy: CAD Art. 21; Spanish Civil Code Arts. 1278 to 1280; Ireland: Electronic Commerce Act 2000; French Civil Code Art. 1175; BGB § 311b | EU-08, CR-18 (Block rule) |
| 06United Kingdom: deeds | Law of Property (Miscellaneous Provisions) Act 1989, s.1; Companies Act 2006, s.44; Law Commission report | EU-20 (Block rule + You build this) |
| 07Switzerland: statutory written form | Swiss Code of Obligations Arts. 11, 14 and 216; Swiss Federal Office of Communications | EU-20 (Block rule) |
| Contracts concluded online | ||
| 08Terms the customer can keep, and a way to fix mistakes | E-Commerce Directive Arts. 10 to 11; Unfair Contract Terms Directive Arts. 3, 5, 6 | EU-09, CR-13, CR-14 (Block rule + You build this) |
| 09The order button says the order costs money | Consumer Rights Directive Art. 8(2); Directive 2024/825; Fuhrmann-2, C-249/21; Conny, C-400/22 | EU-10, CR-11 (Block rule + You build this) |
| 10Durable confirmation and an online withdrawal function | Consumer Rights Directive Arts. 8(7), 11a; Directive 2023/2673; Content Services, C-49/11; BAWAG, C-375/15; German BGB § 356a | EU-11, EU-12 (You build this) |
| 11Offered languages and plain wording | E-Commerce Directive Art. 10(1)(d); Unfair Contract Terms Directive Art. 5; Consumer Rights Directive Art. 6(7) | EU-13, CR-15 (Warn rule + You build this) |
| Personal data in the evidence | ||
| 12Minimal capture and privacy information | GDPR Arts. 5, 6, 25; GDPR Arts. 7, 13 to 14; ePrivacy Directive Art. 5(3) | EU-14, EU-15 (Esign Comply does this + You build this) |
| 13Processor terms, retention, erasure and transfers | GDPR Arts. 28, 32 to 36; GDPR Arts. 5, 17 to 18; GDPR Arts. 44 to 46 | EU-16, EU-17, EU-18 (Esign Comply does this + You build this) |
Where the UK and Swiss rule packs differ from the EU pack
Three separate packs, selected by the signer's country. The record, the timestamp, the seal and the evidence package are the same in all three.
| Part of the checklist | EU pack | UK pack | Swiss pack |
|---|---|---|---|
| Applies to | Signers in EU and EEA countries. | Signers in the United Kingdom, under the UK's own domestic eIDAS. | Signers in Switzerland, under Swiss law. |
| Signature and evidence, items 1 to 4 | All four. | All four. | The explicit act, the frozen version and the signature level. |
| National form rules, items 5 to 7 | Germany, Italy, Spain, Ireland, family-law documents and public deeds. | Deeds in England and Wales. | Statutory written-form contracts and public deeds. |
| Online contract rules, items 8 to 11 | All four. | All four, applied with the UK Consumer Contracts Regulations, without the online withdrawal function. | Not part of the Swiss pack. |
| Personal data, items 12 and 13 | Both. | Both. | Both. |
Enable the packs you need on a profile and send the signer's country with every session. The session tells you which pack applied, the steps your page has to complete and the wording it has to render. Read them at run time.
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. Pick the EU, the UK or Switzerland as the region and the prompt carries these rules.
const { data: session, error } = await esc.sessions.create( { profile: "prof_nda_9c2e", // packs enabled: EU, UK, CH signer: { external_id: user.id, email: user.email, class: "business", country: "DE", // from your form, never from an IP address }, documents: [{ document: "doc_Nd55", version: "current" }], context: { url: "http://localhost:3000/sign/nda", locale: "de-DE", purpose: "nda", facts: { document_category: "nda", offered_languages: ["de", "en"], }, }, }, { idempotencyKey: `nda-${user.id}` }, ); if (error) throw new Error(`${error.code}: ${error.message}`); session.applied_jurisdictions; // [{ code: "EU", version: "2026-11-21", reason: "signer_region" }] session.minimal_capture; // true session.required_steps; // the steps your page has to complete session.required_strings; // wording to render: slot, text, translations
Related articles and checklists
- Article7 things your AI coding tool gets wrong about e-signaturesPre-checked boxes, notices that name nothing, links to terms that change, and four more. Each one as code, with the fix.Read it
- ArticleHow to store terms of service acceptanceThe Postgres schema, the insert and the query for who has not accepted the current version. Then what that table cannot show anyone else.Read it
- ArticleClickwrap vs browsewrap vs sign-in wrapThe three patterns with a code example of each, how courts have treated them, and which one to build.Read it
- ChecklistESIGN Act and UETA checklist for developersEach U.S. requirement with its source, the implementation task, and the rule or SDK step that covers it.Read it
Questions about eIDAS and simple electronic signatures
Is a simple electronic signature legally valid in the EU?
Yes. Under Article 25(1) of the eIDAS Regulation an electronic signature cannot be denied legal effect or admissibility as evidence solely because it is electronic. Its weight rests on the evidence around it: an explicit act by the signer, the exact document, and an independent record of both.
What is a simple electronic signature under eIDAS?
Data in electronic form, attached to or logically associated with other electronic data, which the signatory uses to sign. A ticked box with a signing button, a typed name or a passkey confirmation fits that definition. No certificate or special device is part of it. Esign Comply records this level and marks each record signature_level: simple.
What are simple electronic signatures used for?
Agreements the parties can make in any form: terms of service and clickwrap acceptance, NDAs, contractor and commercial agreements, order forms, consent forms and policy acknowledgments. A document with a national form rule, such as a German employment termination or a deed in England and Wales, follows that rule, and the API blocks it when the session is created.
Every blocked document typeDoes eIDAS apply in the UK and Switzerland?
No. The UK has its own domestic version of eIDAS and its own consumer contract regulations. Switzerland has its own signature act, ZertES, and its Code of Obligations. Esign Comply has a separate rule pack for each. The UK pack blocks deeds, and the Swiss pack blocks contracts with a statutory written-form requirement.
What does an EU consumer checkout need beyond the signature?
Five things: terms the consumer can save or print before agreeing, a way to correct input errors before ordering, a final button labelled "Order with obligation to pay" or a clear local equivalent, a confirmation of the contract on a durable medium such as email, and an online withdrawal function for contracts concluded from 19 June 2026.
The EU, UK and Swiss rule packsBuild the signing flow for European signers. Leave the record to us.
Free plan: 10 live signatures a month and a full test mode. No card required.