Payments and administration

When should a hotel take a card pre-authorisation instead of a deposit?

A temporary card hold and an advance payment solve different problems. Choose according to when you need to collect money, what the final bill may include and what your payment setup supports.

Quick answer

Use a card pre-authorisation when you need a temporary hold near arrival or during a stay, and can complete the payment within the confirmed authorisation window. Take a deposit when your booking terms require an actual advance payment. A hold reduces the guest’s available funds or credit but is not money in your bank. Confirm card eligibility, capture options and release handling before choosing either workflow.

Hotel pre-authorisation vs deposit: what changes?

Authorisation, capture and payout are separate events. Authorisation reserves an amount; capture starts collection; payout transfers processed funds to the hotel under the provider’s schedule. A deposit is an advance payment, although its payout may still be pending.

Choose by purpose, money movement and follow-up
Decision pointPre-authorisationDeposit
Best fitTemporary cover for an upcoming stay or agreed incidentals.Collecting part of the booking price in advance.
Guest’s moneyAn amount is reserved, reducing spending capacity.An amount is charged as payment.
Hotel cash flowNo payout from the hold alone.Payment proceeds through settlement and payout.
Time limitExpires under provider, scheme and transaction rules.No authorisation hold to maintain once payment completes.
If money is not owedCancel or release where supported, or follow the documented expiry process.Arrange any refund due under the booking terms.
Main operational riskA hold expires, cannot be adjusted, or overlaps with another payment.Staff overlook a payment already collected or miscommunicate refund conditions.

The distinction between processed funds and bank payout is explained in Adyen’s payment lifecycle documentation.

Three situations and the better starting point

1. A flexible short stay

A guest pays at departure and may add breakfast. Consider a pre-authorisation at check-in if the confirmed capture deadline covers the stay and the agreed amount. Decide what happens if the visit is extended.

2. A booking months ahead

Your rate requires an advance contribution to the stay. Take a deposit under those terms. Do not treat a temporary hold made today as collected money for a distant arrival.

3. A prepaid room with extras

The accommodation is already paid. A separate, disclosed incidental hold may be appropriate if supported. Keep its purpose and amount separate from the room payment; do not reserve the full room price again.

These are starting points, not universal policies. For a long stay, limited card spending capacity or an unsupported card, agree a suitable payment arrangement before arrival.

Illustrative example: a £300 hold is not a £300 payment

A guest books two nights at £120 each, with no deposit. The hotel agrees a £300 hold covering the £240 room bill and £60 for possible extras. These are final guest-facing GBP amounts, including VAT where applicable; processor fees are excluded.

  1. At check-in

    £300 is authorised. Captured payment: £0. The guest’s spending capacity is reduced by £300.

  2. At check-out

    No extras were used. If partial capture is supported, capture £240 against the existing authorisation and confirm release of the unused £60.

  3. After processing

    The guest pays £240, not £300 plus £240. The hotel checks capture success, release status and the later payout separately.

This example assumes partial capture and release are supported, as described in Stripe’s separate authorisation and capture documentation. It is not a claim that this exact workflow is available in every RoomRaccoon configuration.

If your setup requires a separate charge instead, check what happens to the original hold before proceeding. The guest could temporarily have both the charge and the hold reducing their available balance.

Confirm the deadline and explain the hold to guests

There is no universal hotel pre-authorisation validity period. Adyen’s authorisation guidance distinguishes processor settings from card-scheme rules and limits adjustments by payment method and merchant eligibility. Read your actual provider’s current documentation for the transaction you intend to use.

  • Record the authorised amount, transaction reference and capture deadline. Assign someone to review holds before expiry.
  • Confirm whether your integration supports partial capture, increases, extensions and manual cancellation. Do not infer these from the processor’s API capabilities.
  • Check supported card types and whether an unsupported attempt fails or becomes an immediate charge.
  • Confirm how unused funds are released and which transaction status proves the request succeeded.

Cancellation and refund are different operations: Adyen documents cancellation before capture, while Stripe distinguishes cancelling an incomplete payment from refunding a completed one. The guest’s bank also affects when the available balance updates; do not promise immediate availability.

Guest wording for the illustrative scenario: “At check-in we will request a £300 temporary card hold, covering your £240 room bill and up to £60 of extras. This reduces your available balance or credit. We will confirm your final bill at check-out and explain how any unused hold is released. Your bank controls when the change appears.”

Make the payment workflow part of your software demo

RoomRaccoon’s UK integrated hotel payments page lists pre-authorisations, payment links and permissions for payment and refund actions. Its hotel property management system also provides access to reservation payment statuses.

Ask which provider and UK configuration will serve your property, what is included in your package and which fees apply. Have the team demonstrate card eligibility, capture and release behaviour. Matching a payment to a reservation does not, by itself, prove that external OTA bank payouts are reconciled.

Bring the £300/£240 example and your own deposit policy. Ask: “Show us what the guest sees, what staff must do when the final bill is lower, and how we distinguish authorised, collected and paid-out amounts.”

Explore payment workflows for your hotel

Frequently asked questions

Does a pre-authorisation make a booking paid?

No. Keep the authorised amount separate from collected payments. Even after capture, check the payment outcome and payout record before treating the money as received in your bank.

Can I pre-authorise every debit card?

Do not assume so. Card eligibility and behaviour depend on the provider and integration. Confirm that the proposed action creates a hold rather than an immediate charge before explaining it to a guest.

Is releasing a hold the same as refunding a deposit?

No. Releasing an uncaptured hold removes a reservation of funds. Refunding returns money already collected. Check the original transaction status so staff choose the correct operation and give an accurate explanation.

Can a deposit and a pre-authorisation be used together?

Yes, where supported and clearly explained. For example, a deposit can pay towards accommodation while a later hold covers agreed extras. Record their separate purposes and account for the deposit when calculating what remains payable.

Sources and scope

Checked 10 November 2026. Processor documentation explains payment mechanics; it does not establish which features a RoomRaccoon package or integration exposes.