Building Bulletproof 2FA with Twilio APIs
summary
Shows how to implement multi‑factor auth with Twilio Verify and mitigate fraud using FraudGuard to block suspicious carriers and premium numbers tied to SMS pumping. Recommends channel fallback (authenticator app, WhatsApp, email, SMS), one API call per verification, and exponential resend delays (30s initial, then 60s+) plus backend checks for OTP conversion, traffic spikes and carrier ranking. Cites industry impact (≈$3.1B new‑account fraud in 2019, >$100B telecom fraud estimate by 2023) and demos a working verify+retry prototype.
AI-written summary · about
chapters (36)
- 0:00Introduction
- 2:55A422 Status Code
- 3:50Suspicious Numbers
- 5:20Web Platform
- 5:55Captures
- 6:35Spiral Galaxy
- 6:58User Verification
- 8:20Challenges
- 9:17Mobile Network Operator
- 11:40Detecting fraud
- 12:45Traffic spikes
- 15:25authy
- 16:10Cyber Network
- 16:55Google Research
- 18:05Pass Rate Skip Rate Abandon Rate
- 18:28Unfamiliar Skip Rate
- 19:09Abandoning Security Features
- 19:25Asking Permission
- 19:55Balance
- 20:25Bank Security
- 20:40Bank Security Examples
- 21:15Risk Tolerance
- 22:13Safety Deposit Box
- 23:03GitHub 2FA
- 24:22Twilio Verify
- 26:05Demo
- 26:32Implement SMS
- 27:33Test SMS
- 28:02Retry Logic
- 30:06Retry Demo
- 31:15Twilio Fraud Guard
- 32:39Building practical stuff
- 33:13Multiplatform MFA
- 34:50Wrap up
- 35:22Twitter Verify
- 35:41Outro
