Advanced Electronic Signature (AES)
An eIDAS signature tier meeting the Article 26 requirements: uniquely linked to the signer, capable of identifying the signer, created using data under the signer's sole control, and linked to the signed data so later changes are detectable. Often backed by a certificate, but a qualified certificate is not required.
Sources: Regulation (EU) No 910/2014 (eIDAS), Art. 26
Appears in: Signature level
Associated Signature Container, Extended (ASiC-E)
An ETSI container format that bundles signed files and their signatures or timestamp tokens into one archive.
Sources: ETSI EN 319 162-1, ASiC containers
Appears in: Signature level
Audit trail
A record of who did what in a signing flow and when. A plain database log may not by itself be sufficient legal evidence.
Appears in: Signature level
Certificate chain validation
Checking that each certificate in a signature's chain is signed by the next, up to a trusted root, and not revoked.
Appears in: Signature level
Cloud Signature Consortium API
A standard API for remote signing, where the provider holds the private key and the application calls it to sign.
Sources: Cloud Signature Consortium API specifications
Appears in: Signature level
Commercial certificate authority
A public CA (such as DigiCert or GlobalSign) whose root is widely trusted by PDF readers, so external recipients can see signatures as valid if the chain and revocation checks pass.
Appears in: Signature level
electronic IDentification, Authentication and trust Services (eIDAS)
The EU regulation that defines electronic, advanced and qualified electronic signatures and the trust services behind them; industry often labels these SES, AES and QES.
Sources: Regulation (EU) No 910/2014 (eIDAS)
Appears in: Signature level
Electronic seal (cachet)
A signature applied by an organisation rather than a person. It proves the organisation's origin and document integrity, not an individual's intent.
Sources: Regulation (EU) No 910/2014 (eIDAS), Art. 35 and 36
Appears in: Signature level
Email deliverability
How reliably signing emails reach external inboxes rather than spam folders. A key concern when signers are outside your organisation.
Appears in: Signature level
Embeddable signing widget
A drop-in signing component (iframe, JavaScript, React, Vue or Angular) that lets signing happen inside your own product.
Appears in: Integration
Griffe
The visible signature appearance or mark a signer places on the document.
Appears in: Signature level
Hash chain
A log where each entry includes the hash of the previous one. Any retroactive edit breaks the chain and becomes detectable.
Appears in: Signature level
Headless API integration
Calling a signing engine purely through its API for cryptographic signing and storage, while you build the entire user interface yourself.
Appears in: Integration
Identity document verification
Checking a signer's ID document and selfie with a provider, to tie the signature to a verified person.
Appears in: Signature level
Intermediate certificate authority
A CA certificate signed by the root CA that issues signing certificates. Sits between the root and the signing certificate.
Appears in: Signature level
OCSP / CRL
Revocation-checking mechanisms. OCSP queries a certificate's status online; a CRL is a signed list of revoked certificates.
Appears in: Signature level
One-time passcode
A short code sent to the signer and valid once. Confirms that the person holding the mailbox, not just a link, is signing.
Appears in: Signature level
Open-source platform
A self-hostable, publicly licensed signing application (such as DocuSeal or Documenso). You run and maintain it, but do not own the signing core.
Appears in: Sourcing model, Platform
PDF Advanced Electronic Signatures
The ETSI standard for PDF Advanced Electronic Signatures; it defines profiles for embedding advanced and qualified electronic signatures in PDF files.
Sources: ETSI EN 319 142-1, PAdES digital signatures
Appears in: Signature level
PDF document timestamp
An RFC 3161 timestamp embedded as a new revision inside a PDF, proving the document existed in a given state at a given time.
Sources: ETSI EN 319 142-1, PAdES digital signatures
Appears in: Signature level
PKCS#7 / CAdES
PKCS#7 and CAdES are standard formats for digital signature data; CAdES is the ETSI variant used in advanced and qualified signatures.
Sources: ETSI EN 319 122-1, CAdES digital signatures · RFC 5652, Cryptographic Message Syntax (CMS)
Public Key Infrastructure (PKI)
The system that issues, stores and revokes digital certificates. Certificates bind a public key to an identity through a chain of trusted CAs.
Appears in: Signature level
Qualified Electronic Signature (QES)
The highest eIDAS signature tier. Legally equivalent to a handwritten signature across the EU. Requires a qualified certificate issued by a Qualified Trust Service Provider and a qualified electronic signature creation device.
Sources: Regulation (EU) No 910/2014 (eIDAS), Art. 25, 28 and 29
Appears in: Signature level
Qualified Trust Service Provider
A trust service provider granted qualified status under eIDAS to issue qualified certificates and provide qualified trust services. Required for QES.
Sources: Regulation (EU) No 910/2014 (eIDAS)
Appears in: Signature level
RFC 3161 trusted timestamp
A standard protocol for a Time-Stamp Authority to certify that data existed at a specific time. It makes 'when was this signed' provable years later.
Sources: RFC 3161, Time-Stamp Protocol (TSP) · ETSI EN 319 422, time-stamping protocol and token profiles · Regulation (EU) No 910/2014 (eIDAS), Art. 41 and 42
Appears in: Signature level
Root certificate authority
The top of a certificate chain. Its certificate is the trust anchor that validators must install or trust for signatures to show as valid.
Appears in: Signature level
Security Information and Event Management
A central system that collects and retains security and audit logs from across your infrastructure.
Appears in: Signature level
Self-generated root
A root CA created by your own deployment rather than a public CA. Validators outside your organisation will not trust it unless you distribute or publish it to them.
Appears in: Signature level
Signer attribution
How strongly a signature is tied to a specific person. Under SES it often rests on email and OTP rather than certificates.
Appears in: Signature level
Simple Electronic Signature (SES)
Commonly called the lowest eIDAS signature tier. An electronic signature with no certificate requirement; often implemented with email verification and an audit log. It can evidence intent and record integrity, but does not by itself provide cryptographic signer identity.
Sources: Regulation (EU) No 910/2014 (eIDAS), Art. 25
Appears in: Signature level
SMTP relay
A mail server that forwards outgoing email. Reusing the corporate one lets signing notifications go out from your own domain.
Appears in: Signature level
Sourcing model
Who owns the signing engine: adopt an open-source platform and host it yourself, or build a custom signing service.
Appears in: Sourcing model
Time-Stamp Authority
A trusted third party that issues RFC 3161 timestamps. Free and paid options exist.
Sources: RFC 3161, Time-Stamp Protocol (TSP) · ETSI EN 319 421, policy and security requirements for time-stamp issuers
Appears in: Signature level
Timestamp response token
A detached file containing an RFC 3161 timestamp for a document. Stored separately from the PDF rather than embedded in it.
Sources: RFC 3161, Time-Stamp Protocol (TSP) · ETSI EN 319 422, time-stamping protocol and token profiles
Appears in: Signature level
Trust anchor
The root certificate a validator trusts as the starting point for checking a signature's certificate chain.
Appears in: Signature level
US ESIGN Act / UETA
The US federal (ESIGN) and state-level (UETA) laws that make electronic signatures generally valid. A simple electronic signature meeting their requirements is usually valid.
Sources: ESIGN Act, 15 U.S.C. chapter 96
Appears in: Signature level
White-label branding
Replacing the platform's logos, colours and product name with your own, so signers see your brand instead of the vendor's.
Appears in: Platform
Write-once, read-many storage
Storage that cannot be modified or deleted for a set period. Used to keep evidence outside the signing platform's trust domain.
Appears in: Signature level
No terms match your search.