How To Configure Baremetrics Dunning Management For Failed Payments

Baremetrics dunning management runs through Recover, the Baremetrics tool for failed payment recovery. A failed renewal rarely announces itself. The charge declines, the customer never notices, and MRR drops quietly.

This guide shows how to configure Recover step by step. You will connect your billing data, fix email delivery, set retries, build the billing page, and test the flow. Baremetrics changes menus and defaults over time, so confirm each setting in your own dashboard and in the official help center.

What Recover does and what to expect

Baremetrics describes Recover on its Recover feature page. The page lists these core functions.

• Recover starts an email sequence when a charge fails in Stripe or Braintree. The page lists up to 7 customizable emails.
• Recover sends two card expiration reminders, at 30 and 7 days before expiry, and two annual renewal reminders.
• Email and SMS sequences can be mixed.
• Each email carries a branded billing link. Customers enter a new card, and Recover writes the card back to Stripe or Braintree. Baremetrics also lists Recurly for card write-back.
• A JavaScript widget shows a banner to delinquent customers. After a configurable grace period, the banner can become a paywall.
• Stripe Smart Retries run alongside Recover. Recover adds outreach on top of the retries.

Pricing depends on MRR after a 14 day free trial. Baremetrics also lists a credit if recovered revenue does not cover the full account cost. Read the current terms on the feature page before you start.

Before you configure Recover

Good dunning starts with clean data and clear rules. Review the items below first.

Item to review	Reason	What to check
Billing connection	Recover reads failed charges from your processor	Stripe or Braintree account connected and syncing
Customer emails	Emails need a valid address to reach people	Billing contacts exist and look correct
Sender domain	Poor delivery hides every reminder	DNS records ready to edit
Access policy	Customers need a clear timeline	Grace period and lockout date decided
Brand basics	Billing emails should look trusted	Logo, sender name, reply inbox, and support link ready
Owner	Finance and support must agree on the flow	One person owns changes and reports

Decide who answers confused customers. Finance often controls billing while support handles replies. When both teams know the timeline, launch goes smoothly.

Step-by-step Recover setup

The Baremetrics Recover 101 setup guide lists the official order of work. Follow the steps below and compare each screen with the guide.

1. Start the free trial in the Recover app.
2. Configure DNS settings so emails reach inboxes.
3. Review and customize the 7 email templates.
4. Enable Stripe Smart Retries if you use Stripe.
5. Set up the hosted billing URL or host your own.
6. Embed the widget on your website or app.
7. Customize the credit card capture form.

Step 1: Fix DNS first

Baremetrics calls the DNS step crucial for email delivery. Add the records Baremetrics gives you at your domain host. If your host asks only for the subdomain, enter just the subdomain, such as baremetrics. Wait for the records to verify before you turn on any sequence.

Step 2: Customize the email templates

Open the Settings icon in the side toolbar and go to the email templates section. Baremetrics provides 7 templates. You can toggle each one on, or edit the wording, style, and branding.

Keep each email short. Use a clear subject line, one payment update link, and a plain note about what happens next. Billing emails should read like a calm reminder, not a threat.

Step 3: Enable Stripe Smart Retries

Stripe merchants should enable Smart Retries in the automatic billing settings of the Stripe dashboard. Baremetrics notes Stripe sends one initial payment failed email. Multiple emails before and after a failure give the best results, so keep Recover emails on.

Step 4: Choose the billing page

Use the hosted billing page from Recover or host your own. The page collects payment details and updates the stored card for future charges. Baremetrics says the form can sit on a Baremetrics subdomain or on your own domain.

Step 5: Add the widget and paywall

The widget reaches customers who ignore email. Embed the widget where logged-in users will see the banner. Set the grace period before you enable a paywall. A harsh lockout on day one feels clumsy if a retry would succeed on day three.

Step 6: Style the capture form

Add your logo, colors, and wording to the credit card capture form. A familiar form builds trust and helps customers finish the update.

Email timing and escalation

Baremetrics publishes two schedules, and the dates differ. Treat both as examples and confirm the days inside your own Recover settings.

Baremetrics source	Email days
Ultimate Guide to Dunning Management	Day 0, 3, 7, 10, 13, 20, and 27
Recover feature page	Day 0, 3, 7, 13, 15, 20, and 30

The Ultimate Guide to Dunning Management adds more advice. The guide suggests the following.

• Warn customers about card expiry about 30 days before expiry.
• For annual plans, send a renewal warning 30 days before the charge. For monthly plans, send the warning 3 to 7 days before.
• From day 8, pause the account instead of cancelling, to keep data and make reactivation easy.
• Wait 30 to 90 days before hard cancellation, depending on your data.
• Offer personal outreach to accounts above about $50,000 ARR between day 5 and day 7.

Baremetrics also reports about 9 percent of MRR lost to failed payments. The company does not publish a sample method, so treat the figure as a vendor estimate. Compare the figure with your own numbers inside the dashboard.

Plan your grace period and access policy

Decide when service changes before you enable any sequence. A clear timeline protects both revenue and customer trust.

• Keep full access during the early email window while retries run.
• Show a banner once the first retry fails so users see a prompt inside the product.
• Move to a paywall or paused account only after the grace period ends.
• Keep data safe after a pause so reactivation takes one step.
• Publish the same dates inside your help center and your emails.

Long grace periods leave failed accounts open like unpaid tabs at a cafe. Short ones punish customers whose retry would have worked. Review your recovery numbers after one billing cycle, then adjust the dates.

Write dunning emails customers act on

Every message should answer three questions. What happened, what the customer should do, and what happens next. Use plain subject lines like these.

• Action needed: update your payment method
• Your card did not go through
• Your account will pause on a set date unless payment updates

Keep the body to a few short sentences. Add one button, your support address, and the date access changes. Skip marketing copy, discount banners, and guilt. Match the tone to the stage. Early messages stay friendly. Later messages state the pause date and the steps to restore access.

Test before you go live

Baremetrics does not describe a test routine in the setup guide. Build a simple check yourself.

1. Create an internal customer with a card you control.
2. Trigger a controlled failure through your billing processor.
3. Confirm the first email arrives in the inbox and not in spam.
4. Open the billing link and update the card.
5. Check the new card saved in Stripe or Braintree.
6. Confirm the banner or paywall appears and disappears at the right time.

Fix any gap before you enable every sequence for real customers.

Track results after launch

Watch the first week closely. Track recovered MRR, failure rate, retry success, and email engagement. If retries work but clicks stay flat, the copy may be too vague. If people open emails but revenue stays stuck, the billing page may be the problem.

Segment results by plan, billing cycle, and customer type. Annual plans can hit expired cards more often because renewals sit far apart. Pair recovery reports with churn reduction ideas for SaaS so you do not confuse billing friction with a product problem. For more on message design, read this guide to Baremetrics dunning emails. For processor side tactics, see Stripe failed payment recovery.

Troubleshooting common problems

Symptom	Likely cause	Fix
Missing payment data	Sync delay or wrong account permissions	Reconnect the billing account and check permissions
Emails not arriving	DNS records unverified or spam filtering	Recheck DNS records and sender settings
Retries not firing	Smart Retries off in Stripe	Enable Smart Retries in Stripe billing settings
Customers cannot update cards	Broken billing URL	Open the link yourself and fix the page
Low recovery	Timeline too fast or too soft	Review grace period and email days

FAQ

Do I need code to start Recover?

Email recovery needs no code after setup. The widget and paywall need a script on your site.

Which processors work best with Recover?

Baremetrics lists Stripe and Braintree for failed payment sequences and adds Recurly for card write-back. Other gateways can use email and in-app messaging without write-back.

How many emails should I send?

Baremetrics gives different counts in different places. Start with the 7 templates and shorten the sequence if customers complain.

Should I cancel accounts after the first failure?

No. Baremetrics suggests pausing from day 8 and waiting 30 to 90 days before hard cancellation.

Where do I confirm pricing?

Use the Recover feature page. Pricing depends on MRR after the 14 day trial.

Conclusion

A failed charge starts small, like a drip under the sink. Left alone, the drip becomes a mess. Connect clean billing data, fix DNS, tune emails and retries, test the flow, and watch recovery after launch. Confirm every setting in the official Baremetrics help center, then adjust the timeline around your customers.