Payment Capture

What Is Payment Capture?

Payment capture is the process by which a merchant confirms a previously authorized card transaction and initiates the transfer of funds from the cardholder's issuing bank to the merchant's acquiring bank. When a customer swipes, taps, or enters their card details, the card network first obtains an authorization: a confirmation that the cardholder's account exists, has sufficient funds or credit, and is not restricted. Authorization places a hold on the transaction amount but does not move money. Capture is the merchant's signal that they are ready to collect.

The separation between authorization and capture exists because many transactions involve a gap between the moment a customer commits to pay and the moment the merchant fulfills the order. Hotels authorize at check-in but capture at checkout. E-commerce merchants authorize at purchase but capture at shipment. This two-phase design gives merchants flexibility while protecting cardholders from being charged for goods or services not yet delivered.

How It Works

Card payments follow a three-stage lifecycle: authorization, capture, and settlement. Each stage involves different parties and serves a distinct purpose.

1. The cardholder initiates a purchase. The merchant sends an authorization request through their acquirer to the card network, which routes it to the issuing bank.
2. The issuer verifies the account, checks for sufficient funds, applies fraud rules, and returns an approval or decline. If approved, the issuer places a hold on the authorized amount, reserving it so the cardholder cannot spend it elsewhere.
3. The merchant fulfills the order (ships the product, completes the stay, delivers the service). When ready, the merchant submits a capture request for the authorized amount or a lesser amount.
4. The acquirer batches captured transactions and submits them through the card network for batch settlement. The issuer debits the cardholder's account and transfers funds to the acquirer, who deposits them into the merchant's account.

Settlement typically completes one to three business days after capture, depending on the processor, card network, and merchant agreement.

Auto-Capture vs. Manual Capture

Most payment processors offer two capture modes:

• Auto-capture: the processor captures the transaction immediately after authorization, with no delay. This is the default for most retail and digital-goods merchants. It suits scenarios where fulfillment is instant or near-instant: downloading software, ordering food for immediate preparation, or purchasing digital subscriptions.
• Manual capture: the merchant explicitly triggers capture at a later time. This is standard for e-commerce merchants who ship physical goods, hotels that finalize charges at checkout, and any business where the final amount may differ from the initial authorization.

Consumer protection regulations in several jurisdictions prohibit capturing payment before goods are dispatched to the customer, making manual capture a legal requirement for physical goods in those markets.

Partial Capture

Partial capture allows a merchant to collect less than the originally authorized amount. If a customer orders three items but one is out of stock, the merchant can capture only the amount for the two items that shipped. The remaining hold on the uncaptured portion is released back to the cardholder.

Not all processors handle partial capture the same way. Some automatically void the uncaptured remainder after a single partial capture. Others support multiple partial captures against the same authorization, useful for merchants who ship orders in multiple packages. This feature typically requires explicit activation with the processor.

Capture Windows

Authorizations do not last indefinitely. Each card network defines how long a merchant has to capture after authorization:

If a merchant captures after the authorization window expires, the transaction may be declined, or the network may impose compliance fees. Visa's Processing Integrity Program Fee, for example, penalizes merchants who fail to capture or cancel authorizations within the defined window.

For industries that need longer hold periods, pre-authorizations with extended windows are available. These allow hotels, cruise lines, and vehicle rental companies to hold funds for up to 30 days while the final charge amount is determined.

Use Cases

E-Commerce with Shipping Delays

Online retailers authorize at checkout but delay capture until the order ships. This protects the customer from paying for items that may be backordered, cancelled, or split across multiple shipments. Each shipment can trigger a separate partial capture against the original authorization.

Hotels and Lodging

Hotels authorize an estimated total at check-in (room rate plus incidentals), then capture the actual amount at checkout. The final charge may include minibar purchases, room service, or damage fees that were unknown at authorization time. Extended authorization windows of up to 30 days accommodate long stays.

Vehicle Rentals

Rental companies authorize a hold that covers the estimated rental period plus a deposit for fuel and potential damage. The capture amount depends on actual usage: return date, fuel level, and any damage assessed. Like hotels, these merchants use extended authorization windows.

Subscription Trials

Some subscription services authorize a small amount (often $0 or $1) to verify the card is valid, then capture the full subscription price only after the trial period ends. The initial authorization may be voided if the customer cancels before the trial expires.

Authorization and Capture vs. Push Payments

The authorization-capture model is a product of pull-payment infrastructure. The merchant (payee) initiates collection by pulling funds from the cardholder's account through a chain of intermediaries: acquirer, card network, and issuer. Because the payee controls timing, the system needs authorization holds, capture windows, and chargeback mechanisms to protect the payer.

Push-payment systems work differently. The payer initiates the transfer directly, and funds move in a single step. There is no separate authorization phase because the act of sending is itself the authorization. Real-time payment networks like FedNow and UPI settle individual transactions within seconds. Cryptocurrency transactions on networks like Bitcoin go further: the transfer is cryptographically signed by the sender, broadcast to the network, and settled with finality once confirmed, all without intermediaries.

This atomic model, where authorization and settlement happen as a single indivisible operation, eliminates several pain points of the capture flow: no authorization holds that confuse cardholders, no capture windows that merchants must track, no compliance fees for late captures, and no void transactions to clean up uncaptured authorizations. For a deeper comparison of how different payment rails handle finality, see the research article on payment finality across blockchains.

The tradeoff is flexibility. Push payments are final: there is no built-in mechanism to reverse a completed transfer. The authorization-capture model's two-phase design gives merchants a window to adjust the amount, and it gives cardholders dispute rights through the chargeback process. Industries that need variable final amounts (hotels, rentals) or buyer protection (e-commerce) rely on this flexibility. Push-payment systems that need similar functionality must build it at the application layer, through smart contracts, escrow services, or platform-level dispute resolution.

Why It Matters

Understanding payment capture is essential for any business that processes card payments. Misconfigured capture settings can lead to lost revenue (expired authorizations that fail at capture), customer complaints (premature charges before fulfillment), or network penalties (late captures triggering compliance fees). For merchants evaluating alternative payment rails, the capture model highlights a fundamental architectural difference: traditional card payments separate intent from settlement across multiple parties and days, while instant settlement systems compress this into a single step.

Platforms like Spark that operate on push-payment infrastructure bypass the capture flow entirely. When a user sends a stablecoin or Bitcoin payment, the transaction authorizes and settles atomically. There is no hold, no capture window, and no batch settlement delay. For businesses exploring how instant settlement impacts operations, the elimination of the capture phase is one of the most tangible differences from traditional card processing.

Risks and Considerations

Authorization Expiry

If a merchant waits too long to capture, the authorization expires and the hold on the cardholder's funds is released. Attempting to capture against an expired authorization typically results in a decline. The merchant must then request a new authorization, but the cardholder's available balance may have changed. For high-value transactions, this can mean lost sales.

Compliance Fees

Card networks increasingly penalize merchants who leave authorizations uncaptured. These "stale authorization" fees incentivize merchants to either capture promptly or void authorizations they do not intend to collect. Merchants with high volumes of abandoned carts or cancelled orders need systems to automatically void unused authorizations.

Cardholder Confusion

Authorization holds appear as "pending" charges on cardholder statements. When capture is delayed or the captured amount differs from the authorization, cardholders may see both the hold and the final charge temporarily, leading to confusion and support inquiries. Clear communication about hold timing reduces disputes and chargebacks.

Partial Capture Complexity

Merchants who ship in multiple packages or adjust order totals must coordinate partial captures carefully. Each partial capture must reference the original authorization, and the sum of all captures must not exceed the authorized amount. Some processors require explicit configuration for multiple partial captures, and fee structures may differ from standard captures.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.