What a FunPay Seller Must Deliver to the Buyer
Most disputes lost on FunPay are not fraud and not faulty goods — they are incomplete delivery. The seller sent the key but not the region. Handed over the account but forgot the recovery email. Transferred the currency but never confirmed the credit. Formally the product left; practically the buyer could not use it.
This article covers exactly what belongs in a complete delivery for each category, why incompleteness loses arbitration almost automatically, and what the evidence checklist that protects a seller looks like.
It builds on the core guide to selling on FunPay and the dispute playbook.
The core principle — a product is a bundle, not a string
A new seller thinks in terms of the asset: they sold a key, so they owe a key. The platform and its arbitration think in terms of outcome: the buyer paid for the ability to play, so they are owed everything required to activate.
The gap between those two models is where money disappears. The test is simple — can the buyer use the product without asking you a single follow-up question? If not, delivery was incomplete, whatever you believe it to be.
The practical consequence: every product category has a mandatory bundle, and it should be fixed as a template before your first sale rather than improvised per order.
Delivery composition by category
| Category | Mandatory minimum | Common failure |
|---|---|---|
| Game key | Code, activation region, platform or launcher | Code sent alone |
| Account | Login, password, linked email, recovery data | No access to the email |
| Game currency | Credit confirmation, transaction identifier | No proof of credit |
| Subscription or top-up | Code or confirmed credit, wallet region, denomination | Region not stated |
Keys
The full bundle is the code, the activation region and the platform. A key without a stated region is a lottery: a buyer in a different region hits an activation error and is in the right, because the restriction was never communicated at hand-off. The platform matters wherever the same title exists across several ecosystems — the buyer needs to know where to redeem.
State the activation window separately if one exists, along with what happens on error. The mechanics of regional restrictions are covered in the article on region-locked keys.
Accounts
This is the widest bundle and the most frequently lost category. A working login and password is not a transfer of ownership, it is temporary access. Complete delivery includes the linked email with access to it and the recovery data, otherwise the buyer does not control the asset and can lose it at any moment.
If category rules make some element impossible to transfer, that limitation must be explicit in the listing and repeated in the delivery message. Silence here is read against the seller.
Currency and top-ups
For in-game transfers the closing point of the transaction is not the moment you send but the confirmation of credit. A screenshot or transaction identifier from your side, sent immediately after the transfer, kills the did-it-actually-arrive question. The specifics of this category are covered in the guide to selling game currency on FunPay.
Why partial delivery loses disputes
Platform arbitration does not reconstruct your intentions or assess your good faith. It compares two things: what the listing promised and what actually reached the buyer in chat. Everything between those points — your experience, your reputation, your confidence in your supplier — carries almost no evidentiary weight.
Three practical consequences follow:
- Composition mismatches read instantly. If the listing states a region and the delivery message does not, that is visible in seconds and treated as non-performance.
- Silence is worse than the error. A seller who sends the missing piece a minute after the complaint usually closes the matter. A seller who replies a day later has already lost.
- External channels do not count. Data passed through a messenger barely exists for arbitration purposes, and it simultaneously breaches platform rules — see the article on rules and bans.
The delivery evidence checklist
Your evidence base has to build itself at the moment of sale. Collecting it after a complaint means you are already late. The per-order minimum:
- An exact hand-off timestamp, comparable against the payment time.
- The full text of the delivery message, exactly as the buyer received it.
- The identifier of the specific unit — which code or which transaction went into this order.
- Supplier confirmation of validity, region and platform at the moment of transfer.
- The complete platform-chat correspondence, including your clarifying questions.
Automation matters more than discipline here: configured auto-delivery generates the log itself and makes the bundle identical in every order. How to set that up is covered in the FunPay auto-delivery setup guide.
The delivery template as an operational tool
The cheapest improvement available is one fixed template per category that operators fill in rather than compose. The template holds every mandatory field, a short activation instruction, and one line on what to do if activation fails.
Three effects follow: composition stops depending on operator mood, response speed rises, and in arbitration you present exact text rather than a paraphrase. It also removes friction from scaling — a new hire works to the template on day one.
When the full bundle cannot be delivered
There is a separate class of situations where some data genuinely cannot be handed over — category rules, platform restrictions or supplier terms prevent it. That is normal and does not make you a bad actor. What makes you a bad actor is staying silent about it.
The working pattern has three steps, and skipping any one of them puts you back in the risk zone:
- The limitation appears in the listing as explicit text, not as an implication. Wording like recovery data is not transferred belongs in the description before payment, not in a chat exchange afterwards.
- The limitation is repeated in the delivery message. A buyer who has seen it twice cannot credibly claim they did not know.
- The consequences are named. Exactly what the buyer will not be able to do, and what happens if they try — this removes half of the complaints that would otherwise follow.
Separately, check whether the limitation itself conflicts with platform rules. Some categories require a certain minimum to be transferred, and a listing that does not provide it risks failing moderation or drawing a penalty. What is actually punishable is covered in the article on rules and bans.
A practical rule of thumb: if a limitation is significant enough that you do not want to write it in the description, do not publish the listing. A product that only sells because of an omission produces disputes faster than it produces profit.
Where to source stock so the bundle is complete
Delivery completeness starts not with you but with your supplier: if they do not pass region and platform alongside the code, you physically cannot state them to the buyer. That makes the data set per unit as important in procurement as the price.
FoxReload covers that side of the problem: a catalog of 900+ SKUs including multi-region items, a single REST API, and automatic delivery where region and platform arrive together with the code itself — so your delivery template fills in without manual lookup. For more on choosing a wholesale channel, see the breakdown of digital-goods wholesale suppliers.