Agent Payments Protocol · AP2 Support
Proof for every agent transaction
When an agent checks out for a user, you need to know it was authorized. With Truvera you can issue and verify AP2 mandates that create verifiable proof of what an AI agent was authorized to do on a user's behalf. Start testing trusted agentic commerce flows today.
Agent Payments Protocol · AP2 V0.2 Support
Two mandate credentials.
Verifiable transaction evidence.
AP2 v0.2 uses two mandate credentials cryptographically linked to the checkout and payment flow. Together with receipts, they turn "the agent said the user approved it" into evidence any party can verify, so a disputed transaction has an answer instead of a guess.
Why AP2 exists
Payment rails were built for humans. Agents break three assumptions at once.
You can't prove authorization
How can a merchant verify that the user granted the agent authority for this purchase? Standing instructions do not create a portable, cryptographically verifiable link between the user’s intent and the agent’s action.
AP2 mandates provide verifiable evidence of what the user authorized.
You can't confirm intent
How can anyone confirm that the agent’s request reflects the user’s actual intent rather than an error, hallucination or manipulated instruction? Traditional payment infrastructure does not carry standardized evidence of the instructions given to an AI agent.
Mandate signatures and transaction binding allow the relevant parties to verify the authorization, checkout and payment.
You can't settle disputes
If a transaction is disputed, how can the parties establish what the user authorized and what the agent did? Without a shared protocol, there may be no common, interoperable record that all parties can verify.
Checkout and Payment Mandates and Receipts provide verifiable evidence that can support audits and disputes.
Truvera Capabilities
Everything you need to run AP2, without building any of it.
Whether you're a PSP, wallet provider, merchant platform, or agent developer, Truvera provides you the tools to issue, verifie, and manage AP2 mandates, so your team ships agentic commerce instead of researching it.
AP2 mandate issuance via MCP
Truvera's Wallet MCP handles the creation and signing of open and closed Checkout and Payment Mandates, including selective disclosure and the cryptographic links between the user’s authorization, checkout and payment. Teams can begin issuing AP2 mandates within minutes of MCP onboarding.
Real-time verification
Through Truvera's API or MCP, you can verify mandate signatures and the integrity of the full mandate chain. In autonomous flows, it also validates that the mandate is bound to the authorized agent and that the final checkout and payment match the constraints approved by the user.
Native MCP integration
Truvera exposes AP2 mandate issuance and verification as MCP tools. Once connected, MCP-compatible agents can use these capabilities directly within their workflows, without requiring a separate custom integration for each agent.
AP2 v0.2-compatible formats
Truvera supports the mandate formats and versioning defined by AP2 v0.2, reducing the need for teams to implement the underlying credential structures themselves.
Enterprise-ready infrastructure
Truvera provides multi-tenant infrastructure and audit logging designed for organizations operating in financial services, payments and other regulated environments.
Spec tracking built in
As AP2 and the FIDO Alliance’s emerging agentic-commerce specifications evolve, Truvera updates its tooling to support new versions, reducing the need for teams to track and implement every change themselves.
Build vs buy
Start testing in minutes, not building for a quarter
Building AP2 v0.2 support involves more than issuing a standard credential. Teams must manage mandate signing, selective disclosure, agent authorization, transaction binding, constraint evaluation, versioning and signed receipts.
Building in-house
Mandate signing and selective disclosure
Agent authorization and key binding
Open-to-closed mandate processing
Checkout and payment transaction binding
Mandate versioning and signed receipts
Building on Truvera
Managed AP2 mandate issuance and verification
Open and closed Checkout and Payment Mandates
Verification of signatures, transaction links and constraints
MCP tools for agent workflows
Begin issuing AP2 mandates within minutes of MCP onboarding
The trust layer for agentic commerce is being built now.
AP2 is still evolving, but v0.2 provides a practical implementation baseline for teams that want to begin testing today. The organizations experimenting now will be better prepared to understand how mandates fit into agents, wallets, checkout flows and payment infrastructure as the ecosystem develops.