Consumer-Authorized Intent.
Consumer-authorized intent is the record of what a shopper allowed an AI agent to buy on their behalf. EMVCo's draft agentic payments framework proposes Intent Services to register and manage it across a card transaction.
Consumer-authorized intent is the payments version of a consent record. The consumer says "buy these tickets, under this price, this week," and every party in the transaction needs to be able to see that instruction and check the purchase against it. EMVCo's proposal makes that record a shared service rather than something each agent, wallet and issuer keeps separately.
The OpenID Foundation's response adds the identity half. Knowing what was authorized is not enough; a verifier also needs to know which agent, run by which Agent Provider, is presenting it, and every actor should sign its own step so no one can deny it later. Sources: EMVCo draft framework and OIDF responds to the EMVCo draft.
Our reading. For CIAM teams near payments, the intent record will depend on records you already hold: the verified customer, their consent, and the agent grant. Keep them linked and exportable. Related artifacts include signed authorization verdicts for per-payment decisions and Know Your Agent for the agent itself.
Common questions
What are EMVCo Intent Services?
Intent Services are a shared layer proposed in EMVCo's draft Agentic Payments framework (September 1, 2026). They let card payment participants register, reference, retrieve and manage what a consumer authorized an AI agent to buy, before, during and after a transaction. The draft is a consultation document, not a final specification.
What is an Agent Provider?
Agent Provider is the term the OpenID Foundation's October 8, 2026 comments use for the organization that operates an AI agent. The comments ask that relying parties be able to confirm the Agent Provider behind an agent using signed, attested metadata, so agent identity can be checked separately from the consumer's delegated authority.
Why separate agent identity from delegated authority?
They answer different questions. Agent identity says which software, run by which provider, is acting. Delegated authority says what this consumer allowed it to do. Mixing them means a trusted agent could be assumed to have authority it was never given, or a valid grant could be honored for an unknown agent.
Is the EMVCo agentic payments framework final?
No. The comment period closed September 30, 2026, and EMVCo has said detailed specification work follows the consultation. No participant is required to adopt Intent Services yet.
Related terms
In the guides
Authorization Patterns for Agentic Workflows: Delegation, Constraints, and Just-in-Time Permissions
AI agents need authorization models that handle delegated permissions, multi-step workflows, and least-privilege at machine speed. The patterns that work and the ones being invented.
Know Your Agent: Identity for AI Agents That Buy on a Customer's Behalf
What a CIAM team must build when a customer's AI agent shows up at login, account, or checkout: delegated consent, agent sessions, step-up, audit, and revocation.
PCI DSS 4.0 and CIAM: Identity Requirements for Payment Workloads
PCI DSS 4.0's Requirements 7, 8, and 10 directly constrain CIAM design for any system handling cardholder data. MFA, audit logs, role separation, and the gotchas that fail QSA audits.