Invoice now
Change and collect immediatelyRuba computes the prorated difference, invoices it, and attempts payment in the same operation.
Ruba product infrastructure
Run the full recurring relationship
Launch a plan, change it mid-cycle, recover failed payments, and keep access in sync.
A recurring product connects billing state to customer access. Ruba owns the renewal machinery while your product responds to the resulting subscription and benefit states.
Execution workflow
The subscription lifecycle
Each commercial event advances the same durable record.
- 01
Checkout
Ruba creates the subscription, records the first order, and stores the payment method.
- 02
Active or trialing
Attached benefits remain granted while the customer is entitled to access.
- 03
Renewal
A new order applies current tax and discounts before charging the saved card.
- 04
Past due
A failed charge enters recovery instead of immediately ending the relationship.
- 05
Recovered or ended
A successful retry restores active status; cancellation or non-payment eventually removes access.
Capability matrix
Choose when a plan change takes effect
Set an organization default and override it for a specific API operation.
Next invoice
Change now, settle laterThe plan changes immediately and the prorated adjustment appears on the next renewal invoice.
Next period
Schedule without prorationThe current plan remains until the period closes, then the new one begins.
Deep dive specifications
A failed renewal gets time to recover
Recovery combines charge retries, customer communication, and a configurable access grace period.
- 01
Retry clock
Four attempts are scheduled after 2, 5, 7, and another 7 days, spanning 21 days in total.
- 02
Payment update
The first failure email sends the customer to the portal to replace the payment method.
- 03
Access grace
Benefits can end immediately or remain for 2, 7, 14, or 21 days while recovery runs.
- 04
Long-cycle notice
Cycles of six months or longer receive a renewal reminder seven days before the charge.
01
Plan configuration
Use fixed, free, or pay-what-you-want recurring pricing.
02
Mid-cycle changes
Upgrade or downgrade with the intended proration behavior.
03
Renewal recovery
Retry declined cards before moving the subscription out of service.
04
Customer control
Expose payment, invoice, plan, seat, and cancellation actions in the portal.
Ending access is an explicit choice
Cancel at period end keeps benefits available through the paid term and can be reversed before that date. Revoke immediately ends access at once and cannot be undone. The dashboard, API, and Customer Portal use the same rules.
Customers can also update payment methods, retrieve invoices, change plans, manage seats, and cancel through the hosted portal or an embedded customer experience.
Build with Ruba
Launch a recurring product
Set the cadence and benefits, then let Ruba maintain the lifecycle.