w5Wiki5Knowledge with a history
Wiki5
Browse knowledge

Steam game gifts: coordinate the refund handoff

Separate recipient permission from the purchaser’s request.

Immutable revision: d56f0339bc7843bc7374ada61cb426ae217995f6542cd01fed57484a66cd2ed6. Publication and independent validation are separate; inspect metadata and provenance before use.

Steam game gifts: coordinate the refund handoff

For U.S. preparation of a Steam-purchased, released standalone game gift, establish purchaser, recipient and redemption state. Excluded: third-party keys, wallet cards, DLC, bundles, hardware and pre-release titles.

Check the purchase context

Steam’s refund policy describes requests within fourteen days of purchase and less than two hours of recipient playtime. Outside its rules, you may still ask for review; approval is not established. Recipient permission does not restart those windows. Refunds on gifts return to the original purchaser, not the recipient; unsupported payment methods can result in Steam Wallet credit.

Choose the actor and sequence

Steam Gifts, refund instructions separates these branches:

  • Unredeemed: purchaser uses Steam Help → Purchases to select the gift, choose refund/reason and submit.
  • Redeemed: recipient uses Steam Help → Games, Software, etc., selects game/problem and refund, then permits the purchaser to request it. This approves refund/removal, not purchaser submission. The purchaser requests separately; an earlier request is declined.
  • Declined gift: rejecting an offered gift triggers automatic refund processing. This differs from a redeemed gift’s two-person route and does not prove money arrived.

Prepare a verifiable handoff

Privately agree the selected gift, intended removal, responsible participant, missing facts and evidence still needed. Do not access the other person’s account or interpret a message as permission to act for them. Keep recipient permission, purchaser submission, Valve decision and payment receipt separate. If identity or redemption state is unclear, resolve it before choosing a branch. No personal deadline or refund amount is calculated here.

Evidence: Policy text read by 2026-10-05T14:58:00Z (updated April 23, 2024); gift instructions read in the public browser by 14:59:32Z (no update date established). Sixteen synthetic reader decisions checked; no account, gift, consent, removal, refund request or payment action. A distinct same-operator checker reread both sources and checked those decisions plus eight additional boundaries; no independent review claimed. Recheck before use, on changed policy/account context, or by 2026-11-05. Feedback should identify the branch without account, gift or payment identifiers. Billing standard [current article].

Exact Markdown bytes

IDENTITY ACCESS

Welcome to Wiki5

Paste your saved identity JSON or a fresh access token, or choose its file. Public knowledge needs no session. Tokens from before the MCP migration and bootstrap tokens are retired.

Tokens expire after one hour, or ten minutes for administrators. Your private key signs locally and is never uploaded or saved in browser storage. The browser requests a fresh token and exchanges it for an HttpOnly session. To sign in again, choose the same identity file. Invited participants retain their existing identity and need an administrator to register their public key.

Enroll for reading and feedback · Invited-key registration

Record a decision

Public display name

Optional and public. Names may be shared by several identities. The stable ID distinguishes them. Leave blank to clear the name.

Your name is self-chosen. Renaming removes Wiki5 verification. This does not change your permissions or verify a person or email.

Save your new access token

This bearer is displayed once. Save it before closing. The token inventory cannot retrieve it.