eIDAS 2.0 Ready · Launching 2026

Europe's eSignature Hub
for Qualified Signatures

One API connecting your product with every EU qualified signature provider — like Stripe did for payments. Go live in days, cut costs by 70%.

Get free API key → See how it works

eIDAS 2.0 compliant GDPR · EU data residency 99.9% SLA No credit card required

POST /v1/signature-requests ✓ 201 Created

// 1. Create a qualified signature request
const request = await qsignhub.signatureRequests.create({
  document_id: "doc_9Xk3mN7pQr2vT8wL",
  signature_type: "qes",
  signers: [{
    name: "Jan Kowalski",
    email: "jan@firma.pl",
    identity_verification: { method: "mobywatel" }
  }]
});

// 2. Redirect signer — legally binding across the entire EU
→ request.signing_url // "https://sign.qsignhub.io/r/7Yx4k..."
→ request.status     // "pending"
      

Integrated with EU signature providers & used by

🇵🇱 mObywatel

🔐 Profil Zaufany

🏦 KIR / Szafir

🛡️ CERTUM

🇩🇪 BankID DE

🇫🇷 France Connect+

The problem

Every QES integration is
a separate 6-week project

With eIDAS 2.0 coming into force, every EU institution must support compliant signatures — but today, each provider has a completely different API.

❌ Without QSignHub

⏳ Each provider integration takes 6–12 weeks of dev work
💸 3 providers = 3× the cost, 3× the maintenance burden
⚠️ eIDAS 2.0 will break existing integrations — again
🔁 Different APIs, auth methods, certificate formats per country
🧑‍💻 Your engineers maintain non-core PKI infrastructure forever

✅ With QSignHub

⚡ Integrate once — access every EU QES provider via one REST API
📅 Go live in 2–3 days, not months
🇪🇺 Automatic eIDAS 2.0 compliance updates — we handle regulation changes
🔗 PAdES, XAdES, CAdES — all formats supported out of the box
🎯 Your team focuses on product, not infrastructure

How it works

From zero to QES
in three API calls

No PKI knowledge required. No provider contracts to negotiate. Just clean, documented REST endpoints.

Upload your document

Send any PDF, DOCX or XML to our API. We parse, validate and return a document ID.

POST /v1/documents
-F "file=@contract.pdf"

→ "id": "doc_9Xk3mN7..."

Define signers & method

Specify who signs, in what order, and via which EU verification method — mObywatel, video ID, BankID and more.

signature_type: "qes"
method: "mobywatel"
order: "sequential"

Receive the signed PDF

Get notified via webhook when all parties have signed. Download the legally binding QES document with full audit trail.

event: "request.completed"
→ signed_document_url
→ audit_trail_url

Why QSignHub

Built for developers,
trusted by legal teams

70%

Cost reduction

One subscription replaces separate contracts with each QES provider. Predictable pricing, no per-integration fees.

⚡

Days, not months

Average integration time: 2.5 days. Our SDK, docs and onboarding team get you live fast. Sandbox available immediately.

🇪🇺

eIDAS 2.0 auto-compliant

We monitor EU regulation continuously. Your integration stays valid as requirements evolve — zero maintenance from your side.

🔒

Enterprise-grade security

HSM-based signing, PAdES-LTV format, TSA timestamping. Full audit trail with identity verification screenshots per signer.

🔗

Universal provider network

mObywatel, Profil Zaufany, CERTUM, KIR, BankID DE, France Connect+ — all accessed through a single, stable API.

🏛️

Government-ready

Designed for public administration e-services. Citizens sign with their national digital ID — no registration required.

Pricing

Simple, transparent pricing

All plans include eIDAS 2.0 compliance, GDPR DPA, PAdES/XAdES support and EU data residency.

Starter

Free

50 signature requests/month · No credit card

QES, AES & SES support
All identity verification methods
Sandbox environment
API key + full documentation
Email support

Start for free

Trusted by teams
across Europe

We replaced 3 separate QES integrations with QSignHub. Our dev team saved 6 weeks of work and we got a cleaner codebase as a bonus. The webhook system is exactly what we needed.

Michał K.

CTO · LegalTech SaaS · Warsaw

The only API that handles mObywatel AND video ID with a single codebase. We went from "how do we even approach this" to live in production in under a week. Game changer for our e-government project.

Anna W.

IT Director · Municipal Office · Kraków

Integration took 2 days. The audit trail and certificate metadata alone justified switching — our legal team was thrilled. Pricing is a fraction of what we'd pay for separate provider contracts.

Piotr T.

Lead Developer · FinTech · Wrocław

FAQ

Frequently asked questions

What is a qualified electronic signature (QES)?+

A QES is the highest level of electronic signature under the EU eIDAS regulation. It has the same legal effect as a handwritten signature across all EU member states (Art. 25(2) eIDAS). It requires verified identity of the signer, a qualified certificate issued by an EU-trusted provider, and cryptographic signing via a Hardware Security Module (HSM).

How is QSignHub different from DocuSign or Adobe Sign?+

DocuSign and Adobe Sign are end-user signing platforms focused on AES (Advanced) level signatures. QSignHub is a developer-facing API hub that aggregates qualified signature providers — including national systems like mObywatel, Profil Zaufany, and KIR — that DocuSign simply doesn't support. We're infrastructure, they're an app.

Is QSignHub compliant with eIDAS 2.0?+

Yes. eIDAS 2.0 is a core design principle of QSignHub, not an afterthought. As the regulation comes into force, we update our provider integrations and compliance layer automatically — your integration doesn't need to change.

How long does integration take?+

Our average integration time is 2.5 days for a basic setup. We provide SDKs for Node.js, Python, PHP and Java, detailed documentation, a sandbox environment with test data, and an onboarding engineer for Growth and Enterprise customers.

Where is data stored? Is it GDPR compliant?+

All data is stored in EU data centres (Poland / Germany). We offer a Data Processing Agreement (DPA) on all paid plans. Documents are retained for 90 days by default and can be deleted via API at any time. We are fully GDPR compliant and undergo annual security audits.

Can I use QSignHub in a public administration e-service?+

Absolutely — this is one of our primary use cases. Citizens can sign documents using their existing national digital identity (mObywatel, Profil Zaufany) without any registration. We have dedicated support for public institutions and can provide compliance documentation for procurement processes.

Start today — it's free

Ready to add qualified
signatures to your product?

Join the companies already building on QSignHub. Free plan, no credit card, full API access from day one.

Get your free API key → Book a 30-min demo

⚡ Average integration: 2.5 days 💬 Support response: <2h 🇪🇺 EU data residency

Europe's eSignature Hubfor Qualified Signatures

Every QES integration isa separate 6-week project