How to Confirm Phone Number Ownership with Lookup Identity Match

Summary

The tutorial shows how to use Twilio Lookup Identity Match to confirm that a person is linked to a submitted phone number and reduce sign-up fraud. It describes a zero-knowledge match against authoritative sources such as mobile carrier records, with possible use during sign-up, login, account changes, or checkout. The implementation starts from an international telephone input project, collects first and last names alongside an E.164 phone number, and passes them to the Lookup API with the identity_match field; the response exposes per-field statuses and a summary score. The sample JavaScript treats the check as successful when the phone is valid and both names are exact or high partial matches, then displays the result, while the post also notes approval requirements outside the US, test parameters, and alternative Lookup packages.

Takeaways

1. 1

   Identity Match accepts any combination of name, address, national ID, or date of birth for matching; fields that are not supplied return null in the response.

2. 2

   Responses can contain exact_match, no_match, no_data_available, and partial-match results, alongside per-field error information and a summary_score.

3. 3

   The example accepts a registration when the phone number is valid and both first- and last-name results are exact_match or high_partial_match, allowing variations such as Kelly and Kelley.