How to Sell Game Keys on FunPay
Keys are the highest-margin and simultaneously the most dispute-prone category on FunPay. Currency you transfer yourself and see the result instantly. With a key, a third party sits between your delivery and a satisfied buyer: the activation platform, with its regions, limits and checks that you do not control.
This is the practical playbook — how to disclose region and platform, how to treat revocation risk, what replacement policy to extract from a supplier before your first purchase order, and why activation support pays for itself.
It specialises the general guide to selling on FunPay for one category.
Why keys are more conflict-prone than currency
The difference is structural. Selling currency has a short chain: you transfer, the buyer sees the balance, the deal closes. A key has a longer chain with a link you do not control.
A code can be entirely valid at the moment of transfer and still fail for a particular buyer — because their account region does not match, because the account has hit a failed-attempt limit, because the product is already in their library. None of those is your mistake, but all of them arrive at your door as a complaint.
Hence the core insight: in keys you are not selling a code, you are selling predictability. Anything that reduces uncertainty on the buyer's side directly reduces your dispute rate.
Disclosing region and platform
This is the foundation of the category, and it is no place for brevity.
What to disclose before payment
- Activation region — always filled in, even when unrestricted. An empty field reads as risk.
- Platform or launcher — exactly where to redeem, especially when the title exists across several ecosystems.
- Product edition — base, deluxe, with or without DLC. A mismatch here produces an instant dispute.
- Account-level restrictions — requirements on the buyer's account region if any exist, not just the key's region.
What to repeat in the delivery
Buyers skim the listing but read the delivery message closely. So region and platform must appear in plain text next to the code, not only in the listing. The full delivery composition by category is covered in the article on FunPay seller obligations.
The mechanics of regional restrictions themselves are explained in the breakdown of region-locked keys.
Revocation risk
Revocation is not a rare anomaly but a normal operational risk of the category. A publisher or platform can deactivate a code retroactively if it reached the market through a chain they consider unacceptable. The buyer often discovers the problem not at activation but weeks later.
| Situation | Where fault actually sits | Correct response |
|---|---|---|
| Code invalid on arrival | Supplier or batch | Immediate replacement, claim to supplier |
| Code revoked after activation | Publisher or supply chain | Replacement, escalate to supplier |
| Buyer in the wrong region | Your disclosure | Resolve against what you disclosed |
| Product already in library | Buyer | Explain, refund per your policy |
The practical principle: response speed beats arguing about fault. A buyer who receives a replacement in ten minutes generally never reaches arbitration. Handling revocations and locks is covered in the article on code revocation and region-lock handling.
The replacement policy to demand from your supplier
This is the most underrated line item in procurement. A beginner compares suppliers on unit price. An experienced operator compares them on what happens when a code fails.
The minimum question set before your first order:
- Is there a written commitment to replace an invalid or revoked code, and within what window.
- What qualifies as grounds — invalidity at hand-off only, or later revocation too.
- What evidence you will need to supply for a replacement to go through.
- Is there a time limit from the moment of purchase after which replacement lapses.
- What happens with a mass revocation of a batch rather than a single unit.
A supplier without clear answers is not necessarily bad, but they are shifting the entire risk onto you, and that belongs in the purchase price. The difference between a cheap and a reliable channel is covered in the article on digital code reselling risks.
Activation support as an economic measure
Formally your obligation ends when you hand over the product in the stated composition. Practically, a buyer stuck on activation will open a dispute regardless of where the formal boundary sits.
The arithmetic is simple: three minutes of operator time explaining an activation step costs less than arbitration plus a rating hit. The sensible minimum is a short activation instruction inside the delivery template plus a willingness to answer follow-ups inside the platform chat, where the correspondence carries evidentiary weight.
Which keys to keep out of your assortment
Assortment discipline saves more money in this category than haggling over unit price. Some items statistically produce a disproportionate share of problems, and deliberately declining them is a working strategy rather than lost revenue.
- Keys with opaque batch provenance. If a supplier cannot say where a batch came from, you cannot assess revocation risk. The saving is almost always smaller than the cost of a single mass revocation.
- Items priced anomalously below market. A gap you cannot explain is usually explained by regional arbitrage or by a chain the publisher considers unacceptable.
- Pre-orders and pre-release keys. The long window between sale and activation means the complaint arrives after you have withdrawn the money and lost leverage with the supplier.
- Titles with complicated regional rules, unless you are prepared to explain them to every buyer. Support cost will eat the margin faster than you build volume.
The flip side of the rule: a narrow assortment you understand outperforms a wide one you do not control. Twenty items from a vetted supplier with a predictable replacement rate yield more net profit than two hundred random ones. How to assess a supplier before ordering is covered in the guide to choosing a wholesale gift card supplier.
How to calculate margin on keys
Margin in this category is not the gap between purchase and sale price. Three things enter the calculation and beginners usually ignore the last two:
- Unit purchase price at your actual volume.
- Replacement and refund rate — a direct deduction from margin, driven by supply quality.
- Operator time per order — with manual delivery this is a real cost line that grows linearly with turnover.
Platform fees and withdrawal fees are counted separately and always verified against FunPay's current tariff page before you price — rates change, and pricing from memory is expensive. The full calculation method is in the unit economics of a digital goods store.
Where to source keys
The category imposes two supply requirements that retail rarely meets: a complete data set per unit (code, region, platform, edition) and a documented replacement policy. Without the first you cannot disclose the product correctly; without the second your first mass revocation lands entirely as loss.
FoxReload covers both on the wholesale side: 900+ SKUs including multi-region items, a single REST API, and automatic delivery where region and platform arrive together with the code, letting you populate both the listing and the delivery template without manual lookup. For the broader channel view see the guide to selling game keys online.