> For the complete documentation index, see [llms.txt](https://takes.gitbook.io/takes-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://takes.gitbook.io/takes-docs/holders/claim-tokens-or-usdc.md).

# Claim tokens or USDC

After settlement, Takes attempts delivery to the original controller. If delivery fails, you can manually claim the remaining entitlement: shares for a buy request, or USDC for a sell request.

The contract checks your entitlement. You do not need approval from Takes staff to claim a settled payout.

1. Connect the request wallet on the correct network.
2. Open the request and expand its manual delivery details.
3. Check the remaining payout, choose **Claim all shares** or **Claim all USDC**, and confirm in your wallet. The app claims the full remaining payout; it does not offer partial claim controls.
4. Wait for the transaction and updated balances to confirm completion.

Claims are made per request. Claiming one does not claim another request. You need gas, but no additional Takes claim fee applies.

Undelivered purchased shares still gain or lose value with the trading account. Settlement fixes the request's token quantity, not its future value.

If a confirmed claim has not appeared on the page, allow the data to update before trying again. See [Troubleshooting](/takes-docs/reference/troubleshooting.md#troubleshooting).


---

# 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://takes.gitbook.io/takes-docs/holders/claim-tokens-or-usdc.md?ask=<question>&goal=<user_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.