← Back to Glossary

Definition

Capture

Capture can mean two different things in online business. In payments, capture is the step where an authorized transaction is collected and moved toward settlement. In marketing, capture can mean collecting a prospect's information. For checkout and revenue operations, payment capture is the more important meaning because it is the moment payment approval turns into collected revenue.

A buyer can enter a card, receive issuer approval, and still not be fully charged until the payment is captured. That distinction matters for digital products, subscriptions, payment plans, fraud review, shipping, refunds, reporting, and customer support.

What Payment Capture Means

Payment capture happens after authorize. Authorization asks whether the payment method can be approved. Capture tells the payment processor or payment gateway to collect the authorized amount.

Many checkouts authorize and capture in a single flow. The buyer pays, the transaction is approved, and capture happens immediately. Other businesses authorize first and capture later, usually because they need to confirm inventory, review risk, prepare fulfillment, or finalize the order amount.

Authorization vs Capture

Authorization is permission. Capture is collection.

An authorized payment is not the same as settled revenue. The issuer has approved a hold or approval for the transaction, but the merchant may still need to capture it. If the payment is authorized and never captured, the authorization can expire and the business may not receive the funds.

This is why payment reports should distinguish authorized, captured, voided, refunded, failed, and settled payments. Mixing these states can make revenue look healthier than cash reality.

Immediate Capture

Immediate capture works well when the business can deliver as soon as the order is approved. Digital downloads, course purchases, templates, paid communities, low-risk services, and many subscription starts usually fit this pattern.

Immediate capture keeps the buyer experience simple. The buyer pays, receives confirmation, and gets access or next steps right away. It also reduces operational risk because the business does not need to remember to capture the payment later.

Delayed Capture

Delayed capture separates approval from collection. A business may authorize a payment first, then capture after a manual review, inventory confirmation, shipment preparation, custom quote approval, or high-value order check.

Delayed capture can be useful, but it creates timing risk. Authorizations do not last forever. If the business waits too long, the authorization may expire and the customer may need to pay again.

The right delayed-capture workflow should define who reviews the order, when capture happens, what happens if authorization expires, and how the buyer is notified.

Manual Capture

Manual capture means a human or back-office workflow decides when to collect an authorized payment. This can be appropriate for custom services, pre-orders, high-ticket purchases, B2B approvals, or suspicious orders that need review before fulfillment.

Manual capture should not be casual. If staff are responsible for capturing orders, the business needs clear queues, permissions, reminders, and reporting. Otherwise, approved orders can sit unpaid while customers expect delivery.

Partial Capture

Some payment setups allow partial capture, where the business captures less than the authorized amount. This can be useful when an item is unavailable, shipping changes, a service scope is adjusted, or a manual review reduces the final charge.

Partial capture needs careful customer communication. The buyer should understand what was charged, what changed, and whether any remaining authorization will be released or adjusted by the issuer.

Capture And Card-Not-Present Payments

Most online capture happens in a card-not-present CNP environment. The card is not physically presented, so capture decisions depend on checkout configuration, issuer approval, fraud signals, payment tokens, and fulfillment rules.

For a standard digital checkout, immediate capture is usually expected. For a high-risk or high-ticket CNP order, delayed capture may reduce exposure while the business checks the order before delivering value.

Capture And Tokenization

Tokenization often supports capture and future billing. A token can represent the approved payment method while keeping raw card details away from the merchant's systems.

For an immediate purchase, the token may be used only to complete the first charge. For a subscription, payment plan, or saved-card workflow, the token may support future authorization and capture attempts.

Tokenization does not guarantee capture success. The issuer can still decline a tokenized transaction, the saved payment method can expire, and fraud controls can block the payment.

Capture And Subscriptions

Subscription billing usually captures the first payment at checkout and then attempts future renewals on the billing schedule. Each renewal may involve authorization and capture through the saved payment method.

The billing cycle should match what the buyer agreed to. If the first payment is captured today and future payments happen automatically, the checkout and receipt should say that plainly.

If a renewal fails, the business needs a failed-payment recovery flow rather than silently losing recurring revenue.

Capture And Payment Plans

Payment plan offers depend on clear capture timing. The buyer may pay an initial installment immediately, then future installments are captured on a schedule.

Payment-plan capture logic should match the displayed terms. A buyer should understand the number of payments, amount per payment, dates or cadence, total obligation, refund rules, and what happens if a future payment fails.

Confusing installment capture can create support tickets, refund requests, and disputes even when the payment system technically worked.

Capture And Digital Wallets

Digital wallets can also go through authorization and capture. The buyer may approve the wallet payment quickly, but the merchant still needs the gateway and processor to complete the payment flow.

For most wallet checkout, capture is immediate. If a business uses delayed capture, it should confirm that the wallet, gateway, and processor setup supports the intended timing.

Capture And Fraud Review

Delayed capture can support fraud prevention. A business may authorize a payment, review risk signals, and capture only if the order looks legitimate.

Useful review signals can include unusual order value, repeated failed attempts, mismatch patterns, risky geography, suspicious email behavior, or a product that is often targeted for abuse. The review process should be fast, because slow review can frustrate legitimate buyers and reduce trust.

Capture timing should also be aligned with fulfillment. If the business delivers instant access before review is complete, delayed capture may not reduce much risk.

Capture And Refunds

Capture affects refund handling. If a payment is authorized but not captured, the business may be able to void the authorization instead of issuing a refund. If the payment has already been captured and settled, refund handling usually returns funds through the original payment method.

Support teams should know the difference between void, capture, refund, and cancel. Clear internal rules reduce mistakes when a buyer changes their mind, an order cannot be fulfilled, or a suspicious order is declined after review.

Capture And Chargebacks

Once a payment is captured, it can become part of a later payment dispute or chargeback if the buyer challenges the transaction. Capture timing alone does not prevent disputes, but it can affect how prepared the business is.

For high-risk purchases, delayed capture can give the business time to confirm legitimacy before collecting funds. For standard digital purchases, the stronger prevention work is usually clear checkout terms, recognizable billing descriptor, receipts, product access records, refund clarity, and fast customer support.

Capture And Reporting

Payment reports should separate these states:

  • authorized
  • captured
  • partially captured
  • voided
  • failed
  • refunded
  • disputed
  • settled

If reporting treats authorization as revenue, teams may overstate performance. If reporting ignores failed captures, teams may miss leakage between checkout approval and collected payment.

Good reporting connects checkout, processor, accounting, subscription, payment-plan, and support systems so teams know which payments were actually collected.

Capture Metrics To Watch

Useful capture metrics include:

  • authorization rate
  • capture rate
  • failed capture count
  • authorization expiry count
  • void rate
  • refund rate
  • dispute rate
  • time from authorization to capture
  • manual review queue age
  • captured revenue vs authorized amount
  • payment-plan installment capture rate
  • subscription renewal capture rate

These metrics should be reviewed by offer, product type, payment method, gateway, traffic source, geography, and risk segment.

Lead Capture

In marketing, capture means collecting a visitor's information so the business can follow up. Email opt-ins, webinar registrations, quizzes, application forms, trial starts, and checkout starts are common lead-capture moments.

Lead capture is different from payment capture, but both are handoff points. Lead capture turns anonymous demand into a reachable contact. Payment capture turns approved payment intent into collected revenue.

For Spiffy-style checkout operations, payment capture deserves the tighter operational focus.

Common Capture Mistakes

The first mistake is treating authorization as collected revenue. If capture fails, expires, or is never submitted, the business may deliver without receiving payment.

The second mistake is capturing too early when the business cannot fulfill. That can create avoidable refunds, support tickets, and disputes.

The third mistake is delaying capture without a process. If no one owns the review queue, authorized payments can expire.

The fourth mistake is hiding capture timing from buyers. Subscriptions, payment plans, pre-orders, and delayed fulfillment need clear payment language before purchase.

Practical Example

A customer buys a $499 digital course. The checkout authorizes and captures immediately, then grants access. That immediate capture makes sense because the product can be delivered right away.

A different customer places a $4,000 custom services order. The business authorizes the card, reviews the order, confirms scope, and captures after approval. That delayed capture can make sense if the buyer understands the process and the business captures before the authorization expires.