Version Effective Date: June 16, 2026
This Billing and Subscription Policy governs the entire commercial configuration, payment methods, recurring financial ledger systems, automated renewal procedures, and B2B corporate bulk purchasing matrices implemented across the Nimbus ecosystem.
Nimbus provides its SaaS platform through diverse institutional commercial tiers, flat-rate monthly/annual technical access licensing frameworks, and high-volume B2B regional distributor purchasing modules. All pricing schedules, bulk lesson token rates, currency conversions, processing fees, and regional agency enrollment metrics are clearly displayed within the administrative dashboard or checkout interfaces at the exact time of transaction.
For Regional Distribution Partners executing localized commercial initiatives, Nimbus implements a B2B Bulk Inventory Accumulation model. Under this model, institutional entities execute large-scale credit purchases (e.g., the Agency Licensing Pack or Custom Volume Tier). These transactions are structured as upfront wholesale procurements of digital service tokens or server seats allocated within our central cloud database ledger.
To ensure uninterrupted technical access to the Learning Management System (LMS) dashboards and dedicated server pipelines, all time-phased SaaS subscription tiers are engineered with an integrated automatic renewal protocol. By activating a subscription tier, you explicitly authorize Nimbus and our third-party integrated payment gateways (such as Zota, Praxis Tech, PayRetailers) to automatically charge the designated payment method on file on the exact calendar day marking the conclusion of the current billing cycle.
Users retain the functional ability to cancel recurring subscription configurations at any time. To prevent the execution of the subsequent automated renewal billing trigger, cancellation instructions must be successfully inputted through the centralized billing portal dashboard no less than twenty-four (24) hours prior to the established renewal timestamp. Cancellation actions purely halt future billing cycles; they do not trigger retrospective financial reversals.
Upon successful verification of transaction authorization and settlement confirmation by our upstream payment orchestration gateways, the Nimbus backend database instantly triggers the provisioning sequence. System access credits, virtual lesson token matrices, and sub-agent database allocation codes are dispatched via real-time automated scripts to the User's operational profile. The successful recording of this digital credit allocation within the database ledger constitutes the absolute execution of product delivery and contract fulfillment by Nimbus.
Users and Regional Distribution Partners bear the absolute, non-transferable obligation to maintain valid, authorized, and functional payment parameters (such as verified international corporate credit cards, pre-approved bank routing links, or legitimate digital settlement channels) tethered to their billing profiles. Nimbus assumes no liability for network failures, regional routing errors, or payment failures stemming from card expiration, lack of local funds, or localized banking security blocks.
In the event that our automated billing engines fail to secure payment settlement on the scheduled renewal date, the system will mark the account as Delinquent. Nimbus reserves the immediate right to freeze administrative dashboard access, suspend sub-agent API access nodes, and lock all residual token creation mechanisms until the outstanding balance is satisfied.
All transactions are calculated based on the currency parameters explicitly chosen during checkout. Because Nimbus interfaces with diverse cross-border payment orchestration platforms, your localized banking institution or card issuer may apply localized foreign transaction conversion surcharges, market liquidity spreads, or processing fees. You acknowledge that Nimbus is entirely independent of these third-party banking markdowns and that all such localized financial conversion frictions shall be borne exclusively by the User.