An AI can shorten product discovery. It can search, compare a few candidates and make missing conditions visible. That does not make the rest of a commerce workflow disappear.
The operational question is straightforward: when the customer decides to proceed, which person owns the next action?
At WebAZ, we use the scoped OAuth order-request path as one concrete example. It produces an approval URL for a human to review and confirm with a Passkey. This approval queue is not the same as general account-key order creation.
For that path followed by Direct Pay, the handoffs are:
| State | Buyer action | Seller action | What WebAZ records |
|---|---|---|---|
| Product discovery | Inspect product facts and unresolved conditions | Keep listing facts clear | Public discovery result |
| Order approval | Review exact item, amount and route; confirm with a Passkey | — | Approved intent / order state |
| Payment handoff | Pay the seller directly by the chosen off-platform method | Publish the current payment instruction | Payment-information snapshot |
| After payment | Submit relevant evidence if needed | Acknowledge and update fulfillment | State changes and evidence |
This is not just documentation polish. It prevents a common agent-commerce mistake: treating a payment-shaped event as proof that a merchant accepted the order, inventory is reserved or delivery is complete.
WebAZ is non-custodial on Direct Pay. It does not hold the payment principal, verify the payment method or payee, guarantee payment or delivery, or issue a seller refund. It records the handoff so the customer and seller can see what is expected next.
The broader lesson applies beyond one product: an agent should be able to say what it knows, what it does not know, and who must act before the workflow can advance.
WebAZ's reviewed shopping surface is available for public product discovery at https://webaz.xyz/#discover. Registration is invite-gated; browsing does not require an invite.
Top comments (0)