FunPay Seller Rules: What Gets You Banned and the Risks Involved
A FunPay ban is rarely a surprise — it almost always fits one of a small number of repeating categories. This article breaks down the mechanics of enforcement: which actions the platform treats as violations, how game publishers' own terms of service layer on top of marketplace rules, and what you can practically do to keep a seller account alive. No easy-money promises, and no quoting of exact policy wording — that text changes, and you should verify it at the source.
This builds on our base guide to selling on FunPay, focusing specifically on the risk side.
Why blocks happen at all
A marketplace's economics rest on buyers trusting the platform rather than any individual seller. The guarantor system — where funds are held until the buyer confirms receipt — is FunPay's product. Anything that undermines that mechanism has to be enforced hard, because otherwise the platform has no reason to exist.
That explains the shape of enforcement: the harshest penalties target behaviour that removes a deal from the platform's control, or that systematically creates risk for buyers — not merely "bad products". Understanding that principle lets you predict what will count as a violation even for a clause you have not read.
Category 1: off-platform deals
The most common way a new seller loses an account is offering direct payment. It can look harmless: the buyer asks for a discount, the seller offers a card transfer to skip the fee. Or the conversation drifts into a messenger because "it's easier to confirm the nickname there".
What falls under this:
- Directly offering payment outside the guarantor — card, wallet, crypto.
- Sharing messenger contacts to continue the deal elsewhere.
- Hints and euphemisms — detection is not limited to explicit phrasing.
- Links to your own site or Telegram bot in chat or in a listing description.
Critically: the buyer's initiative does not protect the seller. Even if the client proposed going off-platform, responsibility sits with the account that agreed. The correct response is a polite refusal inside the platform chat, so the refusal itself stays in the log.
Category 2: prohibited and high-risk goods
Every marketplace maintains a list of categories it will not service — because of payment-provider requirements, rights-holder pressure, or an unmanageable dispute rate. Read the actual rules for the exact list, but the filter's logic is predictable. Bans or hard limits usually cover anything that:
- breaches a game's terms of service so plainly that the publisher will reverse the transaction;
- involves transferring access the publisher considers non-transferable;
- relates to software providing unfair advantage;
- cannot be verified by the guarantor in principle.
How publisher rules interact
The second layer is the game companies' own ToS. A publisher may prohibit account transfers, currency purchased from unauthorised sellers, or real-money item trading. FunPay may technically let you post the listing, but when the publisher mass-bans buyer accounts or reverses balances, the dispute reaches you.
The practical takeaway: check both rule sets before launching a category. A category the marketplace formally permits can still be economically unprofitable because of the reversal rate on the game's side. That mechanism is covered in depth in our piece on the risks of reselling digital codes.
Category 3: description does not match the goods
A listing description is an offer. If the buyer received something other than what they read, they are right by default, and the platform will almost always side with them.
Typical mismatches:
| What was promised | What the buyer got | Outcome |
|---|---|---|
| Global key | Region-restricted key | Dispute, refund, statistics hit |
| PC platform | Console version code | Refund, description complaint |
| Instant delivery | Manual delivery hours later | Timing dispute, rating drop |
| New account | Account with history and linked services | Complaint, publisher reversal risk |
Region, platform, activation window, delivery method and any restrictions belong in the description explicitly. That is not just ban protection — it is the best filter against the wrong buyers. A client who read the region restriction and bought anyway almost never disputes. The mechanics of those restrictions are covered in region-locked keys explained.
Category 4: refunds and disputes as a trigger
Even when each individual dispute looks explainable, the share of them functions as an independent signal. Platforms look at statistics: a seller with a noticeably above-average rate of refunds, cancellations or support escalations gets flagged for manual review regardless of the merits of any single case.
Chargebacks are a separate problem — the buyer reverses the payment after receiving the goods. Here the seller loses twice, forfeiting both product and money, while the platform records a problem order. Mitigation tactics are covered in how to avoid chargebacks on digital goods.
Category 5: multi-accounting and evasion
A second account "just in case" is the most expensive mistake on this list. Platforms link accounts on a combination of signals: payment details, devices, network fingerprints, behavioural patterns, overlaps in chat history. A detected link usually means a restriction on one account propagates to all connected ones, turning a temporary measure permanent.
If you genuinely operate as a team and need multiple accounts, resolve that before you start and through the platform's own process — not after the fact.
Account hygiene: what to actually do
A short rule set that closes most of the exposure:
- Keep all communication in platform chat. No moving to messengers, even at the client's request.
- Describe listings precisely. Region, platform, delivery timing, restrictions — explicit and unambiguous.
- Deliver instantly wherever possible. The shorter the gap between payment and receipt, the fewer grounds for a dispute.
- Log every order. Delivery timestamp, code identifier, supplier confirmation — retained at least until the claim window closes.
- Use a verifiable supply source. Codes from opaque channels are deferred disputes.
- Run one account. No exceptions, no spare.
Where to source stock so disputes stay rare
A large share of blocks grows not from bad intent but from bad supply: a revoked code, a wrong-region key, delivery delayed by manual purchasing. FoxReload covers that side: a wholesale catalog of 900+ SKUs — game keys, gift cards, top-ups, subscriptions — a single REST API with instant delivery and SKUs with the region stated explicitly. When delivery is automated and every code's provenance is recorded, disputed orders drop sharply, and with them the reasons for anyone to review your account.
For formal supplier criteria, see how to verify a gift card supplier. For what to do once a dispute is already open, see the FunPay dispute playbook.
Bottom line
FunPay bans are predictable: they cluster around escaping the guarantor, prohibited categories, false descriptions, high refund rates and multi-accounting. A second layer — the publishers' own agreements — always sits on top of platform rules and cannot be ignored. Verify exact wording and the current list of grounds in FunPay's own rules before launching a category. Then build the operational side — supply source, delivery speed, log completeness — so a disputed order is the exception rather than the working background.