Skip to main content
OIDC if you want Hopae to host the verification screens (fastest). REST if you need your own UI. See Choose an Integration.
Developers → API Settings of the app: the App ID and App Secret. Sandbox and production apps have separate credentials. See Authentication.
Use the other app’s credentials. The URLs are the same. See Apps & Environments.
One credential through one provider, such as Smart-ID or a US mDL in Google Wallet. See Connections.
Direct: immediately. Registration: in production, once Hopae has completed the setup with the identity provider; instant in Sandbox. Contract: after an onboarding call, once Hopae has what it needs from you and has completed the setup. See Activate Connections.
It is not available for this app’s environment, for example a production-only connection in a sandbox app.
Activate a connection and enable it in the workflow you run. See Workflows.
On the workflow’s Claims tab. On REST, requestedClaims in Create Verification replaces those claims for one verification. See Workflows.
Tick Source ID on the workflow’s Claims tab and read user.source_id. It is stable only on the same connection, so store it together with the connection. See Source ID.
disclosure returns the user’s attributes. match confirms values you sent. See Verification Model.
Check the level after the verification: read hopae_loa on your server, or add a check-min-loa node on the workflow’s Flow tab and read metLoa. The verification completes even when the level is lower, and the node doesn’t block it. acr_values (OIDC) and requestedLoa (REST) only ask the provider for a level, and only a connection that supports the level accepts them. They don’t check the result. On OIDC, acr_values also limits the offered connections and can end the authorization with invalid_request, so don’t send it to require a minimum. See Assurance.
Use the credentials of the app that created it. Another app’s verification, or one past its expiresAt, returns 404. See Expiry.
Use a sandbox app and, where a provider needs it, request test credentials under Tester Info. See Sandbox Testing.
Yes. It uses real credentials and real provider traffic. See Go Live.
No. Hopae is API-first: your backend calls Hopae and your app performs the user step. See Mobile App Integration.
Yes. See Custom Domain.
Still stuck? Email support@hopae.com.