Common Sending Issues and Solutions
Troubleshoot the most common sending issues with ELLIPAL — invalid address, insufficient funds, missing memo, wrong network, signing failed, and more. Includes solutions for each problem.
To send crypto with ELLIPAL, create the transaction in the ELLIPAL App and complete the signing on your device. ELLIPAL Titan 2.0 signs via QR codes; ELLIPAL X Card signs via NFC by entering the Card-PIN and tapping the card to your phone. Once signed, the app broadcasts the transaction to the blockchain.
Issue 1: Address is invalid or not accepted
The recipient address does not match the selected coin or network, or the pasted address is incomplete.
What to do:
Double-check the coin name and network on both the sending and receiving side
Copy and paste the address again to rule out manual input errors
Use the Scan function in the ELLIPAL App if possible — scanning avoids typos entirely
Issue 2: Insufficient funds
Your balance is not enough to complete the transaction — either the token balance is too low, or there is not enough native coin to cover the network fee.
What to do:
Reduce the send amount, or top up the native coin balance needed for gas
Common examples: ETH for Ethereum transactions, BNB for BNB Smart Chain transactions
Avoid sending your full balance — always leave a small amount to cover the fee
Issue 3: Network fee is too high or transaction is stuck
Network congestion can cause fees to spike or pending transactions to be delayed.
What to do:
If the fee looks unusually high, wait and try again when the network is less busy
If the transaction has already been sent, look up the TXID on a block explorer to check its confirmation status
Do not send a second transaction to the same address while the first is still pending
Issue 4: Missing Memo or Destination Tag
Some exchanges require a Memo, Destination Tag, or similar field to credit your account. If this field was left blank, the transaction may confirm on-chain but not be credited by the exchange automatically.
What to do:
Stop sending further transactions to the same deposit address
Contact the receiving exchange's support team with the following:
Transaction hash (TXID)
Your sending wallet address
Blockchain name and network
Transaction time and amount
ELLIPAL cannot reverse a transaction after it has been signed and broadcast. Recovery depends entirely on the receiving platform.
Issue 5: Wrong network was used
Sending on the wrong network is one of the most common and serious sending mistakes. The recipient may not receive the funds, and recovery is not guaranteed.
What to do immediately:
Stop sending any further transactions to the same address
Save the TXID from the ELLIPAL App or block explorer
Confirm which network was actually used
Contact the receiving platform or recipient first — if they control the destination address, they may be able to recover the funds
Contact ELLIPAL Support with the TXID if you are unsure how to proceed
Issue 6: Signing failed
If a transaction fails during the signing process, the most common causes are: the app and device are not fully synced, the wrong QR code was scanned or scanned in the wrong direction, NFC signing did not complete because the card was moved away too early, or a temporary app or device issue.
What to do:
Restart the signing process from the beginning
Make sure you are scanning the correct QR code in the correct direction — the Titan scans the Unsigned QR Code from the app, and the app scans the Signed QR Code from the Titan
Reconnect or re-sync the device with the ELLIPAL App if needed
Issue 7: Transaction submitted but recipient has not received it
This does not always mean the transaction failed — it may still be confirming on the blockchain.
What to do:
Look up the TXID on a block explorer to check the confirmation status
Confirm that the recipient is checking the correct network and wallet address
Wait for additional confirmations — some networks take longer during high-traffic periods
Ask the receiving platform to check the deposit status if the TXID shows as confirmed but funds have not appeared
FAQ
Titan 2.0
Send Crypto with TitanX Card
Send Crypto with X CardLast updated
Was this helpful?

