How to Handle Refunds and Chargebacks on Your Game Assets
The refund request that quietly turns into a chargeback
Here's the situation that drains the most money out of new sellers, and almost nobody warns you about it. A buyer messages asking for a refund on a $25 prop pack. Maybe they grabbed the wrong thing. Maybe it didn't import the way they pictured. You're annoyed, because the pack works fine and you tested it across three engine versions, so you do one of two things: you ignore the message, or you argue the point. Ten days later that same $25 comes back as a chargeback. Now you're out the money, out a dispute fee that's often bigger than the sale itself, and your payment processor has quietly filed you under "seller who generates disputes."
I've watched this happen to genuinely good creators sitting on genuinely good packs. The topology was never the problem. The silence was.
A chargeback is not just a slower refund
People use these two words like synonyms and they're nothing alike. A refund is you handing money back on your terms. A chargeback is the buyer's bank yanking it back on theirs and dragging you through the paperwork on the way out. When a charge gets disputed, the processor usually bills you a fee (Stripe's runs about $15 in the US) whether you win or lose. On a cheap asset you're underwater even in victory. Rack up enough disputes and you get dropped into a monitoring program with fatter rates, and past a certain ratio your payouts freeze. For a studio that's an annoying meeting. For a solo asset seller, that's your store going dark with your money still trapped inside it.
So the best practice I'd carve into every beginner's desk is almost embarrassingly plain: say yes to the refund, fast, before it has any chance to curdle into a dispute.
A refund costs you one sale. A chargeback costs you the sale, the fee, and a chip off your account's reputation every single time.
Fast and human beats slow and correct
You can be completely right about your pack and still lose, because the dispute system never grades your mesh. It grades whether the buyer felt taken care of. So the whole job is making people feel heard before they get frustrated enough to phone their bank. A handful of habits do most of that work.
Reply within a day, even if the reply is "give me a day"
Most chargebacks are born from feeling ignored, not from feeling robbed. A buyer who gets a real human answer in a few hours almost never escalates, even when that answer is "let me look into this tonight." Silence is what pushes someone toward the dispute button, because to them that button feels like the only lever they've got left. Don't hand them that feeling. A quick "hey, saw this, digging in now" buys you a startling amount of goodwill for basically nothing.
Refund first, ask questions second
On anything under about fifty bucks the math isn't close. The fee, the wasted hour, the account risk, all of it towers over the sale. Just refund it and move on. You can absolutely ask what went wrong afterward, and honestly you should, because half the time the answer is a bug report or a hole in your docs you'll want patched. But you ask it once the money's already on its way back, not as a hostage condition. Try "refunded you just now, out of curiosity what tripped you up? Might be something I can fix for the next buyer." That single message turns an irritated customer into an unpaid tester.
Keep a boring paper trail
For the rare dispute you actually decide to fight, records are what win it. Save the buyer's messages, your delivery timestamp, the license terms they clicked through, screenshots of the working files. Park all of it somewhere you can pull up in two minutes, because processor response windows are short and they do not care about your weekend. Most of the time you'll never touch the folder. The one time you do, it's the whole ballgame.
Put a plain refund line on your store page
Two sentences in the buyer's own language prevent more disputes than any legal wall of text ever will. Something like: "Not happy with the pack? Email me within 14 days and I'll refund you, no drama." That pulls double duty. It calms the honest buyer so they don't panic-dispute, and it hands you a clear, stated process to point at if someone tries to skip straight to their bank.
A refund request is really just a returns desk with worse lighting and no line. Photo via Wikimedia Commons.
When you shouldn't just eat it
Saying yes fast is a rule, not a suicide pact. If you sell high-ticket packs, or you catch a clear pattern (the same buyer refunding a dozen assets across a dozen stores, or someone who obviously ripped your files and then asked for their money back), you're allowed to hold the line and, if it comes to it, fight the dispute with that paper trail you kept. The real skill is telling the two cases apart. A confused first-time buyer and a serial abuser are not the same person, and treating a nervous newcomer like a thief is exactly how you manufacture the chargeback you were trying to avoid. When you can't tell, refund. The abusers are rare and your reputation is expensive to rebuild.
Clean refunds and good support are two sides of the same coin, and I went deep on the support half over in this piece on the fast reply that quietly sells. Worth a skim once your refund line is sorted.
Your marketplace either softens the blow or twists the knife
Here's the part nobody flags until it bites you: the platform you sell on decides how much a dispute actually hurts. If your payouts are slow and pooled together, a chargeback can claw back money you already spent in your head, and you're left waiting weeks to see anything land at all. That lag is its own quiet form of churn.
It's a big reason we built payouts the way we did on DevLoot. Payments run through Stripe Direct Charges, so a sale hits your own connected account fast and direct instead of floating in some middleman pool. You keep up to 92% of every sale (8% on Pro, 12% on Free), which means a refund costs you fewer real dollars than it would on a store skimming a quarter or a third off the top. Verified seller badges and a custom storefront pull their weight too, because buyers who trust the shop they're standing in are far slower to reach for the dispute button in the first place. If you want the fees laid out against the usual names, I put the numbers side by side in this fee comparison.
Start selling where a refund stays a refund
None of this is hard. Answer fast, refund faster, keep receipts for the one fight actually worth having, and sell somewhere your money reaches you quickly and mostly stays yours. Do that and refunds turn into a rounding error instead of the thing that slowly bleeds your store dry.
If you've got a pack sitting on your drive waiting for a home, you can set up a seller account in a few minutes over at the DevLoot vendor dashboard, or start with the get started guide if you'd rather scope out the lay of the land first. Your future self, the one not stuck fighting a chargeback at 11pm on a Tuesday, will thank you.