Latest / Vertical SaaS with Fexingo: Industry-Specific Software for Healthcare, Construction, Legal / How Vertical SaaS Is Embedding Payments Into Software
Transcript
- Lucas: So we've talked a lot on this show about how vertical SaaS companies are embedding financial services into their software — banking, insurance, equipment financing. But there's one layer that's becoming maybe the most profitable of all, and it's the one most customers never think about. Luna: Embedded payments. Lucas: Exactly. The software itself becomes the point of sale system. And the company takes a small cut of every transaction that flows through it. It sounds simple, but the numbers are staggering once you look at companies like Toast. Luna: Toast is the restaurant management platform, right? Point of sale, payroll, inventory. Lucas: Right. And in their most recent full year, 2025, Toast processed over $126 billion in total payment volume. That's not revenue — that's the dollar value of all the transactions that went through their system. Their cut of that was roughly $1.8 billion in payment processing fees alone. Luna: That's more than their software subscription revenue, isn't it? Lucas: Significantly more. Toast's subscription revenue was about $500 million that year. So payments are roughly three-quarters of their total revenue. And the margin on those fees is actually better than on software, because the incremental cost of processing an extra dollar is very low once the infrastructure is built. Luna: But here's what I wonder: restaurants are famously low-margin businesses. Why are they okay with paying Toast roughly 2.5 percent on every credit card transaction? They could use a standard processor like Stripe or Square for less. Lucas: That's the key question. And the answer is that Toast isn't really competing on price. It's competing on integration. When you use Toast's payments, every transaction automatically updates your inventory, your sales reports, your labor cost calculations, your tax records. If you use a separate processor, you're either manually reconciling or paying for middleware to connect the two. Luna: So the value is in the data flow, not the processing itself. Lucas: Exactly. And that's the thesis behind embedded payments across vertical SaaS. The software vendor becomes the merchant of record. They handle the PCI compliance, the chargeback management, the settlement. The restaurant owner gets one monthly bill instead of three. And the software company gets a revenue stream that grows with their customer's transaction volume, not just with seat count. Luna: So it's a natural hedge. If the restaurant does well, Toast does well. If they have a slow month, Toast's payment revenue dips too. Lucas: Right. It aligns incentives in a way that pure subscription fees don't. And that's why you're seeing this model spread beyond restaurants. Mindbody in fitness and wellness, for example — they process payments for yoga studios and gyms. Weave for dental practices. Clio for legal. They all have payment processing built in. Luna: But there's a tension here. The SaaS company has an incentive to keep payment processing inside its walled garden. If a customer wants to shop around for a cheaper processor, the software might make that difficult or expensive. Lucas: That's a real concern. And some regulators are starting to look at it. The Consumer Financial Protection Bureau in the US has flagged what they call 'digital payment platforms' that bundle processing with software. The worry is that it reduces competition and ultimately raises costs for small businesses. Luna: But isn't there also a ceiling? At some point, the payment processing market is commoditized. Square and Stripe have been competing on price for years. Can Toast really sustain a 2.5 percent take rate? Lucas: They might not have to sustain that exact number. What matters is the spread — the difference between what they charge merchants and what it costs them to process. Toast negotiates with card networks and acquirers at scale. Their cost of processing is likely well under 2 percent. So even if they lower their rate to 2.2 percent, they're still making good margin. And the switching cost for the restaurant is enormous — you'd have to retrain staff, change hardware, reconcile data. Most owners won't bother for a few basis points. Luna: So the moat is not the payment tech. It's the software itself. Lucas: Exactly. And that's why vertical SaaS companies are in such a strong position. They own the workflow. Payments are just a feature of that workflow. And as long as they keep the software indispensable, the payment revenue will keep flowing. Luna: But there's a risk on the other side too. If the software company has a data breach or a service outage, it doesn't just affect their software — it affects their customers' ability to get paid. Lucas: That's a huge operational risk. Toast had a major outage in 2023 that left some restaurants unable to process payments for hours. That's existential for a restaurant on a Friday night. So the stakes are higher. But for the software company, the payoff is also higher. You're not just a cost center anymore — you're the financial backbone of the business. Luna: Let's talk about the economics for a smaller vertical SaaS company. If I'm building software for, say, independent hardware stores, can I realistically build a payment processing layer? Lucas: You can, but you probably shouldn't build it from scratch. The smart play is to partner with a payments infrastructure provider like Stripe or Adyen. They handle the regulatory and technical complexity. You white-label the experience, take a revenue share. Typically the SaaS company gets 20 to 30 percent of the processing margin. For a small platform with a few hundred merchants, that might mean a few thousand dollars a month. But as you scale, it becomes meaningful. Luna: So it's a volume game. You need enough transaction flow to make the integration worthwhile. Lucas: Right. And that's why you see this mostly in verticals with high transaction frequency — restaurants, retail, healthcare, fitness. Low-frequency industries like property management or construction have less payment volume per user, so the economics are thinner. But even there, some platforms are finding ways. Luna: One angle I find interesting is how embedded payments change the software company's relationship with its customers. Suddenly you're not just a tool provider — you're a financial partner. That gives you a different kind of data and a different kind of leverage. Lucas: It also gives you a different kind of responsibility. When you process payments, you see exactly how much revenue your customers are generating. You can use that data to offer them loans or working capital — which we've talked about on the show before. But it also means you know when they're struggling. If a restaurant's transaction volume drops 30 percent month over month, you see that before the owner even calls you. Luna: That's both a risk and an opportunity. You could proactively offer help, or you could end up with a portfolio of bad loans if you're not careful. Lucas: And that's where the line between software and finance gets blurry. Some of these companies end up looking more like banks than software vendors. The market has rewarded that — Toast trades at a higher revenue multiple than traditional payment processors because investors see the software stickiness and the data moat. Luna: Is there a point where the payment revenue becomes so dominant that the software itself starts to feel like a loss leader? Lucas: It's already happening in some cases. I've talked to restaurant owners who say they chose Toast because the hardware was subsidized — they got tablets and printers for free or at cost. Toast makes that back in payment processing within a few months. So in effect, the software and hardware are sold at near zero margin to acquire the payment flow. That's a classic razor and blades model. Luna: Interesting. So the software is the razor, and the payment fees are the blades. Lucas: Exactly. And the blade has a recurring revenue component that grows with the customer's business. That's a beautiful model if you can make it work. The challenge is that it requires a critical mass of transaction volume to cover the upfront costs. And you need to be in a vertical where payment processing is frequent enough to generate meaningful revenue per user. Luna: So what verticals do you think are next? Where haven't we seen embedded payments take off yet? Lucas: I'd watch the trades — plumbing, electrical, HVAC. Those are service businesses where the transaction value is high but frequency is moderate. A few platforms are starting to embed payments into their field service management software. Also legal, which we mentioned — Clio is already doing it. And accounting and bookkeeping software, where payments have been surprisingly slow to integrate. Luna: Yeah, I'm surprised QuickBooks hasn't pushed harder into embedded payments. They have the installed base. Lucas: They do offer it — QuickBooks Payments — but it's not as seamlessly integrated as what Toast does. The user experience still feels a bit bolted on. And that's the lesson: embedded payments only work if they feel native to the workflow. If the user has to think about switching modes, you lose the friction advantage. Luna: So it's really about design as much as technology. Lucas: Absolutely. And that's why vertical SaaS companies have an edge over horizontal processors. They understand the specific workflow of the plumber or the dentist or the restaurant manager in a way that Stripe or Square doesn't. They can build the payment experience directly into the scheduling, invoicing, and inventory flows. That's hard to replicate from the outside. Luna: Before we wrap — I want to talk about the regulatory side for a second. If these companies start to look like payment processors, they'll face more oversight. Money transmission licenses, reserve requirements, audit obligations. Lucas: Right. And that's a significant barrier to entry. Getting a money transmitter license in all 50 US states can take years and millions of dollars in legal fees. That's one reason many vertical SaaS companies partner with a licensed processor rather than becoming one themselves. But as they scale, some choose to get licensed directly to capture more margin. Toast actually holds its own licenses in most states now. That's a moat in itself — the regulatory complexity keeps competitors out. Luna: So the winners in vertical SaaS embedded payments will be the ones who can navigate both software and financial regulation. That's a rare combination. Lucas: It is. And it means the window for new entrants is narrowing. The incumbents have the data, the licenses, and the integration depth. But there's still room for niche players in underserved verticals — maybe specialty food, pet services, or even funeral homes. That's where I'd look. Luna: It's fascinating how something as mundane as paying a bill becomes a strategic lever for software companies. If these conversations are useful for what you're building or running, and you want to help keep this show ad-free and independent, you can support us at buy me a coffee dot com slash fexingo. No pressure, just a way to keep the conversations going. Lucas: Appreciate that. And on that note — the next time you swipe your card at a restaurant, just remember: the software company that made your server's tablet is probably making more off that swipe than the restaurant is. Luna: That's a sobering thought for restaurant owners. But for software builders, it's a reminder that the real value isn't in the code — it's in the transaction. Lucas: Well said. Thanks, Luna. Luna: Thanks, Lucas.