A guest checks a banking app after arrival and sees a pending amount larger than the room rate. It looks like a charge, but it may be an authorization hold. The team must explain the amount, payment state and next checkpoint precisely.
Do not answer with “it will disappear soon.” First identify what the hotel actually requested and what has already settled.
Separate the hold from the final charge
An authorization asks the card issuer to reserve available funds. It can reduce available credit or cash even though the hotel has not completed the final charge. Stripe’s official guide to separate authorization and capture explains that hotels may authorize before arrival and capture at checkout.
A final charge is the amount submitted for settlement. A hotel may capture an authorization, release unused value or create another payment record. Staff should read the processor and property-management records before naming the state.
Verify five facts before replying
Open the authoritative booking and payment records, not a copied chat note. Confirm:
- 1Authorization requestedVerify amount and purpose.
- 2Authorization adjustedIdentify the changed request.
- 3Final charge submittedMatch the final folio.
- 4Release requestedKeep time and reference.
- 5Issuer checkpointName the next check.
- the correct guest and stay;
- the amount and currency requested for authorization;
- why the hotel requested it;
- whether a final charge has been submitted; and
- the last processor action, reference and timestamp.
Do not ask the guest to send a full card number or screenshot containing sensitive payment details. If identity or access is uncertain, follow the same minimum-access discipline used for customer conversation access.
| Record state | What the hotel can say | What needs verification |
|---|---|---|
| Authorization requested | Funds were reserved, not described as settled | Amount, currency, reason and processor result |
| Authorization adjusted | The reserved amount changed | Which request replaced or extended the earlier one |
| Final charge submitted | A payment was sent for settlement | Final folio, amount and reference |
| Release requested | The hotel or processor initiated a release | Release reference and time; issuer posting remains separate |
| Unclear or duplicated | The team is investigating two visible records | Whether they are holds, captures, reversals or distinct transactions |
Explain the amount before the timing
Tell the guest what the verified amount covers: room and tax, a stated incidental allowance or another approved component. Never invent a formula from memory. A prepaid reservation can still have a separate incidental authorization.

Do not promise a universal deadline. Authorization windows vary by transaction and network, and some issuer interfaces do not clearly distinguish an authorization from a settled payment.
If arrival details also changed, resolve that booking state separately with the hotel arrival-change workflow. A changed stay can alter the payment calculation, but a message alone must not silently rewrite the booking or folio.
Give a checkpoint, not a promise
If the hotel released an authorization, provide the verified time and a safe processor reference. The issuer may continue to display the pending amount. Do not promise a deadline unless the responsible issuer confirmed it for this case.
Agree on the next checkpoint: the hotel will recheck its processor record, or the guest will contact the issuer with the release reference. Keep one owner. A shared team can use the ownership pattern tested in the hotel messaging inbox pilot, while property and payment systems remain authoritative.
Investigate apparent double charges carefully
Two visible lines do not prove that the guest was charged twice. They might be an authorization and a final charge, two authorizations, a reversal and a new request, or two settled transactions. Label each record by state, amount, currency, timestamp and reference before deciding.
If a settled amount is disputed, move the case into the controlled invoice-dispute process. If money was refunded to an old or closed card, use the separate closed-card refund workflow. Neither problem should be collapsed into a generic “pending payment” reply.
Close the conversation with evidence
Record what was checked, what the guest was told, who owns the next action and when the team will review it. A release request alone is not completion. Close only with a verified processor state, corrected folio, issuer checkpoint or properly handed-off dispute.
A shared inbox can preserve the conversation and owner, but it does not decide whether money settled. That decision belongs to the authorized payment and property records.
Frequently Asked Questions
Is a hotel authorization hold the same as a charge?
No. A hold reserves available funds; a charge is submitted for settlement. Both may appear in banking views, so staff should verify the processor state before explaining either one.
How long does a hotel card hold last?
There is no universal duration. It depends on the hotel’s action, processor, card type, issuer and transaction. Give the verified release action and a checkpoint, not an unsupported deadline.
Can the hotel remove a hold immediately?
The hotel may be able to request or initiate a release through its payment process. The issuer controls when that change appears in the guest’s available balance. Retain the release evidence and explain that boundary clearly.
Want help applying this guide?Ask the DripTell team
From reading to action
Want help applying this to your business?
Share your details. We will read the article you are on and start with a useful answer for your team.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy



