Ascaion
Product platform · Services · Digital signature

A signature that stands in court and before authorities.

Qualified electronic signatures under ZertES and eIDAS — through official Swiss CAs and EU / DE QTSPs. Legally equivalent to a handwritten signature, straight from any procedure.

Preferably with pure trust-service providers: the certificate comes to us, the document stays with you.

ZertES
Art. 6 · CH-QES
eIDAS
Annex II · EU-QES
Lists
OFCOM · BNetzA · EU-LOTL
Ruling
Building authority · V-2026-1148
QES · ZertES
Signed · QES
M. Keller
Building authority · head
Hash · 9f3a · cba2
Pending
A. Brun
Building authority · deputy
Hash · -
Qualified certificate QSCD
Holder M. Keller QTSP Swisscom Trust Services List OFCOM · ZertES Valid 09:41 · 18 min
Key at the QTSP · document with you
Signature valid
PAdES-LT · timestamp ok
PREFERRED
Certificate to us
Swisscom Trust Services · SwissSign
Document stays with the customer
ON REQUEST
Platform workflow
Skribble · DocuSign · other QTSPs
Document with the provider
Platform
ONE CASE · ONE AUDIT
Case · identity · audit
Both architectures end up in the same case, the same audit trail, the same permission model. The signed document sits on the record.
Case
Identity
Audit
Two routes, one frame

We fetch the certificate — or send the case to the provider.

We preferably work with pure trust-service providers that deliver the qualified certificate to our application — typical representatives are Swisscom Trust Services and SwissSign. The document stays in your tenant's perimeter; server signing happens on the hash, not on the content.

On request we also integrate platform-based providers — Skribble, DocuSign and other listed QTSPs — where the document is hosted, routed and signed inside the provider's workflow. The same platform, the same case — a different route.

Highlights

Four traits that carry.

Legally binding under ZertES and eIDAS — preferably via the direct certificate route, alternatively via the platform workflow.

01

Qualified — ZertES and eIDAS

Every signature can be issued as a qualified electronic signature (QES) — via an official Swiss CA under ZertES or an EU / DE CA with QTSP status under eIDAS. Legally equivalent to a handwritten signature.

Legal frame
CH
ZertES · Art. 6
OFCOM
QES
EU
eIDAS · Annex II
EU-LOTL · BNetzA
QES
Equivalent to a handwritten signature
02

Certificate to us, document stays with you

We preferably work with interfaces that deliver the qualified signature certificate directly to the application — Swisscom Trust Services and SwissSign for instance — so the document never leaves your tenant's perimeter.

Certificate path
Absidion
→ hash
QTSP
← cert.
ruling.pdf · 312 KB STAYS
Content never at the provider · only the hash
03

Platform workflow, when desired

On customer request we also integrate platform-based trust-service providers like Skribble or DocuSign — with document hosting, reminders, multi-party routing and audit trail at the provider.

Platform workflow 4 steps
01 Start case in Absidion
02 Hand over document to provider
03 Parties sign in the portal
04 Signed original back into file
04

Open to the trust list

One architecture, many providers. Any QTSP on the Bundesnetzagentur trusted list, the EU LOTL or recognised by OFCOM is connectable — the choice is made by the tenant, not the platform.

PROVIDERLISTAPPROACH
Swisscom TS OFCOM Cert.
SwissSign OFCOM Cert.
Skribble OFCOM·EU Platform
DocuSign EU-LOTL Platform
BNetzA on request
Legal frame

ZertES in Switzerland, eIDAS in the EU.

We rely exclusively on certification services that are listed in official registers — either with OFCOM (recognition through KPMG among others) for Switzerland or in the Bundesnetzagentur trusted list or the EU LOTL for the EU area.

CH Switzerland
ZertES

Federal act on certification services in the area of electronic signature

Supervision Recognised certification services · supervision by OFCOM, recognition through KPMG among others QES Art. 6 ZertES · qualified electronic signature
EU EU · DE
eIDAS

Regulation (EU) No 910/2014 on electronic identification and trust services

Supervision EU Trusted List of Trusted Lists · Bundesnetzagentur as national supervision (DE) QES Annex II eIDAS · qualified signature creation device (QSCD)
Providers

We prefer — and integrate everything anyway.

Our preferred choice are trust-service providers that deliver the certificate and leave the document with the customer. Platform-based providers with their own workflow we integrate on tenant request as well — the choice is the tenant's.

01 · PREFERRED OUR DEFAULT

Certificate to us

Pure remote QES providers · server signing under eIDAS Annex II / ZertES Art. 6 — the document does not leave the customer's perimeter.

Swisscom Trust Services Smart Registration Service · All-in Signing Service

Remote QES provider with server signing under ZertES Art. 6 and eIDAS Annex II. Delivers the qualified signature certificate to the application — the original document does not permanently leave the customer's perimeter.

ZertESeIDASServer signing
SwissSign Signing Service API

Swiss QTSP / CA recognised under ZertES. Pure trust service: the certificate is handed to the signing application; the document stays in the tenant's Absidion environment.

ZertESSwitzerlandServer signing
02 · ON REQUEST

Platform workflow

Platform-based trust-service providers with eIDAS QTSP or ZertES status — the document is hosted in the provider's workflow.

Skribble eIDAS- / ZertES-compliant workflow

Platform workflow: the document is hosted at the provider, parties are invited, signing happens in the provider's portal. The end product flows back into the file signed.

ZertESeIDASPlatform workflow
DocuSign CONNECTIVE · EU QTSP backend

Platform workflow with an underlying EU QTSP for QES. Offers routing, reminders and audit trail at the provider; the signed document is replayed into the platform.

eIDASQTSP backendPlatform workflow
Other listed QTSPs on tenant request

Other providers with eIDAS QTSP or ZertES status are connected on tenant request — either directly via trust-service API or via their platform workflow.

EU-LOTLOFCOMBNetzA
Use cases

Where a qualified signature makes the difference.

Rulings, contracts, decisions, applications — wherever written form is required or authenticity must be proven beyond doubt.

01
Ruling to citizen

A ruling is created in the specialised process, signed qualified and delivered via the portal — legally sound and without media breaks.

02
Contract with externals

A contract is signed by multiple parties: internal owners via the direct certificate route, external partners via the platform workflow if needed.

03
Resolution minutes

Meeting minutes and resolutions are signed qualified directly from meeting management by entitled persons.

04
Application from portal

An external person fills in a form in the portal and signs qualified — identity proven via a trust service.

05
HR and personnel document

Employment contracts and personnel decisions are signed qualified — with a clear audit trail in the tenant, not in someone else's inbox.

06
Invoice & dunning

Outbound documents are signed qualified before dispatch — authenticity verifiable at the recipient, without calling us back.

All capabilities

What digital signature delivers in the platform.

Six areas — from signature quality through both architectures, identification and triggering, integration into the platform to the compliance frame.

Signature quality

From simple to qualified — graded per document type, in a consistent frame.

Qualified signature (QES)

Highest level under ZertES Art. 6 and eIDAS Annex II — legally equivalent to a handwritten signature, issued by a recognised QTSP.

Advanced signature (AES)

Person-bound, forgery-proof and tamper-resistant — suitable where there is no statutory written-form requirement.

Simple signature

For internal confirmations and releases, documented in the platform's audit trail.

PAdES compliant

PDF Advanced Electronic Signatures — embedded signature, verifiable in any PAdES-capable reader, with a visible or invisible signature field.

XAdES / CAdES on demand

For XML and container formats, XAdES and CAdES are available as signature formats — depending on tenant requirements.

Long-term validation (LTV)

Embedding of timestamp and revocation information so that the signature remains verifiable after the certificate expires.

Preferred: certificate to us

Pure remote QES providers deliver the certificate — the document stays in the tenant's perimeter.

Server signing per Annex II

The qualified signature creation device (QSCD) lives at the QTSP — the signature is requested by us; the document does not leave our environment.

Swisscom Trust Services

Smart Registration Service and All-in Signing Service — certificate issuance per case, without permanent provider storage of the original.

SwissSign Signing Service

Swiss QTSP / CA recognised under ZertES; the signing application receives the qualified certificate.

Hash-based handover

Only the hash of the document is handed over — the document itself never has to leave the tenant environment.

Tenant account at the QTSP

One account and one contract per tenant at the trust service — no shared provider account, no mixed supervision.

Data-minimal

Content, attachments and metadata do not go to the QTSP — only the hash and the minimum identity data the qualified signature requires.

Also possible: platform workflow

When the tenant expressly requests it — provider portal with document hosting and routing.

Skribble integration

Direct API integration for QES under ZertES and eIDAS — the case is started from Absidion, signing happens in the provider portal, the finished document comes back into the file.

DocuSign / CONNECTIVE

EU QTSP backend for QES; platform workflow with multi-party routing, reminders and compliance reports.

Dispatch & reminders

Invitations, follow-up reminders and status notes run via the provider — traceable in the case's audit trail.

Multi-party routing

Sequential or parallel signing orders, with roles per participant — the case in Absidion follows the status.

Return of the original

Once completed, the signed document is replayed into the tenant and filed on the case — with a validation report.

Clear data processing

Each platform provider has a separate data-processing agreement — also visible in the tenant's data-protection documentation.

Identification & triggering

Who signs is unambiguous — and how it is triggered depends on the use case.

ID via video / on-site

First identification of the signing person per QTSP requirements — video ID, on-site ID or via an accepted eID.

Accepted eIDs

eIDs of listed providers are accepted for the two-factor trigger — e.g. Mobile ID, eID apps and comparable means.

Two-factor per signature

Every single qualified signature is released with a second factor — push confirmation or one-time code, depending on QTSP.

Visible signature block

On request with a visible signature spot in the document — name, role, date, validation status at a glance.

Qualified timestamp

Every signature can carry a qualified timestamp from a recognised TSA provider.

Batch signature

Release multiple documents in one case — one two-factor step per case instead of one per document.

Integrated in the platform

The signature is a platform service — available to every process, every workflow and every form.

Triggerable from any process

Case, contract, meeting, event — wherever a document is created, the signature can be requested directly.

Workflow step

In the workflow designer "sign" is its own step — with participants, order and escalation, identical for both architectures.

Sign form response

A form response can be signed qualified at submission — for applications, declarations, submissions.

Anchored to the case

The signed document hangs on the record — with validation report and audit entry — retrievable exactly where it was created.

Validation in the reader

The platform shows the validation status directly in the reader — certificate, revocation status, timestamp — without switching to another tool.

Search by signature status

Cases can be searched by signature status — open, signed, rejected, expired.

Compliance & operations

Both architectures follow the platform's same security and data-protection frame.

Trusted-list check

When a trust service is configured we check against the EU LOTL, the BNetzA list and OFCOM recognition — no provider without active status.

Data residency Switzerland / EU

Hosting of the platform and routing of signature calls within Switzerland or the EU, depending on tenant — no unintended third-country transfer.

ISO 27001 / 27017 / 27018 / 27701

The platform service runs in the same certified management system as the rest of the Absidion platform.

Key material at the QTSP

Private keys of the signing person live in the QSCD at the QTSP — not at us, not in the browser, not in a file.

Audit trail

Who handed what to signature when, released or rejected — fully in the platform's audit trail.

Retention & export

Signed documents are retained per tenant specification and can be exported with their validation report — also after a provider switch.

Absidion product platform

All processes and services at a glance.

From any Absidion page, navigate to every other process and to the services that work across all of them.

Next step

See Absidion digital signature in action.

A short demo where we're happy to answer your questions in person. No commitment, no sales theatre.

01 Request a demo