A customer opens their bank app on a Sunday night, scrolls through the month, and sees your company's name twice. Same amount. Eleven days apart. Their stomach drops the way it does when you find something that looks like a mistake with your money in it. They don't email you. They tap "dispute." By the time you hear about it, the story is already written: they charged me twice.

Sometimes that story is true. Sometimes it's the most honest-feeling false statement a person can make.

The second charge belongs to a second account. Months ago, on a different day, with a different email, the same person signed up again. They forgot, or they never connected the two events in the first place. Now you're holding a dispute that says "duplicate," and the truth is more tangled than either word suggests.

Why a second account feels like a billing error

People are poor at remembering where a memory came from. Psychologists call this source monitoring: the mental work of tracking whether you did something, imagined it, or only intended it. When it slips, you can hold a real memory with the wrong context attached.

Apply that to a signup. The customer remembers subscribing to your product. They don't remember subscribing twice. The first signup was on a laptop at work, with a work email. The second was on a phone, three months later, after a link in a newsletter, with a personal Gmail. To them there is one relationship with your product. Two charges look like a glitch on your side, not a second decision on theirs.

Recurring billing makes this worse. A charge that repeats quietly stops feeling like a decision at all. The customer isn't lying when they say "I only signed up once." They're reporting what they remember, and what they remember is incomplete.

That matters for how you write the response. If you treat them as a fraudster, you'll sound wrong to a reviewer who can see an honest confusion. Your job is to lay the two decisions side by side, calmly, and let the record show what happened.

First, find out if you actually double-billed them

Before you build a case, check whether the customer is right. Some of these disputes deserve to be lost, and the fastest way to lose credibility is to defend a real error.

Stripe has a dedicated dispute reason called "duplicate." When it's the reason on your dispute, the evidence fields Stripe provides include the ID of the other charge you believe is the original and an explanation of why the two are separate. That structure tells you what the reviewer wants answered: are these two charges for the same thing, or two different things?

Pull both charges and ask four plain questions:

  • Do they attach to the same Stripe customer, or to two different customer objects?
  • Do they cover the same product and the same billing period?
  • Was the second charge created by a retry, a webhook that fired twice, or a checkout the customer submitted again?
  • Was a second subscription created on the same customer by a double-click or a failed redirect?

If the answer to the last two is yes, you made a mistake. Refund it, thank them, and let the dispute go. Fighting it risks a loss and costs you the goodwill of someone who was right.

If the charges sit on two separate customer records, cover two separate accounts, and each was started by a deliberate act, you have something worth defending.

What makes two accounts count as two purchases

The reviewer is reading for one thing: is this one purchase charged twice, or two real purchases? Your evidence should make the second reading obvious.

Two distinct signup events. Show the creation timestamp of each account, the email on each, and the signup source if you track it. Two dates, weeks or months apart, are hard to explain as a glitch.

Two separate acts of consent. If each signup involved a checkout page with the price and terms, include a record of both. Consent given once doesn't cover a second charge. Consent given twice is two purchases.

Evidence the same person did both. This is the link that turns "someone else's account" into "your account, the one you forgot." Matching device, matching IP range, the same card fingerprint, or a shared billing name can tie the two together. Be careful about how much weight you put on any single signal. An IP address is circumstantial, and a shared household or office can share one. Use these as corroboration, not as the headline.

Activity on the second account. This is the strongest piece. If the second account has logins, usage, files created, or messages sent, the customer was using the thing they say they never bought. Dated activity is difficult to reconcile with "I didn't know about this."

Proof the customer received the receipts. Each charge likely triggered a receipt or invoice email. Show that the second one was sent to the address on that account and, if you can, that it wasn't bounced.

Lay it out as a comparison, not an accusation

A good response here reads like a side-by-side. Two columns, if your format allows it, or two short paragraphs with the same structure: account created on this date with this email, charged this amount on this date, active on these days.

Then one calm sentence about what happened: "These are two separate accounts, created on [date] and [date], each with its own signup, payment authorization, and usage. This is not a repeated charge for a single purchase."

Resist the urge to explain how the customer must have forgotten. The reviewer will draw that conclusion. Speculating about their memory sounds like blame, and it hands the reviewer a reason to side with the cardholder.

Keep it short. A tight, readable packet beats a pile of exports, which is a lesson that applies to every dispute you respond to.

Your next moves

  • Search your database for duplicate customers today. Query for accounts sharing a card fingerprint, billing name, or similar email patterns (for example, a work and a personal address). Knowing how often this happens tells you whether it's a one-off or a pattern.
  • Check your last 90 days of Stripe charges for true duplicates. Look for two charges on the same customer within a short window with the same amount. Fix any real double-billing before a customer finds it for you.
  • Add a warning at signup. If someone enters an email or card that already matches an active subscription, show a plain message: "It looks like you already have an account. Want to log in instead?" This prevents the second account and the dispute.
  • Send a "you have two active subscriptions" email. When your system detects two active paid accounts tied to one card, email the customer and offer to cancel one. A customer who is told is a customer who doesn't dispute.
  • Build a two-account evidence template. Prepare a one-page layout with slots for both signup dates, both emails, both receipts, and activity on each. When the dispute arrives, you fill it in rather than starting from scratch.

Where this leaves you

The hardest part of a duplicate account dispute isn't the evidence. It's holding two ideas at once: the customer is probably sincere, and the charge is probably legitimate. You don't have to choose between them. The records can be kind to the person and still clear on what they bought.

This is the sort of dispute that slips past deadlines because it takes real digging across two accounts. Argeback is built for that moment: it pulls the disputed charge into one place, drafts an evidence-backed response from your records, and files it before the 7-day deadline, all from your phone. If you'd like to see how it handles a messy case like this one, you can look around at argeback.lumenlabs.works.