Credential 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.

Read the docs

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.

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 docs
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 docs

How 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.

  1. Step 1

    Issuer

    A simple API lets you generate a verifiable credential, sign it and deliver it to the holder's wallet.

  2. Receives: The signed credential

    Step 2

    Wallet

    Stores the credential and gives the holder control over when and how to share it.

  3. Receives: Only the approved claims

    Step 3

    Verifier

    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.

  4. Receives: The result

    Step 4

    Your application

    Receives the result and decides what happens next.

Your verifier never contacts the issuer.

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.

Talk to an expert

AltID: the Danish EUDI wallet

Live in Denmark since 3 June 2026

AltID is the Agency for Digital Government's app for ID and credentials, and part of Denmark's implementation of the EU Digital Identity Wallet under eIDAS 2.0. The verification API can verify credentials presented from AltID, so your service can accept the state-issued ID your users already hold.

230,000 +
People downloaded the AltID app in under three weeks.
281,390
AltIDs had been created by 4 August 2026.
13
Everyone over 13 with a CPR number can use their phone as an official ID card, in person and online.

Beyond Denmark

One solution across borders

Germany's EUDI wallet is called d-you and launches on 2 January 2027. It builds on the same EU standards as AltID.

Access to the d-you sandbox

Partisia has access to the German sandbox for d-you, so credentials from d-you can be verified in the same way as AltID once it launches.

A co-author of the EU's reference framework

Partisia is a co-author of the Architecture and Reference Framework, the EU's technical reference framework under eIDAS 2.0, which all EUDI wallets are built on.

Read the docs,
or work with us

The docs take you from the concepts, through a working local deployment, to an integration in your own application. A demo walks through your use case, which of the three APIs it needs, and where it should run.

  • Issuance, signed by your organization
  • Verification with selective disclosure
  • Wallet integration, EU wallet and SD-⁠JWT-⁠VC
  • As a service, Docker, on-prem or hybrid
Read the docs Work with us