Skip to content

Issuance ​

The institution (the issuerThe institution that signs and issues credentials: a university, a professional body, a public institution or a company.) issues a credential to the person's wallet with OpenID4VCI (OpenID for Verifiable Credential Issuance)The protocol an issuer uses to deliver a credential to a wallet. 1.0 (the EU profile HAIP (High Assurance Interoperability Profile)The OpenID4VC profile that fixes the choices for high-assurance use, as in the EUDI Wallet. 1.0). There are two ways to start.

The institution creates a credential offer; the person scans the QR code with the wallet or taps the link. The offer is standard (openid-credential-offer://). In a pre-authorized offer the one-time 6-digit code (tx_code) is mandatory: on the institution's screen it is shown with the QR code to the signed-in person; if the offer goes by e-mail, the code comes through another channel (SMS). An identity-bound offer from the institution has no code; the person presents the verified identity in the wallet instead.

2. The person asks from the wallet ​

In the wallet the person picks their university from the list of institutions and asks for the credential. The institution knows that the requester really is that person because the verified identity in the wallet is presented; there is no matching by name or number. The credential data is read from the institution's own system (the authentic sourceThe system that actually owns the data in a credential, for example a university's student information system.) at the moment of signing; Tamga keeps no register of people.

Wallet attestations ​

When receiving a credential, the wallet presents a short-lived WIA (Wallet Instance Attestation)A short-lived statement signed by the wallet provider that a wallet installation is genuine; issuers check it before issuing. signed by the wallet providerThe organisation that offers a wallet, registers its wallet units and signs wallet and key attestations. Each wallet runs its own provider; the network does not run one, it lists them in the trusted list. that built it, and a key attestationA short-lived statement by the wallet provider that a credential key was created and is kept in secure hardware. showing that its keys are kept in secure hardware. The institution checks them against the wallet providers in the trust listA signed list of a country's root certificates, issuers and registered relying parties. Today trust in Tamga rests on these lists; a shared ledger comes later.; no credential is issued to a wallet from a provider that is not on the list.

The flow at a glance ​

wallet                         institution (issuer.tamga.network/{institution})
  │  metadata  ───────────────▶  /.well-known/openid-credential-issuer/{institution}
  │  PAR + authorisation (DPoP) ▶  identity matching / offer code
  │  token  ──────────────────▶  wallet attestation check
  │  credential (proof) ──────▶  signature; entry in the status list
  │  ◀───────────────────────  SD-JWT VC (+ mdoc for identity), batch copies

Your own service or the hosted one? ​

  • Hosted service: issuer.tamga.network/{institution}; your institution creates offers from its own systems with an API key and manages credentials in the Institution Console. Guide: GUIDE-0003.
  • Your own service: with @tamga-network/issuer; you register in the trust list as an issuer.
  • Registration, on either path: your IT team prepares and tests the institution's side (application file, keys and CSRs, setup and how you appear in the list) with the @tamga-network/onboard onboarding tool: GUIDE-0014.

Details ​