# Authorize, raise the hold if the order grows, then capture

[Charge now or authorize first](https://devportal.qa.winkpg.io/docs/decide/charge-now-or-authorize-first.md): Whether to take the money in the same request as the approval, or hold the funds and capture them when you deliver.

Keep one authorization for the whole order and raise it, rather than adding a second payment beside the first.

**Your answers so far**

- When do you deliver what the customer paid for? Within a few days of the order.
- Can the final amount change before you deliver? It can go up.

**What to build**

Authorize the amount you know about when the customer orders. When the order grows, send an IncrementalAuthorization on the operations endpoint to raise the existing hold. Capture the final amount when you deliver.

**Worth knowing**

- An incremental authorization sends a new authorization message to the card network, so the issuer can refuse it. Decide in advance what you do with an order that grew past what the customer's bank would approve.
- Not every processor supports incremental authorization. Check that the merchant's processor offers it before you design around it.
- An authorization is captured once. Capturing less than you authorized releases the rest of the hold, and a second capture for the remainder is refused.

**Where to go next**

- [Authorize now, capture later](https://devportal.qa.winkpg.io/docs/blueprints/authorize-now-capture-later.md)
- [Run an operation on a transaction](https://devportal.qa.winkpg.io/docs/api/transactionOperationsExecuteOperation.md)
- [Transaction lifecycle and settlement](https://devportal.qa.winkpg.io/docs/guides/transaction-lifecycle-and-settlement.md)

- [Start over](https://devportal.qa.winkpg.io/docs/decide/charge-now-or-authorize-first.md): go back to the first question.

## See also

- [All documentation](https://devportal.qa.winkpg.io/llms.txt): the machine-readable index of every public page on this site.