How to pay for web hosting with USDC in 2026

Hosting is the one category where paying in a stablecoin is not a workaround. The invoices are small and recurring, the product is delivered instantly, and the customers are technical enough that hosts built the integration properly rather than bolting on a widget. It is the largest category in this directory, and USD Coin is the stablecoin most hosts settled on.

It is also where the one unrecoverable mistake in stablecoin payments — sending on the wrong network — happens most, because a hosting checkout offers more chains than almost any other kind of merchant. So this guide is built around one rule: you only send USDC on a network the host documents for USDC. Not for “crypto”, not for “ERC-20 tokens”, not for USDT. For USDC.

Everything below is taken from the hosts’ own payment documentation as recorded in our merchant profiles, each of which carries the source URLs and the date we read them. Where a host does not publish something, this guide says so rather than guessing.

Before you start: three things to have ready

USDC on a network you can name. Open your wallet or exchange and check which chain your USDC is actually on. “USDC” in an exchange balance is not on any chain until you withdraw it, and the withdrawal screen will make you choose one. That choice has to match the host.

A little of the network’s gas token. On Ethereum, Base, Arbitrum, Optimism and Polygon you need a small amount of ETH (or POL on Polygon) in the same wallet to pay the transaction fee; on Solana, a little SOL. Shopify checkouts and Base Pay sponsor the gas, but no hosting checkout in our directory does. A wallet holding $50 of USDC and no gas token cannot send anything.

The invoice amount, and the host’s minimum. Some gateways set per-asset floors. Time4VPS’s help centre says Coinify sets a minimum per asset and revises it; on a cheap annual VPS the invoice can fall below the floor for the asset you wanted. Check before you plan around it.

Step 1: pick a host that documents your network for USDC

This is the step people skip, and it is the one that matters.

A merchant record on this site carries two flat lists, the coins accepted and the networks supported, and for a long time readers assumed the cross product: if a host takes USDC and USDT and lists Ethereum and Tron, surely it takes USDC on Tron. It need not, and several do not. That is why our profiles now show network support per coin, exactly as the host states it, and why the web hosting that accepts USDC page has a “Network by coin” column and a set of questions that filter the table by the chain you hold.

Hosts fall into three tiers by how much they tell you.

Hosts that publish a matrix

These are the easy cases. The host names each coin and the chains it runs on, so there is nothing to infer.

Hostwinds documents its Stripe Crypto integration as an exact token and network matrix: USDC on Ethereum, Solana, Polygon and Base; USDP on Ethereum and Solana; USDG on Ethereum. Its documentation adds that only the token and network shown in your specific checkout session are valid, whatever wallet options Stripe happens to display.

RANDHOST publishes the most useful kind of table — coin, then networks. USDC on Ethereum, BSC, Solana, Polygon, Arbitrum, Base and Optimism; USDT on Ethereum, BSC, Tron, Solana, Polygon, Arbitrum and Avalanche. Note what that means: USDC has no Tron option and USDT has no Base option, at the same host. That is precisely the case the cross product gets wrong.

Cherry Servers names USDC and DAI in its billing documentation and, in a blog post explaining why it dropped USDT, lists the networks USDC is accepted on: Ethereum, BNB Chain, Arbitrum, Optimism and Polygon. DAI’s network is not stated, so our record does not state it either.

HOSTKEY is the instructive edge case. It takes USDC, USDT, DAI, GUSD and USDP through BitPay — and then says, in its own payment terms, that ERC-20 tokens are accepted on the Ethereum network only. BitPay supports Base, Polygon and Solana for other merchants; HOSTKEY says it does not take them. The host’s narrower statement governs, and our record lists one network where other BitPay merchants list six.

Time4VPS lists USDT as three separate selectable assets — Ethereum, Polygon and Tron — so the network is chosen for you. For USDC it publishes the ticker without a network, so for that coin you are back to reading the checkout.

Hosts that name a gateway and stop

Hostinger says it accepts “a wide range of cryptocurrencies” through CoinGate and names none itself. Namecheap documents adding funds via BitPay and links out to BitPay’s list. HostSailor says “Bitcoin, XRP, Ether, Litecoin, and 50+ other altcoins” via CoinGate. Prepaid-Host shows a USDC icon and names CoinGate. Acceptance at all four is real; the coin list is somebody else’s, and it changes when the gateway changes it — CoinGate withdrew USDT for EU merchants under MiCA, and the EU hosts on that gateway lost it without publishing anything themselves.

For these hosts our records carry the gateway’s published network list, cited as a second source, and the status “varies” rather than “verified”. On the spend page their “Network by coin” cell reads “pairing not documented” where the host has more than one coin, because nothing on the host’s own site says which chain goes with which coin. The chain you can use is whatever the gateway’s checkout offers you on the day.

Hosts that name the coin and nothing else

Vultr is the largest cloud provider in the directory to name its stablecoins — USD Coin, Paxos and Gemini dollar, via BitPay — and it states no network for any of them. Porkbun is admirably direct (“We accept USDC cryptocurrency payments via Coinbase Business”) and equally silent on chain. FlokiNET names both Tether and USDC and no network.

These are fine to use. You simply cannot plan the network in advance; you read it off the checkout in step 3.

Step 2: decide how you will handle renewals

Here is the thing that catches people more often than networks do: you cannot put a server on autopay with stablecoins. Not at any host we have verified. A gateway generates a fresh address per invoice, something has to trigger the send, and there is no stored payment method to charge. Hostwinds says so in its own documentation. Hostinger’s payments page says renewals cannot be auto-charged from a crypto payment. Most others leave you to discover it at the first renewal.

Two models exist, and the hosting page’s questions let you filter by them.

Credit balance. Your transfer tops up an account balance, and invoices are paid from it. Vultr, Namecheap, HOSTKEY and Prepaid-Host work this way. One transfer can cover several renewals, which is the closest thing to autopay this model allows, and Namecheap documents that a funded balance will auto-renew domains when it covers the renewal. The trade is that the money is now credit: HOSTKEY says its balance can be spent on any HOSTKEY service or refunded via the original method, Prepaid-Host says credit never expires, and Namecheap says BitPay deposits are non-refundable. Read your host’s line before sending a large top-up.

Per-invoice checkout. You pay each invoice from the client area. Most of the hosts on the page work this way. The practical advice is to buy the longest term you are comfortable with in one transaction: a three-year VPS paid once in USDC on Base costs pennies in fees and removes eleven future opportunities to forget.

Either way, put the renewal date in a calendar. A suspended server is a worse outcome than a card fee.

Step 3: reach the payment step and read the network off the screen

Order the plan as normal. At the payment method step, choose the crypto option — it is labelled “Cryptocurrency”, “BitPay”, “CoinGate”, “Coinbase” or “Crypto” depending on the host — and continue to the gateway’s page.

Now stop and read. The gateway page will show a coin selector and, for a stablecoin, a network selector or a list of network-specific entries. This is the moment the guide has been building towards:

1. Select USDC, not “USD” or a look-alike ticker.
2. Select a network the host has documented for USDC if it published one, and that your wallet holds USDC on. If the host published nothing, this screen is the only documentation there is — choose the network your wallet is on, and if it is not offered, do not improvise. Withdraw from your exchange onto an offered chain instead.
3. Copy the address and the exact amount the gateway shows. RANDHOST’s FAQ describes what happens otherwise: an underpayment is not processed until you send the balance, and an overpayment is refunded to the sending wallet. Not every host is that accommodating.
4. Note the timer. Gateway invoices expire. Namecheap’s documentation gives BitPay’s payment window as fifteen minutes, with the quoted rate holding only while it is open. Do not open the invoice and then go looking for your seed phrase.

If the network you want is not on the list, that is the answer. It does not mean the host is wrong or the page is broken; it means that host, through that gateway, does not take USDC on that chain today. Pick another chain or another host.

Step 4: send from your wallet and confirm

Paste the address into your wallet’s send screen, select the same network, enter the exact amount, and check the address once more before confirming. Some wallets show a network mismatch warning; most do not.

Confirmation times vary by chain. Base and Solana confirm in seconds; Polygon and Arbitrum in seconds to a minute; on Ethereum mainnet gateways typically wait one to five minutes, longer when congested. Hostinger notes that crypto payments are not instant because they need multiple blockchain confirmations, and Prepaid-Host says credit is applied “after network confirmation” rather than immediately as with PayPal or card. If the gateway page has not updated after a few minutes, look up the transaction hash on a block explorer for the network you used before contacting anyone — the answer is usually “still confirming”.

Keep the transaction hash. It is the reference every host’s support team will ask for, and Genghis — a gift card merchant, but the practice is the same — asks for it by name when handling payment errors.

Step 5: what a wrong-network send looks like, and what to do

If you sent USDC on a network the host’s address does not exist on, the funds have gone to an address nobody controls on that chain. RANDHOST and Genghis both state in their own documentation that a wrong-network transfer results in lost funds, and no host in our directory documents a recovery process. Whether a particular gateway can ever retrieve a mis-sent token is between you and its support desk, and nothing on any host’s site promises it.

So the useful advice is entirely preventive. Read the network off the gateway screen. Match it in your wallet. Send a small test amount if it is the first time you have used that chain and the host allows partial payment (RANDHOST holds an underpayment until you top it up). And if you are uncertain, stop and ask support before sending — a support ticket costs an hour; a mis-sent payment costs the payment.

Step 6: keep an eye on the coin list

Hosts lose stablecoins as well as gain them, and the ones that do not publish their own list lose them silently.

Cherry Servers is the exception that shows how it should be done: when CoinGate stopped processing USDT for EU merchants under MiCA, Cherry Servers published a dated post, set a hard stop for 1 April 2025, and told customers to move to USDC. We recorded the change with the merchant’s own date. Most of its EU peers on the same gateway made the same change with no announcement at all, and the only way to know is to reach the checkout.

Two practical habits. Before a renewal, glance at the host’s profile here — the changelog and the “last checked” date tell you whether anything moved. And if you rely on one host, follow it: every profile has a follow form that sends one dated, sourced email when its stablecoin options change, with an unsubscribe link in every message.

When a card is simply better

We would be doing you a disservice to leave this out.

If your hosting bill is small, the host’s gateway only offers Ethereum mainnet, and you have no particular reason to avoid a card, paying in USDC costs you more money and more attention for no benefit. Hostinger states that products purchased with cryptocurrency are not refundable, which removes its money-back window from the deal. HOSTKEY notes that a BitPay ID “may be required” for crypto payments, so the privacy case is weaker than it looks at gateway-fronted hosts.

The stablecoin case for hosting rests on three things: a cheap network (Base, Polygon, Arbitrum, Solana), a larger prepayment that amortises the attention cost, or a genuine need to pay without a card in your name. Offshore and privacy hosts such as FlokiNET and HostSailor exist substantially for the last reason. If none of the three applies to you, use the card. A guide that only ever says “yes, pay in crypto” is marketing.

A worked example

You hold USDC on Base in a self-custody wallet with a little ETH for gas, and you want a VPS paid for a year.

• On the hosting page, answer “Base” to the network question. The table narrows to hosts that document USDC on Base — at the time of writing, Hostwinds, RANDHOST and Prepaid-Host, the last of these through CoinGate’s list rather than its own statement.
• Open the profiles. Hostwinds pays per invoice through Stripe; RANDHOST pays per invoice with exact-amount handling documented; Prepaid-Host tops up a euro credit balance.
• Order the annual plan. At checkout choose the crypto option, then USDC, then Base. Copy the address and amount.
• In your wallet, confirm the network is Base, paste, send. Wait for the gateway page to confirm.
• Put the renewal date in your calendar, because nothing will charge you automatically next year.

Total network cost: well under a cent. Total time: a few minutes. The one thing you did not do was guess.

Where to go from here

• The live, filterable list: web hosting that accepts USDC, and its USDT counterpart.
• Domains are the natural next purchase and behave the same way: domain registrars that accept USDC.
• Anything else in the directory, by coin, network and country: the finder.
• What each verification status means and how a record earns it: the verification methodology.
• The network choice in more depth: best networks for stablecoin payments and what stablecoin payments actually cost.

If a host’s checkout shows something different from what its profile here says, believe the checkout and tell us. The correction gets logged against the record and appears in What’s Changed.