> 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/wallet/add-funds.md).

# Add funds

Deposit into your Size wallet to pay for entries or Store purchases. Free practice needs no deposit.

Use the token and network shown in the deposit flow. Sending funds on the wrong network can lose them permanently.

## Make a deposit

1. Open **Wallet** and choose **Add funds**.
2. Select an available deposit route.
3. Review the token, network, destination, and provider charges.
4. Submit the transfer.
5. Follow its status until the funds appear in your available balance.

A direct deposit and a bridge transfer use different instructions. A bridge moves funds between networks.

USDC is a digital asset designed to track the US dollar. Use the supported USDC shown for your selected route.

## Follow the transfer

A deposit can go through these steps:

| Step               | What happens next                                |
| ------------------ | ------------------------------------------------ |
| Transfer submitted | The source network confirms it                   |
| Bridge processing  | The provider moves the funds between networks    |
| Bridge complete    | Wait for the funds to appear in your Size wallet |
| Funds available    | You can use the credited wallet balance          |

Labels may vary by route. A completed bridge transfer alone does not mean the funds are available in Size.

## Deposit missing

Check the token, network, destination, and transaction status. If confirmed funds are missing, [contact support](/docs/help/support.md) with the transaction ID and route.

Do not send a second deposit to recover the first.


---

# 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/wallet/add-funds.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.