Ecosystem Enforcement
Procivis One separates requirements of regulatory ecosystems — for example, revoking an EU PID when the wallet unit's key attestation has been revoked, or checking that a wallet provider's signing certificate appears on the correct trust list — from the requirements of formats and protocols on their own. This page explains how Procivis One uses "ecosystems" to enable flexible and simple interactions which are trusted according to the rules of their environment.
How it works
During issuance, presentation, and verification, Procivis One automatically and always applies the validation rules of the credential formats and protocols used. However, regulatory ecosystems — such as the EUDI Wallet, swiyu in Switzerland, and mobile driving licenses in the U.S.A. — each require additional constraints on interactions and responsibilities on parties.
To simplify the handling of regulatory constraints, Procivis One uses ecosystems. Ecosystems let you select which regulatory systems your organization is participating in, and then use simple API parameters to apply the relevant constraints in interactions.
When an ecosystem is used, Procivis One automatically handles all of the complex logic required by the ecosystem and returns a straightforward result — trusted, untrusted, or unable to be determined — instead of requiring you to implement that logic yourself.
Constraints provided by ecosystems
In addition to validations performed during interactions, ecosystems also handle other regulatory-specific demands such as lifecycle responses to events. For the complete reference of constraints and functions provided by ecosystems, see the Ecosystem Enforcement Reference for:
Enabling and sharing ecosystems
Ecosystems are enabled per organization. See Enabling Ecosystems for instructions.
Providers of managed instances of wallets and verifiers additionally control which ecosystems are available to those instances. Each managed instance then selects which of the available ecosystems to use for itself, using the same mechanism. Once selected, trust list subscriptions and credential schemas associated with that ecosystem are automatically synced from the provider to the instance. See Enforcing an Ecosystem as a Provider for details.