Pay for a VPS with Bitcoin. Nothing else asked.

A Bitcoin VPS is a server you pay for in BTC without handing the host, or a payment processor, anything about yourself. On Servury that is three facts. The account is a 32-character credential and nothing else. The payment is watched on Bitcoin and Litecoin full nodes Servury operates, with no third-party processor in the path and no block explorer queried with your address, as the privacy policy states. And every invoice gets a newly derived receiving address that is never reused, so two payments cannot be linked to each other on-chain.

The addresses are native SegWit, derived under BIP 84 from an extended public key: bc1q on Bitcoin, ltc1q on Litecoin. The watching side holds public keys only; nothing on the payment server can spend what arrives.

Timing. Bitcoin adds a block approximately every 10 minutes on average, but block discovery is probabilistic, so a confirmation can arrive much sooner or later (bitcoin.org FAQ). Merchants set their own threshold; exchanges that carry double-spend risk commonly wait for 6 blocks (Bitcoin wiki). Servury provisions at 2 on Bitcoin and 6 on Litecoin, whose blocks target a 2.5-minute interval (Wikipedia), so both land roughly 10 to 15 minutes after the transaction is mined. The payment window is 30 minutes and the BTC amount is fixed when the invoice is created. The window limits when you send, not when the network confirms: a transaction already broadcast keeps confirming after the countdown and still completes the order.

Fees. A Bitcoin fee is relative to the bytes in the transaction, not the amount, and if it is below what the network is prioritising the first confirmation may take considerably longer (bitcoin.org FAQ). Rates are quoted in sat/vB and change all the time, so check right before sending; during congestion nodes reject transactions under a purging threshold (mempool.space FAQ). So pick a medium or high priority estimate, and send the transaction replaceable: BIP 125 lets you publish a higher-fee replacement if it stalls; Electrum does this by default and calls it "Increase Fee" (Electrum FAQ), Bitcoin Core uses bumpfee.

Underpaid. A shortfall under 1 percent still counts as paid. Anything short of that and the page shows the remaining BTC; send it to the same address. If the window closes still short, everything received is credited to your balance. Overpaid. The order provisions; the excess is not credited automatically, so send exactly what is shown. Nothing sent in time. The page offers to renew the window, usually on the same address.

Lightning is not offered; payments are on-chain only. Litecoin is the same flow with an ltc1q address, and Monero is the choice when the payment itself should be private rather than pseudonymous: RingCT gives it "hidden amounts, origins and destinations of transactions" (Moneropedia), and its blocks target 2 minutes (Moneropedia), so the 10 confirmations Servury waits for take about 20 minutes. For getting coins into a wallet you control, and what still leaks, read the step-by-step buying guide. Two limits: Servury offers no DDoS protection on any line, and cryptocurrency mining is prohibited under the terms; running a node is fine, pointing a miner at it is not. Then go to the order page, or the Blackbox line if the server should be as private as the payment.