Enforcing an Ecosystem as a Verifier

This page explains how to enforce ecosystem constraints — such as those required by EUDI — during verification. Once an ecosystem is enforced, Procivis One automatically validates each proof request and its results against that ecosystem's requirements, and rejects anything that does not comply.

Prerequisites

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

Enforcing an ecosystem

To enforce an ecosystem on any given verification, use ecosystem during creation of a proof request.

POST /api/proof-request/v1

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

A successful call returns 201. The ecosystem will be enforced during the creation and processing of this proof request.

Requiring ecosystem enforcement

Any ecosystem selected for a verifying organization is available for use in verification, but its use is optional. To require every proof request to use an ecosystem, update the verifying organization:

PATCH /api/organisations/v1/{id}

{
  "configuration": {
    "enforceEcosystemAsVerifier": true
  }
}

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

Related

• Ecosystem Enforcement Reference for Verifiers