# Token Transfers

Follow the instructions below to send and receive tokens with your Kabila Wallet.

## Send Tokens

To send tokens from your account to another Hedera-based account, follow these steps:

1. **Navigate to the "Tokens" section.**
2. **Click on Send button.** This is the green button located in the upper right corner.
3. **Select Recipient.** In this section, you'll need to input the Hedera Account ID you want to send the funds to, and click on Next. Note that you can also send funds to Domain names (like kabila.hbar or others).

<figure><picture><source srcset="/files/ywzjAfrnPVH8o2jHMthx" media="(prefers-color-scheme: dark)"><img src="/files/mq6dNgbgxdORCWluXihP" alt=""></picture><figcaption></figcaption></figure>

4. **Choose Token.** Now, select the type of token you want to transfer.
5. **Specify Amount.** Enter the number of tokens you wish to transfer. You can define the total amount either in tokens or in fiat currency.
6. **Add a Memo (Optional).** Include any notes you want with the transfer. Keep in mind that some exchanges may require a memo for receiving and processing crypto transfers.

<figure><picture><source srcset="/files/gNIQbrBK7ZAcxNKyteuj" media="(prefers-color-scheme: dark)"><img src="/files/PaA2CqinF2bI5M0A2PT6" alt=""></picture><figcaption></figcaption></figure>

7. **Review the transfer details.** Double-check that the recipient's account and the total amount to be transferred are correct.
8. **Click on "Send".** Confirm the transfer and wait for the Success message to appear.

<figure><picture><source srcset="/files/yuHPwJrgKi3jTEG9d9ii" media="(prefers-color-scheme: dark)"><img src="/files/NJvJR9xpmlcNXF0vjDa9" alt=""></picture><figcaption></figcaption></figure>

## Receive Tokens

To receive tokens from other accounts, simply share your Account ID.

You can find your Account ID at the top centre of the Wallet App, just below the Account Alias.

There are three types of Hedera account structures. Click on your Account ID to view and copy the one you prefer:

* **Standard Account.** This is the regular Account ID format, for example: 0.0.1234567
* **With Checksum.** This adds a slash and four extra characters to the Standard ID, providing an additional security layer against typos. While using the checksum is optional, we recommend providing your Account ID with it. Example: 0.0.1234567-abcd
* **EVM Address.** This is the EVM compatible ID of your account, necessary for interacting with certain Ethereum-based applications.

<figure><picture><source srcset="/files/GfoVxRKSFhrVBw1PH3J5" media="(prefers-color-scheme: dark)"><img src="/files/EObsboTkOq40NYgd0bNb" alt=""></picture><figcaption></figcaption></figure>

## Token Association

On Hedera, before being able to receive tokens (other than HBAR) or NFTs, you need to associate their Token ID with your Account. This is a security measure to avoid spam tokens.&#x20;

{% hint style="warning" %}
If a specific token is not associated within your account, you won't be able to receive it.
{% endhint %}

To associate new tokens, go to the "Tokens" section and click on the upper left button "**+ Associate Token**".

Then select a token from the "Known tokens" list or manually add the Token ID.

And click on "Associate".

After successfully associating the Token, you'll be ready to receive tokens with that specific Token ID.


---

# Agent Instructions: 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 current page URL with the `ask` query parameter:

```
GET https://academy.kabila.app/products/wallet/token-transfers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.