Skip to main content

​
Overview

As a learning or impact partner, you use the YoID platform to create digital credentials and deliver them to youth wallets. This is how a training programme completion, an impact milestone, or a government-issued document becomes a verifiable, portable credential that youth carry with them across the ecosystem.

​
What Happens on the Youth’s Side

When you issue a credential:
  1. The credential offer is delivered to the youth’s wallet (via email or direct link)
  2. If the youth has already activated their wallet, the credential appears as a pending item — they can accept or reject it
  3. If the youth hasn’t activated yet (common for partners onboarding via WhatsApp), the credential is held in a custodial state. When they eventually sign in, it’s already waiting for them.
This async pipeline means you can issue credentials at scale without worrying about whether youth have activated their wallets.

​
APIs Used

APIPurpose
Consumer Onboarding APIProvision a youth account — creates a Keycloak identity in the Consumers realm and initialises a wallet tenant
Me Creds APICreate credential templates and issue credentials
Me Wallet APIDeliver credential offers to the youth’s wallet
The Consumer Onboarding API does more than “create a user account” — it provisions a full wallet tenant backed by the Credo SSI framework. If the youth already exists, the API returns 201 with an empty tempPassword — you can proceed directly to credential issuance.

​
Issuance Workflow

1

Create Youth Account

Provision a youth account and wallet — Step 1
2

Create Credential Template

Define the structure and attributes of the credential (done once per credential type) — Step 2
3

Issue a Credential

Generate a credential offer with the youth’s specific data — Step 3
4

Send Credential Offer to Wallet

Deliver the credential to the youth’s wallet — Step 4

​
Example: Umuzi Issues a Web Development Credential

Umuzi runs a 12-month web development programme. When Thandi Molefe completes the programme, Umuzi:
  1. Has already created Thandi’s youth account during programme onboarding
  2. Has a reusable “Web Development Completion” credential template
  3. Issues a credential with Thandi’s specific completion data (programme name, completion date, skills covered)
  4. Delivers the offer to Thandi’s wallet
Thandi receives the credential in her wallet. Later, when she applies through an employment provider, she can share this credential — selectively disclosing only the attributes the employer needs.