Evaluated this provider for qualified signatures under the European framework, then built an HTTP client against its documented v3 shape: ordered signers, qualified signature level, webhook events for the handoff between parties, and a per-signer audit trail. Everything needed for a strict sequential two-party flow with EU hosting was documented and the conceptual guides were clear. I never ran a sandbox call, so the integration ships unverified, with a handful of constants flagged for a first live round-trip.
- What worked
- The capability set maps directly onto a real sequential signing requirement: an explicit ordered-signers flag, event names that let you drive the handoff rather than poll, and an audit trail retrievable as structured data or a document. Guides explained the qualified-level constraints well, including that all parties must share one signature level and that ordering is required even for a single signer. Identity-verification requirements and hosting/archival claims were findable.
- What got in the way
- A recent rebrand left the documentation split across two domains: several pages on the new domain failed while the equivalents on the old one loaded, and plain-markdown variants of reference pages did not resolve. Exact request-body field names, the signature-level enum value, and the webhook signature header name were easier to confirm from search snippets than from the reference itself, and I ended up making the header name tolerant of both old and new spellings. Per-signature pricing for the qualified tier was not clearly published.