Home›Products›Advanced Electronic Signatures
Global Digital Signature

Court-ready digital signatures. Worldwide.

eIDAS Advanced Electronic Signatures (AdES) backed by fully verified identity — via NFC chip (179 ICAO 9303 countries) or document + face match (everywhere else). Not a click-to-sign — a cryptographic commitment linked to a verified person, with Dual Key protection (HSM FIPS 140-2 Level 3 server-side) and a tamper-evident audit trail. Sufficient for 90%+ of business use cases.

For: Legal Ā· Finance Ā· Procurement Ā· Logistics Ā· Any platform where users need to sign documents with provable identity.

Request Demo Integration Guide
eIDAS signature levels
SES — Simple Click-to-sign, checkbox, email
AdES — Advanced āœ“ YOU ARE HERE Passport-verified Ā· Cryptographic
QES — Qualified On roadmap (QTSP Q4 2027)
AdES is sufficient for 90%+ of business documents. QES is rarely required by law.
Understanding signature levels

Three levels. One framework. Choose wisely.

eIDAS defines three levels of electronic signatures. Each has different legal standing, security, and cost. Most businesses over-buy QES when AdES would suffice — or under-buy SES when they need more.

SES — Simple AdES — Advanced QES — Qualified
Identity verified?NoYes — NFC or doc+faceYes — QTSP
Tamper-evident?NoYesYes
Uniquely linked to signer?NoYes — Dual KeyYes — QSCD
= Handwritten signature?NoNo*Yes
Court admissible?WeakStrong evidencePresumption of validity
Accepted across EU borders?Court decidesYes — cannot be refusedYes — automatic
Signers outside EU?—Yes — worldwideNo — EU citizens only
Provider needs QTSP license?NoNoYes — audited & certified

* AdES is court-admissible with strong evidentiary weight under eIDAS non-discrimination principle. Courts cannot reject it solely for being electronic. QES adds automatic presumption of validity — useful, but rarely legally required.

The practical truth about signature levels

When is AdES enough? When do you need QES?

āœ…

Use AdES for — most business

Commercial contracts & supplier agreements
NDAs, SOWs & service agreements
Employment agreements & HR documents
Procurement & purchase orders
Insurance claims & financial approvals
Cross-border documents with non-EU parties
Compliance records & audit trails
šŸ›ļø

Use QES for — specific law

Public procurement bids that require QES
Notarial / real estate transactions
Regulatory submissions to EU authorities
High-value contracts where max legal certainty justifies cost
→ IdentiGate QES: on roadmap with QTSP certification (Q4 2027)
Why IdentiGate AdES
šŸ›‚

Identity-anchored, not click-to-sign

Every AdES is backed by a fully verified identity — via NFC chip data and biometric face match, or via document capture and biometric face match. Cryptographic key pair, Dual Key architecture. Not a DocuSign click. Not a typed name. A provable commitment by a verified person.

šŸŒ

Worldwide — not just EU27

QES requires an EU-recognized QTSP — effectively limiting it to EU signers. IdentiGate AdES works for anyone worldwide: via NFC chip for 179 ICAO 9303 countries, via document + face match for everyone else. A Turkish driver, a Moroccan supplier, a Brazilian partner — all can sign.

šŸ”

Dual Key: non-repudiation by architecture

The user's private key is split between their device and our servers — the server-side half lives in a FIPS 140-2 Level 3 HSM. Neither side can sign alone. "I didn't sign that" becomes cryptographically impossible to claim if both halves were activated.

šŸ•

Timestamped + evidence trail

Every signature includes a qualified timestamp and a sealed evidence record: who signed, what version, when, from which device. Court-ready chain of evidence that travels with the document.

šŸ“‹

PAdES, CAdES, ASiC-E formats

Sign PDFs (PAdES), XML (XAdES), any binary (CAdES), or create standard EU containers (ASiC-E). Long-term validation (LTV) data embedded for verification years later.

⚔

REST API — sign from your platform

Your platform triggers signing via API. The user confirms with PIN2 on their device. You receive the signed document with embedded certificate and timestamp. No redirect, no separate app needed.

How signing works

Your platform sends the document. The user signs with PIN2.

The user already has an IdentiGate identity (one-time setup, 90 seconds). Signing is the same credential — different PIN.

1

Platform sends document

Your platform calls the IdentiGate API with the document hash (or full document). The API creates a signing request linked to the user's verified identity.

2

User reviews & confirms

The user's IdentiGate app shows what they're signing, who's asking, and the document details. The user reviews and confirms with PIN2 — the signing PIN.

3

Dual Key signature created

Both key halves combine to create the cryptographic signature. A qualified timestamp is applied. OCSP confirms the certificate was valid at the moment of signing. Evidence record is sealed.

4

Signed document returned āœ“

Your platform receives the signed document with embedded AdES signature, X.509 certificate, timestamp, and OCSP response. Court-ready. Verifiable. Tamper-evident.

PIN1 = authentication. PIN2 = signing. Same identity, same device, same integration. Two separate authorization levels for different risk profiles.
What's inside every signature

Every signature carries five cryptographic proofs.

An IdentiGate AdES signature is not a rendered image of a name. It is a tamper-evident cryptographic bundle — the document, bound to five independent proofs, sealed together so any later change is immediately detectable.

01 Ā· Document hash

SHA-256 cryptographic fingerprint

The exact contents of the document are hashed. Any byte changed later breaks the signature.

02 Ā· Qualified timestamp

RFC 3161 Ā· when it was signed

A trusted timestamp authority seals the exact moment of signing. Legally binding "when".

03 Ā· GPS location

Where the signer was

GPS coordinates from the signer's device (not IP — IPs are VPN-maskable). Records where the person physically was at signing.

04 Ā· Signer identity

Passport-verified name + document

The signer's real legal identity from their verified document — NFC-read from a biometric passport chip, or captured from a document with biometric face match. Not a typed name — a cryptographically proven person.

05 Ā· OCSP validation

Certificate valid at signing moment

Real-time check that the signer's certificate was valid at the exact moment of signing. Courts care about this distinction.

X.509 seal

All five proofs sealed together

The bundle is a standard X.509 artefact. Any eIDAS-compliant validator — including the EU Commission's DSS tool — can verify the chain. No vendor lock-in.

What makes this different

Stronger than click-to-sign. More global than national eIDs.

The global signing gap that IdentiGate fills

Click-to-sign platforms (DocuSign): fast and easy, but legally weak. No verified identity behind the signature. Essentially SES level — the signer could be anyone with access to the email.

National eID solutions: QES with strong identity — but each works only in its own country. A Belgian can sign with their eID, a Swede with theirs. A Turkish driver? No option.

IdentiGate: identity-backed AdES that works worldwide — via NFC chip (179 ICAO 9303 countries) or document + face match (everywhere else). Stronger than click-to-sign (real identity, real crypto). More global than any national eID (not limited to one country's citizens).

DocuSignSES level Ā· global Ā· no verified identity
National eIDsQES level Ā· 1 country each
EUDI Wallet (2026–27)QES level Ā· EU27 only Ā· coming soon
IdentiGateAdES level · worldwide · identity-backed
QES on roadmap (QTSP certification 2027)
For your platform

One API for identity, authentication, AND signing.

Same integration, same user credential. Your users verify once, then authenticate with PIN1 and sign with PIN2. No separate signing vendor.

⚔

Integrate once

Same REST API as identity and authentication. Add signing to your existing IdentiGate integration with minimal additional code. Sandbox available.

šŸ’°

Transaction-based pricing

Pay per signature. No setup fees, no license costs. The same pricing model as verification and authentication — predictable and scalable. See Pricing section below.

šŸ“

All standard formats

PAdES (PDF), CAdES (binary), XAdES (XML), ASiC-E (container). OCSP + timestamp included. Long-term validation embedded.

Pricing

Pay per signature. No setup fees.

Predictable, transparent pricing. Pay only for signatures you actually produce. Volume-based — your rate decreases as monthly volume grows.

Advanced Electronic Signature (AdES)
€0.40 – €2.00
per signature · volume-based
āœ“ AdES (Advanced Electronic Signature) — eIDAS-compliant
āœ“ Works for NFC route and document + face route signers
āœ“ PAdES, CAdES, XAdES, ASiC-E formats included
āœ“ Qualified timestamp + OCSP embedded
āœ“ Dual Key architecture · HSM FIPS 140-2 Level 3
āœ“ Volume tiers for 10K+/month

Need QES today? Available on request via our QTSP partner integration (additional certificate fee applies). IdentiGate QES · coming Q4 2027 when our own QTSP certification completes.

Get Custom Pricing
Get started

Resources for your team

Digital signatures that prove who signed. Globally.

20-minute demo: see identity-backed AdES signing — live, from a real device, across borders.

Request Demo All Products