> For the complete documentation index, see [llms.txt](https://www.size.club/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.size.club/docs/cash-games/results.md). # Results and prize credit Your result shows your placement, game report, and reward status. ## Collect a cash prize If you win with cash selected, the displayed prize is credited to your Size wallet. A pending prize is not yet available to spend or withdraw. Check wallet history for the credit and your available balance. To move credited funds out of Size, [withdraw from your wallet](/docs/wallet/balance-and-withdrawals.md). ## Play again Review the report, then choose **Play again** or return to free practice. Each paid replay is a new entry. Review its cost and prize before confirming. ## Voided games and forfeits If Size voids a cash game because of a platform issue, your entry is refunded. Check its refund status in the result and wallet history. A pending refund is not yet available to spend. Forfeiting a paid game loses the entry. A connection problem does not guarantee a refund; reopen the existing game to check its result. ## Missing result or prize Check game and wallet history. If the result is missing or the prize remains pending, [contact support](/docs/help/support.md) with the game ID, time, entry, and expected prize. Starting another paid game will not recover a missing result. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.size.club/docs/cash-games/results.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.