A restaurant owner orders avocado toast and gets a slice of burnt bread. Then the bill arrives with extra charges they didn't order, a fee nobody explained, and a cancellation policy that makes leaving the table expensive.

That's a pretty good way to lose a customer. It's also a useful way to understand the allegations at the center of a new lawsuit against Toast.

On October 29, 2026, the Federal Trade Commission, joined by state and local government plaintiffs, sued Toast and affiliated companies, alleging hidden and unauthorized fees, unwanted subscription add-ons, misleading pricing, difficult cancellation procedures, and support that didn't live up to advertised promises. The case is pending. These are allegations, not court findings. Toast disputes them and says it intends to defend its business.

The most important lesson for ISVs isn't whether a particular fee turns out to be lawful. It's what happens when a platform treats fee extraction and exit friction as substitutes for earning the customer's next renewal.

The fee the restaurant didn't order

Start with the allegation that should make every vertical SaaS operator uncomfortable: restaurants allegedly discovered subscription add-ons on their bills that they hadn't agreed to buy.

The FTC's announcement says customers complained of being enrolled in and charged for extra services without consent. Think about what that means in a restaurant. The owner might be managing food costs, staffing, payroll, vendors, delivery platforms, and thin operating margins. The technology bill is supposed to be predictable. Instead, someone has to stop what they're doing and audit the software provider.

That is more than a billing dispute. It's a reversal of the relationship. The vendor that was hired to simplify operations has become another operational problem.

There's nothing inherently wrong with selling payroll, scheduling, marketing, or other add-ons. A restaurant might benefit enormously from having those tools inside one platform. But the value proposition depends on an actual choice. A customer who sees an itemized offer, understands the price, and agrees to it is a customer buying a product. A customer who discovers a mystery line item later is a customer wondering what else is on the bill.

And once that question starts, it doesn't stay limited to the add-on.

The 99-cent fee wasn't really about 99 cents

The lawsuit also challenges a $0.99 fee Toast allegedly added to certain online orders over $10 between September 2021 and late July 2023. According to the FTC, the fee went to Toast rather than the restaurant and was imposed without adequate disclosure or consent from restaurant customers or the restaurants themselves.

The dollar amount sounds small. That's what makes the example so revealing.

A diner sees a higher total on the restaurant's checkout page. Who do they blame? Usually the restaurant whose name is on the order. The software provider may be collecting the fee, but the merchant is the one explaining the bill to the customer standing at the counter.

This is the hidden cost of fee decisions made upstream: the merchant can inherit the reputational damage downstream.

A platform that monetizes an interaction should be able to answer three basic questions. Who agreed to the charge? Who receives the money? And who has to explain it when a customer complains? If those answers point in different directions, the pricing design deserves another look.

To be clear, the allegations about disclosure and consent are being litigated. But the product-design lesson doesn't require a verdict. If a merchant is surprised by how its provider charges its customers, that's already a bad conversation.

A zero-dollar headline can still carry a real price

The complaint also challenges how Toast presented a 'Pay-as-you-Go' offering with hardware and software advertised at $0 per month while processing carried higher transaction fees. The regulators allege important conditions and additional costs weren't adequately disclosed.

Among the examples in the FTC release: customers who didn't begin processing within 120 days allegedly faced returning hardware or paying its retail value; temporarily closed restaurants allegedly still owed an $85 monthly processing charge; and some customers allegedly faced early termination fees calculated at $150 per remaining contract month.

None of this means a low-upfront-cost model is automatically suspect. Financing hardware through transaction economics can be a perfectly reasonable commercial arrangement. So can a minimum commitment when it's clearly negotiated and understood.

The issue is the gap between the headline price and the customer's realistic total obligation.

For an ISV, 'free' is a powerful acquisition message. But if the merchant later feels the terms were buried, the acquisition win can become a retention liability. The price wasn't actually cheaper; it was just harder to understand.

And complexity has a cost. It drives billing tickets, escalations, angry online reviews, sales friction, and disputes over what the contract says. Those costs don't always appear in the pricing team's spreadsheet.

Charging someone to stay isn't retention

The lawsuit's cancellation allegations bring the strategy into focus. Regulators allege Toast used a difficult, multi-team process, a 30-day written nonrenewal notice requirement that wasn't clearly presented during enrollment, and substantial early termination charges in some cases. The FTC describes a customer complaint involving a $5,318.87 termination fee after four years.

The complaint further alleges that some restaurants with outstanding Toast Capital loans could face immediate repayment of their loan balance if they canceled their subscription or switched providers.

Again, these are allegations. Contract terms, financing covenants, and termination fees need to be evaluated in context. Toast contests the government's account.

But from a merchant-strategy perspective, the distinction is worth making: there is a difference between a customer who chooses to stay and a customer who calculates that leaving would hurt too much.

A high switching cost can make a platform look sticky. It can also conceal a relationship that's deteriorating. If customers keep paying only because they can't untangle their software, payment acceptance, hardware, and financing, renewal rates stop telling the whole story.

That matters to founders and investors. A platform's revenue quality depends not just on whether the revenue repeats, but on why it repeats.

The economics of a resentful customer

Here's a hypothetical example, not a claim about Toast.

An ISV adds $40 per month in fees across 1,000 merchant accounts. On paper, that's $480,000 in annualized incremental billing. Nice line on a forecast.

Now imagine that the surprise charges create enough distrust that more merchants request audits, escalate support cases, negotiate credits, or reconsider their processor at renewal. A merchant who once recommended the platform starts warning other operators to check every line of the contract.

The immediate fee revenue is easy to count. The damage to trust, referral flow, and future expansion sales is harder to isolate. That doesn't make it free.

The best SaaS monetization creates a customer who says, 'This product is worth more than I'm paying.' The worst creates one who says, 'I don't know what I'm paying, and I don't know how to stop.'

Those are very different businesses, even if this quarter's revenue chart looks similar.

How to avoid building the same problem

For an ISV or payments provider, the response shouldn't be to eliminate every fee. It's to make the fee model defensible from the customer's point of view.

First, make consent observable. When a merchant enables an add-on, record who enabled it, what price was shown, when billing starts, and what happens when the feature is disabled. That record protects the merchant experience and helps the support team resolve questions without a scavenger hunt.

Second, make the bill explain itself. Separate software subscriptions, processing charges, optional services, hardware obligations, and third-party pass-throughs. Don't make merchants reverse-engineer a bundled invoice to understand why their costs changed.

Third, review the entire checkout experience when a platform adds a diner-facing charge. A merchant shouldn't discover a new customer fee because its regulars start asking questions.

Fourth, treat cancellation as a product flow, not a defensive sales campaign. Explain the notice period, any remaining contractual obligations, hardware return requirements, and financing consequences before a merchant signs. When someone asks to leave, give them a clear, documented path.

Finally, measure the right retention signals. Don't stop at churn. Track billing complaints, disputed charges, credit requests, time to resolve cancellations, and the share of merchants who renew after receiving a transparent explanation of their options.

A renewal achieved through satisfaction is different from one achieved through confusion. The dashboard should help you tell them apart.

Toast's response matters, too

The lawsuit is not a verdict. In a statement reported by Restaurant Business, Toast said it strongly disagrees with the allegations, argued that the FTC overlooked information about customers negotiating their contracts, and said it would defend the case. Toast also disputes the applicability of a federal subscription law to its business-to-business contracts.

Those defenses matter. Whether the specific practices violated the law is for the legal process to determine. An industry article shouldn't convert a complaint into a conviction.

Still, the questions raised by the case are fair questions for every embedded payments platform, regardless of the outcome: Do customers know what they're buying? Do they know what they'll pay? And do they understand what it costs to leave?

Sell better toast

The smartest retention strategy isn't to surprise merchants with another charge or make the exit door hard to find. It's to build a product that makes them reluctant to leave for the right reasons.

Charge for real value. Show the price. Get the authorization. Deliver the service. Make the relationship understandable.

Because if you charge avocado toast prices and deliver burnt toast, the problem isn't that customers don't appreciate your pricing strategy.

It's that they didn't order what showed up.

Want to get featured on the CentsChat podcast? Complete our survey.