Take cards for annual plans and lifetime deals, with nothing held back.
Processors serve software companies, until a launch doubles your volume or a year paid up front starts to look like a long delivery window. Then the reserves arrive. Railbed takes your buyers’ cards for plans paid up front and settles each sale to a wallet you control, with nothing held back.
- Nothing held back
- No monthly fee
- A webhook for every sale
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
Can a SaaS company take card payments without a reserve on annual plans?
Yes, for plans paid up front. Processors place reserves on accounts with long delivery windows, rising disputes or sudden jumps in volume, and an annual plan or a lifetime deal launch can look like all three. Railbed takes your buyers’ cards through independent, licensed card providers and settles each sale to a wallet you control, with nothing held back and no application to pass. It has no recurring billing, so each plan is one payment.
Why software companies lose their payment account
Software is a business card processors like. It ships no parcels, it has no stock to lose, and most of what it sells is delivered the moment someone logs in. That’s why a SaaS founder is often surprised when the payout stops: the account was approved in minutes, and nobody asked what the product does until something changed.
- 5% + 50¢What a merchant of record charges per checkout sale
- 1.5%Visa’s fraud and dispute ratio before a merchant is flagged, since April 2026
- $2.5 billionWhat Amazon agreed in 2025 to settle the FTC’s case over Prime sign-ups and cancellations
This dispute occurs when a cardholder says you continued to charge them for a recurring transaction after they cancelled the agreement.
What changes is usually one of the things a software company does on purpose. Stripe’s own reserves FAQ lists the reasons it holds back part of a business’s money, and several read like a SaaS growth plan. A reserve can follow when “The business belongs to an industry with longer-than-average delivery windows”, which is what an annual plan is: the buyer pays today for twelve months of service. It can follow when “The account shows an unexplainable sharp increase in processing volume”, which is what a launch, a lifetime deal or a Product Hunt day looks like from the outside. It can follow when “The account has elevated dispute activity”, and subscription businesses collect disputes from people who forgot they signed up. The same page warns that “In some rare cases, a reserve may be required indefinitely.”
Subscription billing brings its own kind of dispute. Visa gives it a condition of its own, 13.2, and its Dispute Management Guide describes it in one line: “This dispute occurs when a cardholder says you continued to charge them for a recurring transaction after they cancelled the agreement.” Each one counts toward the ratio Visa watches. Since 1 April 2026 Visa treats fraud reports and disputes above 1.5% of a merchant’s settled card-not-present sales as excessive, down from 2.2%, and merchants in its monitoring programme pay $8 for each disputed or fraudulent transaction.
Free sign-up forms attract a second problem. Card testing is fraudsters checking whether stolen card numbers still work, and the pages they target are the ones that let them “Save card” or “Make a payment”: a free trial that asks for a card is both. The fraud guide also warns that “Excessive retries (dunning) of payments can look like card testing” when they come in spikes, so the retry schedule that recovers failed renewals can itself make an account look risky.
Some founders never get that far. Stripe’s list of supported countries runs to about fifty, so a software studio in Pakistan, Bangladesh, Vietnam or Egypt starts by looking for a company address somewhere else. And a few kinds of software sit on processors’ restricted lists outright, such as cyberlocker and file-sharing services.
The usual answer is a merchant of record, a reseller that sells your software to the buyer in its own name. It handles sales tax and VAT, and it charges for that: Paddle’s published price is 5% + 50¢ per checkout transaction, and Lemon Squeezy, owned by Stripe, lists the same 5% + 50¢ with further fees for some international payments and payouts twice a month.
What a software company runs into, in short
- A reserve on success. A launch, a lifetime deal or a wave of annual upgrades looks like a sharp increase in volume with a long delivery window behind it.
- Disputes from renewals. Buyers who forgot the plan renewed call it a cancelled recurring transaction, and each one counts toward Visa’s 1.5%.
- Card testers at the trial form. A free trial that takes a card is a place to check stolen ones, and the failed attempts count against your account.
- A 5% cut to stay safe. A merchant of record takes on tax and risk for about 5% plus 50 cents of every sale.
- No account at all. Founders outside the processors’ countries, and a few product types, can’t open one in their own name.
How Railbed works for a software company
Railbed is card checkout for software that never holds your money. Buyers pay with the card they already have, and each sale settles as USDC straight to a wallet you control, usually minutes after they pay. There’s no balance with Railbed for a risk team to freeze when a launch goes well, and no rolling reserve on a year paid up front.
| What goes wrong today | With Railbed |
|---|---|
| A reserve after a launch or a lifetime deal | Nothing is held back from your sales, and there’s no cap on monthly sales |
| Annual plans read as a long delivery window | Each plan settles to your own wallet as soon as it’s paid |
| Renewal disputes and a 1.5% ratio to watch | Settled sales can’t be pulled back from your wallet. Card disputes go to the provider that charged the card |
| 5% + 50¢ to a merchant of record | The card provider’s fee, a 1% network fee and the Railbed fee from 0.9% |
| No account outside the processors’ countries | Sign up with an email, your website and a payout wallet. No underwriting and no application to pass |
An independent, licensed card provider charges the buyer’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, then sends your server a signed webhook so your app can switch the plan on.
The trade-off is plain: Railbed has no recurring billing. Every purchase is one payment. A year of Pro is one charge for a year, and when the year ends, the customer buys again. For a lot of software that’s a change worth thinking through, and the next two chapters are about exactly that.
Renewals, trials and the rules around them
Software that renews automatically is regulated more closely every year. None of these rules forbid subscriptions; they set out how a business has to ask, remind and let people leave. A risk team reads them as the reason renewal disputes happen.
- 18 Apr 2020
Visa’s rules for free trials and introductory offers take effect: terms sent at sign-up, and a reminder with a cancellation link at least seven days before the first full-price charge.
- 21 Jun 2023
The FTC sues Amazon, saying it enrolled people in Prime without consent and made cancelling hard.
- 1 Jul 2025
California’s amended automatic renewal law applies to contracts made, changed or extended from this date: consent after a free trial, an annual reminder and a “click to cancel” link.
- Jul 2025
The Eighth Circuit vacates the FTC’s click-to-cancel rule before it takes effect. Enforcement under the federal ROSCA law continues.
- 25 Sep 2025
Amazon agrees to pay $2.5 billion, a $1 billion civil penalty and $1.5 billion in refunds, to settle the FTC’s case.
- 11 Mar 2026
The FTC asks for public comment on a new rule for negative option plans, starting the rulemaking again.
- 1 Apr 2026
Visa lowers the fraud and dispute ratio at which it counts a merchant as excessive, from 2.2% to 1.5%.
- 1 Oct 2026
New York City’s click-to-cancel rule takes effect for automatic renewals offered to city consumers.
Two things follow for a software company. First, the rules attach to the automatic renewal itself: the notices, the reminder before a trial converts, the cancellation path. A plan that doesn’t renew by itself has nothing to cancel and no renewal to remind anyone about. Second, the federal rule is unsettled as of November 2026. The FTC is writing a new one, and in the meantime it enforces the Restore Online Shoppers’ Confidence Act, which is the law behind the Amazon settlement. State laws such as California’s apply on their own terms. If you keep automatic renewals on another processor, those rules still apply there; ask your own adviser how they apply to your plans.
Visa’s 2020 rules are worth reading even if you never offer a trial. Visa requires a merchant whose trial is ending to send a reminder “at least seven (7) days before initiating a recurring transaction”, with the price, the date and a way to cancel. Visa wrote them because a buyer who is surprised by a charge disputes it.
Selling software without automatic renewal
Moving a plan off automatic renewal isn’t free. Some customers renew late, some don’t renew at all, and a monthly plan that was quietly charged for years becomes a decision your customer makes again. Here is how software companies sell well without it.
Price the year, not the month. Most SaaS already offers an annual price at a discount. Make it the main offer, and offer quarterly or six-month plans for buyers who won’t commit to a year. A Railbed pricing table can show up to four plans side by side with a price switch, such as Monthly and Yearly. Railbed’s own guide is plain about what the labels mean: “/ mo” and “/ yr” describe what you sell and never schedule another charge.
Remind people yourself. Your app knows when each plan ends. Send your own renewal emails at 30, 7 and 1 days before, each with a link to buy the next period. A renewal the customer chooses is the opposite of the surprise charge that turns into a 13.2 dispute.
Invoice your bigger accounts. For a team on a yearly contract, send an invoice a month before the term ends. Railbed’s invoices carry a due date, reminders by email before and after it, and your terms, and the customer can pay in full or in parts.
Keep monthly for those who want it. If many of your customers are on monthly plans, keep those on the processor you already have and use Railbed for the plans paid up front. Nothing about Railbed is exclusive.
What you sell, and how each sells through Railbed
Software comes in more shapes than a monthly subscription. Each of these is one payment, made by card and settled to your wallet:
- Annual and multi-month plans. A year, six months or a quarter of a plan, sold from a pricing table or from your own app through the API. Your app records when the period ends.
- Lifetime deals. One price for lasting access, sold during a launch window. Railbed has no cap on monthly sales, so a launch day is only a busy day.
- Credit packs and usage bundles. Prepaid credits for API calls, exports, seats-hours or messages, sold in fixed sizes. Your app adds the credits when the payment webhook arrives.
- Desktop software and licence keys. A perpetual licence, a major-version upgrade or a two-machine bundle. Your server issues the key when it hears the sale is paid.
- Plugins, themes and extensions. A licence for one site or many, with a year of updates. Sell it from your own site with a checkout page or a buy button.
- Team plans and seats. A year of five seats, or more seats added halfway through the term. Price the add-on for the months left and sell it as one payment.
- Enterprise contracts. A yearly contract with a purchase order number, sent as an invoice with lines, tax, terms and a due date. A total over 100,000.00 is split across invoices.
- Setup, onboarding and migrations. One-off services sold beside the plan, on the same invoice or on its own checkout page. Paid support sessions sell the same way, as on the tech support page.
Set prices in USD, EUR, GBP, CAD, AUD, INR or SEK. Every price must be one a card provider can take, the smallest about $2, and a price of $10 or more gives buyers the widest choice of providers.
How a sale works
A buyer on your pricing page chooses a year of the Pro plan. Your server creates a checkout session with the buyer’s account id as its reference, or the page opens a Railbed pricing table.
Railbed’s checkout asks for an email and any details you turned on, such as a company name. Smart Routing picks the card provider most likely to approve this buyer.
The buyer pays on the provider’s page, in a new tab. The provider decides whether to ask for identity details, and Smart Routing tries the providers least likely to ask first.
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.
Railbed sends your server a signed
payment.paidwebhook carrying your reference. Your app turns on the plan, records the end date and sends the welcome email.
Try the whole flow in Test mode first. Payments are simulated, no card is charged, and Test webhooks reach your server as real signed requests.
Licence keys and plan access from webhooks
The part of a software sale that matters most happens after the payment: the plan switches on, or the key arrives. Railbed is built to hand that moment to your code.
Create a checkout session from your server with a secret key. Give it a reference (your order or account id) and up to 20 metadata keys, such as the plan and the seat count. Both come back on the payment and on every webhook, so your fulfilment never has to guess who paid. A session stops accepting new payments 24 hours after it’s created, so create one when the buyer clicks, not in advance.
Then listen for the [payment.paid event](/docs/webhooks/events/). Railbed signs every delivery, retries failed ones for about 21 hours, and delivers at least once, so the same event can arrive twice. The webhook guide says it plainly: deduplicate on the event id, and grant each order once per payment id. A licence server that stores the payment id with each key it issues is already safe against a repeat.
A few details software teams ask about:
- Keys stay on your server. Secret keys start
rb_live_orrb_test_, and the API refuses calls from browsers. Your app calls your server, and your server calls Railbed. - Read-only keys for dashboards. A Read only key lists payments, orders and customers and changes nothing, which suits an internal revenue board.
- Rate limits fit checkout traffic. About 120 requests a minute per mode for each account, and 12 session starts a minute. Queue bursts on your side and back off when you get a 429.
- Receipts are yours to send. A paid checkout shows an on-screen receipt or sends the buyer to your success page. The licence email, the invoice for the books and the welcome series come from your app.
- No-code works too. If your fulfilment lives in Zapier or n8n, their Railbed apps subscribe to the same events.
Free trials without a card on file
Railbed’s checkout doesn’t save cards for later. That takes away the most common SaaS sign-up, the trial that asks for a card and converts it on day 14, and it is worth being clear about what you get instead.
A trial without a card lets anyone try the product, which most teams want anyway. When the trial ends, the user buys a plan through the checkout, the same way they’d buy anything. Nobody is charged by surprise, so there is no trial-conversion dispute to receive and no reminder rule to meet. And because your sign-up form never asks for a card, it isn’t a place to test one.
What you lose is the conversion that relied on people forgetting. Many founders find that the users who buy deliberately are the ones who stay, but the number to measure is yours: run the trial both ways if you can, and keep whichever earns more after refunds and disputes.
Lifetime deals and launch days
A lifetime deal is the sale processors understand least. A buyer pays once for access that never ends, often during a launch week when volume is ten times a normal week. To a risk model that is the “longer-than-average delivery window” and the “sharp increase in processing volume” in one transaction, and a reserve is the usual answer.
Selling through a deals marketplace avoids the reserve by moving the waiting elsewhere. AppSumo, for example, pays partners 60 days after the end of each month, in line with its 60-day refund policy, and keeps 30% of revenue from the customers it brings to you (it keeps 5% of sales from buyers you bring yourself). A deal that sells out on the first of the month is paid at the start of the month after next.
Selling the deal from your own site through Railbed changes the timing. Each sale settles to your wallet minutes after the buyer pays, there’s no cap on monthly sales, and nothing is held back to cover refunds. That puts the refund promise on you: if you offer a money-back window, keep enough of the launch’s USDC in your wallet to honour it, because nobody else is holding it for you. If creators promote the deal for a commission, you pay them from your own wallet; the affiliate networks page covers how that works beside Railbed.
Tax, VAT and the merchant of record question
The real reason many software companies pay 5% to a merchant of record isn’t card acceptance. It’s tax. A merchant of record sells to the buyer in its own name, so it collects and pays the sales tax, VAT and GST in every country, and you invoice it once.
Railbed isn’t a merchant of record. You are the seller, so the tax on your sales stays your responsibility, as it would with any processor:
- In the EU, software and other electronically supplied services sold to consumers are taxed where the customer lives, and sales to businesses where the business is established. The EU’s One Stop Shop lets a seller register in one country and declare VAT for all of them; below €10,000 a year of cross-border consumer sales, an EU seller charges its own country’s VAT.
- In the US, states decide. TaxCloud’s tracker counted 24 states and Washington, D.C. taxing SaaS in some form as of October 2026, and reports California and Colorado starting statewide on 1 January 2027.
- On your invoices, Railbed’s invoice builder adds a named tax rate and prints your terms, so a business customer gets a document its accounts team can file.
If your buyers are mostly businesses, the tax work is often small, and paying 5% of everything to avoid it is expensive. If they’re consumers in thirty countries, a tax service or an accountant is worth more than any checkout. Ask your accountant which applies before you choose.
Apps in the app stores
Railbed takes card payments on the web. It doesn’t replace in-app purchase inside an iPhone or Android app, and the app stores’ own rules decide whether your app may send people to a web checkout. In the US those rules have been in court since Epic sued Apple: in December 2025 the Ninth Circuit largely upheld the order that lets US apps link to outside purchases, and sent the question of what commission Apple may charge on them back to the lower court. Check the store’s current guidelines before you add a link, and sell plans on your website the way you always could.
Before your first sale
None of this needs an application or a waiting period. It is the short list worth getting right once.
A payout wallet. Save the Polygon wallet your sales should settle to. Use a wallet you hold the keys to, not an exchange deposit address.
Plans that end by themselves. Rewrite your plan pages so each says what the payment buys and for how long. Nothing should read as if it renews automatically.
Your own renewal emails. Make sure your app emails customers before their plan ends, with a link to buy the next period.
Fulfilment on the webhook. Turn the plan on or issue the key when
payment.paidarrives, deduplicate on the event id, and store the payment id with what you granted.A refund rule. Write down your money-back window and how you’ll refund, because Railbed can’t reverse a settled payment for you.
Tax settings. Decide where you collect sales tax or VAT and add it to your prices or invoice lines. A merchant of record isn’t doing it for you here.
A run in Test mode. Buy a plan in Test mode and watch your app switch it on before you take a Live payment.
Running Railbed beside your billing system
Most software companies already have a processor, and many should keep it. The usual first step is to add Railbed beside it, for the sales your current setup handles worst. Four places it earns its keep:
- Plans paid up front. Send annual plans, lifetime deals and credit packs through Railbed, and leave monthly renewals where they are. The money that would sit in a reserve settles to your wallet instead.
- The launch. Put the lifetime deal or the launch discount on a Railbed checkout, so a record week doesn’t bring a reserve on the account that carries your renewals.
- The declined card. When your main checkout declines a card, offer Railbed on the same screen. A buyer turned away by one fraud screen is often approved by a different card provider.
- Buyers your processor turns down. A card from a country your processor declines, or a buyer whose bank blocks the charge, gets a second way to pay.
Use the same customer id as the reference in both, so your app grants access the same way whichever checkout took the money.
Refunds, cancellations and disputes
A paid plan has settled to your wallet, so a refund is something you send, not something a processor takes from you. When a customer asks for their money back within your window, send the USDC back or agree another arrangement with them, then record the refund on the order with the API so your books match.
There’s nothing to cancel, which is the point. A plan bought through Railbed ends on its own date, so a customer who changes their mind halfway through simply doesn’t buy the next period. Whether you refund the unused months is your policy to write; say it on the plan page.
A dispute works differently too. The buyer’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. There’s no chargeback fee and no chargeback ratio on your Railbed account. None of that makes a refund policy optional: a customer who can get their money back from you quickly has little reason to ask their bank, and a card provider may decline future payments from a buyer who disputes.
What stays your responsibility
Railbed’s acceptable use policy holds only the limits the law puts on Railbed itself, and Railbed stops new payments only when the law requires it. Everything about how you run your software stays yours: what your plan pages promise, your refund window, whether a plan renews by your own reminder or not at all, the sales tax and VAT on each sale, your terms of service and privacy policy, and the export rules for software sold abroad. If your product handles other people’s money, health data, as medical billing software does, or children’s data, the rules for that are yours to meet with or without Railbed.
Fees and getting paid
Railbed shows every fee before anyone pays, and all of them come out of the USDC that arrives. The card provider takes its own fee and exchange spread, shown to the buyer on its page. Then come a 1% network fee and the Railbed fee, from 0.9%, shown in your dashboard and locked when the buyer starts paying. There’s no setup fee, no monthly fee and no chargeback fee.
The buyer pays the price you set. A year of Pro at $348 is a $348 payment, and what reaches your wallet is that amount less the fees above, usually minutes after the buyer pays. To pay your hosting bill or your team from a bank account, send USDC from your wallet to any exchange or off-ramp you use and withdraw it there. Some contractors and vendors will take USDC directly.
Refunds are your call. Railbed can’t reverse a settled payment, so refund the customer yourself in a way you both agree.
Railbed compared with a merchant of record
| Merchant of record | Railbed | |
|---|---|---|
| Who sells to the buyer | The merchant of record, in its own name | You do |
| Price | 5% + 50¢ per sale at the two best known, with extras for some international payments | The card provider’s fee, a 1% network fee and the Railbed fee from 0.9% |
| Sales tax and VAT | Collected and paid for you | Yours, as with any processor |
| Automatic renewals | Yes, with its billing tools | No. Each plan is one payment |
| Getting paid | Payouts to your bank on its schedule, twice a month at one | USDC to your own wallet, usually within minutes |
| Holds | Its risk team can still hold your payouts | Nothing is held back from your sales |
| To start | An application, and approval of your product | An email, your website and a payout wallet |
When Railbed is not the right fit
Railbed suits software sold as plans paid up front, lifetime deals, credit packs, licences and invoices. It is the wrong tool in a few cases:
- Your business is monthly renewals. Railbed has no recurring billing and no dunning. If most of your revenue is monthly plans charged automatically, keep them on a billing system built for that.
- You bill by metered usage after the fact. Railbed can sell credits in advance, but it can’t charge a card at the end of the month for what was used.
- You want someone else to handle tax. A merchant of record takes on sales tax and VAT for you. Railbed doesn’t, so you or your accountant do.
- Your buyers pay inside a mobile app. In-app purchases stay with the app store’s billing.
- 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 software company meets in a processor’s reply, a card network’s rules or a renewal law.
- Merchant of record
- The company that sells to the buyer in its own name and owes the sales tax and VAT on the sale. A reseller platform takes this role so the software company doesn’t have to.
- Reserve
- Part of a business’s money a processor holds back to cover future disputes and refunds. Processors name long delivery windows and sharp jumps in volume among the reasons.
- Delivery window
- The time between a payment and the end of what it buys. An annual plan’s window is twelve months, which is why a risk team treats it differently from a download.
- Negative option
- A sale where the buyer’s silence counts as agreement to keep paying, such as an automatic renewal or a trial that converts. The FTC’s rules and ROSCA govern it in the US.
- ROSCA
- The Restore Online Shoppers’ Confidence Act, the federal US law the FTC uses against online sign-ups and renewals that lack clear consent or a simple way to cancel.
- Dispute condition 13.2
- Visa’s condition for a cancelled recurring transaction, where a cardholder says they were charged after they cancelled.
- Card testing
- Fraudsters checking whether stolen card numbers work, usually on forms that save a card or take a small payment.
- Dunning
- Retrying a failed renewal charge and emailing the customer about it. Retries in sharp spikes can look like card testing to a processor.
- Lifetime deal
- A one-time price for lasting access, often sold during a launch. The buyer pays once; the service runs on.
- Webhook
- A signed request Railbed sends your server when something happens, such as a payment settling. Your app uses it to switch on a plan or issue a key.
Questions
Can I take card payments for SaaS without a merchant account?
Yes. Railbed isn’t a merchant account. You sign up with an email, your website and a payout wallet, with no underwriting and no application to pass. Buyers pay by card through independent, licensed card providers, and each sale settles as USDC to your wallet.
Does Railbed support recurring billing or subscriptions?
No. Every purchase is one payment, and Railbed never charges a card again on its own. Sell annual or multi-month plans paid up front, remind customers yourself when a plan is ending, and use invoices for yearly contracts. If you need automatic monthly renewals, keep them on a billing system built for that.
Will Railbed hold my money after a big launch?
No. Each sale settles to your own wallet as soon as it’s paid, and there’s no cap on monthly sales. Nothing is held back from your sales, so a lifetime deal that sells a thousand copies in a day settles a thousand times.
Why did Stripe put a reserve on my SaaS account?
Its reserves FAQ names reasons that include an industry with longer-than-average delivery windows, an unexplained sharp increase in volume and elevated dispute activity. Annual plans, launches and renewal disputes can each look like one of those. The FAQ says a reserve is usually temporary, and in rare cases indefinite.
How do I deliver licence keys or switch on a plan?
Create checkout sessions from your server with your own reference and metadata, then listen for the payment.paid webhook. Railbed signs and retries each delivery, so deduplicate on the event id and issue each key once per payment id.
Can I sell a lifetime deal through Railbed?
Yes. A lifetime deal is one payment like any other. Sell it from a checkout page or your own app, and keep enough USDC in your wallet to honour your refund window, since nothing is held back to cover refunds for you.
Is Railbed a merchant of record like Paddle or Lemon Squeezy?
No. You remain the seller, so sales tax and VAT on your sales stay yours. In exchange, you don’t pay 5% plus 50 cents per sale, and the money settles to your own wallet, usually within minutes, rather than on a payout schedule.
Can enterprise customers pay by invoice with a PO number?
Yes. A Railbed invoice has up to 50 lines, a discount, tax, a due date of up to two years ahead, a reference or PO number of up to 64 characters and your terms. It emails reminders, and the customer can pay in full or in parts by card.
Can I offer a free trial?
Yes, without a card. Railbed doesn’t store cards for later, so a trial can’t convert by itself. When it ends, the user buys a plan through the checkout, which also means nobody disputes a charge they didn’t expect.
Will my customers have to show ID?
Usually not, but the card provider decides. Smart Routing sends each buyer to the providers least likely to ask, and some may ask for light details such as a name, date of birth or address. Railbed can’t promise a buyer will never be asked for ID.
Can I run Railbed beside my current processor?
Yes. Many software companies keep monthly renewals where they are and send annual plans, lifetime deals and credit packs through Railbed. Use the same customer reference in both so your app grants access the same way.
What happens if a customer disputes a charge?
The buyer’s bank raises it with the card provider that charged the card, and nothing comes out of your wallet. Settled sales can’t be pulled back from your wallet, and there’s no chargeback fee or ratio on your Railbed account. Refund promptly when a customer asks, so they have no reason to go to their bank.
Which currencies can I price plans in?
USD, EUR, GBP, CAD, AUD, INR or SEK. Every price must be one a card provider can take, from about $2, and $10 or more gives buyers the widest choice of providers. Almost every sale settles as USDC on Polygon whatever the currency.
How do I turn USDC into money in my bank?
Send it from your wallet to an exchange or off-ramp you use and withdraw it there. Railbed’s guide walks through the steps, and some vendors and contractors take USDC directly.
Sources
- Stripe: Reserves frequently asked questions, modified 2 November 2026, checked 20 November 2026
- Visa: Dispute Management Guide for Merchants, checked 20 November 2026
- Visa: Acquirer Monitoring Program fact sheet, checked 20 November 2026
- Merchant Risk Council: Stricter VAMP ratio thresholds are now in effect, 1 April 2026, checked 20 November 2026
- Stripe: Protect yourself from card testing, checked 20 November 2026
- Stripe: Global availability, checked 20 November 2026
- Stripe: Prohibited and restricted businesses, last updated 22 September 2026, checked 20 November 2026
- Paddle: Pricing, checked 20 November 2026
- Lemon Squeezy: Pricing, checked 20 November 2026
- Visa: Updated policy for subscription merchants offering free trials or introductory promotions, effective 18 April 2020, checked 20 November 2026
- FTC: FTC takes action against Amazon for enrolling consumers in Amazon Prime without consent, 21 June 2023, checked 20 November 2026
- California Legislature: AB 2863, automatic renewal and continuous service offers, 2024, checked 20 November 2026
- Gibson Dunn: FTC restarts negative option rulemaking after Eighth Circuit vacatur, 2026, checked 20 November 2026
- FTC: FTC secures historic $2.5 billion settlement against Amazon, 25 September 2025, checked 20 November 2026
- FTC: FTC seeks public comment in response to advance notice of proposed rulemaking regarding negative option, 11 March 2026, checked 20 November 2026
- Skadden: New York City’s click-to-cancel rule, September 2026, checked 20 November 2026
- AppSumo: Getting paid, checked 20 November 2026
- European Commission: Place of taxation, checked 20 November 2026
- European Commission: The One Stop Shop, checked 20 November 2026
- TaxCloud: SaaS sales tax by state, October 2026, checked 20 November 2026
- US Court of Appeals for the Ninth Circuit: Epic Games v. Apple, 11 December 2025, checked 20 November 2026
Last updated .
PaidA year of the Pro plan, settled to your wallet$348.00
A year paid up front.
Settled to your own wallet.
Set up in under a minute. Your first payment can settle today.
- Nothing held back
- No monthly fee
- A webhook for every sale
Moving a lot of volume? Talk to our team