The short answer
Every card transaction is actually two messages: an authorization (issuer confirms funds, reserves them) and a capture (merchant tells the acquirer to actually move the funds into the settlement batch). Capture delay is the elapsed time between the two. For e-commerce with physical shipping, best practice is to auth at order, capture at ship — a 1-3 day delay. For SaaS and digital goods, auth-and-capture typically happen in the same request — near-zero delay.
Auth expiration windows by card brand
- Visa: 7 days (retail), 30 days (travel/lodging/rental).
- Mastercard: 7 days (retail), 30 days (travel/lodging).
- Amex: 30 days across most MCCs.
- Discover: 10 days (retail).
If you don't capture within the auth window, the auth expires: the hold drops off the cardholder's account, but you can still submit a capture. The issuer will usually honor it — but approval isn't guaranteed. Expired auth captures have materially higher decline rates and chargeback risk.
When to use delayed capture
- Physical goods (e-commerce). Auth at order placement; capture at shipment. This is Visa/MC's documented guidance. It prevents charging for items that end up out of stock.
- Services delivered over time. Capture at completion or at defined milestones.
- Travel and hospitality. Auth at booking; capture at check-out or service completion. Use the extended auth window MCCs.
- Custom / made-to-order. Auth at order; capture when production begins (not at ship — capture timing should reflect when revenue is earned).
When to use immediate capture
- Digital goods (instant delivery). Subscription signup, SaaS, digital download.
- In-person retail. Customer takes the product and leaves — no reason to delay capture.
- Pure-service SaaS. Value delivered at charge.
What operators need to know
- Auth holds hit customer psychology. An uncaptured $200 auth on the customer's statement looks like a charge. Delayed captures are fine for 1-3 days; 7+ day delays generate "why are you holding my money" support tickets.
- Release auths if you're not capturing. When an order is canceled or the item is out of stock, run an auth reversal immediately. Letting it expire naturally on day 7 is worse UX.
- Incremental auths for dynamic pricing. Rideshare, hotels, tabs — see incremental auth for how to grow the auth without re-running the full flow.
- Partial captures are allowed. Authed $100, only shipping $80 worth of items, capture $80 and leave $20 on the auth. The $20 hold naturally expires at the auth window.
- Captures after expiry = higher decline. If you're at day 10 on a 7-day Visa auth and haven't captured, expect 5-15% of captures to decline. Plan to re-auth, not just blindly capture.
- Auth fee on every capture attempt. Some processors charge a per-auth and a per-capture fee separately. Check your statement — auth+capture as a combined flow is usually cheaper than auth-then-delayed-capture.