JavaScript (drop-in)
Add a script tag, no build step.
Redirect the user, get a code back, read age_verified. AgeWallet runs the selfie and ID checks and applies the law for each user’s location. You never handle a document or a date of birth.
If you have built “Sign in with” anything before, you already know this flow.
Redirect to /user/authorize with your client ID, redirect URI, PKCE challenge and state.
Face estimation with 3D liveness, or a government ID check, chosen by location and industry rules.
Your server swaps the one-time code for tokens at /user/token.
Call /user/userinfo with the access token and grant access only on age_verified: true.
The response tells you whether the user passed, and nothing you would then have to protect.
Full reference: Verify user age via UserInfo and Endpoints.
# Discovery: point your OIDC library here
https://app.agewallet.io/.well-known/openid-configuration
# After the code exchange
curl https://app.agewallet.io/user/userinfo \
-H "Authorization: Bearer $ACCESS_TOKEN"
{
"sub": 89,
"age_verified": true,
"expires_at": 1765035995,
"metadata": "order:XYZ-42"
} The SDKs handle PKCE, state and nonce validation and the token exchange. See SDKs & libraries.
Add a script tag, no build step.
Custom web flows.
No Composer required for the simple version.
Native Swift, Kotlin and Java.
Cross-platform mobile.
Point it at our discovery document.
On WordPress, Shopify or Telegram, skip the code entirely: use the WordPress plugin, the Shopify app or the Telegram bot.
Age limits and allowed methods per country and US state come from the Legal Matrix. When a law changes, your integration doesn’t.
Bind each flow with state, and pass an opaque metadata value such as an order reference that comes back in the result.
A failed request is never confused with an underage user. See handling responses & errors and the error reference.
Access tokens expire after 900 seconds. Read the result once, store your own decision, and nothing sensitive lingers.
Mobile SDKs use PKCE without a client secret, so no credential ships inside your app.
Join the AgeWallet developer Slack or message us on WhatsApp while you integrate.
No sales call to find out what it costs. Compare age verification providers.
It is a standard OpenID Connect authorization code flow. You redirect the user to AgeWallet, they verify their age, AgeWallet sends them back with a one-time code, and your server exchanges the code for tokens and calls /userinfo to read the result.
The /userinfo endpoint returns age_verified (true or false), a stable user identifier (sub), an expiry timestamp (expires_at), and any metadata string you sent with the request. It never returns a date of birth, name or document.
No. Any OAuth 2.0 or OIDC library that supports discovery can connect using https://app.agewallet.io/.well-known/openid-configuration. Official SDKs for JavaScript, PHP, WordPress, iOS, Android, Flutter, React Native and Ionic handle PKCE, state and nonce for you.
Yes. The iOS, Android, Flutter, React Native and Ionic SDKs run as public clients with PKCE, so no client secret is stored in the app.
Bind the flow to your own user or session with the state parameter, and optionally attach an opaque metadata string, such as an order reference, on the authorization request. AgeWallet returns it unchanged in the /userinfo response.
$0.30 per completed verification and $0.008 per user authorization, with no setup fee or monthly minimum. API access and the SDKs are included, and new accounts start with $5 of credit to build and test.
AgeWallet chooses the method for each user from their location and your industry settings: facial age estimation with 3D liveness, falling back to a government ID check when needed, or ID straight away where the law requires it. Your integration code stays the same either way.
Register, create a client, and point your OIDC library at our discovery document. Your first $5 of verifications are on us. Want the bigger picture first? Read about the AgeWallet age verification service.