Payment Capture

Billing Payments

5 min read

Also known as: Charge Capture, Settlement Capture, Funds Capture

Payment capture is the step where an authorized card charge is finalized and funds move from the customer's account into your merchant balance.

Definition

Payment capture is the second half of a two-step card transaction. The first step, authorization, reserves funds on the customer's card and confirms the account is valid; capture is the action that actually pulls those reserved funds into your merchant account for settlement.

In practice, you'll see capture happen automatically at checkout for most one-click purchases, or get deferred for hours, days, or weeks when you need to confirm inventory, fulfillment, or contract terms before charging. Your billing system fires the capture call to the payment processor, which then queues the transaction for the next settlement batch.

Capture is distinct from authorization (reserves funds), settlement (moves money between banks), and refund (reverses a captured charge). Operators who blur these together usually end up with reconciliation problems or unexpected authorization expirations.

Why It Matters

Capture timing directly affects cash flow, chargeback exposure, and customer trust. Capturing too early on a delayed-fulfillment order can trigger disputes when the customer sees the charge before they receive goods; capturing too late risks the authorization expiring (typically 7-30 days) and forcing you to re-collect payment from a customer who may have already mentally moved on.

When teams ignore capture mechanics, you end up with stranded authorizations sitting on customer cards, declined captures because the hold expired, and reconciliation headaches between your billing ledger and your processor statements. For subscription businesses, mis-timed captures also create dunning loops where retries fire against expired auths instead of fresh charges.

Examples in Practice

A 30-person ecommerce brand selling custom furniture authorizes the full order amount at checkout but only captures when the piece ships 4-6 weeks later. This protects the customer from a premature charge and gives the brand a confirmed payment commitment before manufacturing begins.

A B2B SaaS company running annual contracts authorizes the renewal charge 5 days before the anniversary date, then captures on the renewal day itself. The early authorization surfaces card failures in time for the success team to reach out before service interruption.

A marketplace platform handling event ticket sales captures immediately at purchase because tickets are digital and instantly delivered. The same platform uses deferred capture for merchandise orders, separating the two flows in its billing logic to match fulfillment reality.

Frequently Asked Questions

What is payment capture and why does it matter?

Payment capture is the action that finalizes a previously authorized card charge and moves the funds toward settlement in your merchant account. It matters because the timing of capture controls when revenue is recognized, when the customer sees the charge on their statement, and whether the original authorization is still valid when you try to collect.

How is payment capture different from authorization?

Authorization is a hold that confirms the card is valid and reserves the funds; no money has actually moved. Capture is the follow-up call that tells the processor to convert that hold into a real charge. You can authorize without capturing (and let the hold drop off), but you cannot capture without first authorizing.

When should I use deferred capture instead of immediate capture?

Use deferred capture when there's a meaningful gap between order and fulfillment, such as physical goods that ship later, services that need to be scheduled, or contracts that require countersignature. Use immediate capture for digital goods, instant-delivery services, and recurring subscription renewals where the customer expectation is that the charge happens right away.

What metrics measure payment capture performance?

Track capture success rate (captures completed vs attempted), authorization-to-capture conversion rate, average time between auth and capture, and expired-authorization rate. For subscription businesses, also watch involuntary churn caused by capture failures and the percentage of captures that require a retry or fallback payment method.

What's the typical cost of payment capture?

Capture itself usually doesn't carry a separate fee beyond your standard processing rate, which is typically 2.5%-3.5% plus a small per-transaction fee for card-not-present transactions. Some processors charge for failed authorizations or for authorizations that are never captured, so check your processor agreement for unused-auth or misuse fees.

What tools handle payment capture?

Capture is handled by your payment processor and exposed through whatever billing or commerce platform sits on top of it. Modern subscription billing engines, ecommerce checkout platforms, and order management systems all expose capture controls, with the better ones letting your ops team set per-product or per-order capture rules instead of hardcoding one global behavior.

How do I implement payment capture for a small team?

Start by mapping which products need immediate capture versus deferred capture based on fulfillment timing. Configure your billing system to match, set authorization expiration alerts at the 5-day mark, and build a simple weekly reconciliation between captured transactions and processor settlement reports. For most small teams, the partner that runs your billing stack should handle the technical configuration.

What's the biggest mistake teams make with payment capture?

The most common mistake is capturing too early on orders that won't fulfill for weeks, then dealing with chargebacks when customers dispute charges for goods they haven't received yet. The second most common mistake is the opposite, letting authorizations expire on delayed-fulfillment orders and having to re-collect payment from customers who've cooled on the purchase.

Can a payment capture fail even if the authorization succeeded?

Yes. The authorization can expire before you capture, the customer's bank can revoke the hold, the card can be reported lost or stolen between auth and capture, or the account can be closed. This is why deferred-capture workflows need monitoring and a fallback path to re-authorize or reach out to the customer for an updated payment method.

Does payment capture apply to ACH and bank transfers?

The term is most accurate for card payments, where auth and capture are explicit separate steps. ACH and bank transfers work differently, with a single debit instruction that moves through the banking network over several days. Some platforms borrow the language of capture for ACH flows, but the underlying mechanics are a one-step debit rather than a two-step authorize-then-capture pattern.

The AMW Suite