Skip to main content
Skip table of contents



Lissi Products

Lissi Platform

  • SSI Agent for businesses

  • Consists of Lissi Agent, Lissi Connect, and Lissi Verifier

Lissi Agent

  • Core part of the Lissi Platform

  • Aries cloud agent

  • Supports AnonCreds and Indy Ledgers

Lissi Connect

  • Optional component of the Lissi Platform

  • Offers password-less authentication and authorization based on verifiable credentials

  • Open ID Connect Identity Provider

  • Lissi Connect is the bridge between the OIDC and SSI world

Lissi Verifier

  • Agent for generating connectionless proof requests

  • Offers a UI and directly shows the validated proof presentation

  • Connects to a Lissi Agent instance and allows to generate proof requests based on the proof templates defined in the connected Lissi Agent instance

Lissi Wallet


  • iOS and Android SSI agent for holders

  • Can be used by end-users to manage their verifiable credentials

  • Aries cloud agent

  • Supports AnonCreds and Indy Ledgers

SSI Entities


  • issues credentials to holders

  • is a trust anchor


  • wants to verify a credential from a holder issued by an issuer

  • trusts that the issuer only issued its credential to eligibal holders


  • receives credentials from issuers

  • presents credentials to verifiers

DID Concepts


  • Decentralized ID

  • cryptographically linked to a private and public key

Public DID

  • a DID that is published on a ledger

Private DID

  • a DID that is not published to a ledger

Default DID

  • can be either a public or a private DID

  • every tenant of a Lissi Agent has one default DID

  • the default DID will be used when

    • writing schemas to the ledger

    • writing credential definitions to the ledger

    • connection invitations

    • creating conectionless proof requests

Peer DID

  • a private DID

  • represents a peer-to-peer connection with another agent

  • only shared with one other agent


Connection Exchange

  • process of establishing a connection between two agents


  • a connection established between two agents

Connection Invitation

  • a connection invitation needs to be accepted in order to establish a new connection

Schemas and Credentials


  • outline for credential definitions

  • defines a set of attributes for credential definitions

Credential Definition

  • based on a schema

  • can be revocable or non-revocable

  • has a credential image

Credential Image

  • each Credential Definition is associated with an image

  • the image is displayed in the Lissi Wallet


  • based on a credential definition

  • a credential is a verifiable set of attributes representing identity data of a holder

Credential Attributes

  • a certain attribute values issued in a credential

Credential Exchange

  • issuance of a credential


Proof Exchange

  • consists of a proof request that is answered by a proof presentation

Proof Request

  • request for a proof presentation

  • occurs in the context of a proof exchange

  • can be based on a proof template

  • is send to an existing connection

Connectionless Proof Request

  • request for a proof presentation

  • occurs in the context of a proof exchange

  • can be based on a proof template

  • is not send to an existing connection but instead shared as a URL/QR code with any holder

Proof Presentation

  • answers a proof request

  • occurs in the context of a proof exchange

Proof Template

  • defines the proof presentations that are requested by a proof request

  • can be used to create many proof requests


  • a predicate allows to check if a credential attribute value is >, <, <=, >=, or = a certain value

  • a predicate allows to retrieve data from a credential without revealing the exact attribute value

Self-Attested Attributes

  • a self-attested attribute has not been attested by any issuer

  • instead, the holder can enter any value

  • within the Lissi Wallet a text field will be shown in case a self-attested attribute is being requested



  • one Lissi Agent can have many tenants

  • each tenant represents a different entity (organization, department, individum, …)

  • each tenant has its own public DID


  • every tenant has one wallet

  • a wallet stores private data securely and encrypted


  • each tenant can be accessed by many users

  • a user is either an admin or a tenant user


  • is allowed to access all tenants

  • is allowed to manage tenants (create/update/delete)

Tenant User

  • is only allowed to access one or more tenants

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.