Why subscription payments fail
A subscription payment rarely fails because the customer refuses to pay. The usual causes are an expired or replaced card, an exceeded card limit, insufficient funds for a direct debit, a revoked SEPA mandate, a mistyped IBAN or a bank declining the charge on suspicion of fraud. From the customer’s point of view nothing has happened; they learn about the problem from your message.
The first distinction in subscription dunning is therefore between a temporary decline, where a retry has a real chance (limit, funds, technical error), and a permanent decline, where only a new payment method will help (card blocked, mandate revoked, account closed). Payment providers return this decline reason. If you evaluate it, you retry only where it pays off and otherwise ask for an update straight away.
Unhandled payment failures are one of the biggest causes of churn in subscription businesses, even though the customer wanted to keep using the service. An orderly sequence of retries, reminders and a clear suspension rule recovers most of these payments.
How many payment retries make sense?
The answer depends on the payment method:
- Credit and debit cards: three to four attempts over two to three weeks are common. Do not retry daily; leave two to four days between attempts and place one attempt in the days after the start of the month, when salaries have arrived. After a permanent decline every further attempt is wasted; ask for a new card immediately.
- SEPA direct debit: every returned debit costs bank fees, for you and often for the customer. Allow at most one second collection, and only after announcing date and amount. If that fails too, switch to an invoice payable by bank transfer. After a mandate has been revoked you must not collect again.
- Invoice by bank transfer: there is no retry here, only the regular dunning process with dunning levels and deadlines.
Also check what your payment provider already does. Providers such as Stripe, Mollie or Adyen retry failed card payments several times over roughly two to three weeks by default. If you run your own retry logic on top, you charge the card twice as often and create declines that would not exist otherwise.
How far apart should reminders be? A 30-day schedule
This schedule works well for monthly subscriptions. Days count from the first failed payment:
- Day 0 – payment failed: send a factual message immediately with the reason, the amount and a link that lets the customer update the payment method without logging in. No dunning letter yet, no fee.
- Day 3 – second attempt: automatic retry, followed by a second message if it fails. Now state what happens if no payment arrives by day 14.
- Day 7 – third attempt: retry, then announce the restriction with a specific date.
- Day 14 – restriction and final reminder: access is restricted, for example to read-only or basic functions. This message is the first real dunning notice with a payment deadline, usually seven days.
- Day 21 to 30 – suspension: access is suspended, data is kept. The receivable remains and is pursued like any other open invoice.
- Day 30 to 60 – cancellation or handover: you terminate the contract under your terms or hand the receivable to regular dunning or a collection agency. What follows is described in what happens after the final reminder.
For annual subscriptions and larger amounts the intervals get longer; for business customers invoiced by bank transfer the dunning-level schedule applies instead of this grid.
When should access be suspended for good?
Legally, suspension rests on the principle that you may withhold your service while the customer withholds payment. In practice four conditions apply:
- Suspension is covered by your terms. The customer must know at signup that and when access can be restricted.
- It was announced. A suspension without prior notice and deadline is open to challenge and annoys customers who were willing to pay.
- It is proportionate. A small arrear does not justify a full lockout with data loss. Use stages: notice, restricted functions, suspension.
- The claim is undisputed. If the customer has a legitimate complaint, suspension is not a lever.
Ending the contract altogether is termination for cause. For ongoing contracts under German law this usually requires an unsuccessful deadline first, which is exactly what the schedule above provides. Telecommunications and energy supply have their own statutory rules on minimum arrears and notice periods; for software, memberships and other subscriptions it comes down to contract and proportionality.
Good practice: do not delete customer data at suspension, only after termination and the retention period stated in your terms. Reactivation should take a single payment.
A retry is not a dunning notice
A retry is a technical act: you charge the stored payment method again. A dunning notice is a legal demand for payment. Only the notice puts the customer in default, and only from then on can default interest and dunning fees be considered. Which fees are permitted in Germany is explained in the guide on dunning fees and default interest.
So do not turn every notification into a dunning letter. The messages on day 0, 3 and 7 are service information. The message on day 14 is the first dunning notice, and its subject line should say so. This separation keeps the tone friendly for the first two weeks and makes the later escalation credible.
Channels: email, in-app, SMS and letter
- Email is the default for every step and sufficient for small amounts.
- In-app notices are the most effective channel because the customer sees them at the next login. A banner with a link to the payment method settles many cases without another message.
- SMS suits short deadline reminders before suspension but requires consent for that purpose.
- Letters are reserved for the final reminder on larger amounts and business customers, because delivery can be proven.
- Phone calls pay off for annual contracts and high amounts; often one call is enough.
Common mistakes in subscription dunning
- Several collection attempts on the same day, generating fees and declines.
- Messages without a direct link to update the payment method.
- Suspension without notice, or despite a bank transfer that has arrived but has not been matched yet. Automatic payment matching prevents this.
- Billing suspended periods in which the customer could not use the service, without the terms providing for it.
- Passing on flat returned-debit fees without evidence of the actual cost.
- No ending: accounts that stay suspended for months but are never terminated or dunned.
Where acucollect fits in
Card retries are handled by your payment provider. acucollect, the receivables management software by RLOX (product page in German), starts where subscriptions are billed by invoice: maintenance contracts, software for business customers, membership fees and direct debits that end up as an invoice.
- Invoices come from Lexware Office, sevDesk or Odoo; acucollect runs the dunning levels with texts, deadlines and fees per level.
- Payment matching prevents a customer who has since paid by transfer from being dunned or suspended.
- A dunning block per customer pauses the sequence while a complaint or instalment agreement is pending.
- Approval before sending ensures that the final reminder and the handover to collection are triggered deliberately.
How such a recurring process is structured is described in the guide on the dunning run.
