Signing workflows for regulated product

Build workflows where people, organizations, documents, and external systems need to sign, identify, verify, or exchange trust through qualified infrastructure.

XML

DOC

PDF

Mario Irung

Customer

Workflows

Sign with a person: Send documents for secure electronic signature between individual participants.
Identify a person: Run identity checks to confirm who is signing before approvals move forward.
Sign or seal as an organization: Apply company-level signatures or seals for formal organizational authorization.
Verify signed results: Validate signed outputs and ensure document integrity after execution.
Prove trust to another party: Share verifiable trust evidence with partners, customers, and auditors.
Trigger workflow events: Start downstream actions automatically when signing or verification milestones are reached.
Connect regulated systems: Integrate with compliance-critical platforms while preserving secure workflow controls.

Sign documents with real users

Let users sign documents, XML payloads, and regulated submissions through the correct signing path for their environment.

The platform routes the signing request across local devices, remote qualified infrastructure, or wallet-based flows while maintaining one integration model.

What this workflow supports

PDF signing (PAdES)
XML signing (XMLDSig, XAdES variants)
Structured payload signing for regulated systems
Local signing via QSCD devices (tokens, smart cards)
Remote QES signing via HSM-backed infrastructure
Wallet-based signing where supported

Behind the scenes

device detection and routing
desktop bridge communication
provider-specific signing execution
certificate validation and optional timestamping
unified signed response returned to your system

Local device context. Devices like SafeNet eToken 5110 or IDPrime 940 smart cards are commonly used in these flows.

Identify users through qualified identity

Use certificate-based identity, provider flows, or wallet-based identity journeys to confirm who the user is before allowing a regulated action.

What this workflow supports

identity checks before signing
onboarding flows tied to certificates
signer lookup and authorization
certificate-based authentication
wallet-based identity (EUDI-ready)

Behind the scenes

certificate extraction and validation
QTSP-backed identity verification
challenge-response authentication flows
mapping identity to your system

Sign as a company or system

Support organization-level signing and sealing flows where the signing authority belongs to the business, not an individual user.

What this workflow supports

invoices and financial documents
declarations and submissions
automated document signing
qualified electronic seals
system-originated workflows

Behind the scenes

HSM-based signing infrastructure
remote QSCD execution
policy-driven signing rules
audit traceability

Remote signing context. Remote signing relies on certified HSMs acting as QSCDs under eIDAS.

Verify signatures and trust status

Validate that a document, signature, or certificate can be trusted before accepting it into your workflow.

What this workflow supports

signature validation (PDF / XML / CMS)
certificate chain validation
trust list verification (EU Trusted Lists)
timestamp validation
integrity checks

Behind the scenes

certificate status checks (valid / revoked / expired)
trust provider validation
long-term validation support (LTV)
audit-ready verification outputs

Cross-border validation. QES is legally recognized across EU/EEA under eIDAS, enabling cross-border validation.

Prove identity and authorization in real time

Use signer-backed trust flows when your system needs to prove identity or authorization to another system.

What this workflow supports

TLS client authentication with certificates
QES-backed authentication flows
signer-mediated authorization
secure system-to-system communication

Behind the scenes

certificate-based TLS (mTLS) for local devices
challenge-response signing for remote QES
secure transport with identity binding
trust validation across systems

Automate workflows with events and webhooks

React to signing, identity, and device events in real time without polling or manual coordination.

What this workflow supports

signing completed / failed
device connected / disconnected
certificate status changes
identity flow events
system-level diagnostics

Behind the scenes

webhook delivery system
retry handling
event tracking and audit logging
real-time messaging via socket layer

Integrate signing into real-world systems

Connect identity, signing, and verification workflows into regulated environments such as healthcare, government, and enterprise systems.

What this workflow supports

healthcare integrations (HIS.bg, NHIF.bg-style flows)
government portals and submissions
document management systems
enterprise back-office workflows
API + desktop hybrid execution

Behind the scenes

secure tunneling via desktop client
XML-based regulated exchanges
provider-specific integrations
workflow orchestration across systems