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

Open Checkout Mandate

by FIDO Alliance

Agreement between a user and an agent (or chain of agents) to authorize future checkout actions.

Authority
FIDO Alliance
Subject type
Person
VC format
sd_jwt_vc
Version
1.0
Native identifier
mandate.checkout.open.1
Last updated

Tags

  • agentic ai
  • ecommerce
  • AP2
  • UPC

Sectors

  • finance
  • retail
  • digital

Themes

  • payments
  • agentic_ai

Ecosystems

  • eudi_wallet

Attributes

  • vct string (required) — Verifiable Credential Type claim as defined in SD-JWT. MUST be 'mandate.checkout.open'.
  • constraints array (required) — Array of constraints that the future checkout action must abide by.
  • constraints/item/type string (required) — Constraint type identifier.
  • constraints/item/allowed array (required) — Array of allowed Merchant objects.
  • constraints/item/allowed/item/id string (required) — Unique identifier for the merchant.
  • constraints/item/allowed/item/name string (required) — Human-readable name of the merchant.
  • constraints/item/allowed/item/website string — Website belonging to the merchant.
  • constraints/item/items array (required) — Array of line item requirements.
  • constraints/item/items/item/id string (required) — Identifier for the line item requirement.
  • constraints/item/items/item/acceptable_items array (required) — Defines a set of line items that are acceptable for this line item requirement. One and only one must be present in the Checkout Mandate.
  • constraints/item/items/item/acceptable_items/item/id string (required) — Unique identifier for the line item. Will often be the SKU.
  • constraints/item/items/item/acceptable_items/item/title string (required) — Title of the item.
  • constraints/item/items/item/quantity integer (required) — Required quantity of matching items.
  • cnf object (required) — Confirmation claim defined in RFC 7800 section 3.1. Used for key binding.
  • iat integer — The creation timestamp as a Unix epoch.
  • exp integer — The expiration timestamp as a Unix epoch.

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.