Delayed Capture

Delayed capture holds an authorised payment before actually taking the money, often until an order ships or gets confirmed, letting merchants line up payment timing with fulfilment instead of the other way round. Rather than capturing funds the second someone checks out, the merchant reserves the authorisation and only completes the charge once specific conditions are met. It's especially common wherever the exact order, or whether it can even be fulfilled, isn't fully known at the moment of purchase.

The Basic Idea

Delayed capture separates two steps: authorisation, which confirms funds exist and reserves them, and capture, which actually takes the money. That gap can run from a few hours to several days, depending on the business and the card network's hold rules.

How It Actually Runs

A payment authorises at checkout, placing a hold on the customer's funds. The merchant triggers capture later through their payment gateway, usually once something specific happens, like shipping. If the authorisation expires before that, and it can after several days depending on the network, the merchant has to re-authorise from scratch.

Why Merchants Bother

It cuts the risk of charging someone for an order that can't actually be fulfilled, which matters a lot for pre-orders, made-to-order goods or anything tied to stock checks. It also skips a fair amount of refund processing, since money only moves once fulfilment is confirmed.

Tying Payment to Fulfilment

For ecommerce with multi-step fulfilment, linking capture to something concrete, dispatch, say, keeps the payment timeline honest and cuts down on failed transactions from cancelled or out-of-stock orders. See the architecture of a payment gateway for where authorisation and capture sit in the bigger picture.

Delayed vs Immediate Capture

Immediate capture takes the money right at checkout. Simpler, but riskier if fulfilment isn't guaranteed straight away. Delayed capture costs a bit more complexity but matches payment timing to what's actually happening in the business, particularly useful for anyone with variable lead times.

Customers Handle This Fine, Mostly

People are generally okay seeing a payment authorised before it's actually taken, especially for pre-orders or bookings, as long as the merchant is clear about when the charge lands. Say nothing, and customers start wondering why the charge hasn't shown up yet, which turns into support tickets that didn't need to exist.

Where It Shows Up Most

Travel, hospitality, made-to-order retail, anywhere fulfilment depends on a later confirmation, a stock check, a service date. Each industry tends to have its own tolerance for how long a delay can run before the authorisation needs refreshing.

What Happens When Capture Gets Forgotten

It sounds like a small operational detail until an authorisation quietly expires because nobody triggered capture in time, and the merchant has to go back to the customer for a fresh authorisation on an order that should've been simple. Building an automated check into the fulfilment process, rather than relying on someone remembering to hit capture, avoids this exact kind of avoidable friction, especially at any real volume.