Issuance
Verifiable credentials, signed by you
Issue standards-based credentials signed by your organization. Compatible with the EU Architecture & Reference Framework and any SD-JWT-VC wallet.
Read the issuance docsCredential APIs
The credential APIs behind everything we ship
Issuance, verification, and wallet integration, delivered as APIs and SDKs you deploy inside your own infrastructure or use as a service. Organizations run their own identity flows on them. SitePass, VisitorPass and AgeVerify are three of those flows that we productized.
What you get
3 APIs, use one or all 3
Each is independently deployable. Use them together for a complete identity stack, or pick one to slot into the system you already have.
Verification
Verify the credentials you trust
Request only the attributes you need, such as age, residency, accreditation or membership, and get a verified result back, without writing cryptography yourself.
Read the verification docs Wallet integration
Plug into the wallet your users already have
Adapters for the EU Digital Identity Wallet and the SD-JWT-VC standard. Optional: bring your own wallet, or skip the wallet layer entirely.
Read the wallet integration docsHow the Credential APIs work
From the issuer's signature to your decision
The APIs cover the whole life of a credential, from issuance to verification, on open standards.
- Step 1
Issuer
A simple API lets you generate a verifiable credential, sign it and deliver it to the holder's wallet.
-
Receives: The signed credential
Step 2Wallet
Stores the credential and gives the holder control over when and how to share it.
-
Receives: Only the approved claims
Step 3Verifier
A simple API lets you check the signatures on the credential and the presentation, so you know the information is accurate, came from an issuer you trust, and has not been tampered with.
-
Receives: The result
Step 4Your application
Receives the result and decides what happens next.
Your verifier never contacts the issuer.
Standards
The published standards the APIs implement
Data model
W3C Verifiable Credentials Data Model 2.0
w3.org
Selective disclosure
Selective Disclosure for JWTs (SD-JWT)
ietf.org
Issuance
OpenID for Verifiable Credential Issuance (OID4VCI)
openid.net
Presentation
OpenID for Verifiable Presentations (OID4VP)
openid.net
Identifiers
W3C Decentralized Identifiers (DIDs) v1.0
w3.org
Docs
How the APIs use each standard
docs.partisia.com
What teams build
2 ways in, on the same APIs
Build your own
Credentials for whatever you verify
Accreditation, residency, professional licensing, membership, workforce access, custom regulatory checks. Same building blocks, your shape, inside your own infrastructure or as a service.
Ready-made
SitePass, VisitorPass and AgeVerify
Three flows we productized on these APIs. Start there when the use case matches and skip the build.
Why now
EUDI wallets, live and on the way
Work with us,
or read the docs
A demo walks through your use case, which of the three APIs it needs, and where it should run. The docs take you from the concepts, through a working local deployment, to an integration in your own application.