Enforcing an Ecosystem as an Issuer

This page explains how to enforce ecosystem constraints — such as those required by EUDI — during credential issuance. Once an ecosystem is enforced, Procivis One automatically validates each credential against that ecosystem's requirements, and prevents issuance that does not comply.

Prerequisites

The issuing organization must have an ecosystem enabled. See Enabling Ecosystems for instructions.

Enforcing an ecosystem

To enforce an ecosystem on any given issuance, use ecosystem during creation of a credential.

POST /api/credential/v1

{
  {{...}}
  "ecosystem": "EUDI"
}

A successful call returns 201. The ecosystem will be enforced during the creation and issuance of this credential.

Requiring ecosystem enforcement

Any ecosystem selected for an issuing organization is available for use in issuance, but its use is optional. To require every issuance to use an ecosystem, update the issuing organization:

PATCH /api/organisations/v1/{id}

{
  "configuration": {
    "enforceEcosystemAsIssuer": true
  }
}

When this flag is set, every credential must have an ecosystem assigned. To force all issuances from this organization to use one and only one ecosystem, make sure that selectedEcosystems only contains one ecosystem.

Related

• Ecosystem Enforcement Reference for Issuers