Skip to content

Issuer workflow : create Verifiable Credentials

Now that our organisation is trusted and has its place in the Base Registry, and that we configured a dedicated Issuer service instance that is trusted by the Base Registry, we can run a real end-to-end test that will :

  • Issues a verifiable credential
  • Loads it into the swiyu wallet.

Pre-requisites

For the demo to work, we need to spin-up some services :

  • Docker swiyu issuer/verifier ➡️ spin-up docker+service
  • Cloudflare tunnels ➡️ make the issuer/verifier services reachable from the internet
  • Vercel proxy ➡️ handles CORS errors by fixing headers (restricted by origins)

Check actual service status below before running your demo test. You need green ✅ checkmarks ! Otherwise the demo is not going to work.

Service Status

🔄 Checking services...

SWIYU issuer demo

With Issuer Service reachable - you can use the below form to create your own Verifiable Credential.

  • You'll be acting as authoritative person issueing a valid credential to someone (yourself in this case).
  • You can use dummy text as long as format is respected. In this case we are emulating a membership credential (with a given class level).

Swiyu App

Now once a new Verifiable Credential has been issued, it can be retrieved by one instance (person/Swiyu app). The below picture of my mobile phone shows how these cards are then installed into your Swiyu Wallet. Go to the User eXperience role page for more info.

Example

Illustration of Swiyu eWallet app
Illustration of Swiyu eWallet app

Credential loaded into Swiyu eWallet app
Credential loaded into Swiyu eWallet app