Read the docs
← All use cases

Crypto deposits for exchanges. Every chain your users hold, one deposit integration.

Supporting deposits on a new network usually means running its nodes, watching its addresses, sweeping funds and reconciling them. Users still arrive holding assets you don't list, on chains you don't run.

Flashnet gives each user a permanent deposit address on every source chain and delivers the asset you choose, on the chain you choose, from USDC on Solana to USDC on Hyperliquid's HyperCore. One integration covers Bitcoin, Lightning, EVM chains, Solana, Tron, XRP, Zcash and more.

Read the docs
Annual volume
$5.5B+
Settlement
<10s
Uptime
99.99%
Minimum
$1.00
Maximum
>$50M

How it works

  1. 01Map users to addressesYour own customer reference returns permanent addresses on each source chain; the same request always returns the same ones.
  2. 02Users deposit what they holdAny supported asset on its chain, from a wallet or another exchange, to the address for that chain.
  3. 03Flashnet delivers your assetDeposits are verified, confirmed under Flashnet's policy, converted within your slippage and delivered to your destination.
  4. 04Reconcile by referenceList deposits by reference, follow them by webhook or event stream, and pause conversion on any address without losing deposits.

Why Flashnet

In code

Permanent addresses for customer 4821, one per source chain, every deposit converting to USDC on Solana at your hot wallet. Choose the destination from GET /v1/standing-deposit-addresses/destinations.

curl -X PUT https://orchestration.flashnet.xyz/v1/standing-deposit-addresses/customer-4821 \
  -H "Authorization: Bearer SERVER_KEY" \
  -H "X-Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{
    "destination": { "chain": "solana", "asset": "USDC", "address": "YOUR_HOT_WALLET" },
    "slippageBps": 50,
    "refundAddresses": { "base": "0xYourBaseRefundAddress", "solana": "YourSolanaRefundAddress" }
  }'

# Then list what arrived, newest first:
curl "https://orchestration.flashnet.xyz/v1/standing-deposit-addresses/customer-4821/deposits?limit=50" \
  -H "Authorization: Bearer SERVER_KEY"

Questions

Do we need to run nodes for every chain?

No. Flashnet watches the source chains, verifies each deposit and its sender, applies its confirmation policy and delivers to your destination. You read deposits by your own customer reference.

Can users deposit assets we don't list?

Yes, wherever Flashnet routes them. Every eligible deposit converts to the one asset you set as the destination, so you credit a single asset however the user funded. A deposit of the destination asset on its own chain is held rather than converted, since there's nothing to convert.

Can deposits go straight to Hyperliquid?

Yes. Flashnet delivers USDC and USDe to HyperCore from its other networks, so a user can fund a Hyperliquid account from Bitcoin, Solana or an EVM chain in one order.

What happens to dust and deposits that can't convert?

Deposits below a route's minimum on EVM chains and Solana are held and can batch with later deposits of the same asset to the same address. Bitcoin outputs are independent, so each must cover its own minimum. Held deposits can be returned to a refund address on request.

How fast is Bitcoin credited?

An eligible Bitcoin deposit can get a ZeroConf offer to credit it before the first confirmation, for a fee the offer states. For permanent addresses it needs allowlisting and your consent per deposit; without it, the deposit waits for 1 confirmation.