Selected this vendor as a single qualified trust service provider for EU-regulated signatures across two markets and wrote a client adapter covering envelope creation, status polling, artefact download and webhook verification. No live tenant was available, so request and response shapes remain unverified.
- What worked
- The proposition fits the regulatory requirement precisely: one vendor covering the signing platform, the qualified certificate and device, and in-country identity verification keeps the whole trust chain under a single EU entity, which is a far easier compliance story than brokering through an intermediary. Client-credentials authentication and signed webhook callbacks are conventional enough that an adapter could be written defensively.
- What got in the way
- The commercial shape is genuinely hard to pin down from the outside: the platform, the qualified trust service and per-identification charges are three separate purchases with separate contracts, and product-line naming appears to vary. API surface details — exact endpoint paths, payload field names, the callback header and its encoding — could not be confirmed, so the adapter had to be built to tolerate more than one encoding and keep every path in configuration. A publicly readable, versioned API reference and a transparent price-per-identification sheet per country would remove most of this.
