Overview
Hopae scores assurance on one comparable scale: the Hopae Level of Assurance (HLoA), from 1 to 4, defined by the Hopae Global Assurance Framework. It is built on the NIST and eIDAS standards and calibrated so that HLoA 4 equals eIDAS High. Hopae returns three fields:hopae_loa— the level, 1–4, for programmatic checkshopae_loa_label— the level’s label (none,low,substantial,high)acr— theurn:hopae:loa:{level}URN, present when the provider determined the level
LoA levels
The framework scores each eID on two independent axes, identity proofing (how carefully the person was checked) and authentication (how securely they sign in), and the weaker of the two decides the level. See the framework document for the scales and the eID map.
Specify LoA in requests
Request a minimum LoA when initiating verification:- OIDC
- REST API
Add See acr_values format for additional options including provider filtering.
acr_values query parameter:failed (see Error handling).
Error handling
Provider does not support the requested LoA Returns an error before authentication begins:- OIDC: Error callback redirect
- REST API: HTTP 422
- The user chooses a weaker authentication method than expected
- The provider downgrades the session due to fallback mechanisms
failed, but you can still retrieve user data via the /userinfo endpoint.
This allows you to decide how to handle the situation
Response example
LoA fields are included in both ID Token and UserInfo responses:See also
- Hopae Global Assurance Framework — the full framework and the eID map
- OIDC Integration Guide —
acr_valuesparameter usage - REST API: Create Verification —
requestedLoafield

