Provenance does not establish trust
The UCP 2026-08-25 specification binds namespaces to schema origins. It explicitly distinguishes provenance from the entity’s trustworthiness. The client decides what to trust and support. The protocol also separates selection of a shared protocol version from capability negotiation.
AP2: verify mandates according to role
The AP2 v0.2 specification distinguishes Checkout Mandates, Payment Mandates and their receipts. Role-specific validation must execute in deterministic code. Catalog and commerce APIs remain outside its scope. Intent evidence does not replace checking order and payment state.
An answer is not evidence of an action
The Ask capability must answer without changing resources. It cannot edit a cart or reserve stock. A platform must not treat its response as evidence an operation occurred. We recommend reading the state from the capability that owns the operation before reporting success.
Test rejected requests
We recommend testing incompatible versions, missing permissions, repeated operations, missing information and declined payments. For Shopify, use the current access matrix, which excludes Checkout MCP from Anonymous access. Set request limits for the implementation and its workload, without attributing a universal threshold to UCP.
Retention follows the processing purpose
GDPR Article 5, reproduced by the CNIL, limits identifiable data retention to what the purposes require, subject to its exceptions. UCP does not establish one legal retention period for all logs. Determine the applicable legal basis and obligations for each processing activity.
Review after specification or access changes. This analysis does not certify the security of an individual implementation.