Prepaid balance billing, explained

Two ways to bill for hosting in crypto

Per-invoice billing is the familiar model carried over from card processing: every purchase mints an invoice, you send crypto to a fresh deposit address, wait for confirmations, and the order proceeds. Every renewal repeats the ceremony. It feels natural because it mirrors how fiat checkout works — one purchase, one payment.

Balance billing decouples paying from buying. You convert crypto into a prepaid USD balance in occasional, arbitrary-sized top-ups; purchases and renewals then debit that balance internally, with no blockchain involvement at all. The chain sees a funding event every few months instead of a merchant payment every few weeks.

ServPrivacy is balance-only by design: crypto invoices exist solely for top-ups, and buying a server never generates one. The rest of this guide is why that choice favors you, not just us.

What per-invoice billing leaks

On a transparent chain, per-invoice billing manufactures the cleanest surveillance dataset possible: same merchant, fixed cadence, near-identical amounts, month after month. Chain-analysis tooling is built to find exactly this. One linked payment deanonymizes the series; the series timestamps your relationship with the host and the lifetime of every server it funded. Even on Monero, where outside observers are blinded, per-invoice billing multiplies your operational exposure — more acquisitions, more broadcasts, more wallet sessions, more chances to slip once with an exchange withdrawal or a bare IP.

It also fails operationally. Renewal day means a manual payment under a deadline: wallet at hand, fees spiking or not, confirmations racing the suspension timer. Miss it — travel, illness, a stuck transaction — and the server is suspended or reclaimed on the provider's schedule, not yours. And underpayments and dust are chronic: exact-amount invoices plus volatile fees generate fractional shortfalls that strand value at the processor.

A balance turns all of that into one funding event and an internal ledger. The privacy ladder of which coin to fund with still applies — covered in the anonymous payment guide — but the model itself stops broadcasting your billing relationship on a schedule.

How the balance works here

The mechanics, end to end. You create an account — handle and password, nothing else — and open the top-up screen in the panel. Any amount from $30.00 to $5,000.00 per top-up, paid in your pick of 21 coins and network variants across 17 currencies, with XMR and BTC listed first. The invoice shows a deposit address, the exact crypto amount and a countdown; after network confirmations, the USD balance is credited. The Monero walkthrough shows the full sequence with wallet hygiene included.

Larger top-ups earn bonus credit on a published, linearly interpolated ladder — the schedule lives in the FAQ and the top-up screen previews it before you commit. The bonus lands together with the top-up, as ordinary spendable balance.

Every movement afterwards is visible in the panel's ledger: credits, debits, what each one paid for, running balance. The accounting is boring on purpose — boring is auditable. And note what is absent from the whole flow: no card data, no billing profile, no payment processor holding a file on you. The invoice address and the ledger entry are the entire financial relationship.

Deploys and renewals from balance

Spending from balance is where the model pays rent daily. A funded account deploys instantly: pick a plan and region, the balance is debited, and the box is online in about 15 min for a VPS or 2–12 h for dedicated hardware — no invoice screen, no confirmation wait, no payment step at all between you and the server.

Renewals are the same debit on schedule. Keep the balance covered and a renewal is a non-event you read about in the ledger afterwards; the panel's servers view shows each box and its term so nothing sneaks up on you. Terms run from one month to a year, and longer terms carry a tiered discount shown in the configurator before you commit — at purchase and renewal alike, the discounted total comes off the balance in one internal operation.

If the balance can't cover a purchase, the configurator says so and tells you the exact deficit to top up — no failed-payment limbo, no order stuck half-created.

Refund mechanics, in plain terms

Prepaid models need a written exit, so here is ours without lawyer fog. Unused balance is refundable in crypto within 30 days of the top-up that funded it, minus network fees, paid to an address you control. Request it from the panel's support section; "unused" means exactly that — balance, not time already consumed on a server.

Service time you have used is not refunded. Uptime failures are handled separately under the SLA: we commit to 99.9% monthly uptime, and credits for breaches are applied to the balance on the published schedule rather than wired out.

Two edge cases worth knowing before they happen. An invoice that expires unpaid costs nothing — reset it and pay the fresh one. A payment that arrives late or off-amount is reconciled manually: open a ticket from the panel with the transaction ID and it gets matched to the order rather than lost. The full terms live in the ToS; nothing in this section contradicts them, it just reads faster.

The obvious objections, answered

"I'm trusting you with a float." Correct, and worth saying plainly: a prepaid balance is an advance against future service, like every hosting credit system before it. The mitigations are structural rather than rhetorical — the refund window above gives unused funds a written exit, the per-top-up cap of $5,000.00 bounds the exposure, and nothing forces you to hold more than the term you are actually running. Size your float to your trust, and let it grow with the relationship instead of starting maximal.

"Why is the balance in USD and not crypto?" Because pricing is in USD and a crypto-denominated ledger would silently re-price your purchasing power every day. Conversion happens once, at top-up, at that moment's rate; afterwards a $8.00 plan costs the same number of ledger dollars in any month, whatever the market does. Volatility risk ends at the credit, which is the predictable side of the trade.

"Per-invoice means I can walk away any month." You can here too — terms are prepaid, not auto-extended, and a server you choose not to renew simply ends at its term. The balance does not lock you in; it removes the monthly payment ceremony from the months you were staying anyway.

Sizing your top-ups

A few practical rules get the most out of the model:

• Fund the term, not the month. Top up enough to cover your servers for the full term you intend to run — one chain event instead of several, and you stop thinking about renewal dates.
• Mind the bonus ladder. If you are near a published anchor, rounding the top-up upward can earn credit that outweighs the difference. The top-up screen previews the exact figure.
• Keep a buffer. A spare month's worth of balance absorbs a forgotten renewal or a spontaneous add-on without an emergency wallet session.
• Stay inside the window. Top-ups are capped at $5,000.00 each — for larger footprints, several top-ups work fine and each earns its own bonus.
• Check the ledger occasionally. Every debit is itemized in the panel; thirty seconds a month confirms the accounting matches your expectations.

Then spend it: VPS from $8.00/mo or dedicated from $66.00/mo, across 6 jurisdictions.