Register Your Client
Create a new client to obtain your client_id, client_secret, and register your exact redirect_uri.
A client allows your site to securely communicate with AgeWallet through encrypted OIDC keys.
If you run multiple sites, you may create multiple clients; however, for most sites you will only need one client.
Client settings
When you create or edit a client in the AgeWallet dashboard, you will see the following fields.
| Field | What it does |
|---|---|
| Kind | The type of integration, for example Website or app. This is fixed once the client is saved. |
| Name | A label for your own reference, such as “My Membership Portal” or “iOS App”. Users do not see it. |
| Redirect URI | Where AgeWallet sends users after they verify. It must exactly match the redirect URI your application listens on, and it must use https. |
| App interaction | Whether users must, may, or don't use the AgeWallet app. See App interaction below. |
| Industry | Sets the age verification rules applied in each region. See Industry below. |
| Confidential Client | Turn this on if your integration can securely store a client_secret. See Confidential or public? below. |
App interaction
The App interaction dropdown controls whether your users verify through the AgeWallet app. There are three options.
Require App
Users must use the AgeWallet app to complete verification. They verify their age once, and the app stores the result on their device. On later visits they scan the QR code and use their locally stored key, so they skip full verification.
This suits businesses with transient visitors who come and go, because returning users are not asked to verify again. It also reduces your costs, since repeat visits do not trigger a new full age verification charge.
Bypass App
Users verify in the browser and do not need to download the AgeWallet app. This has the least friction for first-time users, but each full verification is charged as normal.
Allow Users to Choose
Users can either verify with the AgeWallet app or verify in the browser without it. This is the most flexible option: users who install the app save you future re-verification fees, and users who don't want to download an app can still verify without friction.
| Option | App download | Returning users | Best for |
|---|---|---|---|
| Require App | Required | Scan the QR code with their stored key; no full re-verification charge | Repeat or transient visitors; lowest ongoing cost |
| Bypass App | Not needed | Verify again when required | Lowest friction for one-time visitors |
| Allow Users to Choose | Optional | App users skip full re-verification; others verify again | Most sites; balances cost and friction |
Industry
The Industry dropdown tells AgeWallet which age verification rules to apply. Requirements are set by region, based on where the user is located: in a region that regulates your industry, the user verifies using the age and method that the region requires.
If the user is located in a region that does not regulate your industry, they are not required to verify their age.
View locations and verification methods by industry
The map shows, for each industry, which locations require verification, the minimum age, and the method users verify with.
Confidential or public?
A confidential client runs on a server you control and can keep a secret — a web backend, an API. It uses client_secret. Turn on Confidential Client for this kind of integration.
A public client cannot keep a secret because its code ships to the user — a single-page app, a mobile app. It omits client_secret and relies on PKCE. Leave Confidential Client off for browser-based or client-side flows.
If you are unsure, you are almost certainly building a confidential client.