I was charged for a ride I did not take. We were called by the Lyft driver and told to...

GetHuman637671's Billing Issue with Lyft from April 2018

Help with my Lyft issue
I was charged for a ride I did not take. We were called by the Lyft driver and told to stand on a certain corner for pick up from the Stagecoach festival in Indio, CA. When the driver arrived, he honked, slowed at the curb, stopped rfor approximately ** seconds and took off. I canceled the ride after he drove away without us. Now, a charge for $**.** is on my account on top of the ride I actually DID end up taking. There is no record of this ride on the app to be able to report it directly, but somehow he got paid for it. Thankfully, it wasn't a huge amount, but I want that money back. We're spending a small fortune with your company this week and so far the company and service are great. Please resolve this so that opinion remains.
I trust that Lyft will make this right and come up with a resolution that is fair.
Help with my Lyft issue
How GetHuman637671 fixed the problem:
I emailed the company and was advised that it was a temporary hold to my card and would fall off within two business days. It did and I'm satisfied with the customer service and response I received from them.
I have an issue with Lyft too
Do you have a customer issue as well?
We can help you get Lyft's attention and get better help faster. Tap below to get started.
Having Lyft issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
How would Lyft email you?
This email address isn't valid

Lyft

Billing Issue
Reported by GetHuman637671
Apr 28th, 2018 - 3 mons ago
I have an issue with Lyft too
Fixed
GetHuman637671 shared how to fix
Seen by 5 customers so far
Similar issue to 11611 others
0 customers following this
Items needed
Account holder name
Email address on account
Phone number on account
Date of birth
Timeline
GetHuman637671 started working on this issue
Apr 28th 4:21pm
GetHuman637671 confirmed the issue is fixed. Hooray!
May 1st 5:27pm