---
title: "Credential Branding"
description: "How the Enterprise Issuer lets you present credentials with consistent, configurable visuals."
stack: "Enterprise Stack (commercial) — version 0.21.0"
stack_version: "0.21.0"
stack_comparison: https://docs.walt.id/community-vs-enterprise.md
canonical_url: https://docs.walt.id/enterprise-stack/capabilities/issuer/credential-branding
generated: 2026-07-20
---
# Credential branding

The Enterprise Stack 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.

- **Custom Branding per Tenant**  
  Branding lives in tenant-scoped issuer metadata, so different tenants or issuer services can present the same credential type with their own visuals.

- **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 the configured display metadata of a specific credential type into an issuance request using the `display` data function in the mapping object of the issuance request. This lets you embed visuals, defined at issuer level, per credential instance without re-specifying them in the payload. Learn more [here](https://docs.walt.id/enterprise-stack/services/issuer-service/data-functions.md#display).

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
- **[Set up an issuer service](https://docs.walt.id/enterprise-stack/services/issuer-service/setup.md)** – Learn how to create and configure an issuer service where you can define credential branding.
- **[Configure credential display metadata](https://docs.walt.id/enterprise-stack/services/issuer-service/configurations/openid-metadata/credential-display.md)** – Define colors, logos, descriptions, and display fields for each credential type.
- **[Use display data functions](https://docs.walt.id/enterprise-stack/services/issuer-service/data-functions.md#display)** – Learn how to embed display metadata dynamically during credential issuance.