01
Match both USDC and ERC-20
Choose the USDC ERC-20 option in Billing to view its fixed, shared receiving address. Check the complete address and the network label in the sending wallet or exchange. A USDC transfer on another chain is a different payment route even when the balance and token symbol look familiar.
Do not let a sending platform choose a default network without reviewing it. Other chains, bridge routes, or unrelated tokens will not automatically convert into the expected deposit. A wrong-network transfer has no self-service recovery path and recovery cannot be guaranteed.
02
Keep legacy confirmation rules separate
The legacy provider adapter specifies 12 confirmations and distinguishes sent, detected, confirming and credited stages. That adapter is not connected to the manual directory, which detects no transfers and creates no USD credit. A sending platform's Completed label is not Tungsto balance.
Save the transaction reference, destination, asset, network, amount, and time. If the ledger entry is missing, compare each item with the original sending record before contacting billing. Never include a wallet seed, private key, account password, or recovery code.
03
Do not assume a fixed pre-transfer USD result
Tungsto uses a USD-denominated ledger, not a spendable USDC balance; the manual panel does not record a settlement value. Billing does not show a settlement-provider quote or expected USD credit before you send. Check the actual ledger entry rather than assuming that the token amount will equal the final available balance.
Tungsto adds no deposit fee. Your wallet, exchange, or network route may still charge transaction or withdrawal costs and may decide how those costs are funded. Those external charges and processing rules are separate from the server price.
04
Use credited USDC settlement for orders and renewals
Once sufficient USD credit is visible, select the server configuration, region, operating system, term, and quantity. Submission checks the authoritative price, available balance, and regional capacity. The accepted order records its debit and queues one provisioning workflow per requested server.
Agree manual funding arrangements before a paid-through deadline; this panel does not turn confirmations into credit. A token transfer cannot complete a renewal until its USD credit exists. Accepted and Queued are accounting and workflow states, not proof that the hardware has finished installation.
05
Keep the payment route separate from blockchain hosting
USDC on ERC-20 is a funding choice. It does not install an Ethereum node, token service, bridge, exchange, or payment gateway on the rented machine. Running any of those services requires separate software, security, key management, compliance, storage, and network planning.
The no-KYC registration flow also does not make token transfers or server traffic invisible. Payment references, sending-provider records, account timing, assigned addresses, and operational metadata may remain observable. Select application and access controls according to your own risk model.
Direct answers
Questions before you order
Can I send USDC on a network other than ERC-20?
No. This route expects USDC on ERC-20. A same-named token on another chain is different and may not be recoverable. Match Billing exactly.
Will the credited balance equal the USDC amount sent?
Do not assume it. Billing shows no expected USD credit before sending. Use the settled USD ledger entry as the authoritative spendable amount.
When can I order with a USDC transfer?
Only after sufficient USD credit is actually recorded. The legacy adapter's 12 confirmations setting does not activate manual top-up credit; sent or confirming tokens are not account balance.