Ruba field guide
Why Ruba
Practical detail for building, selling, and operating software with Ruba.
Ruba guide
Why Ruba exists
The internet is global, but access to dependable payment infrastructure still depends heavily on where a founder lives. Ruba is being built to close that gap for software businesses.
Approved sellers get one place to create products, accept buyer payments, run subscriptions, understand revenue, and receive earnings.
Ruba guide
Global access
Sell internationally
Buyers pay through a familiar global checkout while sellers receive earnings through supported payout accounts in their own market.
Start where Stripe Payments does not
Ruba is designed first for founders in supported recipient countries that cannot open a conventional Stripe Payments account locally.
Country availability remains subject to Ruba review, Stripe Connect availability, sanctions controls, and local requirements.
Ruba guide
One commerce layer
Checkout
Hosted and embeddable purchase flows for software.
Billing
One-time, recurring, usage, seat, trial, and discount models.
Operations
Orders, customers, refunds, disputes, and seller balances.
Fulfilment
Downloads, license keys, repository access, and benefits.
Ruba guide
Built for developers
Ruba exposes a typed API, SDKs, scoped authentication, signed webhooks, and a sandbox so teams can integrate the commerce layer into their own product without rebuilding it.
Ruba guide
Clear economics
Ruba publishes its platform fee and identifies pass-through costs such as international cards, currency conversion, payouts, and disputes. Sellers should be able to understand a transaction without decoding a statement.
Read the pricing guide ↗