> For the complete documentation index, see [llms.txt](https://support.ellipal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.ellipal.com/docs/features-and-advanced-usage/common-receiving-issues-and-solutions.md).

# Common Receiving Issues and Solutions

To receive crypto with ELLIPAL, open the ELLIPAL App, tap **Receive**, select the coin and network, then share the address or QR code with the sender. On Titan 2.0, you can verify the address on the device screen before sharing. On X Card, the address is displayed in the app.

***

### Issue 1: The sending platform rejects the address

<details>

<summary><strong>Wrong network or coin selected</strong></summary>

Make sure the address you copied was generated for the exact coin and network the sender is using. In the ELLIPAL App, tap **Receive**, select the correct coin, and confirm the network label shown below the address before sharing.

</details>

<details>

<summary><strong>XRP Memo / Destination Tag required</strong></summary>

Personal ELLIPAL wallets do not require a Destination Tag. If the sending platform insists on one, enter a simple numeric value such as `0`, `1`, or `12345`. Always test with a small amount first before sending the full amount.

</details>

<details>

<summary><strong>Address not activated — for example, XRP</strong></summary>

Some networks require a minimum balance to activate a new address. XRP requires approximately 1 XRP. If your address has never received funds, deposit a small activation amount first.

</details>

<details>

<summary><strong>XDC address format not accepted</strong></summary>

XDC addresses can be displayed in two formats. If the platform does not accept the `xdc...` format, change the prefix to `0x...` and try again.

</details>

<details>

<summary><strong>Exchange blocks the address</strong></summary>

Some exchanges block withdrawals to certain address types due to internal risk controls. Try again after some time, or contact the exchange's support team directly — ELLIPAL cannot intervene in exchange-side restrictions.

</details>

***

### Issue 2: Funds sent but not showing in the ELLIPAL App

If a deposit was sent but is not appearing in the ELLIPAL App, work through these checks in order:

1. **Check the withdrawal status on the sending platform** — confirm the transaction has actually been sent and is not still pending or queued
2. **Search the TXID on a block explorer** — look up the transaction hash to check how many confirmations it has received; some networks take longer than others
3. **Check whether the token has been added in the app** — ERC-20, BEP-20, Polygon, Arbitrum, and other custom tokens must be added manually before they appear; tap **Add Token** in the app to add it
4. **Refresh the app** — pull down to refresh, or close and reopen the ELLIPAL App

***

### Issue 3: Funds sent on the wrong network

{% hint style="warning" %}
Sending to the wrong network is one of the most serious receiving issues. Recovery is not always possible and ELLIPAL cannot retrieve the funds on your behalf.
{% endhint %}

If this happens, act immediately:

1. Save the TXID (transaction hash) from the sending platform
2. Confirm the exact network the sender used
3. Contact ELLIPAL Support as soon as possible with the TXID — include the network used and the amount sent

***

### FAQ

<details>

<summary><strong>Do I need to sign anything when receiving?</strong></summary>

No. Receiving crypto does not require any signature or action on your ELLIPAL device or in the app. Just share your address and wait for the transaction to confirm on the blockchain.

</details>

<details>

<summary><strong>Do I need a Memo or Destination Tag?</strong></summary>

For personal ELLIPAL wallets, usually not. Only provide one if the sending platform — typically an exchange — explicitly requires it. If required, a simple numeric value such as `0` or `1` is usually accepted.

</details>

<details>

<summary><strong>Why does the token value show as 0?</strong></summary>

The app may not have real-time price data for that token. The actual token balance should still display correctly — the zero value reflects a missing price feed, not a missing balance.

</details>

<details>

<summary><strong>How long does it take for funds to appear?</strong></summary>

It depends on the blockchain. Some networks confirm in seconds; others may take several minutes or longer during periods of high traffic. Check the confirmation count on a block explorer using the TXID if funds have not appeared after the expected time.

</details>

***

### View Receiving Address

{% columns %}
{% column %}
**Titan 2.0**

{% content-ref url="/spaces/gvuKn3cqyEbasFpMIrmp/pages/oxxjitJQH0ocu0sdhz30" %}
[View Receiving Addresses](/titan-2.0/view-receiving-addresses.md)
{% endcontent-ref %}
{% endcolumn %}

{% column %}
**X Card**

{% content-ref url="/spaces/gvuKn3cqyEbasFpMIrmp/pages/kWnQJj7tPDmMVF0gJsCk" %}
[View Receiving Addresses](/x-card/view-receiving-addresses.md)
{% endcontent-ref %}
{% endcolumn %}
{% endcolumns %}

{% content-ref url="/spaces/mEC6cK465Vpdm1PdRmFl/pages/vY1TBPgjlfWxlwJD7And" %}
[What should I do if I sent assets to the wrong network?](/troubleshooting-and-support/what-should-i-do-if-i-sent-assets-to-the-wrong-network.md)
{% endcontent-ref %}

{% content-ref url="/spaces/mEC6cK465Vpdm1PdRmFl/pages/yzVUuBdq4rSWTuN5cAQP" %}
[Broken mention](broken://spaces/mEC6cK465Vpdm1PdRmFl/pages/yzVUuBdq4rSWTuN5cAQP)
{% endcontent-ref %}