Payment banners: Strategy & best practices
Optimize subscription retention with strategic payment banner timing, frequency caps, and copywriting best practices. Learn how to craft high-converting, compliant messages for failed payments, active dunning cycles, and high-value annual pre-renewals.
Retain • Payment banners
Strategy & best practices
Banners succeed or fail on three things: timing, messaging, and frequency. Get all three right and you'll see measurable retention gains.
Navigation Menu
Navigate Home
Strategy & best practicesTiming & frequency
The single biggest factor in banner performance isn't design or copy — it's whether the banner fires at the right moment and at the right cadence. Fire too early and it's noise; fire too often and subscribers learn to ignore it; fire too late and the damage is done.
| Scenario | When to fire | Frequency cap |
| Expiring card | 30 days before expiry; repeat at 14 days if not updated | Once per 5 sessions or once per week — urgency is low, give them time |
| Failed payment | Next login after the decline — every session for first 3 days, then every 3 sessions until resolved | High frequency is appropriate here — the window is short and the stakes are high |
| Annual pre-renewal | 30 days before the renewal date | Once per week in the 30-day window — weekly reminders before a specific date are sufficient |
| In-dunning recovery | Next login while dunning is active — every session for first 3 days, then every 3 sessions | Same as failed payment — dunning window is short; high frequency reinforces email |
| Cancel save (Engage) | Only when subscriber navigates toward cancellation | Once per active cancel session only — never surface on regular product sessions |
Only 23.3% of failed annual renewals are ever recovered, compared to 53% for monthly. The pre-renewal banner is worth more than any recovery effort after the charge fails — deploy it for every annual subscriber without exception.
Messaging
Specificity builds trust — mentioning the actual card digits or renewal date signals a real alert, not a generic notification. A single clear CTA removes all ambiguity about what to do next.
Do
- Be specific — mention card last four digits or renewal date
- State the consequence calmly: "to keep your subscription active"
- Use a direct, single CTA: "Update payment method"
- Keep copy to two sentences or fewer
- Clear the banner automatically once the issue is resolved
- Exclude the billing info page from display rules
Don't
- Use alarming language: "URGENT", "WARNING!", "Account will be suspended"
- Send the same generic message for every trigger
- Use vague CTAs: "Click here", "Learn more", "Take action"
- Show the banner when the subscriber is already on the billing page
- Leave a resolved banner visible after the issue is fixed
Example copy by scenario
Expiring card: "Your card ending in 4242 expires in 28 days. Update your payment method to keep your subscription active." → Update now
Failed payment: "We couldn't process your last payment. Update your billing info to restore full access." → Update billing info
Annual pre-renewal: "Your annual plan renews on March 15. Confirm your payment method is up to date to avoid any interruption." → Review payment method
During dunning: "We still haven't been able to process your payment — update your billing info now to keep your access." → Resolve now
Cancel save (Engage): "Before you go — would you like to pause your subscription instead?" → Explore my options
Want help applying this to your business?
Strategy questions — the right frequency cap for your subscriber mix, whether your dunning and banner timing are complementary, which scenarios to deploy first — are best answered live. Join a Customer Success Global Office Hours session and our CSMs will work through your specific setup with you. Sessions run weekly and are free for all Recurly customers.
Register for Office Hours →