01
Use ETH on the Ethereum network
Select ETH with the Ethereum network in Billing to view the fixed receiving address for that exact pair. Compare the complete address and network label with the sending wallet or exchange before approval. Do not substitute an address from another service or assume that an Ethereum-compatible chain uses the same deposit route.
Layer-2 routes, sidechains, and wrapped assets are not interchangeable with native ETH here. When a sender offers several networks, choose only the one matching Billing. Another route may be unrecoverable.
02
Separate sending, confirmation, and USD credit
The separate provider adapter specifies 12 confirmations. The following table describes that adapter, not the current manual panel. This panel does not detect ETH transfers, monitor confirmations or create USD credit; a wallet's Sent status is not account balance.
Separate sending, confirmation, and USD credit| Stage | Meaning | Customer action |
|---|
| Address returned | A destination exists for ETH on Ethereum | Verify the full address and network |
|---|
| Sent | The sending wallet recorded a transfer | Save the transaction reference |
|---|
| Confirming | The threshold or settlement stage is incomplete | Do not spend against it |
|---|
| Credited | A positive USD ledger entry exists | Check the available balance |
|---|
03
Keep Ethereum network costs separate from server price
Tungsto adds no deposit fee, but the network, wallet, or exchange may charge gas or a withdrawal fee. Those costs are controlled outside Tungsto and do not change the server price recorded in USD. Review the final sending screen rather than estimating from the server total alone.
Billing does not show a provider quote or expected USD credit before sending. Treat the ETH amount leaving your wallet and the USD amount later credited as separate values. Wait for the completed ledger entry before choosing an order total or relying on the transfer for renewal.
04
Apply confirmed credit to a physical server
Orders use the shared USD ledger rather than an ETH balance; the manual panel does not reconcile ETH transfers into credit. Choose hardware, region, operating system, term, and quantity after checking that the available credit covers the order. Price, balance, and regional capacity are checked again when the order is submitted.
An accepted order records its ledger debit and queues provisioning. Accepted or Queued confirms that the workflow was recorded; it does not mean a physical server is installed or ready for login. Payment settlement time and hardware provisioning time are separate parts of the customer journey.
05
Do not confuse ETH payment with an Ethereum workload
Paying with ETH does not install an execution client, consensus client, validator, RPC service, or wallet. Those workloads have separate requirements for software, storage, bandwidth, keys, monitoring, and updates. Use the blockchain-node guide to assess them before selecting hardware.
Crypto payment does not make server activity anonymous. Transfer references, sending-platform records, IP traffic, timing, and operational records may remain observable. Keep wallet and account secrets out of contact messages; preserve only non-secret transfer details.
Direct answers
Questions before you order
Can I send ETH through a Layer-2 network?
Not through this route. Use native ETH on the Ethereum network shown in Billing. A Layer-2, sidechain, or wrapped-asset transfer is different and may be unrecoverable.
When does an ETH transfer become spendable?
Only after USD credit is actually recorded. The legacy adapter's 12 confirmations setting is not an automatic-credit rule for the manual panel, which does not match ETH transfers.
Does paying with ETH deploy an Ethereum node?
No. ETH is only the funding method. Node or validator software, keys, storage, security, monitoring, and maintenance remain a separate customer-managed workload.