Mastercard Verifiable Intent

A dated reading of what is claimed, reported, and independently verified in the current evidence.

Current reading

The readiness gap, in one scan

AI-assisted assembly · derived results

Evidence strength Critical

Decision

Human editorial judgment · 2026-06-28

Track; not yet

Why: It directly targets our exact problem (machine-checkable proof of user intent for agent purchases), is Apache-2.0 open source on standards we already use (FIDO/EMVCo/IETF/W3C, SD-JWT/JWS/JWK/RFC 7800), and now anchors a GA Mastercard product (Agent Pay for Machines) — but it is Draft v0.1 with non-trivial verifier-side work, so design against it now rather than depend on it.
Next: Pull the open-source spec from github.com/agent-intent/verifiable-intent (Apache 2.0, Draft v0.1), map its SD-JWT three-layer delegation chain + eight constraint types against our existing AP2/ACP mandate model (Rule #12 protocol_type/JSONB), and prototype a verifier against our crypto layer behind a flag — do NOT touch Rule #29 protected components.

Constraints

No named blocker is present in the current public projection.

Evidence summary

AI-assisted assembly

Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.

Publication record

Initial public reading

This is the initial public reading. No earlier readiness change is recorded.