Introduction

Verification and Issue of Credentials Use Cases

This document describes a tipical customer integration cases that cover the two main activity on Dizme Stack:

• asking a credentials verification (proof) to a user wallet
• issue a new credential to the user wallet
• combining the two operation in one flow

Setting up your SERVICE on Dizme Studio

Before your backend application can use Dizme Api you need to configure a service on your Dizme Studio istance. Given the asynchronous nature of the Dizme Stack (DARS) services, the integrating application will have to set up REST services on which it will receive callbacks. Some of the callbacks refer to the three main operations and are:

*verify event : Successfully confirmed verification confirmation.

*issue event: credential release confirmation completed successfully.

The endpoint and path of these callbacks can be configured in the Services section of Dizme Studio.

Callback specifications can be found on the following page:

Scenario

It is common to encounter Dizme service integration scenarios where the customer, in order to provide a specific service, needs to "ask" the user to demonstrate that they are in possession of specific information.

This translates into a proof for issuing integration.

The user who wants to access the service or obtain a specific credential will be given a proof of possession of specific credentials/information. In case of successful verification and on the basis of one's business logic, it will be possible to send a credential offer directly to the user's wallet.

This integration scenario involves using Dizme's APIs to verify and issue credentials.