Sell cloud storage by card without being mistaken for a file locker.
Processors file storage and sharing services beside the cyberlockers the card networks make banks register, so one complaint about a user’s upload can end card payments for every customer. Railbed takes your customers’ cards for storage, backup and sharing plans and settles each payment to a wallet you control.
- No underwriting
- No monthly 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 cloud storage or file hosting company take card payments?
Storage companies can take cards, but processors put file-sharing services in a restricted category, card networks make banks register file lockers, and one complaint about what a user stored can close the account. 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 doesn’t charge cards automatically, so each plan is a prepaid term bought in one payment.
Why do card processors treat file hosting as high risk?
A storage company sells space on its servers, and what customers put in that space is theirs. To a processor, that is the problem: it can’t see the files, it knows that some file services have been built for piracy, and it has been told by the card networks to treat the ones that look like it with suspicion. Honest backup, sync and transfer services get read through the same lens.
- 2015Visa, Mastercard and then PayPal stopped serving Mega, an encrypted storage service
- MCC 4816The code Mastercard makes banks use for each registered high-risk cyberlocker
- 37Online markets on the US government’s 2025 piracy list, two of them file lockers
unknowability of what is on the platform
The processors say so in their own rules. Stripe’s restricted businesses list, last updated 22 September 2026, has a heading for cyberlockers and lists “Cyberlocker and file-sharing services” among the restricted businesses that “require additional due diligence by Stripe”. Visa’s risk guide for payment facilitators names “Cyberlockers and similar remote digital file-sharing” as a high-brand-risk category. Braintree’s acceptable use policy refuses “membership subscriptions > 1 year” without its prior written approval, which catches the two-year and lifetime plans storage companies like to sell.
The story that made processors careful is Mega. In February 2015 TheWrap reported that PayPal had ended its relationship with the encrypted storage service, and that “Visa and Mastercard earlier cut off the site”. It followed a report on cyberlockers by an anti-piracy group and pressure from a US senator on the card companies. Mega’s own account was that PayPal cited the “unknowability of what is on the platform”: end-to-end encryption meant nobody but the user could see the files, which was the product’s whole point.
Most storage companies are nothing like the services that drew that attention. They still meet the same keyword filters, and a processor that reads “file sharing” on a sign-up form doesn’t stop to check whether the business pays uploaders or sells encrypted backups to accountants.
What storage businesses run into
- An application refused, or approved and then closed months later, because the description said “file sharing”.
- One complaint about a single user’s upload, from a rights holder or a card brand, putting card payments for every customer at risk.
- End-to-end encryption read as a reason for suspicion rather than a feature, because the processor can’t inspect what it pays for.
- Two-year and lifetime plans refused or capped, and yearly renewals that customers forget and dispute.
What a cyberlocker is, in the card networks’ own words
Mastercard is the only network that publishes a definition, and it is worth reading closely because it describes a business model, not a technology. Section 9.4.6 of its Security Rules and Procedures, “High-Risk Cyberlocker Merchants”, tells banks to register any file service that meets even one of its criteria, code its sales under MCC 4816 with a special transaction category, and satisfy themselves that the business is lawful before they take it on.
| What Mastercard asks banks to register | What a storage business usually sells |
|---|---|
| Rewards or cash paid to uploaders based on how often their files are downloaded | Space. The customer pays you; nobody is paid for traffic |
| Link codes handed to uploaders so files can be listed on indexing and linking sites | Private folders, shared with the people the customer chooses |
| Files deleted unless someone buys premium, so free storage is never really storage | Files kept for as long as the plan is paid, whatever their downloads |
| Premium sold on faster download speed or removing ads, “as opposed to storage space” | Premium sold on more storage, more devices, longer version history |
| A “link checker” that helps uploaders put removed content back up | Removed content stays removed, and accounts that repeat get closed |
| Anonymous file owners and promotion of copyrighted file types | Known account holders and a published copyright policy |
The criteria read like an indictment because they come from one. When the US Justice Department charged Megaupload’s founders on 19 January 2012, it said the site “was structured to discourage the vast majority of its users from using Megaupload for long-term or personal storage by automatically deleting content that was not regularly downloaded”, that it paid uploaders through a rewards programme, and that when told about an infringing file it “would disable only a single link to the file”. The site earned, the indictment alleged, “more than $175 million in illegal profits through advertising revenue and selling premium memberships”.
The same pattern is still on the US government’s list. The 2025 Review of Notorious Markets.pdf), released on 3 March 2026, names 1fichier and Rapidgator among its 37 online markets, and says Rapidgator “collects revenue through its premium membership and subscription plans and employs rewards and affiliate schemes to compensate users based on downloads and sales of new accounts”. A storage company that pays nobody for downloads, keeps files because they are paid for, and closes repeat infringers sits on the other side of every line in that table. It is worth being able to show it.
How does Railbed fix it?
Railbed is card checkout for storage, backup and file-sharing businesses 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 |
|---|---|
| “File sharing” on an application brings a refusal or a later closure | No underwriting and no application to pass. Sign up with an email, your website and a payout wallet |
| One complaint about one user’s file puts every customer’s payments at risk | Railbed stops new payments only when the law requires it, and never holds money it has already settled |
| Encryption reads as a reason to refuse | Nobody asks what is inside your customers’ folders |
| Sales sit in a processor balance that can be frozen | Each payment settles to your own wallet, with nothing held back |
| Stolen-card disputes come out of your balance with a fee | Settled sales can’t be pulled back from your wallet; card disputes go to the provider that charged the card |
| Lifetime and multi-year plans refused or capped | Any term is one payment, from about $2 up to 100,000.00 |
| Forgotten renewals come back as disputes | Each term is a payment the customer chooses, and an invoice can remind them when it ends |
Railbed checks that the right amount reached the right wallet before it marks a payment Paid, and a signed webhook tells your system to raise the customer’s quota or extend their plan.
What you can sell through Railbed
Storage businesses come in a few shapes, and each sells through a different part of Railbed:
- Personal cloud storage. Put a pricing table of up to four plans on your site, with a price switch between one-year and two-year terms. Each purchase is one payment, never a subscription.
- Online backup for computers and servers. Create a checkout session from your app when a customer upgrades, with their account ID as the reference, and raise the quota when the signed webhook says Paid.
- Business and team storage. Send an invoice with a line per seat or per terabyte, tax, a due date and email reminders, and let the company pay in full or in parts.
- File transfer and sharing. Sell a year of large transfers or a pack of password-protected shares from a buy button on your pricing page.
- Lifetime plans. A plan that never renews is a single payment, which is how some storage companies already sell it. pCloud’s pricing page offers storage for “one lifetime payment”.
- Customers who’d rather pay in crypto. Privacy-minded customers often hold stablecoins. Turn on crypto payments and they can pay on six EVM networks, or in coins such as Bitcoin into a wallet you saved for that network. Card stays the default.
Which checkout fits your storage business
| What you sell | What to use | What you build |
|---|---|---|
| A few fixed plans on your pricing page | A pricing table with up to four plans and a one-year or two-year price switch | A required question for the customer’s account email or username, so the payment finds the account |
| Upgrades inside your desktop or mobile app | A checkout session for each upgrade, with the account ID as its reference | One API call and one webhook handler that raises the quota |
| Storage for companies with several seats | An invoice with seats and terabytes as lines, tax and a due date | Nothing from the dashboard, or one call to the invoices API |
| Plans sold from a WordPress site | The WooCommerce plugin | Nothing. Install it and connect your account |
| Codes sold in batches to resellers | An invoice for the batch, paid in full or in parts | Your own code generator, which issues the codes when the invoice is paid |
A pricing table is a reusable checkout, so it doesn’t carry your own order reference. Ask for the account email or username as one of up to five questions of your own, mark it required, and it arrives in the webhook beside the payment. Upgrades that start inside your app are better as checkout sessions, where your server sets the reference itself.
How a storage plan sale works
Here is one sale from start to finish: a customer buys a year of 2 TB storage for $96 from the pricing table on your site.
The customer chooses the 2 TB plan with the switch on one year, enters their email and the username of the account to upgrade, and chooses to pay.
Smart Routing sends them to the card provider most likely to approve their card, based on their country, the amount and which providers are working today. The provider decides whether to ask for any details, such as a name or address.
The provider charges the card and pays USDC, which is forwarded to your wallet on Polygon. Railbed checks that the right amount arrived and marks the payment Paid.
Railbed sends a signed
payment.paidwebhook. Your system finds the account by the username answer, sets its quota to 2 TB until the same date next year, and records the event’s ID so a retried delivery doesn’t add another year.The customer gets their receipt, and you get an alert in Telegram or Slack if you’ve connected one. Eleven months later, your system sends them an invoice for the next year, due on the day the plan ends.
Build and test the whole flow in Test mode, where payments are simulated and no card is charged. The fulfilment guide shows the checks to make before you change an account.
Encryption and the problem of not knowing
The Mega story is the clearest case of a processor refusing what it can’t see. End-to-end encryption means the storage company holds files it can’t read, and the processor behind it can’t either. For a backup service that sells to lawyers and doctors, that is the selling point. For a payments risk team that has been told file lockers can carry pirated films, it is a blind spot.
Railbed doesn’t ask what is in your customers’ folders, and it doesn’t take payments on the condition that you can read them. That doesn’t take the law out of the picture. Copyright notices, the European Union’s notice-and-action rules and the child-safety duties in the next sections still apply to an encrypted service, and how each applies to files you can’t read is a question for your own adviser. What changes is narrower: a choice you made for your customers’ privacy is no longer a reason for your payments to stop.
Copyright notices, safe harbours and repeat infringers
The legal ground a US storage company stands on is section 512 of the copyright law, which protects a service that stores users’ material from damages for what users upload, if it follows the rules. A payment company doesn’t follow them for you, and neither does Railbed. The main ones:
- A designated agent. The US Copyright Office explains that a service provider that lets users store material “must designate an agent to receive notifications of claimed copyright infringement”, publishing the agent’s details on its own website and filing them in the Office’s online directory. Its FAQ says a designation costs $6 and “will expire and become invalid three years after it is registered” unless it is renewed.
- Acting on notices. Under 17 U.S.C. § 512(c), a provider that receives a notice with the required elements, or otherwise learns of infringing material, must “respond expeditiously to remove, or disable access to” it.
- A repeat-infringer policy. Section 512(i) gives the protection only to a provider that “has adopted and reasonably implemented” a policy for terminating repeat infringers “in appropriate circumstances”, and tells its users about it.
The last point is where providers have lost. In BMG v. Cox, decided on 1 February 2018, the Fourth Circuit held that an internet provider couldn’t rely on the safe harbour because it had not reasonably implemented its policy. The Supreme Court’s later ruling in Cox v. Sony, on 25 March 2026, threw out a $1 billion verdict against the same provider, holding that contributory liability needs intent, shown “only if the party induced the infringement or the provided service is tailored to that infringement”. That is a narrower test than many feared, but it doesn’t make a repeat-infringer policy optional: the safe harbour still depends on one.
Megaupload’s indictment is the counterexample. It said the site “failed to terminate accounts of users with known copyright infringement” and disabled one link while leaving the file in place. A storage company that removes the file, closes accounts that keep uploading infringing material and can show its records is doing what the law asks, and it is also the strongest answer it can give anyone, a payment company included, who asks what it does about piracy.
Storage in the European Union and the United Kingdom
Outside the United States, the duties are different in detail and similar in spirit. Three matter most for a storage business:
- The Digital Services Act. Regulation (EU) 2022/2065 has applied to every hosting service since 17 February 2024. The European Commission says that “all hosting services (including online platforms) are required to inform users whenever they remove or restrict access to their content and explain the reasons”, a “statement of reasons”. Hosts also need a way for anyone to report illegal content. The Commission’s overview adds that micro and small companies have lighter obligations than large platforms.
- The copyright directive’s platform rule. Article 17 of Directive (EU) 2019/790 makes large content-sharing platforms responsible for licensing what users upload, but its definition leaves out business-to-business cloud services and cloud services that let users upload content for their own use. A personal storage service is generally outside it; a service built for public sharing may not be. The EU’s highest court held in YouTube and Cyando, on 22 June 2021, that under the older rules a platform isn’t liable for users’ uploads unless it does more than provide the platform, or knows about illegal content and fails to act.
- The UK’s Online Safety Act. Ofcom opened an enforcement programme on 17 March 2025, the day its illegal content duties came into force, because “Evidence shows that file-sharing and file-storage services are particularly susceptible to being used for the sharing of CSAM”. In June 2025 it opened investigations into seven file-sharing services.
Which of these applies to you depends on where your users are and what your service lets them do, and that is a question for your adviser, not your payment company.
Child safety duties and where Railbed draws its line
Child sexual abuse material is the one subject where storage law, payment law and Railbed’s own rules all say the same thing. In the United States, 18 U.S.C. § 2258A requires a provider that learns of apparent child sexual abuse material on its service to report it to the National Center for Missing and Exploited Children’s CyberTipline. The REPORT Act, signed on 7 May 2024, made a report a request to preserve the reported content for one year.
The UK is going further. On 16 November 2026 Ofcom announced new rules that include “deploying automated tools to proactively identify and remove previously unknown CSAM on certain platforms, including all file sharing services”, expected to apply from early 2027.
Railbed’s acceptable use policy holds only the limits the law sets on Railbed itself: child sexual abuse material, money laundering and structuring, and sanctions. A storage service that knowingly hosts abuse material is outside it, and Railbed stops new payments where the law requires it. A storage service that reports what it finds, removes it and closes the accounts is doing what the law asks, and nothing about that changes how it is paid.
- Jan 2012
Megaupload’s domains are seized and its founders charged with racketeering, copyright and money laundering offences.
- Feb 2015
PayPal ends its relationship with Mega, after Visa and Mastercard had already cut the site off.
- Dec 2016
The US Copyright Office moves designated agents to an online directory, with each designation lasting three years.
- Feb 2018
A federal appeals court rules that an internet provider loses the safe harbour for not enforcing its repeat-infringer policy.
- Feb 2024
The EU’s Digital Services Act applies to every hosting service, with notice-and-action and statements of reasons.
- May 2024
The REPORT Act extends what US providers must preserve after reporting child abuse material to one year.
- Mar 2025
Ofcom opens an enforcement programme into file-sharing and file-storage services.
- Mar 2026
The US Supreme Court overturns a $1 billion copyright verdict against an internet provider, narrowing contributory liability.
- Early 2027Ahead
Ofcom’s rules on proactive detection of unknown abuse material are expected to apply to all file-sharing services.
Prepaid terms instead of automatic renewal
Railbed doesn’t store cards or charge them on a schedule, so a storage plan is a term the customer buys: a year, two years, or for life. Storage suits that better than most software sold by subscription, because the customer’s files give them a reason to come back, and a renewal they chose is one they don’t dispute.
Sell the first term from your pricing table or app, as above. Your system records the date the term ends.
A few weeks before that date, create an invoice for the next year through the invoices API, due on the last day of the term, with reminders turned on.
Railbed emails it in your business’s name with its PDF, and reminds the customer 3 days before the due date, on it, and 3 and 7 days after while it is unpaid.
The customer pays by card. The USDC settles to your wallet, Railbed marks the invoice Paid, and the webhook extends the plan.
If the invoice goes unpaid, do what your terms say: keep the files read-only for a grace period, then delete them after the notice you promised.
Write the grace period and the deletion notice into your terms before the first renewal falls due. Customers are far more forgiving of a lapsed plan than of lost files, and the terms are what you point to when one asks.
Before you sell your first plan
There is no application to wait for, so the work is on your side of the connection. Get these right once and a paid plan upgrades the account 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.
Terms that clear the minimum. Card providers have minimums, the smallest about $2, and around $10 or more gives customers the widest choice of providers. Sell a $1.99 monthly plan by the year.
A way to find the account. A required question for the username on a pricing table, or the account ID as the reference on an API checkout session.
A webhook that upgrades once. Raise the quota when the signed
payment.paidevent arrives, and record the event’s ID, because a failed delivery is retried.A renewal and deletion policy. Decide when you send the next year’s invoice, how long a lapsed account stays readable, and what notice comes before deletion.
A copyright agent and policy. File your designated agent with the Copyright Office, publish a notice address and a repeat-infringer policy, and keep records of what you removed and when.
A report path for illegal content. A way for anyone to report a file, and a process for the child-safety reports the law requires.
A run in Test mode. Buy, upgrade and renew a test account with a Test API key before you take a Live payment.
Running Railbed beside the processor you have
Nothing about Railbed is exclusive, and a storage company with a working card account shouldn’t close it to try something new. The useful places to add Railbed first:
- For the plans your processor won’t take. Lifetime and two-year plans that a processor caps or refuses can sell through Railbed while monthly plans stay where they are.
- For customers your gateway declines. When a card from another country fails your fraud screen, offer Railbed on the same page. A different card provider often approves it.
- As the spare. A storage company with two ways to take cards keeps selling in the week one of them pauses payouts to ask what its customers store.
Use the same account ID or username in both, and let both paid events call the same upgrade code. Each Railbed payment shows on its own timeline, so your team can see which way a customer paid.
Refunds, deleted files and disputes
A storage plan is delivered from the first minute and keeps being delivered, so decide your refund rule before the first request. A common one is a full refund within a short window after purchase and a pro-rated one after that, with nothing back on a lifetime plan once it has been used for a while. Whatever you choose, put it on your pricing page and in your terms.
Because the payment has settled to your wallet, a refund is something you send. Send USDC back or agree another arrangement with them, then lower the quota or close the plan in your own system.
A dispute is a different thing. The customer’s bank raises it with the card provider that charged the card, under that provider’s terms and the card networks’ rules, and nothing comes out of your wallet. Keep the account’s sign-up date, the upgrade, the files uploaded since and the sign-ins, because together they show the service was delivered. A customer who gets a quick answer from you has less reason to call their bank.
What stays your responsibility?
Railbed takes payments. It doesn’t moderate files, answer copyright notices, file reports or decide what your users may store. Your terms of service, your designated agent and repeat-infringer policy, the Digital Services Act’s notice-and-action and statements of reasons if you serve EU users, the Online Safety Act’s duties if you serve the UK, the child-safety reports the law requires, the protection of your customers’ personal data, and tax on what you sell all stay yours, as they would with any processor.
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, and the customer pays the price you set.
Set prices in USD, EUR, GBP, CAD, AUD, INR or SEK. Settlement is almost always USDC on Polygon, straight to your wallet. To pay for disks, bandwidth and data centre space 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 monthly plans are best sold by the year, which also gives customers the widest choice of providers. A lifetime plan of several hundred dollars is well inside what a checkout can take.
Railbed compared with a file hosting merchant account
| Payment processor or high-risk account | Railbed | |
|---|---|---|
| Approval | An application, weighed on what your service is and what your users might store | No underwriting and no application to pass |
| A complaint about one user’s file | Can end card payments for every customer | Railbed stops new payments only when the law requires it |
| Encrypted storage | Often a reason for extra questions or refusal | Nobody asks what is inside your customers’ folders |
| Reserve | Added when disputes or complaints rise | Nothing is held back from your sales |
| Stolen-card disputes | Paid from your balance, with a fee and a ratio | Settled sales can’t be pulled back. Card disputes go to the provider |
| Long plans | Often capped at a year, or refused | Any term or a lifetime plan, as one payment |
| Renewals | Stored cards charged automatically | Invoices with reminders, paid by choice |
| 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 storage company that is content to sell prepaid terms 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. A business built on silent monthly renewals should keep its current processor for them.
- You bill by the gigabyte after the fact. Railbed doesn’t meter anything. Usage-based storage has to become a prepaid allowance, or a monthly invoice for customers you trust.
- You pay uploaders, affiliates or resellers out of each sale. Railbed has no payouts to third parties, and paying uploaders by the download is what the card networks treat as a file locker.
- You send thousands of renewal invoices a day through Railbed’s email. A business can send 200 invoice emails a day. A larger service creates invoices through the API and emails each link from its own system.
- 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 storage company talks to a payment company, and when a payment company reads about storage.
- Cyberlocker
- A file service built for distributing files rather than keeping them, typically paying uploaders for downloads and deleting files nobody downloads.
- High-risk cyberlocker registration
- Mastercard’s requirement that banks register file services meeting its criteria, code their sales MCC 4816 and confirm they are lawful.
- Designated agent
- The contact a US service provider files with the Copyright Office to receive copyright notices, renewed every three years.
- Safe harbour
- Section 512’s protection from damages for what users upload, kept only by a provider that follows its conditions.
- Repeat-infringer policy
- A published rule for closing the accounts of users who keep uploading infringing material, which the safe harbour requires a provider to enforce.
- Statement of reasons
- The explanation the Digital Services Act requires a hosting service to give a user when it removes or restricts their content.
- End-to-end encryption
- Encryption where only the user holds the keys, so the storage company can’t read the files it keeps.
- 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 closed my cloud storage account. Can I use Railbed?
Yes. Signing up takes an email, your website and a payout wallet, with no underwriting and no application to pass. Your customers pay by card through independent, licensed card providers, and each payment settles as USDC to your wallet. Railbed stops new payments only when the law requires it, and it never holds what has already settled.
Is a file hosting service legal to run?
In most countries, yes. Storing users’ files is lawful, and laws such as section 512 in the United States and the Digital Services Act in the EU protect a host from liability for users’ uploads when it follows their conditions: acting on notices, closing repeat infringers, and in the EU explaining removals. Services built to distribute pirated files have been prosecuted and listed by governments. Whether your service meets the conditions where your users are is a question for your own lawyer.
Why do processors treat file hosting as high risk?
Because they can’t see what is stored, and because some file services were built for piracy. Stripe restricts “cyberlocker and file-sharing services”, Visa calls cyberlockers a high-brand-risk category, and Mastercard makes banks register file services that pay uploaders, delete unpopular files or sell download speed rather than storage space. An honest storage service is often caught by the same keyword.
Does Railbed care whether my storage is end-to-end encrypted?
No. Railbed doesn’t ask what is in your customers’ folders, and encryption is not a reason to stop payments. The law still applies to an encrypted service, including copyright notices and child-safety duties, and how it applies to files you can’t read is a question for your adviser.
Can Railbed charge my customers every month or every year automatically?
No. Railbed never stores a card or charges one on a schedule. Sell each term as one payment, and send an invoice with reminders when it ends. Customers who choose to renew don’t dispute a charge they forgot about.
Can I sell lifetime storage plans?
Yes. A lifetime plan is one payment like any other, and a checkout or invoice can take up to 100,000.00 in a single payment. Say plainly in your terms what “lifetime” means if your company closes or the plan changes.
What happens if someone buys a plan with a stolen card?
The money that settled stays in your wallet: settled sales can’t be pulled back, and card disputes go to the provider that charged the card. The account is still yours to deal with. Close it under your terms if you find it was bought fraudulently, and keep your own limits on how fast new accounts can upgrade.
Do customers need crypto or a crypto wallet to pay?
No. They pay with a normal debit or credit card on a card provider’s page, and many can use Apple Pay or Google Pay. The USDC goes to your wallet, not theirs. Customers who already hold stablecoins can pay with them if you turn crypto payments on.
Will my customers be asked for ID?
The card provider decides. Smart Routing sends each customer to the providers least likely to ask, and many payments need nothing beyond the card. Some providers ask for a name, date of birth or address, and occasionally more for larger amounts.
Do I still need a DMCA agent if I use Railbed?
Yes. A payment company doesn’t change your copyright duties. The Copyright Office says a US provider that stores users’ material must designate an agent to keep the section 512 safe harbour, which costs $6 and must be renewed every three years. You also need a repeat-infringer policy that you actually enforce.
Can I pay affiliates or uploaders through Railbed?
No. Railbed has no payouts to third parties, so it can’t split a sale with an affiliate or pay an uploader. Pay affiliates yourself from your wallet. Paying uploaders by the download is what Mastercard’s rules treat as a file locker, so think carefully before you do it at all.
How do I link a payment to the customer’s account?
On an API checkout session, put the account ID in the reference. On a pricing table or buy button, add a required question such as “Account email” or “Username”. The answer arrives on the order and in the payment.paid webhook, so your system can upgrade the right account.
Can I keep my current processor and add Railbed?
Yes. Nothing about Railbed is exclusive. Many storage companies keep monthly plans where they are and use Railbed for long plans, for customers abroad, or as a second way to take cards. Use the same account ID in both and let both paid events call the same upgrade code.
How do I get the money into my bank?
Payments settle as USDC on Polygon to your wallet. Send it to an exchange or off-ramp you use, sell it for dollars or your own currency, and withdraw to your bank. The user guide walks through it step by step.
Sources
- Stripe: Prohibited and restricted businesses, last updated 22 September 2026, checked 20 November 2026
- Visa: Payment facilitator and marketplace risk guide, checked 20 November 2026
- Braintree: Acceptable use policy, last updated 8 November 2017, checked 20 November 2026
- Mastercard: Security rules and procedures, section 9.4.6, high-risk cyberlocker merchants, checked 20 November 2026
- TheWrap: PayPal cuts off Mega cloud site over piracy concerns, 27 February 2015, checked 20 November 2026
- US Department of Justice: Justice Department charges leaders of Megaupload with widespread online copyright infringement, 19 January 2012, checked 20 November 2026
- Office of the US Trade Representative: USTR releases 2025 review of notorious markets for counterfeiting and piracy, 3 March 2026, checked 20 November 2026
- Office of the US Trade Representative: 2025 Review of Notorious Markets for Counterfeiting and Piracy.pdf), 3 March 2026, checked 20 November 2026
- US Copyright Office: DMCA designated agent directory, checked 20 November 2026
- US Copyright Office: DMCA designated agent directory FAQ, checked 20 November 2026
- Legal Information Institute: 17 U.S. Code § 512, limitations on liability relating to material online, checked 20 November 2026
- US Court of Appeals for the Fourth Circuit: BMG Rights Management v. Cox Communications, 1 February 2018, checked 20 November 2026
- Supreme Court of the United States: Cox Communications v. Sony Music Entertainment, 25 March 2026, checked 20 November 2026
- EUR-Lex: Regulation (EU) 2022/2065, the Digital Services Act, checked 20 November 2026
- European Commission: The Digital Services Act brings transparency, checked 20 November 2026
- European Commission: The Digital Services Act, checked 20 November 2026
- EUR-Lex: Directive (EU) 2019/790 on copyright in the Digital Single Market, checked 20 November 2026
- Court of Justice of the European Union: YouTube and Cyando, joined cases C-682/18 and C-683/18, 22 June 2021, checked 20 November 2026
- Ofcom: Enforcement programme into measures being taken by file-sharing and file-storage services, opened 17 March 2025, checked 20 November 2026
- Ofcom: Platforms must take stronger action to combat child sexual abuse material online under new Ofcom rules, 16 November 2026, checked 20 November 2026
- Legal Information Institute: 18 U.S. Code § 2258A, reporting requirements of providers, checked 20 November 2026
- Congress.gov: Public Law 118-59, the REPORT Act, 7 May 2024, checked 20 November 2026
- pCloud: Pricing, lifetime and subscription plans, checked 20 November 2026
Last updated .
PaidA year of 2 TB storage, settled to your wallet$96.00
Your customers keep their files.
You keep what they pay.
Set up in under a minute. Your first payment can settle today.
- No underwriting
- No monthly fee
- Settled sales stay yours
Moving a lot of volume? Talk to our team