Skip to main content
The hosted Customer Portal exposes customer-owned billing records and recovery actions without giving the browser an organization credential.

​
What customers can do

The portal always provides purchase history, invoices, receipts, active subscriptions, benefit access, period-end cancellation, and default payment-method replacement. Optional settings can also expose email changes, plan changes, seat management, and metered usage.

​
Why it matters

​
Decisions and edge cases

No. Invoice and receipt access, subscription cancellation, and secure payment-method recovery remain available. You can disable optional plan, email, seat, and usage controls.
The hosted interface is consistent across organizations. Build a branded surface with the Customer Portal API when you need your own UI.Payment-method replacement remains on the hosted portal so card information does not enter your infrastructure.
The stable portal uses an emailed one-time code. A signed-in product can instead create a short-lived, pre-authenticated customer session.
The failure email links to the portal. Saving another default payment method causes Ruba to retry the open charge immediately.

​
Continue the build

Choose the entry route

Publish the stable URL or create an authenticated handoff.

Set the action boundary

Decide which optional self-service controls appear.

Build a custom portal

Use customer-scoped operations behind your own product UI.