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

# Bridge across chains

> Move a stablecoin between chains.

Bridging moves the same stablecoin from one chain to another. For shared concepts and the common request fields, see [Convert stablecoins](/knowledge-base/platform/developers/stablecoins/convert). This page covers the bridge-specific payload and behavior.

`POST /v2/stablecoins/conversion` requires the `Convert Stablecoins` permission. See [Set up](/knowledge-base/platform/developers/stablecoins/setup).

## Request

Set `sourceAssetType` and `destinationAssetType` to the same stablecoin on different chains.

```json Example payload theme={null}
{
  "destinationAssetType": "USDX_HOODI",
  "destinationWalletId": "82936bb546cf1fc83955b6d9ca76ff16",
  "idempotencyKey": "z763a50d-aa82-4ec7-b5a3-89ad0462d248",
  "sourceAssetType": "USDX_BSC_T",
  "sourceWalletId": "940afa950652ed4fdffceb73b2745d02",
  "amount": "10"
}
```

| Field                                    | Description                                                                 |
| :--------------------------------------- | :-------------------------------------------------------------------------- |
| `sourceAssetType`                        | Stablecoin on the source chain.                                             |
| `destinationAssetType`                   | Same stablecoin on the destination chain—confirm via `GET /v2/asset-types`. |
| `sourceWalletId` / `destinationWalletId` | Wallet IDs on each respective chain.                                        |
| `idempotencyKey`                         | Unique string ≤128 characters. Use a distinct key per conversion.           |

## Two legs, one record

A bridge produces **one** record in `/v2/stablecoins/history` (`operationType: BRIDGE`) but **two** transactions in `/v2/transactions`—a `BURN` on the source chain and a `MINT` on the destination chain. To inspect both legs, retrieve `sourceOperationId` and `destinationOperationId` from history, then look each up via `GET /v2/transactions/{transactionId}`.

## Monitor status

Query [conversion history](/knowledge-base/platform/developers/stablecoins/operate/track-status), or `GET /v2/transactions` with `types=MINT,BURN` to see both legs.

<Tip>
  Confirm the chain-specific `assetType` for both legs via `GET /v2/asset-types` before bridging. Source and destination differ only by chain, so a wrong variant routes funds to the wrong network.
</Tip>