Hi everyone,
I’m sharing my experience here in the hopes that it will be heard by the community and Blizzard alike — not out of anger, but deep disappointment.
Recently, I purchased and redeemed a Diablo IV 2800 Platinum key for Xbox Live . The code was successfully activated through my Microsoft account, and I can see the confirmation in my Microsoft order history. Unfortunately, I do not own an Xbox console — I play exclusively on PC via Battle.net .
What I didn’t realize (and wasn’t made clear at the time of purchase) is that the Platinum is locked to the Xbox version of the game . That means I’ve paid for in-game currency I can’t access at all . After extensive back and forth with Microsoft, G2A (the marketplace where I purchased the key), and Blizzard support, here’s what I’ve learned:
- Microsoft says the content was delivered and cannot be refunded.
- Blizzard says they cannot transfer the currency to my Battle.net account and cannot remove or reassign it since it’s platform-bound.
- The only suggestion was to “log in through an Xbox,” which I do not own , and I don’t feel comfortable jeopardizing my account security by borrowing someone else’s.
In the end, I’ve paid for something that is completely unusable . No refund, no transfer, no workaround. I’ve also been advised against a chargeback, as it could have consequences for my account — and I’ve always tried to resolve issues properly, not through dispute escalation.
I’m a long-time Blizzard player — 11+ years with Diablo alone — and what hurts the most is not just losing the money, but feeling like customer service is no longer empowered to help loyal players in situations like this. A one-time exception, a goodwill gesture, even a partial credit to my Battle.net account would’ve gone a long way. But instead, I was told that there’s absolutely nothing that can be done.
Blizzard used to be about players first . I don’t feel that anymore.
From now on, I’ll only purchase content directly through Battle.net if I continue with Blizzard games at all. I’m sharing this so others don’t end up in the same situation — and to hopefully encourage Blizzard to revisit how these issues are handled.
Thanks for reading,