Somewhere in your customer's past there is a Tuesday evening when they typed sixteen digits into your checkout, ticked a small box, and moved on with their life. They don't remember it. Months later a charge appears on their statement, and the story their mind tells is simple: I never agreed to this. They are not lying. They are misremembering, and that gap between what they did and what they recall is where a surprising number of disputes begin.

This is the saved card chargeback. The payment itself was real and often legitimate. What the bank wants to know is whether the customer authorized you to charge them without being there.

Why a saved card changes the question

When a customer sits at your checkout and pays, the transaction is customer-initiated. They are present, they press the button, and the evidence is simple: IP address, device, session, an order confirmation.

When you charge a stored card later, the customer is absent. In Stripe terms this is an off-session payment, and in card-network terms it is generally a merchant-initiated transaction. The customer has to have given you permission in advance, and the dispute turns on whether you can show that permission.

That is a different burden. You are not proving "this person bought something." You are proving "this person agreed, on a specific date, to let us charge this card again under these terms." Merchants who answer a saved-card dispute with proof of the original purchase alone often miss the point the reviewer is actually weighing.

Why customers forget they agreed

Psychology offers a useful explanation here. Memory researchers describe a process called source monitoring: we remember content far better than we remember where it came from or how we encountered it (Johnson, Hashtroudi and Lindsay, 1993). A customer may remember that they own a subscription yet have no memory of authorizing the recurring part. The fine print was processed in a few seconds, in a hurry, and never encoded as a decision.

So when the second or fourth charge arrives, it feels unauthorized because the authorization was never consciously stored. That doesn't make your claim weaker. It does mean your evidence must do the remembering for them.

What proves the permission

The strongest saved-card evidence reconstructs the moment of consent. Look for these pieces.

The consent language they saw. Card networks expect that a customer who agrees to have credentials stored is told what they're agreeing to: that the card will be saved, what it will be charged for, and roughly how often or when. A screenshot of the checkout or setup screen showing that wording, ideally with its date, is the centerpiece.

The record of the agreement itself. If you collected the card through Stripe's setup flow, a mandate or setup record tied to that payment method may exist, noting when and how the customer accepted. Pull it and cite it. If you used a checkbox, show that it was unchecked by default and that the customer had to act.

The first transaction. The initial, customer-present payment that saved the card is your anchor. Show its date, its approval signals such as a matching postal code or CVV check, and that it was not disputed.

A clean line to the later charge. Show that the disputed charge is consistent with what the customer agreed to: same amount or a stated range, same product, same schedule. If the amount differs from what the consent screen described, expect trouble.

Evidence the customer knew charges were happening. Receipts and renewal notices sent to the customer's email, plus any reply or login activity after the earlier charges, show that this was an ongoing, known relationship rather than a surprise.

The mismatch that sinks these disputes

The most common way to lose is a consent screen that doesn't match the charge. Suppose your checkout said "we'll save your card for faster checkout," and then you billed a recurring fee. To a reviewer, the customer agreed to convenience, not to a subscription. The permission has to cover what you actually did.

A second trap is time. If the card was saved two years ago for a one-off purchase and you charge it today for something new, the link between consent and charge is thin. A reviewer will ask why the customer would expect it.

A short example

Imagine a small design studio that sells a monthly asset library. A customer signs up in March, the card is saved, and billing continues. In August the customer disputes the charge as unrecognized.

A weak response says: "The customer purchased our product in March." A stronger one lays out the chronology: the signup screenshot showing the line "Your card will be charged $19 monthly until you cancel"; the March payment and its successful verification; the confirmation email sent that day; five consecutive monthly receipts sent to the same address; and login activity in July and August. Each item answers one question the reviewer would otherwise have to guess at.

Your next moves

  • Find your consent screen today. Open your checkout in an incognito window, walk through it as a new customer, and screenshot every step where card storage or recurring billing is mentioned. Save those with today's date in the filename.
  • Check what the wording actually says. Read it as a stranger would. Does it name the amount (or range), the frequency, and that the card will be charged without further action? If not, rewrite it this week.
  • Make the box an active choice. If consent currently relies on a pre-ticked box or a link to terms, switch to an unchecked box or explicit button text beside the price.
  • Locate the stored consent record for one real customer. Pick any subscriber in your Stripe dashboard and find the payment method, setup record and first payment. If you can't trace consent in under two minutes, you won't manage it under deadline either.
  • Send a receipt on every off-session charge. Turn on customer emails for successful payments, so the customer has a dated, delivered notice for each charge before any dispute.

Where the evidence quietly goes missing

Consent screens change. A designer tweaks the checkout, a developer ships a new flow, and six months later nobody can show what the customer saw on the day they signed up. Keeping dated snapshots of each version of your signup flow is dull work, and it is exactly the work that decides these cases.

How Argeback fits in

A saved-card dispute rewards the merchant who can assemble consent, first payment, receipts and activity into one clear chronology, and who does it before the seven-day clock runs out. Argeback pulls the dispute and the related payment history from Stripe, drafts the response around that chain of permission, and lets you review and file it from your phone. If you'd like to see how that looks on a real dispute, you can find it at https://argeback.lumenlabs.works.