Skip to main content
This slippage error appears when the expected return amount is lower than the minimum accepted threshold. It often happens due to market volatility or low liquidity.
This error indicates a price change between the quote and execution. To resolve it, increase the slippage tolerance. Be cautious—higher slippage can result in worse rates.If you’re using the SDK, implement acceptExchangeRateUpdateHook and return true to accept updated rates automatically. Refer to the SDK docs: acceptExchangeRateUpdateHook
Some versions of Mayan (mayanWH and mayanMCTP) do not support smart contract addresses as destinations.
Mayan MCTP uses CCTP, which has slower settlement times and higher gas costs on Ethereum. It is generally used for large transfers when other bridges lack liquidity.
This usually means the fromAddress does not have enough funds to cover the transaction.
This message appears when the transaction has not yet been indexed by LI.FI. Once it is indexed, the scanner will display its details.
This code likely represents a custom error from the DEX, such as MinimalOutputBalanceViolation. Most swap failures come from DEX-level checks. If not, LI.FI applies its own fallback checks. Error codes may vary by provider.
Refund policies depend on the bridge. Some bridges issue refunds automatically; others may leave transactions unresolved.
This substatus usually comes from cBridge. It means the transfer could not be processed due to price, gas, or liquidity issues. LI.FI will then trigger a refund on the source chain.
PARTIAL is a final status. The user receives the full value, but in a different token than expected.
LI.FI blocks quotes if the wallet has no SOL. This prevents failures from rent and gas fees. To fetch rates without requiring a funded wallet, use the /routes endpoint without specifying a wallet address.
⌘I