#Credential branding

The Community Stack Issuer API lets you control how credentials appear to wallets and users when issued—setting claim labels, issuer logos, descriptions, and background/text colors (and localized variants) so wallets can render a consistent, branded credential. Use issuer-level metadata to keep visuals consistent across a credential type, or embed display data per credential instance when you need finer-grained differentiation (e.g., ticket tiers or program variants).

#What's included

• Issuer metadata for each credential type
  Define colors, logo, description, and display fields once per credential type (e.g. digital diploma) so wallets can render predictable visuals without hard-coding styling.
• Per-credential display overrides
  Embed display attributes in a specific credential instance when variants of the same type need distinct branding (e.g., VIP vs. standard ticket).
• User-friendly display fields
  Provide human-friendly labels, value hints, and ordering for claims so wallets show meaningful attribute names instead of raw keys.
• Localization for labels
  Supply localized display metadata so wallets can show claim labels and descriptions in the user's language.

#Include display metadata at issuance (data function)

You can pull configured display metadata into an issuance request using the display data function in the mapping object of the issuance request. This lets you embed visuals per credential instance without re-specifying them in the payload. Learn more in the data functions documentation.

Note: This is optional, as the wallet could also fetch the display information from the issuer metadata directly. It really depends on the implementation and the wallet you are using.

#FAQs

• Will other wallets show branding reliably? — Issuer metadata follows standardized display conventions, so it's the most interoperable way to share visuals (including localization). Per-credential embedded display data is not yet standardized; the walt.id wallet supports both approaches, but third-party wallets may only honor issuer metadata and ignore in-credential display info until they add support.
• What is a credential type? — A concrete subtype within a credential standard. For example, under W3C VC you might have a digital diploma or digital ID; under ISO mdoc you might have mDL or a photo ID; under SD-JWT VC (IETF) you might have an identity credential. Each type can carry its own display metadata so wallets know how to present it.

#Get Started

• Configure credential display metadata – Define colors, logos, descriptions, and display fields for each credential type in the issuer metadata configuration file.
• Use display data functions – Learn how to embed display metadata dynamically during credential issuance.