Security Deposit Hold

A hotel may request a card authorisation for room charges and incidentals, and the issuer reduces the customer's available spending capacity while the hold remains. The final charge can be smaller, equal to or, with a valid process, different from the original authorisation.

A hold differs from a cash security deposit collected and later refunded, because the customer may see a pending amount but no settled debit, although a debit-card hold can still make money temporarily unavailable for everyday spending. Stripe describes separate authorisation and capture as a way to reserve funds and collect payment later, and hotels are among its examples.

The merchant must follow the relevant payment method's authorisation and capture rules. A fictional hotel places a $1,500 authorisation and has a final eligible bill of $200, and if it captures only the $200 and releases or lets the remainder expire, the unused $1,300 is no longer reserved, which is not necessarily a $1,300 refund.

Avoid describing release as an immediate cash transfer, because an issuer may take time to update the available balance after a reversal or expiry. The hotel should tell guests what it expects to authorise, why and when it sends a release or final capture, but the exact available-balance timing is not fully under its control, so avoid promising a particular day without support.

A rental business may use a hold for fuel, damage or fees defined in its agreement, which does not establish that it can deduct anything it wants, since the signed terms and evidence for final charges still matter. The authorisation should be distinguished from the nightly room price, since a guest might see the room charge, a separate incidental hold and local taxes at different times, and a clear check-in explanation prevents confusion.

If the merchant needs to capture more than initially planned, additional or incremental authorisation may be needed, and card network rules differ by merchant type and situation. An expired hold is not a paid bill, so if a business misses the capture window it may need a new authorisation or another lawful collection process, and finance teams should watch expiry dates.

A pending card transaction may disappear when the authorisation is reversed, whereas a captured transaction becomes a posted charge, so compare both the pending and posted sections before alleging duplicate billing. A customer should budget for the temporary reduction in available funds, especially for travel with multiple hotels or rentals, because several holds can overlap even when the eventual costs are lower.

If a hold lingers, ask the merchant and issuer about the particular authorisation, and remember that holds can interact with a changed card, an early checkout or a cancelled reservation, so the merchant should check whether an earlier authorisation was reversed and not create a new hold without explaining the overlap. The merchant should keep records of authorisation ID, amount, date and associated reservation, since a vague request to release "the deposit" may delay investigation, and a customer questioning a pending amount should ask for the authorisation amount and the eventual posted charge and keep the reservation and checkout documents.

For accounting, a pure authorisation is not the same as cash received, so recording it as revenue or a refund can misstate sales, and the actual captured transaction and any separate deposit should be recorded according to substance. The merchant should also check that its policy aligns with local consumer and card rules, because this entry explains the payment mechanism, not a legal right to withhold or charge a particular sum, and clear amounts, a valid final capture and timely reversal keep a hold from becoming a surprise to the customer.