Trust the session.
Receive a stable private subject, fresh authentication context, and approved profile fields.
Know it’s a person. Keep their identity private.
Add verified human sign-in that recognizes returning customers, provides recent authentication context, and shares only the details they approve.
A clear way in.
They see your application, its purpose, and every requested detail before anything is returned.
Why Identity
Give real customers a smoother way in and your application a stronger reason to trust the session.
Your application gets
Verified human sign-in
Recognize a verified person with a stable subject created only for your application.
Fresh authentication context
Check when and how the person authenticated before allowing a sensitive action.
Approved profile details
Request name, email, or Persona fields and receive only the fields the person approves.
Session controls
Introspect or revoke an opaque, application-bound session from your server.
The person keeps
A private relationship
The person has a different subject in every application. No global SupahID crosses the boundary.
Their evidence
Document images, selfie details, biometrics, reports, and canonical identifiers never enter your application.
An exact choice
Required and optional details stay visible, and only approved fields are returned.
No silent renewal
There is no refresh token. A new application session brings the person back into the flow.
Integration
From sign-in to trusted session.
A familiar authorization flow, with human verification and consent already built in.
- 01
Register your application
Set the domain, exact callbacks, purpose, and requested details.
- 02
Create the request
Use PKCE and a pushed request so sensitive parameters stay out of the browser.
- 03
Let the person decide
SupahID signs them in and shows the required and optional details.
- 04
Receive the session
Exchange once for an ID token and an opaque session bound to your application.