Pseudonymous Mode Integration

🚧 Note: Under Construction

Heads up: Pseudonymous Mode is still a work in progress. We're actively developing this feature, and it may change significantly before its official release. Expect possible bugs, incomplete functionality, or design tweaks as we refine the user experience.

Pseudonymous Mode lets you integrate Veros as a login or verification provider using an OAuth-style flow. Instead of exposing biometric data or raw user IDs, Veros issues a secure, app-scoped external_user_id for each user. This lets you identify and re-verify users across sessions — while keeping all sensitive information with Veros.

---

When to Use This Mode

Use Pseudonymous Mode if your app:

• Needs a persistent identifier for each user (to link accounts, track activity, or manage rewards).

• Wants a familiar OAuth-like login flow for smoother onboarding.

• Doesn’t need zero-knowledge proofs for anonymity.

For apps that need maximum privacy with no persistent IDs, use Anonymous Mode.

How It Works

The flow follows the OAuth 2.0 pattern:

1. Partner App redirects the user to Veros Connect with:

   • client_id, redirect_uri, and optional external_user_id (for re-verification).

2. Veros Connect frontend displays a QR code for the user to scan with their Veros App.

3. Veros App verifies the user’s palm, confirms identity, and links (or creates) an external_user_id.

4. Veros generates a short-lived AUTH_CODE and completes the session.

5. Partner App receives a redirect with code and exchanges it for the external_user_id as well as access tokens via token exchange.

Endpoints

• GET https://connect.veros.xyz/api/v1/oauth/authorize – Start connection/verification.

• POST https://connect.veros.xyz/api/v1/oauth/token – Exchange auth code for access token, id token and optional refresh token, this allows partner app to retrieve user id.