If you are having trouble sending funds, you are likely running into one of two scenarios. Either you are unable to initiate the transaction, or something went wrong during the transaction. If something goes wrong during the transaction, the first step is to check your transaction status on CeloScan. If there are any errors listed, this will help you pinpoint the issue. If you are getting any in-app errors, please contact support with your logs and a screenshot.
Let’s explore some common reasons for failed or invalid transactions and how to resolve them.
Valora checks if you input a properly formatted address. For example, if the address is missing a character or does not have “0x” at the beginning of the address, then you will not be able to send any funds.
Valora recommends that, when possible, users do test transactions of very small amounts before sending a large amount of funds or sending them to a wallet address for the first time.
You can avoid typos by copying and pasting the address and comparing the first 4 and last 4 characters to ensure you copied the entire address correctly.
There is a fee for every blockchain transaction. You need to have enough of the correct asset in your wallet to be able to pay for gas fees. While Valora allows fees to be paid using CELO or any of the Celo stablecoins, most dapps or wallets only accept fees paid with CELO.
You can find out if you have a gas fee error by looking at the Transaction Details page for your transaction on a blockchain explorer. The following error messages may indicate a gas fee error:
- “Error: execution reverted”
- “Insufficient funds for gas * price”
You can resolve this error by maintaining a balance of at least 0.01 CELO or reducing the send amount if it is also being used to pay fees.
Rarely, there could be issues with the blockchain itself. These may occur from congestion, attacks, bugs, or updates. If your transactions are continuously failing, check the blockchain’s social media pages for news. If there are no posts detailing outages, then you may need to wait and try again later.
If none of the above reasons apply to your situation, it’s possible that you are running into a bug. Contact us directly with your logs attached so that we can resolve this as soon as possible.