Technical OpenID Credential Demo

Personality Data.
Issue it. Store it. Present it. Verify it.

This demo shows the complete technical flow for Personality Data as a Verifiable Credential: issuance through OpenID4VCI, storage in a wallet, presentation through OpenID4VP, verification by an independent verifier, and the application database that links a demo user to the corresponding wallet ID.

Railway components

Live backend services used by this demo
Railway · Online

Credential Issuer

walt.id Issuer2

Creates credential offers and cryptographically signs the Personality Data Credential.

  • Protocol: OpenID4VCI
  • Offer type: Pre-authorized
  • Credential: Personality Data
  • Issuer identity: DID
→
Railway · Online

PostgreSQL Database

Application Data Store

Stores the application-side relationship between the identified demo user and the wallet managed by Wallet API2.

  • User / customer identity
  • Phone or subject identifier
  • Linked wallet ID
  • No private wallet key stored here
→
Railway · Online

Wallet Management

walt.id Wallet API2

Creates and manages demo wallets, keys, DIDs and stored credentials.

  • Wallet ID
  • Holder key
  • Holder DID
  • Stored credentials
→
Railway · Online

Credential Verifier

walt.id Verifier2

Creates presentation requests and validates credentials presented by the holder.

  • Protocol: OpenID4VP
  • Presentation session
  • Credential proof validation
  • Verified claims returned

Run the demo

Three technical entry points
01

Issue Personality Data

Identify the holder, resolve the linked wallet, create Personality Data, generate an OID4VCI offer and issue a signed credential.

Start Issuance Flow
02

Inspect the Wallet

View the technical wallet ID, holder relationship and credentials currently stored through Wallet API2.

Open Wallet Management
03

Present & Verify

Generate an OID4VP presentation request, scan it with a wallet, present the credential and inspect the verified result.

Start Verification Flow
What happens technically?
1Identity mock
2User record
3Wallet ID link
4Wallet + DID
5OID4VCI offer
6Credential stored
7OID4VP request
8Verification result
Separation of responsibilities: PostgreSQL stores application relationships such as customer → wallet ID. Issuer2 signs credentials. Wallet API2 manages wallet keys, DIDs and credentials. Verifier2 validates a later presentation. The verifier does not require direct access to the issuer's database or to the wallet's private key.