Buy VPS, APIs, and Dev Tools with Crypto (2026)

Last Tuesday at 2 AM I needed to spin up three Hetzner boxes for a load test. Card on file had expired. Bank account? Sure, but that's a 3-day ACH wait. I had $4,000 in ETH sitting in a wallet. Sent $500 to my [VeloCards](https://velocards.com) account, waited four minutes for confirmations, transferred to my virtual card, and had the servers provisioned before 2:20 AM.

That's the point of this whole thing. Dev spend doesn't wait for banking hours.

What You'll Learn: Pay for VPS with Crypto

By the end of this tutorial, you'll know how to pay for VPS hosting, API credits, and developer SaaS with crypto — without selling to fiat first and waiting for bank transfers. We'll cover the actual providers that work, the ones that are tricky, and how to structure your virtual cards for clean expense tracking.

I'm using [VeloCards](https://velocards.com) because it accepts BTC, ETH, and USDT directly. Some crypto cards force you to swap to stablecoins first. VeloCards doesn't — you can load Bitcoin and spend it as dollars on the other end. Check [VeloCards pricing tiers](https://velocards.com/#pricing) to see which tier fits your monthly spend.

Prerequisites

Before you start:

- A VeloCards account — email-only tier works for testing (capped at $100 lifetime, one card), but serious dev spend needs KYC verification for unlimited
- Crypto in a wallet you control: BTC, ETH, or USDT
- A list of what you're actually paying for (helps with card organization — more on that below)
- 15-20 minutes for first-time setup; subsequent loads take under 5 minutes

Step 1: Map Out Your Dev Spending Categories

Skip this if you're just testing. But if you're running real infrastructure, take five minutes to list what you pay for monthly.

Mine looks something like:

- **VPS/Cloud:** Hetzner ($89/mo), DigitalOcean ($45/mo for side projects), Vultr ($20/mo for a specific thing)
- **APIs:** OpenAI ($200-400/mo depending on usage), Anthropic ($150/mo), various smaller ones
- **Dev SaaS:** GitHub ($4/mo), Linear ($10/mo), Vercel ($20/mo), Railway ($30/mo)

Why does this matter? Because I run three separate virtual cards — one per category. When the credit card statement equivalent shows "HETZNER ONLINE" versus "OPENAI API," I know exactly which budget bucket got hit. Reconciliation at tax time went from a nightmare to twenty minutes.

Card creation at Tier 2 costs $30 per card plus $15/month per card. If you're only spending $100/month total, one card is fine. If you're at $500+/month, the organization is worth the fee.

Step 2: Create Your Virtual Card(s)

Log into VeloCards and create a card. You'll get a card number, CVV, expiration, and billing address immediately.

The billing address is important. It's a US address assigned to your card. When Hetzner or DigitalOcean asks for billing details, use this exact address — not your personal address. Address mismatches cause more checkout failures than anything else in my experience.

For dev tools specifically, I name my cards by category in the dashboard: "DEV-VPS," "DEV-API," "DEV-SAAS." Makes it obvious at a glance.

Step 3: Fund with Crypto

Click "Add Funds" and pick your asset: Bitcoin, Ethereum, or USDT.

Quick decision tree:

**Loading $500+?** BTC is fine. The $2-4 network fee is negligible at that scale. And if you're specifically holding BTC and want to spend BTC, this is the whole point.

**Loading under $300?** USDT on Arbitrum or Base. Gas under $0.10. Confirms in seconds. I've loaded $50 for a quick Vultr test and paid less than a cent in fees.

**Need it in the next 10 minutes?** USDT on L2. BTC can take 30-60 minutes during mempool congestion. ETH mainnet is middle ground — usually 3-5 minutes but gas can spike randomly.

For this walkthrough, let's say you're sending ETH. Copy the deposit address, send from your wallet (MetaMask, Coinbase, hardware wallet, whatever), and wait for confirmations. VeloCards credits after 2-3 confirmations — usually 3-5 minutes.

The exchange rate locks when you initiate, not when it confirms. Price drops while you wait? You still get the rate from when you sent.

Once funds appear in your account balance, transfer them to your specific card. That's instant.

Step 4: Add the Card to Your Providers

Now the actual spending part.

DigitalOcean

Go to Billing → Payment Methods → Add Payment Method. Enter your VeloCards card number, expiration, CVV, and the billing address from your dashboard.

DigitalOcean does a small authorization hold (usually $1-5). Should clear immediately. If it declines, double-check the address format — DigitalOcean is picky about state abbreviations and zip codes.

Once added, the card works for all future charges. Droplets, Spaces, managed databases — all hit the same card.

Hetzner

Hetzner's billing is in the Robot or Cloud Console depending on which product line you're using. Navigate to Billing → Payment Methods. Add a credit card.

Hetzner's a German company, so their fraud checks can be slightly stricter on US cards. But VeloCards uses commercial credit BINs from recognized US banks — passes without issues. I've run a $400+ monthly Hetzner bill through it for six months with zero declines.

One quirk: Hetzner invoices in euros but can charge your card in dollars if you pick USD as your billing currency. Make sure you're not getting hit with currency conversion fees on top of the VeloCards fees. With a USD-denominated card, pick USD billing.

Vultr

Account → Billing → Payment Methods. Standard card add flow. Vultr's fraud filtering is lighter than some others — I've never had an issue here.

OpenAI (API Credits)

Settings → Billing → Payment Methods. Add your card. OpenAI does usage-based billing, so make sure your card has buffer. If you spike to $300 in API calls and your card only has $250 loaded, the card declines, your API access gets cut, and whatever you were running breaks at the worst possible moment.

I keep 150% of my expected monthly usage loaded. Paranoia from experience.

Stripe-Billed SaaS

Most indie dev tools — Linear, Vercel, Railway, Render, PlanetScale, etc. — bill through Stripe. Stripe basically accepts anything with a valid BIN. If the address matches, it goes through. I've never had a problem here, which is more than I can say for my actual bank card that got flagged twice last year for "suspicious" $19 charges. (Thanks, Chase.)

The one exception: some Stripe Connect merchants (smaller tools built on Stripe's platform) have their own fraud rules on top of Stripe's. I had one random tool decline a $19/month charge because they'd turned on aggressive fraud filtering. The fix was emailing their support to whitelist the card. Annoying, but rare.

Step 5: Set Up Recurring Loads (Optional)

You can't auto-fund VeloCards from crypto — you have to manually send each deposit. Honestly? That's annoying. I'd kill for a "sweep $500 from this wallet on the 1st" feature. But we're not there yet. The workaround is setting a calendar reminder.

I load on the 1st of every month. Takes 5 minutes: check balances across my three cards, load whatever's needed for the month, done. Some people prefer weekly small loads. Whatever matches your cash flow.

If you're running multiple ad accounts and dev infrastructure from the same crypto treasury, [JustBrowser's multi-profile management](https://justbrowser.app/blog/isp-proxies-setup-justbrowser-tutorial) keeps those profiles separated. I use separate browser profiles for each platform's billing dashboard — overkill maybe, but it's saved me from a few "wait which account am I logged into" moments.

Common Errors and How to Fix Them

"Card declined" on first add

Nine times out of ten: billing address mismatch. Copy-paste the address exactly from your VeloCards dashboard. Including the weird state format if it's abbreviated.

If address is correct and it still declines, check card balance. Some providers do authorization holds above the expected first charge. Add an extra $20-50 buffer and retry.

Charge went through but then got refunded

This happens occasionally with new accounts on providers that do fraud reviews. The charge succeeds, then 6-12 hours later it reverses and your account gets flagged for manual review. Usually a support email explaining you're a real person with a real business clears it. VeloCards' commercial BINs help here — prepaid BINs get way more scrutiny.

Service suspended for payment failure

If your card balance runs out and a recurring charge fails, providers suspend service. Usually there's a grace period — 24-72 hours — to update payment and restore service. DigitalOcean is pretty forgiving (you get multiple retry attempts). Some smaller providers cut access immediately.

The fix is keeping buffers on your cards. I aim for 2x my monthly spend loaded at any given time. Yeah, that's capital sitting in a card not earning yield. Yes, I know that's financially suboptimal — my DeFi-brained friends remind me constantly. But the alternative is 2 AM server outages because a $89 charge bounced. Trade-off.

Can't withdraw USD back to crypto

VeloCards cards are spend-only. You load crypto, it converts to USD, you spend USD. You can't convert USD balances back to crypto through the card. If you need to "cash out" a card balance, spend it down or contact support about withdrawal options.

What Actually Works: My Stack

Here's what I've been running successfully for the past eight months:

| Provider | Monthly Spend | Card | Status |
|----------|---------------|------|--------|
| Hetzner | $89-120 | DEV-VPS | No issues |
| DigitalOcean | $45 | DEV-VPS | No issues |
| Vultr | $20 | DEV-VPS | No issues |
| OpenAI API | $200-400 | DEV-API | No issues |
| Anthropic API | $150 | DEV-API | No issues |
| Vercel | $20 | DEV-SAAS | No issues |
| Railway | $30 | DEV-SAAS | No issues |
| GitHub | $4 | DEV-SAAS | No issues |
| Linear | $10 | DEV-SAAS | No issues |

Total: roughly $600-900/month funded from ETH and USDT.

I tried adding Cloudflare Workers and it declined once, passed on retry. That's the only hiccup. I think their fraud rules flagged the first attempt because the card was new.

The Cost Math

VeloCards Tier 2 (KYC verified, under $100K annual): 4% deposit fee, $30 card creation, $15/month per card.

If I'm loading $800/month across three cards:

- Deposit fee: $32/month
- Monthly card fees: $45/month
- Total overhead: $77/month, or about 9.6% of spend

Sounds steep until you compare to the alternative: sell ETH on exchange (0.5% fee), withdraw to bank ($15-25), wait 3-5 days. And you've triggered a taxable event. Look, I'm not pretending this is cheap. It's not. But "expensive and instant" beats "cheaper and takes a week" when you need servers now.

At Tier 3 ($100K+ annual), deposit fee drops to 2.5%. At Tier 4 ($500K+), it's 2%. If you're running serious infrastructure, the math improves.

For tracking where that dev spend actually goes — which API calls are worth the cost, which servers are underutilized — [JustAnalytics](https://justanalytics.app/blog/build-conversion-funnel-without-cookies-justanalytics) can tie your analytics to your infrastructure decisions. And if you're also running paid ads alongside dev infrastructure, [ClickzProtect's fraud detection](https://clickzprotect.com/blog/real-cost-click-fraud-2026) catches the fraudulent clicks before they eat your budget.

Next Steps

Once you've got your dev stack billing through crypto cards:

**Monitor card balances weekly.** Usage-based APIs (OpenAI, Anthropic) can spike. Don't get caught with an empty card during a production deploy.

**Request higher tiers when you qualify.** If you're pushing $8K+/month, you're paying $320/month in deposit fees at Tier 2. At Tier 3, that drops to $200. Email support with your spending history.

**Separate cards by vendor risk.** Sketchy one-off purchases (random dev tools, obscure API providers) go on a separate card from your mission-critical infrastructure. If a card gets compromised or flagged, you don't want Hetzner going down because some random tool leaked your number.

**Keep detailed records.** VeloCards provides transaction history, but export it monthly into your own system. When you're telling your accountant "this is business infrastructure spend funded from ETH," you want receipts.

Frequently Asked Questions

Can I pay for DigitalOcean with Bitcoin directly?

DigitalOcean doesn't accept Bitcoin directly — they only take credit cards, PayPal, and Google Pay. But you can fund a crypto virtual card with BTC and use that card on DigitalOcean. The card looks like a normal Visa or Mastercard to their billing system. Same goes for most VPS providers. They accept cards, and a crypto-funded virtual card is still a card.

Will VPS providers block crypto-funded cards?

Most VPS providers don't care where your card's funds come from — they see a Visa or Mastercard from a recognized bank. The issues happen with prepaid BINs that get flagged by fraud systems. VeloCards uses commercial credit BINs, not prepaid, so the card passes the same checks as a Chase or Amex. I've used it on DigitalOcean, Hetzner, Vultr, and Linode without declines.

Which crypto is cheapest for paying monthly server bills?

USDT on an L2 like Arbitrum costs under $0.10 in gas. For a $50-100/month VPS bill, the gas savings vs. ETH mainnet or BTC network fees add up over a year. If you're specifically spending BTC to avoid selling to fiat, the network fee is worth it — but for routine monthly bills, L2 stablecoins make more sense.

Can I get a refund to my crypto card if I cancel a service?

Yes, but the refund comes back in fiat (the card's denominated currency), not crypto. VeloCards cards are USD-denominated — when a merchant refunds you, the dollars hit your card balance. You can then spend that balance normally or withdraw it. The original crypto you deposited isn't returned as crypto.

---

Spend Crypto Online — Without an Off-Ramp

VeloCards is a **virtual card** for spending BTC, ETH, and USDT at any Visa or Mastercard merchant online. No bank transfer dance, no off-ramp fees, no waiting days for funds to hit fiat. Tier-based pricing — fees drop as your annual spend grows.

**[Open an account →](https://velocards.com/)** · [See the spend tiers](https://velocards.com/#pricing)