The Problem
Youth around the world complete training programmes, earn certificates, and build real skills — but when it’s time to prove it to an employer, they’re stuck with PDF certificates that are slow to verify, easy to forge, and impossible to share selectively. On the other side, employers spend weeks manually verifying candidate documents. Learning partners can’t track what happens to youth after they leave. Impact partners can’t prove outcomes to funders. Everyone operates in silos.What YoID Does
YoID is the shared trust layer of the YOMA ecosystem. It connects learning partners, youth, impact partners, and employers through verifiable digital credentials — cryptographically signed, tamper-proof, and instantly verifiable. When a learning partner like Umuzi credentials a youth who completes their web development programme, that credential flows into the youth’s digital wallet. When an employer wants to verify that a candidate actually completed the programme, they can do so instantly — no phone calls, no emails, no three-week turnaround. Every partner that integrates with YoID strengthens the network for everyone else.Three Zones
The ecosystem operates in three zones:| Zone | Role | What they do |
|---|---|---|
| Learning & Impact Partners | Issuers | Issue verifiable credentials to youth as milestones are reached — course completions, programme participation, impact outcomes. |
| Youth | Holders | Hold credentials in a digital wallet. Control who sees what. Build a verifiable CV that follows them across the ecosystem. |
| Employers & Opportunity Providers | Verifiers | Verify youth credentials instantly. Reduce hiring costs. Get richer candidate profiles than a PDF could ever provide. |
How Trust Flows
- An opportunity provider (e.g. Umuzi) creates a credential template defining what a “Web Development Completion” credential contains
- When Thandi completes the programme, Umuzi issues her a credential that lands in her digital wallet
- Thandi applies for a role through an employment provider
- The employer sends a verification request — Thandi’s wallet prompts her to consent and share
- Thandi selectively shares her completion credential — without revealing her assessment scores or personal details she doesn’t want to expose
- The employer receives cryptographic proof that the credential is authentic, issued by Umuzi, and hasn’t been tampered with
Built on DIDx:Me
YoID is powered by DIDx:Me — the same credential infrastructure, the same REST API, repositioned for the learning-to-earning context. If you’ve integrated with DIDx:Me before, you already know the API. The difference is the ecosystem around it.Next Steps
Meet the Actors
Understand who participates in the ecosystem and what each partner needs
Credentials Explained
Learn how verifiable credentials work — without the jargon