Commerce add-on
RLX Payment Operations
Deposits, partial payments, tips, taxes, fees, schedules, refunds, invoices, receipts, and processor references.
CommerceCategory
1.0.0Version
ProductionRelease stage
$64.85 · AdvancedLicense
Commerce add-on
About this add-on
RLX Payment Operations for LifeRaft OS
Operational records for deposits, partial payments, tips, taxes, fees, schedules, refunds, receipts, and invoices. Never store full card data; use supported processors and verify local tax and refund requirements.
Deposits, partial payments, tips, taxes, fees, schedules, refunds, invoices, receipts, and processor references. Use it when the community needs a revenue layer for paid access, checkout support, entitlements, offers, or product operations while keeping the core lean.
At a glance
- Admin-managed content and settings
- Public pages with clean presentation
- Designed to run as an optional RLX module
- Creates monetization surface area that can be sold above a core community build
rlx-payment-ops
Version 1.0.0 $64.85 · Advanced
Production
Capabilities and outcomes
How RLX Payment Operations improves the build
The overview above identifies the core capability. These supporting outcomes help a project owner judge whether the add-on belongs in the package.
Structured currency for a clearer day-to-day workflow
Structured subtotal for a clearer day-to-day workflow
Structured tax for a clearer day-to-day workflow
Structured tip for a clearer day-to-day workflow
Structured fee for a clearer day-to-day workflow
Add-on-specific scope
Deposits, schedules, taxes, refunds, and receipts
Operational payment records for deposits, partial payments, tips, taxes, fees, schedules, refunds, cancellations, invoices, and processor references without card storage.
This module manages payment operations as its primary customer-facing records.
Entity type and IDcurrencysubtotaltaxtipfeedepositscheduleprocessor referencerefundreceiptand invoice
Typical workflow states: draft → pending → authorized → paid → partially refunded → refunded → failed → cancelled → archived.
Standalone value
What it does by itself
RLX Payment Operations can run as its own Commerce workflow. By itself, it focuses on Admin-managed content and settings, Public pages with clean presentation, and Designed to run as an optional RLX module, so a customer can use the module without buying every related add-on first.
Standalone means it does not have to be cross-linked with other add-ons. It still runs inside LifeRaft OS and requires a valid core LifeRaft OS license.
Connected value
What improves when related add-ons are active
When the customer also owns and activates related modules such as RLX PayPal, RLX Cart, RLX Invoices, RLX Bookings, and RLX Reservations, RLX Payment Operations can hand off data, links, reporting, access control, content, or follow-up steps into those workflows. Those connections are optional and depend on the package being built.
Best fit
Who should care about it
- Commerce builds that need RLX Payment Operations without forcing it into every install
Workflow
How it fits into a real build
- Configure settings, navigation, visibility, staff permissions, retention, and related add-ons
Works well with
The strongest builds connect the right modules
RLX Payment Operations becomes more valuable when it is paired with the workflows around it. Common pairings include RLX PayPal, RLX Cart, RLX Invoices, RLX Bookings, RLX Reservations, depending on the customer package and what the site needs to accomplish.
Admin setup
Confirm settings, navigation placement, permissions, and any required starter content before launch.
Public QA
Review the public page, empty states, mobile layout, and activated/deactivated states.
Payment QA
Test provider setup, order states, entitlements, refunds, and failed-payment recovery.
Docs and support
Add customer-facing notes, admin setup instructions, and known limitations for the module.
Customer FAQ
Common questions about RLX Payment Operations
What does RLX Payment Operations do?
Deposits, partial payments, tips, taxes, fees, schedules, refunds, invoices, receipts, and processor references.
Who is RLX Payment Operations best for?
Commerce builds that need RLX Payment Operations without forcing it into every install.
Can RLX Payment Operations run by itself?
RLX Payment Operations can run as its own Commerce workflow. By itself, it focuses on Admin-managed content and settings, Public pages with clean presentation, and Designed to run as an optional RLX module, so a customer can use the module without buying every related add-on first.
Do I need the other add-ons mentioned on this page?
No. Related add-ons are optional package pairings, not required purchases unless a project specifically needs that wider workflow. RLX Payment Operations should still explain a useful standalone job before any connected modules are considered. Standalone means it does not have to be cross-linked with other add-ons. It still runs inside LifeRaft OS and requires a valid core LifeRaft OS license.
What changes when related add-ons are active?
When the customer also owns and activates related modules such as RLX PayPal, RLX Cart, RLX Invoices, RLX Bookings, and RLX Reservations, RLX Payment Operations can hand off data, links, reporting, access control, content, or follow-up steps into those workflows. Those connections are optional and depend on the package being built.
Which add-ons work well with RLX Payment Operations?
RLX Payment Operations commonly pairs with RLX PayPal, RLX Cart, RLX Invoices, RLX Bookings, RLX Reservations. Active pairings depend on the package, customer workflow, and installed add-ons.
What should be decided before launching RLX Payment Operations?
RLX Payment Operations should be launched with its real data model and public routes in mind. Optional integrations: rlx-paypal, rlx-cart, rlx-invoices, rlx-bookings, rlx-reservations, rlx-food-orders, rlx-tickets.
How much does RLX Payment Operations cost?
RLX Payment Operations has a $64.85 Advanced add-on license. The add-on requires a valid Personal, Professional, Creator, or separately agreed LifeRaft OS core license.
What support is included for RLX Payment Operations?
Enhanced add-on support indicates a broader or more operationally involved module. Exact response scope and duration are confirmed with the licensed package and core edition. Personal includes 3 months, Professional includes 6 months, and Creator includes 12 months of core support and updates.
How ready is RLX Payment Operations for deployment?
Production module: packaged for normal licensed deployment, subject to the hosting, configuration, and integration checks described in the documentation.
How does RLX Payment Operations fit into a real LifeRaft OS build?
Configure settings, navigation, visibility, staff permissions, retention, and related add-ons.
Does the public page include implementation details?
No. The public page explains customer value, package fit, related modules, and launch expectations. Setup steps, route details, data structures, hooks, and operator-only notes stay in the licensed add-on documentation.
Related add-ons
Explore the surrounding add-on ecosystem
Coming soon
Want RLX Payment Operations in your LifeRaft OS build?
RLX Payment Operations is part of the modular LifeRaft OS add-on roadmap. Join the waitlist or discuss a package so the right modules can be planned around the way your community, product, studio, or business actually operates.