Revenue operations
Checkout and payments
Connect reservations, invoices, deposits, packages, memberships, subscriptions, and payment collection.
Checkout context
Checkout is designed to stay connected to operational context. Invoices can reference reservations, line items, deposits, add-ons, packages, memberships, subscriptions, and family billing details.
Payment flows are routed through the frontend API and backend payment services, with Stax-related integration support present in the application.
Owner-facing benefits
- Keep revenue collection tied to the service workflow.
- Reduce duplicate entry between reservations and invoices.
- Support deposits and checkout prompts.
- Use packages, memberships, and subscriptions as part of account value.