Skip to main content

What Are Deposit Addresses?

Deposit addresses let users bridge without connecting a wallet. Instead of initiating a bridge from a connected wallet, users send funds to a designated address provided by Bungee, and Bungee routes funds to the destination chain and delivers tokens to the user’s wallet after processing. This makes it easy to onboard users to a new chain or fund a destination wallet from sources like CEX withdrawals or fiat on-ramps. Once generated, a deposit address expires after 10 minutes and is valid for only a single deposit transaction. This flow is useful when you want:
  • A direct transfer flow from the source wallet
  • To support flows where wallet connection is unavailable or intentionally skipped
  • To onboard users onto a new chain with a single, simple “send to this address” step

How It Works

  • Depositing funds The deposit transaction requires no calldata. You simply send the agreed amount to the deposit address returned by the API. As long as the amount covers the costs, it will be automatically bridged according to the route from the original quote.
  • Gas and fee considerations For low-value transfers, the gas costs overhead can be significant, so we generally do not recommend deposit addresses for low-value bridging.
  • Post-deposit quote recalculation After a deposit is detected, the quote is re-generated to account for gas price fluctuations and to recompute all fees. This means the final received amount may differ from the initial quote, but it will always respect the minimum amount specified. If the minimum amount cannot be achieved, the deposit amount is refunded on the origin chain.
  • Refund behavior Failures via deposit addresses are extremely rare, but still possible. By default, Bungee will automatically refund the funds on the origin chain to the refundAddress in your quote request. Any filling failure will then refund to this address.

Common Use Cases

  • CEX withdrawals that should arrive on a different destination chain.
  • Fiat on-ramp to app onboarding where users should end up directly on the app’s preferred chain.
  • Embedded/headless flows where wallet connection is unavailable or intentionally skipped.

Integration Guide

For the full implementation details, including request/response formats and lifecycle handling, see the Deposit route integration guide.