MitID

Overview

Denmark’s digital identity system for secure access to public and private services. Introduced as the successor to NemID, MitID allows Danish citizens and residents to securely access banking, government services, and other online applications

ID: denmark-mitid
Type: eID (app)
Verification Type: Presentation
Regions: Europe
Countries: DK, FO, GL
Adoption: 5,500,000
URL: https://www.mitid.dk/en-gb/

Integration with Trinsic

MitID is integrated into Trinsic's identity acceptance network, allowing businesses to easily accept MitID-verified identities as part of their verification processes.

Permission required: Yes, this method requires registration before you can activate it for your users. Please contact Trinsic to begin this process.
Cost: Contact the Trinsic team.

How to Test

Before launching the widget or the provider, first go to MitID Test Tool to create an identity by either clickingAUTOFILL or manually entering details, then click CREATE IDENTITY.

While using a test mode App, launch the widget or the provider directly.

Enter the credential and submit.
- id: <Identity Claim from setup>
Either click on "Open app on another device" and go back to the test tool and click "Open simulator".
Click on the "Scan QR and Confirm" to approve the request.
At the end, you will be presented with test data for the verification session.

Branding Requirements

Click here to view MitID's branding requirements.

Direct API Requirements

📘
Direct API is not a requirement.
You can integrate with this provider using the Hosted UI instead, with no additional integration requirements on your end.

What your integration must support in order to use this provider with the Direct Provider Sessions API.

Supports Direct Provider Sessions: ✅
Launch Method: LaunchBrowser — Send the user's browser (via redirect, popup, or new tab) to the given URL.
Collection Method: CaptureRedirect — The user is redirected back to your app with a resultsAccessKey upon completion.

Outputs

ℹ️
Normalized Attributes
These attributes form part of our normalized model, a standardized set used across providers. Trinsic normalizes this for you and lets you know when a property is available for each provider.

Field	Availability	Notes
`person.fullName`	Always	-
`person.dateOfBirth`	Sometimes	If available

Field	Optional	Description	Example Values
`fullName`	Yes	The full name of the individual.	Ove Henriksen
`dateOfBirth`	Yes	The date of birth of the individual.	1943-08-15
`uniqueIdentifier`	Yes	A stable unique identifier representing the individual in MitID's system. It is recommended to use this identifier instead of using the civil registration number (CPR number) directly.	8ba191ec-64b1-41c1-b622-4b8c14c34428
`authenticationAssuranceLevel`	Yes	The authentication assurance level (AAL) for the verification. The National Institute of Standards and Technology (NIST) measures the confidence in a digital identity's authentication strength set by a set of requirements for different levels. More information can be found here: https://pages.nist.gov/800-63-4/sp800-63b/aal/#AAL_SEC4 Possible values: - https://data.gov.dk/concept/core/nsis/Low - (Level 1) Provides basic confidence that the authenticator is either single factor or multifactor authentication. - https://data.gov.dk/concept/core/nsis/Substantial - (Level 2) Provides high confidence that the authenticator uses two distinct authentication factors that use secure authentication protocols. - https://data.gov.dk/concept/core/nsis/High - (Level 3) Provides very high confidence that the authenticator uses an non-exportable private key and another authentication factor. Note: These urls are not valid anymore, but they still contain the level of assurance name.	https://data.gov.dk/concept/core/nsis/Substantial
`identityAuthenticationLevel`	Yes	The identity assurance level (IAL) for the verification. The National Institute of Standards and Technology (NIST) measures the confidence of the digital identity's verification set by a set of requirements for different levels. More information can be found here: https://pages.nist.gov/800-63-4/sp800-63b/aal/#AAL_SEC4 Possible values: - https://data.gov.dk/concept/core/nsis/Low - (Level 1) The individual has self asserted their identity and is neither verified nor validated. - https://data.gov.dk/concept/core/nsis/Substantial - (Level 2) The individual has performed either a remote or in-person identity proofing. - https://data.gov.dk/concept/core/nsis/High - (Level 3) The individual has performed an in person identity proofing with an authorized representative. Note: These urls are not valid anymore, but they still contain the level of assurance name.	https://data.gov.dk/concept/core/nsis/Substantial
`levelOfAssurance`	Yes	The level of assurance (LOA) for the verification. This is an older retired model that is a combination of Identity Assurance Level and Authentication Assurance Level. The National Institute of Standards and Technology (NIST) measures the confidence of the digital identity's verification and authentication strength by a set of requirements for different levels. Possible values: - https://data.gov.dk/concept/core/nsis/Low - (Level 1) The individual has self asserted their identity and multifactor authentication is not required. - https://data.gov.dk/concept/core/nsis/Substantial - (Level 3) The individual has performed either a remote or in-person identity proofing and multifactor authentication is required. - https://data.gov.dk/concept/core/nsis/High - (Level 4) The individual has performed an in person identity proofing with an authorized representative and has strong cryptographic authentication requirements. Note: These urls are not valid anymore, but they still contain the level of assurance name. MitID only returns three of the four potential levels and does not include level 2. More information can be found here: - https://pages.nist.gov/800-63-3/sp800-63-3.html - https://pages.nist.gov/800-63-3/	https://data.gov.dk/concept/core/nsis/Substantial
`identificationSource`	Yes	The source of the identification for the verification Possible values: - private - The verification is from a private individual. - professional - The verification is an individual on behalf of an organization.	private
`civilRegistrationNumber`	Yes	The civil registration number (CPR number) of the individual for the verification. The CPR number is a 10-digit number in the format DDMMYYY-XXXX, where: - DDMMYYY represents the individual's date of birth (day, month, year). - XXXX is a unique identifier. If XXXX is even, the individual is female. If XXXX is odd, the individual is male. More information can be found here: https://international.kk.dk/live/cpr-registration-and-documents/cpr-number	01311985-1234
`organizationName`	Yes	The name of the organization for the verification	Dansk Standard
`organizationNumber`	Yes	The organization number (CVR number). This is an 8-digit unique identifier for the organization. This will be prefixed with "DK" for VAT numbers.	DK12345678
`authorizedRepresentativeNumber`	Yes	The organization number (CVR number) of the organization the individual is authorized to represent. This is only returned if the requested scope is for an organization verification and the individual provides a private source on behalf of a company.	8ba191ec-64b1-41c1-b622-4b8c14c34428

Frequently Asked Questions

Can you support the CPR (Danish ID Number) flow through MitID?

Yes, Trinsic can configure MitID to support receiving the user’s CPR number. MitID exposes this as a matching flow which adds an additional screen after a user successfully authenticates. The screen prompts the user to enter their CPR number and grant consent.

Can you request LoA High verification from MitID?

Yes, Trinsic can configure MitID to only allow a user with a LoA High credential to be able to complete the flow.

Can we collect the user ID outside of the MitID interface?

It is mandated by the MitID scheme UX requirements that the user ID be collected in the MitID UI.