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

Summary

Fake accounts and fraudulent sign-ups motivate a C# onboarding flow that screens phone numbers before sending an OTP. It combines Twilio Lookup line type intelligence, optional line status checks, and Identity Match with Twilio Verify phone verification. The pipeline rejects landline, nonfixed VoIP, toll-free, and pager types, requires first- and last-name results of exact_match or high_partial_match, and can reject lookup failures or mismatches. The post supplies a .NET 9 project setup, environment variables, MVC files, and service code for starting and checking verification. It reports example logs for a mobile number with active status and exact name matches, demonstrates blocked toll-free or VoIP testing, and notes that Lookup and Verify pricing varies by package and country.

Takeaways

1. 1

   Line Type Intelligence blocks landline, nonfixed VoIP, toll-free, and pager numbers before later verification steps.

2. 2

   Identity Match accepts exact_match or high_partial_match for both first and last names; no_match, partial_match, or null results are rejected.

3. 3

   The flow orders cheaper Lookup checks before more expensive Identity Match and Verify calls, with pricing varying by package and country.