What You Are Allowed to Sell on Plati.market: categories, provenance and rules
The question of what you can sell on a digital storefront looks like a list, but in practice it behaves like a system of two independent layers of rules. Sellers who read only the marketplace policy lose listings on a regular basis, because the second layer lives in an entirely different document. Below is the mechanics: how these rules typically work, why the provenance of your codes matters more than the category label, and what you specifically need to verify yourself.
One disclaimer that matters for this article: no current category list is reproduced here. It changes, and any copy of the rules goes stale faster than it can be published. Everything below describes the logic by which such rules generally work on digital marketplaces. For the exact current requirements, read the platform's live rules and its seller help section.
Two layers of rules, not one
The first layer is the marketplace policy. It defines which categories may be listed at all, how a listing must be composed, what cannot be claimed in a description, and which delivery methods are acceptable. Breaches are visible to moderation and typically lead to listing removal or account restrictions.
The second layer is the publisher or platform terms of service attached to the product itself. Licence agreements from game platforms, gift-card issuers and software vendors carry their own restrictions: on commercial resale, on activation region, on transferring a code to a third party, on the use of service accounts.
The conclusion that costs money: these two layers are not synchronised. A product can be fully compliant with the storefront policy and simultaneously violate the publisher terms. In that case the marketplace will usually accept the rightsholder complaint and pull the listing — not because you broke its rules, but because arguing with a rightsholder is not worth it for the platform. The legal side is covered separately in is it legal to resell game keys.
What usually passes without friction
On digital storefronts the core assortment normally lists without trouble, provided the seller has a transparent source and an accurate description:
- Game and DLC activation keys bought from authorised distributors, with the region stated explicitly.
- Gift cards and top-up codes for well-known services, where denomination and region match the description.
- In-game currency top-ups by account ID, delivered through a legitimate vendor channel.
- Software licences, where you hold a distribution right.
- Service subscriptions for which the vendor itself supports a reseller model.
What these have in common is not the category but two conditions: known provenance and a description that does not mislead the buyer. Those two, not the category label, determine whether the listing has a long life.
Categories that always draw more scrutiny
Some goods may be formally permitted yet live under constant risk. Typical markers of elevated scrutiny:
- Region-restricted products sold outside their region. Even when the storefront allows it, the platform terms frequently do not. The mechanics are unpacked in region-locked keys explained.
- Accounts instead of codes. Selling account access is regulated more tightly almost everywhere than selling a key, because the account stays tied to its original owner.
- In-game services such as boosting, levelling and farming. These often breach the game's own rules even where the storefront tolerates the listing.
- Products priced far off the market. An abnormally low price is a provenance flag for moderation and for the rightsholder alike.
- Subscriptions bound to somebody else's payment profile. They work until the first card reissue.
What is typically restricted or prohibited
Industry-wide restrictions that appear on virtually every digital storefront: codes obtained fraudulently or with someone else's payment data; goods infringing third-party rights; anything involving circumvention of protection measures; material restricted by law; and the sale of other people's account credentials. This is not one platform's list — it is a class of prohibitions that is stable across the industry. Read the wording that actually applies to you in the platform's rules.
Category type versus typical treatment
| Product type | Typical treatment | What to verify before listing |
|---|---|---|
| Game key from an authorised channel | Usually acceptable | Activation region, supplier's distribution right |
| Key with unclear origin | High revocation risk | Batch paperwork, supplier reputation |
| Gift card from a known issuer | Usually acceptable | Region and denomination match the description |
| Top-up by account ID | Depends on the delivery channel | Whether the vendor permits a reseller model |
| Account access | Frequently restricted | Storefront rules and platform terms together |
| In-game services and boosting | Frequently restricted | The game's own rules, not just the storefront |
| Software licence | Depends on licence type | Licence type and whether resale is permitted |
This table describes typical logic, not any platform's current policy. Verify every row against the live rules before you launch a category.
Provenance: why it is the central question
Provenance is the answer to "where exactly did this code come from". It matters for three reasons at once.
Economic. A revoked key is paid for by the seller. The buyer gets a refund, the marketplace records a dispute, and the supplier from a random chat is unreachable by then. How this is handled operationally is covered in code revocation and region locks.
Reputational. The storefront ranks you on dispute and refund share. One bad batch degrades visibility for all your listings, including the clean ones.
Legal. When a rightsholder files, the first question is the supply chain. A seller who can produce purchase documents is in a fundamentally different position from one who can produce a screenshot of a transfer.
How a takedown on complaint actually unfolds
The mechanics are almost always the same, and it pays to understand them in advance.
- The approach comes from the rightsholder, not from a buyer — through a dedicated infringement channel rather than normal support.
- The platform acts pre-emptively. The listing is usually hidden or blocked immediately, before any investigation, because that is cheaper for the storefront than arguing.
- The seller gets a short response window. What decides the outcome here is purchase documentation, not the argument that no storefront rule was broken.
- The result depends on the supply chain. A confirmed authorised channel frequently gets the listing restored; missing paperwork almost never does.
- Repeat incidents escalate to account level rather than staying with a single listing, and restrictions there are harsher.
The important part: none of these steps requires you to have broken a marketplace rule. A conflict with the second layer — the publisher terms — is enough on its own.
When documentation gets requested
Documentation is almost never requested when you create a listing. It is requested in three situations: a cluster of buyer complaints about non-working codes, a rightsholder approach, or a review triggered by scaling volume. In all three the response window is short, and silence is not read in your favour. That is why purchase confirmations should be kept from the very first batch, rather than an archive being started after the first incident. Exactly what you need depends on your jurisdiction and legal status; that is a question for a lawyer and for the platform rules, not for an industry article.
Pre-launch checklist for a category
- The platform's live rules were read on the launch date, not recalled from memory.
- The publisher or platform terms for this specific product were checked.
- The batch source is known and documented.
- The activation region is stated explicitly in title and description.
- The description promises nothing the product does not deliver.
- A reserve is budgeted for dispute compensation and for a possible takedown.
Where to source inventory with clean provenance
Most assortment problems are solved at purchasing, not at moderation. FoxReload is a wholesale digital-goods supplier: 900+ SKUs (game keys, gift cards, in-game currency top-ups, eSIM, subscriptions, software licences), a single REST API, instant delivery and multi-region SKUs. A transparent purchasing channel means a predictable region, no grey batches, and supporting paperwork on hand when it is finally asked for.
Related reading: