Glossary
What is a qualified electronic signature (QES)?
A qualified electronic signature (QES) is the highest eIDAS level, made with a certificate from a QTSP. Learn what it takes and how SignatureAPI supports it.
A qualified electronic signature (QES) is the strongest of the three levels of electronic signature that eIDAS (Regulation (EU) No 910/2014) defines. Under Article 25 of eIDAS, a QES has the same legal effect as a handwritten signature, and a QES based on a qualified certificate from one EU member state is recognized in all of them.
What makes a signature qualified
A QES is an advanced electronic signature with two more ingredients:
- A qualified certificate. A digital certificate issued in the signer’s name by a qualified trust service provider, after it verified the signer’s identity.
- A qualified signature creation device. Certified hardware that holds the signer’s private key. For remote signing, the provider runs the device and the signer authorizes each signature, for example with a one-time code.
What is a QTSP?
A qualified trust service provider (QTSP) is a company that an EU supervisory body has approved to provide qualified trust services, such as verifying identities and issuing qualified certificates. The European Commission publishes every approved provider in the EU Trust List.
The QTSP is the party that makes a signature qualified. A signing platform can’t issue a QES by itself: it works with a QTSP that verifies the signer and holds the key.
When you need one
Usually you don’t. A simple electronic signature covers most business documents. You need a QES when:
- The law asks for it. Some national laws accept only a QES in place of a handwritten signature for certain documents.
- 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.
Qualified signatures in SignatureAPI
Add a qualified signer to an envelope and that recipient signs with a QES. You bring your own QTSP: SignatureAPI talks to it through a signing worker, and you sign the contract with the provider.
- Public beta. Qualified signatures are turned on per account, on request, at no extra charge during the beta. See Request access.
- Test mode. A sandbox signing service stands in for the provider, so you can try the flow before you have a QTSP. Its certificates are not qualified.
- The result. Each qualified signature sits in the deliverable as a PAdES signature, with a trusted timestamp.
Related
- What are qualified signatures?: the full overview.
- How qualified signatures work: what the signer sees and what you get back.
- Are electronic signatures legal?: ESIGN, UETA and eIDAS.
- Glossary: other terms.