SameSame

Cross-chain stablecoin guide

How to Swap USDT on BNB Chain to USDC on Base

Published · Updated

This route converts a BNB Smart Chain stablecoin representation into native USDC on Base. It changes both the asset and the network, so compare the USDC output rather than assuming that 10 USDT will deliver 10 USDC.

Check live quote on SameSame

No route is preselected by this link. Choose the tokens and networks in the interface. Checking a quote does not approve or submit a transaction.

Network requirements and token representations

The configured source contract is Binance-Peg BSC-USD, shown as USDT in SameSame and Bridgers. It uses 18 decimals, unlike many other USDT contracts. The destination is Circle-listed native USDC on Base with 6 decimals. Binance-Peg backing and custody introduce considerations distinct from holding an issuer’s native token; neither the USDT label nor a matching wallet address proves equivalence.

The source is BNB Smart Chain (BSC), chain ID 56, not BNB Beacon Chain or opBNB. The receiving network is Base, chain ID 8453. Keep enough BNB on BSC for source network fees unless your wallet actually offers an eligible alternative. ETH on Base cannot directly pay a BSC source fee.

You need USDT at the source contract, a compatible EVM wallet, and a receiving address on Base. Verify that you control the receiving address. Many EVM wallets reuse an address, but exchange deposit addresses can have network restrictions; confirm the recipient’s supported network before proceeding.

Check the BNB Smart Chain to Base quote

  1. Choose USDT on BNB Smart Chain as the sending asset and native USDC on Base as the receiving asset. Enter the amount in normal token units.
  2. Read the estimated USDC output, provider fee, destination fee and minimum received. Routes depend on the current provider catalog and a fresh quote, not this guide’s publication date.
  3. If reviewing execution, compare the source and destination networks, token contracts, input amount and receiving address. A wallet’s approval and swap requests must match what you reviewed.
  4. A required approval permits spending of the source token; it is not evidence of delivery. If a route can be executed, the wallet will present the required confirmations separately. Do not confirm a request with unexpected parameters.

Network fees are confirmed in the wallet. SameSame refreshes ordinary quotes automatically every 30 seconds; an expired review needs a fresh quote. Re-read the figures after a refresh rather than assuming the old output remains available.

Fees on this route

Compare the quoted USDC output with the USDT input and the wallet’s BSC fee preview. Both conversion pricing and route fees matter on this pair. The source contract’s 18 decimals do not mean it is worth more than a 6-decimal USDC token; decimals describe precision, not price.

The quote displays a provider fee and a destination chain fee; the wallet presents source network costs. Some fees may already be reflected in the estimated output, so do not subtract the same fee twice. A separate approval can add gas costs. See how quote fees and wallet fees differ.

Minimum received is the lower output specified by the reviewed quote and slippage settings. It is not an independent guarantee of settlement or immediate delivery. Provider enforcement and settlement have not been independently verified.

Token details

The BNB Chain source is Binance-Peg BSC-USD, displayed as USDT in SameSame and Bridgers. The Base destination is a Circle-listed native USDC contract. Always verify both the contract address and the network.

Verify source confirmation and destination delivery separately

  1. Keep the source transaction hash and any Bridgers order ID shown in History. Open the source receipt on BNB Smart Chain’s explorer and check the network, wallet and success or failure status.
  2. A successful source receipt confirms source execution, not receipt of USDC on Base. Check Base’s explorer for a transfer of the listed destination USDC contract to the receiving address.
  3. Compare the received token and amount with your review, then view that network in your wallet. SameSame’s available provider status is not an independent settlement audit.

History is stored locally for the connected wallet; clearing browser storage or using another device may remove that local record. Save the order ID and transaction hash separately. A missing provider ID is not proof that no wallet transaction was sent.

Troubleshooting this route

MetaMask shows Base while the sending asset is on BNB Chain

Do not approve a source request on Base for this BSC-origin route. Cancel the mismatched wallet request, return to SameSame and review a fresh quote. The source approval and source swap should use BNB Smart Chain, chain ID 56. Base is the receiving network.

A quote is empty, expired, or the balance fails to load

Check your internet connection, the selected source token and network, and the connected wallet. A balance read failure is not proof of a zero balance. Do not treat an old quote or a token listing as proof that the route is currently executable; request a fresh quote and stop if the interface cannot verify the request.

The source succeeded, but History or the wallet still looks pending

Check source and destination explorer records before taking action. Reopen History with the correct wallet connected; use the available provider status as one piece of evidence. Do not submit the same swap again just because status is delayed. If you cannot reconcile the records, retain the hash and order ID and contact support.

For interface issues, contact @samesame_support on Telegram. For provider delivery issues, use the official Bridgers support options. Never share your seed phrase or private key; avoid posting wallet and order details publicly.

Frequently asked questions

Is the BNB Chain USDT contract the same as Ethereum USDT?

No. This route uses Binance-Peg BSC-USD at the BSC contract below. Ethereum USDT uses a different contract and precision. Sending an asset on the wrong network cannot be fixed by matching its ticker.

Why does this route use different token decimals?

The BSC source uses 18 decimals and Base USDC uses 6. SameSame uses the configured token precision for amounts. Enter normal human-readable amounts; do not manually multiply by 10 to the power of the decimals.

Will I receive one USDC for each USDT?

Not necessarily. These are different assets and representations. Pricing, provider fees and network fees can change the USDC output. Review the current quote instead of assuming parity.

How long does this route take?

Network confirmations, provider processing and service availability affect completion. This guide promises no exact delivery time. Check the source receipt and destination transfer instead of inferring success from elapsed time.

Route evidence and security limitations

SameSame uses Bridgers for cross-chain quotes and routing. A read-only quote for 100 USDT on this direction was recorded on October 12, 2026. No transaction was executed in that check. This historical quote does not establish current availability, pricing or successful execution.

Verify native USDC addresses against Circle’s contract directory and the linked explorer records. Token symbols alone are insufficient. See the product’s security-review scope and transaction risks, including provider-side authorization and contract-code verification limitations.

Explore other stablecoin routes

If you already hold native USDC on Base, the Base-to-Arbitrum USDC guide explains a route without a USDT-to-USDC conversion. The Ethereum-to-Base guide covers another source for receiving native Base USDC.

Browse all SameSame guides or read fees, networks, risks and support.