Start from the affected order
Open the private page for the order with the problem and use its replacement-request controls while eligible. For a delivered account, the normal 24-hour window is measured from recorded delivery, not from the time you saved the listing or began checkout. Report a problem promptly rather than waiting until the end of the window.
The order page decides which controls are available from the order’s actual state. Existing remediation and replacement workflows have their own continuing path. If a request is already open, keep using that thread; the passage of 24 hours does not mean you should discard its history and start an unrelated conversation.
Sources: [1]
Describe the failure so it can be reproduced
A clear request identifies the failed step and the expected result. Choose the relevant issue category, explain whether access ever worked, and record when you first noticed the problem if you know.
- Name the game and the action you attempted, such as signing in or opening a disclosed entitlement.
- Copy the non-secret error message accurately instead of replacing it with “broken.”
- Explain whether the supplied account never worked or access changed later.
- List the troubleshooting steps already attempted and their results.
- Describe the exact listing feature that does not match what you received.
Sources: [1]
Add useful screenshots without exposing access
The request supports up to five screenshots in JPEG, PNG or WebP format, with each file no larger than 5 MB. Focus a screenshot on the message or missing feature. Remove passwords, authentication codes, recovery secrets and unrelated personal information before uploading.
If a request is created but an image upload fails, the thread remains available. Add the remaining files there rather than duplicating the whole request. A concise screenshot and a written timeline are usually easier to review than a large collection of nearly identical images.
Sources: [1]
Understand the review and remedy
Submitting a request starts review; it does not immediately authorize a replacement or refund. Support can ask for more information in the same thread. Watch for a status indicating that your reply is needed, and answer the specific question with the relevant observation.
A similar replacement account is the normal failed-delivery remedy. Operator-issued store credit is a secondary option, while cash refunds are exceptional and are not a customer self-service action. Do not interpret a request category or a screenshot upload as a guarantee of a particular outcome or completion time.
Sources: [1]
Keep security steps and evidence compatible
You do not need to leave usable access unsecured for 24 hours. Confirm the delivered account promptly, secure the channels you can actually control and keep a private note of the steps taken. If a publisher blocks one specific change, report that limitation accurately instead of assuming every other security action must wait.
A failed password, changed display name or security notification does not by itself identify who caused an issue. Supply the timeline and observed facts without guessing. Never send your new password or recovery code in a ticket. Your order reference and a clear account of the problem are the useful starting point.
Sources: [1]
