Incremental Authorization

An incremental authorization is an additional card authorization request that increases the total amount approved on an existing transaction. It is used when a merchant starts with an estimated authorization but the final cost grows, for example when a hotel guest adds nights, orders room service or uses the minibar, or when a rental car is kept longer than planned. Each increment is linked to the original approval, so the issuer sees one transaction with a rising total rather than several unrelated purchases.

Card networks allow incremental authorizations only for certain merchant types and transaction kinds, identified by the merchant category code (MCC) and by indicators in the authorization message. The feature sits alongside the payment authorization reversal, which reduces an approval, and partial authorization, in which the issuer approves less than was asked.

Picture a bar tab. When you sit down, the bartender takes your card and opens a tab. Every new round is added to the same tab, and you pay once at the end. Nobody runs your card again for each drink.

Incremental authorization is the card-system version of a running tab. The hotel or car hire firm first asks the bank to hold a rough amount. If your stay or rental grows, it asks the bank to add a bit more to the same hold, and the bank says yes or no. At checkout, the merchant charges the final bill once. Because everything sits under one tab, the bank knows the extra holds belong to the same stay, and you are not left with several separate blocks on your money.

1. Estimated authorization. At check-in or vehicle pickup, the merchant sends an authorization flagged as an estimate, based on expected charges such as the room rate for the planned stay plus a margin for extras allowed by network rules.
2. Incremental requests. As costs rise, the merchant sends one or more incremental requests quoting the original transaction identifier. Each asks for the additional amount, and the issuer approves or declines it based on available funds or credit.
3. Final clearing. At checkout, the merchant submits one clearing record for the actual total through its acquirer, which is matched to the original approval and its increments.
4. Release of any surplus. If the total approved exceeds the final bill, the merchant sends a partial reversal so the unused amount is released.

The total approved hold at any point is the sum of the original and each increment:

• $H$ is the total amount held on the card.
• $A_0$ is the original estimated authorization.
• $A_i$ is the amount of the $i$-th incremental authorization, and $n$ is the number of increments.

For example, a hotel authorizes $450 for three nights. The guest stays a fourth night ($150) and runs up $60 in restaurant charges, so the hotel sends two increments. The hold becomes $H = 450 + 150 + 60 = 660$. The final bill is $640 after a discount, so the hotel clears $640 and reverses the remaining $20.

Eligibility is set by each network and varies by region. Typical eligible sectors include lodging, vehicle rental, cruise lines and some transport and entertainment merchants where the final amount depends on use. Networks have widened the list over time, but a merchant outside the permitted MCCs should expect an incremental request to be declined or treated as a new authorization. Because the merchant usually keeps the card details for later charges, incremental authorizations often go together with card-on-file storage and are classed as a kind of merchant-initiated transaction (MIT) that follows an initial customer-initiated transaction.

A related practice, used in restaurants and taxis, is the authorization adjustment for gratuities, where the cleared amount may exceed the approval by a tolerance allowed in network rules. This is different from an incremental request, because no new message is sent to the issuer before clearing.

For merchants, the benefit is better protection against unpaid bills. Without increments, a hotel that clears more than it authorized risks a chargeback for the unapproved part. Linking increments to one transaction also keeps the cardholder's statement simpler and helps the issuing bank assess risk with full context.

For cardholders, the risk is tied-up funds. Large holds on a debit card can reduce the balance available, or the unused limit on a credit card for other spending, sometimes for days after checkout if the merchant is slow to clear or reverse. Regulators and consumer groups have long raised complaints about hotel and car rental holds for this reason. Issuers may decline an increment if the cardholder's balance is short, which can lead to an awkward conversation at the front desk, a deposit request or a second card.

• Quote the original transaction. Every increment must carry the original network transaction identifier, or the issuer may treat it as a separate purchase.
• Keep the estimate realistic. Over-large initial holds annoy guests and may break network rules on estimates.
• Close the loop quickly. Clear the final amount and reverse any surplus promptly after checkout, since networks monitor unreleased holds.
• Use a clear descriptor. A recognisable merchant descriptor helps guests match pending holds to their stay.

• Visa
• Mastercard