Pre-Authorization
Pre-authorization is a payment hold that verifies funds availability and reserves an amount on a cardholder's account before final capture.
Key Takeaways
- Pre-authorization is a two-step payment process: the merchant first requests a hold on the cardholder's funds through the issuing bank, then captures the final amount later. No money moves until capture.
- Hold amounts often differ from final charges: hotels, gas stations, and car rental agencies authorize estimated amounts that are adjusted at capture, with hold durations ranging from 1 to 31 days depending on merchant category.
- Crypto and blockchain payments skip pre-authorization entirely: on-chain transactions are atomic and final, meaning funds transfer in a single step with no need for temporary holds or delayed settlement.
What Is Pre-Authorization?
Pre-authorization (also called a pre-auth or authorization hold) is the first step in a two-phase card payment flow where the merchant requests the cardholder's issuing bank to verify that funds are available and place a temporary hold on a specified amount. The hold reduces the cardholder's available credit or debit balance without actually transferring money. The merchant then has a window of time to "capture" the transaction and finalize the charge.
This authorize-then-capture model exists because many real-world transactions have uncertain final amounts at the time of purchase. A hotel guest may add room service charges, a driver may pump more or less fuel than estimated, or a car rental may incur additional fees. Pre-authorization gives merchants the flexibility to reserve funds upfront and settle the actual amount later.
Pre-authorization is a foundational concept in card-not-present and card-present commerce alike. It also plays a role in fraud prevention: by verifying card validity and fund availability before goods are delivered or services are rendered, merchants reduce the risk of chargebacks from insufficient funds or stolen cards.
How It Works
The pre-authorization flow involves several parties: the cardholder, the merchant, the payment processor, the card network (Visa, Mastercard), and the issuing bank. Here is how a typical pre-auth transaction unfolds:
- The cardholder presents their card (or enters card details online) to initiate a purchase
- The merchant sends an authorization request for a specified amount through their payment processor to the card network
- The card network routes the request to the cardholder's issuing bank
- The issuing bank verifies the card status, checks available funds, runs fraud screening, and returns an approval or decline code
- If approved, the issuing bank places a hold on the authorized amount, reducing the cardholder's available balance
- The merchant delivers goods or services, then submits a capture request for the final amount (which may differ from the hold)
- The issuing bank releases the hold and processes the actual charge through the clearing and settlement cycle
Authorization Messages
Card networks distinguish between different types of authorization messages. A "pre-authorization" signals that the merchant intends to capture later at a potentially different amount. A "final authorization" signals that the transaction amount is fixed. As of mid-2025, Mastercard requires merchants to explicitly identify each authorization as either pre-auth or final auth, improving transparency in how holds are classified.
The authorization response includes an approval code that the merchant must reference when submitting the capture. This links the two steps and ensures the capture draws against the same reserved funds.
Hold Duration by Card Network
The length of time a pre-authorization hold remains active depends on the card network rules and the merchant's category code (MCC):
| Merchant Type | Typical Hold Duration | Notes |
|---|---|---|
| Standard retail / e-commerce | 5 to 7 days | Visa default is 5 calendar days for card-present transactions |
| Card-not-present (online) | 7 to 10 days | Visa allows 10 calendar days for customer-initiated CNP transactions |
| Hotels and lodging | Up to 31 days | Extended window for variable-length stays and incidentals |
| Car rental agencies | Up to 31 days | Covers fuel surcharges, damage, and extended rental periods |
| Gas stations / fuel | 1 to 3 days | Hold is replaced once the actual pump amount clears |
If the merchant fails to capture within the allowed window, the hold expires and the reserved funds return to the cardholder's available balance. The merchant must then initiate a new authorization if they still intend to charge.
Why Hold Amounts Differ from Final Charges
One of the most common sources of confusion for cardholders is seeing a pending charge that does not match the final bill. This discrepancy is by design. Several scenarios cause the hold amount to exceed or fall below the actual charge:
- Gas stations may authorize a fixed amount ($100 to $175 is common in the US) before the driver pumps, then capture only the actual fuel cost
- Hotels authorize the estimated room rate plus a buffer for incidentals like minibar or room service, then capture the actual total at checkout
- Car rental companies hold the estimated rental cost plus a deposit for fuel, tolls, and potential damage, adjusting at return
- Restaurants may authorize the subtotal before tip, then capture the total including gratuity
The capture amount can be less than or equal to the authorized amount. Some card networks also allow "authorization adjustments" where the merchant can increase the hold within limits (for example, when a hotel guest extends their stay). These adjustments are subject to network-specific rules and may require a new authorization.
Use Cases
Hotels and Lodging
Hotels place a pre-authorization at check-in covering the total estimated stay plus an incidental buffer (often 10% to 20% above the room rate). This hold guarantees the hotel can collect payment even if the guest adds charges during their stay. At checkout, the hotel captures the final bill and the hold is released, though it may take several business days for the released amount to reflect in the cardholder's available balance.
Fuel and Gas Stations
Pay-at-pump transactions are a classic pre-authorization scenario. The pump cannot know in advance how much fuel the driver will dispense, so it sends a pre-auth for a set amount. Historically this was $1 (a simple card validity check), but many stations and card networks have raised the default to $100 or more. Debit card users are particularly affected because the hold reduces their checking account balance directly, which can cause overdrafts if the hold amount is significantly larger than the actual purchase.
Car Rentals
Rental agencies place holds that can exceed the quoted rental price by several hundred dollars. The extra covers fuel refill charges, toll fees, late returns, and potential damage. Holds on debit cards for car rentals can persist for up to 14 days after the vehicle is returned, depending on the issuing bank's policies.
E-Commerce and Subscription Services
Online merchants use pre-authorization in card-not-present transactions to validate cards before shipping goods. This is especially important for high-value items or custom orders where fulfillment takes time. Subscription services may use pre-auth to verify a card is still active before processing a renewal charge.
Pre-Authorization vs. Crypto Payments
Pre-authorization exists because traditional card payments separate the moment of commitment from the moment of settlement. This gap creates complexity: holds can confuse cardholders, tie up funds unnecessarily, expire before capture, or lead to chargebacks when amounts change. Blockchain-based payments take a fundamentally different approach.
On-chain transactions in Bitcoin, Ethereum, and most other blockchains are atomic: the transfer of value happens in a single, indivisible step. There is no separation between authorization and capture. When a user sends a transaction, funds move from sender to receiver once the transaction is confirmed. There is no temporary hold, no pending state that can be adjusted, and no capture window. The concept of payment finality is built into the protocol itself.
This atomicity eliminates several problems inherent to pre-authorization:
- No phantom holds reducing available balances for days
- No discrepancy between authorized and captured amounts
- No expired authorizations requiring re-initiation
- No interchange fees charged on both authorization and capture steps
However, this atomicity also means crypto payments lack the flexibility that pre-authorization provides. A hotel cannot place a hold on a Bitcoin wallet for incidentals. Some smart contract platforms are building escrow-like functionality to bridge this gap: funds can be locked in a contract with conditional release logic, mimicking the authorize-then-capture flow while preserving on-chain transparency. On the Lightning Network, hodl invoices achieve a similar effect by letting the receiver delay settlement of an HTLC until conditions are met.
Stablecoin payment rails are increasingly offering pre-authorization-like features through smart contracts: authorization holds, refunds, and recurring billing logic can all be encoded on-chain with programmable conditions. This represents a convergence of traditional payment workflows with blockchain settlement, combining the flexibility of card-style authorization with the transparency and finality of crypto. For a deeper comparison of these payment models, see the research on stablecoin payment rails vs. traditional systems.
Why It Matters
Pre-authorization is one of the most widely used mechanisms in global card payments, processing billions of transactions annually through the authorize-then-capture model. For merchants, it reduces fraud risk and enables flexible billing. For payment processors and acquirers, it creates an audit trail that helps defend against chargebacks. For consumers, it provides a layer of protection: funds are only captured after goods or services are delivered.
Understanding pre-authorization is essential for anyone building payment systems, whether traditional or crypto-native. As instant settlement becomes the expectation in digital commerce, the gap between authorization and capture is narrowing. Real-time payment networks like FedNow and blockchain-based rails challenge the need for multi-day holds, pushing the industry toward payment models where authorization and settlement collapse into a single event.
Risks and Considerations
Consumer Impact
Pre-authorization holds can temporarily reduce a cardholder's available balance by more than the actual purchase amount. This is particularly problematic for debit card users, where holds block access to real funds in a checking account rather than reducing a credit limit. A $175 gas station hold on a debit card with a $300 balance can leave a consumer unable to make other purchases for days.
Merchant Risk
If a merchant fails to capture within the authorization window, the hold expires and the funds are released. The merchant must then re-authorize, but the cardholder may no longer have sufficient funds. This creates a risk of lost revenue for businesses with long fulfillment cycles. Merchants must also comply with card network rules around hold durations and adjustment limits: capturing an amount significantly higher than the original authorization can trigger chargebacks or network penalties.
Authorization Holds and Fraud
While pre-authorization helps prevent some types of fraud by validating cards before fulfillment, the hold period itself creates a window for friendly fraud. A cardholder might dispute a legitimate hold they do not recognize, especially when the pending amount differs from their expected charge. 3D Secure authentication during the authorization step can reduce this risk for online transactions.
Double-Hold Scenarios
In some cases, both the original hold and the final capture can appear on the cardholder's account simultaneously. This happens when the issuing bank processes the capture before releasing the expired hold. The result is a temporary "double charge" that resolves once the hold falls off, typically within a few business days. While not a true double charge, it can cause confusion and temporary cash flow issues for the cardholder.
This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.