---
title: "Railbed vs PaymentCloud: compare checkout and settlement"
description: "Railbed vs PaymentCloud: compare wallet settlement, bank payouts, billing and refund operations. Choose by real requirements, not headline approval or fee claims."
url: "https://railbed.com/insights/railbed-vs-paymentcloud-compare-checkout-and-settlement/"
markdown: "https://railbed.com/insights/railbed-vs-paymentcloud-compare-checkout-and-settlement/?format=md"
published: "2026-10-05"
author: "Railbed"
publisher: "Railbed by MediaGlobe"
section: "Insights"
reading_time: "7 min"
language: "en"
---

# Railbed vs PaymentCloud: compare checkout and settlement

> Railbed vs PaymentCloud: compare wallet settlement, bank payouts, billing and refund operations. Choose by real requirements, not headline approval or fee claims.

Source: https://railbed.com/insights/railbed-vs-paymentcloud-compare-checkout-and-settlement/ · Published: 2026-10-05 · 7 min read · Railbed by MediaGlobe

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

Choose Railbed if you want card checkout whose proceeds settle as USDC to a wallet you control and you can operate the separate treasury and refund steps. Choose a PaymentCloud proposal if you want a conventional high-risk merchant account with bank funding under a negotiated acquiring agreement. The main difference is the operating model—not a universal winner on fees or approval.


**TL;DR**

- Railbed provides card checkout with self-custody USDC settlement; PaymentCloud offers conventional merchant-account proposals.
- Railbed states it does not underwrite businesses; independent card providers still decide buyer transactions.
- Railbed does not automatically rebill saved cards or reverse settled payments.
- Compare actual total costs, required functions and final money destinations before choosing.


## Railbed vs PaymentCloud at a glance

Railbed’s [wallet and settlement guide](https://railbed.com/docs/user-guide/wallet-and-settlement/) documents a noncustodial model. PaymentCloud’s published fee guidance describes conventional acquiring, account charges, disputes and reserve structures. Use the actual PaymentCloud offer for your business rather than applying a published example as your quote.

| Dimension | Railbed | PaymentCloud proposal |
| --- | --- | --- |
| Best for | Card checkout with wallet settlement | Conventional acquiring and bank-funding requirements |
| Merchant setup | Railbed states no business underwriting or industry-approval application | Business review under the proposed acquiring arrangement |
| Settlement | USDC to the saved Polygon wallet | Funding destination and schedule in the actual offer |
| Custody | No custodial Railbed merchant balance or payout request | Review who holds proceeds and under which conditions |
| Cost model | Account fee, applicable provider terms and separate money movement | Complete account, processing, gateway and event-charge schedule |
| Automatic renewals | Railbed does not auto-rebill saved cards | Confirm the proposed gateway and recurring-billing functions |
| Refunds | Separate reimbursement; no settled-payment reversal | Confirm the supported refund process in the offer |
| Buyer approval | Independent card provider decides | Actual transaction decisions remain separate from merchant approval |

## Why this matters after a shutdown

Both options belong in the same buying decision, but they do not replace identical parts of your business. If the old problem was fund custody, wallet settlement changes that structure. If the requirement is automatic recurring billing with bank payouts, a conventional proposal needs its own feature and contract review.

For a merchant processing more than $50,000 monthly, list the requirements before comparing rates. Include where payroll money must arrive, which orders renew automatically and how support refunds a customer. Those are selection criteria, not details to discover after launch.

## Railbed is the direct fit for self-custody USDC settlement

Railbed sends completed card-payment proceeds to the Polygon wallet saved for that payment. It does not maintain a custodial merchant balance or require a payout request from the dashboard.

That gives the merchant a concrete wallet receipt to reconcile. It also transfers operational responsibility to the business: protect wallet access, check the network and receiving destination, operate conversion and match any bank withdrawal.

The advantage is not that every downstream service becomes unrestricted. An exchange or withdrawal service has its own eligibility, checks and terms. Bank receipt is a separate event from wallet settlement.

**Railbed wins on fit when the requirement is specifically card checkout with direct wallet settlement.** A business that does not want that workflow should not select it solely because it differs from acquiring.

## A conventional PaymentCloud proposal fits a bank-payout requirement

PaymentCloud’s published guide describes conventional merchant accounts that settle funds to a bank, with account-specific fees and possible reserves. That model can fit a finance team that wants acquiring and bank funding rather than wallet operations.

The actual contract still matters. Identify the acquiring and processing parties, gateway, payout conditions, deductions and termination provisions. A funding schedule must be read with its reserve and hold clauses.

This is a functional fit, not proof that every proposal is available to every business. Require acceptance for the actual products, billing model and markets in the application.

**PaymentCloud’s conventional model is the better category fit when bank funding is essential and wallet settlement is not wanted.** Select the offer only when its terms and functions support the requirement.

## Railbed’s setup is not conventional acquiring underwriting

Railbed’s acceptable use policy states it does not underwrite or review businesses and has no list of approved industries. The merchant remains responsible for lawful activity and market-specific obligations.

Do not turn that into a claim that the buyer’s card always succeeds. The independent provider charges the card, displays its own terms and decides any identity checks. Merchant setup and buyer payment decisions are separate.

A PaymentCloud application follows its proposed merchant-account process. Do not compare an email account being created on one service with a fully tested integration on another and call the timing result an equivalent launch comparison.

## Both require a complete buyer-flow test

A card-payment interface says little about the exceptions support will handle. Review the happy path, a closed tab, an unresolved attempt and a customer who believes they paid.

Railbed’s documented journey opens the independent provider for card entry and keeps the original checkout waiting for confirmation. In Live mode, a decline is not directly reported to Railbed, so the payment can remain open or in progress. That is not proof the card was charged.

For either option, verify what updates the order and what authorizes delivery. A return to the thank-you page is not payment proof. Do not invent a checkout-completion rate from a demonstration.

## Automatic renewals are a real selection boundary

Railbed’s pricing tables sell one payment per purchase. Monthly or yearly labels describe the access period; they do not schedule another card charge. It is not a drop-in saved-card subscription biller.

If unattended renewals matter, confirm recurring support, credential custody, import capability, retries and cancellation handling in the conventional proposal. Do not assume a merchant-account name alone proves the specific gateway functions.

A merchant can deliberately use customer-initiated repurchase instead, but that is a business-model change. Plan reminders and access expiry rather than presenting it as an invisible subscription migration.

## Refund operations differ too

Railbed cannot reverse a settled payment. The merchant arranges a reimbursement in USDC or another way agreed with the customer, then records it. Recording a refund in WooCommerce does not send funds.

For PaymentCloud’s proposal, establish the actual refund mechanism, permissions, funding source and treatment after account closure. If an original-card refund workflow is essential, require evidence of that function rather than assuming Railbed provides the same control.

Card disputes are handled by the charging provider in Railbed’s model. Customer support, delivery remedies and reimbursement records remain merchant work. Do not confuse a wallet transfer with closure of a card-side dispute.

## Total cost has no winner without the actual transactions

Apply both complete cost models to the same volume, order count, currencies and customer markets. On the acquiring side, separate fees from reserve withholding. On the wallet side, include the independent provider’s quote and the path to the destination where the business needs money.

Railbed’s fee is shown in the account and saved when the payment starts. Its net receipt can be reported later than the paid status. Use the specific payment, not a current wallet balance, to reconcile deductions.

Do not compare a headline component with another proposal’s all-in result. The correct endpoint is identical: usable funds in your required asset and destination.

## The decision scorecard

| Requirement | Decision |
| --- | --- |
| Direct self-custody USDC settlement | Railbed |
| Conventional acquiring with bank funding | Assess PaymentCloud’s actual offer |
| Automatic card renewals | Confirm a recurring-capable proposal; Railbed does not auto-rebill |
| Original-card refund workflow | Confirm the proposed provider function; Railbed requires separate reimbursement |
| Lowest full cost | No winner without account-specific terms and matched transaction data |
| Guaranteed buyer approval | Neither model establishes a guarantee |

### Choose Railbed if

You want wallet settlement, can operate its treasury steps and sell through customer-initiated payments. You understand the refund procedure and have a verified payment-to-order workflow.

### Choose the PaymentCloud proposal if

Its conventional acquiring, gateway and bank-funding arrangement meets the billing, refund and banking functions you require, under terms you accept. A different settlement asset is not a reason to abandon a working fit.

## FAQ


**Is Railbed the same as PaymentCloud?**

No. Railbed provides checkout with USDC wallet settlement. PaymentCloud offers conventional merchant-account proposals with account-specific acquiring and funding terms.

**Which is cheaper?**

Compare actual complete cost schedules on the same transactions and final destination. Neither a provider name nor a base component establishes total cost.

**Does Railbed underwrite my business?**

Railbed’s acceptable use policy states that it does not underwrite or review businesses. Independent card-provider transaction checks and your legal obligations remain separate.

**Does Railbed automatically renew subscriptions?**

No. Each purchase is one payment; a monthly or yearly label does not schedule an automatic card charge.

**Can Railbed reverse a settled payment?**

No. The merchant arranges a separate reimbursement and records it. A refund note does not send money.

**Does USDC settlement mean my bank has been paid?**

No. Wallet receipt, conversion and bank withdrawal are separate stages with their own records and conditions.

**Will either option guarantee every card is approved?**

No such guarantee follows from the merchant account or settlement model. Test the actual buyer journey and review the transaction requirements.


## One last thing

Compare one real order, its next renewal and its eventual refund—not just its first successful checkout. **The best fit is the model your team can operate after the first sale.**

### Sources and related guides

Checked October 29, 2026. [PaymentCloud’s fees guide](https://paymentcloudinc.com/blog/high-risk-merchant-account-fees/), updated July 18, 2026, describes conventional account structure and charges. It is not an offer to this merchant or an independent performance study.

- [Railbed acceptable use policy](https://railbed.com/acceptable-use/)
- [Pricing-table and renewal limits](https://railbed.com/docs/user-guide/pricing-tables/)
- [Buyer experience and provider choice](https://railbed.com/docs/user-guide/buyer-experience/)

## More from Insights

- [Best NOWPayments Alternatives for Card and Crypto Payments](https://railbed.com/insights/best-nowpayments-alternatives/): Compare NOWPayments alternatives for card checkout, crypto acceptance and bank settlement. Choose Railbed, BitPay or PaymentCloud by your payment needs.
- [Best Stripe Alternatives for iGaming Deposits and Payouts](https://railbed.com/insights/best-stripe-alternatives-igaming/): Compare Stripe alternatives for iGaming. See where Railbed, Nuvei and Paysafe fit on deposits, player withdrawals, verification, settlement and compliance.
- [Best Stripe Alternatives for Supplement Brands](https://railbed.com/insights/best-stripe-alternatives-supplements/): Compare Stripe alternatives for supplements. Choose Railbed or PaymentCloud by one-time checkout, recurring billing, buyer checks and settlement needs.