> For the complete documentation index, see [llms.txt](https://stablemesh.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stablemesh.gitbook.io/docs/home/stablemesh-doc/cards/top-up.md).

# Top Up a Card

Move funds from your Stable Mesh crypto wallet onto a specific virtual card so you can start spending.

***

## How to Top Up

1. Go to **Cards** and click the card you want to fund.
2. In the detail panel, click the green **Recharge** button.
3. In the modal that appears:
   * **Card** — pre-filled with the selected card name.
   * **Currency** — select `USDT` or `USDC` from the dropdown. Your available wallet balance is shown next to each option.
   * **Amount** — enter the USD amount you want to load onto the card.
4. Click **Recharge** to confirm.

***

## What Happens Next

* The amount is **immediately deducted** from your crypto wallet.
* The card's **Available Balance** updates instantly.
* The card is ready to use right away.

***

{% hint style="info" %}
You can only top up using funds currently in your Stable Mesh crypto wallet. If your wallet balance is insufficient, [deposit more crypto](/docs/home/stablemesh-doc/deposit.md) first.
{% endhint %}

***

## Minimum & Maximum Amounts

Check the app for any minimum or maximum top-up limits that may apply to your account.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://stablemesh.gitbook.io/docs/home/stablemesh-doc/cards/top-up.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 `build a script that syncs our docs to a CMS` 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.