Use this guide to verify a Verifiable Credential (VC) on the Inji Verify portal.

You can verify a VC from a QR code. You can also request a VP from a wallet. That uses OpenID4VP.

Choose your flow

Start with the UI basics. Then pick the verification method that matches your use case.

Which method should I use?

• Scan QR when you have a visible QR and camera access.

• Upload QR when you have a PDF or image. Use this if scan fails.

• VP verification (cross-device) when the verifier is on desktop. The wallet is on a phone.

If you’re just exploring

Use the collab walkthrough for a safe, ready-to-use environment.

Inji Verify is a verifier portal. It helps you validate verifiable credentials (VCs).

Use this end user guide when you need to check a VC quickly. Use it when you need to request a VP from a wallet.

• Verify by scanning the QR Code

• Verify by uploading the QR Code

Introduction

This guide provides an overview of the Inji Verify user interface based on the reference implementation. It covers the key sections and features available to end users for credential verification workflows.

For hands-on exploration and testing, you can refer to the Inji Verify collab environment.

Header Section

Home

Verify Credentials

• The Verify Credentials Page will showcase two main features of Inji Verify that is "Upload QR Code" and "Scan the QR Code".

Help

The Help section includes three sub-sections or sub-menus:

• Contact Us: This directs you to our MOSIP Community where you can write to us with any queries related to Inji Verify or general inquiries.

• Documentation: This directs you to the Inji Verify documentation page for detailed information about Inji Verify.

• FAQ: This section is still under development.

Language Selection

Language dropdown is provided for verifier to select a language of his interest for better usability . The languages currently supported are: Portuguese, Spanish, French, English, Arabic, Tamil, Khmer, Hindi and Kannada.

Error Handling

Scenario 1: If Pixel Pass encounters difficulties in decoding the data or encounters an unsupported QR code format, Inji Verify returns to the home screen.

• An error message stating "QR code format not supported" is displayed to the user.

Overview

This guide walks you through verifying credentials by scanning QR codes directly using your device's camera. The scan feature provides real-time verification—simply point your camera at a QR code, and Inji Verify decodes the credential data using the PixelPass library and validates it using the Verification SDK. The scanning workflow supports zoom controls for optimal capture accuracy and displays verification results with full credential details upon successful validation.

Overview

This guide covers the same-device Verifiable Presentation (VP) verification flow, where both the verifier portal and credential wallet operate on the same mobile device. Instead of scanning a QR code, Inji Verify invokes the wallet directly via deep link, enabling seamless app-to-app credential sharing without requiring a second device.

This flow follows the OpenID4VP specification with response_mode=direct_post. The wallet receives the authorization request containing credential requirements, authenticates the user, collects consent, and returns the VP response back to Inji Verify for validation and result display.

Step 1: Initiate VP Request Process

Navigate to the VP Verification tab in Inji Verify on your mobile device. Click Request Verifiable Credentials to begin.

Step 2: Select Credential Types

A popup titled Verifiable Credential Selection Panel appears. You can search, sort, and select the required credential types. Some credentials may be pre-selected based on configuration.

Step 3: Open Wallet on Same Device

After selecting credentials, a Wallet Selection Panel appears listing available wallets on your mobile device. Select your preferred wallet. If only one wallet is available, you will be redirected automatically.

Step 4: Deep Link to Wallet

The system invokes your wallet via deep link (e.g., injiwallet://vp-request?...). The wallet receives the authorization request with credential requirements.

Step 5: Wallet Authentication & Consent

The wallet checks which credentials match the request. You are prompted to authenticate and provide consent to share the selected credentials.

Step 6: Wallet Sends VP Response

The wallet prepares the Verifiable Presentation (VP) and returns the vp_token in an authorization response via redirect.

Step 7: View Results in Inji Verify

Inji Verify parses the vp_token, validates claims, and displays the results. Credential status may be Valid, Expired, or Invalid. For multiple VCs, results are shown as expandable cards with tabular view for multi-attribute values. Options are provided to Download JSON or Expand View.

Credential Status Examples

• Invalid VC display: &#xNAN;Shows the credential marked as invalid.

• Expired VC: &#xNAN;Shows the credential marked as expired.

Same Device Flow Scenarios

• Scenario 1: All credentials shared → List of credentials with status.

• Scenario 2: Partial sharing → Display missing credentials with options to Request Missing Credentials or Restart Process.

Overview

This guide explains how to verify credentials by uploading documents containing QR codes when camera scanning isn't available or practical. The upload feature supports PDF, JPEG, JPG, and PNG files, and can process higher-density QR codes (up to version 32) that may exceed camera scanning capability.

Once uploaded, Inji Verify extracts the QR data using the PixelPass library and validates the credential using the Verification SDK, displaying the full credential details upon successful verification.

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.

Overview

This guide covers the cross-device Verifiable Presentation (VP) verification flow, where the verifier and credential holder use separate devices. The verifier generates a QR code containing an authorization request, which the holder scans using their mobile wallet (such as Inji Wallet) on a different device.

This flow follows the OpenID4VP specification and enables secure credential sharing without requiring the verifier and holder to be on the same device. The wallet authenticates the user, collects consent, and sends the VP response back to Inji Verify for validation and result display.

VP Verification (Cross Device Flow)

1. Initiate VP Request Process

• Initiate VP Request Process by clicking on 'Request Verifiable Credentials' to begin the verification process.

1. Select Credentials & Generate QR Code: The verifier is presented with a list of verifiable credential types with specific credentials already pre-selected(configurable) based on a specific usecase.

• Pre-selected credential types are listed on the top and rest of the credentials (non-selected ones) are displayed in alphabetical order.

• The list of VCs can also sorted in ascending or descending order using Sort option.

• Each credential type is displayed with a checkbox next to it.

• Choose the required verifiable credentials from the popup window and click 'Generate QR Code'.

1. Scan QR Code from Mobile wallet (Use a Different Device): Use a wallet containing verifiable credentials on a different device with QR code scanning capabilities to scan the QR code.

Note: The steps that Inji wallet performs to support this interaction are:

• The Wallet interprets the VP request and lists all the matching credentials available in the Wallet.

• The Wallet prompts the user to authenticate and then seeks consent to share the requested credential(s).

• The Wallet sends the VP response via HTTPS POST to the Inji Verify portal.

1. View Verification Results in Inji Verify: Inji Verify displays the verification results of the verifiable credentials shared from the wallet which could be either 'Valid', 'Valid but Expired', 'Invalid'.

• Single VC display

  • Valid VC

• Click on full screen option to view the Verifiable Credentials data as an enlarged view.

• Click on download option to download the VC data as a json file.

• Expired VC

• Invalid VC

• Multiple VCs display

Partial sharing of requested credentials

If not all the requested VCs are shared from wallet, then the status of missing VC result area is displayed as 'Not Shared'

As the verifier is informed of the missing credentials in VC result section, the verifier has to either Generate Request for Missing Credentials or Generate a New Request for restarting the VP sharing flow. The verifier can request for missing credentials by continuing the flow by clicking on 'Request Missing Credentials' to generate another QR code that requests the missing credentials.

Another button - 'Restart Process' helps user to re-initiate the VP Request process all over again (by displaying the popup window to select the credentials and rest of the process continues to be the same), if required.

Re-Generate VP Request for missing VPs

1. Request Missing Credentials: Upon clicking "Request Missing Credentials" button, the Verifier portal automatically identifies the credentials that were not received in the previous transaction. A new Verifiable Presentation (VP) request is generated, containing only the missing credentials.

1. QR Code/Link Display:

• The new VP request is encoded into a QR code.

• The QR code is displayed on the Verifier portal and is ready for the Holder to scan or access.

1. Holder Interaction:

• The Holder (Inji Wallet) scans the new QR code or accesses the link.

• The Wallet fetches the new VP request and lists the pending credentials (if they are available in the Wallet) along with the list of previously verified credentials from our original request.

1. Credential Sharing and Verification:

• The process of selecting credentials, providing user consent, and sending the VP response follows the standard flow.

• The Verifier receives the pending credentials and completes the verification process.

1. Final Verification Completion:

• Once all credentials are received and verified, the Verifier portal displays a final confirmation message indicating that all requested credentials have been successfully verified.

• The process is marked as complete.

Note:

1. For any VCs displayed after verification, the verifier is provided with an option to download the VCs in json format.

2. For any VCs displayed after verification, the verifier is provided with an option to expand the VCs to full view.