Notcoin transfers incur TON network fees while exchange withdrawals follow provider rules

Notcoin's NOT token can move between TON wallets or leave a custodial exchange through a supported withdrawal route. A standard wallet transfer needs Toncoin for network costs. A custodial exchange applies its fee schedule, any withdrawal minimum and its service processing rules. Its quoted charge can differ from the network cost of the eventual on-chain transaction. Compare the recipient's NOT amount with your total debit, then consider who controls dispatch and when the movement actually completes. A wallet balance, a withdrawal request and a successful token transfer describe different states.

The short version: A broadcast response does not confirm delivery; check whether the NOT transfer succeeded at the intended recipient address.

A self-funded NOT transfer keeps the network fee separate

Sending NOT from a self-custodial wallet moves a TON jetton balance, with the standard self-funded route requiring native funds to execute the token transfer.

The token contracts separate NOT from Toncoin

A jetton is a fungible token on TON. NOT uses this token format, which follows TEP-74. The master contract identifies the token and tracks total supply. Individual jetton wallet contracts hold owners' balances and process transfers. These contracts keep token balances separate from native balances. The owner address that identifies a recipient also has a different purpose from the jetton wallet contract that software calls. The wallet or app handles that relationship when preparing a standard transfer; a jetton master or jetton wallet address should not replace the intended recipient address.

A connected app requests wallet actions

TON Connect links a TON app with a user's wallet over an encrypted session. The app can read the connected address and request signatures or transactions without obtaining the user's private keys. Connecting a wallet establishes that session. A sendTransaction request asks the wallet to sign and broadcast its instructions. An app can show a connected address or token holdings before any transfer occurs. The specific wallet and app determine how they present those requests.

The signing request

A transaction request can contain multiple outgoing messages. Review the recipient addresses, token identity and attached native amount, because the NOT quantity does not describe every instruction.

The native balance

TON transaction fees are paid in Toncoin. The amount of NOT being transferred and the native amount attached for execution are different quantities. Holding enough tokens for the recipient's amount therefore does not establish that a standard self-funded transfer has enough native funds. An attached native amount can also include funds for contract execution and forwarding; it should not automatically be read as the final fee. Network fees vary with execution requirements, so a fixed universal NOT transfer price would misrepresent the cost.

What does an exchange withdrawal quote include?

An exchange withdrawal quote identifies the provider's charge and withdrawal amount, while its minimum and processing rules determine whether the requested movement can proceed. Read whether the amount describes your debit or the recipient's expected receipt. Kraken shows its final withdrawal fee at confirmation, and that fee can differ from its published figure. Other providers set their own terms. The service quote and underlying network cost describe different quantities; they do not establish two separate charges to your account.

Matching received NOT exposes costs in different assets

Comparing the same recipient amount gives both routes a common token target, even when their charges use different assets. A withdrawal fee deducted in NOT changes the relationship between the account debit and delivered tokens. A native network fee belongs alongside the wallet's token amount as a separate cost. Converting those costs to a common currency also requires prices from the same point in time; the token quantities alone cannot establish which route costs less.

Custody determines who controls dispatch

With self-custody, the owner signs through the wallet; with a custodial exchange, the provider processes a withdrawal from the balance that it holds for the account. That adds service processing to blockchain execution. Withdrawal availability follows the provider's eligibility and service rules, including the assets and networks that it supports. A pending request therefore describes a provider-side state, not completed delivery.

Why does a submitted transfer still need an on-chain check?

A submitted transfer needs an on-chain check because recipient execution determines whether the intended transfer succeeds. A signature authorizes the request. Broadcasting submits its message to the network. Neither observation alone proves that the recipient has received NOT. A wallet's transfer history and the relevant on-chain transaction outcome establish more than an app's request confirmation.

TON Connect's sendTransaction response contains a serialized copy of the broadcast external message. That returned message data supports an on-chain lookup. It does not describe the final outcome of every recipient operation. When one request contains multiple outgoing messages, recipient contracts execute independently. One message can fail or bounce while others succeed, and execution order can differ from the input list. A successful result elsewhere in the request therefore does not prove that the intended NOT transfer succeeded.

The provider's processing time and blockchain execution time describe different intervals. A network confirmation estimate does not include any earlier wait for withdrawal dispatch.

Receiving rules distinguish wallet destinations from exchange deposits

A wallet destination and an exchange deposit destination both need to accommodate NOT on TON, while the exchange also controls how it credits incoming tokens. An address existing on the network does not establish that a custodial service accepts a particular asset there. Deposit instructions define the service's supported asset and network combination, together with any additional crediting conditions. Native NOT's TON identity should remain consistent with the destination's supported route; the same ticker on another network does not establish compatibility.

For a transfer intended to fund an exchange account, completion means that the account receives usable NOT. An outgoing transaction identifier alone does not establish that credit.

View image file