Running it

Read, wait, appeal once, calmly

An angry appeal is filed by a person and read by a queue.

By Updated 5 min readRunning it

Guides on Running it: The admin that turns income into a trade

The first hour after a suspension notice is when the recoverable cases get made unrecoverable. Read the notice properly, wait until you are calm, appeal once with the specific information requested, and do nothing else - no second account, no support tickets in three channels, no public complaint.

The appeal is a form-processing exercise, not a persuasion exercise, and treating it as the second thing is what loses it.

Read what the notice actually says

Suspension notices are vague by design, and they are usually less vague than they first appear.

Three distinctions decide everything that follows.

Suspended, restricted or under review. A review with payouts paused is routine and frequently resolves in days. A termination notice is a different document with different language, usually citing a specific term.

Whether it names a clause. A cited clause tells you which queue is handling it and what evidence would answer it. An uncited "violation of our terms" usually means an automated flag that a human has not looked at yet.

In the EU, Regulation (EU) 2019/1150 obliges platforms to give business users a statement of reasons for a restriction or suspension, and the opportunity to clarify the facts through internal complaint-handling, so a notice with no reason at all is itself something to query.

Whether it asks for something. If the notice requests a document, the entire appeal is supplying that document promptly and correctly. People routinely write three paragraphs of context and attach nothing.

What usually triggers a review

Most suspensions are not judgements about your work. They are the output of a monitoring system reacting to a pattern, and the common patterns are dull.

A verification document that expired, failed a check, or does not match the payout name. A sudden change in login country or device, which is what a holiday looks like to a fraud model. Payout details changed shortly after a login from somewhere new. A concentration of disputes or refunds in a short window. A buyer report, sometimes malicious, sometimes a misunderstanding. Messages containing contact details or payment terms, which is why the off-platform conversation is worth declining in writing rather than ignoring.

The single most common one is the first. Identity and payment checks are re-run periodically rather than once, so an account that has worked for a year can trip a check on a Tuesday with no behaviour change at all - what verification involves and how often it recurs is worth knowing before it happens rather than after.

Writing the one appeal

Assume the reader has your account open, thirty seconds, and no memory of you.

Open with the account identifier and the notice reference, not with your situation. State in one sentence what you believe triggered it. Supply exactly what was asked for, correctly formatted, attached. If a clause was cited, address that clause specifically and nothing else. End with the outcome you are asking for.

Then stop.

Do not appeal a second time before the stated response window elapses. Duplicate appeals are frequently handled by resetting the queue position, so the reward for chasing is a longer wait. Do not open a parallel ticket through a different channel; the same thing happens. Do not describe how much this income matters to you, which is true and has no bearing on the decision.

Above all, do not create a second account. Evading a suspension converts a reviewable decision into a permanent one, and platforms detect it easily because they are looking for exactly that.

The tone that works is the tone of a chronology. It is the same discipline that decides what evidence carries weight in a dispute: quoted facts with dates, nothing characterised, nothing argued.

The money, and the timeline

Balances are usually frozen during a review and released on resolution, though not always on the schedule you would like. If the outcome is termination, funds are typically still owed to you and paid after any dispute window closes, which can be months rather than weeks. Stripe's documentation of how disputes work puts the usual card window at 120 days from payment, and a contested dispute at two to three months from start to decision. Withdrawal minimums keep applying to that balance, which is one more reason a high threshold is expensive - trapped float is unpleasant when the account works and worse when it does not.

Expect days for routine verification cases and weeks for anything involving a human decision. Plan around the longer number.

Preparing before it happens

Nothing here can be assembled after the login stops working, which is the whole point.

Keep a current export of payout history, order history and your reviews, refreshed occasionally. Keep verification documents current rather than valid-for-now, and keep the payout name matched to the account name. Keep enough of a buffer that a month of frozen funds is inconvenient rather than serious. Read the prohibited-conduct terms once, properly - before, not after - because the honest mistake and the deliberate breach look identical from the inside of a review queue. Rate Cock's judges page is where the current account requirements for that platform are set out, and every platform states its own equivalent.

And accept the structural point rather than arguing with it. Suspension does not have to be deserved to be total, appeal processes are slow everywhere, and the only real mitigation is that not all of your income and none of your evidence lives in one company's database - account risk and a reputation that survives a platform are the two posts that follow from that.

Two observations from the wider network make the monitoring easier to read without taking it personally. The reason these systems are strict about who is depicted and who agreed is not commercial caution, and the account of image handling and consent is the clearest general statement of the standard every platform in this sector is trying to enforce. The retention and storage practices that sit behind verification are documented on the automated side, and what services keep and for how long explains why a check can recur long after you thought it was settled. The same instinct shows up wherever a claim has to be defensible rather than merely plausible, which is what the measurement side's documented conditions are for.

Most suspensions resolve. The ones that do not are usually made permanent by something the account holder did in the first hour, which is the only part of this you control.

Read next

Full archive