MapGraphSeamsCalendarIntroductionDisclosureMethodFor agents and tools

Updated weekly, new versions on Mondays · Corrections: open an issue

Verifiable Intent

Industryspecificationcore entry

Verified 2026-10-13. Status as of 2026-10-13. All entries.

Seams: S4

Status

Draft v0.1 specification, maintained by Mastercard according to its README (Apache-2.0, tag v0.1.0). The FIDO Alliance release of 2026-04-28 says Mastercard has contributed it to the Payments Technical Working Group. On 2026-10-13 the last commit on main is of 2026-04-20 (356c296, PR #23), v0.1.0 is the only tag, no release is listed, and the README header reads "Draft (v0.1). Maintained by Mastercard; open to multi-stakeholder contribution."

Relevance

The repository describes it as an "Open specification for cryptographic agent authorization in commerce"; the README defines a "layered SD-JWT credential format" giving cryptographic evidence that an agent's actions stayed within the scope the user delegated. Layers hold mandates (signed claims on checkout details or payment parameters) and user constraints; the merchant receives the checkout mandate (layer 3b, Autonomous mode).

The FIDO release says "Mastercard has contributed its Verifiable Intent framework, co-developed with Google and designed to work with AP2"; Google as co-developer: not found in the repository pages read, 2026-10-02.

Committed next

None declared in the sources read.

Boundary

Out of scope in the README: transport, key management, provider enrolment, agent platform APIs, dispute resolution, regulatory compliance mapping.

Sources

Overlaps

Mastercard Agent Pay, Universal Commerce Protocol (UCP), EMV Agentic Payments Framework for Specifications (draft for public feedback), Agent Payments Protocol (AP2)

Neighbours in the map

Neighbours of Verifiable Intent in the map Each circle is an entry of the map and links to its page; the colour is the kind of body behind it, a filled circle is a core entry and a dashed circle a context entry. The entry in the middle, with the entries it overlaps and the entries named by the same seams. Overlaps (10)Share a seam (6)IETF vcon (Virtualized Conversations WG) (IETF, core)IETF vcon AAIF Agentic Commerce Working Group (AAIF, core)AAIF Agentic Commerce W… x402 (Linux Foundation, core)x402 Agent Payments Protocol (AP2) (Industry, core)Agent Payments Protocol Agentic Commerce Protocol (ACP) (Industry, core)Agentic Commerce Protoc… EMV Agentic Payments Framework for Specifications (draft for public feedback) (Industry, core)EMV Agentic Payments Fr… FIDO Alliance agentic authentication and payments work (Industry, context)FIDO Alliance agentic a… Mastercard Agent Pay (Industry, core)Mastercard Agent Pay Universal Commerce Protocol (UCP) (Industry, core)Universal Commerce Prot… Visa Trusted Agent Protocol (TAP) (Industry, core)Visa Trusted Agent Prot… Payment HTTP Authentication Scheme (draft-httpauth-payment, Tempo Labs and Stripe) (IETF, context)Payment HTTP Authentica… S4 Browser vendor positions on WebMCP (WebKit, Mozilla, Chrome, Edge) (Independent, core)Browser vendor position… S4 EMILIA Protocol (individual drafts and open-source gate) (Independent, context)EMILIA Protocol S4 Personal Agent Consent & Trust Protocol (PACT), published by Decagon with Instinct (Industry, core)Personal Agent Consent… S4 Personal Agent Protocol (PAP, "Poppy"), published by Sierra with Meta (Industry, core)Personal Agent Protocol S4 Shopify, MCP surfaces for buyer agents, developers and merchants (Industry, context)Shopify S4 Verifiable Intent

Solid lines: overlaps declared by one of the two entries. Dashed lines, coloured by seam: entries named by the same seam (S1 to S4) in the seams note. Every node is a link.

Evidence and coverage

Read
On 2026-10-13: the head, tags and releases of the repository, the README status line, and the state of PR #40 (open, no comment since 2026-09-28) and issues #9, #10, #22 and #41. agent-intent/verifiable-intent: README, specification, landscape pages (2026-10-02); all 40 issues and pull requests with comments (2026-10-03; #10, #9 and #22 partly read); FIDO release.
Not read
Mastercard announcement of 2026-03-05.
Not found
Not found in the 40 items read, 2026-10-03: standards-body submission, EMVCo.

Open proposals

ProposalAuthorDateStateLink
Issue #41: question whether the cumulative budget is meant to be tracked per merchant, since the L3a sd_hash includes the merchant disclosure (no comment on 2026-10-13).a participant2026-10-03openhttps://github.com/agent-intent/verifiable-intent/issues/41
Environment-state constraint types for autonomous execution (PRs #9, #11, #22, #32, issue #28)a participant2026-03-17openhttps://github.com/agent-intent/verifiable-intent/pull/9
agent_attestation scheme, an SD-JWT agent passporta participant2026-09-21openhttps://github.com/agent-intent/verifiable-intent/issues/36
VI implementation for an EUDI walleta participant2026-03-31openhttps://github.com/agent-intent/verifiable-intent/issues/19
Questions on intent standing after authority change (#35) and on purchase-request matching (#37)a participant2026-09-18openhttps://github.com/agent-intent/verifiable-intent/issues/35
Fix for prompt_summary accepted by the SDK but never written to L2 (issue #39, PR #40)a participant2026-09-28openhttps://github.com/agent-intent/verifiable-intent/issues/39

Payment comparison row

Owner / governance
Maintained by Mastercard (README), "open to multi-stakeholder contribution"; Apache-2.0; contributed to the FIDO Payments Technical Working Group
Version and state
Draft v0.1; tag v0.1.0; last commit 2026-04-20
What it signs
A delegation chain of SD-JWT credentials carrying mandates and user constraints; checkout-payment integrity binding
Who signs
Layer 1 credential provider; layer 2 user device key; layer 3 (Autonomous mode) agent key
Receipt or record
Tamper-evident record of what the user delegated (README); receipt object: not found in README, design rationale, 2026-10-02
Dispute
Dispute resolution is declared out of scope in the README
Source
https://github.com/agent-intent/verifiable-intent/blob/main/README.md