numbersonline
Sign inGet verified
For businesses · KYC · fraud

Match or no-match. Nothing more leaves our hands.

Confirm a customer against a verified phone number without ever pulling their private details into your systems. Submit a number and a name; get match or no-match in milliseconds. The name we hold is never returned — because trusting a number should never mean trading away who is behind it.

We never return the name on file — only whether it matches. This protects the privacy of the number’s owner.
How it works
  1. Enter the phone number and the name you want to confirm.
  2. We check it against the verified identity on record for that number.
  3. You get match, no-match, or not-verified — never the name itself, and nothing you can use to re-identify the owner.
API
POST /api/match
X-API-Key: <your key>
{ "number": "+16285550177",
  "name": "Maria Chen" }

→ { "status": "match",
    "kind": "personal",
    "verified": true }

# the other two outcomes:
→ { "status": "no_match", "kind": "personal", "verified": true }
→ { "status": "not_verified", "kind": null, "verified": false }
Full API docs →

Why this is built the way it is

A phone number is a digital identity — the one that anchors a bank login, a family, a business. We believe verifying one should make it more trustworthy without ever putting its owner up for sale. So this endpoint is deliberately narrow: it tells you whether a name you already hold matches ours, and it stops there. The stored name never crosses back to you, results are for one-time use, and there is nothing here to scrape, cache, or rebuild a directory from. Match or no-match. Nothing more leaves our hands.

Questions

What does the identity match check?

You submit a phone number and a full name. We compare that name against the verified identity on record for the number and return match, no-match, or not-verified. Nothing more leaves our hands — we never return the name we hold.

Why is this privacy-preserving?

A personal number is private by default; it never exposes its owner’s details to the public, only that it is verified and online plus a risk score. The match endpoint confirms whether a name you already have lines up with ours. It is the anti-data-broker approach: we help you trust a number without selling you who is behind it.

Can I use it over an API?

Yes. POST a JSON body with the number and the name to /api/match and you receive a status, a kind, and a verified flag. Use the form on this page to try it interactively before you wire it into onboarding.

How is it priced, and can I store the results?

The interactive tool on this page is free to try. For the API, create a key in seconds with no sales call via self-service signup (free tier, rate-limited); for production volume, add prepaid credit ($5–$500 top-ups) and pay only for what you use. See the API docs for the full reference. Separately, verifying your own number — so it can be matched against — is a one-time USD 9 for a personal number, or USD 29/year (auto-renewing) for a business number. Match results are for one-time use: you should not cache them or build a database from them.