I can't withdraw funds

If you can't move your funds – first of all – don’t worry, your funds are always safely stored on the blockchain. You can contact us via the official support form. We will try our best to help you with the issue. 


There are various reasons why you are not able to send your funds out of Atomic Wallet. Here is a short overview of the most popular reasons for this issue along with some steps you can take to fix it on your end.

Connection issues

The most popular reason why you can't send out your funds is a connection issue. In that case, you may get this error:

If you get this message, don’t worry. Most likely, there is a connection issue. Atomic Wallet connects directly to blockchain nodes to create a transaction. Sometimes, this connection can be unstable or blocked due to various reasons such as CloudFlare blocks or Internet speed instability. Here is a step-by-step guide on what you can do to fix the issue. 

  1. Before proceeding to any actions, make sure that you have our latest version or download it from our website.
  2. Reload the wallet. Close the wallet completely and then open it again. Here is the instruction.
  3. Use a VPN. Install VPN on your device and change the country. Germany, the USA, and Switzerland may be the best choice. 
    If you are already using a VPN, try turning it off. 
  4. Check your Internet connection and see if you can access other crypto-related websites via your browser. 

Fee requirements 

Tokens usually require a network fee to be paid with a coin that is different from the token itself. Take a look: 

So you might have plenty of AWC tokens, for example, but none of the BNB-BSC that is required to cover the fees. More about coins and tokens here. And here are some examples of tokens that you might see this error with:

  • ETH-powered assets or ERC-20 tokens require a small amount of ETH on your balance, in order to pay a network fee. Read more about it here
  • TRC tokens or tokens that run on the TRX blockchain will require you to pay the fee in TRX. 
  • BEP-2 tokens, or BNB tokens, require the fee to be paid in BNB. 
  • BEP-20 tokens, or BSC tokens, require a fee to be paid in BNB-BSC. More about BNB and BSC here
  • Polygon-based tokens, such as USDT, require a fee to be paid in MATIC. Keep in mind, however, that there is an ERC-20 MATIC token and the Polygon MATIC. You need the latter. More about it here.
  • Optimism USDT and other Optimism-based tokens will require you to cover the fee in OP.  

Asset-specific fees 

EOS requires specific resources to be spent on every transaction. If you are not able to move EOS, you may be out of resources. You can check your balance on the block explorer to make sure you've got enough CPU, RAM, and GPU to make a transaction. If you find out that you're lacking resources, simply borrow them

What you can do: deposit a small amount of the coin (or resources) you need to pay a network fee out of. 

Insufficient Funds 

You may get an error message, saying "You'll need more X to make this transaction": 

Consider the fees 

The most obvious explanation is that you are trying to send more funds than you have in your wallet. This may happen if you are not accounting for the network fees. For example, you have 0.1 BTC in your wallet and you try to send out 0.1 BTC without considering the fact that 0.01 BTC will be paid as the network fee, making it so you can only send 0.09 BTC. If you don't want to deal with the fee calculation yourself, simply click 'Send All' and the wallet will automatically fill the amount you can send.  

Minimal balance 

XLM, XRP, DOT, ALGO, and XTZ have an unspendable balance. 1 XLM, 10 XRP, 1 DOT, 0.1 ALGO, and 0.27 XTZ. That means, that if you have 10 XRP, you won't be able to withdraw it, since they have to stay on your address. This is a blockchain rule.  

What you can do: check if that’s the case for you and try a smaller amount. You can also press Send All to automatically take out the network fee and send all your available balance.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.