Skip to main content
Branding works at two levels.

Issuer branding

Your issuer display is the identity holders see attached to every credential you issue: a display name and an optional logo. The didx:me wallet and third-party wallets read it from your published issuer metadata.
logoUrl is restricted to https because the platform fetches it server-side to publish your issuer metadata. The boundary rejects plain http, localhost and other schemes. We download the image and host it ourselves, so the URL you supply only needs to be reachable at the moment you set it. We don’t fetch it again later.

Change your issuer branding

There is currently no self-service endpoint for this. DIDx applies issuer branding during tenant provisioning and changes it on request. To change your display name, logo, or alt text, ask in the DIDx Slack with:
  • your tenant alias,
  • the new displayName, and/or
  • a public https URL for the new logo, plus its alt text.
The change applies to your issuer metadata going forward. Credentials already issued keep the branding they were issued with until the holder’s wallet refreshes them.
A self-service endpoint for issuer branding is on the roadmap. Until it ships, set your display name once, carefully, at onboarding.

Credential card branding

Each credential preset or template can carry a branding block that controls how that credential’s card renders in the wallet. All three are optional. Omit the block entirely and the wallet falls back to its default card styling. The wallet renders the image to fill a 16:9 box, so it crops anything with different proportions rather than scaling it to fit.

When the image is fetched

This differs between presets and templates, and it matters for how long your URL has to stay up.
Credential templates accept the same branding block, whether you define the shape yourself or create the template from a preset. On a template from a preset, branding replaces the preset’s block rather than merging into it, so repeat any value you want to keep.

Colours must be 6-digit hex

backgroundColor and textColor accept #RRGGBB and nothing else. Named colours (red), functional forms (rgb(0,102,204)), and 3- or 8-digit hex all return a 400. This is deliberate rather than an oversight. The wallet derives tinted accents from your colours by appending an alpha byte to the value, which only produces a valid colour when the input is exactly six hex digits.

Branding is fixed at creation

There is no update endpoint for credential presets or credential templates, so the branding you supply at creation is the branding that credential keeps.
  • Presets. Immutable, and you cannot delete them. To change a preset’s branding, publish a new preset (for example acme:membership-v2) and issue against that instead. This also changes the credential type. Types are unique catalogue-wide, so the replacement cannot reuse the old one, and verifiers matching on it stop matching.
  • Templates you own. Whether you defined the shape yourself or created the template from a preset, you can delete and recreate these, so long as you are willing to lose the template id.
  • The platform’s template for a preset. You cannot delete this one. It refuses deletion with a 400, Template '<id>' is managed by a preset and cannot be deleted.
In every case, credentials already issued keep the branding they were issued with. Get the colours right before you issue at volume.
To restyle a preset’s credential, don’t republish the preset. Create a template from it with your own branding and issue from that template. The credential type is unchanged, so verifiers matching on it keep matching, and one preset can back as many differently branded cards as you need.

What the holder sees

Both layers arrive together in the wallet. For each credential a holder opens, the wallet renders: So a well-branded credential needs both: your organisation set up correctly at onboarding, and a branding block on the preset or template you issue from.