🇩🇰

Digital ID verification in Denmark

Accept MitID, the Danish electronic identity for online login and signing, and AltID, a Danish EUDI wallet, through one Trinsic integration for customers in Denmark.

5.3 million

users of the leading digital ID

2

digital IDs available through Trinsic

Released

national EUDI wallet status

GBG
Shufti
Alloy
Daon
Prove
Three stacked report covers titled Digital ID Opportunity Zones in 2025 with world map graphics

FREE REPORT 2026

Digital ID Opportunity Zones

Where your company should prioritize accepting digital IDs in 2026 based on our research of 300+ identity networks.

Get the report

EUDI Wallet

EUDI Wallet readiness in Denmark

Denmark’s AltID launched on 3 June 2026 as the first national stage of a phased EUDI implementation. Official statistics recorded 281,390 accounts created by 4 August. MitID supports enrolment and authentication; it is a separate identity service, not the wallet that becomes EUDI.

AltID already has domestic receiver onboarding and a test environment available through a company-email request, a MitID test user and a test verifier. These are practical routes into the current national service, but the domestic receiver register is explicitly distinct from the future EUDI relying-party register. Full eIDAS2 functionality, wallet-certification arrangements and the national policy for independent private EUDI wallets remain separate milestones or unresolved questions.

Where things stand

Tracked by Trinsic from official sources

National wallet

Released

Developer access

Sandbox restricted

EU status

EU member

Frequently asked questions

01

Which digital IDs can I verify in Denmark with Trinsic?

02

How widely used is MitID in Denmark?

03

What is the difference between MitID and AltID?

04

Where does Denmark stand on the EUDI wallet?

05

How do I start verifying users in Denmark?

One integration. A growing network of digital IDs.

Trinsic verifies hundreds of digital IDs across 50+ countries through one integration. Add a new country without rebuilding your verification flow.