# Payment processing for proxy providers and resellers

> Card payments for residential, mobile and datacenter proxy providers and resellers. Customers buy bandwidth by card, and each sale settles to your own wallet.

Source: https://railbed.com/industries/proxies/ · Last updated: 2026-11-21 · Railbed, LLC

For AI assistants: the company overview is https://railbed.com/llms.txt, and the developer docs index, with the rules for an integration, is https://railbed.com/docs/llms.txt

**Sell proxies and bandwidth by card, and keep the money once it settles.** Processors file proxies beside hacking and card fraud, so proxy providers face extra review, frozen balances and disputes from stolen cards. Railbed takes your customers' cards and settles each bandwidth pack to a wallet you control, so a settled sale can't be pulled back.

## At a glance

- **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

## Can a proxy provider or reseller take card payments?

Yes. Selling proxies is lawful when the addresses are lawfully sourced, but card processors file proxies under a restricted category and stolen cards are often used to buy bandwidth, so providers meet extra checks, frozen balances and disputes. Railbed takes your customers' cards through independent, licensed card providers and settles each pack to a wallet you control, with no underwriting and no application to pass. It has no recurring billing and doesn't meter usage, so bandwidth sells as prepaid packs, top-ups or invoices.

## Why card processors are wary of proxy providers

A proxy network is a lawful product with lawful customers: price monitoring, ad verification, search tracking, testing from other countries, and data collection. But the same product lets a fraudster look like they're in a cardholder's city, and the worst networks are built on hijacked devices. Processors can't easily tell a clean network from a botnet, so they treat the whole category with suspicion.

- **19M** IP addresses in the 911 S5 botnet the US dismantled in 2024, sold as a "residential proxy service" ([US Department of Justice](https://www.justice.gov/archives/opa/pr/911-s5-botnet-dismantled-and-its-administrator-arrested-coordinated-international-operation))
- **550+** Threat groups Google saw using one proxy network's exit nodes in a single week of January 2026 ([Google](https://cloud.google.com/blog/topics/threat-intelligence/disrupting-largest-residential-proxy-network))
- **2M+** Hijacked consumer devices Google says it protected when it disrupted another network in July 2026 ([Google](https://cloud.google.com/blog/topics/threat-intelligence/google-continued-disruption-residential-proxy-networks))

Paddle's [list of what it won't sell](https://www.paddle.com/help/start/intro-to-paddle/what-am-i-not-allowed-to-sell-on-paddle) names "VPN and Proxies (Restricted Category)", explaining that "Paddle must do enhanced due diligence on certain product offerings". Restricted means a review before you sell and a reason to look again whenever your disputes climb.

The enforcement news explains the suspicion. What an underwriter has read about:

- **911 S5.** The US Department of Justice [took it down in 2024](https://www.justice.gov/archives/opa/pr/911-s5-botnet-dismantled-and-its-administrator-arrested-coordinated-international-operation): a botnet with "more than 19 million unique IP addresses" that its operator ran as a residential proxy service.
- **SocksEscort.** In March 2026 the Justice Department [disrupted it](https://www.justice.gov/usao-edca/pr/authorities-dismantle-global-malicious-proxy-service-deployed-malware-and-defrauded) after it had sold about 369,000 IP addresses from infected routers.
- **Sourcing claims.** Google, describing the takedown of one of the largest residential networks, wrote that "While many residential proxy providers state that they source their IP addresses ethically, our analysis shows these claims are often incorrect or overstated."

## The dispute problem: stolen cards buy proxies

The people who want an IP address in a cardholder's city include card thieves. The FBI's [March 2026 alert](https://www.fbi.gov/investigate/cyber/alerts/2026/evading-residential-proxy-networks-protecting-your-devices-from-becoming-a-tool-for-criminals) lists "Making illegal purchases" and "Account takeovers" among the uses criminals make of residential proxies. A thief who buys your bandwidth with a stolen card leaves you the dispute when the real cardholder sees the charge.

That gives proxy providers a dispute pattern of their own:

- **Stolen cards.** A bandwidth pack bought with someone else's card is disputed weeks later, after the gigabytes are spent.
- **Card testing.** Small packs and free trials attract people checking whether stolen cards still work.
- **Usage disputes.** A customer burns through a pack in a day, then says they never got it.

No industry body publishes a dispute rate for proxies, and this page doesn't invent one. What's certain is that each dispute costs a fee, the bandwidth can't be returned, and enough of them can close a merchant account.

The published figures show how little room there is. Take one $30 residential pack bought with a stolen card:

| What it costs at a conventional processor | Published figure | Where it's published |
|---|---|---|
| The sale, debited back from your balance | $30 | Your own price list |
| The fee for receiving the dispute, in the United States | $15, not refunded | [Stripe](https://docs.stripe.com/disputes/how-disputes-work) |
| The fee for contesting it, returned only if you win | $15 | [Stripe](https://support.stripe.com/questions/june-2025-pricing-updates-for-disputes) |
| The fee once a merchant is in Visa's monitoring programme | $8 for each fraudulent or disputed transaction | [Merchant Risk Council](https://merchantriskcouncil.org/learning/resource-center/member-news/blog/2026/stricter-vamp-ratio-thresholds-are-now-in-effect-heres-how-to-stay-compliant) |
| The bandwidth | Already used, and already paid to your exit-node partners | Your supplier's invoice |

Visa's [monitoring programme](https://corporate.visa.com/content/dam/VCOM/corporate/visa-perspectives/security-and-trust/documents/visa-acquirer-monitoring-program-fact-sheet-2025.pdf) counts a merchant as excessive at a ratio of 1.5% with 1,500 or more fraud reports and disputes in a month, and it has a separate test for card testing, which it calls enumeration: 300,000 or more enumerated authorisation attempts making up 20% or more of the total. A small provider won't reach those counts. Its processor is measured too, though: an acquirer's whole portfolio counts as "above standard" at 0.5%, a line Visa began enforcing on 1 January 2026, and as "excessive" at 0.7%. That is why a processor acts on a merchant long before Visa would.

## Proxy networks in the news, 2024 to 2026

An underwriter reading about your industry sees two stories at once. Courts have said that collecting public data through a proxy network can be lawful business, and governments have spent three years taking down proxy services built on hijacked devices. Both are on the record, with dates.

- **Jan 2024:** A US federal judge rules that Bright Data did not break Meta's terms by scraping public Facebook and Instagram data while logged out. ([Courthouse News](https://www.courthousenews.com/federal-judge-rules-against-meta-in-data-scraping-case/))
- **May 2024:** The US Treasury sanctions three people tied to 911 S5, a residential proxy service built on about 19 million compromised IP addresses. ([US Treasury](https://home.treasury.gov/news/press-releases/jy2375))
- **May 2025:** US prosecutors charge four people over Anyproxy and 5socks, which sold access to infected routers for $9.95 to $110 a month. ([US Department of Justice](https://www.justice.gov/usao-ndok/pr/botnet-dismantled-international-operation-russian-and-kazakhstani-administrators))
- **Jan 2026:** Google disrupts IPIDEA, which it calls one of the largest residential proxy networks, after seeing more than 550 threat groups use it in a week. ([Google](https://cloud.google.com/blog/topics/threat-intelligence/disrupting-largest-residential-proxy-network))
- **Mar 2026:** The Justice Department disrupts SocksEscort, and the FBI publishes an alert on residential proxy networks. ([FBI](https://www.fbi.gov/investigate/cyber/alerts/2026/evading-residential-proxy-networks-protecting-your-devices-from-becoming-a-tool-for-criminals))
- **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%. ([Merchant Risk Council](https://merchantriskcouncil.org/learning/resource-center/member-news/blog/2026/stricter-vamp-ratio-thresholds-are-now-in-effect-heres-how-to-stay-compliant))
- **Jul 2026:** Google disrupts a second residential proxy network and says it protected more than two million hijacked consumer devices. ([Google](https://cloud.google.com/blog/topics/threat-intelligence/google-continued-disruption-residential-proxy-networks))

The detail in those cases is what colours a processor's view. The 5socks website carried the slogan "Working since 2004!" and prosecutors believe its operators "amassed more than $46 million" from infected routers. The Treasury said 911 S5 was used to file "tens of thousands of fraudulent applications" for pandemic relief. A lawful provider is asked to prove it is nothing like them, by people who can't see inside its network.

## How Railbed fixes it

Railbed is card checkout that never holds your money. Customers pay with the card they already have, and each pack settles as USDC straight to a wallet you control, usually minutes after they pay. You add the bandwidth once the payment shows Paid, and a settled payment can't be pulled back out of your wallet by a dispute later.

| What goes wrong today | With Railbed |
|---|---|
| Your category needs enhanced review before you can sell | No underwriting and no application to pass. Railbed adds no restrictions of its own beyond what the law requires |
| A stolen-card dispute arrives after the bandwidth is spent | Settled sales can't be pulled back from your wallet. Disputes go to the card provider that charged the card |
| A run of disputes freezes your balance | Each sale settles to your own wallet, so nothing is held back from your sales |
| One acquiring bank decides which customers' cards work | Smart Routing sends each customer to the card provider most likely to approve them |
| Customers abroad can't pay in their own currency | Price in USD, EUR, GBP, CAD, AUD, INR or SEK |

An independent, licensed card provider charges the customer's card and buys USDC with it, and the USDC is forwarded to the Polygon wallet you saved in Railbed. Railbed checks that the right amount reached the right wallet before it marks the payment Paid. The card provider runs its own fraud checks before it charges the card, and if a customer disputes the payment later, the dispute is between their bank and that provider, and nothing comes out of your wallet.

## What you can sell with Railbed

Railbed is built for proxy networks sourced lawfully: datacenter and ISP addresses you lease, and residential or mobile exit nodes whose owners agreed to share their connection. Selling access to devices taken over by malware is computer crime, and no payment company can make it lawful.

- **Residential and mobile bandwidth.** Packs of gigabytes sold from a [pricing table](https://railbed.com/docs/user-guide/pricing-tables/), or from your own dashboard through a checkout session created with the [REST API](https://railbed.com/docs/quickstart/). Your server adds the gigabytes when the signed `payment.paid` webhook arrives.
- **Datacenter and ISP proxies.** Batches of dedicated or shared IPs for a fixed period, sold as one payment for 30, 90 or 365 days.
- **Top-ups.** A customer who runs low buys more from inside your dashboard, and your server credits it once per event ID.
- **Scraping and unblocking APIs.** Request credits for a scraping or browser API, priced per thousand requests.
- **Reseller and enterprise orders.** A reseller's monthly bulk order or a company's yearly commitment sent as an [invoice](https://railbed.com/docs/user-guide/invoices/), up to 100,000 in USD or another supported currency, with part payments if they want them.

## Which checkout fits each kind of proxy

Proxies are priced in three ways, by the gigabyte, by the address and by the request, and each one maps to a different way of selling with Railbed. Most providers use two: one inside the customer dashboard, and one for the buyer who wants a bill.

| What you sell | How it's usually priced | What to use |
|---|---|---|
| Rotating residential and mobile proxies | By the gigabyte, in prepaid packs | A checkout session for each pack, created from your dashboard with the [REST API](https://railbed.com/docs/quickstart/), or a [pricing table](https://railbed.com/docs/user-guide/pricing-tables/) for up to four fixed packs |
| Datacenter and ISP proxies | By the address, for a fixed period | A pricing table with 30, 90 and 365-day terms, or a checkout session when the customer chooses the number of addresses |
| Scraping and unblocking APIs | By the thousand requests | Prepaid request credits bought through a checkout session, credited by your webhook handler |
| Reseller balances | A top-up of any size | A checkout session with the reseller's account ID as the reference |
| Enterprise commitments | A monthly or yearly contract | An [invoice](https://railbed.com/docs/user-guide/invoices/) with lines, tax and a due date, paid in full or in parts |

A pricing table needs no code and can be embedded in your site the same day. A checkout session takes one API call and one webhook handler, and it is the one to build if customers top up from inside their dashboard, because the payment carries your own reference back to you.

## How a bandwidth purchase works

1. A customer picks a pack in your dashboard. Your server asks Railbed for a checkout session with the price and the customer's account ID as the reference.
2. The checkout opens and the customer enters an email address. Smart Routing sends them to the card provider most likely to approve their card at that amount.
3. The customer pays on the provider's page. The provider decides whether to ask for identity details, and larger purchases are more likely to need them.
4. The provider buys USDC with the card payment, and it's forwarded to your wallet on Polygon. Railbed checks the amount and the wallet before it marks the payment Paid.
5. Railbed sends a signed `payment.paid` webhook. Your server credits the bandwidth once per event ID, and the customer's credentials start working.

Build and test it in [Test mode](https://railbed.com/docs/user-guide/test-and-live/), where payments are simulated and no card is charged. The [fulfilment guide](https://railbed.com/docs/guides/fulfilment/) shows the checks to make before you credit an account.

## Keeping fraud off your network

Railbed settles your sales; it doesn't police your customers. The checks that keep stolen cards and abusers off your network stay with you, and they protect your exit-node partners as much as your revenue:

- **Ask for what you need.** [Checkout questions](https://railbed.com/docs/user-guide/checkout-pages/#ask-buyers-for-their-details) can ask for a name, company or intended use before payment.
- **Hold back the risky targets.** Block banking, payment and government domains by default, and open them only for customers you know.
- **Watch the first day.** A new account that spends a large pack in hours, or rotates through a single bank's login pages, is worth a look before its next top-up.
- **Price trials with care.** A paid starter pack at a few dollars puts off card testers better than a free trial.

## Showing where your addresses come from

The question every bank, partner and enterprise buyer asks a residential provider is how the addresses were obtained. Google's [January 2026 report](https://cloud.google.com/blog/topics/threat-intelligence/disrupting-largest-residential-proxy-network) explains why: once a proxy SDK is embedded in an app, "it will turn the device it is running on into an exit node for the proxy network", and it concluded that any claim of ethical sourcing "must be backed by transparent, auditable proof of user consent".

The industry's own body says the same in fewer words. The [Ethical Web Data Collection Initiative](https://ethicalwebdata.com/ewdci-our-principles/), an industry-led consortium of web data collectors, publishes two principles that bear on a provider's checkout. On sourcing: "We commit to sourcing proxies ethically, with informed consent and in compliance with data protection standards." On customers: "We apply Know Your Customer (KYC) practices, especially when high-risk tools like residential IPs are involved, to ensure services are used ethically and by legitimate organizations."

Railbed has no underwriting and no application to pass, so none of this is asked of you at sign-up. It is still worth having in writing, because your exit-node partners, your larger customers and any court will ask for it:

- **A sourcing statement.** Which apps, SDK partners or ISPs your addresses come from, and how the device owner agreed.
- **A way out for device owners.** How someone finds out their connection is shared, and how they stop it.
- **A customer policy.** Who you verify, at what spend, and which targets stay blocked until you have.
- **An abuse contact that answers.** A named address for complaints about traffic from your network, and a record of what you did about each one.

## Refunds for unused bandwidth

A pack that doesn't unblock a customer's target is worth nothing to them, so refund requests are part of selling proxies. A paid pack has already settled to your wallet, so a refund is something you send, not something a processor takes. Railbed can't reverse a settled payment.

Decide the rule before the first request arrives. You might refund unused gigabytes within a set number of days, or offer account credit instead of money. Whatever you choose, state it beside the price, and answer quickly: a customer who can get unused bandwidth refunded by you has little reason to go to their bank. A dispute, if it comes, goes to the card provider that charged the card, under its terms and the card networks' rules.

## Running Railbed beside the checkout you have

Nothing about Railbed is exclusive, and a provider that already has a merchant account shouldn't close it. The usual first step is to add Railbed as a second way to pay by card and see how it performs. Three places it earns its keep:

- **As the fallback.** When your main checkout declines a card, offer Railbed on the same screen instead of losing the sale. A buyer turned away by one fraud screen is often approved by a different card provider.
- **For the products your processor won't take.** If your processor accepts datacenter proxies but not residential or mobile ones, send those orders to a Railbed checkout and leave the rest where they are.
- **As the spare.** A provider with two working checkouts keeps selling in the week a takedown makes the news and its category is looked at again.

Use the same account ID as the reference in both, and let both checkouts' paid events call the same code that credits bandwidth.

## Fees and getting paid

Every fee is shown 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.

About $2 is the smallest card payment Railbed accepts, and around $10 gives customers the widest choice of card providers, because each provider has its own minimum. Sales settle almost always as USDC on Polygon to your own [payout wallet](https://railbed.com/docs/user-guide/wallet-and-settlement/). Pay exit-node partners and IP suppliers in USDC where they take it, or [move money to your bank](https://railbed.com/docs/user-guide/move-money-to-your-bank/) through an exchange.

Railbed doesn't run automatic recurring billing, and it doesn't meter usage. Each pack, period or top-up is one payment. Refunds are your call: Railbed can't reverse a settled payment, so if you refund unused bandwidth, send USDC back or credit the account.

## Railbed compared with a gateway that hides your business

Some high-risk gateways promise to keep what you sell from the banks, or to absorb every chargeback. Railbed does neither, and that's deliberate.

| | Gateway that disguises the business | Railbed |
|---|---|---|
| What the bank sees | A claim that your business will be hidden from acquiring banks, which card networks call transaction laundering | Nothing is disguised. A licensed card provider charges the card for a USDC purchase sent to your wallet |
| Chargebacks | A promise to absorb them all | Settled sales can't be pulled back from your wallet. Disputes go to the card provider that charged the card |
| Your money | Depends on the gateway | Each sale settles to your own wallet, and Railbed never holds it |

## Is selling proxies legal?

Yes, in most countries, when the addresses are lawfully obtained. The FBI [puts the line simply](https://www.fbi.gov/investigate/cyber/alerts/2026/evading-residential-proxy-networks-protecting-your-devices-from-becoming-a-tool-for-criminals): residential IP addresses come from devices whose owner "provides consent", or from devices whose owner "does not provide consent and is unaware their IP address is being used". The second is how botnets like 911 S5 and SocksEscort were built, and their operators were arrested or their networks seized.

Collecting public web data, the main lawful use of a proxy network, has been tested in court. In January 2024 a US federal judge [ruled for Bright Data](https://www.courthousenews.com/federal-judge-rules-against-meta-in-data-scraping-case/), a proxy and data company, in a contract case brought by Meta, writing that "the Facebook and Instagram terms support the interpretation that the terms only prohibit logged-in scraping, and not logged-off scraping". That decision turned on one company's terms and on data anyone could see without an account. It doesn't make every kind of scraping lawful, and it says nothing about personal data rules or other countries.

What your customers do through your network is governed by the laws where they are and by your own terms. Railbed's [acceptable use policy](https://railbed.com/acceptable-use/) holds only the limits the law puts on Railbed itself, such as money laundering and sanctions, and the laws where you, your partners and your customers are stay yours to follow.

## When Railbed is not the right fit

Railbed suits a provider that sells bandwidth, addresses or requests in prepaid blocks and wants card payments without a category decision hanging over it. It is the wrong tool in a few cases:

- **You bill usage after the fact.** Railbed doesn't meter bandwidth or charge a stored card. Pay-as-you-go has to become prepaid top-ups, or a monthly invoice for customers you trust.
- **You need automatic monthly renewals.** Railbed has no recurring billing. A 30-day batch of dedicated addresses is renewed by a new payment, which you can prompt with an invoice and its reminders.
- **Your network isn't lawfully sourced.** No payment company can make access to hijacked devices lawful, and Railbed stops new payments on an account when the law requires it.
- **You sell packs under about $2.** Card providers have minimum amounts, so a trial pack needs to cost a few dollars.
- **You never want to hold USDC.** Sales 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 a proxy provider and a payment company use past each other.

- **Residential proxy:** An address that belongs to a home internet connection, lent by a device whose owner agreed to share it. Usually sold by the gigabyte.
- **Mobile proxy:** An address on a mobile carrier's network, shared by many phones at once. Usually sold by the gigabyte or by the port.
- **ISP proxy:** A static address registered to an internet provider but hosted in a data centre, also called static residential. Sold by the address, for a period.
- **Datacenter proxy:** An address leased from a hosting company. Usually the cheapest kind, and the easiest for a website to recognise.
- **Exit node:** The device or server a customer's traffic leaves from. On a residential network it is someone's phone, computer or router.
- **Sticky session:** A setting that keeps a customer on one address for minutes or hours, where a rotating session changes address with every request.
- **Know your customer:** The checks a provider runs on a buyer before opening risky features: who they are, what they collect and why. Often shortened to KYC.
- **Card testing:** Running stolen card numbers through small purchases to find the ones that work. Visa calls it enumeration and monitors it separately from disputes.
- **Restricted category:** A kind of business a processor accepts only after extra checks. Paddle lists "VPN and Proxies" this way.
- **Transaction laundering:** Putting card sales through a merchant account opened for a different business. It is what a gateway that hides what you sell is offering.

## Questions

### Paddle or another processor refused my proxy business. Can I use Railbed?

Yes. A past refusal doesn't rule you out, and there's no processing history to send. Sign up with an email, your website and a payout wallet and take your first card payment today.

### What happens when a customer pays with a stolen card?

The card provider runs its own fraud checks before it charges the card. If the real cardholder disputes the payment later, the dispute goes to that provider, under its rules and the card networks'. A settled payment can't be pulled back out of your wallet. Under its own terms, the provider may decline future payments from that buyer.

### Can I bill customers for the bandwidth they use?

Not automatically. Railbed takes one payment at a time, so sell prepaid packs and top-ups, or send an invoice at the end of each month for what an enterprise customer used.

### Can residential and mobile proxy networks use Railbed?

Yes. Railbed adds no restrictions of its own, so the law draws the line: exit nodes whose owners agreed to share their connection are lawful, and devices taken over without consent are computer crime. Railbed stops new payments on an account when a court or law enforcement requires it.

### 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, so smaller packs often need little or no check.

### Do customers need crypto or a crypto wallet?

No. Customers pay with the card they already have, and some can use Apple Pay or Google Pay through the card providers that offer them. Only you need a wallet. You can also turn on [crypto payments](https://railbed.com/docs/user-guide/crypto-payments/) for customers who prefer to pay in stablecoins.

### Can Railbed freeze my money?

No. Every paid sale settles straight to a wallet you control, so there's no balance with Railbed to freeze. Railbed can stop new payments on an account only when the law requires it, and it can never touch USDC already in your wallet.

### How do I get the money into my bank?

Send USDC from your wallet to an exchange or off-ramp you use, sell it for your currency and withdraw to your bank, whenever you choose. The [guide](https://railbed.com/docs/user-guide/move-money-to-your-bank/) shows each step.

### Why do payment processors restrict proxy providers?

Because the product can be used to commit fraud, and because the worst networks were built on hijacked devices. Paddle files "VPN and Proxies" under a restricted category, and US authorities have taken down proxy services such as 911 S5, Anyproxy and SocksEscort since 2024. A processor can't easily tell a clean network from those, so it treats the category with caution.

### Is web scraping through proxies legal?

It depends on what is collected, from where and how. In January 2024 a US federal judge ruled that Bright Data did not break Meta's terms by scraping public Facebook and Instagram data while logged out. Scraping behind a login, collecting personal data and the law in other countries are different questions, and they are yours and your customers' to answer.

### Do I have to verify my customers' identity?

Railbed doesn't ask you to, and the card provider makes its own decision about each buyer. The proxy industry's own body, the Ethical Web Data Collection Initiative, commits its members to know-your-customer checks "especially when high-risk tools like residential IPs are involved". Your policy is yours to set and to keep.

### What is the smallest pack I can sell?

About $2 is the smallest card payment, and around $10 or more gives customers the widest choice of card providers. A paid starter pack of a few dollars works better than a free trial, which attracts card testers.

### Can a customer get a refund for bandwidth they didn't use?

That's your decision. Railbed can't reverse a settled payment, so a refund is USDC you send back, or credit you add to the account. State the rule beside your prices.

### Can I keep my current processor and add Railbed?

Yes. Nothing about Railbed is exclusive. Add it as a second way to pay by card, or use it only for the products your processor won't take, such as residential and mobile bandwidth.

### 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

1. [US Department of Justice: 911 S5 botnet dismantled and its administrator arrested](https://www.justice.gov/archives/opa/pr/911-s5-botnet-dismantled-and-its-administrator-arrested-coordinated-international-operation), May 2024
2. [Google Threat Intelligence: Disrupting the largest residential proxy network](https://cloud.google.com/blog/topics/threat-intelligence/disrupting-largest-residential-proxy-network), January 2026
3. [Google Threat Intelligence: Continued disruption of malicious residential proxy networks](https://cloud.google.com/blog/topics/threat-intelligence/google-continued-disruption-residential-proxy-networks), 2 July 2026
4. [US Attorney's Office, Eastern District of California: Authorities dismantle a global malicious proxy service](https://www.justice.gov/usao-edca/pr/authorities-dismantle-global-malicious-proxy-service-deployed-malware-and-defrauded), 12 March 2026
5. [FBI: Evading residential proxy networks](https://www.fbi.gov/investigate/cyber/alerts/2026/evading-residential-proxy-networks-protecting-your-devices-from-becoming-a-tool-for-criminals), 12 March 2026
6. [Paddle: What am I not allowed to sell on Paddle?](https://www.paddle.com/help/start/intro-to-paddle/what-am-i-not-allowed-to-sell-on-paddle), last updated 13 April 2026, checked 20 November 2026
7. [Courthouse News Service: Federal judge rules against Meta in data scraping case](https://www.courthousenews.com/federal-judge-rules-against-meta-in-data-scraping-case/), 23 January 2024, checked 20 November 2026
8. [US Department of the Treasury: Treasury sanctions a cybercrime network associated with the 911 S5 botnet](https://home.treasury.gov/news/press-releases/jy2375), 28 May 2024, checked 20 November 2026
9. [US Attorney's Office, Northern District of Oklahoma: Botnet dismantled in international operation](https://www.justice.gov/usao-ndok/pr/botnet-dismantled-international-operation-russian-and-kazakhstani-administrators), 9 May 2025, checked 20 November 2026
10. [Ethical Web Data Collection Initiative: Our principles](https://ethicalwebdata.com/ewdci-our-principles/), last changed 20 July 2026, checked 20 November 2026
11. [Visa: Visa Acquirer Monitoring Program fact sheet](https://corporate.visa.com/content/dam/VCOM/corporate/visa-perspectives/security-and-trust/documents/visa-acquirer-monitoring-program-fact-sheet-2025.pdf), checked 20 November 2026
12. [Merchant Risk Council: Stricter VAMP ratio thresholds are now in effect](https://merchantriskcouncil.org/learning/resource-center/member-news/blog/2026/stricter-vamp-ratio-thresholds-are-now-in-effect-heres-how-to-stay-compliant), 1 April 2026, checked 20 November 2026
13. [Stripe Docs: How disputes work](https://docs.stripe.com/disputes/how-disputes-work), checked 20 November 2026
14. [Stripe Support: June 2025 pricing updates for disputes](https://support.stripe.com/questions/june-2025-pricing-updates-for-disputes), checked 20 November 2026

## Other businesses we serve

- [VPNs & privacy apps](https://railbed.com/industries/vpn.md): VPN plans and privacy apps, paid by card and settled to your own wallet.
- [Web hosting & VPS](https://railbed.com/industries/web-hosting.md): Bill hosting, VPS and server plans by card without carrying your customers’ stolen-card disputes.
- [Digital goods & game top-ups](https://railbed.com/industries/digital-goods.md): Keys, credits and in-game currency, with sales that stay yours after the code goes out.

## About Railbed

Railbed is card checkout for online businesses that mainstream processors turn away, with no underwriting and no application to pass. Buyers pay by card through independent, licensed card providers, and sales settle to a wallet the merchant controls, almost always as USDC on Polygon. Railbed never holds the money, so there is no balance to freeze and nothing is held back from a merchant's sales. Settled sales can't be pulled back from the merchant's wallet; card disputes go to the provider that charged the card. Smart Routing sends buyers to the providers least likely to ask for ID, and the providers decide. Signing up takes an email, the business's website and a payout wallet, with no setup fee and no monthly fee. Railbed is a product of Railbed, LLC.

## Get started

- Sign up: https://app.railbed.io/signup
- Talk to sales: sales@railbed.com
- Other industries: https://railbed.com/industries/
