Read
6 minute read
November 19, 2026
6 minute read
If you sell software-as-a-service (“SaaS”) subscriptions to other businesses, whether through a website, click-through terms, or an e-signed order form, do not assume those sales practices fall outside the Federal Trade Commission’s (“FTC”) enforcement authority. The FTC has asserted claims under the Restore Online Shoppers’ Confidence Act (“ROSCA”), 15 U.S.C. § 8403, involving services sold to businesses. ROSCA uses the term “consumer,” and its application to particular B2B arrangements, especially negotiated commercial agreements, remains unsettled. Even where ROSCA does not apply, unfair or deceptive pricing, enrollment, billing, and cancellation practices may be challenged under Section 5 of the FTC Act, 15 U.S.C. § 45, or applicable state unfair and deceptive practices statutes. Some state automatic-renewal laws also cover business contracts.
How ROSCA Could Reach Your B2B Subscriptions
ROSCA applies to covered internet transactions with a “negative-option” feature, meaning the customer’s silence or failure to act is treated as acceptance of an offer or continued service, such as automatic renewal or a free trial that converts to a paid subscription. For those transactions, ROSCA requires sellers to:
- Clearly and conspicuously disclose all material transaction terms in writing before obtaining billing information.
- Obtain express informed consent before charging.
- Provide simple mechanisms to stop recurring charges.
Exposure can extend beyond contract damages. A ROSCA violation is treated as a violation of an FTC trade regulation rule. Civil penalties under that framework generally require actual knowledge, or knowledge implied from objective circumstances, that the conduct is unfair or deceptive and prohibited by the applicable requirement. The FTC may also seek refunds or other relief for resulting customer injury. State attorneys general may bring ROSCA claims for injunctive relief, subject to statutory limits, and may pursue penalties and restitution where authorized under their own consumer protection laws.
The five actions below combine recurring-billing safeguards with broader practices for aligning SaaS marketing, contracts, and operations. The following scenarios are illustrative; not every recommended measure is a ROSCA requirement or applies to every B2B transaction.
1. Make the Advertised Cost Match the Actual Cost
Risk scenario. A SaaS platform advertises a subscription price, but material pricing conditions are missing from the advertised offer. Customers who sign up:
- Discover that the advertised subscription price excludes a mandatory implementation package required to use the service.
- Learn that essential reporting or data-export functions are available only through a separately priced module, despite marketing that presents them as included.
- See a per-user monthly price in large type, but learn at checkout that the price requires an annual commitment billed upfront, and that month-to-month billing costs significantly more.
- Discover that the advertised price covers only one seat, workspace, or integration, a limitation not clearly disclosed alongside language describing the plan as “ideal for small teams.”
Actions to take. Clearly explain mandatory charges, how variable charges are calculated, and material pricing conditions alongside the advertised price:
- Conditions next to price. Disclose seat limits, usage caps, minimum spend, and other material conditions next to the advertised price. If a monthly price requires an annual commitment or upfront annual payment, state both prominently alongside that price.
- Qualify “free” precisely. If you offer a free tier or trial, distinguish what is free from paid usage, transaction, or required add-ons, and disclose those charges alongside the claim.
- Trial conversions. For trials that convert automatically, state when billing begins, the post-trial price, the billing frequency, and the cancellation deadline.
- Visibility. Make these key pricing disclosures readable on desktop and mobile screens, without requiring customers to open another document.
2. Make Support and Uptime Promises Match Delivery
Risk scenario. A SaaS provider advertises “99.99% uptime,” but its calculation excludes recurring outages affecting a core integration without explaining that limitation. The provider also promises an assigned customer success manager, but customers receive no assigned contact after onboarding.
Actions to take. Compare support and uptime claims across marketing, sales decks, order forms, and the service level agreement (“SLA”) with what you actually deliver. Distinguish the target time for responding to an initial support request from the target time for resolving the issue. For uptime claims, align the advertised percentage with the SLA’s measurement period, covered services, exclusions, and remedies. Do not rely on fine print to contradict a broader marketing promise.
3. Make Renewal Terms Clear and Renewal Bills Accurate
Risk scenario. A SaaS order form states that the subscription will not renew automatically, but the billing system applies the provider’s default automatic-renewal setting. At the end of the term, the customer receives an invoice for another year despite having agreed to a subscription that expires without automatic renewal.
Renewal pricing creates a separate risk. A first-year promotional discount expires, and the customer is billed at full list price even though the post-promotional price and timing of the increase were not clearly disclosed before enrollment or communicated before the nonrenewal deadline. Or a SaaS provider applies its then-current standard rate at renewal, resulting in an increase that exceeds the customer’s negotiated cap. Customers discover the increase only after the nonrenewal deadline has passed.
Automatic renewal clauses, nonrenewal deadlines, and early termination fees protect the provider only if they are enforceable. Some state laws impose disclosure and notice requirements on automatic renewal provisions, and their application to business contracts varies. The enforceability of an early termination fee also depends on governing law and how the fee operates. If it functions as agreed damages for breach, a fee disproportionate to anticipated or actual loss may be an unenforceable penalty, and the difficulty of estimating loss when the contract was made may also matter.
Actions to take. Put the initial term, renewal term, recurring charges, nonrenewal deadline, and any termination-fee formula next to the acceptance mechanism and in the order form. Present linked terms conspicuously and capture affirmative acceptance. Configure billing to follow each customer’s agreed renewal setting, including subscriptions that expire unless the parties affirmatively agree to renew. Ensure renewal billing reflects customer-specific pricing terms, including negotiated caps on increases, rather than defaulting to standard rates. Distinguish nonrenewal, which prevents the next term, from early termination of the current term. Send customers confirmation of the accepted terms and cancellation instructions that they can keep.
Make renewal and price-change notices accurate and consistent with the customer’s terms. As a practical safeguard, communicate the renewal price sufficiently before the nonrenewal deadline to allow an informed decision. Separately, satisfy applicable contractual and statutory requirements for notice timing, content, and delivery; “then-current pricing” language does not override those requirements.
4. Get Consent You Can Prove
Risk scenario. A platform allows any employee with a user account to activate a paid module, even though the customer’s agreement reserves purchasing authority to designated administrators. The platform bills the customer without obtaining approval from an authorized purchaser.
Actions to take. Obtain affirmative authorization for recurring billing and newly purchased add-ons; do not rely on pre-checked boxes. Preserve who accepted, when, and the terms and disclosures presented. For automatic tier changes, seat increases, usage charges, and overages, confirm whether the accepted pricing arrangement authorizes the charge or additional acceptance is needed. Provide notices required by the agreement or applicable law and use advance usage alerts to help customers avoid unexpected charges. Configure purchasing permissions to reflect the customer’s agreed approval process and record authorization from the appropriate purchaser.
5. Make Nonrenewal and Cancellation Easy to Complete
Risk scenario. A SaaS platform lets only the original account owner turn off automatic renewal. That employee leaves the customer's business. When the customer asks to transfer administrative rights, the platform requires identity documents and a signed authorization form, and support takes weeks to process them. By the time a replacement administrator gets access, the nonrenewal deadline has passed and the customer is billed for another term.
Actions to take. Provide a secure, timely process for an authorized replacement administrator to manage renewal and cancellation when the original account owner leaves. As a practical safeguard, provide an online way to submit cancellation or nonrenewal requests for subscriptions purchased online, and comply with any applicable online-cancellation requirements. ROSCA itself requires a simple mechanism to stop recurring charges, rather than expressly prescribing an online method.
Make clear which action the customer is taking. Confirm the effective date and any remaining enforceable contractual payment obligations. If cancellation triggers termination fees or other payment obligations, disclose those consequences at enrollment and again in the cancellation flow. Record when requests are received and promptly confirm their receipt and effective date. Test the process as a customer would.
Takeaways
Regardless of whether ROSCA applies to a particular transaction, the following safeguards help align the customer experience with the SaaS provider's disclosures and contractual commitments:
- Pricing claims that accurately explain fixed charges, variable charges, and material conditions.
- Support and uptime promises that match contractual commitments and operational capabilities.
- Renewal terms customers can readily find and retain, with notices and charges that reflect agreed pricing terms.
- Records showing authorization for recurring billing, add-ons, and applicable usage-based charges.
- Cancellation and nonrenewal processes that work as described, with clear effective dates and remaining payment obligations.
Before your next pricing change, contact me for a 30-minute walkthrough of your signup and cancellation flow. Bring your pricing page and standard order form. We will identify potential gaps, separate what the law requires from optional safeguards, and prioritize next steps.


