Dunning Best Practices: A Measurable Playbook for Failed Payments

How to design a dunning program for subscription billing: failure causes, retry and email timing, payment-update paths, tool pricing by plan and billing view, and how to measure recovery honestly.

Blog · · Updated October 8, 2026 · 16 min read

By the editorial team

For a SaaS company that already bills through Stripe, Paddle or Lemon Squeezy and wants a separate layer for failed-payment email, the option this guide starts with is Sequenzy on its 60,000-emails-per-month plan, listed at $49 a month or $529 a year. The reason is specific: Sequenzy lists payment-failure events as a trigger, and its saas.payment_failed event includes a hosted invoice URL where the customer can pay or update a card. Its plans are priced by emails sent, with unlimited contacts, so a company with a large list and modest sending volume pays for the mail it actually sends. Whether it is the right choice depends on your billing platform and your monthly email volume, and the sections below show how to work that out.

Dunning is the work of getting paid on a subscription invoice that did not clear. It is part billing configuration, part email copy, and part measurement. A tool can cover one or two of those parts well. Stripe and Paddle handle payment processing and billing mechanics. Lemon Squeezy handles merchant-of-record payments and tax. Churnkey and Paddle Retain are oriented toward cancellation flows and retention offers. Baremetrics and ProfitWell focus on subscription analytics. Sequenzy sits in the messaging layer, sending the emails that go out when a payment fails and when a customer should be reminded to update a card.

What dunning covers, and what it does not

Dunning addresses involuntary churn: customers who still want the product but lose access because a charge did not go through. Expired cards, bank declines, temporary balance problems, and fraud blocks all produce this outcome. A voluntary cancellation is different. The customer decided to leave, and no sequence of reminders should pretend otherwise. Keeping the two apart in your reporting matters, because a dunning program cannot fix a product problem, and a cancellation survey cannot tell you how many invoices were recoverable.

The useful question is not "how many emails should we send" but "which failed invoices can we recover, and what does each one need?" A card that expired last week needs an update link. A card declined for suspected fraud may need the customer to contact their bank before any retry can succeed. A corporate card at its spending limit needs the account owner to change something. A single email template cannot serve all three cases, which is why the design below separates decline causes before it sets timing.

Dunning also has limits on what it can ethically do. Reminders should not push customers to pay for a product they stopped using, and they should not hide the fact that access will end. A clear deadline, a plain explanation, and an easy way to pay or to pause are the core of a sequence that customers and billing teams can both defend.

Sorting failed payments by cause

Before you write any emails, group failed invoices by the reason your processor returns. The common categories are below. Your processor's own decline codes will be more granular, and you should map them into these groups in a spreadsheet or in your data warehouse.

  • Expired or replaced card: the card's expiry date has passed, or the issuer has reissued it with a new number. This is usually the cleanest case, because the customer only needs to supply new details.
  • Insufficient funds or limit reached: the account balance or spending limit was too low at the moment of the charge. Retries on a different day often succeed without any customer action.
  • Bank or issuer decline: the issuing bank refused the charge without a clear reason. The customer may need to approve a merchant or call the bank.
  • Fraud or security block: the issuer or processor flagged the charge. Repeated rapid retries can make this worse, so a slower schedule and a clear update link are usually the better response.
  • Lost or stolen card: the card has been blocked. Only a new payment method solves this.
  • Business card or purchasing-card rules: the card is valid but restricted by policy. The fix often lies with the account owner or finance team, not the person on the card.

Group recovery results by these causes once you have a few months of data. The pattern tells you where to spend effort. If most failures are expired cards, the pre-dunning reminders matter most. If most are limit-related, retry timing matters more than copy. If most are bank or fraud declines, the message should explain what the customer can do at their bank and offer a different payment method.

Designing the sequence

Pre-dunning for cards that are about to expire

Pre-dunning sends reminders before a failure occurs. A customer whose card is expiring in the next month can update it in a calm moment, and a failed charge never happens. Pre-dunning depends on card expiry dates your billing platform already stores, so it costs little to set up beyond the email itself. A common starting schedule is one reminder about 30 days before expiry, a clearer prompt about 14 days before, and a final reminder about 7 days before, each with a direct link to the payment-method page.

Pre-dunning does not replace active dunning. Customers who never received a reminder still fail, and expiry dates do not cover declines, limits, or fraud blocks. Treat pre-dunning as the cheapest part of the program and measure it separately, because its success shows up as fewer failures, not as recoveries.

Active dunning after a failure

When a charge fails, the sequence starts. The first message should be calm and specific. It should say that the payment did not go through, that the account is unchanged for now, and that the customer can update their payment method with one link. Avoid words that imply blame or alarm on the first send. A typical structure after the first email is a second message a few days later with more detail about the decline, a third message that states the access deadline, and a final notice that gives an exact date.

Cadence should follow what you learn from your own cohorts. A widely used starting point is a message on the day of failure, another around day three, a clearer deadline around day seven, a final warning around day ten, and a last notice around day fourteen. Monthly products with low prices often work with a shorter sequence. Annual invoices and high-value accounts may need a longer window and a person involved earlier, because the cost of a wrong guess is higher.

Retry timing

Retries run alongside the emails and should be designed together with them. Retrying the same card several times on the same day rarely helps and can make fraud rules more likely to block the charge. A common starting point is three or four retries spread over one to two weeks, with the spacing set by your processor's guidance. Some teams retry near common paydays, because insufficient-funds declines are more likely to clear around those dates. Document the schedule, because the email timing has to match it. An email that says "we will try again tomorrow" is wrong if the next retry is three days away.

Stop rules

A sequence must end when the reason for it ends. The payment succeeding is the obvious stop. A customer who cancels, changes plan, or moves to a different payment method should also leave the dunning flow, because continuing to send "your payment failed" emails after the account is closed is confusing and can create support tickets. Test both paths in staging before going live. A test failure should create one enrolment, and a test success or cancellation should remove the contact from the sequence within the time your messaging tool takes to process events.

Writing the messages

Dunning emails are read by customers who are busy and sometimes annoyed. Three principles hold across most products. First, state the problem in one sentence. Second, make the fix one click away. Third, tell the customer what happens next and when. Anything beyond those three items is optional.

Send from a named person or from a monitored address that replies to a human. Messages from "billing@" or "noreply@" can read as automated and are easy to ignore. A reply path also gives you a source of information about declines that the processor does not show, such as a customer whose card was replaced by a company that has since changed its banking.

Keep the tone factual and warm. Acknowledge that card expiry and bank declines happen to everyone. Do not write "pay now or lose everything", and do not add a discount to a failed payment, because a discount treats a technical failure as a price objection and can teach customers that failing a payment is a way to get a better deal. Use waived late fees or a grace period if you offer them, and say so in plain terms.

Sample Day 1 email, adapted for a monthly subscription:

Subject: Your latest [Product] payment did not go through

Hi [Name],

We could not process the payment for your [Product] subscription this time. Cards expire, banks sometimes decline charges, and this is usually a quick fix.

Your access is unchanged for now. You can update your payment method in under a minute here:

[Update payment method]

If the link does not work for you, reply to this email and tell us which card or bank you are using, and we will help you sort it out.

Thanks,
[Name], [Company]

Sample final notice, sent before the access deadline:

Subject: Your [Product] access ends on [date]

Hi [Name],

We have tried to collect payment for your [Product] subscription several times without success. If the payment is not updated by [date], your access will be paused.

Your data stays saved, and you can restart the subscription at any time after that date. To keep your access without interruption, update your payment method here:

[Update payment method]

If you have decided to stop using [Product], you do not need to do anything, and we will not send further payment reminders.

Thanks,
[Name], [Company]

Making the payment update easy

The payment-update path is where most recoveries are won or lost. Every extra step, such as a login screen, a navigation menu, or a page that asks for the password again, reduces the number of customers who finish. A link that opens the payment-method page directly is the best option. Hosted invoice pages are another. Several billing setups provide a link to a page where the customer can pay an open invoice or change the card on it, and a dunning email that links to that page gives the customer one action to complete.

Mobile matters because many customers open billing emails on a phone. Test the update page on a small screen, with a saved card and with a new one, before you send anything. Make sure the payment form shows the errors a customer needs to fix, such as an invalid expiry date, instead of a generic failure message.

Card account updater services are another route. These services, offered through card networks and processors, pass new card details to the merchant when an issuer reissues a card. They recover some failures without any customer action, and they are worth asking your processor about. Confirm the details with your processor, since availability and coverage vary by card network and region.

The tools, one by one

The table below lists the tools named in this guide with their starting price and billing view, based on each vendor's public pricing page as checked on October 7, 2026. Where a vendor does not publish a price, the table says pricing on request. Prices can change, so read the vendor's page before budgeting.

Tool Best for Starting price (plan and billing view) Key limitation
Sequenzy SaaS teams that want dunning emails started by payment-failure events and priced by email volume Free: 2,500 emails/month. Paid 15k emails/month: $19/month or $205/year Priced by emails sent, so frequent lifecycle mail raises the plan you need
Stripe Teams that need card processing and subscription billing as the base layer Standard card processing: per transaction, no monthly platform fee on standard pricing Processing is per transaction, and the email messaging around it is a separate design choice
Paddle Billing Software sellers who want merchant-of-record billing with tax and payment handling Per-transaction pricing; no monthly platform fee and no free plan Transaction pricing applies to every sale, so the cost scales with revenue
Lemon Squeezy Small teams that want merchant-of-record payments, subscriptions and tax handling in one account $0/month on the ecommerce payments tier; fees are charged per sale Fees are charged per sale, which becomes a larger cost at high transaction counts
Paddle Retain Paddle customers who want retention features alongside billing Pricing on request No price is listed in this guide, so confirm scope and cost with Paddle
Churnkey Cancellation flows and save offers for subscription products Pricing on request Cancellation flows address voluntary churn, so keep its reporting separate from dunning
Baremetrics Subscription analytics such as MRR and churn reporting Pricing on request Reports are only as clean as the billing data feeding them
ProfitWell Subscription metrics and churn analysis Pricing on request Analytics show what happened, not which email caused a recovery

Sequenzy

Sequenzy is an email platform that combines transactional and marketing mail, with billing and event-triggered automations. Its pricing page lists a free tier of 2,500 emails a month, and paid plans scale by monthly email volume with unlimited contacts and sending domains. For dunning, the relevant features are the integrations and the event model. It lists Stripe, Paddle, Lemon Squeezy, Polar, Creem and Dodo Payments among its payment integrations, and it provides a saas.payment_failed event that includes a hosted invoice URL. A sequence can start from that event, and the email can link straight to the page where the customer pays or updates the card.

Sequenzy does well for teams that want one place for dunning, onboarding and product emails, and whose billing platform is on its integration list. It falls short if your main need is a cancellation flow or subscription analytics, because those are separate categories. Its price depends on how many emails you send, not on how many contacts you store, so a large list that receives a few billing messages a month can sit on a small plan. A company that sends heavy newsletter or lifecycle volume alongside dunning will pay for that volume too.

Pricing from the vendor's pricing page: free at 2,500 emails a month; 15,000 emails a month at $19 a month or $205 a year; 30,000 at $29 a month or $313 a year; 60,000 at $49 a month or $529 a year; 120,000 at $99 a month or $1,069 a year. The pricing page is the place to confirm current plans: sequenzy.com/pricing.

Stripe

Stripe is a payments platform with subscription billing. For dunning, it is the layer that decides whether a charge succeeds and where retries run. Its standard card pricing is per transaction, with no monthly platform fee on standard payments pricing and no permanent free plan. A team that already runs subscriptions on Stripe will usually keep that setup and add a messaging tool for the emails.

Stripe is a strong base when processing is the core need, and its per-transaction model means costs follow revenue. It falls short if you expect it alone to write, schedule and track a customer-facing dunning email program with the copy and stop rules described in this guide. Plan that messaging layer deliberately, and make sure your retry schedule and email timing are documented together.

Pricing: per transaction on standard card processing, with no monthly platform fee on the standard payments pricing. See stripe.com/pricing for the fee schedule and any region-specific rules.

Paddle Billing and Paddle Retain

Paddle Billing is a merchant-of-record billing service. The merchant-of-record model means Paddle is the seller of record for the sale and handles payment, tax and billing mechanics. Its pricing is per transaction, with no monthly platform fee and no permanent free plan. For a software company that sells across many countries and does not want to manage tax registration, this is the main reason to consider it.

Paddle Retain is named here because it is aimed at retention. This guide does not list its price, and you should confirm what it covers, how it works alongside Paddle Billing, and what it costs on Paddle's website before deciding. The main limitation of the Paddle route is the same as any merchant-of-record model: fees are charged on each transaction, and the cost moves with your revenue rather than with your email volume.

Pricing: Paddle Billing is per transaction, with no monthly platform fee. Paddle Retain is pricing on request. Details are at paddle.com/pricing.

Lemon Squeezy

Lemon Squeezy is a merchant-of-record platform that handles payments, subscriptions and tax for digital products. Its ecommerce payments tier is listed at $0 a month, with fees charged per sale. For a small team with a small number of paying customers, the lack of a monthly fee lowers the entry cost, and the merchant-of-record setup takes tax handling off the team's plate.

The trade-off is that fees accumulate with each sale, so a high-volume product pays more than it would on a flat monthly tool. Lemon Squeezy is also not a dedicated email platform, so the dunning emails and stop rules still need a messaging tool or a custom build. Check that your sequence can read Lemon Squeezy's payment events before you commit.

Pricing: $0 a month on the ecommerce payments tier, with fees charged per sale. See lemonsqueezy.com/pricing.

Churnkey

Churnkey is oriented toward cancellation flows, the screens and offers a customer sees when they try to cancel. Its value for dunning is indirect. A cancellation flow reduces voluntary churn, which is outside the scope of this guide, but it can sit beside a dunning program. The two should be reported separately so that a save offer is not counted as a recovered payment.

Churnkey is a fit when the main problem is customers who cancel deliberately and you want to test offers and exit questions. It is not a substitute for a failed-payment sequence. Pricing is on request, so ask the vendor for a quote based on your subscriber count and plan structure.

Baremetrics

Baremetrics is a subscription analytics product. It reports metrics such as monthly recurring revenue, churn and cohort retention from billing data. For a dunning program, the value is in measurement: it can show how much revenue is lost to involuntary churn and whether a change in the sequence moves that number over time.

Analytics are only as clean as the billing data behind them. If failed invoices are not tagged with their decline reason, the reports will show a total without the cause, and the cause is what tells you what to fix. Baremetrics does not write or send dunning emails. Pricing is on request.

ProfitWell

ProfitWell is also a subscription metrics and churn analysis product. It is useful for the same reporting questions as Baremetrics: how much revenue is at risk, how churn splits between voluntary and involuntary causes, and how retention changes by cohort. Like any analytics layer, it describes what happened and does not show which email caused a recovery. A holdout group, described below, is the only dependable way to attribute a recovery to a message. Pricing is on request.

Make as glue, if you need it

Make is a workflow automation service. A team that needs a payment-failure event to reach a CRM, a support queue or a spreadsheet can use it to connect those systems. Its free plan includes 1,000 credits a month, with a limit of two active scenarios and a 15-minute minimum interval between runs. The paid Core plan is listed at $10.59 a month, or $9 a month billed annually, for 10,000 credits a month. Make does not replace a dunning sequence, but it can carry data between the systems that do.

What it costs at different volumes

Sequenzy prices by the number of emails sent in a month, not by the size of the contact list, so the plan depends on how much mail goes out. Dunning volume is usually a small share of total volume, but it is worth modelling the whole account, because lifecycle and product emails count too. The table uses the plans listed on the pricing page. Read the yearly savings column as twelve monthly payments minus the yearly price.

Sequenzy plan (emails per month) Monthly billing Yearly billing (total) Yearly, per month equivalent Saving versus 12 monthly payments
Free, 2,500 $0 $0 $0 Not applicable
15,000 $19 a month $205 a year $17.08 $23 a year (12 × $19 = $228)
30,000 $29 a month $313 a year $26.08 $35 a year (12 × $29 = $348)
60,000 $49 a month $529 a year $44.08 $59 a year (12 × $49 = $588)
120,000 $99 a month $1,069 a year $89.08 $119 a year (12 × $99 = $1,188)

To make the table concrete, consider three example accounts. These are illustrations of how to apply the plan list, not benchmarks for failure rates.

  • A small product with 150 failed invoices and about 4,000 other emails a month. A five-email sequence per failure is 750 emails, and the rest is lifecycle mail. The total stays under 15,000, so the 15k plan at $19 a month applies.
  • A mid-size product sending 40,000 emails a month across billing and lifecycle mail. That volume does not fit the 30k plan, so the 60k plan at $49 a month applies. On yearly billing, the price is $529 a year.
  • A company sending 110,000 emails a month. The 120k plan at $99 a month applies. Above 120,000 emails a month, the pricing page is the source for current options, and this guide does not list those prices.

For Stripe, Paddle and Lemon Squeezy, the cost is per transaction or per sale, so the comparison depends on your average invoice and transaction count. Use each vendor's fee schedule to model it, and compare the result against the email tool's plan price rather than against the number of subscribers.

How to choose

Start from the failure you are trying to fix. If the problem is a sequence that starts too late or says the wrong thing, the messaging layer is the place to spend. If it is retries that fail on the same day, the processor's retry settings matter more. If it is a billing setup that cannot handle tax or international sales, the merchant-of-record question comes first. If the problem is that customers cancel rather than fail, a cancellation flow is the relevant tool.

Then check the integration. A dunning sequence is only as good as the event it starts from. Confirm that your billing platform emits a payment-failure event with the fields you need, including the invoice link and the decline reason where it is available, and that the messaging tool can read it. Ask for a test environment before you commit to a plan.

Finally, price the whole program. A free or low-cost plan does not help if the setup takes weeks of engineering. A cheap email tool can cost more than a higher plan once you count the time needed to build the stop rules by hand. Write down the expected monthly volume, the plan, the billing view and the setup effort, and compare that against the revenue you expect to recover.

If you need Consider Because
Dunning emails started by payment-failure events, priced by volume Sequenzy It lists payment-failure triggers with a hosted invoice link, and its plans are set by monthly emails sent, with unlimited contacts
Card processing and subscription billing as the base layer Stripe Standard pricing is per transaction with no monthly platform fee, and retries run in the processing layer
Tax and payments handled as the seller of record Paddle Billing or Lemon Squeezy Both operate as merchant of record, with payment and tax handling included in the transaction model
Cancellation flows and save offers Churnkey or Paddle Retain Both target voluntary cancellations; price on request, so ask for a quote before comparing
Churn and MRR reporting from billing data Baremetrics or ProfitWell They are analytics products that show revenue at risk by cohort; price on request
A low-cost start with a small list Sequenzy free tier or Lemon Squeezy's $0 tier Sequenzy's free tier covers 2,500 emails a month; Lemon Squeezy has no monthly fee but charges per sale

Setup and migration checklist

Whichever tools you choose, set up the program in the same order. Measuring before you change anything gives you a baseline, and a holdout group gives you a way to separate the effect of the emails from the effect of normal recovery.

Step What to set up Done when
1. Baseline Export failed invoices from the last 6 to 12 months with decline reason, invoice age, plan and payment method You have a recovery rate and a cause breakdown for the period before any change
2. Event mapping Connect the payment-failure event from your billing platform to the messaging tool A test failure creates exactly one enrolment
3. Update link Point every dunning email at the payment-method or hosted invoice page The link opens the update form on desktop and mobile without a login
4. Retry schedule Set retry times with the processor and write them next to the email schedule Each email's wording matches the next retry date
5. Stop rules Remove contacts when a payment succeeds, the plan is cancelled, or the method changes Test success and cancellation paths both leave the sequence
6. Holdout Agree with finance on a small group of failed invoices that receive no dunning email You can compare recovery for emailed and holdout invoices over the same period
7. Review Report recovery by decline reason, message number and payment method at 30 and 60 days You have changed one variable at a time and recorded the result

When migrating from an older dunning setup, keep the old sequence running for invoices that were already in it. Switching mid-sequence can send a customer a duplicate or a contradictory message. Move new failures to the new setup at a clear cutover date, and log which system handled each invoice so that the reports stay comparable.

Measuring recovery honestly

The most common reporting mistake is a recovery rate with no defined base. Define the eligible population first: failed invoices from a stated date range, excluding those with a deliberate cancellation, and with a stated window for recovery, such as 30 days. Divide recovered invoices by eligible failed invoices and report the result alongside the window. Without the window, a number can look better simply because the measurement period is longer.

Break the result down by decline reason, payment method, customer segment and message number. A program that recovers many expired-card failures but few bank declines needs different work from one that recovers little overall. The message number matters because it shows whether the later emails add anything, or whether most recoveries happen before the second message.

Use time-to-recovery as a second measure. Report the median and a high percentile rather than only the average, because a small number of very long recoveries can hide the typical case. Also track involuntary churn as a share of total churn, so you can see whether dunning is moving the number that matters for the business.

The holdout group is the strongest evidence you can produce. Without it, you cannot tell whether a recovery came from the email or from a card that would have cleared anyway. A holdout does cost some recoveries, so size it with finance and keep it small and stable for the test period. Once you have a result, decide whether it is large enough to justify the program, and write that decision down.

Common mistakes to avoid

Escalating too fast. Threatening language in the first two emails damages the relationship and does little for recovery. Save the deadline for the final notices.

Skipping pre-dunning. Waiting for a failure to act means you accept failures that a reminder could have prevented. Card expiry dates are usually already in your billing data.

Making the fix hard. A login wall or a long form between the email and the payment page loses customers at every extra step.

Sending after success. A dunning email arriving after the payment cleared is confusing and generates support requests. Test the stop rules before launch.

Offering discounts for failed payments. A failed charge is usually technical, not a price objection, and a discount can teach customers that failing is a way to get a better deal.

Stopping too early. A single reminder misses customers who need several touches before they act. Let the data decide how long the sequence should run, rather than the first version you wrote.

Mixing voluntary and involuntary churn. A cancellation save and a recovered payment are different events. Report them separately, or the program will take credit for outcomes it did not cause.

How the prices here were checked

The prices in this guide come from each vendor's public pricing page and were checked on October 7, 2026. Sequenzy's figures are the plan prices listed for 2,500, 15,000, 30,000, 60,000 and 120,000 emails a month, with the yearly totals as stated on its pricing page. Stripe, Paddle and Lemon Squeezy are described by their billing model, since their prices depend on transaction volume. Make's figures are its listed plan prices for 10,000 credits a month. Where a vendor did not publish a price, this guide says pricing on request and does not estimate one. Packaging changes often, so read the pricing page on the day you decide, and check the terms for any region you sell in.

Frequently asked questions

How many dunning emails should I send, and how far apart?

A widely used starting point is five emails over about two weeks: on the day of failure, around day three, around day seven, around day ten, and a final notice around day fourteen. Adjust it by segment. Monthly products with low prices often work with a shorter sequence, while annual invoices and high-value accounts may need a longer window and a person involved earlier. Whatever you choose, make the emails match the retry schedule, and measure each message's contribution before you add more.

Does Sequenzy work with Stripe, Paddle and Lemon Squeezy?

Sequenzy lists Stripe, Paddle and Lemon Squeezy among its payment integrations, along with several other billing and commerce platforms. Confirm that the integration covers the events and fields your sequence needs, such as the payment-failure event and the hosted invoice link, by testing it in a staging account before you rely on it.

Is Sequenzy priced per contact?

No. According to its pricing page, Sequenzy's plans are based on monthly email volume, with unlimited contacts and sending domains on all plans. The plan you need depends on how many emails you send in a month, so model your total sending, including lifecycle and product mail, before you pick a tier.

Should I offer a discount to recover a failed payment?

Generally no. A failed payment is usually caused by an expired card, a bank decline, or a temporary balance problem, not by the price. A discount can also teach customers that letting a payment fail is a route to a better deal. If you want to show goodwill, a waived late fee or a grace period is usually a better tool, and it should be stated plainly in the email.

How is B2B dunning different from B2C dunning?

B2B customers often pay by corporate card, invoice or purchasing card, and a failure may come from a spending limit or a policy rule rather than an expired card. The person on the card may not be the account owner, so contacting the billing contact or account owner directly often works better. B2C customers tend to have cards that expire more often and read emails on phones, so the update path and mobile layout matter more. In both cases, the same principles apply: a calm first message, a one-click fix, and a clear deadline.

Can a cancellation flow replace dunning?

No. A cancellation flow addresses customers who choose to leave. Dunning addresses customers who still want the product but whose payment failed. A customer in a cancellation flow who has an open failed invoice still needs the payment handled, so the two programs should run side by side with separate reporting.

How do I know whether the dunning program is working?

Compare the recovery rate for emailed failed invoices against a holdout group over the same period, with the eligibility window and the decline reasons documented. Track time-to-recovery at the median and a high percentile, and track involuntary churn as a share of total churn. If the emailed group recovers more than the holdout and the gap holds across decline reasons, the program is contributing. If the gap disappears when you split by decline reason, the copy may not be the real driver, and retry timing or payment-method coverage may matter more.