Merchant readiness for agentic commerce

Expose commercial truth, not marketing fragments

Agents need structured product identity, price, inventory, variants, shipping, tax inputs, return terms, and final order totals. A model scraping a visual page is a weak substitute for an explicit catalog or checkout interface.

Make changed terms machine-visible and versioned. The agent should be able to freeze an order snapshot with an expiry before requesting authorization.

Recognize agents without trusting them blindly

Signed agent requests and network registration can distinguish known commerce agents from anonymous automation. Verify signatures, timestamps, nonces, covered request components, and current keys. Then feed the verified result into merchant policy and fraud systems.

Recognition is an input, not an allowlist bypass. Preserve the agent and principal signals through order, payment, fulfillment, analytics, and support so downstream teams understand the channel.

Make checkout deterministic and idempotent

Provide create, update, complete, and cancel operations with durable identifiers. Return machine-readable errors. Support idempotency on completion. Reject a credential that does not match seller, amount, currency, order, or expiry.

Avoid hidden state that only exists in a browser cookie. Agent clients may resume from another process or reconnect after a payment result is lost.

Extend the agent channel past authorization

A completed payment still needs order confirmation, inventory commitment, fulfillment, delivery, cancellation, partial refund, full refund, and dispute handling. Publish status operations or events and connect them to the original order and payment references.

Train support teams to recognize agent-led orders, locate mandate or agent evidence, and explain recourse to the principal. Do not send the user back to an agent that cannot access merchant support state.

Merchant readiness scorecard

A merchant is ready when each layer has an owner, interface, and tested failure path.