Mastercard Verifiable Intent Integration
SD-JWT three-layer credential — LCP integrates as a custom Layer 2 constraint via URN naming.
This section is advisory and non-prescriptive. The illustrations describe current possibilities and limitations rather than canonical shapes. The Verifiable Intent stewards are invited to publish authoritative LCP integration guidance for the framework.
What it is
An open-source cryptographic framework for consumer authorization in agent-initiated transactions. Uses a three-layer SD-JWT credential format: Layer 1 (Identity), Layer 2 (Intent — user-signed authorization with constraints), Layer 3 (Action — agent-signed execution record, autonomous mode only). Layer 2 registers a fixed set of constraint types and explicitly permits implementations to define custom types using URN or reverse-domain naming.
Tier A — Available today
LCP can register a custom Layer 2 constraint carrying atrHash, jurisdiction, and dispute method. The custom constraint is included in the consumer's Layer 2 credential alongside the registered constraints, signed by the user's device key, and carried through the mandate chain:
{
"layer": 2,
"constraints": [
{ "type": "mandate.payment.amount_range", "value": "..." },
{ "type": "<reverse-domain>.lcp-terms-hash", "value": "0x7f83b165..." },
{ "type": "<reverse-domain>.lcp-jurisdiction", "value": "USA" },
{ "type": "<reverse-domain>.lcp-dispute-method", "value": "AAA Commercial Arbitration Rules" }
]
}The custom constraint inherits Layer 2's signature, integrating LCP into the consumer authorization chain without upstream protocol change.
Tier B — Forward work
Standardizing LCP-aware constraint types as registered Layer 2 types (rather than custom URN-named types) would give parsers standardized handling across implementations.
Conceptual relationship
Verifiable Intent captures the consumer's authorization chain — who authorized, under what constraints, whether the agent stayed within scope. LCP captures the merchant's terms — what was offered, under what conditions, with what recourse. The combined evidence package — consumer authorization chain + LCP terms record + LCP signed acceptance — provides a complete evidentiary foundation for dispute resolution.
| What | Source |
|---|---|
| Consumer authorized this agent | Verifiable Intent Layer 1-2 |
| Agent stayed within constraints | Verifiable Intent Layer 2-3 |
| Merchant offered these terms | LCP atrHash |
| Both parties agreed | LCP Level 3+ signed acceptance record |
| Dispute resolution available | LCP Level 4 (disputeResolution) |
Steward invitation
The Verifiable Intent stewards are invited to register LCP-aware constraint types in Layer 2 and to publish guidance on the relationship between consumer-side constraints and merchant-side LCP records.
AP2 Integration
Agent Payments Protocol — LCP travels alongside SD-JWT mandates in transport metadata; embedded mandate fields as forward work.
Relationship to Authorization Protocols
LCP captures the merchant's side of a transaction. Authorization protocols capture the consumer's side. Together they form a complete agreement.