Age verification for existing users: are your controls keeping up?

TL;DR: Existing-user age verification is now a separate compliance problem because regulators in Australia and the UK treat self-declaration as insufficient and frame the duty around account holders already on the books, according to OneID. The operational challenge is not sign-up screening but migrating a live base with data-quality, completion-rate and churn constraints.

Editorial analysis by NHI Mgmt Group, based on content published by OneID: “Age verification for existing users: the back-book problem”.

Key questions

Q: How should teams verify existing users without creating unnecessary churn?

A: Design the process as a staged migration, not a blanket re-registration exercise.

Q: Why do self-declared ages fail as a control for existing accounts?

A: Because a self-declaration records a claim, not evidence.

Q: What are the signs that a back-book verification programme is failing?

A: High support contact, low completion, repeated retries and a large unresolved cohort are the clearest signs.

Practitioner guidance

• Define a back-book remediation scope Separate existing users from new sign-ups, then size the older population that still lacks durable age evidence.
• Audit the quality of held identity data Sample existing account records for completeness, consistency and matchability before choosing verification methods.
• Offer multiple verification routes Provide more than one way to complete age assurance so users who already hold a usable credential can clear the process quickly.

Bottom line: Existing-user age verification is a migration problem because it has to reach accounts already on the books, not just new sign-ups.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →