The trust layer is becoming the transaction layer


OZ Signals

April 21, 2026

The Trust Layer Is Becoming the Transaction Layer

Last week’s issue argued that commerce is being reformatted so machines can read merchants, call systems, and execute against them. That layer matters, but it is no longer the only one that matters. Once a machine can act, a different question takes over. Who authorized the action, what exactly was intended, which merchant was verified, and who carries the liability when the machine gets it wrong? This week’s developments suggest that the next competitive layer in AI commerce is not better discovery. It is delegated authority, machine-verifiable identity, and transaction-grade accountability.

What changed in the market this week is that several players stopped treating trust as a compliance wrapper around agentic commerce and started building it into the transaction itself. American Express moved to register agents, capture intent, tokenize credentials, and protect cardholders from registered agent error. World pushed proof of human into agent workflows and document execution. A new IETF draft tried to close the merchant identity gap at protocol level. AEON360 and Google Cloud showed what happens when commerce, finance, loyalty, and consent are stitched into one persistent operating context. Together, these moves point to a more important shift than “AI shopping.” The market is beginning to build the authority chain that lets machine-led commerce scale without collapsing under fraud, disputes, and broken attribution.

American Express moved trust from brand promise into transaction logic

On 14 April, American Express introduced its ACE Developer Kit and announced Amex Agent Purchase Protection for registered agent purchases. The important part is not the headline that Amex wants to participate in agentic commerce. It is the architecture underneath it. The ACE stack is built around agent registration, account enablement, intent intelligence, tokenized payment credentials, and cart context, all tied back to Amex’s closed-loop network. That means Amex is not just trying to help an agent pay. It is trying to make the full chain of who acted, what was intended, what was bought, and how the decision can later be defended visible inside the payment system itself.

Structurally, this matters because it shifts the center of gravity from checkout completion to transaction defensibility. In human commerce, trust was often inferred from interface cues, authentication steps, and post-facto dispute handling. In machine-led commerce, those cues are weak. The network needs evidence. Amex is effectively saying that the payment rail itself must become a place where intent, authorization, and remediation are modeled in machine-readable form. That is a much bigger move than adding another wallet button. It suggests future winners will not be the players who let agents spend first. They will be the players who can prove why a spend should have been allowed, and who can absorb the consequences when it should not have been.

Break: Chargeback-era thinking stops working when agent identity, customer intent, and cart context are expected before authorization, not reconstructed after the damage is done.

Sources: Amex release

American Express also moved upstream into agent-run commercial spend

A day later, American Express announced it would acquire Hyper, an agentic expense management company. Hyper’s core capability is not generic AI productivity. It is native expense agents that auto-categorize spend, check purchases against budget and policy, and push the workflow forward without waiting for manual intervention. Amex said the acquisition will add AI expertise across its commercial services business and support an expense management platform planned for later this year.

This is structurally important because it extends the authority shift from consumer purchases into business procurement and finance operations. Consumer agentic commerce gets most of the attention, but commercial spend is where machine authorization may scale faster because budgets, roles, policy rules, and approval structures are already formalized. By bringing agentic expense logic closer to the card network and commercial services layer, Amex is positioning itself not only as a payment provider, but as a policy engine for business spending. The second-order implication is that spend management, reimbursement, procurement, and payments are likely to collapse into one governed workflow. Once that happens, the line between “finance software” and “payment infrastructure” starts to disappear.

Break: Expense software stops being a record-keeping layer once payment credentials, policy enforcement, and agent execution converge into one commercial control system.

Sources: Hyper deal

Proof of human moved from logins into delegated commerce and agreements

On 17 April, World expanded its proof-of-human infrastructure into agentic workflows and enterprise trust surfaces. Its announcements tied World ID to agent workflows through AgentKit, human-in-the-loop execution with Vercel, planned Human Principal enforcement with Okta, and human continuity inside document signing through Docusign. The most important line in the stack is simple: actions performed directly or through delegated agents must still tie back to a verified human.

That matters because identity in AI commerce is no longer just an access question. It is becoming a continuity question. A normal login tells a system that an account exists and a session was opened. It does not prove that a real human remains behind a chain of delegated actions, especially once agents start acting asynchronously across tools, merchants, and documents. World’s move shows where the market is going next. Verification will need to survive delegation. Human presence will need to be attestable even when the human is not actively clicking. The second-order implication is that future commerce trust may depend less on who owns the interface and more on who can issue portable proofs that a human stood behind the permission, the action, and the resulting commitment.

Break: Login stops being enough once buying, signing, and approving can all be delegated. The winning credential is not access, it is provable human continuity.

Sources: World ID

Merchant legitimacy is starting to move from webpages into protocol

Also on 17 April, a new IETF Internet-Draft, AGTP Merchant Identity and Agentic Commerce Binding, tried to solve what it explicitly calls the “merchant identity gap.” The draft argues that AGTP already governs the sending side of agentic transactions, such as agent identity and authority scope, but the merchant side lacks equivalent protocol-level identity and verification. Its proposed answer is a merchant manifest, merchant birth certificate, merchant trust tiers, intent assertion headers, cart digest, dual-party attribution, and even a 455 Counterparty Unverified status code. It also requires agents with purchase authority to verify merchant lifecycle state, manifest signatures, and trust tier before executing a purchase.

This is one of the strongest signals of the week because it makes a hidden assumption explicit. In human commerce, a merchant’s legitimacy could be inferred from brand familiarity, page design, browser trust, and user judgment. In agentic commerce, that model does not scale. Agents need machine-checkable counterparty identity before they buy. If this line of protocol work gains traction, then merchant verification will start to resemble API security and certificate infrastructure more than storefront branding. The second-order implication is severe for merchants and platforms. Being discoverable to agents will not be enough. Being verifiable to them will become a separate requirement, with its own governance, failure states, and exclusion risk.

Break: A merchant URL stops being a sufficient signal of legitimacy when agents spend money. Counterparty verification is moving from page trust to protocol trust.

Sources: IETF draft

AEON360 showed what delegated commerce looks like when retail and finance share one operating context

On 16 April, AEON360 and Google Cloud announced a multi-year collaboration to build what they call “continuous commerce” across AEON’s retail, finance, and lifestyle ecosystem in Southeast Asia. The system is designed around a unified data foundation, an enterprise knowledge graph, shopping and customer service agents grounded in shared context, financing and rewards integrated into the journey, and future agent-led transactions tied to Google Wallet. AEON360 also said the roadmap extends beyond owned properties through the Universal Commerce Protocol.

This is not just a personalization story. It is a control story. The deeper significance is that AEON is trying to keep identity, preference, inventory, financing eligibility, loyalty status, and transaction consent inside one persistent operating context that can follow a shopper from discovery to post-purchase support. That is a very different architecture from traditional retail, where discovery, checkout, payments, and service often sit in disconnected systems. The second-order implication is that ecosystems with both commerce and financial relationships may gain an outsized advantage in agentic markets, because they can make higher-confidence decisions and execute more steps without forcing the user to reassert context or intent at every turn.

Break: Personalization stops being the right frame when the same system can carry identity, financing, rewards, consent, and execution through the full commercial journey.

Sources: AEON360

The System That Is Emerging

The hidden system layer beneath this week’s announcements is a shift from machine-readable commerce to machine-authorized commerce. Last week, the market focused on making merchants legible to systems. This week, the more difficult problem came into view. Once systems can act, the market needs a transaction-grade chain of authority. That chain has at least four parts: proof of the human principal, proof of the acting agent, proof of the merchant counterparty, and proof of the intent or policy under which the action took place. The companies that can bind those four parts together are not just adding trust features. They are building the operating logic for delegated commerce.

This matters because control is starting to move away from whichever platform wins discovery and toward whichever system can keep the authority chain intact across the full lifecycle of a transaction. That changes who has leverage. It benefits issuers with network visibility, enterprise identity layers that can survive delegation, protocols that can verify both sides of a transaction, and ecosystems that already combine commerce, payments, and loyalty under one governed context. It weakens the old assumption that better recommendations or smoother checkout will be enough. In machine-led commerce, execution without proof creates downstream cost. The more autonomous the agent becomes, the more expensive that missing proof becomes.

Core Truth: In delegated commerce, durable power will sit with the system that can prove who authorized the action, which merchant was verified, what intent governed the purchase, and who carries the liability when the machine executes.

What operators should take from this now is straightforward:

  • Trust is becoming transactional infrastructure, not a policy page.
  • Identity is shifting from account access to delegated continuity.
  • Merchant inclusion will increasingly depend on verification, not just integration.
  • Payment rails are moving closer to intent capture, policy enforcement, and dispute evidence.
  • Retail ecosystems with finance, loyalty, and consent data in one loop will be able to execute more, with less friction and more confidence.

Tool of the Week World AgentKit

World’s AgentKit matters because it gives developers a practical way to bind agent actions back to a verified human and to insert human verification into workflows when it matters most. At system level, that is not a convenience feature. It is one of the first developer-facing primitives for making delegation auditable instead of implicit. In a market moving toward machine-led purchasing, approval, and agreement execution, tools that can preserve human continuity across delegated action will become foundational.

Source: AgentKit

Trend to Watch

Delegated spend will become tiered, not binary

The next pattern to watch is the emergence of permission tiers for machine-led transactions. This week already showed the ingredients: registered agents, spend controls, proof-of-human layers, merchant trust tiers, intent assertions, and protected versus unprotected transaction classes. That points toward a market where agents will not simply be “allowed” or “not allowed” to transact. They will be underwritten. Some will be permitted to research, some to build carts, some to commit within narrow budgets, and only a smaller set to complete higher-risk transactions under stronger verification and liability conditions. The infrastructure for tiered machine authority is starting to appear before most merchants have even adapted to AI discovery.

The important update from this week is that AI commerce is no longer only a discovery story and no longer only an infrastructure formatting story. The market is beginning to answer the harder question of how machines will be permitted to act inside commercial systems without breaking trust, policy, and accountability. That is the layer that decides whether agentic commerce stays a collection of demos or becomes a durable operating model. The actors building this layer are not all the same. Some are networks trying to own liability and intent. Some are identity providers trying to preserve human continuity. Some are protocol builders trying to formalize counterparty trust. Some are ecosystems trying to keep context, finance, and consent in one loop. But they are all converging on the same problem.

That is why this layer deserves close attention in the weeks ahead. Once the market starts assigning transaction privileges based on provable authority chains, a new hierarchy will form. Some merchants will be legible but not trusted. Some agents will be useful but not authorized. Some platforms will drive intent but not control execution. OZ Signals will keep tracking that split, because the next phase of AI commerce will not be decided by who can generate the most shopping interactions. It will be decided by who can make machine action governable, defensible, and economically safe at scale.

Box Hill (Sydney), NSW 2765, Australia
Unsubscribe

OZ Signals

OZ Signals is a weekly intelligence briefing on how AI is restructuring commerce systems. Built for founders, operators, and decision-makers who want high-signal insights, not noise.

Read more from OZ Signals
Minimal editorial diagram showing a shopping cart at the center connected to product data, ads, payments, checkout, and merchant tools.

OZ Signals May 26, 2026 View in browser When the Cart Became the Control Layer Issue 9 tracked the rise of the implementation layer, where agencies, enterprise systems, storefront builders, and deployment partners started making AI commerce installable inside real businesses. That mattered because AI commerce was no longer only a platform announcement. It was becoming something merchants could actually connect, configure, and operate. Issue 10 moves one layer deeper. The week of 19 May to 25...

Minimal editorial image showing AI commerce moving from concept into implementation through storefronts, agencies, assistants, and operational systems

OZ Signals May 19, 2026 View in browser AI Commerce Is Moving Into the Implementation Layer Last week’s issue showed that AI commerce is moving beyond checkout into fulfillment, logistics, service, and post-purchase systems. This week explains the next layer: implementation. The market is no longer only experimenting with AI commerce. It is beginning to build the infrastructure required to deploy it across real businesses. That shift matters because most retailers are not limited by awareness...

Minimal editorial image showing an AI commerce loop moving from intent to payment, then into fulfillment, service, clienteling, and post-purchase support.

OZ Signals May 12, 2026 View in browser The Transaction Is No Longer the End of Commerce Last week’s issue showed that the payment layer is becoming the execution layer. Once AI systems can select what to buy, the next structural question is how they receive controlled authority to spend. That layer matters because agentic commerce cannot scale if agents can recommend products but cannot safely complete the transaction. This week moves one step further. Once payment becomes executable, the...