On *th March, **** I booked accommodation through you to several places. One was to For...

GetHuman2948042's customer service issue with Booking.com from May 2019

Help with my Booking.com issue
First: share to improve GetHuman2948042's odds
Strength in numbers! Companies respond better when others are watching.
Before contacting them, items GetHuman2948042 may need:
Name on the booking, Booking reference, and 4 digit PIN
The issue in GetHuman2948042's own words
On *th March, **** I booked accommodation through you to several places. One was to Forster Holiday Village. I paid $***, Confirmation number **********.*Forster Holiday Village is now asking for this to be paid, suggesting you refunded the amount to me. This is not the case, which I have confirmed from my bank statements. *I am very unhappy that I am now being asked to pay for this accommodation again when we paid through booking.com (more expensive than if we had just booked directly). Please speak with Forster Holiday Village to arrange the payment.
GetHuman2948042 did not yet indicate what Booking.com should do to make this right.
I have an issue with Booking.com too
How GetHuman2948042 fixed the problem
We are waiting for GetHuman2948042 to fix the problem and share the solution with the rest of us customers.
Please help with my Booking.com issue
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

Booking.com

Customer service issue
Reported by GetHuman2948042
May 19th, 2019 - a mon ago
I have an issue with Booking.com too
Not resolved
Seen by 9 customers so far
Similar issue to 14110 others
0 customers following this
Timeline
GetHuman2948042 started working on this issue
May 19th 6:38am
GetHuman2948042 indicated the issue is not fixed yet.
May 19th 8:14pm
GetHuman2948042 indicated the issue is not fixed yet.
May 22nd 6:52am