# Relay: Age 18+ Verified Claim Type

> Age 18+ Verified checks an 18+ threshold with a government ID plus live-bound selfie, informed by ISO 27566-1. The general-purpose 18+ option.

Source: https://help.withpersona.com/articles/HOsbmRJvAh16CPCcttrbOf/
Section: Relay > Features > Claim types

## What is the Age 18+ Verified claim type?

**Age 18+ Verified** evaluates whether a user meets an 18+ threshold using document-based verification with a live-bound selfie, informed by ISO 27566-1 age assurance frameworks for age verification.

Unlike the market-specific claim types, this one is not designed around a single country's guidance. It is the general-purpose 18+ option, built on an international framework rather than a national one.

💡

If you are gating an experience in a market that has its own age assurance expectations, such
as the United Kingdom, Germany, France, Italy, Brazil, or Australia, use the claim type designed
for that market instead. The threshold is the same, but the assurance level and the methods behind
it are not.

## Where you might use it

The use cases below are examples of where this claim type may be a fit:

- Broad-based age assurance

This is the claim type to reach for when you need an 18+ check that is not tied to one jurisdiction, or when you are covering markets that do not yet have a dedicated claim type.

## How the claim is evaluated

This claim type supports one method:

- **Document with selfie.** Confirms a user's age from their government ID, matched to a live-bound selfie to make sure it's really them.

Because it relies on a government ID rather than an estimate, it asks more of the user than facial age estimation does. That is the trade: a heavier flow in exchange for a document-backed result.

When you redeem the result, the payload reports the method as `document_selfie`. It is worth storing that alongside the result for your records.

## Where do you find it in the Dashboard?

Navigate to the Dashboard and click on **Relay > Claim Types**. Age 18+ Verified is listed under **Age**, and you can copy its ID directly from the table.

Relay runs inside your own product, so there is nothing to configure on this page and no verification records to review. Pass the ID from your integration when you create a Relay session, then store the claim result you get back. See [Integrating Relay](https://help.withpersona.com/articles/cOtN25GojXD3Ou6Bz5xADy/).

You can also see Relay running in the public demo at [explore.withpersona.com/relay](https://explore.withpersona.com/relay).

## A note on age assurance and compliance

Age assurance requirements vary by jurisdiction and use case. While Persona's claim types are informed by regulatory guidance, standards, and industry best practices, your organization is responsible for determining how to implement age verification in a way that meets applicable laws and requirements. You should evaluate your use of Relay as part of your broader compliance strategy. Relay is built to be a useful part of that larger process rather than the whole of it. It gives you an assurance signal at the point of access, while the surrounding policy, record keeping, and enforcement decisions stay with you.

[Persona Atlas](https://atlas.withpersona.com) tracks age assurance regulations across markets if you are working out what applies where.

## Plans Explained

### Age 18+ Verified Claim Type by plan

|                             | **Startup Program** | **Essential Plan** | **Growth Plan** | **Enterprise Plan** |
| --------------------------- | ------------------- | ------------------ | --------------- | ------------------- |
| Age 18+ Verified Claim Type | Available           | Available          | Available       | Available           |

[Learn more about pricing and plans](https://withpersona.com/pricing?utm_source=product&utm_medium=referral&utm_audience=a&utm_campaign=cm_gen_ds_hc-plan-table).