Somewhere in a drawer, or a wallet, or a trash can, there is a cut-up debit card. The person who cut it up felt something small and satisfying when they did it: a door closing. New number, new expiry, fresh start after the fraud scare or the lost wallet or the bank's cheerful letter. Three weeks later they open their statement and see your name next to a charge, on the new card. And their stomach drops, because in their mind that card has never been to your website.

They did not give you the new number. You never asked for it. So how could you possibly have charged it?

This is one of the quieter ways a subscription chargeback is born, and it is easy to lose if you answer it the way most merchants do: with a bare "the customer authorized this." The customer will say they did not. And in their own experience, they are telling the truth.

Why a replaced card feels like a reset

People carry a mental model of payments that is tied to the physical object. The card is the contract. Cancel the card, and every promise attached to it dissolves. Researchers who study how people sort their money call this kind of sorting mental accounting: we file spending into categories and treat each one as a closed ledger. A card that has been destroyed feels like a ledger that has been closed.

But recurring billing does not work that way. The agreement the customer made was with you, not with a piece of plastic. When their bank reissues a card, card networks run account-updater programs that pass the new number and expiry to participating merchants and processors, so that legitimate subscriptions don't fail for no reason. Stripe describes this as automatic card updates, and when it happens, the payment method on file is updated and an event is recorded. The customer never sees any of it. The first they hear is the charge.

That gap, between a system working as designed and a human experiencing a breach, is exactly where the dispute lives. The customer is not lying. They simply never learned that the subscription had been carried over.

What the dispute usually looks like

Expect one of two framings. The first is fraud: "I never gave this merchant my new card." The second is a cancelled recurring payment: "I closed that card, so I cancelled." On Visa, the recurring-cancellation family is the 13.2 reason code; on Mastercard, it is 4841. The wording differs, but the question the reviewer is really answering is the same: did this person have an ongoing agreement with the merchant, and were they still using what they were paying for?

Notice what the reviewer is not asking. They are not asking whether the card number matches the one used at signup. It will not. That mismatch is the customer's whole case, and it is the first thing you should defuse.

The argument that actually wins

Your thesis is a continuity story: the same person, the same account, the same product, one unbroken relationship, with only the plastic changing. Every piece of evidence should serve that single claim.

Start with the original authorization. The signup or checkout record, showing the customer accepted recurring billing, with the terms they saw and the timestamp. This is the foundation, and it is the reason a new card number doesn't void anything.

Next, show the card update itself. In Stripe, an automatic update is logged against the payment method, and there is a corresponding webhook event for it (payment_method.automatically_updated). Screenshot the payment method history or the event so the reviewer can see that the number changed through the network's updater and not through anything suspicious on your side. Explain it in one plain sentence: the card's issuer supplied the updated details through the card network's update service.

Then prove the person never left. This is the most persuasive layer and the one merchants most often skip. Login records after the card change. Files downloaded. Features used. Support tickets opened. If the customer used your product last Tuesday and disputed on Friday, "I closed that account" becomes very hard to believe. Match the identifying details where you can: same email, same IP region, same device, same name and billing postcode as the earlier payments.

Finally, show the history of undisputed payments. Months of successful charges on the old card, with no objection, establish the pattern. The reviewer sees a customer who paid, used the product, and paid again.

The pre-dispute notice that quietly does the heavy lifting

Here is the evidence that separates merchants who win these from merchants who don't: a renewal reminder that was sent before the charge. An email that says "your subscription renews on the 14th for this amount" is dated proof that the customer had a chance to cancel and was told what was coming. If it names the card by last four digits, even better, because it shows you sent it to a person who could have noticed that the card was new.

If you didn't send one, that is not fatal, but it is the lesson. Some card networks and regions require advance notice for certain recurring charges anyway, so a reminder is worth building regardless of any one dispute. Check the rules that apply to your market and billing model rather than assuming.

Be honest about when the customer has a point

Not every one of these is a win, and pretending otherwise wastes your time. Consider walking away or refunding when:

  • The customer asked you to cancel before the card changed, and you have a message proving it.
  • There is no usage at all after the update, and the previous months show a pattern of non-use.
  • Your records do not clearly show a recurring-billing agreement from the start.

In those cases a quick refund is cheaper than a lost dispute, and a lost dispute still costs the fee. Fighting should be reserved for situations where your evidence tells the same story the customer's own behavior tells.

Your next moves

  • Pull the payment method history for this customer today. Find the date the card changed and confirm whether it was an automatic update. Screenshot that record next to the disputed charge.
  • Export their activity after the update date. Logins, downloads, API calls, anything with a timestamp. Even two or three events after the card change are enough to anchor your continuity story.
  • Find the original recurring-billing consent. The checkout page, the terms version, the timestamp. Put it first in your evidence, before the dispute is even discussed.
  • Look for any renewal reminder you sent. If one exists, include it with the send date. If none exists, set up a reminder email for every renewal this week so the next dispute starts stronger.
  • Add one sentence to your rebuttal explaining automatic card updates. Reviewers see a different card number and assume the worst. One plain line (the issuer provided updated details through the network's update service) prevents that.

What the customer is really saying

Underneath the dispute, the customer is saying something modest: I thought this was over. They did not rehearse a lie; they acted on a reasonable-feeling belief that a destroyed card ends its obligations. Treating it that way, as a gap in what they knew and not a betrayal, keeps your tone steady and your rebuttal factual. Reviewers respond to calm timelines far better than to indignation.

This is also a case where the facts are scattered: a payment method log in one place, usage data in another, an email in a third. Argeback pulls a dispute's evidence together, drafts a response that tells the continuity story in order, and files it before the seven-day deadline, which you can review and send from your phone. If a replaced card has ever turned a loyal subscriber into a dispute, it's worth seeing how little time the response needs once the records are already assembled: https://argeback.lumenlabs.works