SAPIO lets schools, universities and training providers issue tamper-proof digital credentials. Learners keep them in their own wallet. Employers check them in seconds, without contacting the issuer.
Ki2aO5Mtl3Hq_9fN0y7rVb1uXe4c…pQ8wZs3LmH0dYt6nA2kVx9RfEj1u…Member of
Pilots, partners and networks
A verifiable credential carries its own proof of origin. Nobody has to call the registrar to confirm it is real.
Design a credential template once, then issue to a whole cohort from the SAPIO dashboard. Every credential is signed with your organisation’s key.
Recipients claim the credential into a compatible wallet on their phone. It belongs to them, not to a portal they lose access to after graduation.
The holder presents it with a QR scan. Signature, issuer and revocation status are checked in real time.
A PDF shows everything to everyone and proves nothing. A SAPIO credential proves where it came from and lets the holder decide which details a verifier sees.
Each claim can be revealed or withheld on its own, using SD-JWT VC.
Credentials are bound to your organisation through did:webvh, not to our platform.
Withdrawing a credential is a traceable status change, not a silent deletion.
Content aligned with the European Learning Model (ELM) so others can read it.
Follow issuance, claims and verifications as they happen.
app.sapio.idCAS Digital Transformation · Cohort 2026
Define fields, design and validity once. Reuse them for every cohort.
Decide exactly which claims a verifier may request, per use case.
Import recipients from a structured file and issue in one run.
Check credentials from other trusted schools, academies and companies too.
Built for registrars, programme managers and HR teams.
SAPIO issues and verifies with the open specifications behind the EU Digital Identity Wallet and the Swiss trust ecosystem. Your credentials are not locked into our platform.
SD-JWT VCCredential format with selective disclosureOpenID4VCIIssuing credentials into a walletOpenID4VPPresenting and verifying credentialsdid:webvhIssuer identity anchored in your own domainEDC / ELMEuropean learning semanticsswiyu · EUDISwiss and EU wallet ecosystemsEU large-scale pilot for the EUDI Wallet, use case on micro-credentials and verified skills.
Swiss digital trust association. SAPIO leads its Education Working Group and co-authored its education trust flows.
See the trust flowsDeadline for every EU member state to offer at least one EUDI Wallet under Regulation (EU) 2024/1183.
In the EU.ACE university alliance, SAPIO ran the complete credential journey with real learners: from structured credential design to issuance, wallet storage and independent verification.
Read the pilot storySAPIO has issued its first verifiable credential to swiyu, the wallet of the Swiss Confederation, in the federal sandbox. Swiss schools and training providers can prepare now for certificates that sit next to the e-ID.
How SAPIO issues to swiyuWhat it says, who issues it, when it expires. About two hours of your time.
Issuer identity, template and design. You approve the layout.
Trial issuance and verification in a real wallet.
Production issuance, handover and onboarding for your team.
A digital certificate that is cryptographically signed by the issuing organisation. Anyone can check that it is authentic, unchanged and still valid, without contacting the issuer. It is stored in the holder’s wallet, not in a central database.
No. SAPIO uses the SD-JWT VC credential format with OpenID4VCI for issuance and OpenID4VP for verification. The issuer’s identity is published with did:webvh, which is anchored in the issuer’s own web domain. No blockchain, tokens or cryptocurrency are involved.
Wallets that support OpenID4VCI and SD-JWT VC. We build on the same open standards as the EU Digital Identity Wallet and the Swiss trust ecosystem, and we test interoperability as a consortium partner in the WE BUILD large-scale pilot.
A browser and the SAPIO verification flow. The holder scans a QR code, chooses what to share, and the verifier sees the result with signature, issuer and revocation checks. No integration is needed on the verifier’s side.
Typically four weeks from the first working session to production issuance. Your team spends about two hours defining the credential, then approves the layout and names a small test cohort.
The issuing organisation decides what goes into a credential and acts as controller. SAPIO processes the data on its behalf under a data processing agreement. Details are in our privacy policy.
A first call takes 30 minutes. We look at your credential type and tell you honestly what it takes.