What is a Capture?

What Is Capture in Payment Processing?

Capture is the step in a card payment transaction where the merchant confirms that they want to collect the authorised funds. When a card payment is first made, the cardholder's bank places a hold on the transaction amount -- this is the authorisation. Capture is what tells the bank to actually move forward with transferring that money.

In many everyday transactions, authorisation and capture happen almost simultaneously. When you tap your card in a shop or complete an online checkout, the merchant typically authorises and captures in a single step. But in some business scenarios, these two steps are deliberately separated -- and understanding the difference is important for managing cash flow and customer experience.

How Capture Works

The capture process follows authorisation and precedes clearing and settlement:

• Authorisation -- The merchant requests approval for the transaction. The issuing bank checks the card is valid and has sufficient funds, then places a hold on the amount
• Capture -- The merchant submits the transaction for capture, confirming the final amount to be charged. This can happen immediately or be delayed
• Clearing and settlement -- Once captured, the transaction enters the clearing cycle and the funds are eventually transferred to the merchant

If a transaction is authorised but never captured, the hold on the cardholder's funds will eventually expire and the money is released back to them. The expiry period varies by card network and issuing bank but is typically seven to thirty days.

Immediate vs Delayed Capture

Immediate capture (auth and capture)

The most common approach for straightforward transactions. The merchant authorises the payment and captures it in one step. The transaction is submitted for clearing and settlement right away. This is typical for:

• Retail point-of-sale transactions
• Online purchases where goods are in stock and ship immediately
• Telephone payments for services rendered or immediate deliveries
• Subscription and recurring billing

Delayed capture (auth only, capture later)

In some cases, merchants authorise the payment first and capture it later -- sometimes days later. This is used when:

• Goods need to be shipped -- Many e-commerce merchants authorise at checkout but only capture when the order ships, so the customer is not charged for items that may be out of stock
• Final amount is unknown -- Hotels and car hire companies authorise an estimated amount and capture the final amount at checkout
• Pre-orders -- The merchant authorises to confirm the card is valid but does not capture until the product is ready
• Fraud review -- Some merchants hold transactions for manual review before capturing

Partial Capture and Multiple Captures

Some payment gateways support partial capture, where the merchant captures less than the originally authorised amount. For example, if a customer orders three items but one is out of stock, the merchant might capture only the amount for the two items that shipped.

The unused portion of the authorisation is released back to the cardholder. Note that you generally cannot capture more than the authorised amount -- doing so would require a new authorisation for the difference.

Capture in Telephone Payments

For telephone payments, capture behaviour depends on the nature of the transaction and how the merchant's payment system is configured:

• Service businesses -- A consultancy taking payment over the phone for completed work will typically use immediate capture
• Mail order businesses -- A company taking an order over the phone might use delayed capture, authorising during the call and capturing when the goods ship
• Hotels and bookings -- A hotel taking a reservation over the phone might pre-authorise an amount and capture after the guest checks out

In all cases, the card details are needed only at the authorisation stage. By the time capture occurs, the merchant's payment system already has a reference to the original authorisation -- no card data needs to be re-entered.

Void vs Capture

If a merchant decides not to proceed with a transaction after authorisation, they can void it instead of capturing. A void cancels the authorisation hold and releases the funds back to the cardholder immediately (or as quickly as the issuing bank processes it). This is preferable to letting the authorisation expire naturally, as it gives the cardholder faster access to their funds.

Managing Capture Effectively

Good capture management matters for both cash flow and customer experience:

• Capture promptly when goods or services have been delivered to maintain healthy cash flow
• Use delayed capture when appropriate to avoid charging customers for items you cannot deliver
• Monitor for expired authorisations -- if you wait too long to capture, the auth will expire and you will need to request a new one (which may be declined)
• Ensure your payment gateway is configured correctly for your business model