Check-in
FrontDesk
- Family name
- Hansen
- Given name
- Mette Sofie
Verified with AltID
Identity infrastructure on eIDAS 2.0
Partisia issues and verifies digital credentials, so you know who you are dealing with and people share only what is needed.
A credential on a person's own phone can open a door, prove an age or confirm a role. Partisia provides the products and the APIs behind those checks, built on the open standards of eIDAS 2.0 and connected to the systems you already run.
What Partisia does
Partisia moves the proof to the person. A trusted issuer signs a credential, the person keeps it in a wallet on their own phone, and your service checks it when it needs to.
Signs a credential and delivers it to the person.
Holds it and shares only what the person approves.
Checks the signatures, without contacting the issuer.
Receives the result and decides.
What changes
Organizations verify the same people again and again: at reception, at the site gate, at the checkout. Each check collects a copy of a document or a date of birth that then has to be stored and protected.
Identity is checked with AltID, MitID or a passport scan, so the record links a real person to what happened.
Selective disclosure reveals only the attributes a check needs. An age check returns whether the person is over the age limit, and nothing else.
Partisia records that a verification succeeded, not the document behind it.
Partisia is not an access control system and does not replace your identity provider. It connects to the access control, directory and supplier systems you already have.
A visitor pass or a site ID stops working when the visit or the period on site ends.
As a service, or on your own infrastructure with Docker, on-prem or hybrid.
Products
Three ready-made products for the checks organizations ask for most, and the Credential APIs they are built on, for checks of your own design. The first flow puts the platform in place, and the next one is built on it rather than beside it.
Guests and contractors
Guests and contractors check in from their own phones, and every visit is linked to a real identity and the doors it opened. For offices, hospitals and plants, where NIS2 makes visitor access rules a must for many companies.
The workforce of a site
A verified digital ID on every phone, for workers, contractors and temporary staff. It is used for check-in, time on site and access at gates and doors, and is in operation at New Hospital Bispebjerg.
Age checks
The user proves they are over the age limit from a credential in their wallet, and your service receives that one fact. No date of birth, CPR number or document to store. For webshops, bars and venues, where the age question is already a legal one.
Build your own
Issuance, verification and wallet APIs you deploy inside your own infrastructure, or use as a service. For accreditation, residency, licensing, membership or any check you define.
Which one fits
Each product covers one of them, and the Credential APIs they are built on let you design your own.
| If you need to | Choose |
|---|---|
| Let guests and contractors into a building, with a record of who was inside and when | VisitorPass |
| Give everyone working on a site a verified ID and record their time on site | SitePass |
| Confirm a customer is over an age limit without collecting their ID | AgeVerify |
| Issue or verify credentials of your own design, inside your own systems | Credential APIs |
How the products work together
Where different people arrive at the same place, the products run side by side on one platform.
On a site, SitePass covers the workforce and VisitorPass covers guests and deliveries, recorded in the same log.
A site ID and a visitor pass sit side by side in Partisia ID Wallet, with the same check-in.
Adding a second product does not mean connecting to your access control system twice.
Why now
Every year more people hold a wallet that works, so the identity check gets easier rather than harder.
The EU's NIS2 Directive makes visitor access rules a must for many companies.
Under the UK Online Safety Act, Ofcom enforces age assurance for services hosting pornography and other age-restricted content. Under the EU Digital Services Act, the Commission has opened formal proceedings against several platforms over age assurance.
Wallets from every member state follow the same standard, so a check built for AltID today meets the wallets that arrive next.
Why Partisia
Partisia was founded in 2008 in Aarhus, Denmark, as a spin-out from Aarhus University, on more than three decades of cryptographic research, and is backed by the EIC Accelerator.
SitePass is among the first known solutions in Denmark to put AltID, the Danish EUDI wallet, into use. Germany's d-you follows on the same standards.
W3C Verifiable Credentials, SD-JWT, mdoc (ISO/IEC 18013-5), OpenID4VCI and OpenID4VP: the same standards the EUDI wallets build upon.
Your access control system keeps every authorization and decision. Your directory stays the single place a person is created and removed.
Partisia ID Wallet, AltID, a wallet in your own brand, or an EU Digital Identity Wallet as they arrive.
Proof
Named deployments, named partners, and a hand in the specification the EUDI Wallet is built to.
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.
Region Hovedstaden, Vitani Security and Partisia have brought identity, consent and access together in one flow on the construction of New Hospital Bispebjerg, a 70,000 m² hospital. Workers and partners are approved digitally before they arrive.
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.
A partnership bringing verifiable digital identity into physical access control, so a credential opens a door rather than a badge nobody checks.
Next step
Most organizations begin where the problem is already concrete: visitors at the front desk, workers at the site gate, or an age check at the checkout. The next use case is built on the same platform.
The checks you make today, who makes them, and which need a verified identity.
Which of your systems the credential touches, and what each one needs.
One flow in production, as a service or on your own infrastructure.