What Is an Authorization Hold?

‍An authorization hold is a temporary reservation of funds a payment processor places on a customer's card to confirm the money is available. It isn't a charge. No money reaches the merchant until the hold is captured as a real transaction, and an uncaptured hold expires and releases on its own.

Gas stations, car rentals, hotels, and restaurants estimating a tip use holds most, because the final amount isn't known at the swipe.

Key takeaways

• An expired hold forces a second authorization attempt.
• Most holds release within 1 to 5 business days.
• Hotel and car rental holds can sit up to 30 days.
• Mismatched holds trigger Visa 11.2, Mastercard 4808, and Amex A02.
• A descriptor customers don't recognize reads as an unauthorized charge.

How long an authorization hold lasts

Most authorization holds release in 1 to 5 business days, but the exact window belongs to the customer's bank. Some categories run to 30 days.

Your processor can ask for an early release, and often will if you call. The issuer still decides. That's why two customers who bought the same thing wait different amounts of time.

Hotel and car-rental codes authorize an estimated total covering incidentals, fuel, and damage. Issuers give those codes a wider window.

Picture a $400 hold on a $180 room. That gap is normal there.

Why authorization holds matter for merchants

A hold that expires unused, or settles at an amount the customer didn't expect, is what produces "unauthorized transaction" and duplicate-charge disputes.

The customer still sees "pending" days after the sale. Or they read a figure they don't remember approving. Either way they call their bank, because "processor mechanic" and "someone charged me wrong" look the same from a statement.

The bank files that call under an authorization code. On Visa it's 11.2 for a declined authorization, or 11.3 for none at all. Mastercard uses 4808 and 4837, Amex uses A02 and A08, and Discover uses DA and NA.

Each code asks for different evidence, so a generic response never supplies what the code wants.

A clean authorization settles at the same amount and captures inside the issuer's window, so the customer sees no mismatch. The risk sits in holds that expire, drift, or capture late.

Reducing authorization-hold disputes

You cut hold-related disputes by keeping the authorized and captured amounts close, capturing fast, and using a name customers recognize. Three fixes, each closing a different mismatch:

• Authorize the real amount: Cap padding at a modest percentage over the expected total, then email the final figure the day you capture.
• Capture within 24 hours: Set your processor to auto-capture on fulfillment, so no authorization expires and forces a second attempt.
• Use a recognizable descriptor: Put your storefront name and a support number in the billing descriptor field, then read it back on your own statement.

Run your own hold-related dispute count through our ROI calculator to see what a mismatch is costing you.

The descriptor is the one merchants skip most, and the cheapest of the three.

Ethoca and Verifi alerts reach you on these codes while a refund still resolves the case. Our chargeback alerts guide has each network's timing window.

These fixes only reach disputes the hold caused. Card-present fraud is a separate problem.

Authorization hold vs. pending charge

A pending charge is the line the customer reads, while an authorization hold is the reservation that usually produces it.

Every authorization hold shows up as a pending charge. The reverse isn't true. A charge can also read as pending because it already settled and is waiting for the bank's next statement cycle.

Say a gas station pre-authorizes $100 and the pump total is $42. The statement shows "pending $100" for a day or two, then "posted $42."

The display never changes, but the object under it changes twice.

Casual talk collapses the two, and for a cardholder that's fine. A merchant reading a dispute needs the difference. Only the hold codes apply to a reservation, so a display-lag charge comes back under a different code and takes different evidence.

Neither one is a rolling reserve, which holds back part of your payout across the whole account instead of one sale.

FAQ

Can a customer dispute a hold before it becomes a charge?

No, because there's no settled transaction to reverse yet. The bank usually tells the cardholder to wait for the release or call the merchant.

What happens if an authorization hold is never captured?

Your processor drops the authorization at expiry, and no settlement record is created. You have to re-authorize the card to collect.

Why do hotels hold more money than the actual bill?

Their codes authorize an estimated total, because nobody can price incidentals at check-in. The gap releases on the issuer's schedule after capture, so it can outlive the real bill by days.

Can a merchant access held funds before capturing them?

No. The money stays in the cardholder's account, unavailable to them but not yours until capture and settlement finish.