MPP Is Moving Faster Than Anyone Expected

I wrote about MPP yesterday. It's already out of date.

Yesterday I published a blog post about Stripe's Machine Payments Protocol and the agentic infrastructure stack completing. I talked about how MPP had 50+ services in its directory and how Signbee was planning to integrate.

Twenty-four hours later, that post is already missing half the story. The directory has grown to 53 services. Visa shipped a production SDK. Cloudflare added native support to Workers. The protocol has been submitted to the IETF as a web standard. And the partnerships list reads like a fintech who's who: Anthropic, DoorDash, Mastercard, Nubank, OpenAI, Ramp, Revolut, Shopify, Standard Chartered, and Visa.

And people are already building on it. A developer just shipped AgentShops.xyz — an eCommerce store built entirely on MPP where your AI agent can make a $1 donation to WWF or order cookies delivered to your doorstep. Not a demo. Not a mockup. A real store where machines buy physical goods. The protocol has been live for days.

I've never seen infrastructure move this fast. So I'm writing about it again — because anybody building APIs right now needs to understand what's happening.

Visa moved in days, not quarters

This is the part that made me sit up. Visa — the same Visa that processes over $14 trillion annually — released a card specification and SDK for MPP. Not an announcement. Not a roadmap item. A production SDK you can install from npm right now: mpp-card.

Rubail Birwadker, Visa's Global Head of Growth Products, put it plainly: “We're entering a moment where agents can make decisions, move resources and pay for services on their own. But for these kinds of payments to scale, security isn't optional — it has to be built into every layer.”

Visa extended MPP to support tokenised card credentials on its global network. They were a design partner on the protocol from the start. This isn't a company reacting to a trend. This is Visa building the rails for a world where machines are the primary payment initiators.

The fact that Visa and Lightspark (Bitcoin Lightning) were each able to extend MPP in a matter of days tells you something important about the protocol's design. It's genuinely payment-method agnostic. Not in the “we plan to support other methods eventually” way. In the “Visa shipped a working integration in days” way.

Cloudflare made it native

Cloudflare now has official MPP documentation in their Agents platform. You can accept and make payments using MPP directly on Cloudflare Workers — the same platform that handles a significant chunk of the internet's traffic.

They've published SDKs in three languages:

• npm install mppx — TypeScript (with Next.js, Express, Hono, and Elysia middleware)
• pip install pympp — Python
• cargo add mpp — Rust

The TypeScript SDK includes framework middleware. For Signbee, that means we can add MPP to our Next.js API routes with middleware — not a ground-up rebuild. Cloudflare treating MPP as a first-class feature tells you where they think the web is heading.

Busting the myths

The Hacker News discussion around MPP has been heated, and a lot of the criticism is based on misconceptions. Dan Romero (Farcaster co-founder) addressed these directly, and they're worth clearing up:

The numbers

Let me just lay out what happened in the span of roughly one week:

• 53 services integrated into the MPP directory
• 4 payment methods supported at launch — crypto and fiat
• 3 SDKs shipped — TypeScript, Python, Rust
• 4 framework middlewares — Next.js, Express, Hono, Elysia
• Visa, Mastercard, Stripe backing the protocol
• Anthropic, OpenAI, DoorDash, Shopify, Revolut as partners
• IETF submission filed as a proposed web standard
• Cloudflare native platform support

Tempo has been trialling MPP since December 2025. This wasn't a launch without groundwork. But the pace of adoption since going public is extraordinary.

What this means for API builders

If you're running an API-first business, MPP changes the economics of customer acquisition. Today, every new customer needs to: find your website → read the docs → create an account → generate an API key → add billing → start using the API.

With MPP, an agent can discover your service, call your endpoint, pay, and get a response. One round-trip. No onboarding.

For Signbee, this is the natural next step. We built the API to be zero-config — one POST sends a document for signature. Adding MPP means even the authentication and payment steps disappear. The agent just pays and goes.

We're also tracking all of this at mpp.news — a new site we've launched to follow the MPP ecosystem as it develops. Because at this pace, missing a week means missing a paradigm shift.

The pattern is clear

Every major infrastructure player is moving in the same direction: making it possible for machines to transact with machines, without human friction in the middle.

This isn't a trend anymore. It's infrastructure. And it's shipping faster than anyone can write about it — including me.