A chargeback is not a complaint box; it is a regulated reversal mechanism with a closed list of valid reasons. When a filing doesn't fit those reasons, three things can happen beyond a simple denial. First, the merchant's representment evidence — delivery scans, usage logs, your own account history — proves the claim inaccurate, and the provisional credit is clawed back, sometimes with interest. Second, issuers track dispute behaviour: claims they judge to be first-party misuse (the industry's term is "friendly fraud") can lead to the card account being closed. Third, merchants and platforms react independently: accounts banned, balances withheld, and unpaid amounts sent to collections — our App Store guide documents how a single chargeback can restrict an entire Apple or Google account. None of this argues against disputing — genuine fraud, non-delivery and billing errors are exactly what the system is for. It argues for filing only when the facts fit.
The item arrived, as described, and you simply don't want it. There is no reason code for regret on any network — not Visa, Mastercard, Amex or Discover — because a change of mind is not a billing error, fraud, or merchant failure. Filed anyway (usually disguised as "not as described"), the merchant's listing + delivery records win, and the inaccurate claim is on your record. Instead: the return policy, a goodwill-refund ask, or reselling the item.
Deleting an app, removing a card from a wallet, or just stopping use does not cancel a subscription. The merchant's records show an active account, and "cancelled recurring" (Visa 13.2) requires an actual cancellation before the charge. The twin trap: cancelling properly, then continuing to use the service — the usage logs contradict the claim for those periods. Instead: cancel properly today, with a dated confirmation; ask for the unused final period back; any charge after that confirmation is a genuinely strong dispute.
Your child, partner or roommate used your card or your logged-in account. However unauthorized it felt, issuers generally treat household access as cardholder responsibility, and the evidence — your device, your address, your account — dismantles a fraud claim in representment. Insisting on the fraud framing after learning who did it is where account closures happen. Instead: the merchant's family/accidental-purchase refund (app stores and game platforms grant these far more readily than banks), then lock the card down with purchase approvals and alerts.
The merchant refunded you; you also disputed (or the dispute was already running). Two credits for one charge is double recovery. Issuers and merchants reconcile these routinely; the duplicate is reversed when found, and the overlap can be treated as misuse. Instead: if a refund lands while a dispute is open, notify the issuer the same day. If the merchant only promised a refund and the date passed with no credit, that's the opposite case — a strong "credit not processed" dispute (Visa 13.6 / Mastercard 4860).
Hotel and rental-car security deposits, fuel pre-authorizations, and pending duplicates are holds: they reduce available credit but are not posted charges, and they fall off on their own within days. There is nothing to dispute — issuers can't reverse a charge that doesn't exist yet — and filing noise disputes wastes your credibility for real ones. Instead: wait for posting; dispute only what actually posts, and only the part that's wrong.
The merchant approved your refund two days ago; card refunds can take a statement cycle to appear. Filing a "credit not processed" claim inside that window manufactures the double-dip in case 4 — the refund and the provisional credit collide, the merchant gets charged back for money already returned, and your account absorbs the mess. Instead: note the promised date, wait a reasonable processing window past it, then — if no credit has posted — file 13.6 with the promise attached. That patience is what makes the claim clean.
| Situation | File a chargeback? | The route that works |
|---|---|---|
| Changed my mind, item is fine | No | Return policy → goodwill ask → resell |
| Never cancelled the subscription | Not yet | Cancel with proof today; dispute only later charges |
| Kept using it after cancelling | Weak | Stop using it; dispute only unused post-cancellation periods |
| Family member bought it | Not as fraud | Merchant family-refund policy; platform refunds; card controls |
| Already refunded | No | Nothing owed — tell the issuer if a dispute is open |
| It's a pending hold | No | Wait for it to fall off or post |
| Refund promised, date passed, nothing posted | Yes | Visa 13.6 / Mastercard 4860 — promise + statement as evidence |
Unsure which side of the line your situation sits on? Run it through the Case Checker — it was built to say "don't file this one" when that's the honest answer.
Yes, in the misuse cases — filing claims you know are inaccurate (household purchases as stranger fraud, disputes after refunds) is first-party misuse, and issuers can close accounts over it. Honest disputes in genuine categories do not normally put an account at risk.
The merchant-side name for first-party misuse: disputing a charge you actually made or authorized — because you forgot it, regret it, or want to skip a return. Networks treat it as a policy violation even when the cardholder sees it as harmless.
No. That's double recovery; it is reversed when the overlap is found — and overlaps are reconciled routinely. If a refund lands after you filed, tell your issuer immediately.
Sources (verified October 21, 2026): Visa Core Rules Dispute Category 13 conditions (cancellation and credit-not-processed requirements) and Visa's published guidance on first-party misuse; Mastercard Chargeback Guide (4841 cancelled recurring, 4860 credit not processed); Fair Credit Billing Act, 15 U.S.C. § 1666 (definition of billing error — purchase regret is not one). Merchant and issuer enforcement practices vary.
