FTC Toast lawsuit (29 Oct 2026): 9 cancel-flow fixes for fintech SaaS

ROSCA's three duties mapped to the Toast allegations: disclose every fee before billing, get express consent, and let customers cancel as easily as they joined.

Read time
17 min
Word count
2.7K
Sections
12
FAQs
8
Share
Two colleagues at a worktable sketch a subscription cancellation flow beside a tablet, a card terminal and a small US flag
On this page · 12 sections
  1. What the FTC and the states filed on 29 October 2026
  2. The allegations, one by one
  3. What ROSCA actually requires
  4. The B2B question: does ROSCA protect restaurants?
  5. Why this lands without a click-to-cancel rule
  6. The nine cancel-flow fixes
  7. A self-audit you can run this week
  8. India-specific considerations
  9. US, UK and India compared
  10. What to watch next
  11. How eCorpIT can help
  12. References

Summary. On 29 October 2026 the Federal Trade Commission, the People of California and seven state Attorneys General sued Toast, the restaurant point-of-sale and payments company, in the Northern District of California (case 3:26-cv-12705), under the FTC Act and the Restore Online Shoppers' Confidence Act (ROSCA). The Commission voted 2-0. The plaintiffs allege add-ons charged without consent; a Pay-as-you-Go plan with poorly disclosed costs, including $85 a month in processing during temporary closures and an early termination fee of $150 for each remaining month; a $0.99 fee added to some online orders over $10 from September 2021 to late July 2023; cancellation that needs 30 days' written notice; Toast Capital loans treated as in default when a customer leaves; and false round-the-clock support claims. These are allegations, not findings: the case is pending. Toast says, as reported, that it strongly disagrees and that ROSCA has not been applied to negotiated business contracts. ROSCA has three duties: disclose all material terms before taking billing details, get express informed consent, and offer a simple way to stop charges. Our verdict: audit checkout, add-on consent and cancellation against those three duties this quarter, starting with any flow where signing up is online but cancelling is not.

About this article. This is for product, engineering, billing and compliance leads at fintech, payments and subscription SaaS companies selling to US, UK and Indian customers, including small businesses. On 22 November 2026 we checked the FTC press release, the filed complaint and the FTC case page, the ROSCA text, the Eighth Circuit's 2025 opinion, two 2026 Federal Register documents, the FTC's 2025 Amazon settlement, the RBI's 2026 e-mandate directions and India's 2023 dark patterns guidelines. The FTC and Toast sites refused automated requests, so we read the FTC pages through archived copies and rely on two trade publications for Toast's response. Everything said about Toast's conduct is an allegation. This is general information, not legal advice, and no vendor paid for inclusion. Researched with AI assistance and checked against the primary sources listed in the references.

What the FTC and the states filed on 29 October 2026

The plaintiffs are the FTC; the People of the State of California, acting through the Los Angeles County Counsel and the San Francisco City Attorney; and the Attorneys General of Colorado, Florida, Illinois, Iowa, Nebraska, Oklahoma and Utah. American Banker counts eight states (California plus seven), while Digital Transactions counts seven attorneys general; both describe the same filing.

The defendants are Toast, Inc. and five affiliates: Toast Capital LLC, Toast Processing Services, LLC, Stratex Holdco, LLC, Strategy Execution Partners LLC and Xtra Chef, LLC. The FTC file number is 252 3101, and the case page lists the matter as pending.

The complaint runs to 71 pages and 22 counts (the numbering ends at XXI because Count XI is used twice). The FTC's own counts allege misrepresentation of $0 hardware, misrepresentation of 24/7/365 support, and unfair charging of fees without consent under Section 5 of the FTC Act. All plaintiffs then bring three ROSCA counts: failure to disclose material terms, failure to obtain express informed consent, and failure to provide simple mechanisms to stop recurring charges. The rest are state consumer protection claims. The plaintiffs ask for a permanent injunction, monetary relief, and state civil penalties, restitution and costs.

The complaint says Toast customers span 156,000 locations globally and that Toast reported revenue of $6.153 billion in fiscal 2025, up from $4.960 billion in 2024 and $3.865 billion in 2023. Toast's response, as reported, puts its footprint at almost 200,000 business locations.

The allegations, one by one

Each allegation maps to a product decision many fintech and SaaS companies make. The table below summarises the press release and complaint; every item is a claim by the plaintiffs, not a court finding.

Allegation What the plaintiffs say happened The product decision behind it
Add-ons without consent Customers were enrolled in, and billed for, add-ons such as timekeeping, payroll and payroll tax filing without agreeing Bundling and upsell defaults at checkout and renewal
$0 hardware claim Pay-as-you-Go was sold as $0 a month for hardware and software, with costs elsewhere Headline price versus full fee schedule
120-day activation rule Customers who did not start processing within 120 days had to return hardware or pay full retail value Conditional fees buried in terms
Closure fee Restaurants that closed temporarily still paid $85 a month for processing Minimum-fee clauses during inactivity
Early termination fee An undisclosed $150 a month for each remaining month of the contract Termination fee formula and disclosure
$0.99 order fee Added to some online orders over $10, September 2021 to late July 2023, kept by Toast Fees charged to the merchant's own customers
30-day written notice Customers had to give written notice of intent not to renew at least 30 days before term end Offline-only cancellation for an online sign-up
Retention gauntlet Cancelling customers were sent to phone or chat and pitched to stay Save flows and retention offers
Loan acceleration Cancelling or switching provider was treated as default on a Toast Capital loan Cross-default between lending and subscription
24/7/365 support Some teams, including cancellations and Toast Capital, worked limited hours Marketing claims versus staffing

Two details matter for designers. First, the 30-day notice rule allegedly sat in Section 8.1 of the Merchant Agreement, on page 11 of 25, inside a dense 17-line paragraph, behind a link customers did not have to open during sign-up. Second, the press release cites one customer charged an early termination fee of $5,318.87 after four years, which Toast refused to refund.

The lending point is new territory for many SaaS teams. The complaint says Toast launched Toast Capital in 2019, that loan holders may not change point-of-sale provider without Toast Capital's permission, and that cancelling or switching counts as an event of default, a term it says is not disclosed during the loan application. The agencies' theory is that a loan can work as a cancellation barrier, because leaving means repaying the whole balance at once.

What ROSCA actually requires

ROSCA, at 15 U.S.C. § 8403, makes it unlawful to charge for goods or services sold online through a negative option feature unless the seller does three things.

  1. Before taking billing information, it shows text that clearly and conspicuously discloses all material terms.
  1. Before charging a card, bank account or other financial account, it obtains the customer's express informed consent.
  1. It provides simple mechanisms to stop recurring charges.

A negative option feature, under the Telemarketing Sales Rule definition the complaint cites, is a term under which the customer's silence or failure to act is treated as acceptance. An auto-renewing annual subscription billed monthly fits. Under Section 5 of ROSCA a violation is treated as a violation of an FTC trade regulation rule, which opens the door to civil penalties and money for customers.

The statute does not list button sizes or click counts. Regulators judge the whole flow: could a customer find the full cost before handing over a card, was each charge clearly agreed, and was stopping simple?

The B2B question: does ROSCA protect restaurants?

ROSCA's text speaks of consumers. Toast's defence, as reported by Digital Transactions, is that courts have not applied ROSCA to negotiated business-to-business deals and that it does not believe the law applies here. Toast also says it has cooperated with the investigation since mid-2025 and that the FTC ignored evidence of how much its customers negotiate their contracts. American Banker reported that Toast said it would defend itself vigorously.

The plaintiffs take the other view: the complaint brings all three ROSCA counts on behalf of every plaintiff against a company whose customers are restaurants. No court has ruled on that question in this case, and we draw no conclusion on who is right.

For builders, the safer reading is simple. If your small-business customers sign up through a self-serve web checkout with a card, the flow looks like the online transactions ROSCA describes, whatever the customer's legal form. A negotiated enterprise contract signed after a sales process looks different. Many fintech SaaS companies run both on the same billing system, and the self-serve path is where the risk sits.

The UK draws this line explicitly. Its subscription regime under the Digital Markets, Competition and Consumers Act 2024 covers consumer contracts only, and the draft guidance excludes business-to-business subscriptions; see our UK subscription contracts checklist for the planned 1 January 2027 build list.

Why this lands without a click-to-cancel rule

Many teams relaxed in July 2025. On 8 July 2025 the Eighth Circuit vacated the FTC's 2024 click-to-cancel amendments to the Negative Option Rule in full, because the FTC had skipped a required preliminary regulatory analysis, six days before the delayed 14 July 2025 compliance date. On 12 February 2026 the FTC formally restored the rule's earlier text to match that decision. On 13 March 2026 it published an advance notice of proposed rulemaking asking whether to start again, with comments due by 13 April 2026. We found no proposed rule since.

None of this removed the risk. ROSCA is a statute, not a rule, so the vacatur did not touch it. The FTC used ROSCA against Amazon over Prime enrolment and cancellation, and on 25 September 2025 announced a $2.5 billion settlement: a $1 billion civil penalty and $1.5 billion in refunds, with required changes to the Prime sign-up and cancel flows. The FTC said it was only the third ROSCA case in which it had obtained a civil penalty. The Toast filing takes the same law to a fintech selling to small businesses, alongside state consumer protection claims.

The nine cancel-flow fixes

These fixes come from reading ROSCA's three duties against each allegation. They are engineering and product controls, not a legal safe harbour.

1. Show the full fee schedule before the card field

Put every recurring charge, conditional fee and minimum on the screen before you ask for billing details: monthly price, term length, renewal rule, processing rates, minimum or inactivity fees, hardware conditions and the termination formula. The complaint's 120-day hardware rule and $85 closure fee are the kind of terms that belong here, not in a linked agreement.

2. One unticked consent per paid add-on

Each add-on gets its own unticked control, its own price line and its own consent record. Never pre-select add-ons, and never add them at renewal without a fresh opt-in. Store who agreed, to what price, on which screen version and when.

3. Cancel the way they joined

If a customer can sign up online, give them an online cancel path of comparable effort. A written-notice-only rule for an online sign-up is the core of the cancellation allegation. Email or letter can remain an extra channel, not the only one.

4. Put the non-renewal deadline in the product

If a notice period applies, show the exact date on the account and billing pages, and send a reminder before it. A date the customer has to work out from Section 8.1 of a contract is not a disclosure.

5. Price the exit before the customer confirms it

If you charge an early termination fee, show the formula at sign-up with a worked example, and the exact amount on the cancel screen before the final confirm. On the alleged terms, a customer leaving with 18 months left would owe 18 × $150 = $2,700, and three months of temporary closure would cost 3 × $85 = $255 in processing minimums. If those figures would surprise a customer at the end, show them at the start.

6. One retention offer, then let them go

A single, skippable save offer is common practice. Questioning about why they want to leave and repeated sales pitches over phone or chat are what the complaint describes as obstacles. Make the decline button as visible as the accept button.

7. Separate lending from subscription exits

If you offer embedded loans or cash advances, decide whether cancelling the software should ever affect the loan. If a cross-default stays, disclose it plainly in the loan application and again in the cancel flow, with the balance that would fall due. The complaint says the restriction was not disclosed at any point during the loan application.

8. Get merchant opt-in for fees charged to their customers

The $0.99 fee allegedly went to Toast, not the restaurants, and was added without adequate disclosure to or consent from patrons or restaurants. Any fee your platform adds to your merchants' end customers needs the merchant's explicit opt-in, a visible line item for the end customer, and a clear statement of who keeps it.

9. Make support claims match the rota

If you market round-the-clock support, staff every team a customer might need, including cancellations, lending and tax. The complaint says the cancellation and Toast Capital teams took calls only in limited business hours and the tax team had quarterly blackout periods. Otherwise, state the actual hours per team.

The evidence layer behind all nine

Each fix needs a log you can produce later: the price and terms text shown on each screen version, consent events per add-on, cancel requests with timestamps and outcomes, retention offers shown and declined, and fee calculations at exit. Regulators and courts test the flow a customer saw, so keep versioned rendered copies of checkout and cancel screens alongside the billing data.

A self-audit you can run this week

Run this on your own production flows, once as a new self-serve customer and once as a cancelling one.

Check Pass looks like Fail looks like
Fees before card Full schedule on the checkout screen Only a headline price and a terms link
Add-on consent Separate unticked boxes with prices Pre-ticked bundle or silent renewal add-ons
Cancel channel Online cancel of similar effort to sign-up Letter, email or phone only
Notice deadline Exact date shown and reminded Date derived from contract clauses
Exit fee Exact amount shown before confirm Fee appears on the next invoice
Retention One skippable offer Multiple pitches or forced agent contact
Lending link No cross-default, or disclosed twice Default triggered by cancelling, undisclosed
Pass-through fees Merchant opt-in and end-customer line item Platform fee added without either
Support claims Hours match each team's rota 24/7 claim with limited-hours teams
Evidence Versioned screens and consent logs No record of what the customer saw

India-specific considerations

Indian fintech and SaaS teams face two sets of rules that point the same way.

The Central Consumer Protection Authority notified the Guidelines for Prevention and Regulation of Dark Patterns on 30 November 2023 under section 18 of the Consumer Protection Act 2019. They define a subscription trap as making cancellation of a paid subscription impossible or long and complex, hiding the cancel option, forcing payment or auto-debit details for a free subscription, or making cancellation instructions ambiguous or cumbersome. They also list SaaS billing as a dark pattern, with illustrations including converting a free trial to paid without notice, silent recurring debits and charging for unused features. The guidelines protect consumers under that Act, so the B2B question arises in India too, but the illustrations read almost like a description of the Toast allegations.

The Reserve Bank of India's Digital Payments E-mandate Framework, 2026, issued on 21 April 2026, adds rules at the payment layer for recurring payments on cards, prepaid instruments and UPI. Recurring transactions up to ₹15,000 each may run without additional factor authentication, or up to ₹1,00,000 for insurance premiums, mutual fund subscriptions and credit card bills. The issuer must send a pre-debit notice at least 24 hours before each charge, with the merchant's name, amount, date and mandate reference, and must let the customer opt out of a transaction or the mandate. In practice an Indian customer can stop the money even when your cancel flow is hard to use, so a mandate withdrawal should trigger your own cancellation and dunning logic rather than a fight. Our RBI e-mandate engineering checklist covers the build detail, and our guide to app subscription billing in 2026 covers store-billed plans.

US, UK and India compared

The US column draws on ROSCA and the Toast filing, the UK column on our UK article, and the India column on the CCPA notification and RBI directions.

Question United States United Kingdom India
Main instrument ROSCA plus FTC Act Section 5 and state laws DMCCA 2024 subscription chapter and draft 2026 regulations Dark patterns guidelines 2023 and RBI e-mandate directions 2026
Status on 22 Nov 2026 In force; Toast case pending Planned for contracts from 1 Jan 2027, regulations still draft Both in force
Business customers Disputed in the Toast case Excluded by draft guidance Guidelines protect consumers; RBI rules cover all card, PPI and UPI e-mandates
Cancel duty Simple mechanism to stop charges Online exit without compulsory surveys No impossible, hidden or confusing cancellation
Payment-layer control Card and bank disputes Card and bank disputes 24-hour pre-debit notice and mandate opt-out

What to watch next

The FTC case page, in its latest archived copy (10 November 2026), lists only the complaint and shows the matter as pending. Watch for a motion to dismiss on the B2B question: a ruling either way would tell SaaS companies selling to small businesses how far ROSCA reaches. Also watch the FTC's negative option rulemaking, where any proposed rule would need a further notice after the March 2026 advance notice. For UK teams, the subscription regime is planned to start on 1 January 2027, subject to Parliament approving the draft regulations.

How eCorpIT can help

eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our fintech and payments app development service can review and rebuild checkout, add-on consent, cancellation and e-mandate flows, with the consent and screen-version logs described above. Talk to us at /contact-us/.

Last updated: 22 November 2026.

References

  1. FTC and States Take Action Against Toast Inc. over Hidden and Unauthorized Fees, Deceptive Subscription and Cancellation Practices and Other Unlawful Conduct, 29 October 2026 — Federal Trade Commission
  1. Complaint, FTC et al. v. Toast, Inc. et al., Case No. 3:26-cv-12705 (N.D. Cal.), filed 29 October 2026 — Federal Trade Commission
  1. Toast, Inc., FTC Matter 252 3101, case page — Federal Trade Commission
  1. Toast Responds to FTC Allegations Regarding Fees And Support, 30 October 2026 — Digital Transactions
  1. 15 U.S. Code § 8403, Negative option marketing on the Internet — Legal Information Institute, Cornell Law School
  1. Why the FTC and 8 states are suing payments fintech Toast, 30 October 2026 — American Banker
  1. Custom Communications, Inc. v. Federal Trade Commission, No. 24-3137, opinion filed 8 July 2025 — US Court of Appeals for the Eighth Circuit
  1. Revision of the Negative Option Rule, Withdrawal of the CARS Rule, Removal of the Non-Compete Rule To Conform These Rules to Federal Court Decisions, 12 February 2026 — Federal Register
  1. Rule Concerning the Use of Prenotification Negative Option Plans, advance notice of proposed rulemaking, 13 March 2026 — Federal Register
  1. FTC Secures Historic $2.5 Billion Settlement Against Amazon, 25 September 2025 — Federal Trade Commission
  1. Guidelines for Prevention and Regulation of Dark Patterns, 2023 (CCPA notification of 30 November 2023, reproduced) — TaxGuru
  1. Master Direction: Digital Payments, E-mandate Framework, 2026, 21 April 2026 — Reserve Bank of India

Frequently asked

Quick answers.

01 What did the FTC sue Toast for?
The FTC and state co-plaintiffs allege Toast charged add-ons without consent, hid fees on its Pay-as-you-Go plan, added a $0.99 fee to some online orders, required 30 days' written notice to cancel, treated cancelling as a loan default, and overstated round-the-clock support. These are allegations only; no court has decided them.
02 When and where was the Toast lawsuit filed?
It was filed on 29 October 2026 in the US District Court for the Northern District of California, as case 3:26-cv-12705. The Commission voted 2-0 to authorise it. Plaintiffs are the FTC, California through two local offices, and the Attorneys General of seven more states.
03 What is ROSCA?
The Restore Online Shoppers' Confidence Act of 2010 covers online sales with a negative option, such as auto-renewing subscriptions. A seller must clearly disclose all material terms before taking billing details, get express informed consent before charging, and provide a simple way to stop recurring charges. Violations can bring civil penalties.
04 Does ROSCA apply to business customers like restaurants?
That is disputed in this case. Toast argues, as reported, that courts have not applied ROSCA to negotiated business-to-business deals. The plaintiffs bring ROSCA claims anyway. Until a court rules, treat self-serve small-business sign-ups with card checkout as within reach, and take legal advice for your contracts.
05 Is the FTC click-to-cancel rule in force?
No. The Eighth Circuit vacated the 2024 amendments on 8 July 2025, and the FTC restored the earlier rule text in February 2026. It asked for comments on a new rulemaking by 13 April 2026, but no new rule exists. ROSCA itself was unaffected and is still enforced.
06 What should a fintech SaaS company fix first?
Start where sign-up is online but cancelling is not. Add an online cancel path, show the full fee schedule before the card field, make every paid add-on a separate unticked choice, and show any termination fee before the customer confirms. Then log what each customer saw and agreed to.
07 How do India's rules compare with the Toast allegations?
India's 2023 dark patterns guidelines name subscription traps and SaaS billing practices, such as silent recurring debits and hidden cancellation. The RBI's 2026 e-mandate framework requires a pre-debit notice at least 24 hours ahead and lets customers opt out of a debit or a mandate, which limits hard-to-cancel designs.
08 Has Toast responded to the lawsuit?
Yes. Trade press reported that Toast strongly disagrees with the allegations, will defend itself vigorously, and believes ROSCA does not apply to negotiated business contracts. It also said it had cooperated with the investigation since mid-2025. Toast's own site refused our automated requests, so we rely on those reports.

About the author

Manu Shukla

Founder & Director

Founder of eCorpIT. Hands-on engineer leading senior-only delivery for AI apps, custom software, and cloud systems for global clients.

Subscribe

One engineering note a week. No fluff, no spam.

Senior-architect playbooks on AI agents, mobile apps, cloud, security, data, and marketing — delivered every Wednesday.

Past the reading

Read enough. Let's build something.

A senior architect responds in 24 working hours with scope, indicative cost, and a timeline. NDA before any technical conversation.

Loading search…

Browse all guides