Age-to-mobile-number check API

Catch the applicant whose stated age does not fit the number they gave you.

A customer can type any date of birth. The subscriber behind their mobile number has an age already. If the two do not match, the number is probably not theirs, and you know before you spend on the sign-up, the offer or the KYC check.

Stated age against the mobile subscriber
No document upload
API and bulk upload

Part of: KYC waterfall Eligibility screening

Create an account See a sample response Pricing on request

A threshold check answers one question. This answers the next one.

Age verification confirms the subscriber behind a number meets your minimum age. That is the right first question. It does not tell you whether the person filling in your form is that subscriber.

The age-to-mobile-number check does. Compare the age the customer states with the age held for the subscriber. A 19-year-old applying on a 52-year-old's number, or a stated age of 30 on a number registered to a teenager, stands out immediately.

Borrowed numbers

Under-age customers signing up on a parent's phone.
Bought and burner numbers

Fraudsters pairing stolen identities with numbers that are not theirs.
Mismatched applications

Applications where the stated identity and the phone number tell different stories.

What it checks

Send a mobile number and the date of birth the customer gave you.

Provero compares the stated age with the age information held for the subscriber of that number and returns whether they match. You do not receive the subscriber's date of birth or exact age.

What it returns

One clear result for your rules to act on.

match

The stated age is consistent with the subscriber behind the number.
no_match

The stated age does not fit the subscriber. The number may not belong to the person applying.
unable_to_verify

No age information is available for this number. Use another verification step.
mobile_network_code

The mobile country and network code associated with the result.

Where it is used

Age-restricted sign-up

Gambling, alcohol and vaping sign-ups, alongside Age verification, to catch under-age customers using someone else's phone.
KYC waterfall, Stage 1

Screen out mismatched applications before you pay for credit reference agency checks.
Financial promotions

Confirm the applicant fits the number before an incentive is paid.
Existing records

Check numbers and dates of birth you already hold in bulk, to find records worth re-verifying.

See how it fits into Eligibility screening →

How to read the result

Result	Meaning	What to do
match	Meaning: The stated age fits the subscriber behind the number.	What to do: Continue. Run your threshold or identity checks as normal.
no_match	Meaning: The stated age and the subscriber's age do not fit together.	What to do: Review, or ask for another verification step before the offer or KYC check.
unable_to_verify	Meaning: The check could not give an answer for this number.	What to do: Do not infer a result. Use another permitted verification route.

API and bulk upload

Run the check at the moment of the decision, or across records you already hold.

API

Send mobile_number and dob. Run it on its own, or with Age verification and the other Stage 1 checks in one Multi-validation request.

Bulk upload

Upload a file of numbers and dates of birth and run the check across them, without building an integration first.

Age-to-mobile-number check API example

Request

{
  "mobile_number": "+447700900123",
  "dob": "1988-04-12"
}

Response

{
  "status": "success",
  "verification_id": "age_match_123456",
  "mobile_number": "+447700900123",
  "age_match": "no_match",
  "mobile_network_code": "23410"
}

Illustrative example. +447700900123 is a number reserved for documentation, so the result shown is not a real check. The full field reference is published with the API documentation.

Age-to-mobile-number check pricing

Pricing depends on volume and network coverage.

The check is quoted per account so the rate reflects the networks and volumes you need. Everything else runs on the same prepaid Provero balance.

See published pricing.

For pricing, email pricing@provero.io.

Related checks

Use it with Age verification for age-restricted products, or with Mobile network KYC where you need the full identity picture.

See every Provero check →

Age-to-mobile-number check FAQ

How is this different from Age verification?

Age verification confirms the subscriber behind a number meets a threshold such as 18+. The age-to-mobile-number check confirms the age the customer told you fits that subscriber. Use both to know the customer is old enough and that the number is theirs.

Does it return the subscriber's age or date of birth?

No. It returns whether the stated age matches. You never receive the subscriber's date of birth or exact age.

What does no_match mean?

The stated age does not fit the subscriber behind the number. The number may be borrowed, bought or registered to someone else. Review the application or ask for another verification step.

Does the customer have to do anything?

No. The check uses the mobile number and date of birth they already gave you. There is no document upload and no extra step.

Can I run it in bulk?

Yes. Upload numbers and dates of birth you already hold, or call the API at sign-up.

Run an age-to-mobile-number check

Create an account and request access to the check. Then run it through the API or bulk upload.

Create an account