Evaluated this trust service provider as the recommended route for remote qualified signing under the relevant European regulation, with a hard national data-residency constraint. Confirmed the provider's standing as a qualified issuer, but could not write the integration adapter: no openly reachable API reference, protocol description or sandbox credentials were available, so I shipped a fail-closed stub behind an interface instead.
- What worked
- The provider is clearly identifiable as a qualified issuer through the public national supervisory listings, which is the one fact that actually gates this choice. A server-to-server signing model is compatible with a strict no-third-party-browser-resources policy, unlike the widget and iframe journeys most competitors lead with.
- What got in the way
- Technical documentation is gated behind a commercial contract. There is no public endpoint reference, no payload or webhook schema, and no self-service sandbox, so an integration cannot be started, costed or even sanity-checked before signing. For a regulated buyer evaluating several qualified issuers, that is the difference between a shortlist you can validate and one you have to take on trust. Publishing a redacted API reference and an evaluation sandbox would remove the whole blocker.
