maybe worth building
the blog
← the blog
July 2026 · Verdicts

Is agent payments infrastructure worth building in 2026?

Short answer: not the rails. Stripe, Google, and Coinbase shipped three open agent-payment protocols in under a year, and Natural just raised $30M to fight them anyway. The layer nobody owns yet is control: what an agent may spend, and who it actually is.

The verdict

Not the rails. Stripe and OpenAI shipped one open protocol, Google shipped another with 60+ partners, and Natural just raised a $30M Series A with a team hired out of Stripe, Ramp, and Square. The transport layer is spoken for. What's still open is the control plane above it: what each agent may spend, proof of who it is, and an audit trail a finance team can sign. Builders are asking for that part in public, in their own words.

Why is money suddenly pouring into agent payments?

Because every existing rail assumes a human is present. Cards, ACH, checkout pages: all of it was designed around a person approving one transaction at a time. An agent that pays a vendor or buys compute on its own has nobody at the keyboard, so today it either stalls at the paywall or gets handed a company card with open-ended access. Neither scales past a demo.

That's the bet behind Natural. TechCrunch reported the round on July 20, 2026: a $30M Series A led by Forerunner Ventures, roughly 193 days after launch, taking total funding to $40M. Founder Kahlil Lalji sold his last fintech, Ivella, to Earnin, and he's been hiring out of Stripe, Ramp, and Square. His sizing claim from the piece: "The number of payments that may occur in the world may be two or three or four orders of magnitude greater than the number of payments that exist today." Maybe. But a claim that size is also why the biggest names in payments didn't wait for a startup to define the category.

Who already owns the payment rails for AI agents?

The incumbents, and they're giving the rails away on purpose. Stripe and OpenAI released the Agentic Commerce Protocol (ACP) in September 2025, open source under Apache 2.0; it's what runs Instant Checkout inside ChatGPT. Google announced AP2, the Agent Payments Protocol, on September 16, 2025 with more than 60 launch partners, including Mastercard, PayPal, and American Express. Coinbase's x402 revived HTTP status code 402, "Payment Required," reserved since 1999 and almost never used, for machine-to-machine micropayments. Visa has the Trusted Agent Protocol. Mastercard has Agent Pay. maybe worth building has watched this category go from zero shipped standards to three open ones in under a year, and that speed tells you what the giants think the transport layer is worth as a standalone product: nothing. The protocol is free because the processing volume behind it is the business.

Add the funded startups, Natural at $40M total and the DCVC-backed Skyfire, and the read is simple. The pipe is the most crowded, best-capitalized square on the board. A small team walking into a standards war against Stripe, Google, Coinbase, and both card networks isn't early. It's outgunned.

What do builders actually complain about?

Not the absence of a protocol. The pain that shows up in public is about control and accountability. A builder at Artificial Lab, on Hacker News in March 2026: "We run 17 AI agents at Artificial Lab. One day we realized we had no idea what they were spending. ... The UI for all of that spending was our credit card statement. Once a month. After the fact." Another builder, at APEX Automation Group, in January 2026: "we kept hitting a wall: how do you let an autonomous agent actually pay for a service or data from another agent without a human in the middle to sign off on a $50 credit card transaction or a manual API key exchange?"

Then there's the hole under all of it: nobody can prove who an agent is. That gap is serious enough that Vint Cerf, co-designer of TCP/IP, left 20 years at Google and is now advising Innovation Labs on DNSid, a proposed standard that ties every agent to a verified domain name with cryptographic proof. It went to the IETF as an Internet-Draft, and TechCrunch covered it on July 15, 2026. Cerf didn't pick money movement as the problem worth his time. He picked proof of who's behind the agent.

When is agent payments infrastructure worth building?

  • Build the control plane, not the pipe. Per-agent budgets, approval thresholds, kill switches, spend attribution across a fleet. The 17-agents quote above is a product spec written by the customer.
  • Build the audit layer. Finance teams will reconcile agent spend the way they reconcile corporate cards today: who spent it, on which task, under whose authority. Ramp built a real company doing that for humans. The agent version doesn't exist, and none of the three protocols try to solve it.
  • Make merchants agent-legible. Every seller now has to answer whether a buyer is an agent, whether it's authorized, and which protocol it speaks. Tooling that gets one merchant working across ACP, AP2, and x402 rides all three standards instead of betting on a winner.
  • Use the rails inside a vertical. A payables or procurement agent for one industry, with Natural or ACP underneath, competes on workflow knowledge instead of payments plumbing.

When isn't it worth building?

  • A fourth protocol. Three open standards shipped in about twelve months, backed by Stripe with OpenAI, Google with 60+ partners, and Coinbase. A standards war is a distribution war, and you don't have distribution.
  • A generic "Stripe for agents." That exact pitch already has $40M at Natural, a DCVC-backed rival in Skyfire, and Stripe itself awake to it. The knife fight is fully capitalized.
  • A stablecoin wallet with an agent label. Settlement speed isn't the bottleneck; authorization and trust are, and a wallet solves neither.

The test to run before you build

Run the two checks the engine runs on everything. The space receipt: is real money already in this exact spot? Twice over. $30M into Natural in July 2026, and three open protocols from the biggest names in payments inside a single year. The space is alive, and the crowding sits exactly at the transport layer. The pain receipt: can you find a real person describing the problem in their own words? Yes, and both quotes point above the rails, at visibility and authorization, not at settlement.

Then the standard question: if agents get twice as capable next year, does your product get more valuable or less? More capable agents means more transactions, which makes the control and audit problem worse, so the control plane compounds. A rails bet mostly just gets more crowded.

The one way we're wrong is bundling. Stripe already sells card issuing with spend controls, and if the rails winners fold a good-enough control plane into the protocols before independents find distribution, this wedge closes too. Watch the ACP and AP2 specs; the day they add fleet-level budgets and audit primitives, downgrade this verdict.

Cerf's DNSid draft is sitting at the IETF right now, unfinished. The money layer has three standards. The trust layer has a draft.

Related: Is it worth building AI agent security tooling in 2026?: the same "control the agent, don't rebuild the pipe" logic applied to the runtime instead of the wallet. Also see Is it worth building an AI agent in 2026? and Is it worth building a vertical AI agent in 2026? for the demand side: the agents that will be doing all this spending.

Frequently asked questions

Is agent payments infrastructure worth building in 2026?

The rails, no: Stripe and OpenAI's ACP, Google's AP2 with 60+ launch partners, and Coinbase's x402 all shipped within about a year, and Natural raised a $30M Series A in July 2026 to compete there with a team hired from Stripe, Ramp, and Square. The layer above the rails, yes: spend controls, per-agent identity, and audit for fleets of transacting agents is still unowned.

Why can't AI agents just use a credit card?

Cards and ACH assume a human authorizes each transaction. An agent either stalls at checkout or gets handed a shared card with open-ended access, which is how one team ended up learning what its 17 agents spent from the monthly statement, after the fact. Agent payment rails replace per-transaction human sign-off with programmatic authorization and limits.

Who are the main players in agent payments right now?

Protocols: ACP (Stripe and OpenAI, September 2025, Apache 2.0), AP2 (Google, September 16, 2025, 60+ partners including Mastercard, PayPal, and American Express), and x402 (Coinbase, built on HTTP status 402). Card networks: Visa's Trusted Agent Protocol and Mastercard's Agent Pay. Startups: Natural ($40M total, Forerunner-led Series A, July 2026) and DCVC-backed Skyfire.

What is Natural and what did it raise?

Natural is a year-old startup building payment rails for AI agents: wallets that hold funds, pay invoices, accept payments, and move money across banks and currencies without a human signing off each step. It raised a $30M Series A led by Forerunner Ventures, reported by TechCrunch on July 20, 2026, roughly 193 days after launch, and it names Stripe as its main competitor.

What is Vint Cerf's DNSid project?

DNSid is a proposed identity standard for AI agents from Innovation Labs, a subsidiary of the DNS registry company Identity Digital, with Vint Cerf advising. It links every agent to a verified domain name using cryptographic proofs, so a merchant or counterparty can check who stands behind an agent. It was submitted to the IETF as an Internet-Draft and covered by TechCrunch on July 15, 2026.

What's the open wedge for a small team?

The control plane and the audit trail: per-agent budgets, approvals, kill switches, spend attribution, and reconciliation a finance team can sign off on, plus merchant-side tooling that works across all three protocols. The public pain quotes in this space are about visibility and authorization, not about settlement speed.

Want 100 ideas that pass this test?

The free pack: 100 AI ideas actually worth building, each with the receipts and a clear verdict. No fake MRR screenshots.

You're on the list. The 100 ideas are on the way.