Billing · 6 min read
How to pay for a GPU server in crypto, without KYC, and get a refund if you need one
The prepaid balance explained: which coin to use and why, fees and confirmation times, what to do when a payment is short, how refunds go back to the address they came from.
In short
- An email address and a password open the account; no document is requested, at any amount.
- USDT on TRON is the cheapest and fastest; Monero the most private; Bitcoin takes about an hour.
- Unused balance goes back to the address it came from; rent already charged does not.
Paying in crypto for hosting is mostly about three things: not being asked for documents, not being surprised by fees, and being able to get unused money back. This is how all three work here.
No KYC, at any amount
An account is an email address and a password; there is no verification step to unlock spending, no limit above which documents are requested, and no card on file. The trade-off is on you: we cannot recover an account whose password is lost, because we hold nothing that identifies you and no address to write to. Keep it in a password manager on day one.
Which coin
- USDT on TRON (TRC-20)
- Cheapest and fastest: fees of cents, credited in a minute or two. The default for most people.
- Monero
- Private by design; the transaction shows nothing to anyone. About twenty minutes to credit.
- Bitcoin
- Fees depend on the mempool; allow an hour. On-chain only, no Lightning.
- Ethereum and USDT on Ethereum
- Mainnet only, no layer-2. Fees vary with the network.
- Litecoin, TRON, Solana
- Cheap and quick; fine if you already hold them.
The top-up page tags the cheapest, the fastest and the most private option for the amount you enter, and the invoice tells you how many confirmations it waits for.
The steps
- Billing → Top up: enter an amount, $40 or more. If a renewal is coming, the page proposes the exact amount that covers it.
- Pick a coin. The invoice shows an address, an amount in that coin, a QR code and an “Open in wallet” link.
- Send the exact amount, on the named network. The invoice refreshes on its own: seen, confirming, credited.
- Order a server. The whole term is taken from the balance; the rest stays for the next renewal.
Mistakes and how they end
- Sent a little less
- Credited at the value received once confirmed. Top up the difference with a new invoice.
- Sent after the invoice expired
- Credited at the rate of the moment it is seen.
- Sent on the wrong network
- Not seen by the processor. Open a ticket with the transaction hash; we look, without promising.
- Sent from an exchange
- Fine, but note the exchange's withdrawal fee and pick the network the invoice names. Refunds go back to the address the payment came from, which for an exchange is a shared hot wallet: withdraw to your own wallet first if you might want a refund.
Refunds
Unused balance is refundable on request from a ticket: same coin, back to the originating address, less network fees, within seven days. Rent already charged for a term is not refunded, except through SLA credits or when we fail to deliver. A cancelled server does not refund the rest of its term, so cancel by turning auto-renew off and letting the term run out.
Records
Every top-up and every charge is a ledger line on the billing page, with the balance after it, and the invoice page for each top-up shows the address, amount and network. The API returns the same data as JSON. There is no PDF invoice with a company name on it, because we hold no company name.
An example
An RTX 4090 for three months is $404.49 at the 3-month rate. Top up $410 in USDT TRC-20, order, and the remainder waits for the next renewal.
Keep reading.
