Uploaded image for project: 'Minecraft Realms'
  1. Minecraft Realms
  2. REALMS-7622

Charged for Realms but cannot create world

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 1.16.210 (Bedrock)
    • None
    • Alienware m17 Windows 10
    • Unconfirmed
    • Bedrock

      I was charged automatically for a 10 player realms account earlier in the month, but the realms server I had was still listed as expired, my account says no active subscriptions, the account I bought realms with says I don't even own minecraft, and when I go to create a new realms server it acknowledges I got charged but it cant create a new realm. 

      I've since removed my card information from my account so I don't get charged for a realms I can't use, until this gets resolved. How do I fix this? I'm really not happy with getting billed for something I can't use and I've been trying to resolve this issue all month with no success. If the issue can't be fixed, then how do I go about getting a refund? 

      I play minecraft on PC using my microsoft account and microsoft has no history of this transaction or proof of subscription either, and logging into the minecraft website using my microsoft account (Instead of the regular mojang account) also falsely shows I don't own the game. I can't find ANY proof that I have the game or paid for a subscription anywhere outside my bank account and the realms error messages. I'm absolutely stumped.

        1. Screenshot (170).png
          Screenshot (170).png
          924 kB
        2. Screenshot (171).png
          Screenshot (171).png
          518 kB
        3. Screenshot (172).png
          Screenshot (172).png
          531 kB
        4. Screenshot (173)-1.png
          Screenshot (173)-1.png
          113 kB
        5. Screenshot (174)-1.png
          Screenshot (174)-1.png
          112 kB

            Unassigned Unassigned
            xXLhunaMothXx danny
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: