> 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/mint-tokens.md).

# Buy pool shares

Buying adds exposure to a pool’s strategy. You pay USDC and receive pool shares automatically after settlement. The protocol calls this a **mint** or **deposit request**; the app calls it **Buy**.

Connect your wallet on the pool’s network. Keep enough USDC for the purchase and enough of the network’s [gas token](/takes-docs/reference/supported-networks.md#networks) for approval, the request, and a manual claim if needed.

1. Choose **Buy** in a Portfolio pool row or the pool page’s **Your position** card. From a basket page, select a pool and choose **Buy shares**. You can also select USDC and a pool in [Trade](/takes-docs/trade.md#buy-or-sell-pool-shares).
2. In **Buy pool shares**, enter the USDC amount under **You pay**. **Max** fills the available amount after the estimated gas reserve.
3. Estimated net investment and total fees appear automatically. Expand fee details if needed.
4. Choose **Buy shares**. If approval is needed, confirm USDC approval in your wallet; the app checks the updated allowance, gas and fees automatically, then opens the purchase confirmation.
5. Confirm the purchase transaction in your wallet. If fees or estimated proceeds changed, check the updated amounts and choose Buy shares again.

Approval alone does not submit a buy request. After your request is confirmed, it is Accepted and waits for processing. Takes starts processing as soon as ready and delivers shares automatically after settlement, with a [manual fallback](/takes-docs/holders/claim-tokens-or-usdc.md#claim-tokens-or-usdc).

The share quantity is not fixed until settlement. The signed settlement fee locks at acceptance and includes estimated Circle costs. The 0.1% platform fee and settlement fee are deducted when processing begins. See [Fees and limits](/takes-docs/reference/fees-and-limits.md#fees-and-limits).

## Cancel a buy request

Open **View requests** from Portfolio or **Your requests** in the pool page's Activity section. Before processing starts, choose **Cancel** on the Accepted buy request, then **Cancel buy request**, and confirm in your wallet.

Cancellation returns the full USDC amount of that request without platform or settlement fees. Other requests remain unchanged. It does not refund network fees. Processing starts promptly, so the cancellation window is short. If processing wins the ordering race, cancellation reverts and can still cost gas.

Known transaction hashes resume tracking automatically after reload. If the wallet outcome is unknown, check wallet activity; the app pauses that action to prevent duplicate submission. 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/mint-tokens.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.