Fake Booking.com Hotel Message Steals Card Details and Charges €260

I experienced a serious security issue and financial loss related to my reservation in Florence at Andre Majestic View made through Booking.com. I received a message through the Booking.com app that appeared to be sent by the hotel. The message stated that my card could not be verified through a standard check and that I needed to confirm my card details via a “secure” link to prevent my reservation from being canceled. The same message was also sent to my Gmail account, labeled as being sent “via Booking.com,” making it appear fully legitimate.
To verify the situation, I first contacted Booking.com customer support through the app, but I received no response. I then replied directly to the message that appeared to come from the hotel within the app, and I was told that the request was valid and that I should proceed. Concerned about my reservation being canceled, I clicked the link and entered my card details. Shortly after, on April 23, 2026, €260 was charged from my card without my authorization.
After becoming suspicious, I contacted the hotel through its official website. They informed me that Booking.com had been compromised, that they did not send such a message, and that they never requested card details in this way. Despite this, I received no warning or notification from Booking.com about any security breach. I reported the issue to my bank, submitted a chargeback request, and fortunately, since I used a virtual card, no additional charges could be made. However, the fact that this incident occurred through what appeared to be an official Booking.com communication channel has left me feeling unsafe and unsupported.
I request that Booking.com thoroughly investigate this incident, identify the security vulnerability, and take the necessary measures to prevent similar cases. I also demand that Booking.com actively assist in the refund process of the €260 that was charged without my consent and take responsibility for resolving my financial loss.

Comments