How to Appeal a Wrongful Claude Ban: A Step-by-Step Playbook

Thousands of paying Claude subscribers were banned by mistake in the July 2026 SEPA fraud wave. If you are one of them, an appeal is your first and best move — it is free, reversible, and the only path that restores your account with conversations and history intact. Here is the sequence that works, based on community reports from this wave and earlier ones.

Step 1: Confirm you were actually caught in the wave

Before writing anything, verify your situation matches the mass-ban pattern. Signs you were swept up rather than individually flagged: the ban arrived with no prior warning, you are a SEPA direct-debit subscriber (especially in Germany), the ban landed within the July 2026 window, and the notification email cites a generic terms violation rather than a specific action you took. Anthropic publicly confirmed on X that a SEPA fraud attack — randomly generated German IBANs exploiting direct-debit settlement lag — caused the wave and that legitimate subscribers were caught in the crossfire. If your case fits, you are appealing a false positive, not arguing about your conduct. That framing matters.

Step 2: Gather your evidence before contacting support

A documented appeal outperforms an emotional one. Collect four things before you open a ticket:

1. The billing email on the banned account.
2. The exact charge date and amount of your most recent payment, copied from your bank or card statement.
3. Proof the payment method is yours — a redacted bank statement line showing the debit works.
4. Your account usage context — roughly how long you have subscribed and what you use Claude for. Long-standing Max subscribers with months of clean billing history are the clearest false positives.

Step 3: File through the official channel, on one ticket

Contact Anthropic through the official support flow on claude.ai — the in-app help or the support form. Everything goes on one ticket. Duplicate tickets reset your queue position and split the paper trail a reviewer needs.

Structure the message in three short paragraphs: what happened (account banned without warning on this date), why it is a mistake (you are a paying SEPA subscriber caught in the acknowledged July 2026 mass ban wave — reference Anthropic's own public statement), and what you want (account restoration, plus a refund of the most recent charge if restoration takes time). Factual tone, no legal threats in the first message, no speculation about how the detection system works.

Step 4: Follow up correctly

Community reports from this wave suggest wrongfully banned subscribers who file polite, documented requests have a reasonable chance of restoration — but response times stretch during an active wave because support is processing thousands of similar cases. If you have not heard back after two weeks, send one polite follow-up on the same ticket. Do not open a new ticket, do not email multiple addresses in parallel, and do not post your case publicly expecting it to accelerate review — it does not.

Step 5: Know the parallel moves

While the appeal is in motion, you can note in the same ticket that you are requesting a refund of the most recent charge while the account is inaccessible — refund and appeal can ride together. What you should not do is initiate a chargeback or SEPA reversal while you still want the account back: a dispute on your billing record reads as a settled grievance and makes every later appeal conversation dramatically harder. Disputes are the last resort, not the opening move — our refund guide covers the full sequencing.

What not to do

Three mistakes kill otherwise winnable appeals. First, do not create a replacement account with the same payment method while the appeal is pending — pattern-matching fraud systems link them, and now you have two problems. Second, do not threaten chargebacks or regulators in your first message; it moves your ticket from "false positive to fix" to "hostile case to close." Third, do not fabricate anything — reviewers can see billing history, and a single false claim poisons the entire ticket.

A wrongful ban in a mass wave is a fixable error, and the fix is boring: one documented ticket, factual tone, patient follow-up. Save the escalation tools for when the boring path has genuinely failed.