Incremental Authorization: Adjusting Holds for Tabs and Stays
Incremental authorization lets hotels and bars raise an existing card hold instead of stacking new ones. Learn the network rules, limits and setup.

Photo: Pixabay
On this page 6 sections
Key takeaways
- When a tab or folio grows, raise the original authorization. A second full authorization stacks on the first and can get the customer's card declined.
- Eligibility depends on your merchant category code under card network rules. Changing your code to qualify is miscoding and puts your account at risk.
- Authorizations expire. Long stays and extended rentals need reauthorization or interim billing before the window closes.
- Before you rely on incremental authorization, confirm that every piece of your equipment, from terminal to gateway, supports it.
Incremental authorization lets you raise the amount on a card authorization you already hold, so you don't have to run a new one. A hotel that authorized three nights at check-in can add a fourth night to that same approval. A bar can top up an open tab when the table orders another round. Your customer sees one hold that grows, and you settle against a single authorization trail when the stay or tab ends.
There are limits. The card networks decide which businesses may use it, and no hold lasts forever. Below is how incremental authorization works for bar tabs and hotel folios, why repair shops usually need a different approach, and what to ask your processor before you depend on it.
Estimated vs. Incremental Authorization: Two Parts of One Sale
An ordinary authorization asks the issuer (the customer's bank) to approve a known amount. On a credit card, that amount comes off the available credit. On a debit card, the funds are set aside. You capture the sale later. If you want the basics first, start with our explainer on what an authorization hold is and how pre-auths work.
An estimated authorization covers sales where nobody knows the final amount yet, like check-in at a hotel front desk or a bartender opening a tab. You authorize your best estimate, and a flag on the transaction tells the issuer that more may follow. Visa's rules use the term "estimated authorization." Mastercard describes the same idea as a pre-authorization, which it distinguishes from a final authorization for a fixed amount. American Express and Discover handle this in their own ways, so ask your processor how each brand is treated on your account.
An incremental authorization adds to that estimate. It references the original transaction, so the issuer treats it as part of the same purchase. When the stay or tab ends, you capture the actual total once against the combined approved amount, and the unused portion is released. Our guide to authorize vs. capture timing covers that last step in detail.
The difference for the customer is simple. A new authorization stacks on top of the first one, while an incremental one extends the hold that's already there.
Which Merchant Types Can Use Incremental Authorization
Eligibility is a card network rule tied to your merchant category code (MCC). This is the code assigned during underwriting that tells the networks what kind of business you run. Each network publishes a list of MCCs allowed to use estimated and incremental authorizations. The lists center on businesses that can't know the final bill at the start. Lodging and vehicle rental are the classic examples, and restaurants and bars appear too. Because the lists differ by network and change over time, confirm your current eligibility with your processor. Don't rely on any summary, this one included.
That has two practical consequences.
First, your MCC has to describe what you actually sell. If your business isn't eligible, asking for a lodging code won't solve the problem. A code that misrepresents your business is miscoding. It breaks network rules and can end with your account closed and your business placed on the MATCH list. Running two genuine businesses is a different situation. If you have, say, a restaurant with guest rooms upstairs, ask whether the rooms should get their own merchant account with their own code.
Second, being eligible on paper doesn't mean your equipment can do it. Every link in the chain, from the card reader to the gateway, has to support sending an incremental request tied to the original approval. Plenty of setups can run a pre-auth and a later completion but can't top up in between.
Auto Repair Usually Needs a Different Workflow
Repair shops share the hotel's problem: the estimate at drop-off rarely matches the final invoice. Auto repair generally isn't one of the categories this framework was built for, though, so check before you assume the feature is available. Some shops take a pre-authorization for deposits at drop-off. That carries its own risk, because a job that waits days for parts can outlast the hold.
For most shops, it's cleaner to run the deposit as a normal sale and charge the balance at pickup, when the customer is standing at the counter to tap or insert the card. Avoid copying a card number at drop-off and keying the total days later. A keyed sale counts as card-not-present, which usually costs more and gives you less protection in a dispute. Our article on interchange downgrades and how to fix them explains why. When a customer approves extra work by phone, get that approval in writing, on the work order or by text. Still charge in person at pickup whenever you can. MannyPay works with auto repair shops on in-person payment setups.
How Bar Tab Authorization and Hotel Folios Work
Bar Tabs
Opening a tab usually triggers an authorization for a preset amount you configure in the POS. You also set a trigger point. Once the tab passes it, a POS that supports incremental authorization sends a top-up request for the difference. At close-out, the server captures the final total plus tip.
Tips get special handling. Network rules give restaurants and bars some room to capture more than the authorized amount, since nobody knows the tip when the card is first run. That tolerance has a ceiling. It exists for gratuity, not for a tab that grew from one drink to eight. If you capture far beyond what the issuer approved, the issuer can reject the settlement, and you'll be in a weak position if the customer disputes the charge. Ask your processor what tolerance applies to your account and set your incremental trigger below it.
Your opening amount should reflect how your guests actually spend. Consider a cocktail bar where two drinks with tip already exceed the default. It needs a higher setting or an earlier trigger than a neighborhood bar running beer tabs. Closing out at the table also helps, because the card never leaves the guest's sight. See our piece on pay-at-the-table handhelds and MannyPay's restaurant and bar processing options.
Hotel Folios and the Incidental Hold
At check-in, a hotel runs an estimated authorization for the booked nights with taxes and fees included. A hotel incidental hold sits on top of that to cover extras like parking or the minibar. As the folio grows, or when a guest extends, the property management system sends an incremental authorization whenever expected charges exceed what's already held. At checkout, the system captures the final folio and releases the rest.
Guests usually get frustrated at the release step. When you capture less than you authorized, or send a reversal, you're telling the issuer to free the difference. How fast that money reappears in the customer's available balance is up to the issuer. Your job is to capture promptly and confirm that your system actually sends the reversal. Our article on how long authorization holds last and how to release them covers the timing. Vehicle rentals and tour operators follow the same pattern. MannyPay works with hotels and lodging properties and travel businesses, and it also serves leasing and rental companies.
Avoiding Duplicate Holds on Customer Cards
Most hold complaints trace back to one mistake: running a second full authorization when a stay or tab grows. That first hold doesn't disappear. It stays on the card until you reverse it or it expires, so the customer's available credit shrinks by both amounts.
The table below is an illustrative example, not real rates for any market. It assumes a flat nightly rate that already includes tax, plus a fixed incidental hold.
| Step | Incremental authorization | Stacked new authorization |
|---|---|---|
| Check-in, 3 nights at $200 + $100 incidental hold | $700 held | $700 held |
| Guest extends to 4 nights | +$200 incremental request | New $900 request (4 nights + incidentals) |
| Total held if every request is approved | $900 | $1,600 |
| Same guest, but only $800 available after check-in | $200 top-up approved | $900 request declined |
| Checkout: 4 nights ($800) + $40 minibar | Capture $840, release $60 | Capture $840, release $760 across two holds |
Look at the fourth row. If the guest's remaining credit covers a top-up but not a second full authorization, the stacked approach fails at the front desk, and staff have to ask an annoyed guest for another card. Even when both approvals go through, the guest heads to dinner carrying holds nearly double the real bill. Debit cardholders have it worse. For them, that's cash missing from their checking account until the extra hold drops off.
These habits prevent it:
- Train staff that "add to the hold" and "run the card again" are different buttons. Nobody should run a fresh sale or pre-auth for a guest who already has an open authorization.
- Make sure your system reverses any authorization you won't capture. The networks expect unused approvals to be released, and some processors pass along network fees for authorizations that are never settled or reversed.
- Capture once, at the end, for the real total. Don't split a single folio or tab into several captures unless your processor has set you up for interim billing.
- Review a report of open authorizations by age every day so nothing quietly expires.
Reauthorization After a Hold Expires
No authorization stays valid forever. Network rules set a validity window that depends on the card brand and your MCC, and estimated authorizations are treated differently from standard ones. Lodging and rental categories generally get longer windows than ordinary retail. Those windows still close. Confirm the exact limits for your account with your processor.
If you capture against an expired authorization, you're effectively settling without approval. The issuer can decline that capture. Even if it goes through, the sale may be priced higher, and you no longer have an approval to point to if the charge is disputed. A reauthorization solves this. It's a new request, linked to the original transaction, for the amount still outstanding. If it's declined, that's useful information, and you're better off learning it midway through a long stay than at checkout.
For long stays and extended rentals, you'll have to choose between reauthorizing and billing in stages. If guests often stay past your validity window, interim billing tends to work better. You capture the folio weekly and open a fresh estimated authorization for the next period. Every capture lands inside a valid window, and the customer's statement tracks their stay. You never end up carrying weeks of unsettled charges.
Setting up Incremental Authorization With Your Processor
Before you build a front-desk or bar workflow around incremental authorization, get answers to these questions in writing:
- Is my MCC eligible for estimated and incremental authorizations on each card brand I accept?
- Does my equipment, from terminal to gateway, support incremental requests linked to the original authorization, or only pre-auth and completion?
- What authorization validity windows and tip tolerances apply to my account?
- Does the system send partial and full reversals automatically at capture, or does staff have to trigger them?
- Can keyed and virtual terminal transactions use the same flow, or does it work only with the card present?
- Which network fees for unreversed or expired authorizations can be passed through to me, and where will they appear on my statement?
If the answer to question 2 is no, your equipment is the gap. Compare POS systems that fit hospitality workflows with what you run now. Then match one month of deposits against your folios or tabs. Our guide to monthly credit card reconciliation shows how to spot stacked holds and late captures. To review your setup with a specialist, request a free MannyPay quote and bring a recent statement and a list of the devices at your front desk or bar. A MannyPay specialist responds within one business day.
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.


