Bill hosting and server plans by card, and keep the money you’re paid.
Hosting attracts stolen cards that spin up servers and dispute the bill, and processors judge a host by what its customers run. Railbed takes your customers’ cards for hosting, VPS and server plans and settles every payment to a wallet you control.
- No application to pass
- No setup fee
- Settled sales stay yours
Press the card to run an example sale.
- Settles to
- Your own wallet, as USDC on Polygon
- Chargebacks
- Settled sales can’t be pulled back. Card disputes go to the provider
- To start
- An email, your website and a payout wallet. No setup fee, no monthly fee
- Buyer ID checks
- Providers decide. Smart Routing picks the one least likely to ask
How can a web hosting or VPS company take card payments?
Hosts can take cards, but processors treat them as high risk because stolen cards are used to buy servers and are disputed weeks later, and because a host is judged by what its customers run. Railbed takes your customers’ cards through independent, licensed card providers and settles each payment to a wallet you control, with no underwriting and no application to pass. It never stores a card or charges one automatically, so each billing period is an invoice the customer pays, or a longer term bought up front.
Why do card processors treat web hosts as high risk?
A hosting company hands over a server minutes after a card is charged, and that server is worth stealing. People who plan to send spam, run phishing pages or mine on someone else’s hardware rarely pay with their own card, so hosts take a steady stream of stolen-card orders, and the disputes that follow weeks later.
- 50%Share of new subscriptions some hosts reported as fraudulent
- 1.5%Visa’s fraud and dispute threshold before a merchant is flagged, since April 2026
Some hosting providers report that 50% of all new subscriptions are fraudulent
The problem is old and well documented. Spamhaus, which tracks abuse on hosting networks, wrote in 2012 that abusers “usually use stolen credit cards or compromised Paypal accounts to obtain service”, and that “Some hosting providers report that 50% of all new subscriptions are fraudulent”. Large hosts still build their sign-up around it: Hetzner’s fraud prevention FAQ says it may ask a new customer to verify with a government ID or by prepaying with their own credit card before it processes an order.
Every stolen-card order that gets through comes back as a dispute, with a fee, and pushes the host toward the threshold in Visa’s acquirer monitoring programme, which flags merchants whose fraud and dispute rate passes 1.5%. Small hosts feel it most: a single carding run against a new VPS plan can produce more disputes in a week than a year of honest customers.
Processors also look past the host to its customers. Stripe’s restricted businesses list puts “cyberlocker and file-sharing services” in a tier that needs extra due diligence, and a host with privacy-minded or offshore customers can find itself reviewed for what those customers might store. When a processor decides the risk isn’t worth it, the host loses card payments for every customer at once.
What hosts run into
- Carding waves on cheap plans drive the dispute rate up, and the account gets a reserve or a closure notice.
- Fraud checks strict enough to stop the carders also turn away honest customers abroad.
- Recurring card charges that customers forget about turn into “I didn’t authorise this” disputes at renewal time.
What one stolen-card order costs a host
Hosting is sold at prices so low that the dispute costs more than the sale. Take a $6 VPS ordered with a stolen card and disputed three weeks later, with the fees the processors and card networks publish:
| What it costs at a conventional processor | Published figure | Where it’s published |
|---|---|---|
| The month of service, debited back from your balance | $6 | Your own price list |
| The fee for receiving the dispute, in the United States | $15, not refunded | Stripe |
| The fee for contesting it, returned only if you win | $15 | Stripe |
| The fee once a merchant is in Visa’s monitoring programme | $8 for each fraudulent or disputed transaction | Merchant Risk Council |
| The server | Whatever it sent before you closed it, and any blocklist entries that follow | Your abuse desk |
A $6 sale that ends as a $21 loss, before anyone has cleaned up the IP address, is why hosts spend so much effort on sign-up checks. It is also why the same checks turn away honest customers: the cheapest way to avoid a $15 fee is to refuse any order that looks unusual.
How does Railbed fix it?
Railbed is card checkout for hosting companies that never holds your money. Customers pay with the card they already have, an independent licensed card provider charges it, and each payment settles as USDC straight to a wallet you control, usually minutes after the customer pays.
| What goes wrong today | With Railbed |
|---|---|
| Stolen-card disputes arrive after the server has been used, and come out of your balance | Settled payments can’t be pulled back from your wallet. Card disputes go to the provider that charged the card |
| A dispute spike brings a reserve or a closure | Nothing is held back from your payments, and there’s no balance to freeze |
| A processor reviews what your customers host | No underwriting and no application to pass |
| Card details pass through your billing system | Card details are entered on the provider’s page, never on yours |
| Automatic renewals that customers forget and dispute | Each renewal is a payment the customer chooses, with an emailed invoice and reminders |
| One acquiring bank decides which customers’ cards go through | Smart Routing sends each customer to the card provider most likely to approve them |
Railbed checks that the right amount reached the right wallet before it marks a payment Paid, and a signed webhook tells your billing system to provision or extend the service.
Which way to bill fits your hosting business
Hosts bill in three shapes: a few fixed plans, servers ordered from a control panel, and contracts invoiced each period. Each has its own way to sell with Railbed, and most hosts end up using two.
| What you sell | What to use | What you build |
|---|---|---|
| Shared hosting in a few fixed plans | A pricing table with up to four plans, on its own page or embedded in yours | Nothing. Create the account when the payment shows Paid, or from a webhook |
| VPS and cloud servers ordered in a control panel | A checkout session for each order or top-up, from the REST API | One API call with your order ID as the reference, and one webhook handler that provisions |
| Dedicated servers, colocation and reseller accounts | An invoice for each period, with lines for the server, addresses and bandwidth | Nothing from the dashboard, or one call to the invoices API from your billing system |
| Hosting sold from a WordPress site | The WooCommerce plugin | Nothing. Install it and connect your account |
| Domains, licences and one-off extras | A buy button or a line on the next invoice | Nothing |
Railbed’s ready-made integrations are Shopify, WooCommerce, Zapier and n8n. A hosting billing panel connects through the REST API and signed webhooks: your system creates the session or the invoice, and the payment.paid event tells it to provision or extend.
What stays your responsibility?
Railbed takes payments. It doesn’t police your network or your customers, and it doesn’t handle abuse reports for you. Your terms of service, abuse handling, and the laws that apply to your network and your customers stay yours. Railbed’s acceptable use policy holds only the limits the law sets, such as child sexual abuse material, money laundering and sanctions, and a host knowingly serving those falls inside them.
Abuse complaints and takedown notices
A payment company doesn’t answer your abuse mailbox, and the law doesn’t expect it to. Two duties sit with the host, whoever takes its payments:
- Copyright notices in the United States. The US Copyright Office explains that to qualify for the safe harbour in section 512 of the copyright law, a service provider that lets users store material “must designate an agent to receive notifications of claimed copyright infringement”, by publishing the agent’s contact details on its own website and giving the same details to the Office’s public directory.
- Reports of spam, malware and botnets. Spamhaus advises that “Hosts should null-route a customer’s IP address upon a credible report of spam, malware hosting, or botnet activity until they can contact the customer”, and that your terms should say you reserve the right to.
Neither is legal advice, and other countries have their own rules. The point for payments is narrower: a host that answers its abuse reports is running the kind of business the next section separates from the kind that gets sanctioned.
Offshore, privacy and “bulletproof”: where the line is
Offshore hosting and privacy hosting are lawful products: servers in a country the customer chose, sold with as little personal data as the law allows. “Bulletproof” hosting is something else, and since 2025 governments have named it. The US Treasury describes bulletproof providers as selling “access to specialized servers and other computer infrastructure designed to evade detection and defy law enforcement attempts to disrupt these malicious activities”.
- Oct 2012
Spamhaus writes that some hosting providers report half of all new subscriptions as fraudulent.
- Feb 2025
The United States, Australia and the United Kingdom sanction Zservers, a Russia-based bulletproof host, for supporting LockBit ransomware attacks.
- Jun 2025
Stripe adds a $15 fee for countering a dispute in the United States, beside the $15 fee for receiving one.
- Jul 2025
The US Treasury sanctions Aeza Group, a bulletproof host, for supporting ransomware and data-theft groups.
- Nov 2025
The same three countries sanction Media Land, and US agencies publish a guide for internet providers on bulletproof hosts.
- Apr 2026
Visa lowers the ratio of disputes and fraud reports at which it counts a merchant as excessive, from 2.2% to 1.5%.
The Media Land sanctions of 19 November 2025 named a company that supported “ransomware operations and other forms of cybercrime”. None of the three was sanctioned for being offshore or for protecting customers’ privacy. They were sanctioned for serving criminals knowingly and ignoring the reports.
That distinction matters for payments in two ways. A processor that sees the word “offshore” on your site may not make it, which is how lawful hosts end up reviewed for the label alone. And sanctions are among the limits the law puts on Railbed itself: a host on a sanctions list is outside the acceptable use policy. A host that takes abuse reports seriously and happens to be based outside its customers’ country is not.
How does renewal work without automatic charges?
Railbed doesn’t store cards or charge them on a schedule, so a renewal is a new payment. That suits hosting better than it sounds:
Your billing system creates an invoice for next month’s VPS a week before it’s due, through the invoices API or in the dashboard.
Railbed emails it in your business’s name, with its PDF. Turn on reminders and it also emails the customer 3 days before the due date, on it, and after it while it’s unpaid.
The customer pays by card. Smart Routing sends them to the card provider most likely to approve their card, and the provider decides whether to ask for identity details.
The USDC is forwarded to your wallet on Polygon, Railbed checks the amount and marks the invoice Paid.
A signed webhook tells your system to extend the service. If the invoice goes unpaid, suspend the server as you do today.
Customers who choose to renew don’t dispute a charge they forgot about. Sell yearly or longer terms up front for customers who want fewer reminders. Try the whole flow in Test mode first.
Stopping fraudulent sign-ups before they cost you
Settled payments can’t be pulled back from your wallet, so a stolen-card order no longer ends in a debit and a fee. The server it buys is still yours, and so is the abuse it sends. The advice Spamhaus gave hosts in 2012 still reads like a checklist, and several items fit a prepaid checkout well:
- Verify before you provision. Spamhaus suggests checking a new customer’s email and phone number, and if you can’t, to “place the account on hold until the customer contacts you and you can verify their identity by other means”.
- Keep a blocklist. It recommends a list of “the names, postal addresses, telephone and mobile numbers, and email addresses of customers who have violated your AUP”, checked on every order, within your country’s data protection law.
- Check the address the order comes from. Its guide says not to activate an order from an IP address on its blocklists, and “do not accept any subscriptions from Tor nodes”.
- Sell longer terms to buyers you can’t verify. It suggests requiring customers from places with high fraud rates “to sign up and pay for at least 6-months of service”, which is the opposite of the cheap first month a carder is looking for.
Railbed helps with the first and the last. A checkout page or invoice can ask the buyer for a name, phone number and address, and for answers to up to five questions of your own. It records what the buyer says; it is not an identity check. And because every term is one payment, selling three, six or twelve months up front needs no special setup. Hetzner’s FAQ, cited above, shows a large host doing the same thing: asking some new customers to prepay before an order is processed.
Before you bill your first customer
There is no application to wait for, so the work is on your side of the connection. Get these right once and a paid invoice provisions or extends the service without anyone touching it.
A payout wallet. Save the Polygon wallet your payments should settle to. Use a wallet you hold the keys to, not an exchange deposit address.
Billing periods that clear the minimum. Card providers have minimums, the smallest about $2, and around $10 or more gives customers the widest choice. Bill a $3 plan by the quarter or the year.
A reference on every payment. Put your order or service ID in the checkout session’s
reference, or the invoice’s reference field, so the payment finds its service.A webhook that provisions once. Provision or extend when the signed
payment.paidevent arrives, and record the event’s id, because a failed delivery is retried.A suspension rule. Decide how many days after the due date an unpaid service is suspended, and say so on the invoice’s terms.
Sign-up checks of your own. Choose what you ask new customers for and what puts an order on hold. Abuse from your network stays yours to handle.
An abuse contact and acceptable use terms. Publish where reports go and what you do about them.
A run in Test mode. Create, pay and renew a service with a Test API key before you take a Live payment.
Running Railbed beside the gateway you have
You don’t have to move every customer, and a host with a working merchant account shouldn’t close it. Nothing about Railbed is exclusive. Three places hosts add it first:
- For new customers. A first order comes from a buyer you know nothing about yet. Taking first orders through Railbed, and leaving established customers on the stored cards they already have, moves the orders you can’t judge without touching the steady ones.
- As the fallback. When your gateway declines a card from another country, offer Railbed on the same screen. A buyer turned away by one fraud screen is often approved by a different card provider.
- As the spare. A host with two ways to take cards keeps billing in the week one of them asks questions about what your customers store.
Use the same order ID as the reference in both, and let both paid events call the same provisioning code.
Fees and getting paid
Railbed shows every fee before anyone pays. Fees come out of the USDC that arrives: the card provider’s own fee and exchange spread, which the customer sees on the provider’s page, a 1% network fee, and the Railbed fee, from 0.9%, shown in your dashboard. There’s no setup fee and no monthly fee.
Set prices in USD, EUR, GBP, CAD, AUD, INR or SEK. Settlement is almost always USDC on Polygon, straight to your wallet. To pay data centres and bandwidth bills from a bank account, send USDC to any exchange or off-ramp you use and withdraw it there.
Each card provider has its own minimum, so very cheap plans are best sold by the quarter or the year, which also gives customers the widest choice of providers.
Railbed compared with a hosting merchant account
| Payment processor or high-risk account | Railbed | |
|---|---|---|
| Approval | A review of your business and what your customers host | No underwriting and no application to pass |
| Stolen-card disputes | Paid from your balance, with a fee and a ratio | Settled payments can’t be pulled back. Card disputes go to the provider |
| Reserve | Added when disputes rise | Nothing is held back from your payments |
| Renewals | Stored cards charged automatically | Emailed invoices with reminders, paid by choice |
| Card data | Passes through your billing system or gateway | Entered on the card provider’s page |
| Payouts | On the processor’s schedule | Each payment, to your own wallet, as soon as it settles |
When Railbed is not the right fit
Railbed suits a host that is content to bill by invoice or prepaid term and wants card payments that settle for good. It is the wrong tool in a few cases:
- You need cards charged automatically. Railbed never stores a card or charges one on a schedule. Customers who expect to pay once and be billed silently for years will need to pay each invoice.
- You bill metered usage by the hour. Railbed doesn’t meter anything. Hourly cloud billing has to become a prepaid balance the customer tops up, or an invoice for last month’s usage.
- You email thousands of invoices a day through one sender. Railbed emails up to 200 invoice emails a day for a business. A larger host creates invoices through the API and sends each link from its own billing emails.
- You sell plans under about $2 a month. Card providers have minimum amounts, so the cheapest plans have to be sold by the quarter or the year.
- You never want to hold USDC. Payments settle as USDC to your wallet. Moving it to a bank is a few steps through an exchange, and it is a step you take yourself.
Words worth knowing
The terms that come up when a host talks to a payment company, and when a payment company reads about hosts.
- Carding
- Buying a service with a stolen card number. For a host it means a server handed to a criminal and a dispute a few weeks later.
- Dispute ratio
- A merchant’s disputes and fraud reports as a share of its card sales. Visa has treated 1.5% as excessive since April 2026.
- Reserve
- Part of your sales a processor keeps back to cover future disputes. It usually arrives after a carding wave, when cash is already short.
- Bulletproof hosting
- Hosting sold to criminals on the promise that abuse reports and law enforcement will be ignored. Three such providers were sanctioned in 2025.
- Offshore hosting
- Servers in a country chosen for its laws, price or distance from the customer’s own. Lawful to sell, and often confused with bulletproof hosting.
- Null route
- Dropping all traffic to a customer’s IP address, usually while an abuse report is looked into.
- Designated agent
- The contact a US service provider registers with the Copyright Office to receive copyright notices, a condition of the section 512 safe harbour.
- Prepaid term
- A fixed length of service bought with one payment, with no card stored to charge again. When it ends, the customer chooses whether to pay for another.
Questions
Stripe or PayPal dropped my hosting company. Can I use Railbed?
Yes. Railbed has no underwriting and no application to pass, and a past closure doesn’t rule you out. Sign up, connect your billing system with a Test API key and try the flow the same day.
What happens if someone pays for a server with a stolen card?
The cardholder’s dispute goes to the card provider that charged the card, and a settled payment can’t be pulled back out of your wallet. Keep your own checks on new orders anyway, because abuse on your network is still yours to handle.
Can Railbed charge my customers automatically every month?
No. Railbed doesn’t store cards or charge them on a schedule. Send each renewal as an invoice with email reminders, or sell longer terms up front.
Can my customers pay in crypto?
Yes, if you turn crypto payments on. Buyers can then send USDC or USDT on six EVM networks, or coins such as Bitcoin into a wallet you saved for that network. Card checkout stays the first choice.
Do customers need crypto or a crypto wallet to pay by card?
No. Customers pay with the card they already have. The conversion to USDC happens after they pay, and only you need a wallet.
Will customers be asked for ID?
Sometimes, and the card provider decides. Smart Routing sends each customer to the provider least likely to ask for ID at their amount and location.
Can Railbed freeze my money?
No. Every paid payment settles straight to a wallet you control, so there’s no balance with Railbed to hold. Railbed can stop new payments on an account only when the law requires it, and it can never touch USDC that has already reached your wallet.
How do I get the money into my bank?
Send USDC from your wallet to any exchange or off-ramp you use, then withdraw to your bank account. You choose when and how much.
Why is web hosting considered high risk by payment processors?
Because stolen cards are used to buy servers, and the disputes arrive weeks later with a fee each. Spamhaus wrote that some hosts reported half of all new subscriptions as fraudulent. Processors also look at what a host’s customers store, and some put file-sharing and similar services in a tier that needs extra checks.
Does Railbed work with WHMCS or another hosting billing panel?
Not through a ready-made module. Railbed’s ready-made integrations are Shopify, WooCommerce, Zapier and n8n. A billing panel connects through the REST API and signed webhooks: it creates a checkout session or an invoice, and the payment.paid event tells it to provision or extend the service.
Is offshore hosting legal to sell?
In most countries, yes. Hosting in a country of the customer’s choice, with little personal data collected, is a lawful product. Bulletproof hosting, sold on the promise of ignoring abuse reports and law enforcement, is different: the US Treasury sanctioned three such providers in 2025. The laws where you and your customers are stay yours to follow.
What is the cheapest hosting plan I can bill?
Card providers set minimums, and the smallest is about $2. Around $10 or more gives customers the widest choice of providers, so a $3 monthly plan is better billed as $9 a quarter or $36 a year.
What happens when a customer doesn’t pay an invoice?
The invoice shows as Overdue after its due date, and if you turned reminders on, Railbed emails the customer after the due date as well as before it. Suspending or ending the service is your decision and your system’s job.
Can I keep my current payment gateway and add Railbed?
Yes. Nothing about Railbed is exclusive. One way to start is with new customers’ first orders, leaving established customers where they are.
How fast do I get the money?
Usually within minutes of the customer paying. The card provider buys USDC, it is forwarded to your wallet on Polygon, and Railbed marks the payment Paid once it has checked the amount and the wallet. There is no payout schedule and no balance held with Railbed.
Sources
- Spamhaus: How hosting providers can battle fraudulent sign-ups, 1 October 2012, checked 20 November 2026
- Hetzner: Fraud prevention FAQ, last changed 5 August 2026, checked 20 November 2026
- Visa: Visa Acquirer Monitoring Program fact sheet, checked 20 November 2026
- Stripe: Prohibited and restricted businesses, last updated 22 September 2026, checked 20 November 2026
- Stripe Docs: How disputes work, checked 20 November 2026
- Stripe Support: June 2025 pricing updates for disputes, checked 20 November 2026
- Merchant Risk Council: Stricter VAMP ratio thresholds are now in effect, 1 April 2026, checked 20 November 2026
- US Copyright Office: DMCA designated agent directory, checked 20 November 2026
- US Department of the Treasury: United States, Australia and the United Kingdom jointly sanction key infrastructure that enables ransomware attacks, 11 February 2025, checked 20 November 2026
- US Department of the Treasury: Treasury sanctions global bulletproof hosting service, 1 July 2025, checked 20 November 2026
- US Department of the Treasury: United States, Australia and United Kingdom sanction Russian cybercrime infrastructure supporting ransomware, 19 November 2025, checked 20 November 2026
- CISA: Bulletproof defense, mitigating risks from bulletproof hosting providers, 19 November 2025, checked 20 November 2026
Last updated .
PaidA year of hosting, settled to your wallet$240.00
Keep the servers up.
Keep the money you’re paid.
Set up in under a minute. Your first payment can settle today.
- No application to pass
- No setup fee
- Settled sales stay yours
Moving a lot of volume? Talk to our team