Six layers your agent has to handle. Most products have only thought about two. + a responsibility-layer audit.

For most of the internet’s history, a purchase has been a human action that everyone in the chain could see. A person clicked a button on a merchant’s site. A payment credential moved through a processor. A network or wallet weighed the risk. The merchant took responsibility for the order. The records were imperfect, but everyone agreed on the shape of the evidence: a human was present, a page was shown, a credential was used, a final action was taken.

Agentic commerce breaks that structure.

Software is starting to hold wallets, sign authorizations, and pay merchants directly. Some of those agents are spending your money. Some are spending your company’s. Some are spending your customers’. When one of them sends money to the wrong place — and one of them will — someone is going to be left holding the bag. Protocol camps are fighting over who that someone is.

The question stops being “can the customer pay?” and becomes “how does everyone know the agent was allowed to do what it just did?” That question reaches well past checkout. It touches identity, authorization, fraud, payment credentials, settlement, refunds, liability, data rights, and the merchant’s relationship with the customer. The old purchase bundle comes apart, and the market isn’t converging on a single replacement. It’s splitting into protocol camps, each owning a different piece of what used to live behind one click.

That’s the split. A fight over where commercial trust lives, not over a single button. And it will shape who keeps the customer, who carries the loss, and who gets to write the rules of online buying for the next decade.

Here’s what’s inside:

• The first round of the fight is already over. OpenAI and Stripe shipped Instant Checkout in September. Five months later it was scaled back, while Shopify and Google’s counter-protocol gained ground.

• Authorization is not payment. The evidence layer agentic commerce needs, why it has to outlive the transaction, and the two routes Google and Stripe are taking to build it.

• The stablecoin case that holds up. Software paying software is a different business problem than a person buying shoes, and the rails should be different too.

• Where this lands and who owns which layer. Why AWS quietly matters most, and what every kind of builder, merchant, and operator should do now.

• Two prompts to expose your own gaps. A responsibility-layer audit that forces you to name who owns each piece of an agentic purchase in your product, and an authorization spec that finance and legal will actually accept.

The split started a year ago. Start with Instant Checkout: how OpenAI and Stripe launched it, and why OpenAI walked it back.