Bitlease Help Center
Help Center/Troubleshooting/Common Deposit Errors and Solutions

Common Deposit Errors and Solutions

Last updated on March 11, 2026

Transaction Never Reaches Blockchain

Symptom

You initiated withdrawal from external wallet, but blockchain explorer shows no transaction when you search your transaction ID or destination address.

Problem

  • Insufficient gas/network fee

  • Incorrect password or authentication failure

  • Wallet connectivity issues

  • Exchange withdrawal restrictions

Solutions

Solution 1: Verify Transaction Status at Source

  1. Log in to the wallet or exchange where you initiated withdrawal

  2. Navigate to transaction history or withdrawal history

  3. Locate your withdrawal attempt

  4. Check the status

If status shows failure:
Read the failure reason carefully. Common reasons include insufficient balance for fees, security hold, or verification required.

Solution 2: Increase Network Fee and Retry

If the transaction failed due to low fee:

  1. Cancel the failed transaction if it remains pending

  2. Initiate new withdrawal

  3. Set gas/network fee to "Medium" or "High" priority

  4. Confirm new transaction

  5. Monitor for successful broadcast

Network fee logic:
Higher fees incentivize validators to process your transaction faster. During network congestion, low-fee transactions may never confirm.

Solution 3: Complete Required Verifications

If the exchange shows security hold or verification requirement:

  1. Navigate to the security or verification section

  2. Complete any pending identity checks

  3. Confirm email or 2FA if requested

  4. Wait for hold to lift (typically 24 hours for new verifications)

  5. Retry withdrawal

Solution 4: Contact Source Platform

If the transaction shows as completed at the source but the blockchain shows nothing:

  1. Gather transaction ID from the source platform

  2. Note exact timestamp of the withdrawal

  3. Contact source platform support

  4. Provide transaction ID and timestamp

  5. Request investigation

The source platform can verify whether the transaction actually broadcast.

Transaction Stuck on Blockchain

Symptom

Blockchain explorer shows your transaction, but it remains unconfirmed for extended period (hours or days depending on network).

Problem

  • Insufficient network fee for current conditions

  • Network congestion

  • Nonce conflict (Ethereum-based chains)

Solutions

Solution 1: Wait for Network Congestion to Clear

For Bitcoin:
Check current mempool size at mempool.space. If mempool is large (100+ MB), congestion exists. Your transaction will confirm when congestion reduces.

For Ethereum:
Check current gas prices at etherscan.io/gastracker. If prices are high (100+ Gwei), congestion exists.

Waiting logic:
Network congestion is temporary. Most transactions confirm within 24-72 hours even during severe congestion. If your transaction has been pending less than 48 hours and you used reasonable fees, waiting is often the most efficient solution.

Solution 2: Use Replace-by-Fee (RBF) If Available

Some wallets allow fee increases for pending transactions.

If your sending wallet supports RBF:

  1. Locate the pending transaction in your wallet

  2. Select "Increase Fee" or "Speed Up" option

  3. Set higher fee (typically 50-100% increase)

  4. Confirm the fee bump

  5. New transaction replaces old one with same destination but a higher priority

Bitcoin wallets with RBF: Electrum, Bitcoin Core, some hardware wallets
Ethereum wallets with speed-up: MetaMask, MyEtherWallet

Important: This increases your total fee cost. Evaluate whether faster confirmation justifies the expense.

Solution 3: Check Transaction Age

Bitcoin:
Transactions pending more than 72 hours may be dropped from the mempool. If dropped, funds return to sender. You can retry with a higher fee.

Ethereum:
Transactions rarely drop. They remain pending until confirmed or replaced.

If the transaction is dropped:
Funds automatically return to your sending address. Wait for the balance to reflect the return, then initiate new withdrawal with the appropriate fee.

Solution 4: Transaction Acceleration Services

Some mining pools offer transaction acceleration for stuck Bitcoin transactions.

Process:

  1. Visit acceleration service (ViaBTC, BTC.com)

  2. Enter your transaction ID

  3. Submit for acceleration

  4. Miners prioritize your transaction

Limitations:

  • Often requires the transaction to meet minimum fee thresholds

  • May have daily submission limits

  • Not guaranteed, but often effective

Wrong Deposit Address

Symptom

Transaction confirmed successfully on correct network. But funds went to an address that is not your Bitlease deposit address.

Problem

  • Copied address incorrectly

  • Address book mistake

Solutions

Solution 1: Verify the Destination Address

Check the transaction on blockchain explorer:

  1. Locate transaction on appropriate explorer

  2. Note the "To" address where funds actually went

  3. Compare with your Bitlease deposit address (copy fresh from Bitlease)

  4. Verify character-by-character or use comparison tool

Address comparison method:
Copy both addresses to text editor. Place one above the other. Compare visually. Even one character difference means wrong address.

Solution 2: Recovery Attempts

If funds went to unintended recipient:

For exchange addresses:
Some exchanges can identify if an address belongs to their users and facilitate return through their support process. Contact the exchange where the address exists, provide transaction ID, explain the error.

For personal wallet addresses:
If you control both sender and accidental recipient addresses, simply transfer from recipient to correct destination.

For unknown addresses:
Cryptocurrency transactions are irreversible. If you cannot identify or contact the recipient, recovery is not possible.

Prevention measures for future:

  • Always verify first few and last few characters of address before confirming

  • Use address whitelisting features when available

  • Send small test amount before large deposits

  • Never rely solely on clipboard - verify visually

Minimum Deposit Threshold Not Met

Symptom

Transaction confirmed. Correct address. Correct network. But amount is too small and platform did not credit the deposit.

Problem

Amount below minimum deposit threshold
Platform requires minimum deposit amounts. Transactions below this threshold are not processed.

Dust amount
Extremely small amounts are often not credited because processing fees exceed deposit value.

Solutions

Solution 1: Check Minimum Deposit Requirements

Before depositing:

  1. Navigate to Bitlease deposit section

  2. Select the cryptocurrency you want to deposit

  3. Look for minimum deposit amount displayed

  4. Ensure your deposit exceeds this minimum

Typical minimum deposits:

  • Bitcoin: 0.0001 BTC

  • Ethereum: 0.01 ETH

  • USDT: 10 USDT

  • USDC: 10 USDC

(These are examples; actual minimums vary by platform)

Solution 2: Send Additional Amount to Reach Minimum

If you sent below minimum:

The original amount is not lost. It exists at the deposit address. You can send an additional amount to reach the minimum threshold.

Process:

  1. Calculate how much more is needed to reach minimum

  2. Send the additional amount to same deposit address

  3. Wait for confirmations

  4. Platform should credit combined total if it exceeds minimum

Example:

Minimum deposit: 10 USDT
Your first deposit: 5 USDT (too small, not credited)
Your second deposit: 10 USDT (combined 15 USDT, now credited)

Platform recognizes combined total and credits your account

Suspended or Restricted Account

Symptom

Transaction confirmed on blockchain to correct address, but account balance does not update. Account shows restriction notice or deposit capability is disabled.

Problem

  • Pending KYC verification

  • Security hold

  • Regulatory restriction

  • Terms of service violation

Solutions

Solution 1: Complete Required Verifications

Check account status:

  1. Log in to Bitlease

  2. Navigate to Account Settings

  3. Review verification status section

  4. Look for pending requirements

If KYC is pending:
Complete identity verification process. Upload required documents. Wait for approval. Deposits will be processed after verification completes.

If address verification is pending:
Complete address verification. Upload proof of address. Wait for approval.

Solution 2: Contact Support for Account Review

If account shows restriction:

Do not send additional deposits until restriction is resolved.

Contact support:

  • Email: support@bitlease.com

  • Subject: "Account Restriction - Pending Deposit"

  • Include: Your registered email, description of restriction notice, any pending transaction IDs

Support will:

  • Review account status

  • Explain reason for restriction

  • Provide steps to resolve

  • Process pending deposits after resolution

Solution 3: Review Terms of Service Compliance

If account was suspended for policy violations:

Review the notification explaining the suspension. Understand which policy was violated. Contact support only if you believe the suspension was in error.

If suspension is valid:
Follow the process outlined in the suspension notice. Some suspensions allow withdrawal of existing funds but not new deposits. Others require dispute resolution.

When to Contact Support

Contact Bitlease Support if:

  • Transaction has 50+ confirmations on correct network but not credited

  • You sent to correct address on wrong network (cross-network recovery)

  • You sent native currency instead of token to token address

  • Account shows restriction preventing deposit processing

  • Blockchain shows "Failed" transaction but you need explanation

  • You believe platform error occurred (not user error)

Need Help?

Contact Bitlease Support:

For account access issues, provide:

  • Your registered email address

  • Description of the problem

  • Any error messages you see

  • Steps you already tried

Support can help if you cannot complete the automated process.