E-ID, Wallets, and Verifiable Credentials
Nevis ID acts as verifier and relying party for government and third-party digital identities: a user proves who they are with a credential held in their own wallet, and Nevis ID turns that proof into a sign-in or a new account. Shipped verifier integrations cover the Swiss E-ID (swiyu), the Signicat e-ID and walt.id. Credential issuance, wallet apps, and decentralized identifiers (W3C DID) are delivered by those partners and by the e-ID schemes themselves, not by Nevis ID. Just-in-time account creation and account linking bind a verified e-ID to a Nevis ID account, so an e-ID serves both onboarding and everyday sign-in; bring-your-own-identity through a government e-ID is also covered under Federation and SSO.
Also known as
decentralized identity, verifiable credentials, OID4VC, EUDI wallet, Swiss e-ID (Swiyu), eIDAS, W3C DID, government-eID BYOI.
At a glance
| Capability | Delivery | Details |
|---|---|---|
| Swiss E-ID (swiyu) | Native | Verifier integration for the swiyu wallet app: the user scans a verification QR code and presents the credential. The Swiss E-ID is in public beta, and your organization must be registered in the swiyu trust infrastructure (sandbox) |
| Verifier hosting | Native | The swiyu verifier service runs in the Nevis environment by default; the verifier containers and database can be hosted in your own environment as an alternative |
| walt.id | Example integration | Verifier integration with walt.id, an open source decentralized identity and wallet provider |
| Credential issuance | Partner-delivered | Credentials are issued by the e-ID scheme or the wallet provider. Nevis ID does not issue credentials |
| Wallet app | Partner-delivered | Users hold credentials in their own wallet, such as swiyu or walt.id. Nevis ID ships no credential wallet; the Nevis Access App is an authenticator, not a wallet |
| Account binding (BYOI) | Native | Just-in-time account creation for a first-time e-ID user, and linking an e-ID to an existing account; see also Federation and SSO |
| E-ID as a login method | Example integration | E-ID sign-in appears as a button on the login screen and is configurable per deployment |
| Identity verification through an e-ID | Example integration | An e-ID login can front registration and onboarding; see also Registration, Onboarding, and Identity Verification |
| eIDAS and EUDI wallet alignment | Partner-delivered | Reached through the integrated providers: Signicat conforms to EUDI wallet regulation, walt.id builds on EUDI wallet infrastructure |
| Protocols | Native | OpenID Connect and OAuth 2.0 toward the e-ID provider; the Signicat hub additionally offers SAML 2.0 and a REST API |
| Audit of e-ID logins | Native | E-ID sign-ins are recorded like other authentication events; see Reporting, Analytics, and Audit for retention, export, and SIEM ingestion |
Concepts
- Digital identities (e-ID): what wallet-based digital identity means for a relying party, and the three integrations Nevis ID ships out of the box
How-to Guides
- Integrate the Swiss e-ID: obtain a Beta-ID, hold it in the swiyu wallet, and verify it against Nevis ID
- Integrate the Signicat e-ID Hub: register the OIDC client and wire the client ID, client secret, and provider endpoint
- Integrate walt.id: issue a test eID credential into a walt.id wallet and verify it
- Manage secrets: hold e-ID provider credentials as environment-scoped secrets
References
- E-ID verification patterns: Swiss eID Login Step, WaltID Step, Generic Social Login Step
- Account binding patterns: Social Login Create User, Social Login Link User, Social Login Done
- System overview: architecture, endpoints, and environments
- Data model: how a verified identity is stored on the user