Authorisation holds explained: How they work in card payments

Payments
Payments

Accept payments online, in person, and around the world with a payments solution built for any business – from scaling startups to global enterprises.

Learn more 
  1. Introduction
  2. What is an authorisation hold?
  3. How do authorisation holds work for card payments?
  4. When are authorisation holds commonly used?
  5. Why do businesses place authorisation holds on cards?
  6. How do authorisation holds affect available balance or credit?
  7. How long does an authorisation hold last?
  8. How Stripe Payments can help

Authorisation holds play a critical role in payment systems. They handle variable transaction amounts, help manage risk and keep card payments in sync with real-world fulfilment.
When you see a pending charge or notice that your available balance dropped more than it should have, you might be seeing the result of authorisation holds.

Below, we explain how an authorisation hold works in credit and debit card transactions, how they affect available balance and credit and why businesses use them.

What's in this article?

  • What is an authorisation hold?
  • How do authorisation holds work for card payments?
  • When are authorisation holds commonly used?
  • Why do businesses place authorisation holds on cards?
  • How do authorisation holds affect available balance or credit?
  • How long does an authorisation hold last?
  • How Stripe Payments can help

What is an authorisation hold?

An authorisation hold is a temporary reservation of funds on a credit or debit card. The hold is placed the moment a card payment is approved and stays there until the transaction is finalised. While the hold is active, the bank sets aside the transaction amount so that it can't be spent elsewhere.

An authorisation hold might show up on a banking app or bank statement as a pending charge, with the final charge appearing later. This can be confusing and create the impression of two transactions when there was really only one.

How do authorisation holds work for card payments?

Authorisation holds create a controlled pause between a transaction's approval and its completion. They make sure funds are available while giving businesses time to finalise the transaction.

Here's how it works:

  • The business requests authorisation: When a customer submits a card payment, the business first asks the issuer to approve the payment.

  • The issuer reserves funds: If the transaction is approved, the issuer places an authorisation hold on the customer's account. The hold reduces the customer's available balance or credit, even though money hasn't actually moved yet.

  • The transaction appears as pending: The hold typically shows up as a pending transaction, visible on the customer's account. This signals that the payment is approved, but not yet final. Some holds are only there for a few seconds, but others might last for days. Timing depends on how long it takes the business to finalise the transaction.

  • The business captures the payment: Once the final amount is known or the service is delivered, the payment is captured.

  • The hold becomes a posted charge: After capture, the authorisation hold is replaced by a finalised charge for the actual amount (which might be lower or higher than the original hold). Funds are transferred to the business, and the transaction posts to the customer's account.

  • Uncaptured holds are released: If the business doesn't complete the transaction, the hold eventually expires or is released by the issuer. The reserved funds return to the customer's available balance or credit.

When are authorisation holds commonly used?

Authorisation holds are generally used when transaction totals are unknown at the initial moment of purchase or when payment timing is unclear. Sometimes, the amount and the timing are both in flux.

Here are some scenarios where authorisation holds are common:

  • Hospitality and lodging: Hotels commonly place authorisation holds at check-in to cover the room, taxes and potential incidentals.

  • Car and equipment rentals: Rental businesses use holds as a security buffer to account for the possibility of damages, late returns or added services. The hold stays in place until the item is returned and inspected.

  • Gas purchases: Pay-at-the-pump transactions typically start with a preset authorisation amount. The final charge reflects the actual fuel dispensed, and the unused portion of the hold is released.

  • Restaurants and bars: When a tip amount or final total isn't known up front, a hold confirms that the card can cover the bill. For example, restaurant transactions are often finalised once the receipt is closed.

  • Preordered or backordered items: When an item isn't immediately available, holds might reserve funds until it's back in stock. If the order is cancelled or changed, the hold is adjusted or released.

  • Subscriptions: Small or zero-amount holds help validate a payment method before a subscription begins. These holds usually expire without becoming charges.

  • High-value or custom purchases: Businesses might authorise payment before producing or shipping expensive or customised items.

Why do businesses place authorisation holds on cards?

Authorisation holds give businesses confidence in a purchase at the moment of approval. They provide financial certainty, even if there isn't enough information yet to make a final charge.

Here are some benefits of authorisation holds:

  • They confirm funds: A hold verifies that a customer has enough available funds or credit at the time of purchase.

  • They manage timing gaps between purchase and fulfilment: Businesses can use authorisation holds to verify a customer's card before shipping goods or delivering services.

  • They leave room for add-ons and buffers: Authorisation holds facilitate up-to-date final amounts without multiple payments. They allow businesses to include added services, usage-based charges or adjustments and to cover potential overages, damages or incidentals.

  • They reduce payment risk: Authorisation holds can catch issues such as expired cards, blocked accounts or insufficient funds.

How do authorisation holds affect available balance or credit?

When a hold is placed, the held amount is removed from what the customer can spend. On a debit card, the hold reduces the available account balance. On a credit card, a hold lowers the remaining credit limit. Several pending holds might stack up and significantly restrict spending power. This can be especially noticeable during travel or other periods of high activity. If a large hold is in place, subsequent charges might fail due to insufficient available funds or credit, even if the posted balance looks as though it should cover them.

In the end, only captured transactions become real charges. If a business releases the hold without capturing the payment, the available balance or credit updates when the issuer processes the change.

How long does an authorisation hold last?

Holds typically last a few days to a week or so. If the business captures the payment sooner, the hold disappears as soon as the charge posts.

Some holds are longer, especially in the hospitality industry: travel, lodging and rental transactions often allow extended authorisation periods. In these cases, holds can remain in place for a few weeks.

When the business completes the transaction, the hold converts into a posted charge. If a hold is released instead, it disappears from the account entirely. It never becomes a charge and doesn't appear on statements.

If a business doesn't capture payment or release the hold within a certain window, the issuer will automatically release it. A hold can only be released by an issuer or the charging business, not the customer.

After a hold expires or is released, some banks update available balances instantly, while others take a bit longer. This delay reflects bank processing cycles, not business decisions.

How Stripe Payments can help

Stripe Payments provides a unified, global payments solution that helps any business – from scaling startups to global enterprises – accept payments online, in person and around the world.

Stripe Payments can help you:

  • Optimise your checkout experience: Create a frictionless customer experience and save thousands of engineering hours with prebuilt payment UIs, access to 125+ payment methods and Link, a wallet built by Stripe.

  • Expand to new markets faster: Reach customers worldwide and reduce the complexity and cost of multicurrency management with cross-border payment options, available in 195 countries across 135+ currencies.

  • Unify payments in person and online: Build a unified commerce experience across online and in-person channels to personalise interactions, reward loyalty and grow revenue.

  • Improve payments performance: Increase revenue with a range of customisable, easy-to-configure payment tools, including no-code fraud protection and advanced capabilities to improve authorisation rates.

  • Move faster with a flexible, reliable platform for growth: Build on a platform designed to scale with you, with 99.999% historical uptime and industry-leading reliability.

Learn more about how Stripe Payments can power your online and in-person payments or get started today.

The content in this article is for general information and education purposes only and should not be construed as legal or tax advice. Stripe does not warrant or guarantee the accuracy, completeness, adequacy, or currency of the information in the article. You should seek the advice of a competent lawyer or accountant licensed to practise in your jurisdiction for advice on your particular situation.

More articles

  • Something went wrong. Please try again or contact support.

Ready to get started?

Create an account and start accepting payments – no contracts or banking details required. Or, contact us to design a custom package for your business.
Payments

Payments

Accept payments online, in person, and around the world with a payments solution built for any business.

Payments docs

Find a guide to integrate Stripe's payments APIs.