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 Payment Mandate

by FIDO Alliance

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

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

Tags

  • agentic ai
  • ecommerce
  • UCP
  • AP2

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.payment.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/frequency string (required) — Frequency of allowed recurrences.
  • constraints/item/max_occurrences integer — Maximum number of allowed occurrences.
  • 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/allowed/item/type string (required) — unique string identifying this category of instrument
  • constraints/item/allowed/item/description string — Description of the instrument to be displayed to the user for informational purposes
  • constraints/item/allowed/item/legal_name string (required) — Legal name of the PISP.
  • constraints/item/allowed/item/brand_name string (required) — Brand name of the PISP.
  • constraints/item/allowed/item/domain_name string (required) — Domain name of the PISP as secured by the [eIDAS] QWAC certificate of the TPP.
  • constraints/item/currency string (required) — ISO4217 Alpha-3 currency code.
  • constraints/item/max integer | number (required) — Maximum allowed amount in minor (cents) unit of currency.
  • constraints/item/min integer — Minimal amount in minor (cents) unit of currency. If absent, there is no minimum.
  • constraints/item/not_before string — Earliest valid execution date.
  • constraints/item/not_after string — Latest valid execution date.
  • constraints/item/conditional_transaction_id string (required) — Digest of the associated Open Checkout Mandate.
  • cnf object (required) — Confirmation claim as defined in RFC 7800 section 3.1. Used for key binding.
  • payee object — The merchant receiving the payment.
  • payee/id string (required) — Unique identifier for the merchant.
  • payee/name string (required) — Human-readable name of the merchant.
  • payee/website string — Website belonging to the merchant.
  • payment_amount object — Transaction amount object containing currency (ISO 4217 code, e.g., "USD") and amount (integer minor units per ISO 4217, e.g., 27999 = $279.99). Pre-set by the user at time of mandate creation.
  • payment_amount/amount integer (required) — Amount in minor units, according to the ISO-4217 spec.
  • payment_amount/currency string (required) — ISO-4217 3-letter alphabetic currency code of the payment.
  • payment_instrument object — The payment instrument used.
  • payment_instrument/id string (required) — unique identifier for this instrument
  • payment_instrument/type string (required) — unique string identifying this category of instrument
  • payment_instrument/description string — Description of the instrument to be displayed to the user for informational purposes
  • pisp object — The Payment Initiation Service Provider.
  • pisp/legal_name string (required) — Legal name of the PISP.
  • pisp/brand_name string (required) — Brand name of the PISP.
  • pisp/domain_name string (required) — Domain name of the PISP as secured by the [eIDAS] QWAC certificate of the TPP.
  • execution_date string — ISO8601 date of execution of payment. When absent indicates immediate execution.
  • risk_data object — An map of relevant risk signals collected by the trusted surface at time of mandate creation.
  • 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.