substack.com

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

2026-05-12 · 13:03 UTC ·Nate from Nate’s Substack ·4 min read

Brief

Nate (May 12, 2026) outlines how agentic commerce—software agents holding wallets, signing authorizations, and paying merchants—unbundles the single human checkout click into six commercial responsibilities that must be explicitly assigned: identity, authorization/evidence, fraud/risk, payment credentials, settlement/refunds/liability, and data/merchant–customer relationships. He traces the opening clash to OpenAI + Stripe’s Instant Checkout (shipped in September and scaled back five months later) and contrasts it with Shopify and Google’s counter-protocols, arguing the real fight is over where commercial trust (the persistent authorization/evidence layer) lives. Key technical claims: authorization is distinct from payment and must outlive the transaction; software-to-software payments (including stablecoin rails) should use different infrastructure; and AWS’s platform position matters. Nate ends with two operational prompts — a responsibility-layer audit and an authorization spec — for builders, finance, and legal to close gaps.

Why it matters

Nate argues six commercial responsibilities that used to be hidden behind a single human checkout click must now be named and owned by agentic software (examples: identity/ID proofing, authorization evidence, fraud/risk scoring, payment credentials, settlement/refunds/liability, and customer/merchant data rights).

Key details

  • OpenAI and Stripe shipped 'Instant Checkout' in September; five months after launch it was scaled back while competing approaches from Shopify and Google gained traction, marking the first round of the protocol fight over agentic commerce.
  • Technical thesis: 'authorization is not payment' — agentic commerce needs an evidence/authorization layer that outlives the transaction; Google and Stripe are taking different technical/protocol routes to build that persistent authorization/evidence plumbing.
  • Nate argues software-paying-software (including stablecoin use cases) requires different rails than person-to-merchant checkout, AWS will be a quiet strategic owner of key layers, and he supplies two practical tools — a responsibility-layer audit and an authorization spec for finance/legal teams.
Cleaned source text

Watch now | For most of the internet’s history, a purchase has been a human action that everyone in the chain could see.

͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­͏ ­

Forwarded this email? Subscribe here for more

Get the full post and max your AI career leverage, plus connect with tens of thousands of paid subscribers in Nate’s Substack chat.

Most AI newsletters tell you what happened. This one tells you what to do about it — without the hype.

Upgrade to paid

Watch now

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

The old checkout button hid six commercial responsibilities behind one human click. Software just stopped clicking, and every hidden responsibility has to be named.

Nate

May 12| | | ∙| | Preview

READ IN APP

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.

Subscribers get all posts like these!...

Watch with a 7-day free trial

Subscribe to Nate’s Substack to watch this video and get 7 days of free access to the full post archives.

Start trial

A subscription gets you:

About 10 posts a week on AI, including videos, guides, and how-to’s

Subscriber-only podcast episodes

Active private substack chat with daily posts on all things AI

Like

Comment

Restack

© 2026 Nate

548 Market Street PMB 72296, San Francisco, CA 94104