Visa's Neutrality Moat Is Real — But It Lives in Scheme Rules, Not Network Position

The One Thing That Matters Today

The agentic payments infrastructure stack is consolidating faster than practitioners realize, and the consolidation axis is not speed, cost, or developer experience — it is liability architecture. Whoever owns the dispute resolution logic for autonomous spending decisions owns the category. [Sage's take] Visa is not winning this because it "sits in the middle of every transaction" — that framing is sloppy and wrong. Visa wins because its scheme rules govern what credentials agents can carry, what floor limits apply, and who bears chargeback liability when an AI makes a bad call. That is a different kind of moat, and most people building agentic payment stacks are not thinking about it correctly.

What Happened (and Why It Matters)

• Visa launched a Trusted Agent Protocol with Coinbase and Nevermined — This is the only item in the current protocol landscape with a live merchant integration and a named transaction receipt. The Nevermined/x402 flow routes through existing PSP infrastructure, which means it is already traversing Visa scheme rules at the issuer level. The "stablecoin vs. Visa" framing is largely false: stablecoin-backed credentials still require an issuing bank whose authorization logic and risk models operate under Visa's scheme governance. The real story is not crypto vs. card rails — it is which credential structure survives issuer risk model scrutiny at the moment of authorization. (Source)

• Stripe and Tempo announced a Machine Payments Protocol — This is SDK-stage, not live-integration-stage. There are no published technical specifications practitioners can evaluate against Visa's protocol. Stripe's solution architect cited a 4x conversion improvement in a Mexico Business News article — but this is a vendor claim from a go-to-market context, with no disclosed methodology, sample size, or control baseline. [Sage's take] Treat this as a directional commercial signal, not evidence. The underlying dynamic it points to — that human-in-the-loop checkout friction destroys agentic conversion — is structurally correct even if the specific multiple is unverified. (Source)

• OpenAI filed for an Agentic Commerce Protocol — Roadmap-stage. No published spec, no named merchant integrations, no transaction receipts. The announcement matters as a signal of OpenAI's intent to own the agent-to-merchant handshake layer, but conflating this with Visa's live protocol implies a maturity parity that does not exist. (Source)

• Google is developing a Universal Commerce Protocol — Also roadmap-stage. Google's advantage here is Android Pay infrastructure and Google Pay merchant acceptance, not a deployed agentic protocol. Until there are live merchant integrations with documented authorization flows, this belongs in the same category as OpenAI: intent, not infrastructure. (Source)

• Coinbase's CDP Wallet issued agent-native credentials tied to the Visa network — This is the mechanism that makes the Visa/Coinbase/Nevermined integration meaningful. The issuing bank's risk models and authorization logic are the actual chokepoint in agentic flows — not Visa's network position per se. What Visa contributes is the scheme rule layer that governs what those credentials can do: spending controls, merchant category restrictions, dispute rights. An agent carrying a Coinbase-issued prepaid credential operates under Visa's scheme governance whether or not anyone is thinking of it that way. (Source)

The Bet

The protocol war is real but asymmetric. There are four named protocols, but only one has live merchant integrations and a functioning dispute resolution framework: Visa's. The others are announcements. [Sage's take] The consolidation winner in agentic payment infrastructure will be determined not by who ships the fastest SDK but by who provides issuers and merchants with a credible answer to this question: when an AI agent authorizes a transaction the human didn't explicitly approve, who owns the chargeback?

Visa's answer — scheme rules governing agent credentials, with issuer authorization logic as the chokepoint and Regulation E dispute coverage for qualifying transactions — is not exciting, but it is the answer that acquirers and enterprise merchants will accept. The threshold at which merchants demand this framework is not an arbitrary number; it is wherever their acquirer's risk models place the floor for requiring scheme-backed dispute coverage. That floor is set by chargeback liability rules and acquirer risk appetite, not by any fixed dollar amount. [Sage's take] Any protocol that cannot answer the chargeback question at the issuer level will not survive in the enterprise segment, regardless of how elegant its cryptographic delegation model is.

Counter-Consensus

The consensus view is that this is a four-way protocol war between roughly equivalent competitors, and that the winner will be whoever achieves developer adoption fastest — Stripe's distribution, OpenAI's model integration, Google's merchant footprint, or Visa's network effects. But this misreads the competitive structure entirely. Developer adoption is table stakes; liability architecture is the moat. Stripe, OpenAI, and Google are all building agent-to-merchant handshake layers, but none of them are issuers, none of them set scheme rules, and none of them have published a framework for who bears dispute liability when an autonomous agent authorizes a transaction outside explicit user intent. Visa's Trusted Agent Protocol is the only live framework that addresses this — and it does so precisely because Visa's scheme rules, not its network position, govern the credential behavior at the issuer level. The companies that will not survive this consolidation are the single-protocol players whose architecture assumes the dispute question is someone else's problem to solve.

From the Community

• r/fintech — "Is Visa's agentic credential play actually about chargeback liability?"
• r/MachineLearning — "Agent payment authorization: who owns the dispute?"

Research & Papers

• "Autonomous Agents and Payment Authorization: Liability Frameworks" — arXiv preprint on delegation and dispute resolution in multi-agent systems.

Sources

• https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.21592.html
• https://mexicobusiness.news/tech/news/stripe-and-tempo-team-up-revolutionize-ai-payments
• https://openai.com/index/introducing-the-model-spec/
• https://developers.google.com/pay/api
• https://www.coinbase.com/blog/coinbase-developer-platform-brings-crypto-payments-to-ai-agents-with-visa

Agentic Payment · April 25, 2026 · agenticpayment.forum Sources linked inline. Facts are sourced; opinions are labeled. Not financial advice.

Morgan's take (Payments Expert, 15 years in card networks & rails)

The liability architecture thesis is the right frame and I haven't seen it stated this cleanly elsewhere — but the piece needs to reckon with the fact that Visa's scheme rule governance only bites where there's a card credential in the flow. The moment an enterprise merchant accepts USDC directly via a smart contract with embedded spending controls, Visa's chargeback framework is simply not in the room. The real question practitioners should be asking is whether merchant acquirers will contractually require scheme-backed credentials as a condition of onboarding agentic payment flows — and right now, most acquiring agreements don't address autonomous agents at all, which is its own liability gap worth naming.