What is incremental authorization? Definition and example

Incremental authorization

An incremental authorization is a request to raise the amount of a card authorization that is already approved but not yet captured, used when the final total grows after checkout, such as a longer hotel stay, a car rental or an order with added items.

Also called: incremental auth, authorization increment, authorization adjustment, top-up authorization

Updated 19 October 2026

How does incremental authorization work?

The merchant first authorizes an estimated amount and leaves it uncaptured. When the total grows, it sends an increment request that references the original authorization, and the issuer approves or declines the higher amount. Stripe’s documentation says each increment shows on the customer’s statement as an additional pending entry until capture, when the entries are replaced by one final charge. It also says an increment does not extend the validity period of the original authorization, so the merchant must still capture before it expires. Adyen calls the same feature an authorization adjustment and requires the first payment to be sent as a pre-authorization, because its default final authorization cannot be adjusted.

Why does it matter?

It lets a merchant charge the real total without starting again. As an illustrative example: a car rental company authorizes 300 euros for a three-day booking. The customer keeps the car two extra days, so the merchant requests an increment of 200 euros. If the issuer approves, it captures 500 euros against one authorization. If not, it can still capture the original 300 euros and collect the rest another way.

What are the limits?

Support varies by scheme, merchant category and issuer. Stripe lists Visa, Mastercard, American Express, Discover and UnionPay, with Discover and UnionPay limited to categories such as hotels, car rental and passenger transport, and says some American Express issuers do not support it. Adyen notes that the issuing bank ultimately decides whether to allow an adjustment, and that it does not work for V Pay cards. Stripe notes that most card networks prohibit increments where the amount should be known at authorization, such as subscription charges.

Where does Omno use it?

Incremental authorization is handled by the PSP and acquirer that hold the original authorization, so availability depends on the connected provider and the card scheme. Omno’s routing-decision log shows which provider authorized each payment, which is where any increment has to go, and final status arrives by webhook.

Frequently asked questions

What happens to the original authorization if the increment is declined?

Nothing changes. Stripe's documentation says a declined increment returns a card declined error and the payment remains capturable for the amount already authorized. The merchant can capture that amount and collect the difference separately, for example through a new payment the customer approves.

Is an incremental authorization the same as a new payment?

No. An increment adds to an existing authorization and is captured with it as one charge, while a new authorization creates a separate payment with its own validity window. Adyen describes the increase as an adjustment to a pre-authorized payment that is then captured manually.

Does an incremental authorization need 3-D Secure again?

Usually not. Stripe's documentation says that where strong customer authentication rules apply, the first authorization needs 3-D Secure and later increments are treated as merchant-initiated, which can exempt them from further authentication. The customer should be told at checkout that the amount is an estimate and may increase.