YourID for business · Private beta

One tap to sign in. Only the data you asked for.

Add “Login with YourID” to your site with standard OpenID Connect. Your customers sign in with a passkey and approve exactly what you see — so you store less, and have less to protect.

Become a beta partner Developer docs →

Why YourID

Less to build. Less to store. Less to defend.

What changes when “Login with YourID” sits in front of your sign-in.

No passwords to store

People sign in with a passkey. There’s no password database on your side to hash, reset, rotate — or leak.

No sign-up form

New customers skip the account form. One approval and they’re in, with the details they chose to share.

Less data, less exposure

You receive only the claims you request and the person approves. Data you never receive can’t leak, and doesn’t widen your GDPR footprint.

Phishing-resistant sign-in

A passkey only works on the site it was made for, so a look-alike page has nothing to capture and replay.

Free for your customers

YourID costs people nothing. Nobody hits a paywall on the way into your service.

Plain OpenID Connect

Authorization code with PKCE and published keys. Any certified OIDC library works — or paste the drop-in script.

By sector

What you’d ask for — and what you’d never see.

Each sector needs something different. You request the minimum; the person approves it, claim by claim.

Age-restricted goods, without a birthdate on file

Selling wine, knives or fireworks? Ask one yes-or-no question — is this person over 18 — instead of collecting a date of birth. Add email for the order confirmation.

Verified age relies on identity-document verification (via iDenfy, EU), which is coming soon. Until then, age checks aren’t available in the beta.

Try the fictional demo →

You request

openidageemail

You never see

✕Their date of birth
✕A photo or scan of their ID
✕A password

Integrate

Live in three steps.

Standard OpenID Connect underneath. The drop-in script is the shortest path; any certified OIDC library works too.

Discovery document: https://yourid-web.vercel.app/.well-known/openid-configuration

app/developers

// yourid-web.vercel.app/app/developers → New app

App name        Your shop
Redirect URL    "https://your-shop.example/"
Client type     Public — browser, PKCE

✓ App registered
client_id       "yid_your_public_client"

// Server apps also get a client secret.
// Keep it on the server — never in the browser.

Dashboard view, simplified

Reference

Every claim, and the scope that unlocks it.

People see each item on the consent screen before anything is shared.

ClaimWhat it containsScope

sub
A stable pseudonymous identifier for this person. No personal data — use it as your account key.
Scopeopenid
name · given_name · family_name
Full, first and last name, from a verified identity.Needs ID verification — coming soon
Scopeprofile
birthdate
Date of birth, from a verified identity.Needs ID verification — coming soon
Scopebirthdate
age_over_18
true or false — over 18. Never the birthdate itself.Needs ID verification — coming soon
Scopeage
email · email_verified
Email address, and whether it has been confirmed.
Scopeemail
tier · verification_method
How the identity was verified. Sent along with profile, birthdate or age.
Scopeprofile | birthdate | age
personal: { … }
Fields from the person’s personal profile — only the ones they approve for you.
Scopeprofile:personal
business: { … }
Fields from the person’s business profile — only the ones they approve for you.
Scopeprofile:business

Built for revocation

People can change their mind. Plan for it.

Anyone can revoke your access from their YourID, at any time. Revocation stops your tokens immediately — so build for it from day one.

Treat a refused token refresh as a sign-out, not an error.
Key accounts on sub, not on email.
Keep what you need for your own obligations, such as an order, in your own system.

See it working