Pajic

ID · Digital identity

Sign in. Choose what you share.

Passkey-first authentication and identity verification using OpenID Connect. People approve scoped claims instead of sharing an entire identity profile.

A translucent identity card on a titanium platform
Concept imagery · product interfaces shown below

Authentication and consent.

ID separates signing in from deciding which information a service receives.

Passkey-first sign-in

WebAuthn passkeys provide the normal passwordless authentication path.

OpenID Connect

Services integrate through the Authorization Code flow, with PKCE S256 for public clients.

Scoped consent

The application asks for specific scopes. People see what the service requests before approving.

Selective disclosure

An age-check service can request an age signal instead of a full birth date or an entire profile.

Choose what the service requests.

This local example shows how the requested claims change. It does not sign you in or send identity information.

  1. The service requests scopes

    The application starts an authorization request with deliberately narrow scopes.

  2. The person signs in

    The user authenticates with ID and sees the application’s requested access.

  3. Consent controls disclosure

    After approval, the relying party receives the claims allowed by the request.

  4. The application validates the response

    The service checks the token signature and expected issuer, audience and flow context.

Integrate using OpenID Connect.

Discovery, PKCE and public keys

Start with the discovery document. Use Authorization Code with PKCE S256, keep scopes narrow, and validate RS256 signatures against the published JWKS.

The application remains responsible for its own authorization rules. Signing in does not automatically grant access to every resource.

Questions about ID

Does a service need my full identity profile?

No. Services can request specific claims. The age-check example uses an age_over_18 signal rather than requesting a birth date.

How do applications verify tokens?

ID publishes discovery and JWKS endpoints. Relying parties use the published keys to validate token signatures and their expected protocol context.

Is the example above a real verification?

No. It demonstrates scope selection in this browser. Use the linked product or demo to explore an actual integration flow.

Does ID replace my application?

No. It provides identity and authentication. Your application keeps its own product logic and authorization boundaries.

Get started

Use ID

Open the identity product to manage your account and sign-in experience.

Open ID

Developer documentation

Read about scopes, integration flows and relying-party setup.

Read the docs

Talk to
Pajic Systems.

Tell us what you need to build, connect or operate.

Contact Systems