Ben Leventhal's $50M Crypto Rails: What Blackbird's Series B Reveals About Resy's Missing Piece

I was standing at the host stand of a 38-seat pasta place in Brooklyn last Thursday, watching the floor manager triage the 7:15 wave. She had three windows open on the iPad mounted behind the lectern. One was the reservation system, parsing names against a guest list. One was the loyalty CRM, which was supposed to flag VIPs but mostly flagged people whose emails had bounced. The third was the POS, which knew exactly what every one of these diners had ordered the last time they came in but didn’t know any of their names. Three apps. Three sources of truth. Three subscription line items on the owner’s monthly P&L. And the diner standing in front of her — the human being whose business actually pays for everything in the room — existed as a different ghost in each one of them.

I tell you this scene because today, Tuesday, April 8, Blackbird Labs announced a $50 million Series B led by Spark Capital, and the temptation in our beat is going to be to call it a crypto story. It’s not. It’s the story of that host stand. It’s the story of who, in 2025, gets to own the relationship with the person about to sit down for dinner.

Reporting on this round across TechCrunch, Fortune, and Restaurant Technology News leans, naturally, on the chain underneath the product. Blackbird runs on a blockchain. Coinbase Ventures and a16z crypto are on the cap table. There is a token. Fine. But the operator read — the one I think matters for anyone running a restaurant, building a POS, or sitting on a strategy team at a payments incumbent — is that the chain is the side door, and the front door is loyalty plus payments fused into a single consumer identity the restaurant actually owns. That’s the bet Spark wrote a $50 million check against. And the cap table is the tell.

Why this round isn’t about tokens

Spark Capital led. Spark is not a crypto fund. Spark led the Series A of Twitter, of Slack, of Discord, of Plaid. Spark writes checks into companies that bend a market by re-architecting the consumer relationship inside an existing industry. If you read Spark leading this round, and you read it as “Spark is bullish on blockchain payments for restaurants,” you are reading the wrong sentence on the page.

Read it instead as: Spark thinks the restaurant industry has a Plaid-shaped hole in it, and that the company that fills it will look more like an identity rail than a payment processor.

Now look at who came in alongside Spark. Coinbase Ventures and a16z crypto, sure — those are the chain bets, and they validate the underlying technology choice. Union Square Ventures, who have spent a decade investing in network effects above all else and who wrote checks into Etsy, Stripe, Duolingo. And — this is the one I’d circle in red on the press release — Amex Ventures.

Amex Ventures is sitting on the cap table of the company being built by the man who sold Resy to Amex in 2019. Either Amex is hedging its bet, or Amex believes the diner-identity layer is moving somewhere that Resy, even inside the Amex ecosystem, cannot follow. I would bet on the latter. The Amex Ventures check is the loudest signal in the round about what this company actually is.

The total raised to date is now $85 million. That’s a meaningful number because it puts Blackbird squarely in the band where vertical fintech contenders either start gaining real distribution (Toast at the equivalent stage) or stall out into a pilot product (every loyalty startup of the last decade you’ve already forgotten about). Spark led at a level that says: this is the round that has to convert.

The Eater → Resy → Blackbird arc

You don’t get to underwrite this round without underwriting Ben Leventhal, so it’s worth laying out the arc.

In 2005, Leventhal co-founded Eater. Eater was, for a decade, the dominant editorial brand in restaurants — the place that, before Instagram swallowed restaurant culture whole, told you what was opening, what was good, what mattered. The Eater era was the era in which restaurants became a content category. Leventhal sat at the center of the consumer-attention layer of dining.

In 2014, he co-founded Resy, the reservation platform. The Resy era was the era in which restaurants became a yield-management problem. Resy turned the host stand into a software product and the reservation slot into an inventory unit. American Express bought Resy in 2019 and tucked it into the cardholder benefits stack — the deal price was never disclosed, but the strategic logic was: Amex wants to own the dinner reservation as a touchpoint to its premium cardholder, and Resy was the cleanest way to do it.

Notice what’s missing from that arc. Eater owned attention. Resy owned the reservation. Neither owned the relationship after the diner sat down. Neither owned the check. Neither owned the loyalty loop. Neither owned the data the restaurant actually needed to run a hospitality business on. Resy could tell you who was sitting at table 12 at 8:00, but Resy couldn’t tell you what they ordered, what they tipped, whether they came back, or whether they brought friends. That data lived in the POS — and the POS, in 2025, is Toast or Square or, in fine dining, increasingly a constellation of Tock and SevenRooms and a half-dozen others trying to bolt loyalty onto top of an order-management stack.

Blackbird, read in this context, is Leventhal’s third act and the first one that tries to close the loop. The loyalty-plus-payments combination is not a feature decision. It’s the architectural answer to the question Eater and Resy together implicitly raised: if you own the consumer’s pre-meal intent (Eater) and the reservation (Resy), what would it take to also own the post-meal relationship? Answer: you have to own the payment, because the payment is the only event in the meal that the diner and the restaurant both reliably touch.

Here is Leventhal in his own words from today’s coverage, and I want to give it to you whole rather than chopped up:

“There is a disconnect in the restaurant industry between the popularity and the intensity of consumer love for restaurants and ultimately the profitability of the industry.”

Read that sentence twice. He is not describing a payments problem. He is not describing a crypto problem. He is describing a value-capture problem. Diners care intensely about specific restaurants. That intensity does not, in the current stack, translate into profitable repeat behavior the restaurant can see, measure, and act on. Blackbird’s wager is that the missing translation layer is a consumer-owned identity that travels with the diner across restaurants, accrues value the diner can see, and gives the restaurant a permissioned line of sight into who their best customers actually are.

That is, structurally, not a crypto product. It is an identity product. The chain is the substrate; the identity is the thing.

What “consumer-owned identity” would actually look like

Let’s get concrete, because the phrase “consumer-owned identity” has been doing a lot of work in pitch decks for ten years and almost never showing up in real restaurants.

In the existing stack, every restaurant you visit owns a fragmentary record of you. Your Resy profile knows your reservation history at restaurants on Resy. Your Toast loyalty profile, if the restaurant uses Toast Loyalty, knows your check history at restaurants on Toast — but only that one restaurant’s slice of it, and only if you opted in at the point of sale. Your Square Loyalty profile is the same thing for the Square ecosystem. Your OpenTable profile, your Tock profile, your SevenRooms profile — each one is a fragment, each one is locked inside the vendor that issued it, and none of them follow you when you walk into a restaurant on a different stack.

In a consumer-owned identity model, the diner walks in with a wallet — call it a wallet, call it a profile, call it a pass — that is portable. The restaurant can read it (with permission). The restaurant can write to it (with permission). The diner controls the keys. When the diner leaves and walks into a restaurant down the street that’s also on the network, the new restaurant can see, with the diner’s consent, that this is a high-frequency, high-spend diner who tips well and has a peanut allergy. The data is the diner’s; the access is permissioned; the value of repeat behavior accrues to the diner in a form the diner can see — credits, perks, status — rather than dying inside a CRM the diner will never log into.

That is the architectural pattern, and it is the reason the chain is in there. The chain is the trust rail that lets the data sit with the consumer rather than with the vendor. The same outcome could in theory be built without a chain — federated identity, OAuth-style consent flows — but every attempt to do that in hospitality over the last fifteen years has died on the politics of which vendor gets to be the issuer of record. The chain side-steps the politics by making no vendor the issuer of record. The diner is.

Whether that thesis survives contact with the actual behavior of actual diners — most of whom do not, in 2025, want to manage a wallet — is the open question of this round. But that is the question Spark is underwriting. It is not “will diners pay in crypto.” It is “will diners carry a portable identity into restaurants, and will restaurants pay for the privilege of reading and writing to it.”

Where Toast and Square left the door open

Here is the part of the analysis I think matters most for people building or competing against this category.

Toast and Square both had a window — call it 2019 to 2023 — to build exactly this product. They had the merchant relationships. They had the checkout. They had the loyalty SKUs already in market. They had the data. What they did not do is fuse loyalty and payments into a single consumer-facing identity that the diner owned and that traveled across merchants. They built it the other way: loyalty as a merchant-side CRM tool, with the consumer as the row in the database.

Why? Because the business model of a POS company rewards locking the merchant into the platform. The strategic value of a consumer identity that travels across merchants is, from the POS-company perspective, negative. If the diner’s identity is portable, the diner can defect from a Toast restaurant to a Square restaurant and bring their loyalty status with them. That’s bad for Toast and bad for Square. So neither built it. Toast’s loyalty product is excellent within Toast. Square’s is excellent within Square. Neither is excellent across the industry, because neither is allowed to be.

That gap is the door Blackbird walked through. By building loyalty + payments on a substrate that is neutral to any POS vendor, Blackbird can offer the restaurant a product the POS will never offer: a customer relationship that is not held hostage by the POS contract. That’s a real value proposition for an independent operator. It’s a threatening proposition for an incumbent POS. We’ll have more on the POS-side response to portable-identity loyalty in a forthcoming piece on POS-side identity in this column.

The Amex Ventures piece slots in here, too. Amex bought Resy to own the reservation touchpoint inside the cardholder relationship. What Amex did not buy was the post-meal loyalty loop, because in 2019 nobody was selling it as a product. If Blackbird builds it, Amex wants optionality on the cap table. Hence the check. The Amex bet is not “Blackbird wins.” The Amex bet is “if the diner-identity layer moves to a portable model, Amex needs a seat at the table on day one.” It’s a hedge against Resy becoming the wrong asset for the next decade.

What an independent restaurant gets from this

Let’s pull this down from the strategy layer to the operator layer, because I get the question every time I write about this category: what does this actually do for the 38-seat pasta place in Brooklyn?

Right now, that operator pays for a reservation system, a loyalty system, and a POS. The reservation system gives her names and party sizes. The loyalty system gives her a small, leaky list of opted-in regulars she can email. The POS gives her transaction data she has to manually correlate against the loyalty system to figure out who her best customers are. The work of stitching those three sources of truth together — the work I watched the floor manager doing at the host stand last Thursday — is unpaid labor performed by the restaurant on behalf of vendors who would rather she keep doing it manually than connect the data themselves.

In a Blackbird-style architecture, the loyalty signal and the payment signal arrive together, attached to a portable identity the diner has consented to share. The operator stops doing the stitching. The operator can see, the moment the diner walks in, that this is someone who has been to four other restaurants in the network this quarter, spends in the top decile, and has a stated preference for natural wine. The operator can offer a perk — comp the amaro, hold the corner four-top next time — that the diner sees on their phone and that accrues value to the diner across the network, not just at this restaurant.

For the operator, the value is twofold. One: the data stitching cost goes away. Two: the loyalty perks the operator extends start earning the operator credit in a network larger than the operator’s four walls, because the diner’s repeat behavior is visible to the network.

The operator-side takeaway box. What to actually watch if you run a restaurant:

• Adoption friction at the diner level. The product only works if diners carry the identity in. Watch whether Blackbird ships a flow that does not require the diner to know they are using a chain.
• Restaurant-side fees. The economics of loyalty + payments only work if the fee load is materially lower than the combined cost of your current reservation + loyalty + payment stack. Ask for the all-in number.
• Data portability. If the diner identity is portable, the restaurant’s relationship with that diner should also be portable. Confirm in writing what happens to your guest data if you leave the platform.
• POS interoperability. Blackbird does not replace Toast or Square. Confirm the integration path for whatever POS you already run, and whether the loyalty signal writes back into your existing reports.
• The network question. The value of being on a network scales with how many other restaurants in your immediate competitive set are on it. A single-restaurant deployment is a worse product than a neighborhood-wide one.

If those five things check out, this is a real product. If they don’t, it’s a pilot.

What we’re watching by Q4

By the back half of 2025, the questions I will be asking this company are:

How many restaurants on the network? Blackbird has been quiet about merchant counts. The Series B does not work as a thesis if the merchant count is still in the low thousands by Q4. The product is a network product; the network needs density. Watch for a merchant-count disclosure in the next six months. If they don’t disclose, that’s a tell.

How many diners on the network, and what is the repeat rate? A loyalty product lives or dies on repeat behavior. The metric to watch is not signups; it is the percentage of diners who use the wallet on their second, third, fourth visit. Anything below 40 percent on second-visit usage is a yellow flag.

What does the take rate look like on payments? Blackbird is sitting on the payment leg as well as the loyalty leg. If the take rate is competitive with the Stripe-and-Toast world (call it sub-3 percent all-in), this is a viable payments business with a loyalty wedge. If the take rate is higher because the chain costs are higher, this is a loyalty business that has to subsidize payments. Different unit economics, different valuation math.

What does Amex actually do here? The cleanest sign that the diner-identity thesis is winning would be Amex extending the Resy footprint into Blackbird-style portable identity inside the next twelve to eighteen months. The cleanest sign it’s losing would be Amex Ventures quietly marking the position down at the next round. The Amex Ventures position is the truth-serum on this thesis, and we’ll be watching the Amex side of it closely. We have more on the loyalty-layer dynamics in a later piece in our coverage of the loyalty layer.

And finally: what does Toast do? Toast is publicly traded, has a loyalty product, has a payments product, and has every commercial reason to not let a portable-identity network become the substrate of the next decade of restaurant data. Toast’s response — whether it’s an acquisition attempt, a competitive launch, or strategic silence — will tell you whether the incumbent POS layer is taking this seriously. As of today, April 8, the public response is silence. Silence at this stage is not concession; it’s wait-and-see. The Toast response, when it comes, is the second-most-interesting data point in this story after the Amex one.

There will be a lot of writing in the next week framing today’s news as a crypto round. Some of it will be skeptical, some of it will be cheerleading, and almost all of it will be looking at the wrong thing. The right thing to look at is the host stand. Three apps, three sources of truth, one human being standing in front of you who is, in 2025, still a different ghost in each system. The company that fixes that — the company that gives the diner a single identity they own, and gives the restaurant a single line of sight into the diner — wins a hospitality data layer that nobody currently owns.

Spark thinks Blackbird is that company. Amex is hedging. Union Square is along for the network effects. Coinbase and a16z crypto are validating the substrate. And Leventhal, on his third try at restaurants after Eater and Resy, is finally taking a swing at the part of the relationship his first two companies couldn’t reach.

We’ll know by Q4 whether the swing connects. I’ll be at the host stand, watching.

— Priya files The Operator. Tips: tips@tabletransfers.com.