🛠️Troubleshooting

Try manually increasing the gas LIMIT to 1 000 000. This way, the transaction will only use the gas it needs without running out.

To fix 'SafeERC20: low-level call failed' error, simply increase the gas LIMIT to 1 000 000. This way, the transaction will only use the gas it needs without running out.

If you encounter this issue with MetaMask, the underlying cause remains unclear. However, you can try the following methods to resolve the issue:

1. Consider using an alternative wallet app as a solution.

2. Ensure the BNB network has been added correctly. Refer to our article and find detailed instructions on how to add BNB Smart Chain to your wallet.

3. Ensure you have sufficient BNB balance to cover gas fees.

4. Verify that you are using the app's most recent version or browser extension.

The transaction cannot be completed due to insufficient funds for transfer. Please try again with a sufficient BNB amount to cover the transaction fees.

Increase the gas LIMIT for the transaction in your wallet. Check your wallet's documentation to learn how to increase your gas limit.

The reason behind this issue is currently unclear. Try increasing the gas LIMIT and slippage before trying again.

The exchange on Biswap fails with the error status 'Biswap: TRANSFER_FAILED' when there's an issue with the token transfer during the swap process. This error could be caused by various reasons, such as:

1. Insufficient liquidity: Ensure that there is enough liquidity in the pool for the token you are trying to swap. If the pool has insufficient liquidity, the swap cannot be completed.

2. Approvals: Ensure you have approved the Biswap router contract to spend your tokens.

3. Slippage tolerance: The price of tokens can fluctuate between when you submit your transaction and when it is mined. The transaction will fail if the price moves beyond your slippage tolerance during this time.

4. Gas fees: Ensure you have provided enough gas for the transaction to complete. If the gas supplied is too low, the transaction may fail.

To troubleshoot the issue, double-check these factors and ensure they are correctly configured. Additionally, check Biswap Support if the problem persists.

If you encounter 'INSUFFICIENT_OUTPUT_AMOUNT' error while swapping tokens, low slippage tolerance may be likely the cause. To modify your slippage tolerance, perform the following steps:

1. Head to the settings icon located on the liquidity page.

2. Increase your slippage tolerance gradually and attempt the swap again.

3. Additionally, try entering an amount with fewer decimal places.

Alternatively, 'INSUFFICIENT_OUTPUT_AMOUNT' issue often occurs when exchanging tokens with limited liquidity, indicating that there may not be a sufficient amount of one of the tokens you're attempting to swap in the Liquidity Pool. This is likely due to the token being small-cap and infrequently traded. If the problem persists, you can try refreshing the page, attempting the transaction later, or exploring the option of trading a different token. You may also try to change a fraudulent token that cannot be sold. Biswap cannot restrict the token or refund your funds in such cases.

The 'BiswapV2Router: EXCESSIVE_INPUT_AMOUNT' error occurs when attempting to swap many tokens in a pool or a pool with low liquidity on the Biswap platform. To resolve this issue, try reducing the amount you are trading, rounding off token amounts to avoid tiny fractions, and verifying the pool's liquidity before proceeding with the transaction.

By following these steps, you should be able to successfully execute your token swap on the Biswap platform without encountering the error.

'INSUFFICIENT_A_AMOUNT' or 'INSUFFICIENT_B_AMOUNT' error occurs when adding or removing liquidity from a liquidity pool (LP). There needs to be more quantity of either token A or B in the token pair. Rapid price fluctuations and a low slippage tolerance could be contributing factors.

To resolve the issue, refresh the webpage and attempt the transaction again, or wait and try later.

If the problem persists, navigate to the settings icon on the liquidity page, slightly increase your slippage tolerance, and try the transaction again.

Make sure to confirm the transaction promptly after creating it.

The expiration occurred because the transaction was not signed and broadcasted to the blockchain before the deadline. In other words, you needed to confirm the transaction in your wallet faster.

If this advice doesn't resolve the 'BiswapV2Router: EXPIRED' issue, consider raising the slippage tolerance and clearing your browser's cache as an additional troubleshooting step.

Several possible reasons exist for the 'TransferHelper::transferFrom: transferFrom failed' error during a token swap transaction. To troubleshoot the issue, check the wallet's token balance to ensure sufficient tokens to perform the swap. Verifying the token approval has been granted to the router contract and the allowance is adequate for the desired swap amount.

Additionally, assess the slippage tolerance and consider increasing it. After addressing any relevant issues, resubmit the transaction with the appropriate adjustments.

You're probably trying to unstake from a pool with a low amount of rewards in it. This causes the transaction to fail due to BEP20: transfer amount exceeds allowance.

If not, you may be trying to send tokens you don't have in your wallet (for example, trying to send a token already assigned to a pending transaction). In this case, just ensure you have the tokens you're trying to use.

This occurs when you initially establish a spending cap during the contract approval process and later attempt to use an amount exceeding the cap.

Utilize https://bscscan.com/tokenapprovalchecker to revoke approval for the smart contract you want to engage with. Reapprove the contract, this time setting a higher limit for the spending allowance and attempting to interact with the contract once more.

We've identified an issue when using the Metamask wallet app, where approvals can sometimes be revoked for unknown reasons. If you encounter this issue, please follow the steps below:

1. Clear your browser cache.

2. Approve the contract again.

In this tab, you can enter a number of tokens that can be used by the contract for spending either now or in the future. You should click on the "Use default" button for the maximum amount.

After these steps, everything should work correctly.