Banned right after signing up: why a new account dies
Email verified, card charged, no prompt sent, account gone. Not luck: what gets judged is not how long the account lived, but whether the details at signup agree.
"Banned at signup" comes down to four signals — network and region at signup, payment instrument mismatch, device and browser environment, account-linking history — plus one clause in the terms: being physically located in an unsupported region is itself unsupported, whatever the account's age, ownership or payment. A new account is not an exception; it is when the least ambiguous information exists.
Which ban is it?
At least four situations get called an instant ban, and they are handled differently.
| What you see | What it most likely is | Any way back |
|---|---|---|
| No code arrives, or the code passes and the account is disabled at once | The number is flagged, or the signup environment fails | Essentially none |
| Asked for an ID or a face check, disabled after refusing or failing | The verification gate was not passed | Maybe still a channel |
| Payment succeeds, disabled minutes or days later | Payment and compliance verdicts disagree | Account unlikely; refund path exists |
| You can sign in, but features are limited or erroring | Maybe a risk-control downgrade or an outage | Usually recoverable |
The third row is the loudest complaint: the payment system accepted the transaction while the compliance system did not accept the account. The two never talk, so "paid and banned" is coherent. That is where the refund question starts.
The four signals
1. Network and region at signup
Which class the IP is — datacenter, residential, mobile — and which country it sits in, recorded the moment the form appears. Community reports describe a clear gap between datacenter and residential pass rates, and "IP in country A, billing address in country B" is the usual contradiction.
2. Payment instrument mismatch
Virtual or shared card BINs, a billing country that does not match the IP, one card behind several accounts. Community guidance marks the payment step high-risk: risk control may act on linked accounts, not only decline the charge. Declining is the payment side; closing the account is compliance.
3. Device and browser environment
Timezone, preferred language, regional formats, device fingerprint — do they agree with where the traffic exits? A new account is weakest here: a machine appearing for the first time, with no history to dilute it. See the consistency checklist.
4. Account-linking patterns
Numbers from SMS-verification services are reused heavily: how many registrations a number has served, whether it touched a violating account, is not yours to know. Community summaries rank it among the top reasons for a ban at registration — the number was already on a list and registering triggered it again. That has no official confirmation; it is a long-running user observation. The same applies to one card across accounts and to the linked-account record a retry leaves.
The terms layer
No detection is needed here; it is written in the terms. Three parallel conditions, any one of them is enough:
- Being physically located in an unsupported region, including personnel of otherwise supported entities;
- an entity incorporated or headquartered there;
- direct or indirect majority ownership by a person or entity there.
The first has nothing to do with account age. Being in an unsupported region at signup buys no buffer: signup is simply the point of least ambiguity, and the verdict arrives with the form.
A verification gate
From April 2026, technical community reports describe staged ID upload and live face checks for some users in some regions: failing or refusing them blocks every feature, and the page appears inside the signup flow. That would be a second explanation: stopped at the gate, not judged in violation. The first has no appeal value; the second still has a channel.
The first hour
- Identify which ban it is — read the message, look for a verification entry point, check whether you lost features rather than access.
- Do not open a new account on another machine straight away. Same root cause, same verdict, plus a linked-account record.
- If it was paid, pin the refund evidence down first — channel (web, iOS, Android), order number, payment time and sign-in status. Paths differ by channel: see the refund guide.
- Then decide on an appeal. The expected value for a new account is very low.
What not to do
- Do not pay for "recovery". The only route that overturns a verdict is the appeal, at about 10.5% overall; a new account is the class with the least material. A fee buys no channel that does not exist.
- Do not rebuild the same setup. Nothing changed, so the verdict does not change; you only add another linked account.
- Do not build a plan around the appeal. Write one if you like, then plan a route that works without the account.
Why appeals are a waste
Anthropic's transparency report, as relayed by several outlets: January to June 2026, roughly 11.4 million accounts banned, 398,000 appeals, about 42,000 successful — around 10.5%. What gets overturned usually has a long usage record, a clear payment history and a verifiable false positive; a new account has none of it.
Sources
Each claim is graded.
| Claim | Grade | Source |
|---|---|---|
| Unsupported regions include "persons physically located there" | Official terms | Anthropic Supported Regions Policy |
| H1 2026: about 11.4 million bans, 10.5% of appeals successful | Official report, relayed by press | ITHome report |
| Signup IP class, reused numbers and the payment step are high-risk | Community reports | "Your account has been disabled" guide |
| Some users asked for an ID plus a face check | Community reports, unconfirmed | Related community report |
"Community reports" rows reflect many users' experience, not official wording, and can lapse; "official terms" rows can be checked at the source.
Can an account banned right after signup still be saved?
Work out which ban it is first. If verification was incomplete or failed, a channel may still exist. If the terms decided it — physical presence in an unsupported region, say — an appeal has very little chance: about 10.5% overall, and a new account carries the least material.
Does registering again from a clean IP address help?
Rarely enough. Location, number history, payment and billing details and environment consistency are judged together. Change one, leave three contradictory, and the verdict does not move.
Why was the account disabled minutes after paying, with no explanation?
Payment and compliance are independent tracks. A successful payment means the channel accepted the transaction, not that the account passed the compliance judgement. That is why refunds are separate.