50 Dunning Email Subject Lines That Get Opens

This is a swipe file, not a leaderboard. The 50 dunning email subject lines below are patterns and examples you can copy, adapt, and test — grouped by the stage of the sequence where each belongs. One honesty note up front: we publish no open-rate or performance statistics for these lines, because we have none that are verified, and any page ranking subject lines by invented percentages is making numbers up. What we can give you is the structure that makes a dunning line work, fifty honest examples built on it, and a do-and-don't list that keeps you out of the two traps that sink dunning email: fake urgency and fake familiarity.

Pair these lines with the full bodies in our dunning email templates — the line earns the open; the email earns the card update. For the system around the sequence, see dunning emails that work and the dunning management guide.

The patterns behind the lines

Every line below is built from five honest ingredients. Learn them and you can write the fifty-first line yourself.

• Name the product. Subscribers should know whose charge failed before they open. Hiding your identity to buy curiosity is a spam trick.
• Name the event, plainly. A payment failed. A card needs updating. A subscription will pause on a specific date.
• Use real specifics as merge fields. Bracketed fields like [Plan], [Amount], and [Date] stand for the subscriber's actual values. A real date is the only urgency dunning is allowed.
• One idea per line. A line carrying the failure, the deadline, the fix, and a promotion carries none of them.
• Escalate information, not volume. Later lines add consequence and specificity, not capital letters and adjectives.

Stage 1: First notice (lines 1–10)

The first notice goes out right after the initial failure. Tone: a heads-up, not an alarm. The line's job is recognition and a low-drama path to the fix.

1. "Your [Plan] payment didn't go through" — the plain baseline: event plus plan named.
2. "[First name], there's a problem with your [Product] payment" — personal and direct, no fake familiarity.
3. "Action needed: update your card for [Plan]" — leads with the fix, not the failure.
4. "Your [Product] subscription payment failed — here's the fix" — event plus a promise the body keeps.
5. "A quick fix to keep your [Plan] running" — small-task framing; true at this stage.
6. "We couldn't process your [Amount] payment for [Plan]" — the real amount earns recognition.
7. "Your card was declined for [Product] — nothing is cancelled yet" — answers the first fear; true now.
8. "Billing hiccup with your [Plan] account" — low-drama. This stage only.
9. "[First name], your [Product] payment needs attention" — softer variant for formal voices.
10. "Keep [Plan] active: one billing detail to check" — benefit first, one small task.

Stage 2: Reminder (lines 11–19)

Reminders go to subscribers who have not acted. Restate the event, add the first real date — the next retry, or when access changes — and never fake a reply thread.

11. "Reminder: your [Plan] payment is still outstanding" — honest label: it is a reminder.
12. "Still time to fix your [Product] billing, [First name]" — window open, not forever.
13. "Your [Plan] retry happens on [Date]" — a real retry date informs.
14. "Second notice: [Amount] for [Product] hasn't cleared" — sequence position is legitimate information.
15. "[First name], your card for [Plan] still needs updating" — "still" carries the reminder.
16. "Don't lose your [Plan] settings and history" — concrete loss, if truly applicable.
17. "Your [Product] account is past due — update your card to catch up" — status plus exact action.
18. "Checking in about your [Plan] payment" — lightest reminder; use early.
19. "Before [Date]: one step to keep [Plan] active" — only with a genuine milestone date.

Stage 3: Urgency without fake urgency (lines 20–27)

Urgency is legitimate exactly when it is factual: a retry window closing, an access change, a grace period ending. The pattern is consequence plus date, with no decoration.

20. "Your [Plan] will pause on [Date] unless your card is updated" — consequence plus date. The stage template.
21. "[First name], [Number] days left to save your [Product] account" — only if computed from the real end.
22. "After [Date], [Plan] access changes — here's what to do" — change stated, not dramatized.
23. "Your grace period for [Product] ends [Date]" — a real end date: honest urgency.
24. "Last retries running on your [Amount] [Plan] payment" — only in the genuine final attempts.
25. "Avoid losing [Plan]: update your payment method by [Date]" — deadline on the action.
26. "[Product] billing: action needed before [Date]" — compact; suits B2B finance triage.
27. "Your [Plan] subscription is at risk on [Date] — one update fixes it" — checkable because the date is real.

Stage 4: Final notice (lines 28–35)

The final notice is the last email before the subscription cancels or access ends. Gravity without theater: "final" is allowed here and only here, and the cancellation date is stated. A final notice that is not actually final destroys your credibility.

28. "Final notice: your [Plan] ends on [Date]" — the direct form. Once, when true.
29. "[First name], your [Product] subscription cancels [Date]" — says cancellation, not "change."
30. "Last chance to keep [Plan] — update your card by [Date]" — only if nothing follows it.
31. "Your [Amount] [Plan] payment: final attempt on [Date]" — amount and date aid recognition.
32. "We're closing your [Product] billing on [Date] unless we hear from you" — sounds like a decision, not theater.
33. "Before your [Plan] account closes: your options" — only if the body lists real options.
34. "[First name], this is the last email about your [Product] payment" — must literally be the last.
35. "Keep your [Plan] history: act before [Date]" — leads with preservation, not loss.

Stage 5: Card-update specific (lines 36–43)

Some failures are not about willingness or funds — the card expired, was replaced, or was reissued, and no retry schedule fixes a number that no longer exists. These lines slot into any stage when the decline names the card itself. The pattern is card event plus one-minute fix.

36. "Your card for [Plan] has expired — add the new one" — names the known cause.
37. "New card? Update it once to keep [Product] running" — for replaced and reissued cards.
38. "Your bank replaced your card — [Plan] needs the new number" — explains an unknown failure.
39. "Update your payment card for [Product] in about a minute" — only if your flow is that short.
40. "The card ending [Last four] isn't working for [Plan]" — strongest recognition signal; real digits only.
41. "One new card detail keeps your [Amount] [Plan] payment on track" — card ask plus amount.
42. "[First name], your [Product] card update is still pending" — for unfinished update-page visits.
43. "Secure link inside: update your [Plan] card" — must land on your branded update page.

Stage 6: Annual-plan, high value (lines 44–50)

An annual plan concentrates a year of revenue into one charge; losing that subscriber loses the year. Name the renewal and what the subscriber keeps, and give these subscribers your clearest lines — plus a human touch at the final stage.

44. "Your [Plan] annual renewal of [Amount] didn't process" — first-notice pattern, annual amount included.
45. "Keep your year of [Product]: update your card before [Date]" — preserves a deliberately chosen year.
46. "[First name], your annual [Plan] rate is locked in — one billing update keeps it" — only with a genuinely locked rate.
47. "Your [Plan] annual plan renews at [Amount] — the card on file needs attention" — large amount, early visibility.
48. "Don't restart your [Product] year over a card detail" — small cause, large consequence.
49. "Final notice for your annual [Plan]: it ends [Date]" — final-notice pattern, annual stakes.
50. "We'd rather fix this with you: your [Plan] annual renewal" — only with genuine human follow-up.

Do and don't

• Do name your product and the actual event in every line, at every stage.
• Do use real dates, real amounts, and real last four digits when a line calls for specifics.
• Do escalate information across the sequence — new facts, closer dates, clearer consequences.
• Do reserve "final" and "last" for lines after which the sequence truly ends.
• Do keep the subject line's promise identical to the email body's first screen.
• Don't use fake "RE:" or "FWD:" prefixes to impersonate a reply thread.
• Don't invent deadlines: no false "expires tonight," no resetting countdowns, no final notice followed by more email.
• Don't hide the failure behind curiosity bait — "You won't believe this, [First name]" has no place in a message about money.
• Don't shout: capitals and exclamation marks read as spam.
• Don't claim a personal sender the email does not have.

Adapting the file to your sequence

Three working rules. Test lines inside a stage, not across stages. Read every finished line as the subscriber — a wrong date, amount, or card digit is worse than a generic line. And retire any line that stops being true when your sequence changes.

Swipe Again's dunning runs on this discipline: branded dunning emails and card-update pages, SMS in the sequence, and decline-code-aware smart retries — up to 6 attempts over about 16 days, hard declines never retried — so email and retries agree about what is happening to the payment. It is $179/mo flat with no percentage of recovered revenue, on a 14-day trial with the card upfront. The guarantee, in exact form: "Recover $179 in 30 days, guaranteed — or Swipe Again is free the next 30 days."

The bottom line

Fifty lines, six stages, one principle: a dunning subject line earns its open by being the clearest true statement of where the subscriber's account stands — product named, event named, real date or real amount included, nothing faked. Copy the lines that fit, fill merge fields with true values, and hold the do-and-don't list as law.

Frequently asked questions

How many subject lines does a dunning sequence need?

One per stage at minimum: first notice, reminder, honest-urgency, final notice, plus card-update lines for card-caused declines and higher-touch lines for annual plans. The 50 lines here give you choices per stage, plus spares to test.

Do these subject lines come with open rates?

No. We have no verified performance statistics for these lines and publish no invented ones. They are patterns built on this page's principles — name the product, name the event, use real specifics, escalate information rather than volume. Test them in your own sequence and let your data rank them.

Is it ever acceptable to write "final notice" in a subject line?

Yes, exactly once: when the notice is actually final. The same applies to "last chance" and "last email." If another message follows a line that claimed to end the sequence, that subscriber discounts every future sequence you send. Finality is a claim; make it only when true.

Why not use "RE:" to make a dunning email look like a reply?

Because it misrepresents what the message is. It may buy one open, but it teaches subscribers your emails deceive — fatal for messages asking someone to enter card details through a link. Dunning runs on trust.

Should the subject line include the amount and date?

When they are real and pulled from the subscriber's actual account: a true amount aids recognition, and a true date is the only honest urgency dunning has. Never send a line whose date or amount you have not verified.