Skip to content

Developers

Build in digital identity.

Let users sign in with a wallet, request verified data or issue digital credentials. Choose your integration and continue with the product documentation.

Open the documentationSign in to Studio

Which task are you integrating?

Configure the flow in Studio. The Ver.iD Gateway guides the user through the wallet interaction. Your application processes the result for your task.

Sign in with a wallet

Authentication through OpenID Connect, for login to your own application.

Authentication guide

Ver.iD handles

The wallet interaction and a signed ID token. The separate access token grants access to UserInfo.

Your application handles

Use a maintained OIDC client with Authorization Code and PKCE. Validate the ID token before creating a user session.

Request data

A disclosure requests selected data, for example during onboarding. Its result is not a login token.

Disclosure guide

Ver.iD handles

The data request, the configured mapping and a signed disclosure result.

Your application handles

Choose the browser SDK for a browser flow or the Node.js SDK for server processing. Check the callback and verify the result before using the data.

Issue digital credentials

Issue a digital credential to a wallet configured for your issuance flow.

Issuance guide

Ver.iD handles

The defined structure, the wallet interaction and a signed issuance result with a run ID.

Your application handles

Validate values on your server and create an issuance intent for that run. Use a confidential server client and associate the verified result with your transaction.

Set up access and configuration.

Studio access follows a review and an invitation. An account does not automatically grant sandbox or production access. Agree on the environment, usage and terms for your application.

How to request Studio accessA tailored proposal
Organisation, domain and brand
Arrange access to the right organisation, an active domain and an active brand. These determine where results may be sent and which organisation the user sees.
An available wallet and flow
Choose a wallet offered in Studio for your organisation and task. Test support does not mean production support. Make sure the wallet can share the requested data, and activate the flow.
Issuer, client ID and redirect URI
Copy the issuer URI and client ID from your active flow’s Configuration tab. Register your application’s exact redirect URI. The SDK discovers the endpoints through the issuer.
Secrets and flow context
Keep client secrets on your server. Store state and PKCE context for the callback; use shared storage across server instances. Keep tokens and personal data out of logs.

Request one attribute. Inspect the result.

Start with the disclosure exercise in the product documentation. With Studio access and an available wallet, you can follow the interaction before writing application code.

  1. Create a small disclosure

    Open Verify → Disclosures in Studio. Choose one wallet and one available attribute, attach your active brand and set the test callback. Activate the disclosure as described in the guide.

  2. Start the test from Studio

    Click Test on the active disclosure. The OAuth Debugging Tool fills in the issuer and client ID. Leave optional intent fields empty, click Send request and complete the selected wallet flow.

  3. Check what comes back

    After a successful flow, the tool shows the OAuth response and decoded JWT. Compare the shared attribute with your configuration and mapping, if configured. This is the first result of the exercise.

Guide: configure a disclosureNext: connect your application

Callback for this exercise

Select test.ver.id under Redirect URIs. Studio sets HTTPS, port 443 and the callback path for the debugging tool.

Registered redirect URI
https://test.ver.id/disclosure/callback

This callback belongs to the test tool. Register your own exact redirect URI for your application. Only use data you are allowed to share for the test.

No result?
  • Check that the disclosure is active, the redirect URI matches exactly and the selected wallet holds the requested attribute.
  • If the wallet interaction fails or is cancelled, the tool shows the returned OAuth error. Treat it as a failed or cancelled flow.
  • In your own application: check the callback with finalize and verify the disclosure JWT with decode and assertDisclosureV1JwtPayload, as described in the SDK guide.

OAuth Authorization Code + PKCE. Based on the Studio guide, consulted on 1 October 2026.

Source: Test a disclosure

Keep building, look things up or get help.

The technical sources contain full configuration details, examples and response formats. The linked documentation is in English.

  • TypeScript SDK and examples

    Maintained browser and Node.js clients, sample apps and per-package changelogs. The SDK is pre-1.0: pin your chosen version and read the migration instructions when upgrading.

  • GraphQL API

    Read platform data and manage your organisation. The guide covers client roles, authentication and the public schema. Keep the client secret in your backend.

  • Wallets and availability

    Check each wallet’s current test or production status and the guide for your flow. Studio shows the options for your organisation.