Crypto payment basics for panel buyers: networks, fees and confirmations

A crypto payment is not one thing. It is an asset moving on a specific network, to a specific address, under a fee rule set by that network. The panel publishes an address and a network name. If either side of that pair is wrong, the transfer can be valid on the network and useless to the panel. Much of the risk in a crypto top-up is decided before the send button, not after it.

The four questions below are the whole checklist: which network, which asset, who pays the fee, and how many confirmations the panel requires. A panel that answers all four on its deposit page is giving you a process. A panel that shows an address with no network label is asking you to guess. This page describes the mechanics and the trade-offs. It is not investment advice, and the value of a stablecoin can move away from its target.

What a network is, and why the name matters

A network is the ledger that records the transfer. USDT exists on several networks, including TRON as TRC-20, Ethereum as ERC-20 and other chains under their own standards. The same ticker on two networks is two different tokens on two different ledgers. An address that works on one network may be invalid or controlled by someone else on another. The network name is not a detail. It is the route.

Some networks also use a memo or a tag for deposits to a shared address. A transfer without the tag can arrive at the exchange or panel's main address without identifying the customer. The panel may be able to match it manually, and it may not. If the deposit page shows a tag, copy it exactly. A tag is part of the address for that transfer.

Check the address format against the network the panel names. A TRON address usually starts with T. An Ethereum address starts with 0x. A TON address has its own format. A page that shows a 0x address and calls it TRC-20 is a page with a mistake, and a mistake at that layer is expensive to unwind. Ask support to confirm the pair before the first transfer.

The four questions to answer before you send

1. Which network? Copy the network name from the panel's deposit page, not from a chat message or a tutorial. The name should match the address format.
2. Which asset? Confirm the ticker and the contract if the page shows one. A wrapped or bridged version is a different asset.
3. Who pays the fee? The sender pays the network fee. Ask whether the panel deducts a deposit fee from the credit as well.
4. How many confirmations? Use the count on the deposit page. A credit before that count is a courtesy, not a rule.

Write the answers down before the first transfer. The first transfer is the one where a mistake is likely, because the address and the network are new. A small test transfer is cheaper than a support case. Send the minimum amount the panel accepts, confirm the credit, and only then send the balance you planned.

Fees: the network fee and the panel fee are separate

The network fee is paid to the validators or block producers who include the transaction. It is not set by the panel, and it changes with network demand. The panel fee, if any, is a deduction the panel makes before crediting the wallet. A deposit page may show one, both or neither. The two are separate lines, and a panel that says "no fees" is usually describing its own deduction, not the network's.

A fixed fee hurts a small transfer more than a large one. For the arithmetic, assume the network charges $1.00 for the transfer. The fee is an illustrative input, not a Talon price. On a minimum top-up of $5.00, the fee is 20.0% of the transfer, and the credit is $4.00. On a maximum top-up of $500.00, the same fee is 0.2% of the transfer, and the credit is $499.00.

The lesson is not that crypto is expensive. It is that a fixed cost has a different weight at different sizes. A 1.00 dollar fee on a 5.00 dollar transfer is a large share. On a 500.00 dollar transfer it is a rounding line. If the panel passes the network fee to you, the minimum top-up is an expensive place to pay it. If the panel absorbs it, the fee is already in the price and the comparison moves to the rate.

Confirmations: what the panel waits for

A transaction is broadcast, included in a block, and then confirmed by more blocks. The panel decides how many confirmations it needs before crediting the wallet. That count is a risk decision, not a technical constant. A panel that credits at zero confirmations is fast and exposed to a reorg. A panel that waits for finality is slower and safer. The deposit page should state the count.

TRON's developer documentation, read on 7 November 2026, says a block is typically solidified in about one minute, and that a transaction is final when its block is solidified. Ethereum's documentation defines finality as a block that cannot be reverted without a consensus failure, and explains that finality is explicit rather than probabilistic. Those are network facts. The panel's count can be lower, and the panel's count is what governs your credit.

If a transfer is confirmed on the network and the wallet is not credited, the transaction id is the evidence. Send it to support with the network, the asset, the amount and the time. Do not send a second transfer to the same address to "push" the first one through. A second transfer is a second payment, and it does not speed up the first.

Wrong network, wrong address and the limits of recovery

A transfer on the wrong network is an expensive mistake. The panel controls the addresses it published. If the asset arrives on a different network, the panel may not hold the key that can move it. Recovery depends on the other network and the holder of the receiving address. It is not automatic, and it may not be possible at all.

A wrong address inside the right network is a different case. The transfer is valid, but it went to an address the panel does not control. The panel cannot reverse it. The receiver can send it back, and the receiver may not. A copy-paste error in the last four characters is enough. Check the first and last four characters and the network before you confirm.

The panel's queue rules matter after the transfer. A deposit that is confirmed but not credited can hold an order in the queue. The queue deadline is 180 minutes for an order that never started, and the funds deadline is 180 minutes for an order waiting for a supplier top-up. Those deadlines are the panel's promise about how long a paid order can wait before a refund. They do not replace the deposit credit, but they bound the wait.

Stablecoins are not a bank balance

USDT is designed to track the US dollar, and it usually trades close to one. It is not a bank deposit and it is not insured. The market price can move away from the target, and the panel credits the wallet at its own rate. A panel that credits one dollar per USDT is taking the price risk on its side. A panel that credits at a market rate is passing it to you. Ask which one applies before a large transfer.

The same applies to the network asset used to pay the fee. If the fee is paid in the network's own token, the dollar cost of the fee moves with that token. A fee that was small when you planned the transfer can be larger when the network is busy. The deposit page may show an estimate. The estimate is not a quote.

None of this makes a stablecoin payment unsafe. It makes the cost variable and the remedy policy-based. A card payment has a dispute path and a card fee. A crypto payment has a network fee and finality. The chargeback guide compares the two paths in detail.

The deposit flow step by step

The flow starts before the transfer. Open the panel's deposit page, copy the network name and the address, and check that the address format matches the network. If the page shows a tag, copy it. Then open your wallet or exchange, choose the same network and asset, paste the address, and compare the first and last four characters. Send the minimum amount first.

After the send, the wallet shows a transaction id. Keep it. The panel's deposit page or support channel takes the id and the network, and the panel waits for its confirmation count. When the count is reached, the wallet is credited and a ledger entry appears. Check the ledger entry against the transaction id and the amount. If the credit is short, the difference is the panel's deposit fee or the network fee, and the deposit page should say which.

If the credit does not appear after the stated count, send the transaction id to support with the network, the asset, the amount and the time. Do not send a second transfer. A second transfer is a second payment, and it does not make the first one confirm faster. The chargeback guide explains why a crypto payment has no reversal path after finality.

What to keep

Keep five fields for every crypto payment: the transaction id, the network, the address, the asset and the amount. The transaction id proves the transfer. The network proves the route. The address proves the destination. The asset proves what was sent. The amount proves the value. A support case without all five is a conversation; a case with all five is a record.

Keep the panel's deposit page as it looked on the day, or a screenshot of it. The address and the network can change, and the version you used is the version that matters. Keep the wallet's send confirmation too. The two records together show what the panel asked for and what you sent.

The record is also the input to a refund. A refund to the sending address needs the address and the transaction id. A wallet credit needs the order or deposit reference. A card dispute needs the transaction and the merchant. Each path has its own evidence, and the evidence is easier to collect before the payment than after it.

Questions to ask support

Ask four questions before the first transfer: which network, whether a tag is required, who pays the network fee, and what amount the wallet will receive for a test transfer. The answers should be specific. A network name and a tag are facts. A fee rule is a fact. A credit amount is a number. A promise that the transfer will be "credited automatically" is not an answer to any of the four.

Ask the same questions for a refund. A refund can be a wallet credit, a new transfer to the sending address or a card refund. The policy should name the path and the fee. If the policy is silent, the support answer is the record. Keep it with the transaction id.

A checklist before the first transfer

1. Network. Copy the network name from the deposit page. Check that the address format matches.
2. Asset. Confirm the ticker and the contract if one is shown. Do not substitute a bridged version.
3. Tag or memo. If the page shows one, copy it exactly. A missing tag can leave the deposit unmatched.
4. Fee. Ask who pays the network fee and whether the panel deducts a deposit fee. Compare the credit, not the amount sent.
5. Confirmations. Note the count on the deposit page. Wait for it before expecting the credit.
6. Test. Send the minimum amount the panel accepts. Confirm the credit and the ledger entry before the larger transfer.
7. Record. Save the transaction id, the network, the address and the amount. The id is the only proof that the transfer happened.

Three networks compared

Question	TRON, TRC-20	Ethereum, ERC-20	TON
Address shape	Usually starts with T	Starts with 0x	Its own format, often with a tag
Finality	About one minute, per TRON's documentation	Explicit finality, per Ethereum's documentation	Set by the network and the panel's count
Fee	Set by the network, paid by the sender	Set by the network, paid by the sender	Set by the network, paid by the sender
Common mistake	Sending an ERC-20 transfer to a TRC-20 address	Sending a TRC-20 transfer to an 0x address	Leaving out the tag
Panel credit	After the panel's confirmation count	After the panel's confirmation count	After the panel's confirmation count

A qualitative comparison. The finality statements are from the networks' documentation read on 7 November 2026; the panel's own count is on its deposit page.

The table is not a recommendation. The network the panel supports is the network you can use. The useful comparison is the credit you receive for the same amount leaving your account, after the network fee and any panel deduction. That number is on the deposit page or in support's answer, and it is the number to compare with a card or Stars top-up.

For the Stars alternative, read Stars versus USDT. For the account side, read wallet safety. The payment terms are on the terms page, and a deposit that has confirmed but not credited can be sent to support with the transaction id.

اعدادی که با کلید داده مشخص شده‌اند، هنگام رندر همین صفحه از دیتابیس Talon، ماژول سیاست، ماژول پول یا ماژول سفارش خوانده می‌شوند. هر واقعیت بیرونیِ تاریخ‌دار، لینک منبع و تاریخ خوانده‌شدن را دارد.