Sign in

Credential Types

The Credential Catalog provides an overview of verifiable credential types that can be used across digital trust use cases.

The Credential Catalog provides an overview of verifiable credential types that can be used across digital trust use cases. Within a use case, a credential type defines what trusted information can be issued, stored in a wallet and presented to a relying party, such as identity data, eligibility, authorization, qualifications, compliance status or membership. The catalog helps organizations discover and reuse existing credential types and schemas, instead of creating proprietary ones, supporting interoperability and reuse.

The FIDES Credential Catalog is being updated to align with TS11, the EUDI Wallet specification for catalogues of attributes and attestations.

ADD
UPDATE
LEARN MORE

Payment Terms

by WE BUILD Consortium

Schema for the SD-JWT VC payload of a Payment Terms Attestation as defined in the Payment Terms Attestation Rulebook (Chapter 3.2).

Authority
WE BUILD Consortium
Subject type
Organization
VC format
sd_jwt_vc
Version
0.1.0
Native identifier
eu.we-build:paymentterms:1
Last updated

Tags

  • webuild
  • payments
  • kys

Sectors

  • finance
  • trade
  • supply_chain

Themes

  • payments
  • trade_documents

Ecosystems

  • eudi_wallet

Attributes

  • vct string (required)
  • iss string (required)
  • iat integer (required)
  • exp integer (required)
  • issuing_entity string
  • issuing_country string
  • attestation_legal_category string (required)
  • schema_version string
  • trust_anchor_url string
  • payment_due string (required)
  • currency string (required)
  • incoterm string (required)
  • buyer_identifier object (required) — Unique identifiers of the buyer party. At least one identifier MUST be present.
  • buyer_identifier/euid string
  • buyer_identifier/lei string
  • buyer_identifier/tax string
  • buyer_identifier/gln string
  • buyer_identifier/duns string
  • buyer_identifier/eori string
  • buyer_identifier/bpnl string
  • buyer_identifier/siren string
  • supplier_identifier object (required) — Unique identifiers of the supplier party. At least one identifier MUST be present.
  • supplier_identifier/euid string
  • supplier_identifier/lei string
  • supplier_identifier/tax string
  • supplier_identifier/gln string
  • supplier_identifier/duns string
  • supplier_identifier/eori string
  • supplier_identifier/bpnl string
  • supplier_identifier/siren string
  • agreement_date string (required)
  • payment_reference_event string
  • contract_reference string
  • transaction_amount number
  • delivery_location string
  • status object
  • status/type string (required)
  • status/status_list_credential string (required)
  • status/status_list_index integer (required)
  • status/status_purpose string (required)
  • cnf object (required)
  • cnf/jwk object (required)

Related listings

  1. Aadhaar Verifiable Credential

    UIDAI Aadhaar mDoc schema derived from the ISO 18013-5 Aadhaar mDoc Specs. Schema derived from public UIDAI documentation.

  2. Academic Base Credential (ABC)

    Basic credential indicating affiliation with an education institution in the Npuls/SURF eduwallet proeftuin. Attributes derived from the…

  3. Academic Enrollment Credential (AEC)

    Proof of enrollment in an education programme in the Npuls/SURF eduwallet proeftuin. Attributes derived from the issuer OpenID4VCI creden…

  4. Student Card Credential (SCC)

  5. Study Data Credential (SDC)

  6. Exam Enrollment Credential (EEC)

  7. Support Credential (SC)

  8. Open Badge Credential (OBC)

View full catalog

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.