Playbook · Shopify manual payment capture failing / authorization expired

Shopify manual payment capture failing / authorization expired — capture settings, auth window, Shopify Payments, Flow.

Written for a Shopify owner or ops lead whose Capture payment fails, stays Authorized past the window, or voids when staff try to capture — usually Payments is set to capture manually, the authorization expired, Shopify Payments / the gateway returned a capture error, or Flow / an app captured or voided on the wrong trigger. DIY-first: prove capture settings and auth window, prove gateway Timeline errors, prove Flow capture/void, then fix one order and watch the next. Distinct from Shopify Payments card declined, fulfillment hold stuck / cannot release, and draft order invoice not sending. Also distinct from payment-pending email not sending (customer notice silence while payment is still pending — not the capture failure itself). No earnings claims, no invented case studies.

Nico at Latch AI Ops · Sep 10, 2026 · ~11 minute read

Buy the 72-hour install — $997Card declinedFulfillment holdMerchant FAQ

01

Manual capture failing / auth expired — not card declined, fulfillment hold, draft invoice.

Several products can look like “we cannot take the money.” They do not share a settings panel. This page is only when an order is Authorized (or Authorization expired) and Capture payment fails, times out, or never becomes Paid — capture settings, auth window, Shopify Payments / gateway, Flow. Issuer declines at checkout with no paid / authorized order are card declined / AVS 3DS. Order stays On hold and Release / Fulfill will not complete (often after payment is already captured) is fulfillment hold stuck. Draft invoice email silence is draft order invoice not sending. Customer never got a pending-payment notice is payment-pending email. This page is only: Shopify manual payment capture failing / authorization expired.

Six ordinary reasons capture will not clear: Payments set to capture manually while ops never clicks Capture, authorization past the card network window (often ~7 days for many cards), Shopify Payments / gateway returns a capture decline or soft error, Flow or a fraud / OMS app voids or captures on the wrong trigger, staff without capture permission, or you are debugging card declined / fulfillment hold / draft invoice instead. Walk them in that order. You already pay for Shopify. You do not need another payments SaaS to read Settings → Payments and the order Timeline.

02

Prove capture settings and authorization window.

Open Settings → Payments → Capture payment. Note whether Shopify captures payments automatically or manually. Manual capture leaves every card order Authorized until someone clicks Capture payment (or Flow / an app does). Then open Orders → the stuck order → Payment. Note authorized at, capture attempts, and whether the status is Authorization expired, Voided, or still Authorized with a capture error.

Honest proof: screenshot Payments capture setting and the order’s Payment card with timestamps. If the auth is already expired, Capture will not revive it — re-authorize or send a new invoice / payment request. Issuer declines before any authorization lands are still card declined. Keep those separate from an order that authorized cleanly and then failed on capture.

03

Shopify Payments / gateway capture errors and Flow capture or void.

Open Timeline and Payment history on the order. Capture can fail with issuer soft declines, insufficient funds at capture time, 3DS / SCA issues on delayed capture, or gateway timeouts. Then open Flow / apps: workflows that run “Capture payment,” “Void payment,” or cancel on fraud tags can race staff clicks. Soften those to notify only, or require a cleared tag before void. Confirm the staff account can capture payments (not view-only collaborator).

Honest proof: try Capture once, refresh within a minute, and note the exact Timeline error line. If Flow voided or captured after you, edit that workflow before blaming Shopify Payments core. Misread high-risk cancels of good customers are covered on Fraud analysis false positives. Paid order that still will not leave fulfillment hold is fulfillment hold stuck — that playbook is the hold UI, not the capture failure.

04

Re-authorize, invoice again, or switch to automatic capture.

When the authorization is expired or voided, capture is done. Paths that usually work: send a new invoice / payment request for the balance, ask the customer to re-pay with Shop Pay / card, or create a draft order invoice if that is how you close B2B / high-ticket. For high volume, switch Settings → Payments to capture automatically at checkout so ops is not racing the auth window — keep manual capture only when you truly need pre-capture review.

Honest proof: after one successful capture or re-pay, confirm Payment shows Paid and the next order in the same path captures cleanly. Draft invoice email never arriving is draft order invoice not sending. Customer silence while payment is still pending is payment-pending email. Keep those separate from Capture payment failing on an already authorized order.

05

You tested card declined, fulfillment hold stuck, or draft invoice instead.

Checkout cards declining with no authorization are card declined / AVS 3DS. On hold / cannot Release after money is already captured is fulfillment hold stuck. Draft invoice email not arriving is draft order invoice not sending. Pending notice never emailed is payment-pending email. None of those fix manual capture settings, an expired auth window, or a Flow that voids on capture.

Finish the capture settings → gateway/Flow → re-auth proofs first. Only then open the related playbook that matches the remaining symptom.

06

When to stay DIY vs pay $997.

Stay DIY if you can spend one afternoon on the list above: prove capture settings and auth windows, clear gateway / Flow capture-or-void races, re-auth or switch to automatic capture, capture one order, and stop confusing card declined / fulfillment hold / draft invoice with Capture payment failing. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: card declined, fulfillment hold stuck, draft invoice, payment-pending email, Fraud analysis false positives.

Pay for help when the work is not the Payments panel — it is connecting the stack you already have so lead capture is not dying in DMs, capture failures and ops exceptions land in a channel you already check, and the live store is one workflow instead of a spreadsheet plus a Slack bot you forgot. That is the Latch AI Ops install.

What $997 USD one-time buys: lead capture on the live store, ops alerts in a channel you already check, and a checkout-ready workflow. 72 hours after collaborator access, not after payment. One live Shopify store. Access plus a delivery thread. Store URL collected at checkout. Not a SaaS seat, not a payments-app retainer, not a capture guarantee, not a brand or theme job.

Other shops’ public ranges, not testimonials: a checkout / ops install typically runs $500–$2,500. A full ops consulting block typically runs $2,000–$5,000. $997 is the cheap end of that work, sold as a 72-hour install of three systems — not as an earnings number or conversion-lift claim.

What it does not buy: more orders, recovered revenue, a forever capture guarantee, chargeback insurance, or a case study. Latch AI Ops has not published customer proof because there are no customers yet. You are buying the install.

Checkout is on Whop. Operator is Nico. United States offer. You can revoke collaborator access after handoff. We do not take owner passwords.