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
    • 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
    • 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
  • 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
  • Select a credential schema
  • Select a design
  • Add recipients
  • Formatting the CSV file for recipient upload
  • Expire credential
  • Choose credential options
  • Choose credential variant
  • Distribute credentials

Was this helpful?

Edit on GitHub
  1. Truvera Workspace

Issue verifiable credentials

PreviousCreate an organization profile (DID)NextFiltering, downloading and deleting credentials

Last updated 1 month ago

Was this helpful?

Issuing Credentials

In the Credentials menu, click Issue credentials.

Select a credential schema

Select a design

Add recipients

If you have many credentials to issue, you can issue them in bulk. To do this, select Import Spreadsheet.

If you want to add recipients one by one, select Add Manually.

You can distribute your credentials by email or directly to their wallet through their DID.

To send the credential by email, fill in their email in the Recipient Email field.

To send the credential directly to the holders wallet fill in their DID in the Subject ID (Recipient ID) field.

Fill in all other attributes that need to be included in the credential e.g. Subject name, Credential Title etc.

Formatting the CSV file for recipient upload

You can download the CSV sample file to use as a base for you recipient data upload. The sample file has only 3 collumns with the name, did and date attributes.

You will need to add columns and remove the ones you do not have in your credential schema.

When uploading a file you will be able to select a charset specification. UTF-8 will bet the choice for most users. If your dataset contains special characters you might need to choose a different charset, based on the one used to encode your data file.

If you do not know the holders dids you do not have to use it for the import, you can add emails, for the email distribution or distribute credentials manually.

You will be asked to match the columns on the csv file to the credential fields. If there are any required fields on the credential schema they must be filled in, otherwise the import will not be successful.

Expire credential

If you need the credential to expire, turn on the expiration toggle and enter the expiration date.

Choose credential options

After you have added your credential recipients you will be able to select the credential settings. You have the options to:

Persist credential: This option will encrypt the credential by providing a password to access it and store it on Truvera's servers. The credential can be accessed and verified by a URL or QR Code. The recipient can scan the QR Code to import the credential into a wallet app. The credential can be deleted from Truvera's cloud whenever you decide.

Persisting is a good option for issuers if they want to securely store the credentials as a backup. It encrypts the credentials using Libsodium crypto secretbox Salsa20/Poly1305 algorithm and stores them on our servers that are located in the US and are powered by Amazon Web Services (AWS). Because the credential information is encrypted, Truvera can’t access the information to ensure data privacy and security. ​

Credential revocation: By selecting Enable Revocation, you leave an option for the credential to be revoked to invalid state at any time. If you leave this option unchecked, the credential can never be revoked and will always be verifiable.

Choose credential variant

Truvera offers a choice of 3 different credential variants that have distinct features and are best fit for different use cases.

  • Standard Signature (ed25519) - a more simple credential variant that is the best option for interoperability with other verifiable credential services.

  • Anonymous (dockbbs23) - uses BBS+ to enable selective disclosure and zero knowledge proofs. Best for use cases where user data privacy is a top priority.

  • EUDI (SD-JWT-VC) - follows European identity standards for compliance and interoperability.

Distribute credentials

If you have entered the holders DIDs to Subject ID the holder will receive the credential directly in their wallet without any additional communication needed.

If you have entered the email address, you will have an option to write a message and preview the email that is going to be sent to the receiver of the credential.

If you do not have or want to use DIDs for the credential distribution you will need to enter an email of the recipient or persist the credential.

Select a pre-made credential schema by clicking on it's name or . You can click on Preview to see what attributes are included in the template.

Select a design or for your credentials. Alternatively, you can proceed without a design.

Download the sample CSV template and fill in the details needed for your credential template. Upload the completed .csv file back to Truvera.

Select which you want to use to issue the credentials.

There is a 4th credential variant Ecosystem-bound (BBDT16) that is used for It will get automatically selected when a price is assigned to a schema in an ecosystem.

Create your own schema
create a new one
Organization Profile (DID)
Ecosystem bound credentials.
Read how to correctly format the Spreadsheet for CSV upload.