Caught an auto-approval bug in a fraud rule on Prime Day
Under Prime Day volumes, ruleset failures were letting wallet top-up orders pass without a fraud check; I traced them to one wrongly written rule, pointed to the exact coding error and, after checking with my manager, escalated a sev-2.
- Without it
- Top-up orders keep passing without fraud checks through the heaviest traffic of the year.
- The call
- Go into the rule logic itself and treat the business impact as a sev-2.
- What I did
- Matched the start of the errors to the time a rule change was pushed, found an assignment where a comparison belonged, and asked the rule owners to correct it on priority.
- What changed
- The rule was corrected, and my manager called it a great example of deep diving.
What people said
“You have shown great example of Deep Dive. Finding out exactly which rule was incorrect and also pointing to exact coding error.”