We suspected fraudulent Amazon charges on our Capital One cards. Capital One reversed a...

GetHuman4721019's Dispute a Charge issue with Amazon from May 2020

Help with my Amazon issue
First: share to improve GetHuman4721019's odds
Strength in numbers! Companies respond better when others are watching.
Before contacting them, items GetHuman4721019 may need:
Email address on the account, Order number, Name on the account, and Billing address
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 GetHuman4721019's own words
We suspected fraudulent Amazon charges on our Capital One cards. Capital One reversed all Amazon charges back to November. I've tried multiple times to get information regarding what each Amazon charge was for. Every time I get turned over to a legal service, which I don't want and won't pay for. I desperately want to pay whatever charges are valid in the ****- I owe you. Is there a phone number I can use to talk to a supervisor? We also want to get our Amazon Prime reinstated.

GetHuman4721019 did not yet indicate what Amazon should do to make this right.

How GetHuman4721019 fixed the problem

We are waiting for GetHuman4721019 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 Amazon's attention and get better help faster. Tap below to get started.
Having Amazon 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


Dispute a Charge issue
Reported by GetHuman4721019
May 11th, 2020 - 5 months ago
Not resolved
Seen by 10 customers so far
Similar issue to 69798 others
0 customers following this


GetHuman4721019 started working on this issue
May 11th 10:01pm
GetHuman4721019 indicated the issue is not fixed yet.
May 12th 2:10pm