MitID Test Tool

The MitID test tool lets you simulate a complete verification flow without a real MitID account. It is the only way to test in test mode — real MitID accounts cannot be used with test API keys.

Important: Test keys (pk_test_) only work with the MitID test tool. Production keys (pk_live_) only work with real MitID accounts. They are not interchangeable.

Step 1 — Create a test identity

Go to pp.mitid.dk/test-tool/frontend/#/create-identity.

Fill in the identity details. The most important field for age verification is the date of birth — set this to control whether the test identity passes or fails your age check.

For example:

• To test a passing verification with minAge: 18, set a birth date more than 18 years ago
• To test a rejection, set a birth date less than 18 years ago

Save the identity. You will need the identity ID or the user details in the next step.

Step 2 — View the identity and open the app simulator

Go to pp.mitid.dk/test-tool/frontend/#/view-identity and open your test identity.

From here you can launch the app simulator — a popup that mimics the MitID mobile app. When a verification flow is waiting for app confirmation, you open this simulator and approve or reject the request, exactly as a real user would do on their phone.

Keep this tab open while testing. When a verification is triggered from your integration, the simulator will receive the push notification automatically.

Full test flow

1. Create a test identity with the age you want to test
2. Trigger a verification from your integration using your pk_test_ key
3. You are redirected to the MitID test environment
4. Enter the test identity credentials on the MitID test page
5. Switch to the app simulator popup and tap Approve
6. You are redirected back to your integration with the verification result
7. The event appears in Account → Events marked as a test

Tips

• Create multiple identities with different birth dates to cover all your test scenarios
• You can reuse the same test identity across multiple test runs
• The simulator can be opened at any time — it reacts to live events as they arrive, so you can keep it open permanently while developing
• If the simulator does not receive a notification, check that you triggered the request using a pk_test_ key against the test endpoint