Read the docs
← Crypto deposit APIs compared

LI.FI alternatives for deposits. For deposits from any chain.

Checked October 27, 2026.

Why teams taking deposits look past LI.FI

LI.FI picks a route across third-party bridges, DEXs and solvers, among them Relay, NEAR Intents, Across and Mayan, and returns a transaction for the user to sign. Funds in transit sit with whichever provider fills each step.

Best for: Wallets that want one SDK over many bridges and DEXs for swaps their users sign. What teams taking deposits run into:

  • Deposit addresses are a gated enterprise feature, single-use and valid for 24 hours.
  • If a bridge step lands but the swap after it fails, the user is refunded on the destination chain in the bridged asset.
  • No webhooks and no Lightning: integrations poll for status every 10 to 30 seconds.

The alternatives

  1. 1. Flashnet

    Deposits, swaps and withdrawals API

    Best for: Exchanges, prediction markets and wallets whose users fund from anywhere, Bitcoin and Lightning included, by sending to an address.

    Choose Flashnet if users should fund by sending to an address that keeps working, you need Bitcoin or Lightning to land fast, or you want one quote and one order status from deposit to delivery.

  2. 2. Relay

    Intent-based cross-chain protocol

    Best for: Apps whose users sign from connected wallets and want low published fees across a long list of chains.

  3. 3. NEAR Intents

    Intent-based cross-chain protocol with competing market makers

    Best for: Swaps across a very wide set of chains with competing market makers, where per-quote addresses are enough.

  4. 4. deBridge

    Intent-based cross-chain swap protocol

    Best for: DeFi apps whose users already sign from an EVM or Solana wallet and want a guaranteed rate.

How they compare

On the points above, with each fact linked to its source. Every provider on every point is on the comparison page.

LI.FI alternatives for deposits, as of October 27, 2026
FlashnetLI.FIRelayNEAR IntentsdeBridge
Orders
Deposit by sending to an addressYesEvery quote returns a deposit address; paying it creates the order. No wallet connection, approval or contract call.SourcePartlySmart Deposit Addresses are an enterprise feature, enabled per integrator. Native ETH and BNB can't be the input.SourceYesA quote can return a deposit address instead of a transaction to sign.SourceYesA 1Click quote returns a deposit address on the origin chain; the swap starts when funds arrive.SourceNoEvery order is a transaction the user signs. No deposit-address flow is documented.Source
Permanent address per userYesOne permanent address per user and source chain. Every eligible deposit converts to the destination you set.SourceNoEach address is single-use and valid for 24 hours.SourcePartlyOpen addresses can be reused, but only for the same origin and destination token and chain.SourcePartlyAddresses belong to one quote and expire at its deadline. Reusable ANY_INPUT addresses are partner-only and funded inside NEAR Intents.SourceNoNo reusable deposit addresses are documented.Source
Automatic refundsYesOrders that can't fill within the quote's bounds go back to the refund address you set.SourcePartlyIf a bridge step lands but the swap after it fails, the user is refunded in the bridged asset on the destination chain.SourceYesRefunds go to the refundTo address on the origin chain, less gas. Without one, there's no automatic refund.SourceYesUnfilled or underpaid deposits go to your refundTo address after the deadline.SourcePartlyBy default the user cancels on the destination chain. Auto-cancel needs deBridge's approval, and refunds usually arrive as USDC.Source
Networks
LightningYesIn and out over Lightning, including BOLT11 invoices and Lightning addresses.SourceNoNot among LI.FI's chains.SourceNoNot among the chains in Relay's API.SourceNoNot among the supported chains.SourceNoNot among the supported chains.Source
Operations
WebhooksYesWebhooks, plus a server-sent event stream of order status.SourceNoPoll the status endpoint every 10 to 30 seconds.SourceYesWebhooks and a websocket status stream.SourceNoPoll the status endpoint by deposit address.SourceNoPoll the order tracking API.Source