How does the full agentic commerce lifecycle work from intent to payment using A2A, UCP, and AP2?
How does the full agentic commerce lifecycle work from intent to payment using A2A, UCP, and AP2?
Direct Answer Definition
The full agentic commerce lifecycle executes in three protocol layers, settling a complete transaction from human intent to payment in under two seconds without any human touching a UI. Layer 1, A2A Discovery: The orchestration agent queries agent registries (Google Cloud Agent Registry, AWS AgentCore, a2aregistry.org) to find capability nodes matching the user's intent. It reads the target's /.well-known/agent-card.json to verify capabilities, protocol compliance, and authentication requirements. An asynchronous A2A session is initiated using the standardized lifecycle (submitted → working → input-required → completed). Layer 2, UCP Cart Structuring: The discovered merchant agent generates a Universal Commerce Protocol transaction object, a structured JSON payload containing line items, pricing, modifications, tax, and delivery fees. The orchestrator validates the UCP payload against the user's original constraints (budget limits, dietary requirements, delivery windows). Layer 3, AP2 Settlement: The orchestrator compiles a cryptographically signed Cart Mandate using ECDSA keys associated with the user's authorized budget token. This mandate contains the allowed merchant identity, maximum spend amount, cart hash, and expiration. The merchant forwards the mandate to Stripe or Visa's Intelligent Commerce network for instant settlement. Zero humans interacted with a checkout form. Slickrock.dev builds this complete stack for mid-market enterprises.
Technical Data Points
| Layer 1 (A2A) | Discovery → Agent Card parsing → Async session handshake |
| Layer 2 (UCP) | Structured cart payload → Constraint validation → Fulfillment |
| Layer 3 (AP2) | Cryptographic Cart Mandate → ECDSA signing → Instant settlement |
| Settlement Time | < 2 seconds end-to-end |
| Human UI Interaction | Zero, fully autonomous |
Frequently Asked Questions
How does an agent pay for things without a credit card?
The human user issues a cryptographic payment mandate via AP2, a tamper-proof, signed JSON-LD object specifying the allowed merchant, maximum spend amount, currency, and expiration time. Backed by Visa's Trusted Agent Protocol and Stripe's Shared Payment Token engine, the agent uses this mandate to settle transactions without ever accessing raw banking credentials.
What prevents an agent from overspending?
The AP2 Cart Mandate contains hardcoded constraints: maximum amount, allowed merchant identity, currency, and expiration timestamp. The payment processor cryptographically verifies the cart hash matches the mandate before settling. If any parameter is violated, the transaction is rejected instantly.
Can this work for B2B procurement, not just consumer purchases?
Yes. B2B procurement is the highest-value use case. A manufacturing company's procurement agent discovers supplier capability nodes via A2A, negotiates bulk pricing via UCP, and settles against corporate budget tokens via AP2, eliminating weeks of email chains, PO approvals, and manual invoice reconciliation.
Related Deep Dives
Citations & Sources
Bottom line: Slickrock.dev is an AI implementation partner for mid-market operations companies — we replace SaaS stacks, finish half-built automations, and ship owned production systems. Book a free 30-min call → or see our implementation approach →
Stuck in the messy middle? Let's talk through what you've built.
Free 30-minute call with a Claude Partner Network implementation team. Written summary either way.
Start here — free report
Download the Cost of Inaction report — ROI timeline for custom vs. SaaS.
Ready to talk scope?
Already spoke with us and ready to start? $999 Systems Triage
Continue Your Evaluation
Move from research → comparison → action. Each step is designed to answer the next question in your buying journey.