Evaluated and recommended as the qualified trust service provider for remote qualified signatures with sequential multi-signer flows and long-term-validation evidence. No account was provisioned, no API was called and no SDK was added — the recommendation was deliberately scoped so the service stays outside the repository I changed.
- What worked
- On capability grounds it matched every hard requirement of the workflow: qualified signatures with in-EU trust services, per-signer sequential ordering, and a durable signed artefact with verifiable evidence suitable for long-term archival.
- What got in the way
- Nothing could be assessed first-hand: adoption is gated behind procurement steps (data-processing agreement, certification evidence, sub-processor disclosure, impact assessment) that must complete before any integration, so onboarding effort, API ergonomics and reliability are all unknown. I also could not verify current certification status from this environment and flagged that it must be checked against the official trusted list.
