MitID integration in your own app: broker, price and white-label

That is the sentence most SME owners need. The rest of this page is the three models you can actually buy, and what they typically cost. Ceptiv builds MitID white-label into custom apps.

The three MitID integration models

Model C is under-explained because it only exists if you are building a system anyway. That is why you will not find it on the brokers’ own sites.

What MitID actually is (without the official jargon)

MitID is Denmark’s digital ID. More than 4 million Danes use it. It replaced NemID. It can prove who signed in (authentication), sign something legally binding (signature), and confirm age or identity in a flow you define.

MitID Erhverv is the business variant — login and actions on behalf of a company. Private MitID and MitID Erhverv are not the same product, and the price per transaction is not the same at the brokers either.

eIDAS is the EU framework that makes certain electronic signatures recognised across countries and, ultimately, in court. “We have a checkbox in a PDF” is not an eIDAS-compliant signature.

You almost never need to be the broker yourself

A MitID broker is certified in the public MitID setup. The broker pays a transaction fee (AAP) to the MitID core and resells access to you. Public figures from MitID Broker (from 1 July 2026) show the core itself costs øre per authentication request — plus broker certification in the tens and hundreds of thousands. That is why you do not “just turn on MitID” in a WordPress plugin.

List prices on the broker layer typically look like this (public Criipto/Idura-style figures, 2025–2026):

• Onboarding / setup: often around 1,200 DKK at some brokers, much more if you certify yourselves
• MitID login: on the order of 0.28 DKK per authentication plus the broker’s own subscription
• MitID Erhverv: higher per login, publicly shown around 0.75 DKK at least at one broker
• Building the full broker stack yourselves: often from about 50,000 DKK to establish plus several thousand a month — which is why SMEs do not do it

Prices move. Always check the broker’s current page. The point is the structure: core fee + broker layer + your own development work.

What the business must decide first

Before a developer writes a line of code, leadership should answer five questions:

1. Should the user sign in, sign a document, or both?
2. Are the users private individuals, staff acting for a CVR, or both?
3. May the user leave your screen? (Many drop off mid-redirect.)
4. Who owns the evidence afterwards — the PDF, the log, the timestamp, the MitID transaction id?
5. Is this a legal requirement (contracts, age check, authority) or “it will look professional”?

If the answer to 5 is the last one, consider model A. If the answer is a legal requirement and you have a custom system, model C is almost always right.

White-label vs “we call Penneo in an iframe”

Iframe / redirect: the user sees another brand, sessions die, support lands on you even when the fault sits in the SaaS tool, you pay per signature for life, and the document data lives outside.

White-label in your own system: the same colours, the same URL, the same receipt. The signature is a step in your flow — like “pay” or “approve order”. You store evidence in your own database. You pay to have it built, not per click afterwards (apart from any MitID core fee).

That is why white-label wins in products where a signature is not an occasional PDF but part of the core: leases, memberships, trades quotes, consent, onboarding of business customers.

What does it cost to put MitID in a custom system?

There are three lines on the budget. Quotes often mix them.

• Line 1 — broker / eID fee. Øre to a few kroner per login or signature, plus maybe a small setup. You cannot negotiate this away. It is infrastructure.
• Line 2 — building the flow in your app. Button, redirect or embedded flow, error handling (“the user closed the app”), receipt, log, admin view. In a system where the vendor has done it before, this is one integration in a package — not an 80,000 DKK project on its own.
• Line 3 — operations. Key rotation, broker updates, monitoring failed logins, the audit trail.

If you are already building a web app at a fixed price, MitID is typically one of the integrations, not the whole project. See packages and what custom software costs. If you only need MitID and you are otherwise done in WordPress, buy a finished SaaS. Do not hire a studio to save 8 DKK per signature if you sign 20 documents a year. When the signature should trigger an invoice, e-conomic or Dinero belongs in the same flow.

Use cases that actually pay for themselves

• Trades: the customer accepts the quote in your portal. Not print-and-scan.
• Lettings / membership: the contract is signed before a key or access is handed over.
• B2B onboarding: you know it is the authorised signatory, not an intern.
• Age gating: you sell something the law requires you to know the age for.
• Internal approval: the board signs without mailing PDFs around.

If your case is “we want MitID on the homepage because it looks Danish”, skip it. That is a fee and a support problem with no business effect.

Security and compliance without the scare campaign

You must be able to answer: where does the evidence live (hash, timestamp, broker transaction id, document version)? Who can access it? How long do you keep it, and why (GDPR storage limitation)? What happens if the broker is down? Your flow should fail cleanly, not in the middle of a payment.

eIDAS and “accepted by Danish authorities and courts” is exactly why companies pick MitID over a checkbox and a photo of a passport.

Typical mistakes in MitID projects

1. You start in the broker dashboard before you have drawn the user journey.
2. You mix private MitID and MitID Erhverv in the same sentence in the spec.
3. You forget test users. You cannot use your own MitID 400 times in UAT without a plan.
4. You build the signature but forget to lock the document. The signature is then tied to the wrong version.
5. You promise “unlimited signatures” without reading the broker’s transaction price.

What to do now

Write two sentences: “The user must [sign in / sign / both] because [law / risk / conversion].” And: “The user [may / may not] leave our screen.” With those two sentences a studio can tell you whether to buy Penneo, a broker login, or have it built in. MitID and digital signature.