Every card payment moves through two distinct steps: authorisation, which confirms a customer has the funds or available credit for a transaction, and capture, in which the funds are collected. By delaying capture, a business allows itself time to calculate the final bill or check whether it has the inventory to fulfil the order.

Below, we'll discuss how authorisation and capture work as separate steps in the payment cycle, when delaying capture might help a business, and what happens when an authorisation hold expires before it's used.

Key takeaways

• Authorisation places a temporary hold on a customer's funds to confirm the transaction amount will be available, while capture is a separate step in which the funds are transferred.

• Delaying capture often benefits businesses such as hotels, e-commerce sellers, and marketplaces that need to confirm a final bill or fulfilment status before collecting payment.

• Authorisation holds expire within a time frame the card network sets. Capturing after that time frame closes usually requires running a new authorisation.

What is payment authorisation?

Authorisation is the first automated step in a card transaction. When a customer uses their card to pay, the business's payment provider sends the transaction details to the acquiring bank, asking whether the cardholder has enough available credit or funds for the transaction. The acquiring bank sends the request to the card network, which, in turn, forwards the request to the issuing bank. The issuing bank then determines whether the account has sufficient funds. If it does, then the bank places a hold on the account for the requested amount, and sends back an approval for the pending transaction. If there are insufficient funds, the bank sends a decline message.

What is payment capture?

Capture is the step in which the business asks to receive the authorised funds. The issuing bank converts the pending hold into a posted charge, and the funds start moving through the card network, towards the business's account. Until capture happens, the transaction is just an approved hold that can still be cancelled or left to expire.

When does delayed capture make sense to use?

Delayed capture adds time to the payment process, so a business needs to determine whether it's actually beneficial to use.

Multiple industries and business models depend on delayed capture:

• Hotels and travel: A hotel typically requests a hold on a customer's card at check-in to secure funds for the room and estimated incidentals, then captures the final amount – adjusting for minibar charges or room service – at checkout. Rental car companies and cruise lines usually follow a similar pattern. They have an authorisation hold placed on an estimated amount up front and capture the adjusted total after the trip or rental contract ends.

• E-commerce fulfilment: Businesses that ship products often request an authorisation hold at the time of purchase but wait to capture payment until the seller confirms an order has left the warehouse. Then, if an item is out of stock or cancelled before shipment, the customer is not charged.

• Platforms and marketplaces: A platform connecting customers and sellers sometimes requests that the issuing bank authorise a hold for a transaction when an order is placed. Then, it waits to capture payment until the seller confirms the order has been fulfilled or the service has been delivered. This protects the customer from paying for something that might not arrive, and, if a dispute happens, it gives the platform a natural point to intervene before any money has moved.

• Usage-based and estimate-driven services: A repair shop might request an authorisation hold on the estimated amount before fully inspecting a vehicle. This lets the shop know most of the payment is secure before it begins work and gets a better idea of the total cost. Delayed capture can similarly benefit any business that doesn't know the final price until work is underway.

What are the risks of authorisation window expiry?

Authorisation holds expire. Time frames vary by card network and the way a transaction is coded, but they often last less than two weeks for standard purchases. Longer time frames are often set up for hotels, rental cars, and similar categories where the final amount isn't known at the time of authorisation. The exact hold time can also shift depending on whether the transaction is card-present (CP) or card-not-present (CNP).

If a business tries to capture a transaction after the authorisation hold has expired, the charge typically fails, since the issuing bank no longer has funds reserved for that hold. The business then has to attempt a new authorisation, which means the customer's card is checked again to see if a new hold can be placed. If the original card has since been cancelled, has reached its limit, or the customer's available balance has changed, a new authorisation hold might be declined, even though the first one succeeded.

A few practices reduce the chance of running into this:

• Track authorisation dates alongside order status: This is important if your business operates with variable fulfilment timelines.

• Build alerts for orders approaching an expiration deadline: This gives your business time to either capture or reauthorise before the hold lapses.

• Match your capture strategy to your fulfilment timeline: If your business regularly ships within two to three days, then you might largely sidestep expiration issues with automatic or near-automatic capture. If your business requires longer fulfilment times, you might need a reauthorisation step built in for at-risk orders.

Automatic and manual capture: What's best for your business?

The decision between automatic and manual capture depends on how much the final transaction amount is likely to change between the time of purchase and when your business is ready to collect payment.

Automatic capture is generally a good model if the order is complete the instant it's placed. This works well if your business manages retail transactions, digital purchases, or subscriptions. Usually there's no fulfilment gap to manage, so delaying capture just adds overhead.

Manual capture is worth the extra step when your business needs a delay between authorisation and payment, whether to confirm stock is available, to verify a service was delivered, or to calculate a final bill. It also gives your business time to catch a cancelled order or take action on any signs of fraud before money moves, which matters more if your business handles higher-ticket purchases or deals with elevated dispute rates.

Stripe's Payment Intents API supports both manual and automatic capture, allowing your business to decide which approach is best. It can be paired with Stripe Radar to help your business evaluate the risk of a transaction, which adds a layer of protection.

How Stripe Radar can help

Stripe Radar helps detect fraud and unlock growth, using artificial intelligence (AI) trained on data from Stripe's global network. Radar helps protect your business from fraud throughout the customer lifecycle before it affects your bottom line, while helping you approve more legitimate customers and payments.

Radar can help your business:

• Prevent fraud losses: Radar's AI learns from more than US$1.9 trillion in annual transactions across Stripe's global network, helping it identify and block fraud patterns that individual businesses might not catch on their own.

• Unify protection across evolving fraud attacks: Radar brings protection against transaction fraud, account fraud, and customer abuse all into one solution, so you gain unified protection across major fraud types.

• Adapt as fraud evolves: Radar continuously adapts to changing fraud patterns, from first-party abuse to agentic transactions, helping protect your business against emerging threats.

• Work with your existing tech stack: Use Radar with Stripe payments with no integration required, or access Radar's intelligence through programmable APIs, whether you process payments on Stripe or not.

Learn more about Stripe Radar or get started today.

FAQs about authorise and capture