Read the docs
← Crypto deposit APIs compared

Flashnet vs LI.FI for deposits

For deposits from any chain. Checked October 27, 2026.

The short answer

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.

Choose LI.FI if your users sign swaps in a wallet, you want one SDK in front of many bridges and DEXs, or you need its widget and DeFi vault deposits.

Read the docs

How each works

Flashnet

Users send to the address on a quote, or to their own permanent address, and Flashnet settles on the destination network, filling from onchain liquidity and its own markets. It holds no user balances; its settlement workers run in AWS Nitro enclaves whose identity integrators can verify.

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.

Side by side

Each fact links to the page it came from.

Flashnet vs LI.FI for deposits, as of October 27, 2026
FlashnetLI.FI
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.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.Source
Firm quotesYesA quote's price holds for 2 minutes within your slippage. Fixed-output quotes commit to the amount out.SourcePartlyOutput bounded by a minimum. Rates are held for 24 hours only on opted-in deposit-address routes.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.Source
Networks
BitcoinYesNative BTC on Bitcoin L1, in and out.SourceYesBy wallet-signed transaction; Bitcoin as a deposit-address source is in beta.Source
LightningYesIn and out over Lightning, including BOLT11 invoices and Lightning addresses.SourceNoNot among LI.FI's chains.Source
Bitcoin credited before confirmationYesEligible deposits can be credited before the first confirmation, for a fee. Otherwise after 1 confirmation.SourceNot documentedIt depends on the bridge filling the route.
Hyperliquid (HyperCore)YesUSDC and USDe delivered to HyperCore.SourceYesDeposits, withdrawals and spot swaps.Source
SolanaYesSOL, USDC, USDT and other SPL tokens.SourceYesSOL and SPL tokens.Source
TronYesTRX and USDT.SourceYesSupported.Source
XRPYesXRP.SourceNoNot among LI.FI's chains.Source
ZcashYesZEC.SourceYesSupported.Source
Fiat
Fiat inYesUsers pay from Cash App or Strike over Lightning and receive BTC or stablecoins.SourcePartlyA Transak checkout in the widget, on EVM chains only.Source
Fiat outYesPay out a deposited asset to a Cash App username or a Lightning address.SourceNot documented
Operations
Your own fee on every orderYesSet a fee per order or per affiliate, from 1 to 9,999 bps, and claim it on the chain and asset you choose.SourceYesA fee percentage, forwarded to your fee wallet.Source
Sanctions and AML screeningYesSource and destination addresses checked with Elliptic and other providers on every order.SourcePartlyToken-risk screening with Hypernative. No documented sanctions or AML screening of deposits.Source
WebhooksYesWebhooks, plus a server-sent event stream of order status.SourceNoPoll the status endpoint every 10 to 30 seconds.Source
Platform feeSet per partner and route, and itemized on every quote.Source0.25% on every transaction, plus the fees of the bridges and DEXs it routes through.Source
Support24/7, with direct access to the engineers who run settlement.A partner portal. No published SLA.Source

Where Flashnet wins

What teams taking deposits run into with LI.FI:

  • 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.

Where LI.FI is strong

  • One API in front of dozens of bridges, DEXs and intent solvers.
  • Broad coverage, from EVM chains to Solana, Bitcoin, Tron, Zcash and Hyperliquid.
  • A mature widget and SDK, with integrator fees built in.

Weighing more than two? See LI.FI alternatives for deposits or every provider side by side. Comparing swaps? See Flashnet vs LI.FI for swaps.

Questions

Does LI.FI support deposit addresses?

As an enterprise feature, enabled per integrator. Each Smart Deposit Address is single-use and valid for 24 hours, and native ETH and BNB can't be the input. LI.FI's standard flow returns a transaction for the user's wallet to sign. Flashnet gives every quote a deposit address and can give each user a permanent one.

Does LI.FI take Bitcoin and Lightning deposits?

LI.FI takes Bitcoin by wallet-signed transaction, Bitcoin as a deposit-address source is in beta, and Lightning isn't among its chains. Flashnet takes native Bitcoin and Lightning deposits and can credit eligible Bitcoin deposits before the first confirmation.

Who settles a LI.FI transfer?

LI.FI is an aggregator: each step is filled by a third party it routes to, such as Relay, NEAR Intents, Across or Mayan, so execution, custody in transit and size limits depend on that provider. With Flashnet, one quote covers the whole order and one order status follows it to delivery.