WebAZ 驗證 x402 訂單付款：購物智能體超越商品搜尋

A shopping agent should be able to do more than return product links. It should be able to move an authorized purchase into a paid order, with a result the merchant can verify.

WebAZ's agent x402 payment path has now been exercised with completed order payments. We checked the corresponding authenticated order views: they showed x402 on-chain verification, a settlement event, and a transition out of awaiting payment.

This is a payment-path validation milestone, not a claim about independent customer adoption or completed delivery. The operator reported agent execution; the internal check verified the payment rail and recorded settlement. We are not publishing order records or transaction details.

Paying for an order, not for a search response

In this integration, x402 pays an eligible Direct Pay order. It is not a charge for querying the product catalog.

The current flow uses USDC on Base mainnet. Direct Pay is non-custodial: payment goes to the seller's receiving address, and WebAZ records and verifies settlement without holding the principal. Payment verification does not verify delivery or establish the seller's trustworthiness.

The following integration details describe the current public contract, rather than additional tests performed for this post.

The boundary that matters: an exact order

1. Discover and compare products, then obtain a quote with the available payment methods.
2. Create an eligible order using its x402 receiving account. Seller acceptance may be required before payment becomes available.
3. Read the order's payment.x402.resource_url.
4. POST without a payment signature to receive HTTP 402 and PAYMENT-REQUIRED.
5. A wallet signs the exact EIP-3009 authorization, then repeats the request with PAYMENT-SIGNATURE.
6. Check the settlement response and order state before proceeding.

The amount and recipient in the payment requirement come from the order's frozen snapshot. A model-generated estimate is not a payment instruction.

Authorization is a separate concern

An account owner must enable agent autopay with a Passkey and set per-order, rolling 24-hour and rolling 30-day limits. A wallet-backed integration also needs the appropriate credential and funds.

The documented payment-only key has narrower access than a full account key, but it is still a payment-capable credential and must be protected. Its access includes eligible order creation, order reads and payment; it is not a general account-management credential.

OAuth/grant agents follow a different path: with payment:request, they can request a payment for owner approval. That permission alone does not let the agent sign or execute a transfer.

A timeout is not permission to pay again

The public contract distinguishes settlement in progress from failure. If a request times out or the endpoint returns a conflict, inspect the order and settlement state instead of creating another authorization.

The documented retry behavior returns the same result for the same signed request and refuses a second different authorization for the same order. Integrators should test these boundaries in their own controlled setup; a successful payment is not exhaustive failure-path coverage.

Looking for shopping-agent builders

We would like to work with developers who already have product discovery or comparison working and want to connect it to an explicit, bounded order-payment flow.

A useful first collaboration is small: start with read-only discovery, agree on the authorization model, and review how your agent represents payment success, uncertainty and owner handoff. Any live payment should be a separately authorized step, not an automatic consequence of trying the connector.

• x402 integration guide
• Agent entry points
• Agent Commerce Lab

Which part is hardest in your shopping agent today: binding a quote to payment, owner authorization, or recovering an uncertain settlement?

Disclosure: Published on behalf of WebAZ. This article was generated by an AI agent, which checked the public documentation and internal order-state evidence, with no human editing of the article. Private order and customer details are intentionally omitted.