A co-author of the EU's reference framework
Partisia is a co-author on the Architecture and Reference Framework, the technical specification the EUDI Wallet ecosystem is built to. Not alignment with a standard. A hand in writing it.
Decentralized identity
Prove who you are, reveal nothing else
Decentralized identity puts people and organizations in control of their own credentials. Decentralized identifiers, verifiable credentials, and zero-knowledge proofs combine so a holder can prove a claim (over 18, EU-resident, accredited) without handing over the document behind it or depending on a central registry.
eIDAS 2.0 EUDI Wallets mandatory from December 2026
How it works
Identifiers, credentials, and proofs in one stack
Decentralized identity (also called self-sovereign identity, or a reusable ID) gives a person full control over their own identity and data, without relying on a central authority. It starts with a decentralized identifier (DID): a globally unique identifier cryptographically bound to a key the holder controls.
A verifiable credential is a cryptographically signed statement an issuer makes about a holder: a passport authority asserting a nationality, a university a degree, an employer a role. The holder keeps it in a wallet and presents it to a verifier, who confirms the credential's integrity and authenticity by checking the issuer's and the wallet's signatures in the presentation, without ever contacting the original issuer. That offline check is what preserves the holder's privacy.
The credential carries two privacy options. Selective disclosure shares only the exact attributes a transaction needs. Zero-knowledge proofs go one step further: prove a property of a credential, over 18 or resident in the EU, without revealing the claim behind it. The verifier learns one bit, not the birthday.
Partisia ships the issuer side too: a credential-issuance service that authenticates the holder over OAuth2 and delivers the credential to their wallet over the OpenID for Verifiable Credential Issuance (OID4VCI) protocol, so any organization can become a verified issuer.
Proof
Deployed, not theoretical
Named deployments, named partners, and a hand in the specification the EUDI Wallet is built to.
New Hospital Bispebjerg, with Region Hovedstaden
Verifiable digital identity underpins secure identification and access management on the New Hospital Bispebjerg construction project, in Denmark's largest region.
Vejle Municipality, through FrontDesk
AltID runs inside the booking and attendance systems a Danish municipality already uses, with Vejle as the first pilot, rather than asking anyone to adopt a separate system.
Physical access control, with Vitani
A partnership bringing verifiable digital identity into physical access control, so a credential opens a door rather than a badge nobody checks.
The actors
3 parties, and one never gets called
A credential moves between three roles. What surprises most people is the arrow that is missing from the picture.
- Step 1
Issuer
A passport authority asserting a nationality, a university a degree, an employer a role. It signs a statement about the holder and hands it over.
- Step 2
Holder
The person or organization the credential is about. It lives in their wallet, and they decide which parts of it to present, to whom, and when.
- Step 3
Verifier
Your service. It checks the issuer's signature and the wallet's signature on the presentation, and learns exactly the claim it asked for.
The verifier never contacts the issuer. That offline check is what keeps the issuer from building a log of everywhere the holder has been.
What it solves
The same stack, from where you are standing
Leadership, product teams, developers, compliance, and the public sector each ask a different question about one technology. Find yours.
Leadership
What does this cost us, or save us?
Verification costs drop when a credential is reusable rather than re-proved from documents every time, and removing document uploads removes the drop-off they cause. If you are in an obligated sector, it also avoids a compliance cliff with a date on it.
Product teams
Can we build this into what we are shipping?
Reusable credentials take repeated onboarding friction out of your own surfaces. The same credential APIs sit behind SitePass, VisitorPass, and AgeVerify.
Developers
What is the actual integration path?
OAuth2 for issuance, OpenID for Verifiable Credential Issuance (OID4VCI) to deliver to a wallet, and an SDK for the verifier side. The protocol names are all in the docs rather than paraphrased here.
Compliance and legal
Does this satisfy our obligations, and by when?
Built on the W3C Verifiable Credentials Data Model and DID Core, the standards the EUDI Wallet architecture uses. Member states must offer a wallet by December 2026 and obligated sectors must accept one about a year later.
Public sector
Is this compatible with the national wallet?
It is built to the same standards a national wallet is, so it complements one rather than competing with it. That matters most where a service has to keep working before, during, and after a national rollout.
Where it shows up
Inside the products you can buy today
Decentralized identity is the layer beneath every Partisia flow that interacts with a user's wallet.
Credential at the door
VisitorPass
Visitors present a credential issued by their employer or the venue; the host receives a signed, scoped attestation of identity, and no one learns more than they need to.
Age check, no document
AgeVerify
Age claims live in a verifiable credential, and the verifier receives the attribute it asked for, never the document behind it.
Issuance + verification
Credential APIs
Become an issuer, sign your own credentials, and verify credentials issued by others. All three flows live in the platform SDK.
Further reading