Loading route...
Loading route...
Pair route
This route is useful when the goal is to move from TON volatility into SUSDS while keeping wallet control and network selection explicit from the start.
Pair intent
Useful when the user wants to move out of TON into SUSDS for a more stable landing asset without leaving the non-custodial flow.
Send
TON on TON
Receive
SUSDS on Ethereum
Live swap card
Current rate
Select a valid pair to fetch a live variable rate
You send
You receive
Live unit rate
--
Current live rate before the shift is created.
Deposit rule
[warning] Select a pair to see the live min and max deposit range before you create the shift.
Status note
After you create the order, the app redirects to a dedicated shift screen with the QR code, countdown, waiting state, and live status polling.
Live route context
Send
TON on TON
The route starts with the exact deposit asset and network selected for this page.
Receive
SUSDS on Ethereum
Settlement is sent to the destination asset and network defined by this route.
Timing
Provider-driven
Processing time depends on deposit detection, blockchain confirmations, route processing, and final settlement on Ethereum.
Deposit limits
Live minimums
Even with a stablecoin deposit asset, live minimums and maximums still depend on the selected route and destination network, so confirm the range again on the shift page before sending funds.
How this swap works
Choose TON on TON as the asset you send and SUSDS on Ethereum as the asset you receive.
Enter the SUSDS receiving address before creating the shift so settlement has a defined destination.
Create the shift, then send TON on the exact TON route shown on the shift page within the allowed deposit range.
Track the route until SUSDS settlement is completed on the dedicated status screen.
Route-specific notes
This route can be useful after trading or profit-taking when the goal is to preserve value in SUSDS.
Stablecoin routes are network-sensitive, so the selected path must match the exact deposit and settlement chain shown on the shift page.
Some routes can require memo-style destination details depending on the asset and receiving wallet, so the final instructions on the shift page should be checked carefully before sending funds.
Related routes
Reverse route
Looking for the reverse path? Swap SUSDS to TON
Move in the opposite direction while keeping the same pair context available from a dedicated route page.
TON to BTC
Another route that still settles into BTC, with a different send asset or deposit network before Bitcoin delivery completes.
BTC to SUSDS
Land in the same destination asset through a different source route, useful when the starting wallet or source network changes.
TON to USDT
Use the same send asset but redirect value into a different destination asset and ecosystem.
ETH to USDC
Useful when the user wants to move out of ETH into USDC for a more stable landing asset without leaving the non-custodial flow.
Explore tokens and networks
Explore TON routes
View routes where TON is the asset being sent or received.
Explore SUSDS routes
See more swap paths that settle into SUSDS.
Explore TON routes
Review routes that start from the TON network.
Explore Ethereum routes
See destinations and routes that settle on Ethereum.
Explore Altcoin to stable routes
Move up one level and review the full altcoin to stable routes family instead of a single route only.
Compare BTC to stable routes
Review the adjacent btc to stable routes family when the next decision could change the destination or landing intent.
Pair FAQ
This route is often used to lock in value after trading, reduce exposure, or keep funds ready on a more stable settlement asset.
The minimum is provider-driven and route-specific. Always use the live builder and the shift page as the final source of truth before sending funds.
Processing time depends on deposit detection, blockchain confirmations, route processing, and final settlement on Ethereum.
Deposits below the allowed range can fail to settle normally and may require provider-side handling, so the live deposit rule should always be checked before sending.
Very important. SUSDS can exist on multiple networks, so the shift page instructions and selected route must be matched exactly before you send funds.
Yes. You should have a compatible SUSDS receiving address on Ethereum before you create the shift, because settlement is sent to the exact destination you provide.
Route disclaimer
Rates, minimums, and maximums are provider-driven and can change before the shift is created.
Always verify the deposit instructions on the shift page before sending funds.
The selected receiving network must match the destination wallet and asset route.
For TON to SUSDS, the live builder and shift page remain the final source of truth.