Hotel bookings made through the live supplier search do not charge the card at checkout. They place an authorization hold instead, and the money is only taken once the consultant has confirmed the booking with the supplier. This article explains what that means for the client and what to do when a re-authorization is requested.
Hold Now, Charge Later
When the client pays for a GDS booking request, the card is authorized for the booking amount. The funds are reserved with the bank but not transferred, which is why the statement may show a pending item rather than a completed payment. TravelFlow treats the hold as valid for six days. The consultant captures it when the supplier confirms the booking; if the booking does not go ahead, the hold is released instead.
“Card authorisation needed”
Immediately before placing the supplier booking, TravelFlow compares the current supplier price with the price the hold was based on. If it has moved, the booking is not placed: the original hold is released and the request is flagged for re-authorization, because the client agreed to a different amount. A request is also flagged when its hold is released while the booking is still open — the hold reached its review date, or the supplier refused the first attempt and the booking is being tried again.
Clients see an amber Card authorisation needed banner on their bookings page — Bookings in the portal, or Bookings > My Bookings for private users. Each booking in it shows the amount to authorise, whether The price changed or The card hold was released, and an Authorise again button; private users also get the same button in the booking's details. It shows only while the booking is still open, not once it is completed, cancelled or under cancellation. Authorising again places a fresh hold for that amount; you are still not charged until the consultant confirms. The assigned consultant is notified as soon as you do it.
3D Secure During Authorization
Authorization uses the same card flow as a normal payment, so your bank may require 3D Secure. The browser leaves TravelFlow for the bank's verification page and returns afterwards. Do not close the tab or press back during that step; if you land on Payment Status Unknown, check the booking before trying again rather than authorizing a second time.
Holds That Are About to Lapse
A background job watches active holds. Two days before a hold lapses it notifies the assigned consultant so the booking can be finalized in time; once a hold has lapsed, the request is marked as needing re-authorization and both the consultant and the client are told. If the supplier booking was already confirmed but the money was never taken, the same job captures the hold rather than letting it expire.
Authorizing Twice
Nothing stops a second authorization on the same request, and a second hold reserves the funds again. If you authorized twice by accident, tell your consultant or support with the booking reference and the times — the extra reservation is not tracked against the request and may otherwise sit on the card until the bank releases it.