Refund Guidelines for Stuck Transactions
Last updated
Was this helpful?
Last updated
Was this helpful?
When conducting cross-chain transactions on the Rubic platform, most are completed within 2–10 minutes (depending on the chosen networks and provider). However, due to the nature of such transactions, they may occasionally get stuck, requiring refunds from the provider.
The transaction exceeds the deadline set by the provider (e.g., 90 minutes).
An incorrect wallet address is specified by the user for receiving funds in the target network.
The sent token or the token to be received is not supported by the provider.
Due to gas price changes during the exchange process, the paid amount of gas is not sufficient to cover the gas fee in the target network.
Token price changes during the transaction execution, causing the transaction to get stuck due to the set slippage.
The user receives the originally sent token in the source network.
The user receives a pool token (e.g., USDC, USDT, WETH, ETH) in either the source or target network.
Website LiveChat widget on or
Telegram Support Bot:
Discord ticket system:
Rest assured, when using Rubic, your funds are always safe!