Authorization and Capture: The Gap Where Things Go Wrong

Approving a card and taking the money are two separate events. In between, the customer's available balance has dropped and the merchant has received nothing — and that gap, invisible to the person experiencing it, generates more customer anger than any other routine payment behaviour. The hold that didn't disappear, the second amount that looks like a double charge, the authorization that expired before anyone captured it. None of these is a malfunction. All of them are the gap doing what it does, badly managed.

Two events, not one

	Authorization	Capture
What it does	Checks the card and reserves an amount	Claims the money
Money moves?	No	Yes, into settlement
Customer sees	Available balance drops	A posted charge
Merchant has	Nothing yet	A receivable in settlement
Reversible by merchant?	Yes, promptly	Refund only
Expires?	Yes	No

Row three against row four is the whole problem. The customer's money is unavailable and the merchant doesn't have it. Nobody has it — it's reserved, in a state most people don't know exists.

Which is why the customer framing matters so much. "We haven't charged you" is true and useless to someone whose card is declining at the next merchant. From their position the money is gone and nobody warned them.

When to use each pattern:

• Authorize and capture together — immediate fulfilment: in person, digital delivery, services rendered at the time.
• Authorize now, capture later — shipped goods, work performed after ordering, anything where the amount or the fulfilment isn't final. Per our deposits guide, capturing before delivering creates its own exposure.

The capture window

The operational constraint that catches merchants out.

An authorization is valid for a limited period and the period is shorter than most merchants assume. It varies by card type, merchant category, and issuer.

What happens if you miss it:

• The capture may be refused entirely.
• Or it may settle at a worse rate. Per our downgrade guide, a late capture is a common and quiet cause of a higher effective rate — the transaction goes through and costs more, which nobody notices until someone computes the rate.
• Or the funds may no longer be there, since the reservation lapsed.

Confirm the windows applying to your account with your processor rather than working from general guidance, since they differ by category and change.

Practical implications:

• Capture at fulfilment, and make fulfilment trigger the capture automatically rather than relying on someone remembering.
• Where fulfilment may exceed the window, either authorize closer to shipping or plan to re-authorize deliberately.
• Report on ageing authorizations — see the monitoring section.

When the amount changes

Common in practice and the source of most double-charge complaints.

The final amount differs from the authorized one — a partial shipment, a substitution, a tip, additional nights, a service that ran longer.

Situation	Preferred handling
Final is lower	Capture the lower amount against the same authorization
Final is slightly higher	May be permitted within a tolerance — confirm yours
Final is materially higher	Incremental authorization where supported
Partial shipment	Partial capture; authorize the rest separately at fulfilment
Order cancelled	Reverse the authorization immediately

Incremental authorization — adding to an existing hold rather than taking a second one — is the important capability and it's supported in some categories and not others. Where it's available, use it: a second standalone authorization alongside the first is what customers see as a double charge.

Tolerances for capturing above the authorized amount exist and differ by category, per our tips guide where tip adjustment is the standard case. Exceeding a tolerance risks a downgrade or a refusal, so confirm what applies to you.

Releasing what you won't take

The obligation merchants most often neglect, and it costs the customer directly.

If you're not going to capture, reverse the authorization. Otherwise the amount stays reserved until it expires — which can be days.

What reversal does and doesn't do:

• It tells the issuer to release the reservation, promptly.
• How fast the customer's available balance recovers depends on their issuer, so it may not be instant even done correctly.
• An abandoned authorization is worse in every respect — nothing signals release and the amount sits until it lapses.

When to reverse:

• The order was cancelled.
• The item is out of stock.
• You captured a lower amount and the remainder isn't released automatically — check whether your processor does this.
• A duplicate authorization was taken in error.
• Verification failed and you won't proceed.

The fourth deserves attention. A customer who ordered $340, had $340 authorized, and received a partial shipment captured at $190 may still have $340 reserved if nothing released the difference — and they've been charged once and had nearly twice that amount made unavailable.

Why customers see two amounts

The most common complaint and almost always benign.

Causes:

• An authorization showing alongside the posted charge, until it drops off.
• A second authorization taken instead of adjusting the first.
• A retried transaction after a decline, where the first authorization succeeded but the response was lost.
• Separate authorizations per shipment on a split order.
• A pending amount and a final amount that differ, which reads as two charges rather than one adjusted.

All of these look identical to a double charge in a banking app, and customers reasonably treat them that way — which per our dispute guide means some become disputes that cost you the fee regardless of outcome.

What reduces them:

• Adjust rather than re-authorize, where supported.
• Handle retries carefully, checking whether the first succeeded before re-attempting.
• Reverse promptly, always.
• Use a consistent descriptor, per our descriptor guide — a recognizable name lets a customer call you instead of their bank, which is the difference between a phone call and a dispute.
• Explain it in the confirmation, before they see it.

Estimated authorizations

Where the final amount isn't knowable at the outset — hospitality, vehicle rental, fuel, and services billed on usage.

The practice is legitimate and the customer experience is frequently poor:

• The estimate is usually above the expected total, to avoid re-authorizing.
• So more is reserved than will be charged.
• The customer sees the higher figure with no explanation.
• On a card near its limit or an account with a low balance, this can decline their next purchase — which is how a routine hold becomes a serious problem for someone with little slack, per our liquidity analysis.

Doing it better:

1. Estimate tightly. A large cushion is convenient for you and expensive for them.
2. Use incremental authorization to extend rather than over-reserving at the start.
3. Say the amount out loud at the point of taking it.
4. Say when it will be released, honestly, including that their bank determines the final timing.
5. Capture and reverse promptly at the end.
6. Consider a lower hold for smaller transactions, since the cushion matters least where the amount is smallest and hurts most where the customer has least.

Step three is close to free and eliminates most of the complaints, because the whole problem is that the customer didn't know what to expect.

Telling customers first

Per our descriptor analysis, most payment complaints are recognition failures. The same applies here.

What to say and where:

• At checkout, where you'll authorize and capture later: a line stating that the amount is reserved now and charged on despatch.
• In the confirmation email, restating it — this is where customers look when the amount appears.
• At the point of an estimated hold, verbally, with the number.
• On cancellation, stating that the reservation is released and that their bank determines when it clears.
• On a partial shipment, explaining that each part is charged as it ships.

The cancellation message is the highest-value one and it's rarely sent. A customer who cancelled and sees their money still missing, with no communication, concludes something went wrong — and per our refunds guide, silence during a waiting period is what converts a resolved situation into a dispute.

What to monitor

• Uncaptured authorizations by age, as a standing report. This is money you approved and never took, and it's invisible unless someone looks.
• Captures beyond the window, which indicate a process failure and cost you in downgrades.
• Authorization-to-capture time, by product or channel.
• Reversal rate, and how quickly reversals follow cancellations.
• Duplicate authorizations on the same order.
• Capture amounts differing materially from authorized, which flags where estimates are poor.
• Complaints and disputes citing holds, which tell you where the explanation isn't landing.

The first is the one to build today. Uncaptured authorizations are straightforwardly lost revenue — a fulfilled order nobody captured is goods delivered for free — and in most operations nobody owns the report.

Frequently asked questions

---

This guide is educational and does not constitute legal or compliance advice. Authorization validity periods, capture windows, permitted tolerances, incremental authorization availability, and reversal handling are set by the card networks, your processor, and the issuer, and vary by merchant category and change over time. Confirm the specifics applying to your account with your provider.