From ap2-agentic-payments
Implements AP2 human-present transaction flow for interactive agentic checkout, guiding user confirmation of cart and payments via Cart Mandate with 11-step architecture.
npx claudepluginhub orcaqubits/agentic-commerce-skills-plugins --plugin ap2-agentic-paymentsThis skill is limited to using the following tools:
**Fetch live docs**:
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.
Fetch live docs:
https://ap2-protocol.org/specification/ for the human-present flow specificationsite:github.com google-agentic-commerce AP2 samples human-present for reference implementationshttps://github.com/google-agentic-commerce/AP2/blob/main/samples/python/scenarios/a2a/human-present/cards/README.md for the card payment samplehttps://ap2-protocol.org/topics/core-concepts/ for flow overviewIn a human-present flow, the user is actively engaged throughout the transaction. They review products, select items, choose a payment method, and confirm the purchase — all while interacting with the Shopping Agent.
The official AP2 specification describes approximately 11 high-level steps for the human-present flow. The primary VDC in this flow is the Cart Mandate.
Phase 1: Shopping Intent
1. User → Shopping Agent: Provides shopping prompt ("I want to buy a coffee maker")
2. SA → User: Confirms intent and collects CP preference + shipping address
Phase 2: Product Discovery
3. SA → CP: Queries Credentials Provider for available payment methods
4. SA → Merchant: Presents shopping intent
5. Merchant → SA: Creates and signs Cart Mandate(s) with product offers
Phase 3: User Confirmation
6. SA → User: Displays final cart + payment options
7. User → SA: Reviews cart, selects payment method, confirms on trusted device surface
Phase 4: Payment Processing
8. SA → Merchant: Sends confirmed Cart Mandate + user attestation
9. Merchant → MPP: Submits payment for processing
10. MPP: Constructs Payment Mandate and requests credentials from CP
Phase 5: Completion
11. MPP → Merchant → SA → User: Payment processed, receipt delivered
Each step involves A2A protocol communication:
The user is involved at these critical points:
Step 7 is a load-bearing security step:
During the flow, any participant may trigger a challenge:
Fetch the specification and sample implementations for exact message formats, mandate structures at each step, and agent communication patterns before implementing.