Copart, Member Mobile
reCAPTCHA Enterprise rollout
I added bot protection across login, registration and bidding in the Copart Member Mobile app.
- Sessions protected in two months
- 3.7M+
- Role
- Owned it end to end
- Built with
- reCAPTCHA Enterprise
- Account Defender
- React Native
- Node.js
- WhereLogin, registration and bidding, on the client and the server.
- RolloutPer-market flags controlled a staged rollout.
- FallbackIf the SDK fails, the app recovers and sign-in still works.
- Account DefenderAdded for login and registration, with outcome feedback for risk assessment.
WhereWhoRiskOutcome
- Sign inPerson on the app0.9Allowed
- RegisterScripted sign-ups0.1Blocked
- Place a bidPerson on the app0.8Allowed
- Sign inreCAPTCHA unreachable–Still signs in
Each outcome goes back to Account Defender, so later scores improve.
An illustration with example scores. The app and the server both check, and the rollout went market by market behind flags.
Problem
The reCAPTCHA Enterprise rollout had to protect login, registration and bidding without locking out a real buyer. Sign-in still had to work when the SDK failed.
What I built
I integrated reCAPTCHA Enterprise on the client and server. Per-market flags controlled the staged rollout, and the app recovers from SDK failures without blocking sign-in. I added Account Defender for login and registration, plus outcome feedback for risk assessment.
Result
The reCAPTCHA Enterprise rollout protected 3.7M+ sessions in two months.
I’ve kept this to what my resume says. Ask me for more detail when we talk.