The Agentic Commerce Standoff: Banks Join Site Blocks While PAP and KYA Agent-Identity Standards Emerge (October 2026)

The Agentic Commerce Standoff: Banks Join Site Blocks While PAP and KYA Agent-Identity Standards Emerge (October 2026)

The open question this cycle tracks: will the open web accommodate consumer agents via authenticated agent identity, paid agent-access deals, or escalating blocks? October 2024 brought the sharpest escalation yet — banks — plus the first concrete identification standard. (Prior state: Amazon blocked Meta Muse on Sept 21 as an "unauthorized AI agent" violating its Conditions of Use, citing non-identification and credential storage; Meta publicly pushed sites to stop blocking.)

JPMorgan Chase blocks outside agents — "rogue agents... there could be thousands of them"

On JPMorgan's Q3 earnings call (Oct 13, 2026), CEO Jamie Dimon said the bank will not let outside AI agents — he named Meta's Muse and Instinct — operate on retail customer accounts. Finextra quotes him directly: "We're not going to allow just any...outside agent to come in inside the company, because it's just too risky for clients and for JPMorgan.¹.. You don't want rogue agents, and there could be thousands of them." And on the risk allocation: "If people are using them, they should understand the risk. There's a liability transfer. They should understand the liability transfer." A bank spokesperson confirmed the block and left the door open for a future authenticated channel: "Because it is not safe, we do not permit third parties to access accounts by obtaining customers' banking credentials and logging in on their behalf. We support secure, customer-authorised data sharing through open banking providers and are committed to enabling agentic connections securely." Agents can still read some data (e.g., balances) through Plaid-style connectors with user credentials; there is no timeline for direct agent access. JPMorgan is simultaneously deploying agents internally and piloting customer-facing tools (Smart Cash cash-flow optimization), so this is a boundary decision, not an agent boycott.

Amazon's block widens; Musk escalates

Amazon had already blocked Muse and restricted OpenAI Dots; in October it banned xAI/SpaceX's Grok Bot from shopping the site as well. Elon Musk responded by floating a competitor to Amazon — and, after a demo in which he leaked his own order number, shipping and billing addresses, and the last four digits of an Amex card in an X post showing off a Lego purchase, pledged blanket liability: "If Grok @bot makes a mistake with a purchase or leaks your card (never happened yet), SpaceX will make you whole." Fintech Brain Food's analysis of the standoff notes Amazon's three complaints — "1. Nobody told us 2. The agent doesn't identify itself, 3. It stores our customers' logins" — "read almost like a term sheet," since Amazon's own Buy for Me agent identifies itself and lets brands opt out when it shops other retailers' sites. Context that shapes the endgame: Amazon sued Perplexity and lost the hacking claim in the Ninth Circuit in August (the court held the user, not the AI company, accesses Amazon's computers — contract claims survived, which is why the Muse block cites Conditions of Use rather than a new suit); Cloudflare changed defaults on Sept 15 so new sites behind it block agent traffic on ad-carrying pages; and Walmart's 200,000 products in ChatGPT's Instant Checkout converted roughly three times lower than on Walmart's own site — the conversion problem that makes merchants demand a trust framework before opening the door.

The standards race consolidates: PAP and KYA

The first cross-industry identification standard landed Oct 6: the Personal Agent Protocol (PAP), announced by Meta and Sierra and developed with Genesys, Shopify, Walmart, and others, defines how personal agents identify themselves, obtain authorization, and interact with businesses. (Google's A2UI, introduced December 2025, solves a different piece — agents generating structured UI across channels.) In payments, the protocol zoo — Visa's Trusted Agent Protocol, Mastercard's Verifiable Intent, Ant's Agentic Mobile Protocol, Google's Universal Commerce Protocol, OpenAI+Stripe's Agentic Commerce Protocol — took a consolidation step on Sept 10, when Visa, Mastercard, and Ant agreed to combine their standards into a shared KYA (Know Your Agent) framework that checks who operates an agent, who certified it, and how it has behaved on every transaction, with certification revocable.

Enterprises are caught in the middle — and starting to build for agent customers

Contact-center and CX vendors report agents are already arriving through human channels. Genesys's Mike Szilagyi: "Customers are saying they have AI agents coming in through what I would call human channels — voice, web chat or web pages — so they're already here, [but] right now it's hard to tell at what volume." And: "One of the key things that we need to do as contact center providers and experience orchestration providers is to get better at identifying whether something is human, or whether it's AI." Kustomer CEO Brad Birnbaum: "There will be a world in which I believe there will be agents talking to agents. [It] will very much happen." Skeptics persist: IDC's Jordan Jewell notes Meta's commerce attempts have "always fallen flat because they have the innovator's dilemma and are always focused on advertising," and Gladly CMO Ali Fazal is blunter — "I think that he's full of crap... Regular people like to shop."

Where this stands: the standoff is forcing an identity layer faster than either side expected — banks (JPMorgan), retailers (Amazon), and infrastructure (Cloudflare) all blocking unauthenticated agents while Meta/Sierra (PAP) and the card networks (KYA) race to define the trusted alternative. The unresolved question is who owns that layer and its fees. See Meta Muse's Trust Deficit: Verified Incidents, Apple's Permission Crackdown, Monetization, and the Block List (Oct 2026) for the Muse-specific trust record, Agent-to-Agent Risk Across Company Boundaries: The Next Governance Gap (Oct 2026) for the B2B boundary version of the same problem, and Enterprise FinOps and Payment Rails for Autonomous AI Agents in 2026 for the payment-rails background.