Policy
Select provider according to product/policy.
Connect approved providers while preserving certificate context and audit-relevant differences.
Version • signer • authority
Applicable identity and signing service route
Desktop application handoff
Asynchronous transaction integration
Transaction-bound authorization
Signature creation with the applicable key and certificate
Output • state • correlation
Production provider names and support status belong in the Integration Support Matrix.
Select provider according to product/policy.
Common lifecycle for monitoring and reconciliation.
Consistent result/evidence interface above providers.
Multi-CA is valuable when business applications integrate once while provider eligibility, route selection, normalized status and evidence remain policy-controlled. It must not silently switch certificate/provider when that changes assurance or legal context.
Multi-provider orchestration may normalize requests, states and errors for the business application, but it must not erase certificate profile, provider identity, assurance requirements or legal context. If provider A fails, routing to provider B is valid only when policy permits it and the signer has an eligible credential; technical reachability is not proof that a fallback is allowed.
Mobile-ID publishes the module-specific cooperation below. This list does not establish that every CA is connected or available in a particular Sign configuration.
MISA · TMS-RA · Remote Signing
Published cooperationEFY · TMS-RA
Published cooperationHN · TMS-RA
Published cooperationSavis · TMS-RA · CA
Published cooperationMobile-ID published source · Partners and deployment records