Your auth capture strategy is the rule set that decides when you authorize a card, when you capture the funds, and what happens when something changes in between. Capture at checkout when you ship or deliver right away. Authorize first and capture later when the final amount, stock, a clinical review or a compliance check is still pending. The right choice cuts voids, declines, disputes and processor scrutiny. The wrong one creates all four.

This guide is for established merchants, including telehealth providers, med spas, supplement brands, subscription businesses and other regulated ecommerce operators. You will see how the two steps work, how to pick a timing model for your business, what breaks when captures fail, and how to set it up so a single processor problem does not stop your revenue.

DavinciPay
Build More Resilient Payment Processing
DavinciPay helps established and regulated businesses navigate underwriting, payment gateway integration, and multiple processing relationships.
Explore payment solutions

TL;DR

  • Authorization checks the card and holds funds. Capture moves the money. Your strategy is the timing and rules between those two steps.
  • Capture immediately when you fulfill immediately. Delay capture when the final amount or the decision to fulfill is not settled at checkout.
  • Every unmatched, expired or partial authorization is a risk: declines, customer confusion, disputes and fees. Reverse what you will not capture, and send clean linking data.
  • Document the strategy per product line. A telehealth visit, a supplement subscription and a custom order should not share one rule.
  • Spreading volume across more than one merchant account gives you options when a processor changes its terms.

Table of Contents

What auth capture means

A card payment has two distinct moments. First comes authorization: your gateway asks the issuing bank whether the card is valid and whether the purchase can be approved. The Office of the Comptroller of the Currency describes authorization as designed to stop approvals for cardholders who are over their limits or have not maintained their accounts, and to protect against stolen or fraudulent cards. The approval does not move money. It reserves it.

Second comes capture: you tell the processor to collect the authorized amount. Captured transactions are batched, settled and funded to your account according to your processor’s schedule.

Gateways expose this in two ways:

  • Auth only, then capture: two separate API calls or dashboard actions, with time between them.
  • Auth capture (sale): one request that authorizes and queues the capture together.

So when someone searches for “auth capture,” they usually mean the single-request sale. When they search for a strategy, they mean the policy that decides which of the two modes each of your transactions uses.

What a capture strategy actually decides

A workable capture strategy answers five questions in writing:

  1. Trigger: What event causes capture? Checkout, shipment, provider approval, service completion, or a billing date?
  2. Delay: How long can you be between authorization and capture for each product?
  3. Amount: Can the captured amount differ from the authorized one, and by how much?
  4. Failure handling: What happens if capture is declined, times out, or the authorization has expired?
  5. Cleanup: Who reverses authorizations you will never capture, and how fast?

If your team cannot answer these in a sentence each, you do not have a strategy yet. You have defaults from your gateway.

Immediate capture vs. delayed capture

Factor Immediate capture (auth + capture together) Delayed capture (auth first, capture later)
Best for Digital goods, instant access, in-stock items shipped same day Made-to-order items, backorders, clinical or compliance review before fulfillment
Cash flow Funds enter the settlement cycle sooner Settlement starts only after you capture
Customer experience Charge appears right away A pending hold may show first, then the charge
Operational load Low. Refunds handle cancellations Higher. You must capture or reverse every authorization
Main risk Charging before you can deliver, then refunding Expired authorizations, mismatched amounts, forgotten holds
Refund cost Cancellations become refunds Cancellations can become reversals, which are cleaner

Neither mode is better in general. Delayed capture gives you control but demands discipline. Immediate capture is simple but pushes cancellations into refunds and, if handled badly, disputes.

How to choose by business model

Telehealth providers

Many telehealth flows have a natural gate: a clinician reviews the intake and decides whether to treat or prescribe. Authorizing at checkout and capturing after that decision keeps you from charging patients you cannot serve. If the provider declines, you reverse the authorization and the patient never sees a completed charge. The tradeoff is time. If review can run longer than your authorization window, you need a plan to re-authorize or collect again before service. Telehealth teams already juggle billing rules; the same attention you give to new RTM CPT codes belongs on the transaction records that tie each charge to a visit.

Supplement and nutraceutical brands

For in-stock products that ship within a day or two, immediate capture is usually the cleaner model. If you carry backorders or ship from several warehouses, authorize at checkout and capture when each shipment is confirmed. Capturing per shipment also matches the amount charged to the goods that left the building, which reduces “I was charged for something I have not received” disputes.

Subscription merchants

Trial offers, first renewals and card-on-file billing each call for a different rule. A trial start can use a low-value authorization to verify the card. Recurring cycles are normally captured on the billing date. Whatever you choose, make the billing terms obvious at checkout and in the receipt. Unclear recurring terms are a common reason customers dispute a charge they actually agreed to.

Med spas

Deposits, packages and services delivered later pair well with a split approach: capture a deposit at booking, and authorize or capture the balance when the treatment is completed. If the final price depends on what the provider performs, authorize with a clear estimate and capture the actual amount.

Research-use-only peptide businesses

These merchants usually face tight underwriting and close attention to what is sold and how. Capture timing should be conservative: capture when you ship, keep your order records consistent with your approved business description, and keep documentation of each order ready. Your processor’s underwriting terms control what you can process, so work from your approval, not from assumptions.

Timing: how long can you wait between auth and capture?

There is no single universal answer. The window depends on the card network, the transaction type (card-present or card-not-present, customer-initiated or merchant-initiated), the industry, and your processor’s own limits. Gateways often set their own shorter cutoffs than the networks do. Treat the number in your gateway documentation as your operating limit, and confirm it with your processor when you set up each merchant account.

What the networks do publish is how they expect you to behave with authorizations you will not use. Visa’s guidance for lodging, car rental and cruise merchants says approved authorizations should be matched to settled transactions within 20 days, or the merchant risks a misuse fee. The same document says unsettled authorizations should be reversed electronically within 24 hours for card-present and 72 hours for card-not-present transactions. That guidance is written for those three industries, but it shows the standard the networks apply to unused holds. Use it as a benchmark and ask your processor which rules apply to your merchant category.

When an authorization expires before you capture, the hold falls off the cardholder’s available credit and the approval is no longer reliable. Capturing against it may fail or be treated as an unauthorized transaction. Your safe options are to re-authorize the card (if the customer has agreed to be charged), or to contact the customer for a new payment method.

Timing: how long can you wait between auth and capture? — overview diagram

What the customer sees: holds are not charges

Customers call support when a pending hold appears. Your team should know the answer. An authorization hold generally does not take money from the cardholder’s account. It reserves part of the available credit without charging the card or changing the balance, though it can lower available credit until it drops off or is captured. On debit cards the effect on the available balance can feel more direct, so give customers a plain explanation at checkout.

A short line on the confirmation page helps: “Your card is authorized now and charged when your order ships.” Pair it with a descriptor customers recognize on their statement.

What goes wrong with failed, partial and reversed captures

Most capture problems come from a few repeatable causes.

  • Expired authorization. The capture arrives after the window closes and is declined or at risk.
  • Amount mismatch. You capture more than you authorized. Small differences can be allowed in some industries, but as a rule, capture no more than what was approved unless your processor confirms the tolerance.
  • Partial shipments. You capture the full order but ship half. Customers see a charge for goods they do not have.
  • Orphaned authorizations. An order is canceled, nobody reverses the hold, and the customer’s credit stays tied up.
  • Duplicate captures. Retries without idempotency controls charge the same order twice.
  • Weak linking data. Reversals cannot be tied to the original approval.

On that last point, Visa’s best-practice document tells U.S. merchants to populate fields such as the Transaction Identifier, System Trace Audit Number and Retrieval Reference Number correctly so authorization messages and reversals can be linked. Your gateway normally handles this, but you should verify that your integration passes the original transaction reference whenever you capture, void or reverse.

Disputes can turn on authorization details

Authorization problems are not only an operations issue. Visa’s merchant dispute guidance says authorization disputes look at whether required approval, indicators and timing were met, and proof that the cardholder received the goods does not override failed authorization requirements. In other words, delivering the product does not rescue a transaction that was captured improperly. Clean authorization records are part of your chargeback defense.

Build your strategy in six steps

  1. Map every sale type. List each product, service, deposit, renewal and add-on, and note when you actually fulfill it.
  2. Assign a capture trigger. Immediate for instant fulfillment. Event-based (shipment, approval, service completed) for everything else.
  3. Set a maximum delay. Use the shortest window among your gateway, processor and card-network limits, and set an internal alert earlier than that.
  4. Automate reversals. Any authorization you will not capture should be reversed by a scheduled job, not by memory.
  5. Pass linking data. Store the transaction ID, and send it with every capture, void and refund call.
  6. Review monthly. Track the share of authorizations that end in capture, reversal or expiry. A rising expiry rate means your trigger is too slow.

Perspective: why capture strategy is a continuity issue

We see capture strategy treated as a developer setting, and that is a mistake. For merchants processing between $100K and $5M a month, capture behavior shows up in underwriting reviews, in dispute ratios, and in how a processor views the account. A merchant who authorizes and never captures, or who captures in odd patterns, gives a risk team questions to ask.

Our advice is practical. Write down your timing rules by product line. Match them to how you really fulfill orders. Make sure your gateway and your processor agree on the limits. And do not run all of it through one merchant account. When a processor changes terms, adds a reserve or pauses an account, a second account with a different acquiring relationship lets you keep taking orders while you sort it out. Capture rules can then be tuned per MID, with delayed capture where review is required and immediate capture where it is not.

We work with high-risk and regulated merchants every day, and the ones who last are the ones whose payment flow is documented, consistent and redundant. All approvals, pricing, reserves and settlement terms still depend on underwriting and processor requirements, so we always start from what your processor will actually approve.

— Peter

Get a capture setup that fits your underwriting

If you run a high-risk payment processing account today, or you are moving off a processor that closed or restricted you, your capture rules should be part of the application conversation. We place established merchants with acquiring banks, processors and gateways that suit their business model, and we help set up multiple MIDs so one provider is not a single point of failure. Telehealth teams can start with our telehealth payment processing page, and supplement brands with supplements payment processing.

DavinciPay

See how it works, then apply now to tell us your volume, your fulfillment model and your current processor situation.

Capture rules across multiple merchant accounts

Once you have more than one MID, strategy gets more interesting. You can route different products to different accounts, keep a backup account warm with a small share of volume, and set separate capture rules where processors differ. Two cautions apply. First, never capture on a different account than the one that authorized: the capture must go back through the original authorization path. Second, keep descriptors, refund policies and product descriptions consistent across accounts, so customers and processors see the same business everywhere.

Payment routing and capture rules across merchant accounts

A short internal runbook helps your team respond fast: which account handles which product, who can void or capture, what to do if a processor goes offline mid-day, and how pending authorizations are handled during a switch.

FAQ

What does “auth capture” mean?

It means authorizing a card and capturing the funds. In many gateways, an auth capture transaction does both in a single request, which is the standard sale. Auth-only transactions stop after authorization and wait for a separate capture.

What is a capture strategy?

It is your documented policy for when you capture funds relative to authorization, how long you may wait, and how you handle expired, partial or canceled transactions. It differs by business model, such as immediate capture for digital goods and delayed capture for reviewed or shipped orders.

Does an authorization hold take money out of your account?

Generally, no. A hold reserves part of the available credit or balance without completing the charge, but it can reduce what the cardholder can spend until it is captured or released. Holds on debit cards may feel more immediate to the customer, so explain them at checkout.

How long can I wait between authorization and capture?

It depends on the card network, the transaction type, your industry and your gateway or processor limits. Use the shortest limit that applies to you, confirm it with your processor, and reverse any authorization you will not capture. Visa’s guidance for lodging, car rental and cruise merchants sets 24 hours (card-present) and 72 hours (card-not-present) for reversing unsettled authorizations.

Is delayed capture better for high-risk merchants?

Not automatically. It helps when you need a review step or ship later, because you can reverse cleanly. It adds risk if your team lets authorizations expire or captures mismatched amounts. Choose it where it fits your fulfillment, and keep immediate capture where you deliver instantly.

Sources