Skip to content
QUALIFIED TRUST SERVICES

Legally compliant digital signatures (eIDAS) to drive forward the digitalization of your business processes.

CORPORATE TRUST SERVICES

Cryptography-based trust services
to protect your digital identities,
data and business secrets.

Qualified electronic signature products based on eIDAS - legally binding and secure.

API GUIDE

Upgrade your application with electronic signatures by primesign.





DOCUMENT SIGNING API

Signing of PDF documents. primesign handles document processing and adds a visual signature stamp.

HASH SIGNING API

Signing of hash values. Your application handles document processing and provides the document viewer.

CASH BOX API

RKSV-compliant JWS- or raw signatures for cash box receipts.





primesign TRUST CENTER

All documents for our qualified trust services, certificate revocation list, root-/CA- certificates, etc.

RESOURCES

Fact sheets, product documentation and more.



BLOG

Insights on digital signatures, eIDAS and trust services.

BG_ICON_ARROW_3-1
Back to all questions

How do signature workflows with multiple signatories work?

A signature workflow controls who signs a document, in what order and at which signature level. Serial workflows route the document from one signatory to the next, for example when an approval must precede a signature. Parallel workflows deliver it to everyone at once and cut turnaround substantially.

Both patterns can be stored in templates rather than defined for each transaction. On a contract with five parties of equal standing, parallel routing can shorten turnaround from weeks to hours.

Here's how a robust signature workflow is built:

  • Template-driven control: Sequence, signatory group and signature level are fixed per document type rather than decided case by case.
  • Serial routing: Required when one signature depends substantively on another — for example a four-eyes approval before a managing director signs.
  • Parallel routing: The right choice for parties of equal standing; everyone receives the document simultaneously.
  • Dynamic form fields: Fields are completed before signing, so data capture and signature happen in a single operation.
  • Delegation and escalation: Stored delegation rules or automatic escalation apply during absences so processes do not stall.
  • Selective signatures: Where only certain pages or sections require a signature, it is applied precisely there.

What a workflow must deliver for evidence:

  • Complete logging: Every step — dispatch, opening, signature, rejection — is documented with a timestamp.
  • Traceable authorisation: It must be demonstrable who was permitted to sign which document at which level.
  • Immutability: Once complete, the transaction must not be alterable; the PAdES signature secures this technically.

primesign ENTERPRISE provides fully configurable signature workflows with serial and parallel routing, multi-party support, powerful templates and comprehensive form support. Where no workflow engine is required, the primesign SIGNATURE SERVER is sufficient as a lean signing hub for API-triggered signatures.

Benefits

  • Dramatically shorter turnaround on multi-party contracts
  • No lost transactions thanks to delegation and escalation
  • Signature level per document type technically enforced
  • Data capture and signature in a single operation
  • A complete evidence chain for audits and disputes

Still have questions?

See your workflows demonstrated live.

Talk to an expert