The short answer
An incremental authorization is a message that increases the amount held on a prior authorization without canceling and recreating it. If a hotel authed $200 at check-in and the guest adds $300 of room-service charges, the hotel submits a $300 incremental auth. The original auth's transaction identifier is preserved, the held total grows to $500, and when capture runs at check-out, it settles against the full combined amount.
When incremental auth is used
- Hotels and lodging: Original auth at check-in for room rate + incidentals deposit. Incrementals each night or as charges accumulate (minibar, spa, restaurant).
- Car rental: Initial auth for estimated rental + deposit. Incrementals for extensions, damage fees, fuel.
- Rideshare / taxi: Estimated fare authed at trip start. Incremental if the trip extends or takes a longer route.
- Bar/restaurant open tabs: Initial auth when card is dropped. Incrementals as tab grows.
- In-flight commerce: Airlines auth for duty-free purchases with incremental additions.
- Dynamic SaaS usage: Rare but possible — usage-based billing scenarios where the final charge exceeds initial auth.
Card-brand rules
- Visa: Supported on specific MCCs — lodging, car rental, cruise line. Message type 0100 or 0101 with transaction identifier linking to original.
- Mastercard: Similar MCC-restricted support. "Estimated authorization" pattern documented.
- Amex: Longer-running auth windows make incrementals less critical but supported.
- Discover: Support added in 2020-2022 for key MCCs.
Outside the approved MCCs, attempting an incremental auth might be rejected by the network or recategorized as a fresh auth — causing a second hold instead of growing the first.
What operators need to know
- Better than re-authing. A fresh auth for $500 + the original $200 auth = $700 held. The customer sees two charges. Incremental auth keeps it clean — one linked auth, one total.
- MCC has to be on the approved list. If you're not in an eligible MCC (3500-3999 lodging, 7512 car rental, etc.), incremental auths may not work. Check with your processor.
- Approval rates decline on incrementals. The issuer's risk engine sees a growing auth and can decline if the incremental amount exceeds some threshold or the cardholder's pattern doesn't fit. Build fallback: decline incrementals gracefully, consider a fresh auth or customer contact.
- Time windows matter. Most card brands cap incremental auth additions to the original auth's validity window (30 days for hotel/lodging, 7 days for most others). Past that, issue a new auth.
- Auth limits accumulate. Original $200 + four $100 incrementals = $600 total held. Don't assume the cardholder has infinite available balance — excessive holds generate support calls and declines on subsequent attempts.
- Capture against the combined total. At check-out, a single capture against the primary auth's transaction ID settles for the sum of original + all incrementals. Don't try to capture each incremental separately — most networks won't allow it.