Case Studies and Extensions
10.1 UCP Extension Mechanism
Beyond its core capabilities, UCP defines an extension mechanism. Extensions are associated with core capabilities through namespaces and participate in dependency pruning during capability negotiation.Buyer Consent Extension
Namespace:dev.ucp.shopping.buyer_consent
This extension enables merchants to obtain buyer privacy consent during the checkout flow, in compliance with regulations such as GDPR and CCPA:
| Dimension | Meaning | Default |
|---|---|---|
analytics | Allow data to be used for analytics | Requires explicit consent |
preferences | Allow saving user preferences | Requires explicit consent |
marketing | Allow marketing communications | Requires explicit consent |
sale_of_data | Allow sale of personal data | Requires explicit consent |
buyer_consent extension, the AI agent must present consent options to the consumer and collect explicit consent or refusal. A boolean value of true indicates consent; false indicates refusal.
Dependency: buyer_consent depends on the checkout capability. If checkout is not included in the negotiation result, buyer_consent is automatically removed during the pruning step.
AP2 Mandate Extension
Namespace:dev.ucp.shopping.ap2_mandate
This extension adds cryptographic binding to the payment flow, ensuring non-repudiation of payment authorizations:
Core mechanisms:
- JWS Detached Signatures: Uses JSON Web Signature in detached mode, where the signature is transmitted separately from the payment request body
- SD-JWT+kb Credentials: Selective Disclosure JWT with Key Binding, allowing buyers to disclose only the minimum information required to complete a transaction
ap2_mandate depends on both checkout and identity_linking. If either is missing from the negotiation result, ap2_mandate is pruned.
10.2 Case Study 1: Quick Onboarding for a Shopify Merchant
Background: A Shopify merchant with 500 SKUs wants AI agents to recommend products and complete checkout. Strategy: Leverage Shopify’s existing API foundation and deploy a UCP Profile via a proxy. Steps:- Deploy the UCP Profile (30 minutes)
/.well-known/ucp via a Shopify App Proxy or a standalone service:
- Product catalog adaptation (2 hours)
- Checkout integration (1 day)
- Testing and validation (2 hours)
10.3 Case Study 2: Full Integration for a Custom-Built Store
Background: A Node.js custom-built store with 2,000 SKUs, a PostgreSQL database, and existing Stripe payment integration. Phase 1 — Profile + Product Catalog (1 day)- Deploy an OAuth 2.0 authorization server (consider using an existing library such as
oidc-provideroroauth2-server) - Publish
/.well-known/oauth-authorization-server - Generate an ES256 key pair and publish the public key in the Profile’s
signing_keys
- Order query API
- RFC 9421 signed Webhook notifications
- Return / refund adjustment API
10.4 Case Study 3: WooCommerce Cloudflare Worker Adapter
Background: A WooCommerce store with 800 SKUs, looking to integrate UCP with minimal effort. Solution: Deploy a Cloudflare Worker as a UCP adapter layer.- No modifications to WooCommerce itself; the Worker is independently deployed
- Global edge nodes for low latency
- Can be toggled on or off without affecting the existing website
- CF Worker Secrets can securely store signing private keys
10.5 Recommended Integration Priority
Regardless of your platform, follow this sequence:| Phase | Work | Time | Outcome |
|---|---|---|---|
| 1 | /.well-known/ucp Profile | 1 hour | AI agents can discover you |
| 2 | Product catalog API | 1 day | AI agents can search and display products |
| 3 | Checkout capability | 2-3 days | AI agents can complete purchases |
| 4 | Identity linking | 2-3 days | Personalized shopping experiences |
| 5 | Order management + Webhooks | 2 days | Full post-purchase support |
| 6 | Extensions (Consent / AP2) | 1-2 days | Compliance and advanced payment |
10.6 Ecosystem Collaboration
UCP’s 30+ ecosystem partners mean:- Payments: Declare supported processors via
payment_handlers(Stripe, Adyen, PayPal, Klarna, etc.). AI agents automatically negotiate the optimal payment method. - Buy now, pay later: Affirm and Klarna, as UCP partners, are expected to provide standardized installment payment processors.
- Retailers: Support from major retailers like Best Buy, Target, and Walmart means AI agents can compare prices and make purchases across merchants.
- Card networks: Participation from Visa and American Express ensures financial compliance in payment token exchange.
Congratulations on completing Book 3. You now understand the full technical architecture of the UCP protocol — from
/.well-known/ucp Profile discovery and capability negotiation, through the four core capabilities (Checkout, Identity Linking, Order Management, and Payment Token Exchange), four transport mechanisms (REST, MCP, A2A, and Embedded), to RFC 9421 signatures and JWK key management.
Recommended next steps:
- Learn about AI agent ordering protocols — Book 4: ACP Protocol
- Build an MCP Server — Book 5: MCP Protocol
- Optimize AI visibility first — Book 6: SEO for AI
- Use templates directly — Templates and Prompts
Suggested next: ACP Agentic Commerce Protocol — Learn about the AI agent checkout and payment standard created by Stripe More case studies: OTR Case Studies | ACP FAQ | MCP Case Studies