AgeOnce Docs
Dashboard

FAQ

Frequently asked questions about AgeOnce

Frequently Asked Questions

General Questions

What is AgeOnce?

AgeOnce is a biometric age verification service that allows websites and applications to verify user age without storing their personal data.

How does verification work?

  1. User is redirected to the AgeOnce page
  2. Grants camera permission
  3. System analyzes biometric data in real time
  4. Result is returned: age confirmed or not

Are photos or videos stored?

No. Biometric data is processed in real time and not stored. We only store the fact of successful verification.

How accurate is the verification?

Our system has over 95% accuracy for determining age category compliance (18+, 21+).

Integration

How long does integration take?

Basic integration takes from 30 minutes to a few hours depending on your stack:

  • WordPress — 5–10 minutes (ready-made plugin)
  • Node.js/Python/PHP — 30–60 minutes
  • Custom solutions — several hours

Is an SSL certificate required?

Yes. AgeOnce works only over HTTPS to ensure data security.

Can I test on localhost?

Yes, for development you can register https://localhost:3000/callback as redirect_uri. Make sure the local server runs over HTTPS.

What programming languages are supported?

AgeOnce provides a REST API that works with any language. We have examples for:

  • Node.js
  • Python
  • PHP
  • Go
  • Ruby
  • Java

Pricing

How much does AgeOnce cost?

See current plans and pricing: ageonce.com/pricing.

What happens when the limit is exceeded?

  • Free plan — verifications are blocked.
  • Paid plans — if Overage is disabled, verifications are blocked. If Overage is enabled, verifications continue at the overage rate ($0.02–0.04 per successful reverification).

Is there a free trial?

Yes, the Free plan is free forever with a limit of 100 verifications per month.

Security and Privacy

Does AgeOnce comply with GDPR?

Yes. We minimize data collection and do not store biometric information.

Who has access to verification results?

Only you (the client owner) have access to statistics and results. We don't share data with third parties.

Can users be identified by token?

No. The token contains sub: "anonymous" — we don't identify users.

Audit logs and compliance

How can I prove or check that a verification took place?

Each successful verification returns a Transaction ID (the same value as verification_id in the JWT). You can store this ID (e.g. in your order, database, or CRM). In the Dashboard Audit Logs you can search by this Transaction ID to see when and how the verification was completed — useful for compliance and support.

Where can I see all reverifications?

In the Dashboard you can open Audit Logs to see the full list of reverifications: successful and failed. You can filter and search by Transaction ID, date, and status.

Technical Questions

How long is age_token valid?

By default — 10 minutes.

Can the token be validated offline?

Yes. Use the JWKS endpoint to get the public key and validate locally.

What if the user closed the browser?

The session is lost. On the next visit the user must complete verification again (if you don't store the result in your database).

Are mobile browsers supported?

Yes. AgeOnce works in all modern browsers with WebRTC support:

  • Chrome (Android, iOS)
  • Safari (iOS)
  • Firefox (Android)
  • Edge (Android)

WordPress

What is the minimum WordPress version?

WordPress 5.0 or newer.

Does it work with WooCommerce?

Yes. The plugin has built-in WooCommerce integration for checkout protection.

Is it compatible with caching plugins?

Yes, but ensure that verification pages are not cached for unauthenticated users.

Troubleshooting

Verification doesn't work

  1. Check Client ID and Secret
  2. Ensure redirect_uri is registered
  3. Verify the site runs over HTTPS
  4. Check logs for errors

"Invalid state" error

State doesn't match. Possible causes:

  • Session expired
  • User opened verification in another tab
  • CSRF attack

Token doesn't validate

  1. Verify the token is not expired
  2. Refresh public key cache
  3. Ensure you're using the correct algorithm (RS256)

Support

How to contact support?

What is the response time?

  • Free plan: up to 48 hours
  • Starter/Pro: up to 24 hours
  • Enterprise: up to 4 hours (SLA)

Didn't find your answer? Contact our support — we're happy to help!

Error Codes

Complete list of AgeOnce API error codes

On this page

Frequently Asked QuestionsGeneral QuestionsWhat is AgeOnce?How does verification work?Are photos or videos stored?How accurate is the verification?IntegrationHow long does integration take?Is an SSL certificate required?Can I test on localhost?What programming languages are supported?PricingHow much does AgeOnce cost?What happens when the limit is exceeded?Is there a free trial?Security and PrivacyDoes AgeOnce comply with GDPR?Who has access to verification results?Can users be identified by token?Audit logs and complianceHow can I prove or check that a verification took place?Where can I see all reverifications?Technical QuestionsHow long is age_token valid?Can the token be validated offline?What if the user closed the browser?Are mobile browsers supported?WordPressWhat is the minimum WordPress version?Does it work with WooCommerce?Is it compatible with caching plugins?TroubleshootingVerification doesn't work"Invalid state" errorToken doesn't validateSupportHow to contact support?What is the response time?