Credit Card Authorization Holds: How Long They Last, How to Release Them
Learn how a credit card authorization hold works, how long it lasts, and how incremental auths and reversals prevent customer double-charge complaints.

Photo: Pixabay
On this page 7 sections
- What a Credit Card Authorization Hold Does to a Cardholder's Balance
- How Long Does an Authorization Hold Last? Card Brand and Industry Factors
- Estimated vs. Incremental Authorizations for Hotels and Rentals
- Capturing Less Than You Authorized
- How to Release an Authorization Hold You No Longer Need
- Scripts for Explaining Pending Charges to Customers
- Next Steps: Getting Your Setup Right
Key takeaways
- An authorization hold lowers a cardholder's available balance, but no money moves until you capture and settle the transaction.
- Hold length depends on the card network, the transaction type and your industry, and the issuing bank decides when a hold drops off the customer's account.
- Incremental authorizations and partial captures with reversals keep a single hold in place, which prevents the "double charges" caused by stacked authorizations.
- Reversing holds you won't use lets pending amounts fall off sooner. A refund does not do the same job as a reversal.
A guest checks out of your hotel, pays the final bill and calls two days later, upset that their banking app shows the stay "charged twice." In most cases nobody was charged twice. The customer is looking at a credit card authorization hold, sometimes called a pre-authorization hold, that hasn't dropped off yet. This guide explains what holds do, why their length varies, and how incremental authorizations, partial captures and reversals reduce confusing pending charges.
The same confusion shows up at restaurants. A diner sees a pending tab amount and a different final amount side by side and assumes the worst.
What a Credit Card Authorization Hold Does to a Cardholder's Balance
When you run a card for authorization, you ask the issuing bank one question: is this card valid, and is enough credit or money available for this amount? If the bank approves, it sets that amount aside. This lowers the cardholder's available credit, or their available balance on a debit card. No money moves yet.
Money moves only after you capture the transaction, usually when you close your batch. The transaction then goes through clearing and settlement. For a full walkthrough of each step, see our guide on how credit card processing works from swipe to deposit.
The cardholder sees the authorization as a "pending" transaction. Pending items typically:
- Reduce the amount the cardholder can spend right away
- Show the authorized amount, which may differ from the final bill
- Drop off once the final transaction posts or the hold expires
Debit cardholders feel holds the most. On a credit card, a hold uses part of a credit line. On a debit card, it ties up real cash in a checking account, so a large hotel or rental hold can interfere with the customer's rent or other bills.
Why Customers Think They Were Double-Charged
The usual causes:
- The final charge posts before the hold drops. The settled amount appears while the original authorization is still pending, so for a short time the customer sees both.
- Staff ran a second authorization instead of adjusting the first. For example, an employee re-swipes at checkout for the final amount, and now two separate holds exist.
- A transaction was retried. A terminal timed out, staff ran the card again, and both attempts were approved.
- The authorized and final amounts differ. A bar tab authorized for one amount and closed for another, with the tip included, can look like two charges.
You have little control over the first cause. The other three come from how your system and staff handle transactions, so you can fix them.
How Long Does an Authorization Hold Last? Card Brand and Industry Factors
There is no single answer to how long an authorization hold lasts. Several factors determine it:
- The card network. Visa, Mastercard, American Express and Discover each publish their own rules on how long an authorization stays valid.
- The transaction type. Card-present and card-not-present transactions can be treated differently. So can estimated authorizations and final-amount authorizations.
- Your merchant category code (MCC). Networks give some industries, lodging and vehicle rental in particular, longer validity windows than general retail, because their transactions naturally happen days after the first authorization.
- The issuing bank. The issuer decides when the pending item disappears from the customer's account. Even if you send a reversal right away, a slow issuer may keep showing the hold for a while.
Network rules change, so this article doesn't list specific day counts. Ask your processor which validity windows apply to your MCC and transaction types, and check again when the networks announce rule updates.
Why this matters for you: Capturing a transaction after its authorization has expired can lead to higher interchange costs, a decline when you try to settle, or a chargeback for an invalid or stale authorization. If you routinely capture days after you authorize, find out your window.
Industry Patterns
| Industry | Typical Hold Scenario | What to Watch |
|---|---|---|
| Hotels and lodging | Estimated hold at check-in for room, tax and incidentals | Extended stays that outrun the original estimate; releasing unused incidental amounts at checkout |
| Restaurants and bars | Pre-authorized tab, then tip adjustment at close | Final amount differing from the authorization; tabs left open across batches |
| Travel and tourism | Vehicle or equipment rentals, tours booked ahead | The gap between booking and service may exceed any hold window |
| Events and ticketing | VIP table minimums, venue rentals, damage deposits | Holding funds for events weeks away; releasing unused minimums after the event |
If an event or tour is far in the future, a hold usually isn't the right tool because it will likely expire before the service date. Instead, charge a deposit under clearly stated terms, or use an account-verification request. Many processors support this type of request, which confirms the card is valid without setting money aside.
Estimated vs. Incremental Authorizations for Hotels and Rentals
Lodging and rental businesses rarely know the final amount at the start. The networks offer two tools for this situation.
Estimated authorization. At check-in or pickup, you authorize an amount based on the expected stay or rental period. That usually covers the room or vehicle rate, taxes and a reasonable amount for incidentals.
Incremental authorization. If the guest extends their stay or adds charges, you increase the existing authorization rather than running a new one. The original approval and the increment are linked to the same transaction, so the customer sees one growing pending amount instead of several separate holds.
Incremental authorizations are the main fix for stacked holds. Without them, a guest who extends twice may see three separate pending amounts and assume they paid for the stay three times.
A few practical points:
- Eligibility is limited. Networks restrict estimated and incremental authorizations to certain MCCs. Your processor sets them up based on your actual business type. They cannot be added by recoding your account, and you shouldn't try.
- Your POS or property management system has to support them. Some systems re-authorize by default. Confirm with your provider that extensions send an incremental request.
- Keep estimates reasonable. Holding far more than a stay is likely to cost creates the cash-flow complaints you're trying to avoid, especially from debit card users.
For a deeper look at sizing incidentals and timing their release, read how much hotels should authorize for incidentals. MannyPay works with lodging businesses on hotel payment processing and rental and tour operators in travel.
Capturing Less Than You Authorized
It's normal for the final amount to come in under the authorization. A guest skips the minibar, or a VIP table doesn't hit its minimum. What matters is what happens to the difference.
When you capture less than the authorized amount, a properly configured system should send a partial reversal for the unused portion along with the capture. That tells the issuer to release the leftover funds. If your system captures the lower amount without a reversal, the excess may stay on hold until the authorization expires.
Restaurants and Tip Adjustments
Restaurants and bars usually face the opposite problem. The final amount includes a tip and comes in above the original authorization. Networks allow some tolerance for this in eligible restaurant and bar transactions. Tolerances vary by network and situation, so confirm with your processor how much variance your setup supports before staff close tabs well above the pre-auth. Our explainer on credit card tip adjustment and where it goes wrong covers the mechanics in more detail.
Our guide to holding a card for a bar tab without getting burned covers tab limits, walkouts and when to re-authorize. You can also explore payment options for restaurants and bars. For tableside checkout, see our guide to pay-at-the-table handhelds for faster turns and safer card handling.
Online Orders and Split Shipments
E-commerce merchants often authorize at checkout and capture when an order ships. If items ship separately, your gateway may support multiple partial captures against one authorization. Backorders that sit for a long time can outlast the authorization window. Ask whether your payment gateway supports multiple captures and how it handles authorizations that age out.
How to Release an Authorization Hold You No Longer Need
To release an authorization hold, send an authorization reversal, often labeled a "void" on your terminal. The reversal tells the issuer you won't capture the transaction and that the funds should be released.
A void is not the same as a refund:
| Action | When to Use It | What the Customer Sees |
|---|---|---|
| Void / authorization reversal | Before the transaction is captured or the batch closes | The pending hold should drop off, on the issuer's timeline |
| Refund | After the transaction has settled | A charge, then a separate credit, often days later |
If a guest cancels or a tab was run twice, void the extra authorization. Don't let it settle and then refund it. A refund on a settled charge doesn't remove an earlier hold, and the customer ends up seeing more activity, not less.
Good habits:
- Void duplicate authorizations immediately. If a terminal times out, check whether the first attempt was approved before running the card again.
- Reverse unused holds at checkout or close-out, not whenever the batch happens to run.
- Don't let authorizations expire on their own. Some networks charge fees on authorizations that are never captured or reversed. Ask your processor whether this applies to you.
- Review open authorizations daily, especially keyed and phone transactions, where follow-up is easy to forget.
For phone reservations and card-on-file deposits, many businesses use a virtual terminal for keyed transactions. Our explainer on taking card payments without hardware shows how voids and captures work in that setting.
Scripts for Explaining Pending Charges to Customers
Even with clean processes, the issuer's timing will sometimes leave a hold visible after the final charge posts. Staff need short, clear language for these calls. Adapt the following to your business.
At check-in or when opening a tab: "We'll place a temporary hold on your card for [amount]. It isn't a charge. It reserves funds in case of extra charges. When you check out, we'll charge only what you actually spent and release the rest. Your bank controls how quickly the hold disappears from your account."
When a customer calls about a "double charge": "I can see one final charge of [amount] on our end. The other item you're seeing is the original hold, which we released on [date]. Your bank removes it on their schedule, and it usually disappears without any action from you. If it's still showing after a few business days, your bank can confirm it was released."
For debit card customers at check-in: "Since this is a debit card, the hold will reduce your available checking balance until it's released. If you'd prefer, you can use a credit card for the hold instead."
Follow-up email template: "Thank you for staying with us. Your final charge was [amount]. We released the remaining hold of [amount] on [date]. Pending amounts are removed by your card issuer, and timing varies by bank. Contact us at [phone/email] if you have questions."
Two rules for staff:
- Never tell a customer the hold "will be gone by tomorrow." You don't control that timing.
- Never run a second transaction to "fix" a pending item. That's how one hold becomes two.
Next Steps: Getting Your Setup Right
Most hold complaints trace back to configuration: whether your terminal or POS uses incremental authorizations, sends partial reversals and voids cleanly before batch close. If your team gets frequent double-charge calls, review how your system handles each of those steps. If you also run self-service equipment, see our guide to unattended payment terminals for vending, laundry and kiosks.
MannyPay supports hotels, restaurants, travel businesses and event and ticketing promoters with in-person, online and keyed acceptance. To review how your current setup handles authorizations, request a free quote from MannyPay and talk through your workflow with the team.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


