How Capture Rate Works
Capture rate tracks the final step of the payment lifecycle — the moment an authorized hold is converted into an actual transfer of funds. Understanding it requires separating two distinct events: authorization reserves the cardholder's funds, while capture actually moves them to the merchant's account.
When a customer completes checkout, the issuing bank places a hold on the cardholder's funds through an authorization. The merchant then sends a separate capture request — automatically or manually — to instruct the acquirer to collect those funds and route them through settlement. Capture rate measures how consistently that second step succeeds across all authorized transactions.
Customer completes checkout
The cardholder submits payment details. The issuing bank evaluates the request and returns an authorization code, placing a temporary hold on the approved amount. The transaction is authorized but no money has moved yet.
Merchant sends a capture request
The merchant's platform — automatically at checkout or later upon fulfillment — sends a capture instruction to the payment processor. This may happen within seconds of authorization or several days later depending on the business model.
Processor submits to the card network
The acquirer batches capture requests and submits them to the card network (Visa, Mastercard, Amex, etc.), which forwards the instruction to the issuing bank for settlement processing.
Funds are settled to the merchant
The issuer releases the held funds. They flow through the card network and acquirer to the merchant's account, typically within 1–3 business days. This transaction is now counted in your capture rate numerator.
Uncaptured authorizations expire
If a capture request is never sent — due to cancellation, a technical error, or a fulfillment delay — the authorization expires (typically within 5–30 days depending on card network rules). These transactions count in the denominator but not the numerator, reducing your capture rate directly.
Why Capture Rate Matters
Capture rate is a direct measure of revenue collection efficiency. Every authorized transaction that goes uncaptured is approved revenue that never reaches your bank account — a loss that rarely surfaces in authorization dashboards and is easy to overlook until reconciliation reveals the gap.
Industry payment operations data shows that uncaptured authorizations account for 0.5–2% of gross authorized volume for merchants running delayed-capture models. At significant transaction volumes, even a 1% capture rate gap represents hundreds of thousands of dollars in annual leakage. Research from payment analytics providers tracking merchant cohorts found that teams who actively monitor and alert on capture rate outperform passive peers by an average of 0.8 percentage points — a meaningful gain at scale that compounds month over month.
Revenue impact benchmark
A merchant processing $10 million per month with a 97% capture rate versus a 99% capture rate leaves $200,000 per month on the table. At a 40% gross margin, that is equivalent to $80,000 in lost profit each month — from transactions the issuer already approved and the customer intended to complete.
A declining authorization rate affects revenue by blocking transactions before they start. A declining capture rate affects revenue after the issuer has already said yes — making it arguably more damaging, since both customer intent and bank approval were already secured. Ignoring capture rate while optimizing authorization rate is like fixing a leaking pipe by increasing water pressure.
Capture Rate vs. Authorization Rate
These two metrics are frequently conflated, but they measure entirely different stages of the payment funnel and have different root causes, owners, and remediation paths. Confusing them leads to misdiagnosed revenue problems and misallocated engineering effort.
Payment conversion rate adds a third dimension — measuring how many checkout sessions result in any payment attempt at all. All three metrics together provide a complete view of funnel health; any single metric in isolation is insufficient.
| Metric | Funnel Stage | What It Measures | Typical Benchmark | Primary Owner |
|---|---|---|---|---|
| Payment Conversion Rate | Intent → Attempt | % of checkouts with a payment attempt | 60–85% | Product / UX |
| Authorization Rate | Attempt → Approval | % of attempts approved by issuer | 85–97% | PSP / acquirer |
| Capture Rate | Approval → Collection | % of approvals actually captured | 97–99%+ | Merchant ops / dev |
These metrics compound directly. A merchant with 80% conversion, 90% authorization, and 97% capture collects revenue from just 70% of checkout sessions — meaning nearly one in three customers who intended to pay does not result in collected revenue.
Types of Capture Rate
Capture rate is not uniform across business models. Different fulfillment patterns create distinct risk profiles, and merchants running multiple models will see materially different capture rates by channel if they look closely enough.
Immediate capture (auto-capture): The capture request fires at the same time as the authorization, typically within seconds of checkout. Standard for digital goods, SaaS subscriptions, and direct-to-consumer ecommerce. Capture rates are highest here — usually 99%+ — because authorization expiry is irrelevant and the only failure modes are technical.
Delayed capture: The merchant authorizes at checkout but captures later, upon shipment or fulfillment confirmation. Common in physical goods ecommerce, travel (hotels, car rentals), and B2B orders. This model carries the highest capture rate risk, as fulfillment delays — whether from inventory issues, logistics backlogs, or manual review — can push capture attempts past card network authorization expiry windows.
Marketplace and platform capture: In marketplace models, the platform authorizes on behalf of sub-merchants and captures after seller fulfillment is confirmed. Authorization-to-capture gaps can range from hours to weeks, requiring robust expiry tracking and proactive re-authorization logic.
Pre-authorization and card-on-file capture: Common in hospitality, car-sharing, and consumption-based billing. An initial authorization validates the card; the actual capture occurs later based on real usage. Capture rate here depends on the health of the stored card token — expired or replaced cards increase failure rates at capture time.
Best Practices
Improving capture rate requires coordination between operations, engineering, and the payment stack. The levers available differ meaningfully by role, and the most resilient programs address both sides simultaneously.
For Merchants
Configure automatic capture wherever your fulfillment model permits — eliminating the manual step eliminates its failure modes. For delayed-capture models, set internal SLA alerts well before card network expiry deadlines, typically targeting capture at the 3-day mark for a 7-day authorization window. Build a daily reconciliation process that flags any authorized transaction without a corresponding capture or void within your SLA. Work with your PSP to understand per-network expiry rules, since Visa (7 days), Mastercard (30 days), and Amex (7 days for most transactions) differ significantly. Train customer support and operations teams to void authorizations immediately upon order cancellation rather than letting them expire naturally — expired-but-uncancelled holds drive cardholder confusion and chargeback risk.
For Developers
Implement capture retry logic with exponential backoff for transient API errors — a single failed attempt due to a network timeout should never result in a permanently uncaptured authorization. Log every capture attempt and its outcome code at the application layer, not just at the PSP dashboard level, so you can detect silent failures. Set alerting on capture failure rates segmented by error code to distinguish transient network issues from hard declines or configuration problems. For async fulfillment systems, use a durable job queue rather than a cron job to ensure capture calls survive application restarts and deployment cycles. Regularly audit authorization-to-capture latency distributions in your data warehouse to detect drift — an increasing p95 latency is an early warning sign before aggregate capture rate drops.
Common Mistakes
1. Treating authorization rate as a proxy for capture rate. Authorization and capture are separate API calls with separate failure modes and separate dashboards. A strong authorization rate provides no signal about capture health. Both metrics must be tracked independently with distinct alerting thresholds.
2. No expiry monitoring for delayed-capture models. Merchants frequently implement capture as a downstream fulfillment step without tracking how close each in-flight authorization is to its expiry date. A single fulfillment delay — a warehouse backlog, a manual review queue — can push thousands of authorizations past their window simultaneously.
3. Silent capture failures in PSP integrations. Many PSP integrations return an HTTP 200 on the capture endpoint even when the downstream capture fails. Developers who check only for non-error HTTP status codes miss these failures entirely. Always parse the full response body and validate explicit success codes before marking a transaction as captured in your system of record.
4. Not voiding uncaptured authorizations. Leaving expired or unnecessary authorizations without an explicit void creates pending balance holds that confuse cardholders, increases friendly fraud disputes, and adds refund and dispute-management overhead on top of the original revenue loss. Every authorization should end in either a capture or a void — never in silent expiry.
5. Aggregating capture rate across all channels without segmentation. A blended 98.5% capture rate can mask a 93% rate on marketplace orders or delayed-ship SKUs alongside a 99.8% rate on auto-captured digital goods. Always segment by capture model, sales channel, product category, and PSP before drawing conclusions or setting remediation priorities.
Capture Rate and Tagada
Tagada's payment orchestration layer monitors capture rate in real time across all connected processors and payment methods. Because Tagada sits between the merchant's platform and multiple PSPs, it can detect capture failures independently of any single processor's reporting — catching silent failures that individual PSP dashboards miss entirely.
Use Tagada's capture rate alerting to set per-processor and per-channel thresholds. When a PSP's capture rate drops below your defined floor, Tagada can automatically shift new authorization attempts to a backup processor — protecting revenue without requiring manual intervention or an on-call incident.
For merchants running delayed-capture models, Tagada tracks authorization age across all connected processors and surfaces authorizations approaching network expiry limits, giving operations teams a prioritized action queue before revenue is lost. This is particularly high-value for travel, marketplace, and B2B merchants where fulfillment timelines are variable and authorization windows are the most constrained.