How to Approve Real Users and Block Fake Accounts at Sign Up with Lookup and Verify

Summary

Fake accounts and signup fraud can undermine onboarding, so the tutorial builds a Node.js flow that collects a user's name and phone number. It combines Twilio Lookup and Verify through four progressively intense checks: line type, line status, identity match, and SMS OTP possession. The implementation blocks landline, nonfixed VoIP, toll-free, and pager numbers, checks submitted first and last names against authoritative sources using exact_match or high_partial_match, and sends an OTP only after the lookup steps pass. Line status is optional in the example because access is in Private Beta, while the project uses Express, EJS, and environment variables for its Node.js setup. It also demonstrates expected outcomes for mobile, blocked, and mismatched inputs, then notes that pricing varies by country.

Takeaways

1. 1

   The example rejects landline, nonfixed VoIP, toll-free, and pager numbers through Lookup Line Type Intelligence before proceeding.

2. 2

   Identity Match accepts first- and last-name results only when each is exact_match or high_partial_match; other results reject the request.

3. 3

   Line Type Intelligence and Line Status are described as cheaper than Identity Match and Verify, and the checks can be rearranged for country-specific pricing and business logic.