Skip to main content
A sandbox app runs verifications with test identities. No real eIDs, no real users, no billing.
1

Create a sandbox app

In the Console, create a sandbox app. Quickstart activates the sandbox connections and creates a default workflow. Start from scratch leaves the setup to you.
2

Activate connections

Under Configuration → Connections, activate what you need. In Sandbox nothing waits for a review: see Activate Connections. Use Sample Fill to complete company forms with demo values.
3

Request test credentials (only if a provider needs them)

Some providers only work with a registered test identity, such as a demo-app account or a whitelisted phone. Add a tester under Verification → Tester Info: name, an app-store email per device, phone, and photo. Hopae requests the credentials for you.
Provisioning can take several days. Request credentials early.
4

Follow the Testing Guide

Open a connection in the Connections table and switch to its Testing Guide tab. It lists what the provider needs and how to run a test.
5

Run a verification

Open the workflow’s verification link (Verification → Workflow), or call your own integration with the sandbox app’s credentials. The hosted flow shows a Sandbox Mode banner. For connections with a Testing Guide, its Tester Info button opens it.

​
What to test

  • Success, user cancellation, provider failure, and expiry (30 minutes)
  • Redirect URIs, state and nonce handling (OIDC)
  • The claims you requested, including missing_claims
  • Webhook delivery and duplicate handling
Tester Info and Testing Guides exist only in Sandbox. A few connections exist only in Sandbox (for example dk-altid-eudi-pid). The Connections table marks them Sandbox Only.
Next: Go Live.