I was charged ***.** even though I canceled my reservation in a timely manner. I was on...

GetHuman4026664's Refund My Booking issue with Booking.com from December 2019

Help with my Booking.com issue
Top Tip from another customer
If Booking.com calls the hotel, and the hotel denies the refund, you can always call the hotel directly yourself to make your case for a refund.
The issue in GetHuman4026664's own words
I was charged ***.** even though I canceled my reservation in a timely manner. I was on the phone with a Representative last week who was supposed to send me a email but never did. I am taking care of this for a family member. It's ridiculous to me that she was charged by the hotel but never stayed.*The reservation was for September *-** cancelled on August **, ****. I do have an email on her phone showing the cancellation that Booking.com sent. It states booking.com ****.***.*** Pin ****. Then it states the link is expired not sure what that means. The next email received states Sorry need to cancel reservations for sept *-** laurette key west. I am confused to why she is being charged?

GetHuman4026664 did not yet indicate what Booking.com should do to make this right.

How GetHuman4026664 fixed the problem

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


Refund My Booking issue
Reported by GetHuman4026664
Dec 2nd, 2019 - a year ago
Seen by 10 customers so far
Similar issue to 13907 others
0 customers following this
Items needed
Name on the booking
Booking reference
4 digit PIN


GetHuman4026664 started working on this issue
Dec 2nd, 2019 5:49pm
GetHuman4026664 indicated the issue is not fixed yet.
Dec 3rd, 2019 5:55pm
GetHuman4026664 confirmed the issue is fixed. Hooray!
Dec 3rd, 2019 5:55pm