Follow one sale through the system
Think about Ruba as a sequence of connected records rather than a collection of unrelated payment tools.1
Model the offer
A catalog item holds the customer-facing name, pricing, billing cadence, checkout details, and benefits attached to the sale.
2
Open checkout
Send the buyer to a hosted buy link, create a checkout session, or place embedded checkout inside your product.
3
Record the transaction
A completed payment produces an order. Recurring offers also create a subscription that controls later renewals.
4
Deliver access
Benefits keep product access aligned with the order or subscription state.
5
Operate after purchase
Customers use the self-service portal, while your team follows revenue, refunds, balances, and payouts from Ruba.
Choose the revenue behavior
The catalog item determines how money should move. Start with the model that matches what the customer is buying.Charge once
Collect a fixed amount for a permanent purchase, download, service, or other non-renewing offer.
Renew on a schedule
Create an ongoing subscription with renewal, cancellation, recovery, and benefit state handled as one lifecycle.
Bill measured activity
Ingest events, aggregate them through a meter, and turn the resulting quantity into a charge.
Price access per member
Connect a subscription quantity to the members who actually receive access.
See the buying surface
Checkout uses the same offer and pricing model whether it is hosted or embedded.
Decide how your application connects
You do not need every integration surface on day one.Take the shortest launch path
1
Work in the sandbox
Use the testing environment while building. Sandbox data and credentials remain separate from production.
2
Create an access token
Issue an Organization Access Token for the organization your backend will operate.
3
Create the first catalog item
Configure its price, billing behavior, checkout copy, and any access that should be delivered.
4
Complete a test checkout
Confirm that the order, customer state, and attached benefits change as expected.
5
Subscribe to the events your product needs
Add a webhook endpoint and implement only the state transitions your application must react to.
Continue the build
Model an offer
Start with catalog structure, pricing, and delivery.
Connect your backend
Choose credentials and make the first authenticated request.
Read the API contract
Review environments, authentication, pagination, responses, and rate limits.