Help us improve
Share bugs, ideas, or general feedback.
From ap2-agentic-payments
Implements AP2 VDC framework with tamper-evident signed credentials for agentic payments. Covers issuance, verification, holder binding, SD-JWT format, and mandate types.
npx claudepluginhub orcaqubits/agentic-commerce-skills-plugins --plugin ap2-agentic-paymentsHow this skill is triggered — by the user, by Claude, or both
Slash command
/ap2-agentic-payments:ap2-vdc-frameworkThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Fetch live docs**:
Implements AP2 cryptographic signing: hardware-backed user/merchant signatures, VDC integrity, key management, attestation flows. Use for AP2 mandate signing/verification.
Implements UCP AP2 Mandates for autonomous agent payments using SD-JWT credentials, JWS merchant signatures, and Agent Payments Protocol in 7-step flow with security lock.
Provides ACP patterns for idempotency, error handling, 3D Secure flows, request signing, rate limiting, monitoring, and security best practices. Use when designing architecture or addressing production issues.
Share bugs, ideas, or general feedback.
Fetch live docs:
https://ap2-protocol.org/specification/ for the VDC framework specificationhttps://ap2-protocol.org/topics/core-concepts/ for VDC conceptual overviewsite:github.com google-agentic-commerce AP2 src/ap2/types mandate for VDC type definitionsap2 protocol verifiable digital credentials VDC for community guidesVerifiable Digital Credentials (VDCs) are tamper-evident, portable, and cryptographically signed digital objects that serve as the trust building blocks for AP2 transactions. They provide:
AP2 VDCs use the SD-JWT with Key Binding (+kb) format, enabling selective disclosure and cryptographic holder binding.
JSON payloads are canonicalized using JCS (RFC 8785) before signing to ensure deterministic serialization.
1. Creation → Mandate generated (by Merchant for Cart, by SA for Intent)
2. Signing → User signs with hardware-backed device key
3. Presentation → Mandate presented to verifying party
4. Verification → Signature and contents validated
5. Usage → Mandate used to authorize payment
6. Archival → Mandate stored for dispute resolution/audit
Every VDC follows a common structure:
The VDC trust model involves:
AP2 VDCs align with W3C standards:
Cart Mandates receive both merchant authorization (a detached JWS JWT) and user signature (hardware-backed device key), forming a dual-authorization model.
To verify a VDC:
Fetch the specification for exact VDC schemas, signature formats, and verification algorithms before implementing.