Truvera Documentation portal
WebsiteTruvera Workspace
  • Truvera overview
    • Decentralized identity explained
    • Roadmap
    • Subscription plans & billing
  • Solutions
    • Biometric-Bound Credentials
  • Truvera Workspace
    • Create an organization profile (DID)
    • Issue verifiable credentials
      • Filtering, downloading and deleting credentials
    • Verify credentials
    • Create a schema
    • Create a design
    • Team management
      • Inviting a team member
      • Removing a team member
      • Changing team member roles
      • Data retention policies
      • Sub-accounts
    • Revoking credentials
    • Ecosystem Tools
      • Ecosystem set up
      • Ecosystem example
    • Monetizing credentials
      • Setting up monetizable credentials
    • Creating API keys and webhook endpoints
    • Transaction history
    • Custom branded distribution emails
    • Truvera Workspace release notes
      • 2025 Release notes
        • Release notes Q1 2025
      • 2024 Release notes
        • Release Notes February 2024
        • Release Notes March 2024
        • Release Notes April 2024
        • Release Notes May 2024
        • Release Notes June 2024
        • Release Notes July 2024
        • Release Notes August 2024
        • Release Notes September 2024
        • Release Notes October 2024
        • Release notes November 2024
        • Release notes December 2024
  • Truvera API
    • Getting started
    • Webhooks
      • Webhooks API endpoints
    • Sample Postman collections
      • Issue-Store-Verify sample flow
      • Create ecosystems
      • Issue monetizable credentials
      • Create sub-accounts
      • Issue OpenID credentials
    • Truvera Swagger UI
    • DIDs
    • Profiles
    • Credentials
    • Presentations
      • Proof templates
      • Proof requests
      • Other proof endpoints
    • Registries
    • Revocation Status
    • Credential Schemas
    • Jobs
    • Templates
    • Sub-accounts
    • Teams
    • Messaging
    • OpenID
      • OpenID Issuance and Verification Integration Guide
    • iden3comm
    • Ecosystem Tools
      • Trust Registry Integration Guide
      • Creating a Trust Registry
      • Inviting participants
      • Verifiers and Public info
      • Trust Registry Schemas
      • Trust Registry Proof Templates
      • Reports
      • Updating and Deleting Trust Registry
    • Issuing paid credentials (KVAC algorithm integration)
    • Data
    • Verify
    • Keys
    • Schemas
  • System architecture
    • Proposed architecture with Truvera
    • Revocation
    • System scalability
    • Security policies
    • How data is processed and stored
  • Supported standards
    • Interoperability with OpenID
  • Credential wallet
    • Create and manage DIDs in the Truvera Wallet
    • White label wallet
      • Configuration
        • Enabling and Disabling Features
        • Customizing the Styling
        • Configuring for Android Builds
        • Configuring iOS Builds
      • Publishing in App Stores
        • Android Build Testing and Publishing
        • iOS Build Testing and Publishing
    • Wallet SDK
      • Getting started
        • Example Credential
        • Presentation definition
        • Verify credentials
      • Cloud wallet
      • Biometric plugin
      • Ecosystem Tools
    • Download Truvera Wallet
    • Truvera Wallet release notes
      • Release Notes 2025Q1
      • Release Notes 2024Q4
      • Release Notes 2024Q3
        • Release Notes September 2024
        • Release Notes August 2024
        • Release Notes July 2024
      • Release Notes June 2024
      • Release Notes May 2024
      • Release Notes April 2024
  • Open source community
    • Code of Conduct
    • Truvera Credential SDK
    • Blockchain archives
      • DOCK token
        • Migration terms and conditions
  • Support
    • System Status
    • Discord
    • Support services
    • Security policy
Powered by GitBook
On this page
  • Steps for the Verifier
  • Steps for the Holder
  • Verification History
  • Wallet-to-Wallet Verification

Was this helpful?

Edit on GitHub
  1. Truvera Workspace

Verify credentials

PreviousFiltering, downloading and deleting credentialsNextCreate a schema

Last updated 2 months ago

Was this helpful?

Verification process

In a typical verification process, there are three main parties:

  1. Issuer: Party that creates and issues a Verifiable Credential to a holder (individual or organization)

  2. Holder: Person or organization that holds the credential (e.g. degree, professional certificate, or identity document)

  3. Verifier: Party that checks that the credential is valid and authentic

Steps for the Verifier

Click on Verification in the left menu and select Create verification template or choose a premade Indentify Verification or Drivers License Verification template.

Add the Template Title and Template Purpose, which the holder will be able to see. Optionally, you can choose a Verifier DID which will be shown to the holder so that they know who is verifying their credential.

When creating a template you can choose a specific credential schema and attributes included in that schema.

If the Optional toggle is selected the holder can decide if they want to share that information or not. If the toggle is turned off the holder will have to share that information or the verification will fail.

The information needs to present in the credential if the attribute is not marked as optional. E.g. if Expiration Date is not marked as Optional it will have to be present in a credential and any credential without an expiry date will fail the verification.

You can combine verifying multiple credentials in one verification template by adding a credential and selecting schema and attributes.

The list will have only the attributes that are included in the credential schemas. If you want to include an attribute that is not on the schemas owned by that account it can be typed in instead of the listed attributes.

When verifying Zero Knowledge Proof credentials, you can use range proof verification conditions, that will verify the credential without disclosing the actual value of an attribute. For example, if you want to verify that the credential holder is older than 18 you can choose attribute Age and condition is greater than 18.

If the verification template contains a paid schema a notification on the bottom will appear.

Last step for a verification request is to click Request, which will generate a QR code. Every time a new request is made, it generates a new QR code. ​

Steps for the Holder

First step for the holder is to Scan the QR code with their wallet and select the credential(s) that contain the information the verifier is requesting.

If the credentials were issued with Zero Knowledge Proof signatures the holder will be able to choose which details on the credentials to share with the verifier.

If the credentials are valid and the verification is successful, this is what the holder will see a Verification Successful message, if the credential could not be verified a Verification Failed message will appear.

Verification History

To see a log of all your verification requests, go to Verification and click on History.

When the credentials are valid it will show up as “Verified” under Status. The verifier won’t get a notification if the credential is invalid because Dock’s tools won’t let the holder submit invalid credentials.

Verification request templates can only be created in Truvera Workspace, not the wallet. These templates can be important into the wallet from Truvera Workspace for wallet-to-wallet verification.

Wallet-to-Wallet Verification

After creating the verification request in Truvera Workspace it can be imported in to the wallet for a wallet-to-wallet verification.

Go to Settings and choose Credential Verifier.

After the Verification template is imported you can share it with the holder to present and verify their credential.

In order to reduce the data stored on the system we recommend deleting the verification template data after it is not needed anymore. Read more about .

Click Import via QR code and scan the verification template QR code generated in Truvera Workspace.

Holder will scan this QR code with their Truvera Wallet and follow the .

data retention policies
See how to create a verification template here.
verification steps for the holder