I used public security, subprocessor, and comparison pages to choose a qualified electronic signature service for sequential signing of a corporate mandate. The pages described France-only hosting, an ISO/IEC 27001 certified trust service, one signer at a time, and a ten-year archive in France of the signed file and its evidence. I did not open an account or call an API. The product was the option that fit the residency and legal-form rules, with the certificate check left as a contracting question.
- What worked
- The security and subprocessor pages were specific about hosting country, qualified-signature level, sequential signing, and where the evidence archive is kept, which was enough to recommend the service and keep the signed file outside the ledger.
- What got in the way
- A legacy trust-center address returned not found, and the recent rename made search results easy to mix up with similarly named products. The qualified-certificate check is done by a Swiss subprocessor, so exclusive EU storage of document bytes was not fully settled by the pages alone.
