
Paying in cryptocurrencyEight assets. No card, no bank, no name.
A card would carry your legal name, your billing address and a processor with a veto over what you are allowed to host. Removing it is not a limitation we apologise for — it is the single decision that makes everything else on this site possible.
Accepted
Eight assets across six networks.
Confirmations are chosen per chain from what it would actually cost to reorganise it, not one number applied to nine different security models. The wait column is what you should expect in practice.
If the payment itself is part of what you are protecting, Monero is the only asset here that is private by default — every other chain on this list is a permanent public record of the transfer, and no policy of ours can change that. What we add to it is nothing: an amount and a date in your ledger, and no address clustering or chain analysis of any kind.
What a card would cost you
Four things, and every one of them undoes something this business is built on. The question is not why we refuse cards — it is what a host taking them has already conceded.
- A name attached to a server
- A card is an identity document It carries your legal name, your bank, your billing address and a permanent record at a processor we do not control. Accepting one would undo the entire inventory on the privacy page in a single form field.
- A third party with a veto
- Processors decide what you may host Every card processor has an acceptable-use policy of its own, and it is far longer than ours. Taking cards would mean enforcing their content rules regardless of what ours say.
- Chargebacks
- Six months of reversal risk Which is why hosts that take cards ask for identity documents: they are managing fraud, and you pay for that with a passport scan. Remove the chargeback and the identity check has no reason to exist.
- A single point of failure
- One processor, one bad morning A processor freezing an account takes the whole business offline. Eight assets across six chains do not have a bad morning together.
How a payment works
One balance funds everything. There is no invoice to chase and no card to expire.
-
01
At checkout
You get an address that is yours alone
Freshly derived, never reused between customers or between payments, and valid for the window shown on screen. The amount is locked at the rate you were quoted.
-
02
You send
From anywhere, at any fee rate
Exchange, wallet, hardware device — we do not care and we do not look. What matters is the network: sending an asset over a chain it was not issued on is the one mistake nobody can reverse.
-
03
On confirmation
The balance moves, and any bonus with it
Between twenty seconds and twenty minutes depending on the chain. The bonus is credited in the same transaction as the payment, not applied later as a coupon.
-
04
From then on
Services draw from the balance
On their renewal date, never before. The client area shows the runway in days and the exact date of each upcoming charge.
When it goes wrong
Sending the wrong amount is not a lost payment.
Most providers reject an underpayment and make you start again, which is how a fee-rate miscalculation turns into a support ticket. Here it is simply credited for what arrived — you top up the difference whenever you like, and the balance was never at risk.
The top-up runbook- UnderpaidCredited for what arrived. Nothing is lost or returned.
- OverpaidThe excess stays on your balance. It does not expire.
- Sent lateArrives after the window: still credited, at the rate on arrival.
- Wrong networkThe one we cannot fix. Check the chain before you send.
Top-up bonuses
Credited at the moment the payment confirms, in the same transaction. Not a voucher, not a code, and not conditional on spending it within a period.
Balance never expires, is not clawed back for inactivity, and is refundable in the asset of your choice to an address you provide. Combine a top-up bonus with a 24-month cycle and the compound discount is the lowest effective rate on this site — the configurator shows the figure as you choose.
Before you send anything.
Do I need to verify my identity for a large payment?
No, at any amount. There is no threshold at which a document is requested, because there is no process here that could act on one — we do not collect identity at sign-up, at payment or at withdrawal. A host with "no KYC" on the front page and a limit further down has a KYC programme with a delay on it.
Which asset should I use?
If the payment is part of your threat model, Monero, because it is the only one on the list that is private by default. If you want it cheap and fast, USDT over Tron or SOL. If you already hold it and none of the above matters, use whatever you hold — none of them is treated differently once the balance moves.
What if the price moves while I am sending?
The amount is locked at the rate you were quoted for the window shown at checkout. Arriving after that window is fine too: it is credited at the rate on arrival rather than rejected, which is the opposite of what a payment processor would do.
Can I get a refund?
Unused balance is returned in the asset you ask for, to an address you provide. A service that does not work as described is refunded to the balance in full. A service you simply no longer want runs to the end of the term you prepaid — that is what the multi-month discount was paid for.
Do you keep my payment addresses?
A ledger entry with an amount and a date, and that is genuinely all. We do not cluster addresses, we do not run chain analysis and we add nothing to the public record that was not already in it. The complete inventory is on the privacy page.
Is there a minimum?
Thirty dollars to open an account and start ordering. After that, top up in whatever amounts suit you; the bonus tiers begin at $100 and there is no obligation to reach any of them.
Will you ever accept cards?
No. It would hand a processor a veto over what may be hosted here and would require an identity from you to manage chargeback risk. Both are the exact things this business exists not to do, and adding them later would make every other page on this site retroactively false.
