My March Hotel Wanted Money in August
Let me set the scene.
It was 28 August 2026. My Taiwan trip was still almost 200 days away. Kaohsiung existed as a collection of bookings, maps and suspiciously ambitious plans for March—not as a place where I was expected to start paying hotel bills before summer had even packed its bags.
My travel card contained €8.01.
This was not a financial emergency. It was deliberate. I use a separate Revolut card for travel and normally transfer hotel money roughly two weeks before departure. Until then, it sits nearly empty because unfamiliar booking platforms do not need recreational access to my main bank account.
Then City Suites tried to take €17.57. Declined. Insufficient balance.
The hotel tried before I had boarded a plane, entered Taiwan or stood anywhere near its reception desk. I was due to check in on 10 March 2027. The reservation had free cancellation. Agoda advertised “Pay at hotel” and “Pay nothing until 1 March 2027.”
Yet here we were in August, with the hotel already tapping the glass of my travel account to see whether any money might fall out.
It had tried two days earlier too: NT$682, or €18.44. That attempt also found precisely what should exist on a travel card almost 200 days before a trip—very little and absolutely no enthusiasm for premature hotel payments.
At first, I thought something had gone wrong. Then the emails arrived.
Nothing had gone wrong. Agoda and the hotel simply had a remarkably creative understanding of the words pay later.
Pay Nothing Until March—Apparently August Counts
The Agoda listing was not hiding behind vague language.
The room was advertised at €65 per night with breakfast, free cancellation and a large green promise: Pay nothing until 1 March 2027. The booking button itself said Pay later, presumably because “Let the hotel investigate your balance whenever it feels restless” would not fit neatly beneath it.
The cancellation conditions were equally clear. I could cancel for free before 3 March. Only a cancellation within seven days of arrival—or failing to appear—would trigger a charge equivalent to roughly the first night.
That arrangement made perfect sense.
The hotel had protection once the cancellation deadline arrived. I retained flexibility while the trip was still more than six months away. Everyone knew when money would become relevant.
Then City Suites ignored the calendar.
On 26 August, it attempted NT$682, converted by Revolut to €18.44. On 28 August, it returned for another try: NT$644, or €17.57. Both transactions were declined because the card did not contain enough money.
These were separate from Agoda’s own card-verification entries, which appeared in Revolut on 25 and 26 August. The City Suites attempts carried the hotel’s name, a monetary value and the wonderfully unsurprising result: insufficient balance.
Even the amount changed between attempts. Apparently, my premature financial hostage was receiving dynamic pricing. The important part was not whether €17 or €18 would bankrupt me. It would not. The problem was the timing and the contradiction.
Agoda told me I would pay nothing until March. City Suites arrived in August with a card terminal.
Two Hours to Surrender Another Card
The failed attempts did not end with City Suites quietly accepting that March had not arrived. Agoda sent me an email.
It began by confirming that payment for the booking would be made at the property. Then, without pausing to admire its own contradiction, it announced that the card provided during booking “could not be processed” and instructed me to supply another one.
My reservation would remain active for two more hours. If I failed to provide a “valid” card within that time, the booking would be cancelled.
The card was valid. It simply did not contain enough money for a hotel stay taking place 194 days later. Those are not the same problem, unless your definition of a valid card is one that allows an unfamiliar hotel to reserve money whenever it chooses.
This also exposed the pre-authorisation for what it really was. It was not an optional little verification happening quietly in the background. Allowing City Suites to place a monetary hold on my card immediately had become a condition for keeping a pay-at-property, free-cancellation booking alive.
The message was wonderfully simple:
You do not need to pay now. However, if we cannot temporarily take some money now, you have two hours to provide another card.
I did not provide another card. I had no intention of opening a different account merely because the first one had correctly refused to fund a March hotel in August. Agoda could keep its countdown. City Suites could keep its sudden insecurity. The reservation was cancelled. At least one part of their system understood deadlines.
City Suites Explains the Financial Acrobatics
After I asked why the hotel was trying to charge my card almost 200 days before arrival, City Suites replied with its explanation.
According to the hotel, bookings paid at the property require a pre-authorisation to “secure” the reservation. The amount temporarily held was equivalent to 30% of the first night’s room charge and was also intended to confirm that the card was valid and authorised for my use.
They were very careful to explain that this was not an actual charge or completed transaction.
Fine.
A pre-authorisation is not technically a payment. It merely makes part of your balance unavailable, keeps it connected to a hotel you have not visited and leaves you waiting for the card issuer to restore that balance after the hotel releases it.
Completely different. The money is not gone. It has simply been asked to sit elsewhere and think about March. City Suites said the hold would be released after I paid for the stay at check-in—or if I cancelled within the free-cancellation period. It also warned that the time needed for the available credit to return would depend on the card-issuing bank.
That was apparently their version of balanced security.
The hotel received reassurance immediately. I received a reduced available balance, a possible release delay and responsibility for sorting out the consequences if life changed before March.
And life does change. Flights move. Illness happens. Family emergencies happen. Taiwan has typhoons, earthquakes and a geopolitical situation that does not consult my hotel calendar before developing. This is precisely why free cancellation exists.
City Suites wanted the protection of a financial commitment in August while still advertising the flexibility of a March cancellation deadline. It transferred the inconvenience to the guest and called the arrangement security.
My security, meanwhile, was the reason the transaction failed.
Security Goes Both Ways
I understand why hotels want protection.
Guests cancel late, fail to appear and occasionally treat hotel rooms as experimental demolition sites. A property needs a valid payment method and a way to collect the agreed fee once the free-cancellation deadline has passed.
I have no argument with that.
My argument begins when a hotel interprets access to my card details as permission to put its paws into the account whenever it feels insecure.
A pre-authorisation in August does not guarantee anything about March. The card could expire, be replaced or remain empty. The trip could change. The reservation could be cancelled perfectly legally within the free period. All City Suites proved was that my travel card did not contain enough money on one particular morning, 194 days before check-in.
Correct. It was not supposed to.
I do not attach my main bank card—complete with its full balance—to Agoda, Trip.com, Booking.com or any other travel platform. I use Revolut or PayPal as a financial middleman. My travel card remains nearly empty between trips, and I normally transfer hotel money roughly two weeks before departure.
That is not an accident. It is the system working as designed.
If an unfamiliar merchant attempts something unexpected, Revolut tells me. The hotel does not receive automatic access merely because it once collected my card number through a booking form. City Suites wanted evidence that I could be trusted.
I wanted evidence that City Suites would follow the payment schedule displayed when I booked. Only one of us performed due diligence.
Same City Suites, Different Platform, Missing Emergency
Then I performed a deeply scientific experiment. I opened Booking.com and reserved City Suites again.
Same hotel. Same dates: 10–13 March 2027. Breakfast included. Free cancellation—this time until 7 March. The total came to TWD7,218, approximately €196 at the exchange rate shown during booking.
I entered the same type of card information and pressed the same basic button.
The reservation was confirmed.That was all.
No City Suites transaction appeared in Revolut. Nobody attempted to reserve 30% of the first night. No email announced that my perfectly functional card had failed or countdown began. No one gave me two hours to expose another account for inspection.
Booking.com simply stated that the stay had been reserved using my Visa and that the final payment would be handled by the property. Apparently, City Suites’ urgent need for immediate financial reassurance depended entirely on which platform introduced us.
Through Agoda, the hotel needed to examine my balance in August, tried twice, rejected the card and allowed the reservation to collapse when I refused to replace it.
Through Booking.com, the same hotel accepted the reservation without touching the money. That comparison removed every excuse about an unavoidable hotel policy. The building had not changed. The March dates had not changed. The guest had not changed. Only the booking platform changed—and the payment emergency vanished.
City Suites needed 30% security when Agoda delivered me. When Booking.com delivered me, that need achieved enlightenment, released all earthly attachments and disappeared.
Trip.com Invents “Pay at Hotel Twice”
Agoda’s version of pay later was irritating enough. Then I tested Trip.com.
I searched specifically for rooms that could be paid for at the hotel. At the prices I considered reasonable—around $150 for three nights—the results largely disappeared. Affordable rooms came with online prepayment. The pay-at-property option began resurfacing mainly after the price climbed above $200.
Apparently, payment flexibility had become a luxury room feature.
I selected a superior twin room at Chateau de Chine Kaohsiung for 10–13 March. Breakfast was included. Cancellation was free until 6 March. The original price was shown as more than $400, dramatically sliced by several discounts until the final amount reached US$282.13.
The page clearly said Pay at Hotel.
Then came Trip’s definition.
To secure the booking, Trip.com would pre-authorise or charge the full US$282.13 to my card. I would still pay the room rate when I arrived at the hotel. Trip would return the first amount after checkout.
In other words, a US$282.13 hotel stay required access to US$564.26: one serving for Trip’s emotional security and another for the actual hotel.
My card did not have enough money.
A large box appeared announcing Payment Failed, as though I had neglected to settle a bill rather than refused to provide full collateral almost 200 days before receiving anything.
To be fair, Trip disclosed the arrangement on the payment page. I read it. That did not make the words Pay at Hotel any less ridiculous.
Pay at the hotel usually means the hotel receives payment when you arrive. It should not mean that the platform may take the full amount now, keep it until after your stay and require you to fund the same room twice in the meantime.
I tested three hotels through Trip. Three immediate attempts. By then, the pattern was no longer subtle. Trip did offer pay-at-hotel rooms. It simply wanted the money first.
The Corporate Plot Twist
At first glance, the explanation appears wonderfully simple. Booking.com operates from Amsterdam. Agoda is headquartered in Singapore. Trip.com Group grew from China’s Ctrip and remains headquartered in Shanghai. Different markets, different expectations and apparently very different interpretations of when a hotel guest’s money becomes communal property.
Then the family tree becomes interesting. Agoda and Booking.com belong to the same parent company: Booking Holdings.
Yes. The platform that confirmed my City Suites reservation without touching the balance and the platform that allowed the same hotel to attempt two pre-authorisations, reject my card and issue a two-hour ultimatum live under the same corporate roof.
Same family. Different table manners. This means the contrast cannot be explained by ownership alone. The more revealing difference is how each brand operates in its market, what behaviour it permits from hotel partners and what it expects customers to tolerate.
Booking.com appears to understand that pay at the property should remain recognisable after the reservation is confirmed. Agoda allowed the definition to stretch until it included an immediate monetary hold. Trip.com stretched it further until the guest needed enough money to fund the entire stay twice.
I cannot prove that Taiwanese hotels dislike Booking.com because it gives them less freedom around pre-authorisations. Hotels do not generally publish cheerful little statements titled Why We Prefer Platforms That Let Us Touch Your Money Earlier.
But the incentive is visible. Through Agoda, City Suites could demand access to funds almost 200 days early. Through Booking.com, it accepted the reservation without doing so. Apparently, corporate standards can change dramatically when the same company swaps its Amsterdam coat for a Singapore one.
What “Pay at Hotel” Should Mean
This is not complicated. If a listing says prepay online, I expect to pay online.
It says non-refundable, I understand that changing my mind will cost money. If it says the hotel will collect a deposit immediately after booking, I can decide whether that condition works for me before handing over my card details. And if it says pay at the hotel, I expect to pay at the hotel.
A hotel may still need a valid card to guarantee the reservation. It may charge the agreed cancellation fee after the free period expires. It may place a clearly disclosed hold shortly before arrival, when the booking has become an actual financial commitment rather than a distant possibility floating somewhere in next year’s calendar.
None of that bothers me.
What bothers me is displaying one payment promise in large friendly letters, then reversing it through a pre-authorisation clause, a hidden platform arrangement or an email demanding a better-funded card within two hours.
Calling it a hold does not make it harmless. The money may not enter the hotel’s account, but it still leaves the guest’s available balance. If the booking is cancelled, the guest may wait for the bank to release it. If Trip holds the full room price until after checkout while the hotel also expects payment, the traveller must temporarily finance the same stay twice.
That is not flexibility.
It is the hotel securing itself against every imaginable inconvenience by transferring those inconveniences directly to the guest. Security is reasonable. One-sided security with access to my card is merely entitlement wearing a policy badge.
Final Verdict: My Card Is Not a Hotel Amenity
By the end of this little experiment, I still had a confirmed room in Kaohsiung.
I had simply taken the scenic route through three booking platforms, two failed City Suites pre-authorisations, one two-hour ultimatum and Trip.com’s attempt to make a single hotel room require two full portions of money.
The final result was almost offensively ordinary.
I booked City Suites through Booking.com. Breakfast included. Free cancellation. Payment handled by the property. No immediate Revolut alert and no hotel pawing at the travel-card balance while March remained 194 days away.
That was all I had wanted from the beginning.
I am not abandoning Agoda completely. I have used it without problems before. But its pay later label no longer receives automatic trust, especially when a property-specific policy can quietly turn delayed payment into an August balance inspection.
Trip.com is a simpler decision. If its pay-at-hotel option requires the full booking amount as collateral until after checkout, then it does not offer the payment arrangement I selected. It offers prepayment with extra choreography.
The receipts also confirmed why I keep travel money separate. My main card never entered the performance. Revolut showed every attempt, rejected what the travel balance could not cover and gave me time to ask why a March hotel had developed financial ambitions in August.
From now on, the headline payment label is only the opening statement. The cancellation terms, pre-authorisation clause and final checkout page are the actual evidence. Screenshots stay with the booking. Identical rooms get compared across platforms.
Because the same hotel may suddenly require less “security” when a different website delivers the guest.
I asked to pay at the hotel. Booking.com understood the sentence. Agoda added an ultimatum. Trip.com apparently needed subtitles.
Leave a Comment