Crypto and billing FAQ

Billing lists the currently enabled manual destinations by cryptocurrency and network. USDT has separate TRON and Ethereum choices; USDC uses Ethereum, while its legacy TRON option is disabled. The exact asset and blockchain must match your wallet selection. These fixed operator-supplied addresses do not provide chain monitoring, automatic confirmation or balance crediting. Confirm handling before sending real funds.

The manual top-up panel displays fixed, real receiving addresses supplied by the operator. They are shared destinations, not addresses generated for your account or assigned to an order. Selecting a network and copying its address are read-only actions. Transaction matching and automatic crediting are not connected, so confirm the handling process with the operator before sending funds.

Sending a transfer, observing its blockchain finality and crediting an account are separate events. This manual-address preview performs none of the transaction detection or reconciliation needed to connect them. An address, wallet receipt or transaction hash does not create spendable USD balance. The developer still needs to verify the transfer, associate it with the correct account or order, and prevent duplicate crediting.

The account spends a USD-denominated ledger, but the manual address panel does not calculate a crypto quote or convert transfers into credit. The operator must define valuation and acceptance rules, and the developer must connect verified settlement to the ledger. A sending wallet conversion is not an agreed credited amount. Local TEST_CREDIT is simulated and unrelated to real transfers.

Tungsto charges no deposit fee and no server setup fee. Your wallet, exchange, or blockchain may still charge mining, gas, withdrawal, or other network fees. Those external costs are separate from the USD amount credited to your Tungsto ledger. Review the asset, network, and destination address before sending, especially when fees are high or the sending platform offers several network choices.

This preview does not monitor blockchains or match manual transfers, so refreshing Billing cannot detect or credit a payment. Keep the receipt, asset, network, amount and destination, then contact the operator through an established real channel. Local support tickets are not delivered messages. Do not send twice or use test credit as proof of payment, and never share wallet secrets.

A deposit address is valid for one configured asset and network. A transfer made on another chain or with another asset will not match the expected deposit and may be unrecoverable. Do not send a test transfer on an unsupported network expecting automatic conversion. If an error occurs, preserve the transaction reference and address before contacting us, but recovery cannot be guaranteed.

A single blockchain transfer is designed to create at most one ledger credit. The network, asset, and transfer reference identify the deposit uniquely. Repeated payment notifications may update its confirmation count, but they do not create additional DEPOSIT_CREDIT entries for the same transfer. Your spendable balance is always calculated from the ledger, so every accepted credit remains visible as a separate accounting entry.

Your balance is not stored as one editable number. It is calculated by summing ledger entries. Deposits add positive entries, while orders, renewals, and withdrawal holds add separate negative entries. The Billing area can show the latest 100 entries. Downloadable invoices or statement files are not available yet, so preserve relevant order and ledger references for your own records.

A withdrawal must fit within your available balance and use an asset that previously credited your account. Enter the USD amount and follow the form’s amount validation. Submission places that amount on hold and returns a request reference for manual review; it does not send funds immediately. Withdrawal history and a guaranteed processing time are not available yet.