Everything a login broker needs
Multi-tenant from day one – for municipalities, cantons and SME portals.
Purpose binding per client
Every client has an attribute policy and a visible purpose text. Only the intersection of scope and policy is ever requested.
Data minimization
DCQL requests exactly and only what the purpose requires – never more.
Consent log
An append-only log of every release – with a purpose snapshot, but no attribute values.
Pairwise subjects
A separate, non-correlatable subject per tenant – portals cannot link users across each other.
Standard OIDC
A standard OIDC client (Authorization Code + PKCE). No proprietary SDK, no wallet logic in your portal.
Swiss hosting
Operated in Switzerland, multi-tenant, with an admin console and audit log – with your own verifier DID on request.
Provica in action
One QR code, four steps – and your portal knows the verified attributes.
The login page of an integrated portal: "Log in with e-ID", QR code for the swiyu wallet, visible purpose text.
The flow: portal integrates via OIDC, the user scans the QR code, the wallet presents selectively, Provica delivers verified claims.
Build it yourself, or use Provica
The swiyu verifier is open source – it's operating it that hurts.
Operate a verifier
Yourself: deploy and operate the swiyu verifier, manage signing keys as SEC1, response encryption is mandatory. With Provica: done.
Track swiyu changes
Yourself: keep VCT and issuer DIDs current while the documentation lags behind. With Provica: we keep it current for you.
Purpose binding and consent
Yourself: build purpose binding, consent and data minimization from scratch. With Provica: built in, from day one.
Tenants and audit
Yourself: solve tenants, key rotation and audit logs on your own. With Provica: multi-tenant, with an admin console and audit log.
How it works
One QR code. Four steps. Done.
Portal integrates via OIDC
A standard OIDC client (Authorization Code + PKCE). No proprietary SDK, no wallet logic.
User scans the QR code
Provica generates the verification request and shows a QR code or deep link for the swiyu wallet.
Wallet presents selectively
The wallet presents only the purpose-bound attributes – as an SD-JWT VC via OID4VP.
Verified claims returned
Provica verifies, minimizes and delivers the attributes as an OIDC ID token and via the userinfo endpoint.
On the official Swiss e-ID ecosystem
Weeks of work saved
A custom swiyu integration costs weeks of implementation – plus ongoing operation. With Provica you're live in an afternoon.
Built for the public sector
Multi-tenant for municipalities, cantons and SME portals – with consent logging and non-correlatable subjects.
Closed beta
Provica is currently in closed beta. Talk to us if you'd like to get your portal ready for the e-ID early.
Ready to get your portal ready for the Swiss e-ID?
Provica is in closed beta. We'll discuss your use case and get in touch as soon as a spot opens up.