← Back home

Account health

The truth about account bans: patterns that trigger them

Bans feel sudden, but they almost never are. Here are the eight behaviour patterns that put verified accounts under review — and the steady habits that keep yours safe.

Business owner reviewing an account warning on a laptop

Why this guide exists

Most account bans are preventable. The owners who lose accounts are rarely the ones doing something obviously wrong — they are the ones who changed five things at once, moved too fast after a quiet period, or let small mismatches pile up until the platform's risk system could no longer tell them apart from abuse. This guide makes the patterns visible so you can avoid them on purpose.

A ban is usually the last step, not the first

When an account gets banned, the owner usually remembers one moment: the login that failed, the email that arrived, the dashboard that went grey. What they rarely see is everything that came before it. Platforms do not watch a single action in isolation. They watch patterns — sequences of small signals that, taken together, look like risk. A ban rarely arrives out of nowhere — it is usually the last step in a chain of small signals the platform has been counting.

That is actually good news. Patterns can be understood, and most of them can be avoided with ordinary, consistent habits. This guide walks through the patterns that most often lead to reviews and bans on verified accounts, explains why each one worries a risk team, and shows what steady, normal-looking behaviour looks like instead. Nothing here is a trick to fool a platform. It is the opposite: how to run an account the way a legitimate owner would, so the platform's own systems reach the right conclusion about you.

Pattern 1: Sudden location and device changes

The single most common trigger is a login that does not fit the account's history. An account that has always signed in from one city and one device suddenly appears on a new continent, on a new device, at an unusual hour. To a risk system, that looks exactly like a stolen account being opened by someone else — because that is what a stolen account looks like.

Travel, new phones and team members in other countries are all legitimate reasons for a location change, and platforms expect them. The problem is not the change itself; it is the change arriving with no context. Keep login locations as consistent as you can, use the same devices where possible, and when travel or a handover is planned, give the account a few days of normal activity first rather than changing everything at once. If a second person needs access, add them through the platform's own team or role features instead of handing over the main login.

Pattern 2: Velocity spikes — too much, too fast

Risk teams think in rates, not just totals. An account that has sent a handful of payments a week for months and then suddenly moves many times its usual volume in a single day is a classic review trigger, even if every payment is genuine. The same applies to new payees, new recipients and new transaction types appearing all at once.

The fix is pacing. When your business genuinely grows, let volume rise gradually and keep the shape of your activity recognisable: the same kinds of payments, to the same kinds of recipients, on a similar schedule. If a large, unusual transfer is coming, plan it in advance and keep the rest of your activity normal around it. A spike that follows months of steady behaviour reads very differently from a spike that is the account's first week of life.

Pattern 3: Identity details that stop matching

Verification is not a one-time event. Platforms re-check the details on file — names, addresses, tax IDs, business registrations — whenever something changes or whenever a review starts. When the name on a payout bank account does not match the account holder, when the business address changes three times in a month, or when a document on file has expired, the account looks like it is being passed between people.

Keep one consistent identity across everything tied to the account: the same legal name, the same address, the same tax details, the same payout destination. When something legitimately changes — a move, a new bank account, a company rename — update it in one place, keep the supporting document ready, and expect a short review while the platform confirms the change. Updating details calmly and completely is far safer than letting mismatches accumulate.

Pattern 4: Payment method churn

Adding and removing cards, banks and payout methods in quick succession is another strong signal. A legitimate owner usually settles on a payment setup and leaves it alone. Someone testing stolen cards, cycling through payout destinations, or trying to move funds before a review will swap methods constantly — and risk systems are tuned to notice exactly that.

Choose your payment methods deliberately, verify each one properly, and then leave them in place. If a card expires or a bank account closes, replace it once, verify it, and carry on. Avoid linking a method, unlinking it the same day, and linking another. Each change is a small event on its own; a cluster of them in a short window is what triggers a closer look.

Pattern 5: Automation and bot-like behaviour

Platforms can tell the difference between a person and a script, and they care about it. Logins at perfectly regular intervals, dozens of actions in a few seconds, copy-paste behaviour repeated hundreds of times, and sessions that never pause all look automated — and automated access is how most large-scale abuse is carried out. Even genuine business tools can trip this pattern if they hammer an account's interface instead of using the platform's official API or integrations.

Use the platform's own tools, integrations and APIs where they exist, and keep manual work human-paced. If you run a tool that touches the account, check that it respects rate limits and behaves like a person would. A short pause between actions is not inefficiency; it is what normal use looks like.

Pattern 6: Chargebacks, disputes and complaints

A chargeback is not just a refund by another name. To a platform, a chargeback says a customer went to their bank instead of to you — and a pattern of them says something is wrong with the product, the delivery or the communication. The same applies to disputes, abuse reports and complaints from other users. One is usually manageable. Several in a short period will put the account under review, and a sustained rate of them is one of the fastest routes to a ban.

The defence here is customer-facing, not technical. Clear descriptions, honest delivery times, fast replies to unhappy customers and a simple refund path of your own will prevent most disputes from ever reaching a bank. When a dispute does arrive, respond to it promptly and completely, with records. Platforms notice which sellers fight to keep customers happy and which ones leave buyers with no option but to escalate.

Pattern 7: Linked accounts that fall together

Platforms link accounts in ways owners often forget: the same device, the same IP address, the same payout bank, the same phone number, the same recovery email. When one account in a linked group is banned for abuse, the others are reviewed too — and if they share the same risky signals, they can fall together. This is why a single bad decision on one account can quietly endanger several.

Keep each account's footprint as separate as you reasonably can: its own device or browser profile, its own recovery email, its own payout destination. Never share credentials between accounts, and never use a banned account's device or payment method on a healthy one. If one account does run into trouble, stop and sort it out before the shared links pull others into the same review.

Pattern 8: Dormant, then suddenly very active

An account that sits untouched for months and then bursts into heavy activity is a familiar fraud pattern — it is what a purchased or hijacked dormant account looks like. Risk systems treat long silence followed by sudden volume with suspicion, even when the owner simply came back to an old account.

If you are returning to an account after a break, warm it up gradually: sign in from your usual device and location, check settings, make a small ordinary transaction, and build back to normal volume over days rather than hours. The same applies to a newly acquired verified account: its first days should be calm and ordinary, not a race to maximum volume. Patience in the first week is what keeps the account alive for the next year.

If your account gets flagged anyway

  • Stay calm and do not try to work around the restriction — creating a replacement account while one is under review usually makes things worse.
  • Read the platform's message carefully and answer exactly what it asks for, with the documents it requests, in the format it requests.
  • Gather your records before replying: proof of address, business registration, invoices, and a short, honest explanation of any unusual activity.
  • Keep your reply factual and short. Long, emotional appeals slow reviews down; clear documents speed them up.
  • Do not change the account's details, devices or payout methods while a review is open — every change during a review adds another signal for the reviewer to check.
  • If the review ends in a ban you believe is wrong, use the platform's formal appeal route once, with new evidence, rather than sending the same message repeatedly.

One identity

The same legal name, address and payout details everywhere the account touches.

Steady pace

Volume that grows gradually, in a shape the platform already recognises.

Few surprises

Changes planned one at a time, with documents ready and normal activity around them.

Keep your account in good standing

Every account in our catalog is verified and checked before handover. Ask us anything about keeping it healthy before you order.