Duplicated booking**Booking ID: ********* as detailed below:*Hotel: OYO *** Hotel Arian...

GetHuman3210591's Problem With a Payment issue with Agoda from July 2019

Help with my Agoda issue
The issue in GetHuman3210591's own words
Duplicated booking**Booking ID: ********* as detailed below:*Hotel: OYO *** Hotel Ariana Iskandar*Room Type: Deluxe Queen Room*City*Country: Johor Bahru*Malaysia*Arrival: July **, *****Departure: July **, *****Email address on booking: *****@***.com***I first pay with maybank*u (online banking) payment and Agoda system showed "unsuccessfully payment" and asked me to try other payment method, only then I paid with my Mastercard. **However, the first attempt subsequently turned out to be "successfully" and duplicated charges to my saving account for the same day, same room type and same hotel booking.**I have contacted Agoda Customer Service, Alicia. *However, none helpful outcome is obtained by her!**Kindly please assist to solve this issue and ensure one of the duplicated booking is refunded! **Your consideration and cooperation is very much appreciated!
Cancel and refund the sum of duplicated booking
How GetHuman3210591 fixed the problem

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


Problem With a Payment issue
Reported by GetHuman3210591
Jul 8th, 2019 - 2 years ago
Seen by 28 customers so far
Similar issue to 33377 others
0 customers following this
Items needed
Email address on the account
Last 4 digits of the payment card
Phone number on the booking
Booking ID


GetHuman3210591 started working on this issue
Jul 8th, 2019 6:14am
GetHuman3210591 shared this issue with friends on Facebook
Jul 8th, 2019 6:21am
GetHuman3210591 confirmed the issue is fixed. Hooray!
Jul 11th, 2019 2:00am