Igrantio Dcql Query Certificate Of Registration

DCQL query: Certificate Of Registration

When to use

Use this template when you must know that a company exists and who it is. The Certificate Of Registration credential is the digital form of the registration extract that a business register issues. The query asks for the registered name, the legal form, the business activity, the registration date, the legal status, the organisation number, and the registered address.

Typical uses are know-your-business (KYB) checks, supplier onboarding, business account opening, and tender or procurement portals.

Ask only for the claims that your check needs. Drop the rest from the query.

Template facts

Registry version: 2025.7.1.

The doctype and the namespace differ for mso_mdoc. The doctype names the document, org.iso.18013.5.1.cor. The namespace groups the data elements, org.iso.18013.5.1.

Claims

Format dc+sd-jwt

{
  "claims": [
    {
      "path": ["name"]
    },
    {
      "path": ["legalForm"]
    },
    {
      "path": ["activity"]
    },
    {
      "path": ["registrationDate"]
    },
    {
      "path": ["legalStatus"]
    },
    {
      "path": ["registeredAddress"]
    },
    {
      "path": ["registeredAddress", "adminUnitLevel1"]
    },
    {
      "path": ["registeredAddress", "fullAddress"]
    },
    {
      "path": ["registeredAddress", "locatorDesignator"]
    },
    {
      "path": ["registeredAddress", "postCode"]
    },
    {
      "path": ["registeredAddress", "postName"]
    },
    {
      "path": ["registeredAddress", "thoroughFare"]
    },
    {
      "path": ["orgNumber"]
    }
  ]
}

Format jwt_vc_json

{
  "claims": [
    {
      "path": ["credentialSubject", "name"]
    },
    {
      "path": ["credentialSubject", "legalForm"]
    },
    {
      "path": ["credentialSubject", "activity"]
    },
    {
      "path": ["credentialSubject", "registrationDate"]
    },
    {
      "path": ["credentialSubject", "legalStatus"]
    },
    {
      "path": ["credentialSubject", "registeredAddress"]
    },
    {
      "path": ["credentialSubject", "registeredAddress", "adminUnitLevel1"]
    },
    {
      "path": ["credentialSubject", "registeredAddress", "fullAddress"]
    },
    {
      "path": ["credentialSubject", "registeredAddress", "locatorDesignator"]
    },
    {
      "path": ["credentialSubject", "registeredAddress", "postCode"]
    },
    {
      "path": ["credentialSubject", "registeredAddress", "postName"]
    },
    {
      "path": ["credentialSubject", "registeredAddress", "thoroughFare"]
    },
    {
      "path": ["credentialSubject", "orgNumber"]
    }
  ]
}

Format mso_mdoc

{
  "claims": [
    {
      "path": ["org.iso.18013.5.1", "name"]
    },
    {
      "path": ["org.iso.18013.5.1", "legalForm"]
    },
    {
      "path": ["org.iso.18013.5.1", "activity"]
    },
    {
      "path": ["org.iso.18013.5.1", "registrationDate"]
    },
    {
      "path": ["org.iso.18013.5.1", "legalStatus"]
    },
    {
      "path": ["org.iso.18013.5.1", "registeredAddress"]
    },
    {
      "path": ["org.iso.18013.5.1", "orgNumber"]
    }
  ]
}

The registry also holds an older mso_mdoc file that names each claim with a namespace and a claim_name pair. It lists the same seven claims. Use the path form above for a version_01 presentation definition.

How to read the path arrays

The path array names one claim, one element per level.

• dc+sd-jwt: the path starts at the top level of the SD-JWT VC payload. ["registeredAddress", "postCode"] reads the postCode member inside the registeredAddress object.
• jwt_vc_json: the path starts with credentialSubject, because a W3C VC keeps the subject claims under that key. Every path is one element longer than the dc+sd-jwt path for the same claim.
• mso_mdoc: the path holds exactly two elements. The first element is the namespace, here org.iso.18013.5.1. The second element is the data element name. An mdoc has no nesting below the data element, so the address arrives as one registeredAddress object. The six single address members that the other two formats list have no mso_mdoc counterpart.

registeredAddress appears twice in the SD-JWT VC and W3C VC lists: once as the whole object, and once per member. Ask for the whole object when you want the full address. Ask for single members when you want less, for example the post code only.

Use with the iGrant.io API

Create a presentation definition with POST /v2/config/digital-wallet/openid/sdjwt/presentation-definition. Put the claims of one format into one entry of dcqlQuery.credentials[]. Give the entry an id, set format, and set meta for that format:

The format gates the meta keys. The server refuses vct_values on jwt_vc_json and refuses anything but doctype_value on mso_mdoc.

Set version to version_01.

{
  "label": "Company registration check",
  "version": "version_01",
  "responseType": "vp_token",
  "responseMode": "direct_post",
  "dcqlQuery": {
    "credentials": [
      {
        "id": "certificate-of-registration",
        "format": "dc+sd-jwt",
        "meta": { "vct_values": ["CertificateOfRegistration"] },
        "claims": [
          { "path": ["name"] },
          { "path": ["legalForm"] },
          { "path": ["legalStatus"] },
          { "path": ["orgNumber"] },
          { "path": ["registeredAddress"] }
        ]
      }
    ]
  }
}

Then send the verification request with the V3 send operation, POST /v3/config/digital-wallet/openid/sdjwt/verification/send, and pass the presentationDefinitionId of the record that you created. Read the disclosed claims from presentation on the verification history record.

The igrantio-api-verifier skill holds the full operation reference: every field of the presentation definition, every transport option, and the shape of the verification history record.

Source is the registry

The iGrant.io verifiable data registry is the source of truth for this template. If this skill and the registry file disagree, the registry wins. Fetch the source directory before you rely on a claim path:

• https://github.com/decentralised-dataexchange/verifiable-data-registry/tree/main/presentationDefinitions/dcqlQuery/certificateOfRegistration
• Raw file: https://raw.githubusercontent.com/decentralised-dataexchange/verifiable-data-registry/main/presentationDefinitions/dcqlQuery/certificateOfRegistration/2025.7.1/dc%2Bsd-jwt.schema.json

Follow the registry and report the drift so this skill can be corrected.