If you’ve ever tried to get a refund for a game purchase that wasn’t yours maybe your kid tapped “buy” without asking, or someone used your account without permission you know how frustrating it can be when the platform says no. Often, the issue isn’t whether you’re telling the truth. It’s whether you gave them the right kind of proof. That’s where knowing what counts as acceptable evidence formats for invalidating game purchases comes in.

What does “acceptable evidence” actually mean here?

It’s not about writing a long story or sending screenshots of your bank statement. Platforms like Steam, PlayStation Store, Xbox, or mobile app stores need specific types of documentation that clearly show the purchase wasn’t authorized by you. Think of it like showing a receipt and ID at a store return counter except digital, and stricter.

When do you need to submit this kind of evidence?

You’ll usually need to provide acceptable proof if:

  • You’re disputing a charge because someone else made the purchase (child, friend, hacker).
  • The refund request was denied the first time, and you’re appealing.
  • You’re submitting directly through a support portal instead of going through your payment provider.

If you skip this step or send blurry screenshots, incomplete logs, or unrelated documents, your case will likely get closed without review.

What kinds of files or formats actually work?

Most platforms accept these, but check their help section first:

  • Screen recordings – A short video showing login history, purchase timestamps, or unauthorized access. Make sure timestamps are visible.
  • Chat logs or messages – If someone admitted to using your account, save those. Export them properly don’t just take cropped screenshots.
  • Device usage logs – Some parental control apps or system logs can show who was using the device at the time of purchase.
  • Bank or card alerts – Notifications you received at the exact time of purchase, especially if they include location data or device info.
  • Account activity reports – Downloaded from your console or storefront account, showing IP addresses or unrecognized devices.

Avoid sending things like handwritten notes, voice memos, or social media rants. They won’t count.

Common mistakes people make

Here’s what gets requests rejected faster than you’d think:

  • Sending a screenshot of the game in your library that just proves you own it, not that you didn’t buy it.
  • Uploading blurry, zoomed-in, or cropped images that hide key details like dates or usernames.
  • Submitting evidence after the deadline most platforms give you 14–60 days from purchase.
  • Assuming customer service will “figure it out” without clear, labeled files.

How long should you wait after submitting?

Responses vary, but most platforms take between 3–10 business days. If you haven’t heard back after two weeks, it’s reasonable to follow up. You can check typical response times for different services on this page about how long refunds usually take.

What if your evidence was rejected?

Don’t just resubmit the same thing. Look at the reason given. Was the file unreadable? Did it lack timestamps? Fix that. Then, if needed, go through the proper channel to appeal there’s a separate process for that outlined here.

Where to find official guidelines

Each platform has slightly different rules. For example:

  • Steam’s refund policy is here.
  • PlayStation’s purchase dispute steps are here.
  • Xbox and Microsoft Store explain their process here.

Always start with their official page before submitting anything.

Quick checklist before you hit submit

  • Is your evidence in an accepted format (PDF, MP4, PNG, TXT)?
  • Does it clearly show the date, time, and account/device involved?
  • Did you remove personal info (like full credit card numbers) before uploading?
  • Have you double-checked the file isn’t corrupted or too large?
  • Did you reference the correct purchase ID or transaction number in your message?

If you’re unsure what formats your platform accepts, you can review examples and templates on this page.