Subscription Billing Orchestration

Method: applicability review. The supplied MSA documents a comparable SaaS contract, not legal authorization for our launch. It states: “USE OF THE SERVICE IS NOT A GUARANTEE OF COMPLIANCE WITH APPLICABLE LAW.” No applicable federal legal basis or complete launch conditions are supplied. State-dependent registration, tax, privacy and subscription requirements remain unresolved because no state is selected. The proposed non-custodial role does not itself establish lawfulness.

The evidence does not establish legal eligibility in our applicable jurisdictions.

Method: operating-design assessment corroborated by the comparable's SaaS access and technical-support provisions. Our proposed subscription scheduling, invoice generation and processor-account integrations deliver digital results without our own physical operations. This design-level judgment assumes customer onboarding and support are also provided remotely; it does not establish implementation readiness.

The proposed service is digital, but our support and onboarding processes are not yet documented.

Method: licensing-applicability review. Our proposed role excludes custody, lending and guarantees, but no supplied legal authority establishes that this role requires no special licence before the first customer. No external processor or partner permissions have been verified. Zuora's third-party and PCI provisions do not determine our licensing status. Applicable state requirements remain unknown without a selected state.

Neither jurisdiction-specific licensing analysis nor partner eligibility evidence is supplied.

Method: contractual mechanism comparison. MSA sections 6.1(b) and 8.1 document annual renewal, advance annual service fees and additional usage-based fees. This supports an applicable recurring mechanism for our proposed prepaid platform subscription plus metered billing-event charges. The judgment assumes we implement those proposed recurring charges; it does not assert that our pricing or customer contracts already exist.

The comparable contract explicitly documents both subscription and usage-based recurring monetization.

Method: proposed money-flow and obligation analysis, with the MSA used only as a software-fee comparison. Our design collects prepaid service fees while customers' proceeds settle through an external operator; we do not lend or guarantee payment. Generating customer invoices does not make us the creditor for those invoices. This judgment assumes no advances, payment guarantees or processor-loss obligations are added. Zuora's own receivables and collection terms are not transferred to us.

The proposed boundaries clearly exclude credit provision, but our processor and customer contracts are not supplied.

Method: proposed obligation classification against the comparable software-service contract. Our product provides scheduling and invoicing, and the supplied operating boundaries explicitly exclude insurance. Assuming we do not add insured-event benefits or risk underwriting, we accept no insurance risk. The comparable's service warranties and indemnities are not evidence that our proposal conducts insurance.

The defined product and explicit operating boundary exclude insurance; this is a design assessment, not a licensing conclusion.

Method: proposed funds-flow tracing. Customer-owned processor accounts receive settlement directly through an external operator; our platform generates invoices and charges its own service fees without holding customer proceeds. The MSA's distinction between service fees and financial account data provides context, not proof of either company's settlement flow. The judgment assumes the implementation preserves direct settlement and introduces no pooled balances or custody.

The proposed flow explicitly excludes custody, but processor agreements and implementation evidence are absent.

Method: activity classification. Our proposed product translates subscription terms and usage into invoices, rather than trading assets. The comparable describes its software scope as “From pricing and packaging, to billing, payments and revenue accounting”. Assuming our launch remains within the stated billing scope, trading is not its core activity. The acquisition of Zuora is a corporate transaction, not evidence that our product is trading.

The proposed customer job and the comparable's documented billing category clearly distinguish this service from trading.

Method: buyer-and-function assessment. Our baseline targets businesses selling recurring services and explicitly excludes performing a state service; it does not depend on government procurement. The comparable documents a business software market with named corporate customers. This judgment assumes our initial sales strategy follows the stated business-buyer baseline, rather than making government contracts its foundation.

The proposed function and buyer are explicit, and the comparable supports the commercial software category.

Method: documented valuation comparison. Zuora's October 17, 2024 announcement reports a definitive acquisition agreement “in a transaction valued at $1.7 billion.” Calculation: $1,700 million exceeds the $300 million threshold. Its documented billing and subscription monetization activities make it a relevant, though broader, comparable. This is an announced transaction valuation, not proof of completion or a standalone valuation of Zuora Billing.

The company announcement explicitly supplies a qualifying transaction value and describes relevant billing activities.