> ## 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.

# Types of eID

> Overview of eID types supported by Hopae Connect: Centralized IdP, Chip-based, and Decentralized Wallet.

Hopae Connect supports three eID types. Here’s the quick overview you can rely on during integration.

| 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.

```mermaid theme={null}
flowchart LR
  U[User] -->|Request| P[Platform]
  P -->|Request| H[h.Connect]
  H -->|Request| I[ID Provider]
  I -->|Generate Response + evidence| H
  H -->|Normalized Result| P

  classDef node fill:#ECECEC,stroke:#222,color:#111;
  class U,P,H,I node
```

### 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.

```mermaid theme={null}
flowchart LR
  U[User] -->|Request| P[Platform]
  P -->|Request| H[h.Connect]
  H -->|Scan NFC| C[Passport or ID]
  C -->|Return Response| H
  H -->|Verify Remote| T[Trust Registry<br/>ICAO PKD / eIDAS]
  H -->|Normalize Response + Generate Evidence| P

  classDef node fill:#ECECEC,stroke:#222,color:#111;
  class U,P,H,C,T node
```

### 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.

```mermaid theme={null}
flowchart LR
  U[User] -->|Request| P[Platform]
  P -->|Request| H[h.Connect]
  H -->|Request OID4VP| W[Wallet]
  W -->|Generate Response| H
  H -->|Verify Remote| T[Trust Registry<br/>eIDAS 2.0 Registry]
  H -->|Validate Response + Generate Evidence| P

  classDef node fill:#ECECEC,stroke:#222,color:#111;
  class U,P,H,W,T node
```