I was charged $**.** on ********? What is it for.

GetHuman-fbpickle's Dispute a Charge issue with iTunes from October 2019

Help with my iTunes issue
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 GetHuman-fbpickle's own words
The problem: I was charged $**.** on ********? What is it for.

GetHuman-fbpickle did not yet indicate what iTunes should do to make this right.

How GetHuman-fbpickle fixed the problem

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

Prefer a step by step guide?
We've taken the time to write instructions for how to solve some of the most common iTunes customer problems.
How Do I Turn Off Auto Renewal on Itunes?How Do I Transfer Music to My Phone from Itunes?How do I dispute an iTunes charge and get a refund?
Do you have a customer issue as well?
We can help you get iTunes'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 iTunes 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

iTunes

Dispute a Charge issue
Reported by GetHuman-fbpickle
Oct 31st, 2019 - 2 years ago
Fixed
Seen by 15 customers so far
Similar issue to 6525 others
0 customers following this
Items needed
Username
Email on Account
Phone number on Account
Order Number
Confirmation Number
Name of Account Holder

Timeline

GetHuman-fbpickle started working on this issue
Oct 31st, 2019 7:18pm
GetHuman-fbpickle confirmed the issue is fixed. Hooray!
Nov 1st, 2019 1:56am
GetHuman-fbpickle confirmed the issue is fixed. Hooray!
Nov 1st, 2019 3:22am