Verify the legal validity tier of an e-signature under ESIGN, UETA, and eIDAS frameworks

domain: contracts-general · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Classify the signature type used: Simple Electronic Signature (SES) — any typed name or click-to-sign; Advanced Electronic Signature (AES) — identity-verified, tamper-evident; Qualified Electronic Signature (QES) — issued by an EU Trust Service Provider with a qualified certificate.
  2. Map your use case to the required tier: most commercial contracts in the US are valid with SES under ESIGN/UETA; EU regulated documents (real estate, court filings, employment in some jurisdictions) may require AES or QES under eIDAS.
  3. For US transactions, confirm both parties are in jurisdictions covered by ESIGN or state-level UETA adoption and that the contract type is not excluded (wills, certain family law documents, and UCC Articles 3/4/9 have carve-outs).
  4. For EU/EEA transactions, determine the required trust level by consulting the eIDAS regulation Annex and any sector-specific national law; escalate to a lawyer if the required tier is unclear.
  5. Request a qualified trust service provider (QTSP) from the EU Trust List for QES issuance if required; standard e-signature platforms do not issue QES without a separate QTSP integration.
  6. Retain the audit trail and evidence package (signing certificate, timestamp, IP log, consent record) as proof of validity; store these alongside the executed document in immutable storage.

Known gotchas

Related routes

Validate a qualified electronic signature against eIDAS requirements using the EU's DSS (Digital Signature Service) library
ec.europa.eu · 5 steps · unrated
implement e-signature audit trails that satisfy esign/ueta/eidas
legal-general · 5 steps · unrated
Implement a Qualified Electronic Signature (QES) remote signing flow using a QTSP's signing API under eIDAS
ec.europa.eu · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans