# BNB Smart Chain (BSC) Swap API

Broker as a Service (BaaS) swaps BNB and the listed tokens on BNB Smart Chain (BSC) to and from every other supported chain, through the REST API and the [MCP server](https://docs.chainflip-broker.io/resources/ai-documentation/). This page collects what is specific to BSC: minimums and token contracts, addresses, deposits and refunds, vault swaps and pitfalls. For the general flow, start with [Starting a Swap](https://docs.chainflip-broker.io/features/start-swap/) and [View Available Assets](https://docs.chainflip-broker.io/features/view-assets/).

## Assets and minimums

| Asset | id | Decimals | Minimum | Native minimum | Contract |
| --- | --- | ---: | ---: | --- | --- |
| BNB | `bnb.bsc` | 18 | 0.02 BNB | `20000000000000000` | — |
| USDT | `usdt.bsc` | 18 | 10 USDT | `10000000000000000000` | `0x55d398326f99059fF775485246999027B3197955` |

*Snapshot captured on 2026-11-17 from the production [`/assets`](https://docs.chainflip-broker.io/features/view-assets/) endpoint. Minimums are Chainflip's current source (ingress) minimum deposit amounts; query `/assets` for live values. Destination-side egress minimums depend on gas and are not in `/assets`; see [Error Codes](https://docs.chainflip-broker.io/features/error-codes/) for `egress_below_minimum` and `egress_fee_not_covered`. `minimalAmountNative` is in the asset's smallest unit. Assets disabled upstream are omitted.*

The Contract column is the token's BSC contract. Check the Decimals column before converting amounts: USDT on BSC has 18 decimals, unlike USDT on the other chains.

## Addresses

BSC uses Ethereum's address format: `0x` followed by 40 hexadecimal characters. A mixed-case address must carry a valid EIP-55 checksum; an all-lowercase or all-uppercase address is accepted without one. The same rules apply on [Ethereum](https://docs.chainflip-broker.io/chains/ethereum/) and [Arbitrum](https://docs.chainflip-broker.io/chains/arbitrum/), so BaaS cannot tell which EVM chain an address was meant for: confirm the user controls it on BSC.

A destination address is checked with the destination asset's rules and a refund address with the source asset's, so a BSC `refundAddress` is required when the source asset is on BSC.

## Deposits and refunds

A [`/swap`](https://docs.chainflip-broker.io/features/start-swap/) call opens a deposit channel and returns the `address` the user sends the source asset to.

* Deposit channels close after 24 hours. Open a new channel for every deposit-channel swap and send the deposit immediately ([Chainflip: closure of deposit channels](https://docs.chainflip.io/brokers/broker-deposit-channels-swaps#closure-of-deposit-channels)).
* `minimumPrice` and `refundAddress` are required.
* `retryDurationInBlocks` is optional: omitted or negative, it is the 150-block (15-minute) default, and a value above Chainflip's current runtime limit is lowered to that limit. Use the quote's `recommendedRetryDurationInBlocks`.
* If the minimum price or live price protection is not met within the retry window, the source asset is refunded to `refundAddress`. For DCA, only unexecuted chunks are refunded; executed chunks still pay out to the destination.

See [Starting a Swap](https://docs.chainflip-broker.io/features/start-swap/#slippage-protection) and Chainflip's [Swapping Basics](https://docs.chainflip.io/protocol/swapping-basics#slippage-protection).

Chainflip's [ingress table](https://docs.chainflip.io/protocol/ingress-witnessing-deposits#the-witness-process) lists a safety margin of 29 to 42 BSC blocks, at about 0.45 seconds per block. Show users the quote's `estimatedDurationSeconds` rather than a fixed number.

## Vault swaps

A BSC vault swap is a call to Chainflip's Vault contract on BSC that your application or the user's wallet signs and submits; there is no deposit channel. [`/tx-payload/evm`](https://docs.chainflip-broker.io/features/tx-payload/) serves BSC as well as Ethereum and Arbitrum. It takes `sourceAmount` (in the source asset's smallest unit), `minimumPrice`, `refundAddress` and `retryDurationInBlocks`, and returns:

* `to` - the Vault contract to call.
* `callData` - the encoded swap call.
* `value` - the amount of native BNB to attach, hex-encoded.
* `sourceTokenAddress` - only for a token source: the token to approve. It is a response field, not a request parameter.

For a token source, the Vault must be approved to spend the token before the swap transaction is submitted; without the approval the call fails on chain. For a BNB source, the swap amount travels as the transaction's `value`.

Payloads can stay valid for a long time, but Chainflip advises signing and broadcasting only freshly built ones. See Chainflip's [EVM Vault Swaps](https://docs.chainflip.io/brokers/vault-swaps-api/evm) for the protocol details.

Boost is documented for Bitcoin deposits; see the [Bitcoin page](https://docs.chainflip-broker.io/chains/bitcoin/#boost).

## Known pitfalls

* **18-decimal USDT.** USDT on BSC uses 18 decimals; an amount computed with 6 decimals is off by a factor of 10^12.
* **Token approval.** A token vault swap needs an approval transaction first.
* **Gas and egress fees.** A small output can be rejected at quote time with `egress_below_minimum` or `egress_fee_not_covered`; quote a bigger amount.
* **Payload freshness.** Build a new vault payload for each transaction instead of reusing an old one.
* **Same address, other chains.** A BSC address is also valid on Ethereum and Arbitrum; check which chain the user expects.

## Related

* [Starting a Swap](https://docs.chainflip-broker.io/features/start-swap/)
* [Vault Swap Transaction Payloads](https://docs.chainflip-broker.io/features/tx-payload/)
* [View Available Assets](https://docs.chainflip-broker.io/features/view-assets/)
* [View Available Networks](https://docs.chainflip-broker.io/features/view-networks/)
* [Error Codes](https://docs.chainflip-broker.io/features/error-codes/)
* [Testing Environment](https://docs.chainflip-broker.io/environments/testing/)
