> For the complete documentation index, see [llms.txt](https://docs.chaingpt.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chaingpt.org/our-ecosystem/chaingpt-pad/flexible-refund-policy/claim-and-refund-guide.md). # Claim & Refund Guide

> ***A quick guide to understanding the claiming and refunding process post IDO.*** After an IDO on the ChainGPT Pad is completed, a cooldown period lasts until the TGE. As soon as the TGE begins, the cooldown is over, and users will have two options unlocked in their dashboards: **Option #1:** Claim Tokens\ **Option #2:** Request a Refund

*CLAIM OR REFUND OPTIONS BECOME AVAILABLE*

### Claiming

As soon as you select “Claim Tokens”, the dashboard will show a green checkmark on the right-hand side under the “Schedule” section. Once the checkmark appears, the refund option on the bottom will show a red cross and state, "you have already claimed TOKEN; you are not eligible to request a refund. *💡 **Reminder:** By claiming tokens, you will forgo the ability to refund your allocation.* ### Refund

*REFUND REQUESTED FROM CHAINGPT PAD IDO*

If you select the “Request Refund” option in the bottom section, the dashboard will immediately remove your alternative “Claim” option and confirm that your refund has been submitted. Submitted requests will provide the status of “Refund Requested” in yellow characters in the refund section, as well as the time of the request and the approximate time the refund will become available. *💡 **Reminder:** Refund requests require a processing time of up to 24 hours after initiation.*

Once the request is processed, you must return to the IDO page and verify that it has been processed. As soon as the Refund section at the lower portion of the dashboard changes to green text by the status, you will collect your funds into the wallet you used to participate. \--- [**Disclaimer**](/misc/legal-docs/disclaimer.md) --- # 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://docs.chaingpt.org/our-ecosystem/chaingpt-pad/flexible-refund-policy/claim-and-refund-guide.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.