Overview
Move the same stablecoin from one supported chain to another — for example USDT on Ethereum to USDT on Polygon, or USDC on Base to USDC on Solana. The destination amount matches the source amount. No conversion, no FX spread. Create a normal crypto-to-crypto transfer (or use the Console transfer page) with the same currency on both legs and differentpaymentRail values.
Supported corridors
Both the source and destination networks must be in this matrix for that asset. Networks must differ.
Same-chain moves (for example USDC on Base → USDC on Base) are wallet transfers, not bridges.
Amounts on this path support at most 4 decimal places. Use
5.1234 USDT, not 5.123456. In minor units that means the last two digits of a 6-decimal rawValue must be 00 (for example "5000000" for 5 USDT).Prerequisites
- Verified customer (KYC/KYB completed) with same-asset bridging enabled for their account
- Distinct source and destination accounts (the same Infinite wallet cannot be both)
- Source funded on the source chain, or a deposit instruction if the customer will push funds in
Quote (optional)
Same-asset bridges quote at 1:1. A quote is optional; the transfer API will still settle at par.Create the transfer
depositInstructions with the address and amount to send on the source chain. After the deposit confirms, Infinite delivers the same asset on the destination chain.
Console
On the transfer page: First Party → pick two different treasuries or wallets → set source toUSDT · ETHEREUM (or another supported pair) and destination to the same asset on a different chain. The quote should show a 1:1 rate.
What this is not
- USDC ↔ USDT is a conversion, not a same-asset bridge. Use a quote for that pair.
- USDC on Tron and USDT on Base are not in the native bridge matrix above.
- Recurring inbound addresses that always sweep to another chain use a
CRYPTO_TO_CRYPTOfixed route instead of a one-off transfer.