Overview
AgeWallet adds age verification to your app using standard OpenID Connect. Use your preferred OAuth/OIDC library, or one of ours, and be production-ready in an afternoon.
How a verification works
- You redirect the user to AgeWallet with an authorization request.
- They verify their age with us. You never see a document or a date of birth.
- We redirect them back to you with a one-time code.
- Your server exchanges that code for tokens, then calls
/userinfoto get the result: verified, or not.
Four steps, three of which are ordinary OIDC. If you have integrated “Sign in with” anything before, this will look familiar.
Two ways to integrate
| Use this when | Start at | |
|---|---|---|
| AgeWallet SDK | You are on a platform we ship an SDK for — JavaScript, WordPress, PHP, iOS, Android, Flutter, React Native, Ionic. | SDKs & libraries |
| Any OIDC library | You are on another stack, or you already have an OIDC client in the app. | Endpoints |
Before you start
- An AgeWallet account — see Account Creation.
- A registered client, which gives you a
client_idandclient_secret. - A callback URL on HTTPS that you can register exactly.
- A server you can make requests from. The token exchange carries your client secret and cannot run in a browser.
Start here
New to AgeWallet: start with Account Creation, then Register Your Client.
Already have credentials: go straight to Endpoints and point your library at our discovery document.
If you need assistance with integration, please join the AgeWallet Developer Slack Channel or contact us on WhatsApp.