At a London restaurant counter, the standard tech stack is a small museum: a card reader from one vendor, a point of sale from another, a reservations app on an iPad in the corner, and a marketing tool that nobody on the night shift remembers the password to. Zavo, a London fintech founded in 2025, wants the operator to throw most of that out and run the floor on one piece of software and one terminal [Zavo website, 2025].
The pitch is direct. Zavo "unifies payments, POS, reservations, AI, and marketing into one platform built for restaurants," according to its own site [Zavo website, 2025]. Card acceptance starts at 0.7 percent, with instant payouts and Tap to Pay alongside branded hardware including countertop terminals and handhelds [Zavo website, 2025]. Pricing is flat, payments come included, and modules for POS, reservations, AI, and marketing are added as the operator grows [Zavo website, 2025]. The company is explicit about what it is not: "Zavo is not a POS company. We are not a reservation company" [Zavo website, 2025]. The bet is that hospitality buyers want one vendor, one bill, and one support number.
The bet
The wedge is payments. Restaurants feel card fees on every transaction, and a quoted rate starting at 0.79 percent on Zavo's custom pricing page is aggressive against the headline rates most UK SMB acquirers advertise [Zavo website, 2025]. Once the terminal is on the counter and payouts are landing the same day, Zavo's plan is to sell upward into the rest of the operator's stack: table management, reservation flow, an AI layer over the point of sale, and outbound marketing. Crunchbase describes the product as "payments and point of sale powered by AI" [Crunchbase]. The Y Combinator listing goes further, calling it an "agentic point of sale for restaurants and retail" [Y Combinator, 2025].
That phrasing matters. Agentic POS implies software that does more than ring up a check: routing refunds, flagging anomalies, drafting marketing sends, reconciling end-of-day without a manager hunched over a spreadsheet. If Zavo can ship that and keep the payments rate competitive, the unit economics of a single restaurant relationship look very different from a pure acquirer's.
Why it could be big
The UK and European hospitality market has been a long, frustrating hunt for a unified operator stack. Square owns part of it, SumUp owns part of it, Toast has pushed into the UK, and a long tail of legacy POS vendors still runs on hardware older than the staff using it. None has cleanly stitched payments, reservations, and marketing into one subscription for an independent restaurant.
Y Combinator put Zavo through its F25 batch and is the named lead on the company's seed funding, with roughly $500,000 disclosed under the standard YC deal structure [Y Combinator, 2025; Y Combinator deal]. Pioneer Fund is also listed as an investor. The check size is modest by design; the signal is the batch and the network, which gives a London team early access to US benchmarks and operator introductions that UK seed rounds rarely include.
| Metric | Value |
|---|---|
| Disclosed seed (USD thousands) | 500 $K |
| Headline payments rate (bps) | 70 bps |
| Custom pricing rate (bps) | 79 bps |
The team and traction
Zavo was founded by Can Zehebi and Ilkan Gezer, both listed as Zavo (YC F25) on LinkedIn [LinkedIn; LinkedIn]. Zehebi announced the YC batch in September 2025 [LinkedIn, 2025]. The company operates as Zavo LTD, UK company number 14543620, out of London [Zavo website, 2025], and sells its own hardware line direct to restaurants [Zavo website, 2025]. On Trustpilot, customers "consistently praise the user experience, finding the system easy to use and efficient for managing payments, even during busy periods" [Trustpilot]. More recent reviews note appreciation for "the simplicity and speed of the system" [Trustpilot, 2026].
The same review channel surfaces the friction. Some merchants have reported "issues with communication and delays in payouts due to account flagging for suspicious transactions" [Trustpilot, 2026]. For a payments business courting restaurants that live on daily cash flow, payout reliability is the product. It is the single operational metric Zavo will be judged on as volume scales.
What the bears say, what the bulls answer
The bear case is competitive density. UK SMB payments is a crowded category, and a seed-stage entrant going head-to-head on rate against SumUp, Square, and Stripe-powered resellers has to defend margin while it builds the rest of the stack. The bull answer, supported by Zavo's own positioning, is that the company is not selling payments in isolation [Zavo website, 2025]. It is selling a hospitality operating system where payments are the on-ramp and the AI-driven POS, reservations, and marketing modules are the retention story. If a restaurant runs its floor, its bookings, and its email list on Zavo, switching costs look very different from swapping a card reader.
What to watch
Three things over the next twelve months. First, a priced seed extension or Series A: YC F25 companies typically raise on Demo Day momentum, and a lead beyond Pioneer Fund would mark outside validation of the agentic POS thesis. Second, the rollout cadence on the non-payments modules. Reservations and marketing have been named on the website [Zavo website, 2025]; shipped, dated launches with named restaurant customers would move the story from pitch deck to platform. Third, payout reliability. Zavo's Trustpilot signal is mostly positive, but the flagged-account complaints [Trustpilot, 2026] are the kind of issue that compounds quickly at scale. A public service-level commitment, or a named risk and compliance hire, would tell the market the company is taking it seriously.
The broader question for readers: in a category where every incumbent is now bolting AI onto an existing POS, can a London seed-stage team define the operating system for European hospitality before the incumbents copy the bundle?