For institutions
Issue digital credentials with Tamga
Universities, hospitals, chambers, public bodies, companies and event organisers can issue credentials that people carry on their phones and anyone can verify in seconds, without calling you.
Your data stays with you
Tamga does not access your database and does not store people's data. At issuance the details are read from you, through an endpoint you control, signed with your own key and sent to the person's phone.
Who can join
- Education
- student credential, diploma, certificates
- Health
- licence to practise, chamber membership, employment credential (in preparation)
- Public bodies
- credentials from an authentic source, on behalf of the state
- Companies
- employee and authorisation credentials, building access
- Events
- tickets bound to a person, single-use at the gate
What you get
No more confirmation requests
verifiers check the credential themselves; nobody needs to call or write to you.
No forgeries
without your signature and your entry in the signed trust list, no valid credential can exist.
Control
revoke or suspend at once; issuance statistics in the Institution Console, never personal data.
Data minimisation
people share only what is asked; you never learn to whom a credential was shown.
European standards
SD-JWT VC, OpenID4VCI / OpenID4VP, X.509 and signed trust lists — the EU wallet's building blocks.
No lock-in
open-source packages (Apache-2.0); you can run the issuing service on your own servers.
What we need from you
Registration data
- legal name and display name
- official identifier (tax number, trade register number)
- postal address, website, institutional contact
- data protection authority; public body or not
- privacy policy link (shown in the wallet)
Legal
- cooperation agreement
- data processing agreement: you are the controller, Tamga the processor
- updated privacy notice for the people you issue to
- proof that you are entitled to issue this credential
Technical
- a signing key generated in your own key vault (KMS / HSM); you send only a certificate request (CSR)
- a lookup endpoint in front of your records, following our OpenAPI contract, and/or calls to our API
- a revocation process (API or Institution Console)
- technical, data-protection and security contacts
How joining works
1 · Scope
live demo; which credentials, which pilot group
2 · Credential type
choose from the public catalogue or design a new type together
3 · Legal
agreements and privacy notice
4 · Registration
registration data, certificate, entry in the trust list
5 · Integration
lookup endpoint and/or API, tested end to end in the sandbox
6 · Pilot, then live
a small group first, then everyone
Verifying instead of issuing?
Employers, websites and gates join as registered verifiers: for each use you register which credential and fields you request, the purpose and a privacy policy. The wallet warns people when a verifier asks for more than it registered.
Apply
Write to us with your institution's name and the credentials you want to issue or verify. We reply with a demo date and the full requirements guide.
info@tamga.networkFull requirements guide on request