Join our Newsletter — 33% off our NHI Course
Authentication, Authorisation & Trust

Intent Mandate

← Back to Glossary
By NHI Mgmt Group Updated November 4, 2026 Domain: Authentication, Authorisation & Trust

An Intent Mandate is a cryptographically signed authorization that lets an agent make purchases within defined limits when the user is absent. It records the identity being represented, the spending boundary, and the permitted merchant context, making consent provable and later reviewable.

What an Intent Mandate does

An intent mandate turns a user’s purchase intent into a verifiable authorization object. In practice, it lets an agent act only within the spending limit, merchant context, and represented identity that were explicitly signed, so the later transaction can be checked against the original consent rather than inferred after the fact.

Why cryptographic signing matters

The signature is what makes the mandate more than a policy note or a chat instruction. It binds the user-approved terms to the exact authorization event, reducing ambiguity over who approved what, when, and under which conditions. That matters when an agent operates while the user is absent and the decision has to remain provable later.

Because the mandate records the represented identity and the permitted merchant context, it creates a tighter trust boundary than a generic payment token. The relevant security question is not just whether the agent can pay, but whether it can only pay in the way the user intended.

How intent mandates fit agentic purchasing

Intent mandates sit between user consent and delegated action. They are designed for cases where an autonomous or semi-autonomous agent needs bounded authority to complete a purchase without fresh human confirmation at every step. That makes them a control for constrained delegation, not a blanket payment license.

For agentic commerce, the mandate should be understood as a machine-readable expression of approval that downstream systems can validate. A well-formed mandate supports merchant checks, amount checks, and later audit review without depending on memory, screenshots, or informal approval trails.

NHIMG’s Agentic Commerce Identity Guide covers the identity model behind AI agent payments, including verifiable mandates, tokenised credentials, AP2, and the controls that make agent checkout safer.

What can go wrong without strong mandate controls

If mandate scope is too broad, an agent can spend outside the user’s real intent even when the transaction is technically authorised. If the merchant context is weakly defined, a mandate may be reused in places the user never meant to approve. If signatures are not verifiable end to end, the organisation may be left with a dispute trail that proves a payment happened but not that consent was valid.

These failure modes are especially important when mandates outlive the immediate session that created them. The longer an authorization remains usable, the more valuable it becomes to an attacker, a dishonest intermediary, or an overly permissive integration.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

OWASP API Security Top 10 addresses the attack and risk surface, while NIST SP 800-53 Rev 5 sets the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementIntent mandates rely on controlled, reviewable authorization material with clear lifecycle limits.
IA-9 — Service Identification and AuthenticationThe mandate is used by an agent acting on behalf of a user, which requires strong machine-to-machine authentication.
AC-6 — Least PrivilegeThe mandate is defined by narrow spending and merchant limits that should constrain delegated action.
Recommendation — Manage mandate-related secrets and cryptographic material under IA-5 so approvals remain bounded and revocable. Authenticate agent-mediated purchase flows under IA-9 before accepting a signed mandate. Apply AC-6 to restrict agent purchase authority to the smallest approved scope.
OWASP API Security Top 10API5 — Broken Function Level AuthorizationAn agent buying on behalf of a user is an authorization problem where only specific actions should be allowed.
API2 — Broken AuthenticationA signed mandate only helps if the system can reliably authenticate the actor presenting it.
Recommendation — Validate that purchase actions are explicitly authorised so agents cannot invoke broader buying functions. Require strong authentication before a mandate can be accepted or replayed in a purchase flow.

Practitioner guidance

Governance implication: Treat the mandate as a first-class authorization record, not a convenience layer. The approval must define the represented identity, spending boundary, merchant scope, and expiry in a way that can be enforced and reviewed consistently across systems.

What to watch for: Pay close attention when mandate language is vague, merchant context is broad, or the approval can be replayed across sessions. Those are the conditions that most often turn a bounded delegation mechanism into an open-ended spending right.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 4, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org