Shopify failed payment email not sending — after the card declined or dunning should have asked the customer to update payment and they never got the recovery mail.

A failed-payment or dunning recovery email is not an upcoming-charge reminder and not an open authorization. Subscription renewal / upcoming charge is subscription renewal email not sending. Payment pending / authorization still open is payment pending email not sending. Abandoned checkout is abandoned checkout email not sending. COD confirmation is COD confirmation email not sending. Order cancelled is order cancelled email not sending. Refund confirmation is refund email not sending. This page is the customer-facing path when a charge fails, a card declines, or dunning / “update your payment method” recovery should fire: native Shopify Payment failed (or related) notifications, Shopify Flow watching payment failed / order payment status, or Recharge / Skio / Appstle / Shopify Subscriptions payment-failed / card-update / dunning emails.

Six ordinary reasons failed-payment mail never lands: no decline / failed charge / dunning attempt, payment-failed or dunning template off or Flow / Klaviyo Draft, two owners fighting over the same event, sender/spam hid a send that did fire, you tested a different email product, or you never built a path for declines. Walk them in that order. You already pay for Shopify notifications and (often) a subscription app. You do not need a second SaaS to read their notification history.

Open the order Timeline and/or the subscription app (Recharge, Skio, Appstle, Shopify Subscriptions) → the customer’s subscription or payment attempts. You need a visible Payment failed, Declined, Soft decline, Hard decline, or Dunning / retry attempt — not Paid, not Payment pending still authorizing, not Cancelled, not Refunded, and not an upcoming-charge reminder with no charge attempt yet. A cart left unpaid is abandoned checkout. An open authorization is payment pending. An upcoming-billing reminder with no decline is subscription renewal mail.

Common traps: staff voiding or cancelling before dunning can email; testing on a Paid one-time order; conflating Shopify Payment pending with a hard decline; a subscription paused so retries never start; and expecting “update card” mail when the gateway never reported a failure. Wrong event, wrong silence.

Prove it on a test you own: force a declined test card (or the app’s test payment-failed / dunning email) to an inbox you control, then read the order Timeline, gateway log, and subscription-app notification history. No decline event means fix the payment attempt / dunning schedule first — not the template copy.

Open Shopify admin → Settings → Notifications. Confirm any Payment failed / related customer email you rely on is enabled — not disabled after a brand redesign. Open the subscription app’s Emails / Notifications settings. Confirm Payment failed, Card declined, Update payment method, Dunning / retry recovery, and related templates are enabled — not Draft. Open Shopify admin → Flow (and Klaviyo if that owns recovery mail). Find any “payment failed,” “card declined,” “dunning,” or “update card” workflow. Status must be Active / Live, not Draft. Conditions that only match first orders, exclude subscription tags, or require Paid status will silently skip every decline.

Marketing campaigns titled “We miss you” in Shopify Email or Klaviyo are not the transactional failed-payment path. Building a campaign does not fire when a specific gateway decline lands. Mixing campaign email with native / app notification / Flow actions is how you pay for three products and still send none on decline. If Flow never runs on any trigger, that is the broader Shopify Flow not running playbook. This page assumes failed-payment / dunning events exist and asks why the recovery path stays quiet.

Pick one owner for payment-failed / dunning / card-update. If Recharge (or Skio / Appstle / Shopify Subscriptions) owns it, turn the duplicate Klaviyo flow and Shopify Flow Send email off for that event. If native Shopify owns one-time declines and the subscription app owns recurring declines, document that split so nobody “cleans up” the wrong toggle. Running both is how the customer gets two emails, contradictory copy, or silence after someone disabled the live owner.

The subscription renewal playbook at /subscription-renewal-email-not-sending is about upcoming-charge reminders before a successful rebill. This page assumes a charge already failed or a dunning attempt exists and asks why recovery mail is quiet. Fix ownership first, then templates.

The order Timeline or subscription-app log can show Payment failed / Dunning / Card update email sent while the customer swears silence. Check the From domain / SPF / DKIM Shopify or the app uses, Gmail Promotions vs Primary, and whether the subject looks like marketing (“exclusive offer — update your wallet”) so filters bury a recovery notice. Force one test payment-failed / dunning email to an inbox you control. Search spam for the exact subject the template uses.

If the log says sent and the inbox is empty after spam checks, fix deliverability — do not buy another recovery email app to paper over a domain that already fails DMARC on order confirmation.

An upcoming-charge / renewal reminder is subscription renewal. Leaving a card Payment pending is payment pending. Leaving a retail cart unpaid is abandoned checkout. Cash on delivery retail is COD confirmation. Cancelling an order is order cancelled. Issuing a refund is refund.

The only honest test for this page: a real or test decline / payment-failed / dunning attempt to an inbox you own, payment-failed or dunning / card-update template Active in native Shopify or the subscription app (or the single Flow / Klaviyo owner Live), then Timeline / app email log + inbox. Anything else is a different product.

Stay DIY if you can spend one afternoon on the list above: decline / dunning event exists, one owner’s template or Flow Active, sender/spam checked. Force one live test email to an inbox you own. Read the Timeline or app log. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related troubleshooting: subscription renewal not sending, payment pending not sending, abandoned checkout not sending, order cancelled not sending, refund not sending, Shopify Flow not running.

Pay for help when the work is not the notification toggle — it is connecting the stack you already have so every decline and dunning attempt emails the customer, lead capture is not dying in DMs, and checkout-ready ops paths are one live workflow instead of a draft Flow plus a payment-failed template 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 Recharge / Skio / Appstle rebuild, not a Klaviyo rebuild, not a Gorgias implementation, not a support VA, not a brand or theme job.

Other shops’ public ranges, not testimonials: a Shopify Flow or notification-path install typically runs $500–$2,500. A full ops / recovery-email 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 a ticket-cut number or recovered declined-order revenue.

What it does not buy: fewer decline tickets, recovered revenue from dunning trust, a lift in recovery rate, 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.