Credential Types
The FIDES Credential Catalog is being updated to align with TS11, the EUDI Wallet specification for catalogues of attributes and attestations.
Approved Supplier
by WE BUILD Consortium
Schema for the Approved Supplier Attestation encoded as SD-JWT VC, based on the WE BUILD Attestation Rulebook for attestations of type Approved Supplier (Use Case SC5, eInvoicing) and draft-ietf-oauth-sd-jwt-vc
Tags
- webuild
- einvoicing
- peppol
- sc5
Sectors
- trade
- supply_chain
- digital
Themes
- trade_documents
- organizational_identity
Ecosystems
- eudi_wallet
Attributes
-
vct
string(required) — Verifiable Credential Type — uniquely identifies the credential type. Always present in plain text. NOT selectively disclosable. -
iss
string(required) — Issuer identifier — a URI identifying the issuer of the credential (the Buyer's issuing system / EBW). As per RFC 7519. NOT selectively disclosable. -
iat
integer(required) — Issued At — Unix timestamp (seconds since epoch) indicating when the attestation was issued. NOT selectively disclosable. -
exp
integer(required) — Expiration Time — Unix timestamp after which the attestation is no longer valid. NOT selectively disclosable. -
nbf
integer— Not Before — Unix timestamp before which the credential MUST NOT be accepted. Optional. NOT selectively disclosable. -
sub
string— Subject — identifier for the subject of the credential (the approved Supplier legal entity). Optional. NOT selectively disclosable. -
attestation_legal_category
string(required) — Legal category of this attestation under eIDAS 2. For the Approved Supplier attestation this SHALL be 'EAA' (self-issued by the Buyer). NOT selectively disclosable. -
schema_version
string— Version of the Approved Supplier attestation schema used. Optional metadata. -
trust_anchor_url
string— URL at which a machine-readable version of the trust anchor used for verifying the attestation can be found or looked up. Optional metadata; for this EAA, trust is anchored in the issuer's EBWOID per Chapter 5 of the Rulebook. -
cryptographically_bound_to
string— vct of the attestation on the same Wallet Unit to which this attestation is cryptographically bound (the Supplier's EBWOID). RECOMMENDED per ARB_28. NOT selectively disclosable. -
approving_party
object(required) — The Buyer (Peppol corner C4) issuing the approval. Mandatory. MAY be selectively disclosable. -
approving_party/legal_name
string(required) — Registered legal name of the Buyer. -
approving_party/legal_id
string(required) — Unique legal-person identifier (EUID) of the Buyer, sourced from the Buyer's EBWOID. -
approving_party/peppol_id
string(required) — Peppol participant identifier of the Buyer (scheme:value, e.g. '0009:FR59120680088'). -
approved_supplier
object(required) — The Supplier (Peppol corner C1) being approved — the holder/subject. Mandatory. MAY be selectively disclosable. -
approved_supplier/legal_name
string(required) — Registered legal name of the approved Supplier. -
approved_supplier/legal_id
string(required) — Unique legal-person identifier (EUID) of the Supplier, sourced from the Supplier's EBWOID. -
approved_supplier/peppol_id
string(required) — Peppol participant identifier of the Supplier (scheme:value). -
approval_scope
string(required) — Scope of the approval per the code list in Section 2.8 of the Rulebook. Mandatory. MAY be selectively disclosable. -
approval_valid_from
string(required) — Date from which the approval is valid (RFC 3339 full-date). SHALL NOT be later than approval_valid_until when present. Mandatory. MAY be selectively disclosable. -
approval_valid_until
string— Date until which the approval is valid (business validity, distinct from the technical exp claim). Optional. MAY be selectively disclosable. -
approval_reference
string— Buyer-internal reference for the underlying commercial relationship (e.g. framework agreement number). Optional. MUST be selectively disclosable (SD claim). -
status
object(required) — Status object per SD-JWT VC status-list mechanism. MUST be present when validity period is greater than 24 hours. -
status/type
string(required) — Status mechanism type. For SD-JWT VC Status List this SHALL be 'status-list'. -
status/status_list_credential
string(required) — URI of the Status List Credential that contains the bitstring indicating revocation status. -
status/status_list_index
integer(required) — Zero-based index into the status list bitstring for this credential. -
status/status_purpose
string(required) — Purpose of the status entry. For the Approved Supplier attestation this SHALL be 'revocation'. -
cnf
object(required) — Confirmation claims per SD-JWT VC. Holder binding via JWK to the Supplier's EBW is recommended. -
cnf/jwk
object(required) — Public key bound to the holder. -
cnf/jwk/kty
string -
cnf/jwk/crv
string -
cnf/jwk/x
string -
cnf/jwk/y
string -
cnf/jwk/n
string -
cnf/jwk/e
string
Related listings
-
Aadhaar Verifiable Credential
UIDAI Aadhaar mDoc schema derived from the ISO 18013-5 Aadhaar mDoc Specs. Schema derived from public UIDAI documentation.
-
Academic Base Credential (ABC)
Basic credential indicating affiliation with an education institution in the Npuls/SURF eduwallet proeftuin. Attributes derived from the…
-
Academic Enrollment Credential (AEC)
Proof of enrollment in an education programme in the Npuls/SURF eduwallet proeftuin. Attributes derived from the issuer OpenID4VCI creden…
-
Student Card Credential (SCC)
-
Study Data Credential (SDC)
-
Exam Enrollment Credential (EEC)
-
Support Credential (SC)
-
Open Badge Credential (OBC)
Help us make the catalog better
The FIDES Credential Catalog aims to provide a clear and up-to-date overview of verifiable credential types. While FIDES Labs BV does not assume responsibility or liability for the completeness, accuracy, or timeliness of the information presented, we have made a best effort to compile a correct and representative overview. The data in this catalog is aggregated from publicly available sources, as well as information published by authorities themselves. Schema owner and authorities can manage and publish their credential types and schema information via a public GitHub repository or through service endpoints referenced in their DID documents. The FIDES catalog aggregates and presents this data. If a schema owner or authority is not yet able to manage a DID document, they may submit a JSON file directly to the credential catalog GitHub repository.
Missing a credential type? Let us know at catalog@fides.community.

