Preauthorization vs Sale: Which Transaction Should You Run?

A sale charges the card now. A preauthorization holds the money now and lets you collect later, once the final amount is known. Run a sale when the price is settled and the goods or service are delivered. Run a preauthorization when the final amount is uncertain or the service comes later.

The choice looks small on the terminal screen. It affects cash flow, chargebacks, tip handling, and how your customers read their bank statements. This guide shows you how each transaction works and where each one fits. It also covers the mistakes that cost small businesses money.

TL;DR

• A sale authorizes and captures in one step. The funds move toward your bank account in your next settlement.
• A preauthorization (preauth) only reserves funds. Nothing is paid to you until you capture the transaction.
• Use preauth for tabs, deposits, rentals, fuel, and any job where the final total is unknown. Use a sale for fixed-price, point-of-purchase payments.
• A hold that you never capture or release can sit on your customer’s card for days and trigger complaints. Always finish what you start.
• Ask your processor how its terminal or gateway labels each transaction type. The names vary, the logic does not.

Table of Contents

• What a sale transaction does
• What a preauthorization does
• Preauthorization vs sale: side-by-side
• When to run a sale
• When to run a preauthorization
• How long a hold lasts
• Do customers get the hold money back?
• Common mistakes with preauthorizations
• A simple decision guide
• Preauth vs sale for online and card-not-present payments
• Fees, dual pricing, and what changes between the two
• What about ACH and eCheck?
• Our perspective
• Set up the right transaction flow with Merchant Solutions Corp
• Training your team on both transaction types
• Security and compliance notes
• Quick reference: pick by business type
• FAQ
• Sources

What a sale transaction does

A sale is the default payment most customers expect. The customer taps, dips, or swipes. The card issuer approves the amount. Your system then marks that approved amount for settlement.

In plain terms, a sale combines two steps: authorization and capture. The first step asks the issuing bank whether the card is valid and the funds are available. The second step tells the bank and your processor to actually collect.

One point trips up many owners. Every card payment starts with an authorization. The difference is whether you capture it right away or later. Visa’s developer documentation lists authorizations, verifications, sales, captures, refunds and voids as separate payment functions. That tells you these are distinct actions, not one blur.

What happens after a sale

The approved sale joins your open batch. When the batch closes, your processor sends it for settlement. The money then reaches your bank account on your processor’s funding schedule.

You can still void a sale before the batch closes. After that, you refund it. A refund is a new transaction, so the customer waits for the credit to post.

What a preauthorization does

A preauthorization asks the issuer to approve an amount and set it aside. The customer’s available balance or credit line drops by that amount. You receive an approval code, but you collect nothing yet.

The authorization hold reduces the cardholder’s available funds until the merchant clears the transaction or the hold expires. The customer sees a pending item, not a finished charge.

You then do one of three things:

1. Capture the full amount, which turns the hold into a charge.
2. Capture a lower amount, which collects only what you earned.
3. Void or reverse the preauth, which releases the hold.

Partial captures and incremental authorizations

Many owners assume the hold and the final charge must match exactly. They do not. Visa’s merchant guidance says any merchant may seek an estimated authorization when the final amount is unknown at the start of a purchase. The same document describes incremental authorizations for cases where the first estimate falls short.

That flexibility matters. If you hold $150 and the job costs $110, you capture $110 and release the remainder. If a hotel guest extends a stay, the merchant can raise the authorization instead of starting over.

Visa’s own acceptance page makes a related point. Its authorization solutions let merchants authorize and secure funds for estimated transactions and extend approved authorizations. The aim is fewer re-authorizations, which are a common source of declines.

Preauthorization vs sale: side-by-side

The table shows the real trade. A sale is simple and final. A preauth gives you flexibility and a bit of homework.

When to run a sale

Choose a sale whenever the price is final and the customer leaves with what they paid for. That covers most counter transactions.

• Retail checkout. The cart total is fixed, so there is nothing to hold.
• Quick-service orders. The customer pays and receives the food right away.
• Prepaid services. A haircut package or a gym membership has a known price.
• Invoices. The customer pays a stated amount through a link.

Sales also keep your daily routine light. Nobody has to remember an open item at closing time. For a busy shop, that is a real benefit.

If you run a store, our guide to streamlining retail checkout shows how a clean sale flow speeds up the line.

When to run a preauthorization

Choose a preauth when you need assurance of funds before the final amount exists. These are the common cases.

Restaurants and bars with open tabs

A guest opens a tab. You preauthorize a set amount to confirm the card works. At the end of the night you close the tab with the real total and the tip.

This protects you from a guest who leaves with a declined card. It also keeps the guest’s card out of your hands, since you can hold the tab against the card’s token.

Hotels, motels, and short-term rentals

Lodging is the classic use. You hold the room rate plus incidentals at check-in. At checkout you capture the actual bill. Visa’s guidance covers incremental authorizations for cases where the initial estimate proves too low, which suits an extended stay.

Gas stations and fuel pumps

A customer starts a pump before the fill amount is known. The terminal holds a set amount, then captures the real total when the pump stops. The customer should see a final charge close to what they pumped.

Contractors, HVAC, and repair work

You quote a range, and parts or labor may change it. A preauth for the deposit or the high end of the quote confirms the card is good. You capture the actual invoice when the work is done.

Equipment rentals and gyms with deposits

A refundable deposit works well as a hold. You never touch the money if the customer returns the item undamaged. You release the hold and the customer pays nothing.

Salons, spas, and clinics with no-show policies

A card on file protects your calendar. Some businesses use a small preauth or a stored card, then charge only if the customer breaks the policy. Post the policy where the customer sees it before booking.

Healthcare and dental offices

Practices often verify a card before an appointment, then charge the patient share after insurance settles. A preauth can confirm the card is valid. For the final balance, a sale or a capture of the adjusted amount closes the loop. Follow your own billing and privacy rules for any patient data.

How long a hold lasts

This is the question your customers will ask first. The answer depends on the issuing bank, not on you.

According to a general reference on authorization holds, debit card holds can fall off anywhere from one to eight business days, depending on the bank’s policy. Credit card holds may last as long as thirty days, depending on the issuer.

Those are ranges, not promises. Your best protection is to capture or void promptly. When you void, the hold typically clears faster than if you let it expire, though the customer’s bank controls the posting time.

Tell customers this plainly at the point of hold. A short line works: “We place a temporary hold of $X. We will release any unused amount when you check out.”

Do customers get the hold money back?

Yes, when you release it. The hold never became a charge, so there is nothing to refund. The customer’s available balance returns once the issuer processes the release.

The frustrating part is timing. Your terminal may show the void as complete while the bank still shows a pending item for a few days. Staff should know this, so they can explain it kindly instead of guessing.

Common mistakes with preauthorizations

Most problems come from the same few habits. Fix these and your disputes drop.

1. Never capturing. The hold expires, you never collect, and you chase the customer for payment.
2. Capturing twice. Someone runs a sale on top of an open preauth. The customer is now charged and held.
3. Holding too much. An inflated hold ties up the customer’s credit line and sours the visit.
4. Skipping disclosure. A surprise pending amount looks like fraud to an unprepared customer.
5. Mixing up the labels. Staff select “pre-auth” at the counter when they meant “sale.” The sale never settles.
6. Ignoring the tip step. In a restaurant, the tip must be added before the batch closes.

A short daily checklist solves most of this. Before closing, review open authorizations and either capture or void each one.

A simple decision guide

Ask these questions in order.

1. Is the final amount known right now? If yes, run a sale.
2. Will the customer leave with the goods or service today? If yes, run a sale.
3. Do you need proof of funds before you start work? If yes, run a preauth.
4. Might the total change? If yes, run a preauth for an estimate and capture the real amount.
5. Is it a deposit that may be returned? If yes, run a preauth and release it when the customer meets the terms.

If you answer “yes” to both 1 and 4, something is off. Revisit the quote.

Preauth vs sale for online and card-not-present payments

The same logic applies on your website. An online store that ships physical goods often authorizes at checkout and captures when the order ships. That way you charge only for what you send.

If an item is out of stock, you release the hold instead of issuing a refund. That is cleaner for the customer and avoids a refund line item.

A store with instant digital delivery usually runs a sale, since fulfillment happens at once. Your online and eCommerce payment setup should let you choose either mode per product or per order.

For invoices and remote billing, payment links let the customer pay a stated amount without a call. Understanding how your gateway and processor divide the work also helps. The gateway sends the request, and the processor moves the funds.

Fees, dual pricing, and what changes between the two

A preauthorization on its own does not pay you, so your final capture is the transaction that settles and normally carries the processing cost. Pricing varies by plan, card type, and how a card is entered, so check your own statement and agreement.

If you use a cash discount or dual pricing program, make sure the displayed price and the captured price line up. The amount held should reflect the pricing the customer agreed to. Our overview of what cash discounting is explains the basics. You can also see how dual pricing offsets processing costs.

Do not guess at rates. Ask for a written breakdown of your pricing model, whether it is interchange-plus or a flat-rate plan, and confirm how each transaction type is billed.

What about ACH and eCheck?

Card holds do not exist in the same way for ACH. An eCheck is a request to pull money from a bank account, and it can later be returned. That is a different risk profile.

For recurring service work, such as maintenance contracts, ACH can lower costs. Our post on ACH processing for HVAC companies walks through a typical setup. Our ACH and eCheck page lists published fees, including a Gateway + eCheck plan at 25 USD per month and a 15 USD ACH return fee.

Our perspective

We see the same pattern with new merchants. They sign up, receive a terminal, and use whichever button is nearest. For a retail counter that works. For a restaurant, a hotel, or a contractor, it creates avoidable problems.

We configure equipment before it reaches you, so the transaction types match how you work. A quick-service shop gets a clean sale flow. A bar gets tab and tip handling. A service company gets a way to hold a deposit and capture the real invoice.

Our advice is practical. Train every employee on the two or three transaction types they will actually use. Write down what each button does. Review open authorizations at close.

We also push for plain language with customers. A hold that is explained rarely becomes a dispute. A hold that is a surprise often does.

— Jonathan

Set up the right transaction flow with Merchant Solutions Corp

We serve restaurants, retail shops, service providers, and specialty businesses across the US. Our POS systems arrive configured for the way you take payments. That includes tabs, deposits, and counter sales.

We also run payment processing programs with dual pricing options and transparent pricing. If you want to compare hardware before you decide, read our POS hardware comparison.

Ready to talk through your setup? Start at merchantsolutionscorp.com and tell us how you charge customers today.

Training your team on both transaction types

A good setup still fails if the person at the counter picks the wrong button. Spend ten minutes on this at every new hire’s first shift.

• Show the difference on the actual terminal screen.
• Explain that a preauth is a promise to finish later.
• Practice a void and a partial capture with a test amount.
• Post a one-page cheat sheet by the register.

Set one person to review open authorizations at close. That single habit prevents most of the mistakes above.

Security and compliance notes

Storing a card for a later capture raises a security question. Your system should use tokenization, so the real card number never sits in your records. Ask your provider how stored cards are protected and how your setup fits PCI DSS requirements.

Never write card numbers on paper or in notes. If a customer must give a number by phone, use your payment system’s virtual entry screen and not a notebook.

Quick reference: pick by business type

Use this as a starting point. Your own mix may differ.

FAQ

What is the difference between a sale and an authorization transaction?

A sale authorizes the card and captures the funds in one step, so the money heads to your account at the next settlement. An authorization only reserves the funds. You must capture it later to be paid.

How long do pre-authorizations last?

It depends on the issuing bank. General references say debit holds may drop off in one to eight business days and credit holds may last up to thirty days. Capture or void promptly instead of waiting for expiry.

What is a point of sale pre-authorization?

It is a hold placed at your terminal or POS before the final amount is set. Restaurants use it for tabs, and gas stations use it at the pump. You later capture the real total or release the hold.

Do I get pre-authorization money back?

Yes, if the merchant voids or releases the hold, or if it expires uncaptured. The hold was never a charge, so there is nothing to refund. Your bank may take a few days to show the funds as available again.

Can I capture less than I preauthorized?

Yes. Visa’s merchant guidance describes estimated and incremental authorizations, and a lower final capture is a normal outcome. Ask your processor how partial captures work on your terminal.

Sources

• Visa: Estimated and Incremental Authorization and Reversal Processing Requirements
• Visa: Authorization solutions for merchants
• Visa Developer: How to use VisaNet Connect Acceptance
• Wikipedia: Authorization hold

Recommended

• Retail Payment Processing Guide
• Authorize.Net Payment Gateway