What is Mastercard Verifiable Intent?

An open-source cryptographic framework co-developed with Google that creates tamper-resistant proof of consumer authorization for AI agent transactions.

Why did Mastercard create Verifiable Intent?

Triggered by OpenClaw's security crisis — autonomous AI agents making purchases and accessing accounts needed a trust layer. 43% of CFOs expect high impact from agentic AI for budget reallocation.

Which companies back Verifiable Intent?

Google, Fiserv, IBM, Checkout.com, Basis Theory, Getnet, plus FIDO Alliance, EMVCo, IETF, and W3C standards bodies.

How does Verifiable Intent work?

It links three elements into a single immutable cryptographic record: the consumer's identity, their original instructions, and the outcome of the transaction. Uses Selective Disclosure to share only minimum info.

Where can I find the Verifiable Intent spec?

Available at verifiableintent.dev as an open-source specification.

← Back to dashboard

clawsmith.com/signal/mastercard-verifiable-intent-ai-agent-cryptographic-trust

📈 TrendsWide OpenStandardLive

Mastercard and Google Launch Verifiable Intent: Cryptographic Trust Layer for AI Agent Transactions

Mastercard and Google co-developed Verifiable Intent, an open-source cryptographic framework that creates tamper-resistant proof of consumer authorization for every transaction executed by an AI agent. Announced March 5 2026, backed by Google, Fiserv, IBM, Checkout.com, Basis Theory, and Getnet. Built on FIDO Alliance, EMVCo, IETF, W3C standards. Directly triggered by OpenClaw's security crisis — the framework addresses the trust gap when autonomous agents move money. Available at verifiableintent.dev.

Product Idea from this Signal

A middleware library that adds Mastercard Verifiable Intent cryptographic authorization proofs to self-hosted AI agent transactions

2 ▲

Mastercard and Google released the Verifiable Intent spec in March 2026 after the OpenClaw security crisis exposed that autonomous AI agents making purchases and API calls have no trust layer. The enterprise SDK exists, but self-hosted agent builders running OpenClaw, Hermes, or custom frameworks have no simple way to produce cryptographic proof that a human authorized each agent action. This middleware wraps any agent's outbound API calls and financial transactions with Verifiable Intent proofs, so disputes are resolvable and audit trails are tamper-resistant. Drop-in integration for OpenClaw skills and Hermes actions.

SDKOPEN-SOURCESECURITYPAYMENTSMIDDLEWARE

CompetitiveView Opportunity →