Never used lyft! My account was charged $**.**. For a ride taken on ********* at *pm. N...

GetHuman4674697's Dispute a Charge issue with Lyft from April 2020

Help with my Lyft issue
First: share to improve GetHuman4674697's odds
Strength in numbers! Companies respond better when others are watching.
Before contacting them, items GetHuman4674697 may need:
Account holder name, Email address on account, Phone number on account, and Date of birth
Top Tip from another customer
You can also dispute a charge through the app. Once logged in, look up your ride under Your Trips, select the ride that you wish to dispute, then click "I would like a refund" and then select the reason for the refund request.
The issue in GetHuman4674697's own words
Never used lyft! My account was charged $**.**. For a ride taken on ********* at *pm. Number with charged **********. Last * digets on account charged are ****. I'm just wondering how this happened when I live in Oklahoma! Will be going to bank to rebute this charge.

GetHuman4674697 did not yet indicate what Lyft should do to make this right.

How GetHuman4674697 fixed the problem

We are waiting for GetHuman4674697 to fix the problem and share the solution with the rest of us customers.

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.
Help from Real People?
If our free tools aren't enough, we partner with a US-based company with live tech support experts available 24/7. Take advantage of a $1 one-week trial membership and chat with an expert now.
Chat with a Live Expert
Having Lyft issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
This email address isn't valid

Lyft

Dispute a Charge issue
Reported by GetHuman4674697
Apr 19th, 2020 - 6 months ago
Not resolved
Seen by 3 customers so far
Similar issue to 7562 others
0 customers following this

Timeline

GetHuman4674697 started working on this issue
Apr 19th 1:41am
GetHuman4674697 indicated the issue is not fixed yet.
Apr 19th 4:24pm