Qualified Electronic Signature (QES)

1. The signatory must be identified via a qualified certificate from an EU-trusted service provider 2. The signature must be created using a qualified signature creation device (QSCD) 3. The trust service provider must be on the EU Trusted List

QES is the only type of e-signature that automatically has the legal effect of a handwritten signature across all EU member states (eIDAS Article 25.2). SES and AES can be challenged in court; QES cannot.

Most business contracts do NOT require QES. It is typically needed for: - Real estate transactions in some EU countries (e.g., Austria, Belgium) - Certain government filings and public procurement - Regulated financial documents and insurance contracts - Pharmaceutical and healthcare compliance - Fixed-term employment contracts in some member states

**The three tiers compared**

• **SES (Simple Electronic Signature):** Any electronic indication of intent — a typed name, a checkbox, an email confirmation. No specific security requirements. Sufficient for 95%+ of business contracts.

• **AES (Advanced Electronic Signature):** Uniquely linked to the signer, created under their sole control, with tamper detection. Uses cryptographic keys but doesn't require a qualified certificate.

• **QES (Qualified Electronic Signature):** An AES created by a qualified device with a qualified certificate from a trusted provider. The gold standard — legally equivalent to a handwritten signature in all 27 EU member states without any additional proof required.

**How to obtain a QES**

To create a QES, a signatory must go through identity verification with a Trust Service Provider (TSP) listed on the EU Trusted List. This typically involves video identification or in-person verification. Providers like eID Easy connect to 80+ TSPs across Europe to facilitate this process.

**Do you need QES?**

For most developers building commercial applications — SaaS platforms, marketplaces, freelance tools, AI agents — standard electronic signatures (SES) are legally sufficient under both eIDAS and the ESIGN Act. QES adds friction (identity verification) that breaks autonomous workflows. Consider QES only if your specific use case legally requires it.

eID Easy is currently the only MCP-enabled signing provider that supports QES.