You guys charged me more then once on May ** @ **:**pm,**:**am,**:**am for the amount o...

GetHuman-vagalovz's customer service issue with Priceline from May 2018

Help with my Priceline issue
Tip from another customer
If you are trying dispute charges that were made against you or trying to a get a refund from Priceline then click here https://priceline.custhelp.com/app/chat/chat_launch_help/.
The issue in GetHuman-vagalovz's own words
You guys charged me more then once on May ** @ **:**pm,**:**am,**:**am for the amount of $**.** all * time and earlier that same day I was charge $**.** at **:**am, **:**am. Then onces again at *:**am, *:**am, *:**am, *:**am I was charged another $**.**. so now that you guys have taken all my money I would like for you guys to pay back all the money you guys over charged me. I never cancelled any of my reservation.
GetHuman-vagalovz did not yet indicate what Priceline should do to make this right.
I have an issue with Priceline too
How GetHuman-vagalovz fixed the problem
We are waiting for GetHuman-vagalovz to fix the problem and share the solution with the rest of us customers.
Please help with my Priceline issue
Do you have a customer issue as well?
We can help you get Priceline's attention and get better help faster. Tap below to get started.
Having Priceline issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
How would Priceline email you?
This email address isn't valid

Priceline

Customer service issue
Reported by GetHuman-vagalovz
May 20th, 2018 - 6 mons ago
I have an issue with Priceline too
Fixed
Seen by 5 customers so far
Similar issue to 543 others
0 customers following this
Items needed
Priceline Trip Number
Billing address
Email address
Phone number
Timeline
GetHuman-vagalovz started working on this issue
May 20th 10:58pm
GetHuman-vagalovz indicated the issue is not fixed yet.
May 21st 10:55am
GetHuman-vagalovz indicated the issue is not fixed yet.
May 21st 10:58am
GetHuman-vagalovz indicated the issue is not fixed yet.
May 22nd 5:19pm