| Role | What it does | What to verify |
|---|
| Sending wallet | Sends TON into the exchange flow | Enough TON for the amount and network fees |
| Exchange address | Receives TON for the current swap or deposit | Exact address, memo or tag if required, and minimum amount |
| Receiving wallet | Receives the output asset after processing | Support for the output coin and the selected output network |
What to check before you send TON
Before sending TON from a wallet, decide what you want to receive first. The output asset matters because it determines the receiving wallet you need and the output network you must select. A wallet that supports one coin does not automatically support every network version of that coin.
You should also verify the minimum exchange amount. If the route has an under-minimum threshold and you send less than required, the transfer may not process as expected. Another common issue is sending your entire TON balance and leaving no fee buffer for network costs. If you are unsure about TON address formatting before pasting details, a TON address converter can help you compare address representations.
TON wallet exchange checklist
- Choose the output asset first
- Choose the output network carefully
- Confirm that the receiving wallet supports both
- Copy the exact exchange address for this transaction
- Check whether a memo or tag is required
- Check the minimum exchange amount
- Keep a small TON fee buffer in the sending wallet
- Plan to save the transaction hash or TXID after sending
How to swap TON from a wallet step by step
Start by choosing the coin you want to receive. After that, select the delivery network for that output asset. This step is critical because the output network can be different from TON, and the receiving wallet must support the exact combination you choose.
Next, prepare the receiving wallet before you send anything. Make sure you control the address, that the wallet accepts the output asset, and that it supports the chosen network. Only after that should you generate or review the exchange instructions, including the exchange address, any memo or tag, and the minimum amount.
Then open your TON wallet, such as Tonkeeper, and prepare the transfer. Enter the TON amount carefully and leave enough balance for network fees. Review the destination details one more time before confirming. After you send TON to the exchange address, save the transaction hash or TXID so you can later verify the transfer if needed.
Once the TON transaction is broadcast, the process usually moves through several stages. First, the transaction is confirmed on-chain. Second, the exchange service detects and processes the incoming TON. Third, the output asset is sent to the receiving wallet on the selected output network. That is why confirmation is not the same as completion. If you want more background on this distinction, the article on TON network confirmation time adds useful context.
Using Tonkeeper in a TON exchange flow
Tonkeeper can act as the sending wallet in this process, but the exchange itself may happen outside the wallet interface. In practice, Tonkeeper may simply be the app you use to send TON, approve a transaction, and copy the TXID afterward. The receiving wallet can be the same app only if it supports the output coin and the selected output network.
This distinction matters because users sometimes assume that if Tonkeeper can send TON, it can also receive any output asset from the exchange. That is not always true. The destination wallet must be chosen based on the output asset, not based on the wallet you happened to use for the TON transfer.
What happens after you send TON
After you send TON, the first visible event is usually blockchain confirmation. That only shows that the TON transaction reached the network and was included successfully. It does not always mean the exchange has finished processing or that the output asset has already been delivered.
A confirmed-but-not-arrived case often comes from one of four issues: the exchange is still processing, the amount was below the minimum, the wrong output network was selected, or the receiving wallet does not support the delivered asset correctly. This is why the TXID matters. It helps you confirm that the TON was actually sent and gives you a reference point when checking the next processing stage.
Risks and mistakes to avoid
Most TON wallet exchange problems come from avoidable setup errors rather than wallet failure. A user may copy the wrong exchange address, miss a required memo, select an unsupported output network, or send an amount below the minimum. Another frequent mistake is sending all available TON and leaving no balance for fees.
It is also common to confuse a successful TON transfer with completed delivery of the output coin. The wallet may show the TON transaction as confirmed while the exchange still has to process it and send the output asset onward. If you are comparing direct in-wallet swaps with external routes, the guide on TON DEX vs instant exchange explains that difference separately.
Troubleshooting common TON wallet exchange issues
| Issue | What it can cause | What to check |
|---|
| Sent less than the minimum amount | Delayed or failed processing | Minimum exchange amount in the instructions |
| Wrong output network selected | Output coin may not arrive where expected | Receiving wallet support for the exact network |
| Wrong exchange address or missing memo | Funds may not be credited correctly | Address details and any required memo or tag |
| No fee buffer left in TON wallet | Inability to complete or repeat actions | Remaining TON balance for fees |
| TON confirmed but output not received yet | Confusion about status | TXID, processing stage, and receiving wallet compatibility |
How to choose the right wallet setup
The simplest way to think about a TON wallet exchange is to work backward from the asset you want to receive. If the destination coin will arrive on another network, choose the receiving wallet for that network first. Then review the exchange instructions, and only then send TON from your wallet.
This approach reduces the most common mismatch: using a sending wallet that is fine for TON but unsuitable for the output asset. The sending wallet and receiving wallet do not need to be the same, and in many practical exchange flows they are different on purpose.
Final thoughts
A TON wallet exchange is best understood as a route, not a single wallet feature. You send TON from a wallet, follow exact exchange instructions, and receive another asset in a wallet that supports the chosen coin and network. The safest approach is to verify the exchange address, confirm the receiving wallet setup, stay above the minimum amount, leave a fee buffer, and save the TXID before waiting for final delivery.
