智能體商務協議如何保障交易安全?
How Do Agentic Commerce Protocols Secure a Transaction?
智能體商務協議透過分層授權、付款執行、訂單與交付證據、爭議裁決及結算驗證,讓交易可供核查;付款成功本身不能證明貨品符合規格。SAAX旨在配合 MCP、A2A、AP2、x402、ACP 及 EAS,記錄協議承諾、證據、爭議流程和結算授權,而非取代它們。SAAX目前在 Base 主網支援即時 x402 付款,託管僅限測試網,且尚未完成獨立審計。
Originally published on the SAAX Protocol site: https://saax-protocol.com/blog/agentic-commerce-security
An agentic commerce protocol is a defined set of rules and interfaces that let AI agents discover, authorize, pay for, and track commercial transactions in a machine-verifiable way. The security question is not "can agents act?" — it is "how do we know the right agent acted, within the right limits, for the right purpose, and that the outcome can be verified afterward?"
The scenario: payment succeeds, then the agent times out
A plant's procurement agent ordered a replacement filter. Payment succeeded — USDC moved from buyer to seller via x402. Then the agent's process times out and dies. The buyer later disputes the shipment: the part number is right, but the filtration rating is wrong.
This is the case that separates agentic commerce security from ordinary payment security. The payment was authorized. The money moved. The dispute is about fulfillment.
What each system actually verifies
- Authorization (AP2 mandates): the agent had permission to pay. Not: that the delivered goods matched.
- Payment confirmation (x402): value moved. Not: that the correct filter shipped.
- Order evidence (durable commitment): the terms of the agreement, durably recorded. Not: that the seller performed.
- Delivery evidence: something was delivered. Not: that it matched the specification.
- Dispute authority: the decision came from the authorized evaluator. Not: that the decision is factually correct.
- Evaluator fallback: a preauthorized fallback exists, bound by the same rules. A timeout alone never authorizes release or refund.
- Financial enforcement (custody contract): the on-chain effect matches the authorized decision; forged or replayed settlement is rejected.
- Settlement verification: the transfer actually confirmed on-chain. Not: that the physical filter conforms.
Why a payment receipt cannot prove delivery
A payment receipt proves a transfer occurred — amount, asset, sender, recipient, hash. It is not evidence of fulfillment. A signature proves who signed, not that the claims are true. A hash proves a file wasn't altered, not that its contents are accurate. An EAS attestation anchors a claim on-chain; it does not independently establish that the physical event occurred. A transaction submission proves an attempt, not settlement.
Token terminology: three different "tokens"
- Authorization credentials (AP2 VCs, OAuth, JWTs) — prove permission to act; not value.
- Tokenized payment credentials (card tokens) — enable payment; not the payment itself.
- Blockchain assets (USDC) — the value being transferred.
These are not interchangeable. Confusing them is how agentic commerce vulnerabilities happen.
How the protocol layers complement each other
MCP connects agents to tools; A2A connects agents to agents; AP2 authorizes agent payments; x402 executes machine-native payments; ACP defines agentic checkout; EAS anchors evidence. SAAX is designed to complement these — recording the durable commitment, evidence trail, dispute lifecycle, and settlement authorization around them. It is not a replacement for any of them.
Where SAAX stands today
See the SAAX status page: immediate x402 payments on Base mainnet; escrow testnet-only; Financial Recovery Engine custody candidates local-only; no independent audit completed. The specification and conformance suite document the commitment lifecycle, evidence interface, authorization model, and settlement linkage.
Sources
- AP2 — specification and repository.
- x402 — specification v2 and x402.org.
- ACP — agentic-commerce-protocol repository.
- MCP — official specification.
- A2A — a2a-protocol.org.
- EAS — attest.org and EASScan.
- Ecosystem registry — agenticcommerceprotocol.info.
AI disclosure: This article was developed with AI assistance and reviewed by the SAAX team. Claims about external protocols are sourced from official documentation linked in the text; SAAX status claims reflect the published status page. Nothing here is an independent audit, certification, or production-custody approval.
Next step: read the protocol overview and the security page, then try the public preflight and acceptance flow.
來源:DEV Community · dev.to