There is no single best age verification provider for every site. The best age verification provider for you is the one whose methods are accepted in every country you serve, that is independently certified, that your users actually complete, and that keeps as little personal data as possible. Price matters, but a cheap check that fails a regulator's review or loses half your traffic is the most expensive option of all.
This guide gives you a practical buyer's checklist, the questions to put to vendors, and a simple scoring method for an age verification vendor comparison. For listings, see our compliance and verification services directory.
General information, not legal advice. For high-risk decisions, take advice from a lawyer who knows your markets.
Start with your markets, not the vendor
Before you speak to anyone, write down where your traffic comes from and which rules apply there. A UK-only site needs a method mix that meets Ofcom's "highly effective" standard. A site with significant French, Italian or German traffic faces additional technical requirements:
- France: Arcom's technical standard requires at least one "double anonymity" option, where the age provider does not know which site the proof is for and the site does not learn who the user is.
- Italy: AGCOM requires checks by independent, certified third parties using a double-anonymity model, repeated at each access.
- Germany: the KJM assesses age verification systems for closed user groups, which need reliable identification and authentication at each use.
- EU platforms: the DSA Article 28 guidelines expect independent, audited age verification for adult content.
With that list in hand you can rule vendors in or out quickly. Our guide to age verification laws in Europe summarises each country.
The age verification vendor checklist
1. Regulator acceptance in each country
Ask which regulators have assessed, approved or listed the vendor's methods, and get evidence: a link to a KJM assessment, an Arcom-compliant double-anonymity flow, or a description of how each method meets Ofcom's four criteria (technically accurate, robust, reliable and fair). "Compliant across Europe" with no detail is a warning sign.
2. Age assurance provider certification
Independent certification is the quickest way to check a vendor's claims. Relevant standards include:
| Standard or scheme | What it covers |
|---|---|
| PAS 1296:2018 (BSI) | UK code of practice for online age checking, long used as the baseline for UK certification |
| IEEE 2089.1 | Framework for online age verification |
| ISO/IEC 27566-1:2025 | International framework for age assurance systems, including core principles and performance assessment |
| ISO/IEC 27001 | Information security management; important because the vendor handles sensitive data |
Certification bodies such as the Age Check Certification Scheme (ACCS) audit providers against these standards. Ask for the certificate, its scope (which methods and which version of the product) and its expiry date.
3. Method mix
A single method will not serve every user or every country. Look for a vendor that offers several of the following and lets you choose the order by country:
- facial age estimation with liveness detection and a configurable challenge age;
- photo ID matching with document fraud checks;
- open banking, mobile operator and credit card checks for UK users;
- a double-anonymity flow for France and Italy;
- reusable age verification, such as a token or wallet credential, so returning users skip a fresh check.
See age verification methods compared for the strengths of each.
4. Accuracy and fairness evidence
For estimation methods, ask for the false-accept rate for under-18s at your challenge age, split by age, sex and skin tone, from independent testing where possible. For document checks, ask about fraud detection and the share of genuine users wrongly rejected. Ofcom's July 2026 report on age assurance recommends regular due diligence on vendors, so plan to repeat these questions every year.
5. Data handling
The vendor will usually act as your processor, and sometimes as an independent controller. Either way you need clear answers on:
- exactly what data is collected and how long it is kept (images should normally be deleted straight after the check);
- where data is processed, and the transfer safeguards if it leaves the UK or EEA;
- whether your site receives anything beyond a pass or fail result;
- sub-processors, security testing and breach notification terms.
Our guide to age verification and GDPR explains what your contract and privacy notice need to say.
6. Integration and the age verification API
Ask how the check is delivered: a hosted page you redirect to, an embedded widget, a mobile SDK or a server-side API. Check:
- how your server receives and verifies the result (signed tokens or server-to-server callbacks, not a client-side flag that a user could fake);
- session and re-check handling, including Italy's per-access requirement;
- geo-targeting support so each country gets the right flow;
- uptime commitments, status pages and what happens to your site if the vendor goes down;
- dashboards and exportable logs you can show a regulator.
7. Pricing and contract terms
Compare the full cost, not the headline per-check price: minimum monthly commitments, set-up fees, charges for failed or abandoned checks, fees per method, and the price of reusable tokens. Our age verification cost guide breaks down the models. Also check notice periods and data export on exit, so you can switch vendor without a gap.
A simple scoring method for comparing vendors
Turn the checklist into a score so the decision is defensible and documented. One approach:
- Treat regulator acceptance in your key markets and certification as pass or fail gates. Any vendor that fails is out.
- Score the remaining vendors from 1 to 5 on method mix, accuracy evidence, data handling, integration and price.
- Weight the scores to your business. A site with mostly mobile UK traffic might weight completion and method mix most heavily; a multi-country platform might weight country coverage and data handling.
- Run a paid pilot with your top two on a slice of real traffic and compare completion rates before signing a long contract.
Keep the paperwork: your vendor comparison, pilot results and reasons for choosing a method are exactly the evidence a regulator asks for. Under the UK Online Safety Act, adult content providers must keep a written record of the kinds of age assurance they use and how they use them.
Questions to ask on the first sales call
A 30-minute call with these questions will tell you more than a stack of brochures. Ask for written answers afterwards so you can compare like with like.
- Which adult sites of a similar size and audience to ours use you, and in which countries? You are not asking for client names, just evidence they understand adult traffic.
- What completion rate do comparable clients see for each method? Ask how the figure is defined: share of users who start a check and pass, or share of all visitors.
- What is your false-accept rate for 16 and 17-year-olds at a challenge age of 21 and 25? A vendor that cannot answer has not tested properly.
- Which data do you keep, for how long, and in which countries? The answer should match the contract and their privacy notice.
- How do you handle a user who fails? Look for clear retry rules, alternative methods and a route to challenge an incorrect result, which France's standard requires.
- How do we prove the check happened? You need logs that show a check took place for each session without storing the user's identity.
- What changes when regulations change? Ask how quickly they updated flows for Arcom's double-anonymity rule or Italy's per-access check, and whether updates cost extra.
- What happens if your service is down? Your options are to block access until it returns or to fail closed with a holding page; never fail open.
Reusable age verification across a network of sites
If you run several sites, ask whether a user verified on one can be recognised on the others without a fresh check, and how that sits with double-anonymity rules that forbid tracking users across services. Some reusable schemes work across any participating site; others only within one operator's network. Either can cut costs and friction, but check that the token cannot be shared between users and that it expires sensibly.
Red flags in an age verification vendor comparison
- No independent certification, or a certificate that covers a different product.
- Vague claims of acceptance "in all EU countries" with no regulator references.
- Results passed to your site in a way that can be tampered with in the browser.
- Retention of face or ID images "to improve the service" without a clear lawful basis.
- Offering self-declaration or debit card checks as compliant options for adult content.
- No fallback for users the primary method cannot handle.
Frequently asked questions
Do I need more than one age verification provider?
Not usually. One provider with a broad method mix and country routing is simpler to run and audit. Larger operators sometimes keep a second provider as a backup or for a specific market.
What is reusable age verification?
The user verifies once and receives a credential or token that proves they are over 18 on later visits or other sites, without repeating the full check. It improves conversion for returning users, but check that each regulator you deal with accepts the specific scheme.
Can I build my own age verification?
You can, but you take on accuracy testing, fraud prevention, data security and certification yourself, and in France and Italy you need an independent third party anyway. For most webmasters a certified vendor is cheaper and easier to defend.
Next steps
Shortlist vendors from our compliance and verification services directory, then follow our age verification implementation checklist to put your chosen provider live correctly.