> For the complete documentation index, see [llms.txt](https://docs.inji.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inji.io/inji-verify/functional-overview/end-user-guide/credential-display-capabilties.md).

# Credential Display Capabilties

## Overview

This guide covers how Inji Verify displays verification results and renders credentials after validation. Understanding these display capabilities helps verifiers quickly interpret credential status, view issuer-branded presentations, and access multilingual claim values.

Inji Verify provides clear visual indicators for credential validity, supports SVG-based rendering to preserve issuer branding, and enables multilingual display for global accessibility.

### Valid Credentials

* These credentials are currently active and verified using the Inji Verify Portal.

<figure><img src="https://3039626265-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaY8BQ4hdzhSchZV814Ev%2Fuploads%2Fgit-blob-48e916dd993fdc331ac64b3a4f4ce0fc3f8ac1fb%2Fimage14.png?alt=media" alt=""><figcaption></figcaption></figure>

### Invalid Credentials

* These credentials are currently active but invalid.

<figure><img src="https://3039626265-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaY8BQ4hdzhSchZV814Ev%2Fuploads%2Fgit-blob-6e57d78a9e12fdb66c488848f3024f4f6c5dc07b%2Fimage39.png?alt=media" alt=""><figcaption></figcaption></figure>

### Expired Credentials

* These credentials have passed their validity period and are no longer active.

<figure><img src="https://3039626265-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaY8BQ4hdzhSchZV814Ev%2Fuploads%2Fgit-blob-630c1396fe1e9ec9eb0ed0c6f8191f219624ab0d%2Fimage40.png?alt=media" alt=""><figcaption></figcaption></figure>

### Revoked Credentials

Inji Verify can now detect “Revoked” credentials if it is invalidated by the issuer. It ensures that verifiers can always check the latest credential status and helps maintain the integrity and trustworthiness of the verification process.

<figure><img src="https://3039626265-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaY8BQ4hdzhSchZV814Ev%2Fuploads%2Fgit-blob-d889c53e9213c7aa44c1ba62109a494515b767ab%2Fiv-0160-revokedvc-1.png?alt=media" alt=""><figcaption></figcaption></figure>

### SVG Credential Rendering

This feature enables the rendering of Verifiable Credentials in Scalable Vector Graphics (SVG) format, preserving the original design, layout, and branding of the credential. As a result, the displayed credential closely matches the issuer’s intended visual presentation, ensuring both authenticity and aesthetic consistency.

<figure><img src="https://3039626265-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaY8BQ4hdzhSchZV814Ev%2Fuploads%2Fgit-blob-b295a98ea0e55b835c3a5ba22269e13bb605a30f%2Fiv-0160-svg-credential-1.png?alt=media" alt=""><figcaption></figcaption></figure>

### Multilingual Credentials

VCs can now display claims in multiple languages. It allows issuers to include localized claim values, enabling verifiers and holders to view credentials in their preferred language, thereby improving accessibility and inclusivity across different regions and user groups.

<figure><img src="https://3039626265-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaY8BQ4hdzhSchZV814Ev%2Fuploads%2Fgit-blob-b14a4c175deae06378ce2689dfba72c2ff3d9e16%2Fiv-0160-multilingual-vc-rendering-1.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.inji.io/inji-verify/functional-overview/end-user-guide/credential-display-capabilties.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.