[slayed0]

This is a very serious issue and you should not stop pursuing all available support channels until you get an answer. I can guarantee you that such a glaring bug will immediately get high priority in their issue tracking system. The last thing Lyft wants is for something like this to get reported on and shake confidence in the platform they are trying so hard to build.

[leephillips]

The problem is that it's not a bug, it's the foolhardy way that the system is designed.

[slayed0]

I guess it's a semantic disagreement but I would still call this a bug. If they considered this use-case when they designed the system and then decided it was not worth designing for then I suppose it is not a bug, but I find it hard to believe that is the case.

[icebraining]

I don't (find it hard to believe). A few chargebacks are nothing compared to adding friction to the signup of the majority of users, financially speaking.

[NearAP]

My opinion leans towards - they considered the use-case but ruled it as uncommon and so didn't design for it (or pushed it down the priority queue). This is because it seems that most people in the US (at least those with smart phones) are on some form of contract rather than use a pay-as-you go; it also seems to me that those on contract would most likely retain their number even when they move (within the US).

[leephillips]

I understand your point, and I wish I could also find it hard to believe. But there is nothing in the article to suggest that the system is not working as intended. Of course they knew that phone numbers change hands, yet they designed their system to let the number act as both identification and authentication, knowing that it would lead to a certain number of fraudulent charges.