> For the complete documentation index, see [llms.txt](https://docs.cakewallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cakewallet.com/features/basic/receive-funds.md).

# Receive funds

How to receive crypto in Cake Wallet: share your address or QR code, set an amount, and choose Bitcoin, Litecoin MWEB, Monero subaddress or token addresses.

Tap `Receive` on the home screen and you get your address as text and a QR code — copy it, share it, or let the sender scan it. Use `Set amount` to embed a specific amount in the QR so the sender's wallet fills it in automatically.

![Receive screen with QR and actions](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/fund_btc_carrot-cake_receive_hl.png)

**Tip: tap the QR code to enlarge it.** You get a full-screen, Cake-branded version that's easier to scan from another phone — and a cleaner visual if you want to screenshot or share your address.

![Enlarged QR view after tapping the QR code](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/receive_qr_enlarged.png)

{% hint style="info" %}
On Bitcoin-family and Monero wallets, your receive address rotates after each payment for better privacy. Old addresses keep working forever — rotation just means new payments get fresh addresses.
{% endhint %}

## Bitcoin: pick your address type

Bitcoin wallets have several address types. Tap the type shown under the QR code to switch:

* **Standard** — the default (SegWit/P2WPKH, starts with `bc1q`). Right for almost every payment.
* **Lightning** — instant, near-free payments via your `@cake.cash` address. See [Lightning](https://docs.cakewallet.com/features/basic/bitcoin-lightning).
* **Silent Payments** — a static `sp1` address you can post publicly; every payment lands at a fresh on-chain address. See [Silent Payments](https://docs.cakewallet.com/features/privacy-and-security/silent-payments).
* **More Options** — legacy and specialty types (Taproot, P2SH, and others) for compatibility with older services.

![Bitcoin address type sheet](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/receive_btc_address-types.png)

## Litecoin: Standard and Private

Litecoin wallets offer `Standard` (`ltc1`) and `Private` — your MWEB address (`ltcmweb1`), where amounts and addresses are confidential. See [Litecoin MWEB](https://docs.cakewallet.com/features/privacy-and-security/litecoin-mweb).

## Monero: accounts and subaddresses

Monero wallets organize addresses into **accounts** (separate buckets with their own balances) containing **subaddresses** (fresh receive addresses, generated automatically). Tap `Addresses` on the Receive screen to browse them — each shows how many payments it has received. Long-press an address to label it.

![Monero addresses view with account and subaddresses](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/receive_xmr_accounts_02_addresses.png)

To rename an account or change its card color, tap `⋮` on the home screen balance card to open `Edit Account`.

## Ethereum, Solana, Tron and tokens: one address per chain

These wallets use a single address that never changes (Ethereum-family addresses start with `0x`). The same address receives the native coin and every token on that chain — the receive screen reminds you of exactly that.

![Ethereum receive screen with 0x address](https://raw.githubusercontent.com/cake-tech/docs-assets/main/v6.3.1/eth_receive_01.png)

{% hint style="warning" %}
When receiving tokens, make sure the sender uses the right network. USDT on Tron sent to an Ethereum address (or vice versa) will not arrive — the address format alone doesn't guarantee the network matches.
{% endhint %}


---

# 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.cakewallet.com/features/basic/receive-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.