← All templates

Template

Friendly Payment Failure Email (Day 0)

The first email sent immediately after a payment fails, before any retry. Goal: catch the 40-60% of failures that resolve with a simple nudge, before the customer feels embarrassed or annoyed.

EmailDay 0 (first touch)Tone: FriendlyB2C

Subject line options

A/B test these. Lowercase, question format, and specific-time framings consistently win.

  • Quick heads-up about your {{product_name}} payment
  • Your card was declined - takes 30 seconds to fix
  • Small hiccup with your {{product_name}} subscription
  • quick thing about your payment, {{first_name}}

Template

Hi {{first_name}},

Quick note - the card on file for your {{product_name}} subscription
was declined today when we tried to process your ${{amount}} payment.

This happens all the time (banks flag subscriptions as "unusual
activity", cards expire, limits get hit). No action needed beyond
updating your card when you get a minute.

→ Update your card (takes 30 seconds)
{{secure_update_link}}

We will automatically retry the payment once your card is updated.
Nothing to cancel, nothing else to do.

Ping me if you hit any trouble.

- {{sender_first_name}}
{{product_name}}

Variables in {{like_this}} should be replaced with your merge fields.

Why this template works

Normalizes the failure with "this happens all the time" which pre-handles customer anxiety and embarrassment. Single tokenized link (no login wall, no form). Signed by a real human with first name. No legal language, no alarm language. The 30-second framing removes friction objection.

Implementation tips

  • 1Use a real sender name and reply-to address, not no-reply@
  • 2Lowercase subject lines feel more personal
  • 3The link should be tokenized (one-click, pre-authenticated) - no login required
  • 4Cancel the sequence immediately when the retry succeeds
  • 5A/B test 2-3 subject line variants per campaign

Frequently asked questions

When should I send this email?

Immediately after the first retry fails, or at the moment the initial charge is declined if you retry on a delay. Timing matters: sending within 2 hours of the failure recovers 20-30% more than waiting 24 hours.

Should I send a different version based on decline reason?

Yes. Customize the body for expired_card (administrative), insufficient_funds (sensitive/soft tone), do_not_honor (direct with bank-call instructions), and authentication_required (SCA 3DS link). Generic copy converts 15-25% worse.

Automate this with Rebounce

Rebounce sends this template automatically based on decline codes and timing

Rebounce detects payment failures via Stripe Connect, classifies them by decline code, and runs the optimal dunning sequence across email, SMS, WhatsApp, and in-app banners. The templates above are the exact patterns Rebounce uses out of the box - you can adapt the copy to your brand voice and Rebounce handles delivery, timing, and sequence cancellation when a retry succeeds.

Start free trial