Playbook · Payment pending / authorization failed customer mail
Shopify payment pending or authorization-failed email not sending — after checkout already tried to take money.
Written for a Shopify DTC owner whose buyer sees Payment pending, Pending payment, or Authorization failed — and the customer email that should explain what to do next never arrives. This is a native-notifications / Flow playbook for payment-pending and authorization-failed customer mail — not abandoned checkout, not draft order invoice, not refund / cancel, not gift card, not return request, not fulfillment hold, and not WISMO. Native tools first. Honest limits. No ticket-cut number, no recovered-revenue claim, no invented case studies.
Nico at Latch AI Ops · Sep 7, 2026 · ~9 minute read
Buy the 72-hour install — $997Abandoned checkout not sendingDraft order invoice not sendingOrder confirmation not sendingMerchant FAQ
01
Payment-pending mail, not abandoned checkout or draft invoice.
A payment-pending email is not abandoned checkout and not a draft order invoice. Abandoned checkout fires when a cart never became an order — that playbook is abandoned checkout email not sending. A draft order invoice is a merchant-sent pay link — see draft order invoice not sending. Order confirmation fires after the payment is captured / paid — order confirmation email not sending. This page is the buyer-facing “your payment is pending / authorization failed — here is what to do” path: native Notifications and/or Shopify Flow Send customer email on Payment pending / Authorization failed / Payment status changed to pending.
Also not this page: refund / cancel, gift card, return request / label, fulfillment hold / order on hold, WISMO. Six ordinary reasons pending mail never lands: the order never stayed Payment pending, the template or Flow send is off, Notify customer was unchecked, Flow never matched, you tested the wrong email, or sender / spam hid a send that did fire. Walk them in that order. You already pay for Shopify. You do not need a second payment-status email app to read the notification list.
02
Order never stayed Payment pending (paid, voided, or never authorized).
Payment pending / Authorization failed is a payment status, not a fulfillment status. Open the order → Payment status. If it already says Paid, the pending / authorization-failed templates have nothing to send (order confirmation may have fired instead). If the authorization never started, or the gateway voided before Shopify wrote a pending order, there is no pending event for native mail or Flow to hook.
Manual mark-as-paid, cash on delivery that never flips to pending, and test gateways that auto-capture in one step also skip the pending window. A sticky note (“buyer said they will pay later”) is not a Shopify Payment pending status. Fix the payment path so the status actually lands on pending / authorization failed, then re-read sections 03–05.
Some payment methods (bank transfer, local methods, delayed capture) stay Pending by design. Others flash Pending for seconds and then Paid — you will never catch that with a “wait 1 hour still pending” Flow. Name which payment method and which status you intended before you debug the wrong template.
03
Pending / authorization-failed template or Flow send is off.
Open Settings → Notifications → Customer notifications. Look for payment pending, pending payment, payment error, or authorization failed related templates (wording varies by Shopify plan and which payment methods you use). Read the on/off state, not Order confirmation next to them, not Abandoned checkout, not a preview. Disabled does not send. A staffer who turned native pending mail off “so Flow can own it” and then never activated the workflow leaves a hole that looks like Shopify is broken.
Many shops never enable a native pending template and instead send custom copy with Shopify Flow → Send customer email. If that is your path, a missing native template is expected — the bug is Flow (section 05), not Notifications. Do not leave both native and Flow on unless you want two emails for one pending payment.
Order confirmation can be on and pending mail still off. Abandoned checkout can be on and pending mail still off. Refund and return templates are different events again. Do not debug this page on an Order confirmation or Abandoned checkout toggle.
04
Notify customer was unchecked on the payment action.
The template can be on and still not send. Capturing, voiding, marking as pending, or retrying an authorization sometimes includes Notify customer / Send a notification to the customer. Unchecked means no email, even with a live template and a real Payment pending status on the order. Ops who quietly re-authorize cards for fraud review often never email the buyer.
This is the payments / risk trap. Someone retries twenty authorizations at 9am with the box off, then never sends. A saved browser that remembers the last payment dialog state will keep it off. Capture and void checkboxes move money — they do not send the pending email by themselves.
For the next test: create (or find) one order that truly sits on Payment pending or Authorization failed with Notify customer on (or run the Flow path), to an inbox you control, wait a minute, then read that inbox — not the order timeline alone. The timeline can show “Payment pending” without “Payment pending email sent to…”.
05
Shopify Flow payment-pending email never matched.
Some shops skip native templates and send pending copy with Shopify Flow: trigger Order payment status changed / Payment authorization failed / Order created + Payment status is Pending, then Send customer email. If that is your path, a disabled native pending template is expected — the bug is Flow, not Notifications.
Open Shopify Flow → the workflow → Run history. Inactive workflows never run. A condition that requires gateway = “Shopify Payments” will skip PayPal / third-party gateways. A wait step that has not elapsed looks like silence. An action that failed (missing customer email, template variable error) shows in the run, not in the buyer’s inbox. Full Flow debugging is Shopify Flow not running— use that page when the workflow itself never fires.
Flow “Send internal email” or Slack is staff mail. It is not the customer pending template. Do not treat a Slack ping to finance as proof the buyer got a “complete your payment” email.
06
You tested abandoned checkout, draft invoice, refund, or order confirmation.
Leaving a cart proves Abandoned checkout, not pending mail. Sending a draft order invoice proves the invoice path, not payment-pending on a checkout order. Placing a clean paid test order proves Order confirmation, not pending. Issuing a refund proves Order refund. Preview in the notification editor and Send test email prove the template renders. They do not prove a live pending / authorization-failed event fires it.
Honest test: use a payment method or gateway setting that actually leaves the order on Payment pending or Authorization failed (delayed capture, a failing test card that lands authorization failed, or a bank method that stays pending), to an inbox you own that is not the store’s staff address. Wait. Then search that inbox and spam for the store name. If Order confirmation arrived and the pending mail did not, the bug is payment status / template / notify box / Flow — not “Shopify email is down.”
Missing customer email on the order has nowhere to send — same failure mode as order confirmation, different event. POS / draft-only shops that never create a checkout pending status also never need this email.
07
Sender, BCC, and spam hid the send.
Shopify (or Flow) can send and the customer still reports nothing. Open Settings → Notifications and read the sender email. A custom from-address without authenticated DNS (SPF / DKIM for the domain Shopify tells you to add) lands in spam, or is dropped. A shared @shopifyemail.com from-address also gets filtered on some inboxes. BCC to the owner is not proof the customer got it — BCC can arrive while the To: line bounced.
On the order timeline, look for a notification sent event, not just Payment pending. If Shopify says it sent, have the customer search spam, promotions, and the exact from-address. If Shopify does not say it sent, go back to payment status / template / notify box / Flow — do not buy a deliverability app for a mail that never left.
Do not install a second payment-status email app to “make sure it fires.” You will double-email the next customer who was never the bug. Shopify Email (marketing campaigns) and Klaviyo “incomplete payment” flows are also not this native pending template — mixing them is how you pay for two products and still send none, or send three.
08
When to stay DIY vs pay $997.
Stay DIY if you can spend one afternoon on the list above: real Payment pending or Authorization failed status, templates / Flow on, notify box on, Flow run history if you use Flow, sender/spam. Force one live pending / failed authorization from a phone. Read the inbox. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related troubleshooting: abandoned checkout not sending, draft order invoice not sending, order confirmation not sending, refund email not sending, Shopify Flow not running, fulfillment hold email not sending.
Pay for help when the work is not the notification toggle — it is connecting the stack you already have so payment-pending / authorization-failed mail is one live path instead of a native template plus a Flow draft plus a Klaviyo incomplete- payment flow you forgot, lead capture is not dying in DMs, and exceptions show up in a channel you already check. 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 notification 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 recovery-app install typically runs $500–$2,500. A Klaviyo-only rebuild 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 checkout revenue.
What it does not buy: fewer WISMO tickets, recovered checkout revenue, a lift in conversion, 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.