SSI TrustChain

Issuer ConsoleSSI TrustChain

Issue credentials your institution stands behind

For universities, colleges, schools, hospitals, councils, banks and identity partners. Keep your own sealed records, design certificates, set approval paths, and sign credentials that people carry in their wallets for life.

  • No personal data on the network
  • Keys in secure hardware
  • Open standards
Issuer Console: a real screen with invented sample data.

What it does

Everything in Issuer Console

  • Approvals that cannot be skipped

    Each credential type has a path to signing: a senate or board vote, approvals by the right roles in the right units, then a signature. Nobody approves their own draft, and high-stakes types need two different roles.

  • Records sealed to your institution

    Student and staff records are encrypted in your staff browsers to your institution's own key, unit by unit. TrustChain keeps ciphertext; every opening is in your audit trail.

  • Journeys, not single documents

    A degree is signed only over a complete, in-order and unrevoked chain: admission, each year's transcript, then the award. A forged certificate cannot fake four years of signed history.

  • Certificate designs and printing

    Design your certificates (branding, wording, signatories, security profile), approved by a second person. Every credential comes with a PDF and a check code; print on your own numbered paper with spoilage and hand-over tracked.

  • Batches with spot-checks

    Upload a cohort, have approvers spot-check a sample with personal details masked, then sign. Rows are sealed at rest and deleted when the batch ends.

  • Issue only to verified people

    Each credential goes to a wallet whose identity was verified in person, matched through the identity index and never stored. Mismatches pause, person by person.

  • Keys in secure hardware

    Your signing key is created in AWS KMS (with HSM standby keys) and never leaves it. Revocations publish to a public status list at once.

  • An API for your systems

    Your student or HR system drafts credentials over /api/v1 with OAuth client credentials, idempotent writes and signed webhooks. People always approve and sign.

See it

Issuer Console, screen by screen

Real screens from the app, with invented sample names and figures.

How the trust works

Trust you can check, step by step.

  1. 1

    Draft

    An officer drafts from your records; the holder is a pseudonymous reference.

  2. 2

    Approve

    The path you set: votes, approvals by role and unit, each audited.

  3. 3

    Sign

    Signed with your institution's key in secure hardware; its fingerprint goes on the ledger.

  4. 4

    Deliver

    The credential, its SD-JWT VC copies and its PDF go to the wallet. Revoke or reissue later, never edit.

What you achieve

From the old way to the verified way

  • Verification letters that take weeksEmployers check a degree in seconds on their own
  • Forged certificates bought on the streetA signed chain that cannot be faked
  • One officer able to issue anythingSeparation of duties enforced by the system

Made for

  • Universities and colleges
  • TVETs and schools
  • Hospitals and professional councils
  • Banks and identity partners
  • Regulators
  • Employers

Questions

Can a signed credential be corrected?

Never edited. A mistake is corrected by a reissue that passes the whole approval path again; the old one is superseded only when the new one is signed. Or it is revoked with a reason.

Who sees our records?

Your own staff, for the units their role covers. They are sealed to your institution's key, held only in your staff browsers. TrustChain cannot open them.

How do we join?

Apply, pass vetting, and two TrustChain people accredit you. Your entry then appears in the public registry and your keys are created.

Try Issuer Console

We are onboarding the first institutions and organisations. Tell us what you issue or check today.