The Uber voucher-credit bug.

For a while, Uber's support flow would hand out courtesy credit for a voucher complaint without ever checking whether the voucher was valid for your account. That was the whole bug.

How it happened

It came down to two systems that didn't talk to each other: voucher eligibility and support goodwill.

Vouchers can be locked to a region. One issued for Florida, say, wouldn't apply to a rider outside Florida, and claiming it would normally do nothing.

The gap was in what happened next. If you opened the help flow on a recent ride or order and reported a problem with that voucher, support treated it as a service issue, and the goodwill path issued a small courtesy credit to smooth it over. It never confirmed the voucher was eligible for you in the first place. A voucher built not to apply still produced credit, because the complaint was handled by a flow that only saw "customer is unhappy about a voucher," not "is this voucher even valid."

The credit was small, and the same path could be repeated, which is how a minor gap turned into something that got passed around.

The root cause

The goodwill step was built to close complaints quickly, not to verify them. An eligibility check costs more agent and system time than a small credit is worth, so validation lived on the promo side and never got wired into the support side. The credit paid out on the shape of the complaint, not on whether it was real.

Status

Patched. Uber closed it the boring, correct way: validate voucher eligibility before issuing credit, rate-limit courtesy credits, and flag repeat patterns. This is a write-up of a dead bug, documented for how it worked, not a method that still works.