Buy a VPS with Cardano (ADA) — no KYC

Pay a VPS invoice with native Cardano: one addr1 transfer, exact amount, credit in 1–10 minutes. No memo, no KYC. Core from $4.80/mo on the annual term.
Pay a VPS invoice with native Cardano: one addr1 transfer, exact amount, credit in 1–10 minutes. No memo, no KYC. Core from $4.80/mo on the annual term.
The price locks into ADA the moment the invoice exists
The counter-intuitive part of paying for a server with Cardano is that it does not shield you from price movement — it concentrates it. A hosting invoice is quoted in dollars, converted to ADA once, and then stored as an exact coin figure. From that second on, waiting for a better rate is not prudence; it is a directional bet on the ADA/USD pair, taken without charts, while your order sits unbuilt.
The mechanism is simple once you watch it happen. The checkout prices the plan in dollars, pulls a live ADA rate, and prints a figure beside a addr1 receive address. That printed number is the contract: the watcher will look for exactly it, no more and no less. Create the invoice at 14:00 and the figure is frozen at 14:00's rate, whatever the market does by 15:00.
Where this breaks is the classic holding pattern. You generate an invoice, step away to read rate predictions, and come back six hours later having talked yourself into a different plan at a different dollar amount. The old invoice now points at nothing — its address is single-use, tied to that exact figure — and if you send to it anyway you have made a donation, not a payment. Regenerate, pay the fresh figure, keep nothing else.
If rate risk genuinely bothers you, the checkout offers rails built for exactly that problem. USDT holds a dollar figure flat between quote and confirmation across seven networks, and XMR is the quieter pick when you want the payment itself to leak less — see the USDT walkthrough and the Monero one. ADA's honest case is different: you already hold it, the chain settles inside a 1–10 minutes window, and spending it beats converting it first. Quarterly billing takes 10% off instead of 20% if a full year upfront feels long.
So treat invoice creation as the trigger, not a quote to shop against. The habit that survives every crypto checkout is create-and-pay in one sitting, because every rule downstream — exact amounts, single-use addresses, catalog depth — assumes the invoice is fresh. With that framing set, the rest of this page is about the mechanics of one honest transfer and the handful of ways a clever wallet ruins it.
VPS from $4.80* — Core on the annual term (list $6/mo), one invoice for 12 months, no auto-charges. Dedicated with IPMI from $39.20/mo. Crypto invoice, no KYC.
Launch nowOne output, the printed figure, nothing clever
Here is the claim that surprises people: the smartest Cardano payment is the dumbest one. The crediting engine does not interpret intent, weigh probabilities, or forgive rounding. It scans the chain for one unspent output — a UTXO — of the printed amount sitting at the printed address, and anything else, however well-meant, becomes a support ticket with your name on it.
The mechanics follow from the chain itself. Cardano is a UTXO system, so a transfer consumes existing outputs and creates new ones, and the invoice match is literal: an output of exactly the printed figure, at exactly the addr1 address on the invoice. Indexers such as Koios make that scan a lookup rather than a crawl — the same indexing layer the public block explorers run on — which is why credit lands inside the catalog 1–10 minutes window instead of after a manual review. The address format itself is standardized in CIP-19, so there is no host-specific address type to learn.
Your wallet's change output is not a problem, which surprises people too. You send the full figure as one output; the wallet creates a second output back to your own address carrying the remainder after the fee. The matcher keys on the payment output only, so change stays your business and never touches the invoice. The network fee rides on top of the printed amount — it is never subtracted from it.
Where it breaks: wallets and habits that subtract or split. A wallet configured to pay its fee from the amount delivers a short figure and matches nothing. A send split across two outputs of half the amount each matches nothing twice. And sending twice in a panic after a slow minute can leave a second transfer with no invoice left to claim — recoverable through a ticket, but only with the txid handy, and only before you open a second order.
One transfer, exact figure, fee on top, own wallet: four rules, zero exceptions. Everything above assumes the ADA itself is native, which is exactly where the next section goes, because no amount of clean output structure rescues a payment that never touched the Cardano chain at all.
A same-ticker token is not ADA, whatever the exchange calls it
The most expensive mistake in this guide costs the whole payment, and it starts with a ticker: ADA. Exchanges list an ADA token on Ethereum and on BNB Chain with the identical three letters, and if one of those arrives at your invoice the watcher credits nothing — not slowly, not after review, nothing. A wrapped asset is a different asset, and the difference is not negotiable.
The mechanism is the chain boundary. Native ADA exists only as the settlement asset of the Cardano chain itself; the wrapped versions are contract balances on machines that have never heard of your invoice. The watcher reads Cardano and nothing else, which is why the checkout repeats the same warning for every coin: the rail you pick on the invoice is the rail the money must travel. An exchange balance, meanwhile, is often an IOU on an internal ledger until a withdrawal touches the chain at all — one more hop where the asset is not yet yours on any chain. In developer terms the distinction is chain asset versus minted token, and the project's developer portal documents it in full.
Where it breaks: the withdrawal form. You hold ADA on a large exchange, open the withdrawal dialog, and face a network selector — Cardano, or the wrapped pairs on ERC-20 and BEP-20. The wrong pick usually happens because your destination elsewhere was a browser wallet, and habit carries over. Here there is no correction pass: the tokens arrive at an address on a chain that does not contain the invoice, and no ticket reunites them with it.
The same logic runs in reverse across the nineteen-coin checkout, and it is why USDT is offered on seven separate networks — TRC-20, ERC-20, BEP-20, SPL, Polygon, Arbitrum and Optimism. Each network is its own invoice rail, and none of them substitute for each other. Your Dogecoin options fail the same way when wrappers enter the picture — the DOGE guide covers its own impostors — and the fix is identical everywhere: match the chain, not the ticker.
Chain first, ticker second — that ordering prevents the one unrecoverable error in this guide. Everything before it was recoverable with a fresh invoice, and everything after it is easier, because the wallet question turns out to have almost no wrong answers: any current Shelley-era wallet speaks the same address language, and the next section shows why the wallet you already use is probably fine.
Any Shelley-era wallet pays; the wallet is not the variable
You do not need a special wallet for this checkout, which goes against the instinct that crypto payments to strangers require ceremony. The invoice address is a standard mainnet Shelley address — the addr1 format every current wallet generates by default — so the question is never whether your wallet can pay, only whether the coins it holds are native.
That covers the whole modern field. Daedalus, the full-node wallet, works once its sync finishes; light wallets like Eternl, Lace and Typhon skip the chain download entirely and sign the same transaction against remote node data. The address format they all produce is specified in CIP-19, which is why one invoice address serves every client. Delegation — staking to a pool — changes nothing about the payment path, so there is no need to undelegate, re-register or touch your stake keys before sending.
Where it breaks: wallets old enough to predate Shelley. A restore phrase from 2019 lands in a modern app and recovers the coins, but the software of that era may not construct clean single-output sends at current fee markets. Address prefixes tell the eras apart at a glance — the Byron-style strings start differently and predate the Shelley upgrade entirely — and neither Daedalus's current builds nor the light wallets will resurrect a pre-migration paper backup without a restore pass first. The second failure is psychological: using a custodial wallet inside an exchange app, which is the exchange case from the identity section wearing a different hat.
Keys matter more than brand. The instruction that survives every scenario is to send from a wallet whose keys you hold — a phrase the checkout uses deliberately — because a custodial app can freeze, queue or gate the withdrawal, and none of that is visible to the invoice. Between the full-node original and the light field, pick by convenience; the transaction is identical on chain.
Wallet choice is a comfort decision, not a compatibility decision, and that closes the software half of the picture. The account half is smaller still: what the checkout actually knows about you is a token or a password, and the next section sizes that honestly.
The account behind the invoice is a token or a password
For a payment guide, this section has remarkably little to say about you, because the account your ADA pays into has no identity layer at all. Signup is a login token, or an email address plus a 12-character password. No passport scan, no phone number, no card on file — and the invoice itself carries no identity fields for a payment to contaminate. The no-KYC requirements page maps the same boundary for every workload.
The mechanism is deliberately boring. You create an account, pick a plan and term, and the checkout prints the invoice; the moment payment credits, provisioning starts and an SSH root login lands about 60 seconds later on the VPS line. Nothing in that pipeline branches on who you are, because the pipeline never learns. The coin you pay with is metadata about the ledger, not about the customer. What the platform does keep is operational and published: billing and panel actions on record, connection metadata held no longer than 24 hours, no payload or guest traffic logs.
Where it breaks: expectations imported from exchanges. People wait for a review step that does not exist, or hunt the dashboard for a verification badge to complete. The opposite mistake is assuming a no-KYC checkout means unobserved everywhere — an exchange that identified you when you bought the ADA keeps that record on its own books, upstream, and a withdrawal sent straight from it ties your identity to this invoice address in its history. A wallet you control keeps the two ends separate.
The cheap way to prove the whole path to yourself is one small order. Order a Core at $4.80/mo on the annual term — list $6.00/mo, one invoice, twelve months, no auto-charges — and pay it from your usual wallet. If the credit, the image step and the SSH login all behave inside your paste-from-wallet workflow, you have tested everything this page argues with a single transfer and about the price of a sandwich.
Identity, then, is a non-event by design: the checkout gates the account on a token or password and the invoice on an amount, and nothing else. That leaves time as the only honest variable left to dissect. Credit is not the same event as chain confirmation, a VPS is not the same event as dedicated metal, and the clocks each of them runs on are the next section's subject.
Credit is catalog depth, and dedicated runs its own clock
Chain confirmation and invoice credit are different events, and confusing them is the root of most payment anxiety. The watcher credits your order when a matching transfer reaches catalog depth — the depth this checkout treats as final — which lands inside a published 1–10 minute window for Cardano. Before that, the chain can say confirmed while the invoice still says pending, and both are correct.
After credit the paths split by product line. A VPS images in about a minute, which is why the checkout can promise roughly 60 seconds end to end from payment to SSH on the fast path. Dedicated metal keeps its own schedule: 2–4 hours of racking and burn-in before the box is yours, with IPMI credentials handed over last, and no coin, tip or ticket changes that order.
Where it breaks: the stall you did not cause. Exchange withdrawals batch, and a Friday-night queue can hold your transfer long past the window; the chain is innocent and the invoice is patient. The recovery drill is two steps: pull the txid from the sending wallet, check it on an explorer to confirm the send actually broadcast, and if it never broadcast, the ticket belongs to the exchange, not to the host.
If the destination is dedicated, plan the evening differently. Book the Forge at $39.20/mo on the annual term — list $49/mo, 16 cores, two 1 TB NVMe drives, IPMI on every tier — pay the ADA invoice, and let the 2–4 hour rack clock run while you do something else; the payment side finishes in minutes either way, and only the racking takes hours, on the same clock for every coin on the list.
Timing, then, is two clocks and one habit: confirm the broadcast, then leave the window alone. The payment also has a cost side inside the chain itself — fees — and their mechanics are less folklore-dependent than you probably expect, which is the next section's subject.
Fee mechanics: lovelace, size, and the dust floor
The counter-intuitive thing about Cardano fees is that they have nothing to do with congestion. There is no auction and no mempool marketplace to wait out: a fee is computed deterministically from the transaction's size and its script resource usage, so a plain payment costs the same at midnight and at peak. People arriving from gas-era chains keep waiting for fees to fall — here there is nothing that rises, so there is nothing that falls.
The mechanism is arithmetic, not markets. The chain's smallest unit is the lovelace, and the fee formula is linear in transaction size — a two-output payment carrying your figure plus your change costs only slightly more than a single-output send. Scripts written in Plutus pay more because they consume memory and execution steps on chain, and the eUTXO model validates the whole thing in one deterministic pass, which means the exact cost is knowable before you ever broadcast. The protocol documentation publishes the parameters; wallets hide them behind an estimate.
Beneath the fee sits a second floor that puzzles nobody until it does: every output must hold a small minimum reserve, denominated in lovelace and adjustable by chain parameters. Dust outputs below that floor are invalid, which is why your wallet will never produce a change output worth nothing, and why the residual after a payment always stays spendable rather than evaporating.
Where it breaks: imported habits and estimate psychology. Waiting for fees to fall is a category error — the number is not moving. Wallets quote an estimated fee that includes headroom, and the ledger charges the exact figure instead, so a payment can show a smaller final cost than the confirmation screen promised. And the chain has upgraded in place since the 2020 Shelley transition, so very old clients can mis-build transactions a modern node would reject — one more argument for a current wallet.
So the chain's cost side is deterministic and small; the price side of the order form is where the real spread lives. Which coin you pay with has no vote in it, and the next section shows what actually does — the flag above the rack.
The coin never moves the price; the rack does
Here is a claim worth testing against any host you compare: the payment coin has zero effect on price at this checkout. ADA, BTC, XMR and the seven flavors of USDT all settle the same dollar figure. What genuinely moves the number is geography — the flag above the rack — and the premium table is published, not negotiated.
The table is short. Iceland and Norway carry +20%, Switzerland +35%, Luxembourg +15%, and the other eight of the twelve locations bill at base list: Amsterdam, Frankfurt, Stockholm, Helsinki, Hong Kong, Tokyo, Singapore and Taipei. The annual term then applies −20% to the dollar total before any coin conversion happens, and the quarterly term takes 10% off instead. Your rate risk from the first section applies only to the already-discounted figure.
Where it breaks: choosing the rack for the wrong reason. People pick Zurich or Reykjavik expecting faster delivery or better ping, then meet the premium; delivery depends on reputation and routing, not on the flag's mystique. Pick the jurisdiction for its legal posture — retention law, data protection regime, distance from your threat model — which is the entire argument of the jurisdiction-first guide, and see the offshore primer for how the flags differ in practice.
The rack does decide real things you will feel. Amsterdam peers at AMS-IX and DE-CIX behind a 40 Gbps uplink; Tokyo rides JPIX and JPNAP at 100 Gbps; Reykjavik sits in a Tier IV building under Icelandic law with no mandatory retention. Reykjavik and Helsinki both peer on FICIX; Zurich rides SwissIX. Those are physical facts with legal consequences, unlike the coin field on the invoice, which is pure transport.
Coin constant, geography variable — with the pricing map flat and the payment mechanics settled, everything left is assembly: the full sequence from empty cart to SSH prompt, in one pass, and it is shorter than you expect, because nothing in it repeats.
The ADA payment, in the order to run it
Run the whole thing in this order. Open the deploy page, choose the plan and the term — annual if the 20% cut suits you — and let the checkout print the invoice: one addr1 receive address, one exact ADA figure, one rate locked at creation. Read the figure off the invoice, not off a converter tab, because the printed number is the contract the watcher will match.
Second, send from a wallet whose keys you hold — any Shelley-era client works — as a single output of the printed amount with the network fee on top. No memo, no tag, no second transaction while the first is in flight. If the wallet offers to subtract its fee from the amount, decline; the exact-amount rule is the only discipline the chain asks of you, and it is checkable before you press send.
Third, wait out the window. Credit lands at catalog depth inside 1–10 minutes; a VPS then images in about a minute and hands you an SSH prompt roughly 60 seconds after payment on the fast path. Do not refresh, do not double-send. If ten minutes becomes an hour, pull the txid, check it on an explorer, and open a ticket with it attached.
Fourth, if the box is dedicated, reset expectations before the invoice: 2–4 hours of racking, IPMI credentials last, no coin expedites it. The ADA leg is identical — exact figure, one output, one address — and finishes in minutes either way; only the racking takes hours, and it runs the same for Bitcoin payers and Monero payers alike.
That is the whole sequence: create the invoice, pay it exactly, respect the two clocks, keep the txid until you are logged in. Every failure earlier in this page is a deviation from one of those steps, and none of them needs a rescue manual — just a fresh invoice and one clean transfer.
Does an ADA invoice need a memo or tag?
No. A Cardano invoice is a receive address plus an exact amount, with nothing else to mistype. The one discipline is the exact-amount rule: the printed figure must arrive intact in a single output, with the network fee paid on top rather than deducted from it by the sending wallet.
Can I pay straight from an exchange withdrawal?
You can, and the transfer credits the same way. The trade-off is upstream: the exchange identified you when you bought the ADA and now holds a record linking your identity to this invoice address. A wallet whose keys you control keeps the two ends of the payment separate.
What happens if I send the wrong amount?
The watcher matches the printed figure literally, so a short or split send matches nothing and the order stays pending. Open a ticket with the txid and support can trace the transfer. The cleaner habit is one output at the exact printed amount with the fee on top.
Is there KYC on this checkout?
No. An account is a login token or an email plus a 12-character password, and the invoice carries no identity fields. Where you bought the ADA is a different company with its own records, upstream of this checkout entirely and outside its reach.
Why is my payment uncredited after an hour?
The usual cause is exchange-side batching, where the sending platform queues withdrawals and broadcasts them later. Pull the txid from your wallet and check it on a public explorer: if it has not broadcast, the queue is at the exchange; if it has, attach the txid to a ticket.
Can other tokens ride along with the ADA?
The watcher matches the ADA figure and ignores anything else in the transfer, though the cleanest send is pure ADA in one output. Token-bearing transfers consume the same output structure, so pure single-asset sends are the ones that match first time, every time.
Primary sources
More ways to pay
Pay with Bitcoin · Pay with Monero · Pay with USDT (TRC-20/ERC-20/SPL) · Pay with Litecoin · Pay with Ethereum · Pay with Solana · Pay with x402 · Pay with Dogecoin · Pay with XRP · Pay with TRX · Monero on bare metal · Dedicated servers with crypto · Pick the jurisdiction first.
Ready to launch?
Build the box — VPS or bare metal — create the password, pay the invoice that follows.