Skip to main content
This feature is in Beta.
Bridge’s flexible liquidation addresses let a single deposit address support:
  1. Multiple chains — For EVM-compatible networks, the same address can be used across any supported EVM chain. For example, your customer can use one address to receive deposits on both Tempo and Base.
  2. Multiple currencies — deposits in any currency Bridge supports for that chain. Previously, your customer needed a separate address per currency — one for USDC, another for USDT. With a multi-currency liquidation address, they can use a single address to accept both.
These two capabilities are independent: you can enable one, the other, or both on the same address.

How to Create a Multichain or Multicurrency Liquidation Address

Note that we do not support this feature for Stellar at the moment
Multichain and multicurrency liquidation addresses use the same Create a Liquidation Address API as standard liquidation addresses. You opt in by setting specific values for chain and/or currency: 1. Multichain. Set chain to evm:
Request Body
2. Multicurrency. Set currency to all_supported:
Request Body
3. Both. Set chain to evm and currency to all_supported — see the examples below.

Determining What’s Supported: supported_currencies

Every Liquidation Address response — from POST, PUT, and GET — includes a supported_currencies field, mapping each supported chain to the currencies your customer can send to that address:
This field is computed from three factors:
  1. What you requested when creating the address — a specific chain/currency, or evm / all_supported
  2. What Bridge supports overall, across chains and currencies
  3. What your customer has access to, which may depend on factors like where they reside
supported_currencies can change over time, independent of anything you do. As Bridge adds chains or currencies, or your customer’s access expands, new entries may appear.Because of this, don’t cache supported_currencies long-term — re-fetch the Liquidation Address (GET) before relying on it, especially before showing deposit instructions to a customer.
Bridge does not support returning unsupported currencies. Funds sent in a currency not listed in supported_currencies may be unrecoverable. Always check supported_currencies before instructing a customer to send funds, and never let them send an asset that isn’t listed.

Crypto returns

Please remember to set up a crypto return policy! Read more here. Note that for multichain / currency liquidation addresses, we do not support the return_instructions or return_address fields at the moment. The crypto return policy is the only supported crypto return mechanism for this feature.

API Examples

The supported_currencies values shown below are illustrative only, and don’t necessarily reflect what a given request will actually return.

Multichain Only

Accepts one currency, across all supported EVM chains.
Request Body
Response Body

Multicurrency Only

Accepts any supported currency, but only on one chain.
Request Body
Response Body

Multichain and Multicurrency

Accepts any supported currency, across all supported EVM chains.
Request Body
Response Body