Hopae Connect supports three eID types. Here’s the quick overview you can rely on during integration.Documentation Index
Fetch the complete documentation index at: https://docs.hopae.com/llms.txt
Use this file to discover all available pages before exploring further.
| eID type | Examples | Hopae role |
|---|---|---|
| Type 1: Centralized IdP | OIDC providers, national or customer IdPs | Relay (normalize + return original + evidence) |
| Type 2: Chip-based | Passport (ICAO 9303), eIDAS 1.0 card | Verifier (decode/decrypt, trust registry check, normalize + evidence) |
| Type 3: Wallet | EUDI / eIDAS 2.0 wallet, ISO 18013 mDL | Verifier (validate VP, trust registry check, normalize + evidence) |
Type 1: Centralized IdP
Hopae Connect integrates with centralized identity providers to authenticate the user in real time.- User: Completes OTP, PIN, ID/PW, or FIDO challenge at the provider.
- Hopae: Relays the provider response, normalizes attributes, returns original data + evidence.
Type 2: Chip-based
Chip-based credentials rely on NFC and trust registries to validate secure elements in documents.- User: Unlocks the chip (PIN or CAN) and scans the document via NFC.
- Hopae: Decodes/decrypts the payload, verifies status with ICAO PKD or eIDAS registry, normalizes data, returns original + evidence.
Type 3: Decentralized Wallet
Decentralized wallet flows use verifiable presentations from user-controlled wallets.- User: Approves in-wallet consent (PIN or biometric) after an OID4VP request.
- Hopae: Validates the presentation, checks registry status, normalizes data, returns original + evidence.