Refund requested, approved and received describe different states
Updated
A submitted refund request is not yet an approval, and an approval is not the same observation as a credit visible in the expected destination. Start with the exact purchase and latest official status. This helps you distinguish an eligibility question, an unresolved request and a payment observation without predicting an outcome from another player's experience.
Identify the transaction and product type
Use the relevant purchase record rather than a similar-looking game name. A base game, DLC, bundle, gift and purchase made outside Steam can have different applicable terms. Match the request to the actual transaction and check the current policy section for that category. Do not copy the ordinary game's conditions onto every product merely because it is related to a game.
Suppose a player meant to request a refund for an expansion but instead reads the base game's record. The title may look familiar while the purchase date and product are different. Correct the transaction question before interpreting playtime or request status. Keep transaction identifiers private and use Steam's official support route for the relevant purchase.
Read the ordinary rule with its scope
Steam's stated ordinary offer for store games and software is within 14 days of purchase and less than 2 hours of playtime. The policy also says that a request outside its described rules can still be submitted for consideration. Neither statement turns this article into an individual approval decision. Check exceptions and purchase-type terms rather than treating the ordinary rule as universal.
For example, DLC conditions concern the underlying game's use after the DLC purchase and other stated restrictions. That is not interchangeable with a casual estimate of lifetime playtime. When an account's actual record is unclear, use the official purchase-specific information instead of rounding a guessed value into a definite claim of eligibility.
Find the latest official request state
Check whether the relevant request was actually submitted and what Steam currently reports for it. Writing an explanation in a form, receiving a general help message and having a submitted request are different observations. If the submission is confirmed but a decision is not, record that pending decision rather than saying the refund is already approved.
In the hypothetical case, a player sees confirmation of submission but no decision and checks a payment account repeatedly. The missing credit has not established a payment failure because approval remains unconfirmed. Read the official request history first and follow its applicable response or support options; do not create duplicate requests merely to make the process appear active.
After approval, check the expected destination
Steam says a full refund is issued within a week of approval and describes Steam Wallet or the original payment method, with Wallet used when the initial method cannot be refunded. Use the actual approval and destination information for the transaction. Do not infer that a refund went to a bank account simply because the purchase was once made through one.
Suppose the official response identifies Wallet funds while the player checks only an external statement. These are different destinations. If the response identifies the original payment method, inspect that method's relevant transaction record instead. This comparison does not promise an exact display time or diagnose the payment provider.
Keep approval and receipt evidence separate
Record the approval information, expected destination and what you actually see there. A game disappearing from a library is not itself a payment record. Similarly, an account balance viewed without checking the matching transaction may not establish which purchase was credited. Use the appropriate official history and preserve the distinction between a status and an observed credit.
If the expected outcome remains absent after the applicable period or the response is unclear, follow the purchase's support path with a concise description. Do not expose full card details or private transaction information in a public forum. This article does not decide whether Steam or another provider caused a delay; it organizes the evidence needed to ask the relevant question.
Write a result without promising another user's outcome
A useful result distinguishes request submitted, decision received and matching credit observed. If only the first is confirmed, leave the later states unresolved. If a decision declines the request, report that decision without turning another person's approved case into a guarantee that yours must be reversed.
Recheck the current policy when the purchase type or circumstances differ. The practical aim is to understand the transaction's present state and the next official step. A historical policy summary or a fictional example cannot replace the account's response, predict approval or settle jurisdiction-specific rights.
Match the transaction and applicable policy, confirm submission and decision, then compare the expected refund destination with an actual credit. Keep these states separate. When something remains unclear, use the relevant official support path with private, transaction-specific evidence instead of assuming an approval or payment outcome.