> ## Documentation Index
> Fetch the complete documentation index at: https://apidocs.bridge.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Multichain and Multicurrency Liquidation Addresses

<Note>
  This feature is in Beta.
</Note>

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>
  Note that we do not support this feature for Stellar at the moment
</Note>

Multichain and multicurrency liquidation addresses use the same [Create a Liquidation Address API](/api-reference/liquidation-addresses/create-a-liquidation-address) as standard liquidation addresses. You opt in by setting specific values for `chain` and/or `currency`:

| Field      | Value           | Effect                                                                                                           |
| ---------- | --------------- | ---------------------------------------------------------------------------------------------------------------- |
| `chain`    | `evm`           | Generates an EVM deposit address usable across **any supported EVM chain** (e.g. Ethereum, Polygon, Base, Tempo) |
| `currency` | `all_supported` | Generates a deposit address that can accept **any currency** Bridge supports on the given chain(s)               |

**1. Multichain.** Set `chain` to `evm`:

```json Request Body theme={null}
{
  "chain": "evm",
  "currency": "usdt",
  "external_account_id": "external_account_a1b2c3",
  "destination_wire_message": "alice_wire_123",
  "destination_payment_rail": "wire",
  "destination_currency": "usd"
}
```

**2. Multicurrency.** Set `currency` to `all_supported`:

```json Request Body theme={null}
{
  "chain": "ethereum",
  "currency": "all_supported",
  "external_account_id": "external_account_a1b2c3",
  "destination_wire_message": "alice_wire_123",
  "destination_payment_rail": "wire",
  "destination_currency": "usd"
}
```

**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:

```json theme={null}
"supported_currencies": {
  "ethereum": ["eurc", "usdc", "usdt"],
  "polygon": ["usdc"],
  "base": ["eurc", "usdc"]
}
```

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

<Note>
  `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.
</Note>

<Danger>
  **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.
</Danger>

## Crypto returns

Please remember to set up a crypto return policy! Read more [here](/platform/orchestration/more/returns).

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

<Note>
  The `supported_currencies` values shown below are illustrative only, and don't necessarily reflect what a given request will actually return.
</Note>

### Multichain Only

Accepts one currency, across all supported EVM chains.

```json Request Body theme={null}
{
  "chain": "evm",
  "currency": "usdc",
  "external_account_id": "external_account_a1b2c3",
  "destination_wire_message": "alice_wire_123",
  "destination_payment_rail": "wire",
  "destination_currency": "usd"
}
```

```json Response Body theme={null}
{
  "id": "liquidation_address_001",
  "chain": "evm",
  "address": "0xabc123...",
  "currency": "usdc",
  "customer_id": "customer_xyz",
  "external_account_id": "external_account_a1b2c3",
  "destination_payment_rail": "ach",
  "destination_currency": "usd",
  "state": "active",
  "created_at": "2026-09-02T12:00:00.000Z",
  "updated_at": "2026-09-02T12:00:00.000Z",
  "supported_currencies": {
    "ethereum": ["usdc"],
    "polygon": ["usdc"],
    "base": ["usdc"]
  }
}
```

### Multicurrency Only

Accepts any supported currency, but only on one chain.

```json Request Body theme={null}
{
  "chain": "ethereum",
  "currency": "all_supported",
  "external_account_id": "external_account_a1b2c3",
  "destination_wire_message": "alice_wire_123",
  "destination_payment_rail": "wire",
  "destination_currency": "usd"
}
```

```json Response Body theme={null}
{
  "id": "liquidation_address_003",
  "chain": "ethereum",
  "address": "0x789abc...",
  "currency": "all_supported",
  "customer_id": "customer_xyz",
  "external_account_id": "external_account_a1b2c3",
  "destination_payment_rail": "ach",
  "destination_currency": "usd",
  "state": "active",
  "created_at": "2026-09-02T12:00:00.000Z",
  "updated_at": "2026-09-02T12:00:00.000Z",
  "supported_currencies": {
    "ethereum": ["eurc", "usdc", "usdt"]
  }
}
```

### Multichain and Multicurrency

Accepts any supported currency, across all supported EVM chains.

```json Request Body theme={null}
{
  "chain": "evm",
  "currency": "all_supported",
  "external_account_id": "external_account_a1b2c3",
  "destination_wire_message": "alice_wire_123",
  "destination_payment_rail": "wire",
  "destination_currency": "usd"
}
```

```json Response Body theme={null}
{
  "id": "liquidation_address_002",
  "chain": "evm",
  "address": "0xdef456...",
  "currency": "all_supported",
  "customer_id": "customer_xyz",
  "external_account_id": "external_account_a1b2c3",
  "destination_payment_rail": "ach",
  "destination_currency": "usd",
  "state": "active",
  "created_at": "2026-09-02T12:00:00.000Z",
  "updated_at": "2026-09-02T12:00:00.000Z",
  "supported_currencies": {
    "ethereum": ["eurc", "usdc", "usdt"],
    "polygon": ["usdc"],
    "base": ["eurc", "usdc"]
  }
}
```