A signal service signs up 400 subscribers in a quarter. Month two, the renewal run goes out and a chunk of it fails. Support fills with people saying they were charged twice, people saying they cancelled, and people who genuinely do not recognise a charge from a company whose descriptor reads as an eight letter abbreviation of a holding entity in another country. Six weeks later the acquirer sends a note about the dispute ratio.
None of that is a payments problem in the abstract sense. Each piece has a specific cause and a specific fix.
The first charge and every charge after it are different transactions
When a customer types a card number into a checkout, that is a customer initiated transaction. The cardholder is present, they can be challenged by their bank, and the issuer treats the whole thing as consented in the moment. When your system charges the same stored card on the fifth of next month, nobody is present. That is a merchant initiated transaction, and it has to be submitted with flags that say so.
Two data points ride along. The stored credential indicator tells the issuer the card was saved with the customer's agreement. The scheme transaction identifier from the original authorisation links the renewal back to the moment consent was given. Send a renewal without either and it looks to the issuer like an unauthenticated card not present charge on a card whose owner is asleep, which is exactly the profile their fraud model is built to decline. A large share of what firms call renewal churn is this, and it shows up directly in approval rates.
The same flags carry the European authentication treatment. The mandate is authenticated once at setup through 3D Secure, and correctly flagged fixed amount renewals afterwards fall outside the challenge requirement. Change the amount or the billing interval in a way the customer did not agree to and you are back to needing fresh authentication.
Cards move, subscriptions should follow
Cards expire, get reissued after a fraud event, or are replaced when a customer switches bank. Nobody emails their signal provider about it. Card account updater services, offered by the schemes through most acquirers, push the new expiry or new card number to the merchant of record so the subscription keeps running. Network tokens do something similar by design, since the token stays valid across a reissue.
Without either, a business loses a slice of its book every month for reasons that have nothing to do with whether customers still want the product. If your payment provider does not offer updater coverage on your card mix, that belongs in the same evaluation as pricing when you pick a provider.
Where subscription disputes actually come from
| What the customer says | Real cause | Fix |
|---|---|---|
| I do not recognise this charge | Descriptor shows a legal entity name nobody has seen | Trading brand plus a support contact in the descriptor |
| I cancelled this weeks ago | Cancellation buried behind an email request | Self service cancel button inside the account |
| I did not know it would renew | Silent renewal after a trial or a first month offer | Renewal notice sent before the charge |
| It did not work as promised | Marketing implied outcomes the service cannot deliver | Rewrite the offer page and the refund terms |
Only the last row is a product argument. The other three are operational, and they are the majority. Card scheme rules for subscription merchants have moved steadily in the same direction over recent years: clearer descriptors, a reminder before a trial converts, and a cancellation path as easy as the sign up path. Following those rules is cheaper than fighting the disputes they prevent, and it is separate from the harder question of customers who dispute in bad faith.
A subscription business is judged on its dispute ratio, not its dispute count. Growth hides the problem for one quarter and then makes it worse, because the ratio is measured against a month of sales that has already stopped growing.
Dunning: retry like an accountant, not like a bot
When a renewal fails, the response code tells you whether retrying is sensible. A hard decline, such as a closed account or a card reported stolen, will never succeed and retrying it repeatedly can count against your account with the acquirer. A soft decline, such as insufficient funds or an issuer timeout, is worth a retry on a schedule spread over days rather than hours, and spacing attempts around a typical payday improves the outcome without any technical change at all.
Pair the retries with a message the customer will actually read, containing the amount, the date of the next attempt and a link to update the card. A dunning sequence that runs silently and then cancels the account teaches the customer nothing except that the service stopped working. Where a firm sells subscriptions next to trading accounts, the billing state belongs in the same record support already has open, which is one of the reasons subscription handling sits inside the client CRM rather than in an isolated billing tool.
What to write down before you launch
Set the renewal date rule and the proration rule in writing, decide what happens to access on the day of a failed payment, and publish refund terms that match what your support team will actually do at 2am when a customer is upset. Keep the audit trail: consent timestamp, IP, the terms version accepted, every renewal attempt and its response code. That file is what wins a representment when a dispute does come, and it is the same evidence pack described in the guide to how chargebacks work.
"Half the subscription disputes I have seen were solved by changing the billing descriptor. It costs one email to the acquirer and it saves an argument every single month."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- Renewals must carry the stored credential flag and the original transaction identifier or issuers decline them.
- Account updater services and network tokens keep subscriptions alive through card reissues.
- Unrecognised descriptors and silent renewals cause more disputes than card fraud does.
- Retry soft declines on a spread schedule, never hard declines, and tell the customer each time.
Frequently Asked Questions
Why do renewals get declined when the first payment went through?
Usually because the stored card has expired or been reissued, or because the renewal was submitted without the stored credential and merchant initiated flags that tell the issuer this is an agreed subscription rather than a fresh unauthenticated charge. Card account updater services and correct transaction flagging fix most of it.
Do recurring payments need 3D Secure every time?
Under European strong customer authentication rules the first transaction that sets up the mandate is authenticated, and later merchant initiated renewals of the same fixed amount can be submitted without a challenge when they are flagged correctly. If the amount or the schedule changes materially, the customer normally has to authenticate again.
What is the fastest way to cut subscription chargebacks?
Fix the billing descriptor so it carries the brand the customer recognises and a support contact, then send a renewal notice a few days before each charge. Unrecognised charges and surprise renewals cause more disputes at signal and subscription businesses than genuine card fraud does.