On October 6, 2026, American Express did something no card network had done before. It published a rulebook โ not for the people who carry its Platinum cards, but for the software agents that increasingly shop, compare, and pay on their behalf. The company rolled out an agentic commerce playbook, a product called Agent Purchase Protection, a Merchant AI Advisory Council, and โ layered on top of the ACE Developer Kit it shipped back in April โ a set of "guardrails" meant to govern how autonomous agents spend other people's money.
The number that should stop you cold comes from a survey by research firm Trendex: 93% of merchants and enterprises said they believe AI providers โ not merchants, not the card networks โ should absorb the cost when an agent gets a transaction wrong. Everyone agrees somebody should pay for agent error. Nobody agrees who. That is not a technical problem. It is a governance problem, and it is the exact kind of vacuum that gets filled by whoever moves first.
The trust gap underneath is just as stark. Only 15% of consumers said they would trust an agent with a large purchase. Sixty-six percent said they would use one to compare prices. Wide trust for small, reversible decisions; narrow trust for big, consequential ones. That asymmetry is the fault line running through the entire agentic commerce thesis โ and it is the reason American Express's real battle is not with Visa or Mastercard at all.
Let me back up and explain what actually happened, because the announcement reads like a compliance memo and the stakes are buried three layers down.
American Express is not a typical card network. Since 2008 it has operated as a bank holding company under Federal Reserve supervision, and โ unlike Visa and Mastercard, which run four-party "open loop" systems โ it runs a closed, three-party loop. It issues the cards. It acquires the merchants. It sits on both ends of the transaction. That structural fact is the single most important thing to understand about this announcement, because it is the source of both Amex's speed and its isolation.

The pieces Amex put on the table are these. First, an agentic commerce playbook: a documented set of expectations for how agents should authenticate, transact, and behave. Second, Agent Purchase Protection: a promise โ so far, only an announced intention โ to stand behind transactions that go wrong when an agent is involved. Third, a Merchant AI Advisory Council: a body of merchants convened to advise on agent policy. Fourth, and building on April's ACE Developer Kit, a technical layer that centers on a concept Amex calls the "registered agent."
That last piece is where the technical substance lives. Amex's approach is a whitelist: an agent is either registered and verified, or it is not. This is a deterministic model โ you are in the club or you are outside it. It contrasts sharply with the route Mastercard has taken, which leans on probabilistic scoring: assign every agent a risk score and let the transaction clear or flag based on the number.
Two philosophies. One says identity is binary and verified up front. The other says identity is a probability, assessed in real time. I have watched this exact argument play out in DeFi for years โ deterministic allow-lists versus probabilistic risk engines โ and I can tell you how it usually ends: whoever controls the list wins, and everyone else complains about the list.
The geography matters too. This is US-only. Global merchants are, in Amex's own framing, still waiting for a real standard. That is not an oversight. It is a sequencing decision, and a deliberate one.
And then there is the data. The four headline figures โ 93%, 83%, 15%, 66% โ all trace back to a single source: Trendex. No cross-validation, no second poll. When I ran community sentiment analysis during the March 2020 DAI de-peg, I learned to treat single-source numbers as directional, not dispositive. The 15% large-purchase trust figure feels right. The 93% merchant figure feels like the answer you get when you ask people who they would like to pay a bill. Keep that skepticism in your pocket; it matters later.
Here is where I want to do the work the announcement does not do for you.
The first thing to understand is what Amex is actually monetizing. Not payments. Trust. The card network's traditional revenue is merchant discount revenue โ the cut taken on every transaction โ plus net interest income and annual fees. But the underlying settlement function is being commoditized fast, and Amex knows it. When an AI agent can route a payment through any rail it wants, the card network stops being the destination and becomes one option among many. It gets downgraded to a pipe. Merchant discount revenue, the crown jewel, becomes negotiable.

So Amex's play is defensive, dressed as innovative. It is trying to bind merchants and agents to its trust infrastructure so that it retains pricing power over the discount fee even as the settlement layer underneath it commoditizes. That is the honest read. And it is a smarter read than the press release, which frames the whole thing as customer protection.
The registered-agent whitelist is not primarily a safety feature. It is an identity and data play. Think about what registration requires. An agent has to identify itself, present credentials, and share data with Amex. Registration becomes a KYC layer for machines โ a gateway through which every agent that wants to transact on the Amex loop must pass. Amex does not just get a safer network; it gets a proprietary map of agent behavior, shopping intent, and cross-platform identity. That is an asset no four-party network can assemble as cleanly, because a four-party network has to coordinate issuers and acquirers who do not share a single balance sheet.
This is where my oracle-latency obsession becomes relevant. In DeFi, we learned the hard way that a verification layer is only as good as its latency and its failure modes. Chainlink "solved" decentralization with a set of nodes that, in practice, concentrate trust in ways the whitepaper did not advertise. The lesson was not that oracles are bad. The lesson was that the entity that defines the verification standard quietly becomes the trusted party, regardless of how decentralized the diagram looks. Amex's registered-agent scheme is an oracle for identity. Whoever writes the registration spec โ and validates against it โ becomes the trusted party in agent commerce. That is a far more durable moat than a discount fee.
Now, the technical weak point. The playbook and the ACE Developer Kit give you the base layer and the guardrails. But the two hardest problems โ how a third-party agent gets verified, and how disputes get resolved at scale โ are still unresolved. Amex has said it will stand behind agent transactions. It has not said under what terms. That is a blank check, and blank checks have a way of being cashed by someone.
Which brings me to the liability question, and this is the part that genuinely excites me as a cryptographer.
Under Regulation Z, in the US, a consumer's liability for an unauthorized transaction is capped at $50. The whole architecture of consumer protection rests on a clean distinction between "authorized" and "unauthorized." Now drop an autonomous agent into that distinction. If a registered agent acts within its parameters, and those parameters were set by the consumer, is the transaction authorized? Almost certainly yes โ and if it is authorized, the $50 cap does not apply. Responsibility shifts downstream, toward the merchant.
Amex's Agent Purchase Protection is, whether it says so or not, an attempt to redraw a statutory liability boundary that was written for humans. That is a much bigger deal than a new developer kit. And it is why the "announced intention" language is doing so much work. The moment you promise to reimburse cardholders for agent errors, you have created something that looks a great deal like an insurance product โ and insurance is a state-licensed activity. Unless, of course, you route it through a partner. The announcement does not say. The silence is the story.
I have sat on the issuing side of this equation. In 2022, running market operations for a mid-tier exchange through the post-FTX collapse, I watched how quickly a liability promise becomes a balance-sheet problem. I spent that winter livestreaming cold-wallet audits and answering five hundred support tickets a day, because I had learned that a reserve proof is only worth the trust people place in it. The same logic applies to Agent Purchase Protection. A promise to pay is only as strong as the capital behind it and the fine print in front of it. Amex has shown neither yet.
Let me put a number on why this matters economically. If agent transactions scale โ and the enterprise willingness data at 83% says the demand is there โ chargebacks and disputes will not scale linearly. They will scale with the surface area of agent behavior, which is to say, super-linearly. Human arbitration cannot absorb that. You would need fully automated dispute resolution, which is itself a cryptographic and legal engineering problem of the first order. I have built and audited verification systems; the cost of proving a claim is real is not zero, and it does not get cheaper just because you call it automatic. My skepticism about ZK proving costs comes from the same place: cryptographic guarantees are wonderful, but somebody pays for the computation, and at scale that bill is not a rounding error.
So the honest technical assessment of Amex's stack is this: it is a "good enough to follow" architecture, not a "leading from the front" one. The ACE Kit is the foundation. The guardrails are a patch. The genuinely novel components โ registered verification and automated dispute resolution โ are promised, not shipped.
Now, the competitive picture, because this is a standard war and standard wars are won by distribution, not by elegance.
Mastercard is running probabilistic scoring with its agent payment efforts. Visa has its own intelligent commerce push. Google has AP2. OpenAI and Stripe have instant checkout and an agentic commerce protocol. Shopify is in the mix. And โ this is the piece the announcement scopes out entirely โ there are on-chain agent payment protocols emerging, the kind that let an agent settle a transaction in stablecoins over a blockchain rail without touching a card network at all.
That last category is the actual threat, and it is not on Amex's slide. The framing of "CBDC versus card networks" is a distraction. A digital dollar issued by a central bank plugs into the same account-based world Amex already navigates. The genuine disintermediation risk comes from two directions: stablecoins settling agent-to-agent payments directly, and open-banking account-to-account rails that let an agent pull funds straight from a bank account, bypassing the interchange fee entirely. Both are live. Both are growing. Both make the card network optional.
I spent 2024 building a comparative matrix of custodial providers for institutional advisors, and the question that kept surfacing was not "is crypto safe" โ it was "what is the rail, and who controls it." That is the right question here too. An agent does not care whether it pays through a card network or a stablecoin transfer. It optimizes for cost, speed, and reliability. Card interchange is a tax on the transaction that a stablecoin rail simply does not carry. If agent commerce grows the way the enterprise data suggests, the rational agent routes around the tax wherever it legally and technically can.
This is why Amex's playbook is so revealing. It is a rulebook for a game whose field is being repaved underneath it. And note what the playbook does not address: stablecoins, open banking, and account-to-account direct settlement. The document governs agents that transact on the Amex loop. It is silent on the agents that will not.
The Merchant AI Advisory Council deserves its own scrutiny. Convening merchants to "advise" on agent policy sounds collaborative. But a council is also a channel โ a way to socialize a standard before it is imposed, to make the people who will bear its costs feel like co-authors. I have sat in enough governance forums, from the MakerDAO task force to post-FTX community calls, to know the difference between genuine co-authorship and consultation theater. The coverage already flags the doubt: is this a real voice for merchants, or standard capture wearing a friendly face? When the entity that writes the rule also selects who gets to comment on it, the comment period is a formality.
And the cost-shifting question remains unresolved. Agent Purchase Protection introduces a new cost โ reimbursement. Where does it land? The most likely answer is on merchants, via higher discount fees. But merchants, per the Trendex data, believe the AI providers should pay. So you have three parties โ Amex, the merchant, and the AI platform โ each pointing at the others. That three-way standoff is the core commercial variable of the entire agentic commerce era, and no one has priced it yet.
Here is the quieter insight, and I think it is the one that matters most over a three-to-five-year horizon. The moat in payments is migrating from network scale to trust infrastructure. Amex is not trying to win by having the most cardholders. It is trying to win by becoming the party that certifies which agents can be trusted, and monetizing that certification. That is a pivot from being a network to being a standard-setter โ and standard-setters have a much better long-term position than networks, because networks compete on price and standards compete on legitimacy.
But there is a catch, and it is fatal if unaddressed. A certification standard only becomes valuable if it is open enough to be widely adopted. If the registered-agent scheme stays closed โ a walled garden only Amex agents can enter โ it fails to become a standard and succeeds only in becoming a smaller garden. The paradox is brutal: to win the standard war, Amex must open the gate, and the moment it opens the gate, it gives up the exclusivity that made the closed loop special in the first place. This is the same tension that broke the private-chain dream a decade ago. A blockchain only one company uses is not a network. It is a database with extra steps.
I watched a version of this in 2017, when I was translating wallet mechanics for five thousand Icon community members and fielding two hundred questions a day. The gap I kept hitting was not technical illiteracy. It was that the technology's value depended on adoption, and adoption depended on trust, and trust depended on the very clarity the project had not yet provided. Amex is running the same gauntlet now, just at institutional scale and with a much bigger balance sheet. The ethics of it are identical: the ethical pulse of the decentralized economy beats the same whether the ledger is a blockchain or a card network's private register.
Let me also flag the operational risk that gets almost no airtime. The registered-agent model is only as good as its validation. If the standard for "registered" is vague, you do not get safety โ you get a systematic wave of disputes as agents, merchants, and cardholders argue over whether a given agent was legitimately authorized. The biggest operational risk here is not a technical failure. It is a standards vacuum. A vague definition of "registered" is not a neutral gap; it is an active liability generator. I have seen this before, in the NFT metadata failures I investigated in 2021 โ the risk was not that the storage was centralized per se, it was that nobody had defined what decentralized storage actually meant, so ten thousand assets sat on a foundation no one had specified. The same failure mode is available here, at the scale of every agent transaction on the network.
There is also a data-privacy dimension the announcement skips. Registered agents carry user credentials and personally identifiable information across party boundaries. Registration means identity data gets shared. Under CCPA and the patchwork of state privacy laws, that is a compliance surface. But more interestingly, it is a data asset: the identity layer that authenticates agents is also the layer that observes their shopping intent. Amex does not just get a safer network; it gets a behavioral dataset. Whether that becomes a monetizable asset or a regulatory exposure depends entirely on how the registration spec is written โ and on who is allowed to read it.

And the international picture. This is US-only by design. That is a first-mover bet: define the standard at home, then export it. But the window is short. If the EU or the UK moves first on regional agent-liability rules โ and both have shown appetite for digital-payment regulation โ Amex's American standard fragments into a regional one, and the export strategy collapses. The bridge only works if it is built before someone else builds the one next door.
Which, finally, brings me to the macro variable that matters most and gets discussed least: the intersection of stablecoin legislation, open banking, and AI liability rules. Those three policies together determine whether agent payments can bypass the card network. Stablecoin law determines whether a token rail is legally viable for mainstream settlement. Open banking determines whether agents can pull funds directly from accounts. AI liability rules determine who is on the hook when an agent errs. Get those three aligned against the card networks, and the closed loop becomes a nice historical artifact. Get them aligned with the networks, and Amex's early standard-setting pays off enormously. The whole bet rides on policy it does not control.
Here is the angle you will not find in the coverage, and it is the one I would stake my reputation on.
Everyone is reading this as a card-network-versus-card-network story โ Amex versus Mastercard versus Visa, who wins the agent-payment standard. That is the visible fight, and it is the wrong one to watch. The real contest is between the account-based payment world and the token-based one, and the AI agent is the wedge that pries them apart.
Consider what an agent actually needs. It needs to authenticate, to transact, and to be held accountable. Cards offer authentication and a mature dispute apparatus. Stablecoins offer settlement without interchange. Open banking offers account access without a card network in the loop. An agent that can combine token settlement with open-banking funding does not need the card network at all โ and the only thing keeping it on the network is trust and convenience. Amex's entire strategy is an attempt to make the trust too valuable to abandon and the convenience too entrenched to replace.
But here is the contrarian twist. By leading with Agent Purchase Protection โ a liability promise โ Amex may be handing its competitors the very argument they need to bypass it. The moment the card network says it will cover agent errors, it implicitly concedes that agent errors are common enough to need covering. That concession is a gift to the token-based rails, which can say: our settlement is final, our authorization is cryptographic, our disputes are programmatic โ we do not need a protection product because we do not have the ambiguity the card network is promising to insure. Whether or not that claim is fully true, it is a compelling marketing position, and it is available to every stablecoin rail the instant Amex normalizes the idea that agent payments are risky.
There is a deeper irony. Amex's structural advantage โ the closed three-party loop โ is precisely what limits its ability to become the neutral standard the agent economy needs. A neutral trust layer has to be credible to parties who are not on your network. Amex can compel its own cardholders and merchants. It cannot compel Google's agent platform or a stablecoin protocol to register. The closed loop is a fortress, and fortresses do not become public infrastructure. The very thing that makes Amex fast makes it un-neutral โ and un-neutral standards lose the distribution war to the players who own the platforms where agents actually live.
I will add one more under-the-radar risk, because it is the kind of thing that only shows up in the postmortem. The Trendex data is single-source. If the 93% and 83% figures do not survive replication, the entire premise that there is enormous demand for agent commerce weakens, and Amex's aggressive bet starts to look like a solution in search of a problem. I have learned to distrust convenient consensus numbers. When I coordinated the response to the March 2020 DAI de-peg, the loudest sentiment data was the least reliable, and the quiet on-chain signals told the truer story. Here, the loudest number is 93%, and it comes from one firm. Watch for a second source. If none appears, treat the demand thesis as unproven.
So the contrarian read is this: Amex is fighting the wrong war on the right instincts. It correctly senses that the moat is trust, and that trust must be monetized before the settlement layer commoditizes. But it is building that trust inside a fortress, using a liability promise that concedes the very risk it is meant to neutralize, while the token-based rails it will not name are quietly assembling the open, final, programmatic settlement layer that makes the fortress optional. Building bridges in a fragmented digital frontier requires the bridge to reach both banks. A bridge that only connects to your own island is not infrastructure. It is a pier.
The next eighteen months will tell us which way this breaks. Watch three signals. First, whether the registered-agent spec gets published openly or stays proprietary โ that single decision determines whether Amex becomes a standard or a silo. Second, whether US regulators bless the private standard or demand neutrality, because a blessing turns Amex's early move into a rule-writing dividend and a neutrality mandate guts it. And third, whether the stablecoin and open-banking rails name a liability model of their own โ because if they do, and if it is cleaner than a reimbursement promise, the card network's trust play gets undercut at exactly the moment it is trying to scale.
The ethical pulse of the decentralized economy does not care whether the register is public or private. It cares whether the party writing the rules is accountable to the people the rules govern. On October 6, American Express volunteered to write those rules. The question the industry has not asked yet is a simple one: who writes the rules for the rule-writer, once the agents are doing the spending?