Failed payment and incomplete checkout recovery with SMS + email

Payment-failure / incomplete-checkout recovery means: when a shopper reaches the gateway but payment does not complete, you run a short SMS + email sequence that says “your payment did not go through” and returns them to the same checkout — not a generic abandoned-cart template.

What is failed-payment recovery?

Abandoned cart covers shoppers who left with items in the basket. Failed payment is one step later: identity is often known, a pending payment order may exist, and the gateway returned an error, cancel, timeout, or 3-D Secure failure (Zarinpal, IDPay, NextPay, or whatever the store uses).

2026 recovery guides recommend naming the failure clearly, offering an alternative method, and capping the sequence at a few touches. Iranian WooCommerce SMS recovery plugins likewise treat “half-paid / pending payment” as its own scenario.

Merchants usually ask: “What SMS and email should I send when the gateway fails?” Practical answer: a separate payment_failed tag, a return-to-pay link, a helpful tone, and immediate exit after a successful purchase.

Why Iranian stores care now

Gateway blips, card limits, OTP friction, and COD habits leave many shoppers “almost bought.” Reusing “your cart is waiting” feels off; sending nothing wastes expensive acquisition.

Early Mehr / October 2026 adds pressure: pre–Black Friday traffic stresses gateways, paid acquisition is costly, and a precise message can offer a second gateway or COD without rebuilding the whole funnel.

Suggested compact sequence

2026 rule of thumb: about three touches max for payment recovery.

Sample SMS

“[Brand] payment for your order did not finish. Complete here: [short link]. Need help? Message support.”

Avoid: instant “30% last chance” when the issue may be the bank; three SMS in one hour; homepage links instead of pay/checkout return.

Sample email subject

“Payment for order #[id] did not complete”

Body: one clear paragraph (only claim “no final charge” if your capture state is truly clean), a single continue-payment CTA, a short item list, and one line about an alternative method (second gateway or COD if truly enabled). For high-AOV carts, invite human Live Chat.

Step-by-step implementation

1. Separate the event — payment_failed, checkout_payment_abandoned, or durable pending_payment beyond X minutes; do not merge with generic cart abandon.
2. Preserve session/order ids — links should return to the same invoice or checkout when possible.
3. Suppress — successful buyers, shoppers who completed via COD, opt-outs.
4. Channel priority — mobile → fast SMS; email for detail; web push only if subscribed and not crowding SMS.
5. Value branch — above AOV threshold → human support path after touch 1; small carts stay automated.
6. COD handoff — if you suggest COD and they place it, enter the COD confirmation journey next — do not keep saying “payment failed.”
7. Gateway QA — expired links, cancelled orders, OOS SKUs.
8. Report — recovery rate, time-to-purchase, opt-outs.

Coordination with cart and browse abandonment

• Left before the gateway → cart/browse journeys;
• Touched the gateway or has pending payment → failed-payment journey;
• If both could fire, use priority + mutual suppress so nobody gets “cart” and “payment” SMS within 15 minutes.

Common mistakes

1. Cart copy with one word swapped;
2. Instant coupons for every OTP failure (feels like a ransom and burns margin);
3. Expired links;
4. Claiming “no money was taken” when capture state is unclear;
5. Messaging after a successful purchase;
6. Blasting promo SMS to transactional-only numbers — keep recovery service-like and separate from sale broadcasts.

How to build it in Leadara (truthfully)

With events, segments, journeys, email, and SMS via your Kavenegar or Nikaline:

1. Trigger on payment-failure / incomplete-checkout events or a pending_payment segment;
2. Short journey: SMS → wait → email → optional final touch;
3. Exit on purchase_completed / paid / cancelled;
4. For high-AOV, branch to the team via human Live Chat after the first touch;
5. Use in-dashboard AI Chat only to draft internal copy — it does not answer customers in Live Chat;
6. Exit-intent popups can enrich identity earlier but do not replace this journey;
7. Align frequency caps with other promos so a failed payer is not also hit by three sale blasts the same night.

FAQ

How is this different from abandoned cart?

Cart abandon may happen before payment data. Failed payment is gateway friction; the copy should say so.

When should the first SMS go?

Often within 15 minutes; a 60–90 second delay can avoid interrupting an in-progress retry.

Should we include a discount code?

Try without first. Save incentives for a final touch or selected carts — not every dynamic-password failure.

Can we offer COD as an alternative?

Yes if COD is truly available for that cart — one line is enough — then move into COD confirmation.

Is a night SMS OK?

A same-session failure ping is reasonable; push the 24h reminder to daytime.

How do we QA links?

Create a sandbox/cancelled-pay test order and walk the full mobile path.

What if the gateway is nationally down?

Switch copy from “retry your card” to “gateway is unstable — try COD or later” using an incident flag.

Is open rate the success metric?

No. Recovered purchases and recovered revenue matter more.

Wrap-up and next step

This week: split payment_failed from abandoned cart, ship a 15-minute SMS + detail email with exit on purchase, add human Live Chat for expensive carts, and compare recovery rate to your cart journey for a month. Someone who reached the gateway is your cheapest lead — bring them back with the right message.

Related reading

• Abandoned Cart Recovery Playbook
• Browse abandonment recovery SMS + email
• Transactional vs promotional email and SMS