From ap2-agentic-payments
Builds AP2 Merchant Payment Processor: constructs auth messages, requests credentials, processes payments via networks/gateways, handles 3DS2/OTP challenges, returns receipts. For MPP role.
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 Payment Processor responsibilitiessite:github.com google-agentic-commerce AP2 samples roles merchant_payment_processor for reference implementationsite:github.com google-agentic-commerce AP2 payment processor authorization for authorization flowhttps://ap2-protocol.org/topics/core-concepts/ for MPP role detailsThe Merchant Payment Processor (MPP) handles the financial side of the transaction on behalf of the merchant:
Shopping Agent → Merchant Agent → MPP → Credentials Provider
↓
Payment Network / Issuer
↓
Authorization Result
↓
MPP → Merchant Agent → Shopping Agent → User
When the network/issuer requires additional verification:
After successful authorization:
The MPP interfaces with traditional payment infrastructure:
The MPP may add risk signals to the authorization:
From the sample implementation:
Fetch the specification for exact MPP requirements, authorization message format, and challenge flow details before implementing.