From ap2-agentic-payments
Implements AP2 challenge flows: 3DS2, OTP verification, redirects to trusted surfaces for step-up auth in agentic payment processing.
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 challenge flow specificationsite:github.com google-agentic-commerce AP2 challenge OTP 3DS step-up for implementation exampleshttps://ap2-protocol.org/topics/privacy-and-security/ for security contextap2 protocol 3DS2 OTP challenge redirect for integration detailsChallenges are additional authentication steps that any participant in the payment ecosystem can require during an AP2 transaction. They provide an extra layer of security beyond the mandate signatures.
Any ecosystem participant may trigger a challenge:
AP2 V0.1 supports redirect challenges:
1. Payment processing initiated
2. Network/Issuer determines challenge required
3. Challenge request returned to MPP
4. MPP sends challenge to Merchant Agent
5. Merchant Agent forwards to Shopping Agent (via A2A)
6. Shopping Agent redirects user to trusted surface
7. User completes challenge (enters OTP, completes 3DS)
8. Trusted surface confirms completion
9. Shopping Agent receives confirmation
10. Flow resumes from where the challenge was triggered
The redirect challenge follows this pattern:
Why redirect? Agent conversations are not trusted surfaces for authentication. The challenge must happen on a system controlled by the challenging entity.
Why A2A messaging? The challenge request and completion notification flow through the A2A protocol, keeping the multi-agent orchestration consistent.
Duplicate prevention: The protocol ensures that if one entity has already challenged the user, others are informed to avoid duplicate challenges.
The reference sample implements OTP:
For 3DS2 (Strong Customer Authentication):
AP2 challenges are backward compatible with existing systems:
Fetch the specification for exact challenge message formats, redirect protocols, and completion callback schemas before implementing.