A pre-authorization is not a charge. It's a promise — the card issuer sets aside funds so they're there when the final bill is settled. Nothing moves until the merchant captures the authorization, and the hold becomes a posted charge only at settlement. Keep those three steps — authorize, capture, settle — separate in your head and every "double charge" complaint in hospitality explains itself.
How a pre-authorization actually works
At check-in, the front desk authorizes the card for an estimated amount: the room total plus an incidental buffer. The issuer approves and reserves those funds — the guest's available credit drops, but no money moves. At checkout, the hotel captures the final amount against that authorization, and the transaction goes to settlement, where it becomes a posted charge.
How long can a hold last? Card-network rules and the issuing bank decide — not the hotel. Typical online purchases clear in a few days to a week; hotels and car rentals can keep holds open longer, and lodging gets different authorization-tolerance rules because extended stays are expected to run over. If the merchant never captures, the hold expires and the funds release — one hotel policy document cites 10–15 working days via the guest's own bank, and issuer policies can stretch to 30 days. The hold is placed by the guest's bank, not by the hotel: the property never holds the money.
How much to authorize? One property-management system's documentation frames the bounds: pre-authorize up to the reservation's due amount, and for guests who've already paid in full, up to $300 for incidentals — more than that should be a separately described charge.
The double-charge confusion (and the procedure that prevents it)
The classic complaint: a guest sees two $1,000 entries — one pending, one posted — and concludes they were charged twice. What's actually happening is one of two things: a pending authorization hold alongside the final posted charge, or a leftover hold from an abandoned authorization. Only one charge is ever collected; the extra pending entry drops when the issuer releases it.
But here's the part that's the hotel's fault: the abandoned-auth pattern. It happens when the front desk doesn't pull up the original authorization to post the final payment, and instead runs a second, separate transaction at checkout. The first authorization goes abandoned — and abandoned holds linger for weeks. One documented case: a hotel authorized €1,000 at check-in, charged €1,000 separately at checkout, and the first authorization was still pending two weeks later. The restaurant analogy is the correct mental model: authorize when the card is opened, add the final amount to that same authorization, close one transaction. Two transactions for one stay is the bug.
Where the hospitality flow raises your processing cost
Pre-authorizations are usually described as free — one PMS vendor notes they incur no fees in its product because a hold "is not a complete transaction." That's true of the hold itself. The flow around it is where hospitality pays:
- Delayed settlement downgrades. Transactions settled within 24–48 hours qualify for the lowest interchange rates; delays push them into higher-cost categories — a penalty for slow data management.
- Abandoned auths multiply authorizations. Every re-authorization — a declined card at check-in, an abandoned auth forcing a fresh charge — is another authorization event on the statement. Sloppy front-desk procedure directly increases the authorization count.
- Incremental authorizations on extended stays. Multi-night stays exceeding the original estimate need incremental auths; each is a new event with its own qualification. Lodging tolerance rules are more forgiving than retail's, but not unlimited.
The through-line: authorization discipline is a cost control. Every unnecessary auth is a line item; every delayed capture risks a downgrade.
Front-desk hold procedure
- Authorize once, for the right amount. Room total plus a stated incidental buffer (many properties use $50–$100/night or a flat $300 cap for incidentals on prepaid stays). Tell the guest the hold amount out loud — surprises at checkout start here.
- Keep the authorization open. Do not void it "to be safe." The open auth is what the final charge attaches to.
- At checkout, pull up the SAME authorization and post the final amount against it — never run a fresh standalone charge for a stay that already has an open auth.
- If the final exceeds the auth (extended stay, big incidentals), capture the authorized amount and charge the remainder as a described separate transaction — or take a new authorization for the full revised total before checkout.
- Batch the same day. Capture and settle within 24 hours to protect your interchange qualification.
- Reconcile auths to folios nightly. Every open authorization must map to an in-house guest. Orphaned auths get released, not left to expire.
What success looks like: zero orphaned authorizations on the nightly report, every folio's final charge visibly attached to its check-in authorization, settlement within 24 hours of checkout — and "you charged me twice" complaints dropping to the occasional guest who just needs the pending-vs-posted explanation.
FAQ
Why does a hotel put a hold on my credit card?
It's a pre-authorization: the issuer reserves the estimated stay amount plus an incidental buffer so the funds exist at checkout. No money moves until the hotel captures the final amount — the hold just reduces your available credit meanwhile.
How long does a hotel authorization hold last?
The issuing bank decides, not the hotel. Expect roughly 10–15 working days for release after checkout; some issuer policies stretch to 30 days. If a hold lingers past that, the guest should call their own bank — the hotel can't release another bank's hold.
Why do I see two charges from a hotel?
Usually it's the pending authorization hold displayed next to the final posted charge — only one is collected. But if the hotel ran a second transaction instead of capturing the original authorization, the abandoned hold can linger for weeks. That's a front-desk procedure failure, and the procedure above prevents it.