On Railbed’s homepage, the villain arrives by email. A fictional merchant named Alex learns that payments have stopped and $48,210 will be held for up to 120 days. The message ends with a particularly efficient little cruelty: please do not reply. It is a sales illustration, not a customer case study. But it introduces the question around which Railbed has built its business: who gets to keep the money between the sale and the payout?
- Buyers pay by card; merchants receive USDC on Polygon.
- Railbed targets legal businesses that mainstream processors restrict.
- The advertised 0.9% starting fee has company: network and provider charges.
- Merchants control their wallets, and handle their own refunds.
Railbed, operated by MediaGlobe, sells checkout software for merchants who find that question uncomfortably practical. Its audience includes supplements sellers, adult creators, dating businesses, licensed gambling operators and digital-goods shops. These are its stated markets. The common problem is dependence on someone else’s decision about whether the next sale may proceed, and when the last one becomes spendable.
The balance is the product decision
The mechanism is straightforward enough to diagram, though it involves several businesses. A merchant publishes a payment link, adds a buy button or creates a checkout through the API. The buyer chooses a provider and pays on that provider’s page. The provider buys USDC, which travels through a one-time forwarding address to the merchant’s own Polygon wallet. Fees come out along the way.
Railbed records and checks the payment. It says it never holds, pools or controls the funds. Its distinction from a conventional merchant account is therefore architectural: remove the merchant balance sitting inside the checkout company. In Railbed’s explanation, money already delivered to the merchant’s wallet is beyond its ability to freeze. The merchant takes responsibility for the wallet and its keys.
“Whoever holds your money between the sale and the payout can freeze it.”
Railbed, explaining its design
That distinction also explains a potentially confusing detail. Railbed markets card acceptance while describing itself as software, rather than a card processor or exchange. Independent providers perform those functions under their own terms. Railbed builds the route between checkout, conversion, settlement and the merchant’s order system.
The bouncer still has a say
Railbed calls its provider selection Smart Routing. Its website says the system considers signals including location, browser, IP and card, seeking a provider that can accept the payment with fewer identity checks and lower costs. Banxa, Coinbase, Stripe and Topper appear in its routing illustration. Availability and the final decision belong to each provider.
This is where the cheerful promise meets the working machinery. Railbed’s acceptable-use policy says stricter provider rules still apply. Identity checks can still happen. A legal product must be legal where the merchant operates and where the buyer is located. A provider can decline a payment or merchant category. Merchants cannot split purchases to dodge checks.
For a merchant choosing between Railbed and a specialist high-risk merchant account, this is the comparison that matters. Railbed offers settlement into a wallet without its own rolling reserve. In exchange, the business accepts a crypto settlement workflow and dependencies on on-ramp providers. A seller who needs every payout delivered directly into a bank account has another step to arrange.
The small percentage with two companions
The homepage advertises Railbed fees “as low as 0.9%.” That is the software company’s component. A separate 1% network fee pays for the forwarding infrastructure. The card provider adds its own fee and exchange spread, varying with provider, country and amount. There is no setup fee, monthly fee or Railbed reserve.
The sensible calculation runs all the way to usable cash. After settlement, moving USDC or converting it into a bank deposit may create additional costs. Railbed’s terms explicitly leave those with the merchant. Volume pricing is available, and the site invites businesses processing more than $50,000 monthly to contact sales. A headline rate alone cannot tell a merchant what each order will yield.
A paid order needs more than a happy browser
The developer documentation contains one of Railbed’s most useful lessons for any seller: a customer arriving on a success page does not prove payment. Fulfilment should follow a verified notification or an authenticated API status check. Railbed checks settlement before marking a payment paid, including whether the amount and destination match expectations.
There are practical wrinkles. The documentation says a payment counts as paid when the arriving value meets its stated 90% threshold against the order’s dollar value; larger shortfalls go to merchant review. A “held” payment is a record needing a decision, rather than a custodial Railbed balance. Late payments can arrive after a session expires. Duplicate notifications must not deliver the same order twice.
That makes Test mode valuable. It simulates paid, underpaid, declined and failed outcomes without charging a card or moving funds. A merchant can rehearse the awkward cases before selling anything. The official n8n integration, released in October 2026, extends this to workflows that look up orders, react to signed payment events and record fulfilment.
The refund comes back to you
Railbed also supports assistants through an MCP server: they can read business records and prepare checkout or webhook changes, with the owner confirming changes inside Railbed. The attraction is less administrative work. The same boundary remains: a report about payment records is not independent verification of funds on a blockchain.
For buyers, the provider’s name can appear on the card statement. Railbed’s integration guide advises merchants to explain that and send their own order confirmations. Refunds also belong to the merchant: Railbed cannot reverse a settled payment, and the API has no refund endpoint. Card disputes go through the provider that charged the card.
The lesson readers can copy is specific. Map who holds funds, who approves payments, who confirms delivery and who handles a refund. Then test the handoffs. Railbed’s pitch makes ownership of the payout unusually visible. A merchant still has to run the rest of the transaction.