Notifications
Clear all
Topic starter
15/08/2026 6:45 pm
TL;DR: Agent-driven checkout flows break down when the system cannot bind a purchase session to a verified user, because personalization, order history, and authorization trail all depend on identity continuity, according to Descope. The core issue is that existing agent commerce patterns assume a user identity will be present, but anonymous agents leave merchants unable to govern who is acting on whose behalf.
NHIMG editorial — based on content published by Descope: Build an Ecommerce UCP Server With Identity Linking
By the numbers:
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, inappropriately sharing sensitive data, and revealing access credentials.
Questions worth separating out
Q: How should security teams handle agent checkout flows that start without a verified user identity?
A: They should allow anonymous browsing but require identity linking before any checkout, order lookup, or other user-specific action.
Q: Why do agent-driven shopping flows need user identity continuity?
A: Because the commercial value of the session depends on recognising the customer across tasks and channels.
Q: Where does agent authorisation fail if scope is checked only at login?
A: It fails the moment the agent tries to switch from a low-risk browse action to a sensitive operation like checkout or order retrieval.
Practitioner guidance
- Require linked identity before purchase completion Block checkout completion until the agent has a verified user binding, and reserve anonymous sessions for catalog browsing only.
- Separate browse scopes from transaction scopes Map catalog access, checkout management, and order retrieval to distinct scopes so the agent cannot inherit payment or customer data privileges from browsing.
- Make consent claims auditable end to end Preserve the user consent record, token scopes, and session identifiers so finance, fraud, and support teams can reconstruct who authorised the action and when.
What's in the full article
Descope's full article covers the operational detail this post intentionally leaves for the source:
- A complete FastMCP implementation showing how the UCP server, OAuth provider, and checkout tools fit together
- The exact discovery document fields used for capabilities, payment handlers, and identity linking scopes
- Sample middleware logic for enforcing tool-level scope checks and returning structured UCP error envelopes
- End-to-end code for storing order history under the user's sub claim and reusing verified claims downstream
👉 Read Descope's guide to building an ecommerce UCP server with identity linking →
Agentic commerce identity linking: are your checkout flows ready?
Explore further
15/08/2026 6:46 pm
Identity linking is the control that prevents agentic commerce from collapsing into anonymous transaction handling. Without a verified user binding, an agent can move through browse and checkout states without any durable answer to who authorised the action. That breaks receipt routing, order history, loyalty attribution, and dispute handling in one stroke. Practitioners should treat identity linking as the prerequisite for governed agent commerce, not as an optional convenience.
A few things that frame the scale:
- Only 52% of companies can track and audit the data their AI agents access, leaving 48% with a complete blind spot for compliance and breach investigation, according to the AI Agents: The New Attack Surface report.
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, inappropriately sharing sensitive data, and revealing access credentials.
A question worth separating out:
Q: What should teams do with consent and identity records for agent purchases?
A: They should retain the consent artefact, token scope set, and user binding so support, fraud, and audit teams can reconstruct the transaction later. That evidence is what converts delegated commerce from a black box into a reviewable identity event. If the record cannot be recovered, the governance model has failed.
👉 Read our full editorial: Identity linking is the missing control for agentic commerce
