From ap2-agentic-payments
Implements AP2 Payment Mandate VDC to signal AI involvement and user authorization in payments. Guides schema fetch, construction for merchant processors in auth flows, tokenization.
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 Payment Mandate schemasite:github.com google-agentic-commerce AP2 payment mandate for type definitionssite:github.com google-agentic-commerce AP2 src/ap2/types payment for Python typeshttps://ap2-protocol.org/topics/core-concepts/ for Payment Mandate conceptual detailsThe Payment Mandate is a separate VDC specifically for the payment ecosystem — shared with payment networks (Visa, Mastercard) and issuers (banks). Unlike the Cart/Intent Mandates that focus on purchase authorization, the Payment Mandate provides visibility into the agentic nature of the transaction.
The Payment Mandate serves three functions:
The Merchant Payment Processor (MPP) constructs the Payment Mandate from the transaction information after the user has authorized the purchase. The Shopping Agent does not create the Payment Mandate — it is assembled on the MPP side from the payment context.
{
"payment_mandate_contents": {
"payment_mandate_id": "pm_unique_id",
"payment_details_id": "order_id",
"payment_details_total": {
"amount": {
"currency": "USD",
"value": "29.99"
},
"refund_period": 30
},
"payment_response": {
"request_id": "order_id",
"method_name": "CARD",
"details": {
"token": "dpan_token_xyz"
},
"shipping_address": null
},
"merchant_agent": "MerchantAgentName",
"timestamp": "2025-09-01T12:00:00Z"
},
"user_authorization": "eyJhbGc..."
}
1. User authorizes purchase on trusted device surface
2. Shopping Agent sends Cart Mandate + user attestation to Merchant
3. Merchant submits payment to Merchant Payment Processor (MPP)
4. MPP constructs the Payment Mandate from the transaction context
5. MPP requests payment credentials from Credentials Provider (CP)
6. CP verifies and performs tokenization (if needed)
7. CP returns credentials to MPP
8. Network/Issuer evaluates the mandate for risk assessment
9. Payment authorized (or challenged)
The Payment Mandate includes a tokenized payment method (DPAN — Digitized Primary Account Number):
All three work together: the Cart/Intent Mandate proves the purchase is authorized; the Payment Mandate proves the payment is authorized and provides network visibility.
The refund_period field in the mandate specifies the refund window (in days). This is important for:
Fetch the specification for exact Payment Mandate fields, token formats, and network integration requirements before implementing.