How the concept is used
A MitID journey normally starts in the service the user wants to access. The user approves a particular request with MitID and returns to that service. MitID is therefore one part of a larger transaction: the service must still decide which action it is requesting and how to interpret the result. Signing into an account, checking an age threshold and accepting an agreement should not be presented as interchangeable tasks.
A practical example
A Danish wine shop might ask a customer to confirm that a required age threshold has been reached. The customer completes the MitID step, and the shop uses the outcome to decide whether the order may continue. The configuration determines which information the shop receives. The presence of a general MitID integration does not, by itself, demonstrate that every requirement for a particular sale has been met.
Important distinctions
MitID is separate from Swedish and Norwegian BankID. A customer’s name or preferred language does not establish which electronic ID they hold. Explain the required method before checkout and provide an understandable route to help. IDguard currently offers MitID age verification for WooCommerce; its Swedish and Norwegian BankID integrations are under development. Other uses of MitID should not be interpreted as additional features of IDguard.
Sources
- MitID: About MitID Checked
- IDguard: BankID og nordiske eID’er Checked
These explanations were prepared with AI assistance and draw on the sources listed.