Deposit troubleshooting
What to do when a crypto deposit is not showing, was sent on the wrong chain or as the wrong asset, or a Lightning or Bitcoin payment is stuck.
Most deposit problems have one of a few causes. Run through these checks first, and keep your transaction hash ready.
Deposit not showing
- Find the transaction hash in your wallet or exchange history and open it in the chain's block explorer.
- Check confirmations. If the explorer shows fewer confirmations than Fundly requires, wait. Bitcoin takes 20 to 30 minutes; most other chains take 1 to 3 minutes. See the table on the deposits overview.
- Check the amount. At launch, deposits below 10 EUR equivalent (20 EUR on Ethereum mainnet and Bitcoin) are not credited automatically. Support can recover them for a fee.
- Check the network. EVM chains share the same
0xaddress, so a transfer meant for Polygon can land on Ethereum or BNB Chain. Compare the explorer with the chain you chose in Fundly. - Check the asset. Only the assets listed on each chain page are credited.
- Check for a pending conversion. "Converting" means the deposit arrived and is being exchanged into your account currency, usually within a minute.
Sent the wrong asset or wrong chain
- Supported chain, supported asset, wrong deposit screen. For example, USDC sent on Base while the Ethereum screen was open. Usually credited automatically or recoverable by support.
- Supported chain, unsupported asset. Support may recover it for a fee; not guaranteed.
- Unsupported chain. Usually not recoverable; Fundly holds no keys there.
At launch, the recovery fee is 25 EUR or 5% of the amount, whichever is higher, and recovery can take several business days.
Open a recovery request in the in-app support chat with:
- The transaction hash.
- The chain the funds were sent on.
- The asset and the amount.
- The date and time of the transfer.
- The Fundly deposit address you used.
Lightning invoice expired or payment failed
Fundly Lightning invoices expire after 1 hour. An expired invoice cannot be paid and nothing leaves your wallet, so create a new one. A failure on a valid invoice is usually a routing failure: retry, try a smaller amount (capped at 500 EUR equivalent per invoice at launch), or use an on-chain Bitcoin deposit. If a payment shows "in flight", do not pay a second invoice until the first has clearly failed.
Bitcoin stuck with a low fee
A low-fee Bitcoin transaction can wait hours when the mempool is busy. Fundly credits after 2 confirmations and treats replace-by-fee transactions as unconfirmed until then. Bump the fee with RBF or child-pays-for-parent if your wallet supports it, or wait; the deposit is credited once it confirms.
Quick reference
| Symptom | Likely cause | What to do |
|---|---|---|
| Pending in app for a few minutes | Waiting for confirmations | Wait; check the explorer |
| Confirmed on explorer, not in app | Wrong network or asset, or below minimum | Check all three; contact support with the hash |
| "Converting" in app | Conversion in progress | Wait about a minute |
| Lightning payment fails | Routing failure or expired invoice | New invoice, smaller amount, or on-chain |
| Bitcoin unconfirmed for hours | Low network fee | Bump the fee, or wait |
Related
Fundly is a financial technology company, not a bank. Limits and fees described as “at launch” are proposals and may change.