Selecting a signing provider hinges on a “trust model” that answers three questions the workflow demo often hides: who holds or manages the signing key (and how the signer retains sole control), who verified the signer’s identity before certificate issuance, and who is accountable when a signature fails years later. In the EU, these questions are largely determined by whether a qualified trust service provider (QTSP) is involved, because only a qualified electronic signature (QES)—based on a qualified certificate and (for QES) a qualified signature creation device (QSCD)—is guaranteed the legal effect of handwritten equivalence. While organizations buy from signing providers, the decisive structure is transaction-path specific: a provider may be a QTSP for some flows and merely route to partner QTSPs for others.
Four trust models classify transaction paths by the QTSP behind them: integrated trust provider (provider is the QTSP), multi-QTSP orchestrator (routes to multiple partner QTSPs), single-partner qualified path (routes to one partner QTSP), and non-qualified signatures only. Each model has a “test” buyers can validate (e.g., trusted-list status per entity and service). The key tradeoffs include reach versus visibility (especially in orchestration) and dependence on a partner’s status and roadmap.
In the US, there is no qualified tier; ESIGN and UETA prevent denying legal effect solely because a signature is electronic, leaving evidentiary weight to contracts, procedures, and records (plus sector rules like FDA 21 CFR Part 11). Cross-border recognition matters: as of September 2026, no EU-US recognition exists for qualified services, so US organizations still need EU QTSPs for EU-qualified requirements.
From 2026–2028, EU changes culminate on August 19, 2027, when new reference standards apply for remote QSCD management and identity verification. The EUDI Wallet adds a channel, not a new trust model. Long-lived documents introduce post-quantum urgency: after 2030, organizations need retention-driven evidence, preservation, and crypto-agility plans, including migration away from RSA keys under 3000 bits by the end of 2028.
See All Locations
See All Locations